Errors in Check Home Assistant configuration

Configuration
1

I need some help PLEASE.

Early this month an auto update to supervisor on my Home Assistant crashed my installation. I was running a Ubuntu system with docket as outlined by JuanMTech some time. I followed his YouTube install back then on a NUC-i3

With this install being unsupported now I decided to rebuild and go with the standard image install on the NUC-i3.
I flashed the HA NUC image to an NVMe drive and restored a backup I created from 2022.7.6 which was just prior to the crash.
I am now running image
All seems to be back the way it was prior to the supervisor issue but I noticed that there were some updates to do
image
Part of my procedure on updates is to run the Check Home Assistant Configuration so that I can see if there are any problems in loading the update.
Well there were and there was quite a list. I have no idea on what to do now so need some help please.
I have listed below the file generated by the Check Home Assistant Configuration add-on.
I note that there are some references to a HACS component Sonoff which are probably down to @AlexxIT and SonoffLAN but the latter ones in the file I have no idea about.

I was hopeful that using a supported system might keep me away from most issues

image
image590×988 68.6 KB

This is the error file I got.
I had to put it on my google drive because there were too many characters to fit in post.
check_config.txt
Thank you

2

your txt isn’t shared properly via google drive

4

yep, have access

5

well supported / unsupported wont’ change your config check. It looks like it’s failing to install 3 packages.

6

I don’t understand what you mean?
Can you expand please.
Is there anything I can do?

7

I’ve never used the check configuration addon, so I just had to learn it real quick. First, that addon is deprecated. You no longer need it. If you update, home assistant will still start even if you have errors and the errors will be in the logs.

With that being said, I think that’s the route you should go and post your logs here.

8

Just to put it into perspective, that addon failed my config, yet I have no errors in my logs and everything is working on the current version.

1 Like
9

OK, I will do a backup and the update.
I did note that the addon was depreciated but did not think it might be the cause.
At 70 yrs I am a bit slow on the uptake Heh heh
I will post any errors I get
Thank you

10

I have performed the update on the core and as you said it worked fine.
I did get one error in the log but that has to do with too many calls on the Efergy API which is where I get my consumption of electricity. I have tried to reduce the number of calls by reducing time between calls without success.
However there is nothing that wan not there before.

Thank You again!

Logger: homeassistant.helpers.entity
Source: components/efergy/sensor.py:167
First occurred: 8:26:03 AM (1 occurrences)
Last logged: 8:26:03 AM

Update for sensor.daily_consumption fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 514, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 709, in async_device_update
    raise exc
  File "/usr/src/homeassistant/homeassistant/components/efergy/sensor.py", line 167, in async_update
    data = await self.api.async_get_reading(
  File "/usr/local/lib/python3.10/site-packages/pyefergy/__init__.py", line 203, in async_get_reading
    _data = await self._async_req(command, params=params)
  File "/usr/local/lib/python3.10/site-packages/pyefergy/__init__.py", line 150, in _async_req
    raise exceptions.APICallLimit(
pyefergy.exceptions.APICallLimit: API key has reached calls per day allowed limit
1 Like