Me too. What gives?
Look at the reverse proxy breaking change. That is your issue.
It looks like Iāve solved my issue by installing pkgconf package. It contains the pkg-config binary.
apt install pkgconf
had same issue, I renamed the deebot in the app, restart and working again
Look at the reverse proxy breaking change.
I think so if youāre using an venv
Beware the timeout with authentication. I had a similar message on mine, and I just went into the configuration for the integration and set the interval to something massive (36000 I think) and left it for about fifteen minutes. After that, I restarted HA and it all came back.
Their server blacklists your IP occasionally and the solution is to back off a while. Changing the interval is an easy way to do that. Alternative is remove the integration, then re-add it after 15 mins. Or just powering down your HA box for a while.
I had an issue with an esp32 camera running through esphome when updating to 2021.7 the log said the esphome API connection failed 100+ times. It is my only esp32 camera and the only esphome device that had this issue.
Iām experiencing the exact same error message, also āConfiguration validationā does not revert with a response when āCheck Configurationā button is pressed. Having to restart the host with a VM reinitialization. Have never see this error prior to 2021.7
Error message:
Failed to call service homeassistant/restart. **init** () got an unexpected keyword argument āencodingā
Iāve updated, installed Forecast.Solar and get this error: āRetrying setup: Error occurred while communicating with Forecast.Solar APIā.
Have rebooted Home Assistant and still no luck. I can see that I am registered with forecast.solar as on their website there is a panel just near where I live. But doesnāt seem to work in home assistant. Only log issue I can see is: āConfig entry āHomeā for forecast_solar integration not ready yet: ālistā object has no attribute āitemsā; Retrying in backgroundā
Any ideas? Or is there a better place to report this?
3 Likes
Also have connection issues (as well as no image) from my esphome (1.19.0) esp32 camera. Besides the camera entity, I have a light entity for the on-board LED and restart switch, they both go unavailable every 10 seconds. Looking at the esphome logging, it looks like every time an image is captured/transmitted, Home Assistant disconnects from (or is disconnected by, canāt tell which) the esp32. Had been working flawlessly for months through multiple esphome and home-assistant versions. A few other people mentioned an issue with 2021.7 earlier in this thread as well.
I am getting the exact same issue, or
āRetrying setup: Error occurred while communicating with Forecast.Solar APIā
Thought it might possibly be because of this new release a lot of people may have jumped on-board and now its over-taxing their API. Says 8 installations, though not sure how frequently that updates.
2 Likes
Setup failed for fritz: Unable to import component: cannot import name 'get_all_profiles' from 'fritzprofiles' (/usr/local/lib/python3.9/site-packages/fritzprofiles/__init__.py)
If you havenāt seen it already in the replies to the github issue, or for anyone else experiencing this, there is a conflict between library version required by the custom component FritzBox Tools, and the builtin Fritz Box Tools. I previously had both installed, as the custom component had some features that the built in integration didnāt, but only the built in integration provides device tracking.
It seems most/all of the features are in the built in integration now, so delete that old custom integration and restart, and the required library will get updated.
3 Likes
Did I miss something in the release notes? Why did the colors in my graphs change?
3 Likes
I was just about to post about that myself.
Its not just the colours for me, its seems to be a significant restyle of the graphs.
I had to roll back as it has screwed the layout of several pages due to sizing etc. changing. It might not look like much but when you have a page with quite a few graphs it adds up.
For example, top is old graph, bottom is the new format/colours.
1 Like
Bram mentioned it in the release party stream today (near the end I think). It was a frontend change, and the release notes donāt always cover them in great detail.
1 Like
Have you updated the firmware on the device, it may now require a certain esphome version?
RainBird integration: āSetup failed for rainbirdā
Error after 2021.7 update, any suggestion appreciated.
Logger: homeassistant.setup
Source: components/rainbird/__init__.py:4
First occurred: 4:50:07 PM (1 occurrences)
Last logged: 4:50:07 PM
Setup failed for rainbird: unknown error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 201, in _async_setup_component
component = integration.get_component()
File "/usr/src/homeassistant/homeassistant/loader.py", line 490, in get_component
cache[self.domain] = importlib.import_module(self.pkg_path)
File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 855, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "/usr/src/homeassistant/homeassistant/components/rainbird/__init__.py", line 4, in <module>
from pyrainbird import RainbirdController
File "/usr/local/lib/python3.9/site-packages/pyrainbird/__init__.py", line 14, in <module>
from pyrainbird.resources import RAIBIRD_COMMANDS
File "/usr/local/lib/python3.9/site-packages/pyrainbird/resources/__init__.py", line 6, in <module>
RAIBIRD_COMMANDS = json.loads(resource_string('pyrainbird.resources', 'sipcommands.json').decode("UTF-8"),
File "/usr/local/lib/python3.9/json/__init__.py", line 359, in loads
return cls(**kw).decode(s)
TypeError: __init__() got an unexpected keyword argument 'encoding'
1 Like
In my case I was on esphome 1.16.something, but tried updating to 1.19.0 (current as of writing this). Didnāt help.
/edit: Actually, just realized thereās a 1.19.4 version (didnāt see it at first), so updated and still the same. Hereās a sample of the esphome logging:
[21:35:46][D][esp32_camera:156]: Got Image: len=18419
[21:35:46][D][api:067]: Disconnecting Home Assistant 2021.7.0 (192.168.1.78)
[21:35:46][D][api.connection:630]: Client 'Home Assistant 2021.7.0 (192.168.1.78)' connected successfully!
[21:35:56][D][esp32_camera:156]: Got Image: len=18548
[21:35:56][D][api:067]: Disconnecting Home Assistant 2021.7.0 (192.168.1.78)
[21:35:56][D][api.connection:630]: Client 'Home Assistant 2021.7.0 (192.168.1.78)' connected successfully!
[21:36:06][D][esp32_camera:156]: Got Image: len=18355
[21:36:06][D][api:067]: Disconnecting Home Assistant 2021.7.0 (192.168.1.78)
[21:36:06][D][api.connection:630]: Client 'Home Assistant 2021.7.0 (192.168.1.78)' connected successfully!
[21:36:16][D][esp32_camera:156]: Got Image: len=18420
[21:36:16][D][api:067]: Disconnecting Home Assistant 2021.7.0 (192.168.1.78)
[21:36:16][D][api.connection:630]: Client 'Home Assistant 2021.7.0 (192.168.1.78)' connected successfully!
The rest of my esphome devices (running a few different but recent esphome versions) are all fine, itās only the camera with a disconnect issue.