I’m running the latest possible firmware and it’s still an issue.
Have opened an issue on github https://github.com/home-assistant/core/issues/52718
He @hoover1980, thank you very much! I will add the config as you mentioned.
This is helpfull information!
I have neither.
My http config looks like that:
http:
Same here ESP cameras not working anymore!
Follow the githib issue.
My Alexa interface was broken with the same message but that fixed it for me.
Interesting! What does Home Assistant log about those requests?
you’re welcome. Each time i reconnected to my external cloudflare proxy DNS address, I got an error with a new IP address. So I came to the conclusion I had to whitelist every IP of cloudflare. Fortunately cloudflare has a list of subnets and it did the trick when I added them.
For the people using duckdns. I can not find a list of ip’s or subnets used by duckdns or if it uses different IP addresses when you reconnect to you external duckdns address. But I think it does. Just press F5 in the browser and see if the error fills up with different IP adrresses. Duckdns is not a proxy. So ignore this part.
1 Like
It’s not a proxy so irrelevant
1 Like
You are correct. It’s just a dynamic DNS forwarder.
The ‘Hourly gas’ is now missing from the DSMR integration.
Instead of using the Derivative integration, wouldn’t be also posible to use Utility Meter to create a new sensor from the gas usage and cycle that hourly?
Any advantage or disadvantge in using that intead of the Derivative integration?
The utility meter would reset every hour in that case, while a derivative can make a sensor that shows a moving window. Its personal preference for what you prefer/need/like to see.
You can find more information about the derivation solution here: Issue with derivative as replacement of DSMR gas usage per hour · Issue #52538 · home-assistant/core · GitHub
Is there a specific reason why you are looking for another solution instead of the derivative integration?
Same here. ESPHome camera not working.
Issue 1: HomeKit Controller (to HOOBS) not working properly anymore. Needs to reload constantly
Gives several Errors in Server Log:
Exception in async_write_ha_state when dispatching 'homekit_controller_FA:0D:74:06:FE:3E_state_updated': () Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 419, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 450, in _async_write_ha_state attr = self.capability_attributes File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 217, in capability_attributes supported_features = self.supported_features File "/usr/src/homeassistant/homeassistant/components/homekit_controller/climate.py", line 533, in supported_features if self.service.has(CharacteristicsTypes.TEMPERATURE_TARGET): File "/usr/src/homeassistant/homeassistant/components/homekit_controller/__init__.py", line 64, in service return self.accessory.services.iid(self._iid) File "/usr/src/homeassistant/homeassistant/components/homekit_controller/__init__.py", line 52, in accessory return self._accessory.entity_map.aid(self._aid) File "/usr/local/lib/python3.9/site-packages/aiohomekit/model/__init__.py", line 283, in aid return next(filter(lambda accessory: accessory.aid == aid, self.accessories)) StopIteration
Issue 2: Google Chromecast integration causing issues. Port is being reset and many errors
Gives Errors in Server Log:
Logger: pychromecast.socket_client
Source: /usr/local/lib/python3.9/site-packages/pychromecast/socket_client.py:661
First occurred: 24:02:33 (3 occurrences)
Last logged: 03:49:26
[Living Room Speaker(10.10.0.103):8009] Heartbeat timeout, resetting connection
[Bedroom Display(10.10.0.13):8009] Heartbeat timeout, resetting connection
I’m now seeing: “Retrying setup: ‘list’ object has no attribute ‘items’”
Seeing this error every hour.
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:87
First occurred: 20:00:00 (1 occurrences)
Last logged: 20:00:00
Error doing job: protocol.resume_writing() failed
Traceback (most recent call last):
File "/usr/local/lib/python3.9/asyncio/transports.py", line 294, in _maybe_resume_protocol
self._protocol.resume_writing()
File "/usr/local/lib/python3.9/asyncio/sslproto.py", line 516, in resume_writing
self._app_protocol.resume_writing()
File "/usr/local/lib/python3.9/site-packages/aiohttp/base_protocol.py", line 31, in resume_writing
assert self._paused
AssertionError
Possibly due to trying to play a chime on my Chromecast Audio (the chime is working).
1 Like
Yep, also seeing this. It works initially after a restart and then all entities show as unavailable. If i reload the integration then entities come back but only for a short period and go back to unavailable approx 5 minutes later or whenever the entity state is updated
The same problem, if you physically remove the camera module from the board, the connection remains stable and the other functions of the esp32cam module work stably. I tried to upgrade the cameras from 1.19-dev to 1.20-dev - no changes, apparently a problem when receiving an image from the camera.