Closed RobertD502 closed 1 year ago
Hey there @starkillerog, mind taking a look at this issue as it has been labeled with an integration (reolink
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
reolink documentation reolink source (message by IssueLinks)
It is now causing supervisor errors:
[139876157196736] Supervisor from 172.30.32.2 (HomeAssistantSupervisor/2023.09.3 aiohttp/3.8.5 Python/3.11): Client unable to keep up with pending messages. Stayed over 1024 for 5 seconds. The system's load is too high or an integration is misbehaving; Last message was: {"id":18,"type":"event","event":{"event_type":"entity_registry_updated","data":{"action":"update","entity_id":"binary_sensor.backyard_deck_cell_motion_detection_1146"
Note the appended number on the entity created by the Reolink integration - it is continuing to create endless entities.
Edit: looks like this is related to the Onvif integration, which is then directly affecting the reolink integration:
It is continuing to ramp up creating entities. Once the Onvif integration was disabled and I re-enabled the Reolink integration, everything worked fine on the Reolink side.
@RobertD502 So you had both Reolink and ONVIF configured at the same time. Could you figure out (from the entity_registry file) if all those duplicate entities are comming from the Reolink or the ONVIF integration?
I do not see anything weird in the Reolink logs provided...
Because the ONVIF and Reolink integration will create entities that will be linked to the same device.....
Because the ONVIF and Reolink integration will create entities that will be linked to the same device.....
Hey, thanks, but as I mentioned I narrowed it down to not being Reolink related. I figured out that the Onvif integration was creating a new motion binary sensor whenever an event came in - with Reolink sharing the same devices it was causing the UI to glitch out when visiting the Reolink device page and wrongfully made me assume it was Reolink related.
I confirmed that it is not caused by Reolink as I have Reolink up and running without a problem with onvif disabled. Aside from that, at that time, I raised an issue in relation to the onvif bug and some regressions made to the onvif integration caused it, but that seems to have been fixed now and should be out in the next beta.
Thanks for the update!
The problem
There seems to be an issue with the reolink integration not acting as expected after updating to
Home Assistant 2023.10.0b0
. For starters, when clicking on the device for my reolink config, initially, it reports as the device not being found. Eventually, it loads, but the entities list continues to increase and causes Home Assistant to lock up. See video below:https://github.com/home-assistant/core/assets/52541649/60ead2a7-0be3-4445-a66b-f3d4df7169b8
What version of Home Assistant Core has the issue?
2023.10.0b0
What was the last working version of Home Assistant Core?
2023.9.3
What type of installation are you running?
Home Assistant OS
Integration causing the issue
reolink
Link to integration documentation on our website
https://www.home-assistant.io/integrations/reolink/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?