Reolink camera no longer working within HA

ginfts commented 1 month ago

The problem

Probably since updating several RLC-511 cameras to the latest FW v3.0.0.2356_23062003 a few weeks ago, they no longer "work" within HA, but they do within the macOS Reolink app. I have tried removing them and re-integrating them to HA, but that never works.

What version of Home Assistant Core has the issue?

2024.8.0

What was the last working version of Home Assistant Core?

No response

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

home-assistant_reolink_2024-08-12T14-52-49.072Z.log config_entry-reolink-aa58d9602d888420e9e4d2ed27cb4e5f.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

When I try to connect an RLC-511 camera, using the correct admin and correct password and correct LAN IP, and trying 80, 443 and 8123 for the port number and ticking or unticking the Enable HTTPS box, it always fails to connect.

home-assistant[bot] commented 1 month 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!

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 commented 1 month ago

@ginfts did you check the HTTPS and RTMP ports are still open? You can check in the mobile app or in the PC client.

What is the exact error you get when trying to connect the camera?

starkillerOG commented 1 month ago

@alexmoney could you please share the error in the log when you see "Unknown error occurred" there will be a much more detailed trackback of the error in the logs in case of a Unknown error.

alexmoney commented 1 month ago

@starkillerOG apologies my issue was completely unrelated so I have deleted my comment.

flinthamm commented 4 weeks ago

I've just had a similar problem, not sure if it's related but the latest integration doesn't allow the # (hash) symbol to be used in passwords but the reolink firmware does. Consequently the integration was asking for re-authentication and when this was done it failed. Once the password was changed to a different special character supported by both integration and firmware the authentication completed and everything started working again.

Hope this might help.

starkillerOG commented 4 weeks ago

@flinthamm your issue is a duplicate of https://github.com/home-assistant/home-assistant.io/issues/34199 and https://github.com/home-assistant/core/issues/123302 and a few others

See my explination here: https://github.com/home-assistant/core/issues/123302#issuecomment-2274337355

Sorry for the inconveniance of having to make a new user/change the password.

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.

blacksirius435 commented 3 weeks ago

Yeah I got also an authentication error due to not supported special characters in my password. It worked until a few days and then just stopped. My Passwort includes spaces but the integration says it's not supported what is wrong. Reolink supports that and I'm sure it worked also with the integration before due to the fact that I used it since half of a year without an issue. So this seems to be a mistake in a new update or so.

starkillerOG commented 3 weeks ago

@blacksirius435 see https://github.com/home-assistant/core/issues/123302#issuecomment-2274337355

Space is also a special char that is not allowed anymore.

AaronIsFab commented 2 weeks ago

@ginfts did you check the HTTPS and RTMP ports are still open? You can check in the mobile app or in the PC client.

What is the exact error you get when trying to connect the camera?

It's 99% likely to be this, our 410W recently went to: v3.0.0.2356_23062002 and following that the default for all the network ports on the camera is disabled even when other user settings are kept so it looks like its the HA side that "breaks".

Re-enabling the necessary ones (Settings > Network > Advanced > Port Settings (PC)), rebooting the camera then waiting 15mins before reloading the device worked for us.

ginfts commented 2 weeks ago

@AaronIsFab Thanks for that; I might have found the problem; if I re-enable any / all of the RTMP / HTTP / HTTPS / RTSP within Network / Advanced / Server Settings within the MacOS Reolink app and then click on SAVE, then go to System / Maintenance / Reboot, when the camera comes back on line none of the RTMP / HTTP etc are enabled - ie the software is not "remembering" the change of setting.

Most strange...

EDITED TO ADD:

If I do the same thing within the Reolink iOS app as soon as I click on Reboot the setting is forgotten (as above). But if I check HTTPS within the iOS app but I DO NOT reboot the camera, I see that the HTTPS also shows as checked within the macOS app AND the camera feed works within HA.

I have not yet tried it but I am 95% sure that as soon as the camera is rebooted / powered off/on it will fall over, but at least this is beginning to narrow down where the fault lies.

xannor commented 1 week ago

@starkillerOG can you contact reolink and confirm it is not firmware issue? I left two camera's with my parents that were updated to the 3.1 firmware (an 810A and a 520A) both now exhibit this error, though they were fine until your recent change in the password requirements (coincidence most likely). In addition, the web interfaces of those cameras refuse to allow login as well, the app is fine. Even resetting the password to as simple as possible is fine in the app, but the web interface refuses the password. Rebooting the cameras did not solve this, did not try a factory reset because they are ok with using the app for now.

Also, both cameras had https turned off and turning https on on one of them produces a bad gateway when trying to connect to https, event after reboot.

I only visit them about once a month so trouble shooting is not viable at this time.

For everyone else with this issue, please confirm if you can log into the web interface.

I am going to see if I can find a prior firmware version and back down to it to see if the problem goes away, but Reolink seems to pull older copies so that may not be possible either.

starkillerOG commented 1 week ago

@xannor the password requirement change is definetely unrelated. So if I understand correctly you can see/load the web-interface but you are unable to actually login becuase it says the password is wrong?

If you cannot login to the web-interface it definelty sounds like a firmware issue or a issue with the password you configured. But if you changed the password to something simple and are 100% sure you are typing it correctly (no capslock etc) then it could be a firmware issue.

see https://github.com/gtalusan/reolink-fw-archive for older firemware versions.

home-assistant / core