could not verify a working RTSP url for channel 0

[Scoff123]

The problem

After updating to HA Core 2024.7.1 I've had no issues with my Reolink integration, until today - after my normal 2am reboot of my Reolink Doorbell Camera (PoE). I performed a restart of HA today subsequent to the doorbell restart, and I have the following error loggd, which I've not had before

Logger: reolink_aio.api
Source: components/reolink/host.py:126
First occurred: 13:11:51 (2 occurrences)
Last logged: 13:11:51

Host 192.168.1.105:443, could not verify a working RTSP url for channel 0, stream sub
Host 192.168.1.105:443, could not verify a working RTSP url for channel 0, stream main

While searching for this message online, I cam across the below issue that was resolved:
#107104

if this helps?

What version of Home Assistant Core has the issue?

2024.7.1

What was the last working version of Home Assistant Core?

2024.7.0

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

config_entry-reolink-64eb8415e2cae13ed0ff041caae5e386.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: reolink_aio.api
Source: components/reolink/host.py:126
First occurred: 13:11:51 (2 occurrences)
Last logged: 13:11:51

Host 192.168.1.105:443, could not verify a working RTSP url for channel 0, stream sub
Host 192.168.1.105:443, could not verify a working RTSP url for channel 0, stream main

Additional information

No response

[home-assistant]

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!

Code owner commands

Code owners of reolink can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign reolink Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

reolink documentation
reolink source
_{^{(message by IssueLinks)}}

[starkillerOG]

How much time was there between the reboot of the camera and the restart of HomeAssistant?
If the doorbell is still booting, a restart of the reolink integration will indeed show this error.

Please try clearing the HomeAssistant log, restarting the reolink integration and see if the error happens again.

[Scoff123]

Thanks for the response. There was around 8 hours between the doorbell rebooting and when I rebooted Home Assistant.

I've just cleared logs, and reloaded the Reolink Integration, and it has generated the same error:

Logger: reolink_aio.api
Source: components/reolink/host.py:126
First occurred: 10:09:29 (2 occurrences)
Last logged: 10:09:29

Host 192.168.1.105:443, could not verify a working RTSP url for channel 0, stream sub
Host 192.168.1.105:443, could not verify a working RTSP url for channel 0, stream main

No Home assistant restarts or doorbell restarts were involved this time, just a reload of the Reolink Integration.

[starkillerOG]

That is weird, did you change anything in your network setup?

could you try power cycling the Doorbell, wait 5 minutes and then restart the reolink integration?

Do you have any special chars in your password?
(I am currently working on a issue where the encoding of special chars in a password can give issues).

[Scoff123]

No, I haven't made any network changes at all. The only thing I've done is update HA core to the latest version. Whether that is a coincidence or not, I'm not sure, but I've never had that error logged before and I've had the doorbell and Reolink integration running for several months now. There are no special characters in the password either.

I've restarted the doorbell, waited for around 10 minutes or so, and then reloaded the Reolink integration, and there were no errors this time. I enabled debug logging prior to rebooting the doorbell as well, but having reloaded the integration twice now, the error haven't returned. I've also tried restarting Home Assistant, then reloading the integration, but still no more errors.

So it looks like there was something that was maybe stuck in a particular state previously, although the doorbell was working correctly in the Reolink app. Very odd - I guess now that I can no longer replicate it I can close this one down!

[starkillerOG]

@Scoff123 yea I guess there was some internal firmware issue in the doorbell causing the RTSP server to not be available.
Glad a power cycle solved the issue.

If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library or purchase Reolink products through this affiliate link.