Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reolink Duo Floodlight - snapshot error #127117

Open
domosgabor opened this issue Sep 30, 2024 · 11 comments
Open

Reolink Duo Floodlight - snapshot error #127117

domosgabor opened this issue Sep 30, 2024 · 11 comments
Assignees

Comments

@domosgabor
Copy link

The problem

Hi,

I bought a new Reolink Duo Floodlight POE camera connected to my NVR as my other Reolink cameras. Everything is working fine except that I'm not able to take a snapshot from this camera. Other cameras are working fine.
What is strange that the stream of the Duo camera is ok, although it takes some time to load. I use RTSP protokoll, tryed RTMP but the situation is the same.
In the official Reolink apps (desktop/mobile) the streams are ok.
Additional info: the Duo camera is protected by a password, but I assume that still it is connected to the NVR and the password is known by the NVR it should not be a problem.

Here is the error message I got when I try to take a shanpshot (with camera.snapshot service):
Expected type 'image/jpeg' but received 'text/html', response: [ { "cmd" : "Snap", "code" : 1, "error" : { "detail" : "rcv failed", "rspCode" : -17 } } ]

Thanks,
Regads,
Gábor

What version of Home Assistant Core has the issue?

core-2024.9.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

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?

Expected type 'image/jpeg' but received 'text/html', response: [ { "cmd" : "Snap", "code" : 1, "error" : { "detail" : "rcv failed", "rspCode" : -17 } } ]

Additional information

No response

@home-assistant
Copy link

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
Copy link
Contributor

@domosgabor are you using the fluent or clear camera stream entity to request the snapshot?
Could you try both and tell me for each one if it is working or not?

Could you also provide the diagnostic info: https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics

And start debug logging, request a snapshot (that fails) and then stop the debug logging and post the resulting log.txt file here:
https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

@domosgabor
Copy link
Author

@domosgabor are you using the fluent or clear camera stream entity to request the snapshot? Could you try both and tell me for each one if it is working or not?

Could you also provide the diagnostic info: https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics

And start debug logging, request a snapshot (that fails) and then stop the debug logging and post the resulting log.txt file here: https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

I think I'm using the fluent stream, the clear seems to be disabled.
Here are the requested files:
config_entry-reolink-01J8Z5B8MEZM6R7DK4FYZSD36M.json
home-assistant_reolink_2024-10-02T07-59-26.679Z.log

@starkillerOG
Copy link
Contributor

@domosgabor I looked at the diagnostics, but everything seems normal and both the NVR and DUO cam are updated to the latest firmware.

I indeed see the snapshot command is beeing send correctly but it does not receive the correct response.
It might be the width and height parameters in the snapshot command, due to the low res fluent stream.

Could you enable the clear stream and then try to make a snapshot using the clear stream, while making another debug log?

@domosgabor
Copy link
Author

Sure, here you are. The error message is the same, no snapshot was taken.

home-assistant_reolink_2024-10-02T08-27-35.759Z.log

@starkillerOG
Copy link
Contributor

I see, it is indeed also returning an error when using the clear stream.

Unfortunately this will require some more advanced debuging please do the following:

In HomeAssistant go to Settings->Devices & Services -> click the "X Devices" under the reolink integration -> Duo Floodlight -> press the "Visit" button under the Device Info box.

This will take you to the web-client of the NVR, if needed accept the SSL certification warning, then login using your username and password of the NVR.

On this web-page go to the DUO Floodlight and try taking a snapshot there by pressing the camera icon.
Let me know if you are able to make a snapshot or not.

@domosgabor
Copy link
Author

Strange, I'm not able to take a snapshot from the web UI. This is the error message: Picture capture failed!
I tried it in the mobile app and int the windows desktop client as well, both of them work fine.

@starkillerOG
Copy link
Contributor

That was what I was expecting, this proves there is a issue in the firmware, not in the Reolink HomeAssistant code.
The mobile app and desktop client use diffrent protocols.

Unfortunately there is nothing I can do about this since the issue is in the firmware.

Please contact Reolink support and explain the issue, also clearly state the snapshots are also not working in the web-client, with the steps to reproduce. Then ask for them to fix this in the firmware.

I will also pass this allong to the Reolink firmware engineers.

@MiAutomations
Copy link

Hello and sorry about this mentioned on the post

@starkillerOG regarding the POE Floodlight can you please confirm me that this device is supported on this integration?

I try to check on the oficial page https://www.home-assistant.io/integrations/reolink/

But I don't see any reference to the standalone POE or wi-fi version supported by the integration

Thank you

@starkillerOG
Copy link
Contributor

@MiAutomations the standalone Floodlight is NOT supported.
Only the onces combined with a camera.

Maybe I will add support in the future, but because it is lacking the HTTP API and I do not have a test model at the moment, it could take quite long before I start implementing this.

@MiAutomations
Copy link

@MiAutomations the standalone Floodlight is NOT supported. Only the onces combined with a camera.

Maybe I will add support in the future, but because it is lacking the HTTP API and I do not have a test model at the moment, it could take quite long before I start implementing this.

Ok thank you for the reply

I have the POE version integrated into Home Assistant, but I need to use the Neolink Docker container and the MQTT in order to control the floodlight and this doesn't make me sense once is a very complex way to control this device...

Please let me know if you need any further information about the floodlight POE, I can try help with some information

Hope in the future we can use this integration to control the standalone floodlight POE & Wifi Versions

Best regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants