Closed sezlony closed 5 days ago
Hey there @hunterjm, @uvjustin, @allenporter, mind taking a look at this issue as it has been labeled with an integration (stream
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
stream documentation stream source (message by IssueLinks)
Try this, for me it's help
Older firmware versions do not expose the necessary information the integration needs to function. Ensure the camera is updated to the latest firmware prior to setting up the integration. Note that Reolink auto update and check for update functions in the app/windows/web client often do not show the latest available firmware version. Therefore check the version in the Reolink download center online.
Ensure at least one of the HTTP/HTTPS ports is enabled in the windows/web client under Settings > Network > Advanced > Port Settings, see additional instructions on the Reolink site.
The problem
At first it started with a regular "
Error opening stream (ERRORTYPE_110...)
", but instead of reconnecting by itself as it used to, the situation escalated to this:which is very unusual, never seen before.
Thanks to this cute one, the camera was unaccessible for 3,5 hours...
The original ERRORTYPE 110 is already reported in #116268.
What version of Home Assistant Core has the issue?
core-2024.3.3
What was the last working version of Home Assistant Core?
core-2024.3.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/stream
Diagnostics information
config_entry-reolink-e36d438a58aab698c970b10632d8a977.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I don't know what is happening, but all of my cameras event connection changed to "onvif push" since I don't know when, although I sweat blood to set up NGINX, to have SSL locally... so I'm currently very dissapointed in all this HA thing