home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.71k stars 30.84k forks source link

Reolink integration no Mainstream in HA #106161

Closed ConvarDeutschland closed 10 months ago

ConvarDeutschland commented 11 months ago

The problem

Hello,

I have 3 reolink cams added to HA, but none of them show me an entity for the main stream only substream is present. I use RTSP . It is also not present as en disabled entity. What I'm doing wrong ?

What version of Home Assistant Core has the issue?

core-2023.12.3

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 11 months 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 11 months ago

Please post the diagnostic information from you Reolink camera: https://www.home-assistant.io/docs/configuration/troubleshooting/#download-diagnostics

Also go to Settings > Devices & Services and select the Reolink integration, select device and go to the camera device, there you should see the sub_stream entity and below that in blue something like "Show x disabeled entities", hit that and then select the "Clear" camera entity. If it is not visible there, please post a screenshot of that page where I can see it is not there.

ConvarDeutschland commented 11 months ago

Hello @starkillerOG

The main stream is not to find there see the attachment picture. only Fluent stream is there, and that the same on all 3 cams Screenshot from 2023-12-21 12-38-30

Diagnostic also attached config_entry-reolink-ae09fd6c1372f3e6b07c0ff85772abd2.json.txt

starkillerOG commented 11 months ago

@ConvarDeutschland that is really strange. Did you try refreshing your browser (F5)? Sometimes entities don't show up due to browser catch.

Do you see any errors in the log regarding the Reolink integration?

ConvarDeutschland commented 11 months ago

Delete cache et refresh did not help in this case

In log the only error I can found is 2023-12-21 09:35:30.429 ERROR (MainThread) [homeassistant.components.reolink.config_flow] Unexpected exception Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/reolink/config_flow.py", line 168, in async_step_user await host.async_init() File "/usr/src/homeassistant/homeassistant/components/reolink/host.py", line 165, in async_init await self.subscribe() File "/usr/src/homeassistant/homeassistant/components/reolink/host.py", line 393, in subscribe self.register_webhook() File "/usr/src/homeassistant/homeassistant/components/reolink/host.py", line 494, in register_webhook webhook.async_register( File "/usr/src/homeassistant/homeassistant/components/webhook/init.py", line 53, in async_register raise ValueError("Handler is already defined!") ValueError: Handler is already defined!

ConvarDeutschland commented 11 months ago

@starkillerOG

I did try to change settings from RTSP to RTMP. In this case the Mainstream is added to the cam config, If I change it back to RTSP then it not available anymore

starkillerOG commented 10 months ago

@ConvarDeutschland that is really strange, could you enable debug logging of the reolink integration https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging then switch from RTMP to RTSP and back (have enough time inbetween so the main stream camera entity is available) then disable debug logging and post the log.txt file here.

ConvarDeutschland commented 10 months ago

@starkillerOG

here is the logfile home-assistant_reolink_2023-12-23T15-12-54.870Z (1).log

starkillerOG commented 10 months ago

@ConvarDeutschland I see a lot of connection errors to the camera at IP 192.168.11.117 and never see a proper response from that IP. Is that camera not connected anymore? I would at least recommand disabeling the integration of that camera if it is not connected anymore.

You might have setup the integration twice, one for the wifi connection and one for the LAN connection to the same camera. That could potentially be causing issues...

ConvarDeutschland commented 10 months ago

@starkillerOG the cam 117 is disababled at the moment but will go online again, but that make no difference also wehen this cam is online there is no difference.

What do you mean with "ou might have setup the integration twice"? each cam is only setup once, do you mean the integration or the cams ? I will test it by deleteeverything and setup it again

ConvarDeutschland commented 10 months ago

@starkillerOG

I have removed all cams, restarted and add only one cam. which is connected over cable. It is still the same RTSP no main stream possible, RRMP both stream possible. Is there a way to remove the reolink integration and reinstall it ?

starkillerOG commented 10 months ago

@ConvarDeutschland I feel pretty stupid and schould have checked this better: In this screenshot the clear view is present: 292193355-5a1bb178-2dac-4659-8563-f551616f3308

Clear is translated to Effacer in French. afbeelding

So simply enable the "Effacer" entity.

I don't speek French, but Google Translate seems to indicate to me "Effacer" me be a bad translation. I would guess that "Clair" or "Claire" would be a better translation.... Are you a native French speaker?

starkillerOG commented 10 months ago

@ConvarDeutschland for your information, the "Fluent" entity has not been translated to French yet: afbeelding

ConvarDeutschland commented 10 months ago

@starkillerOG

your right this was the problem, I have rename it and activated it an d it works perfectly. For me it was a button to delete something that the reason I did not activated it

Thanks for you hepl i will clause the case

Merry Christmas to you

starkillerOG commented 10 months ago

@ConvarDeutschland good to hear it is now working for you!

If you are a native French speaker, could you confirm that "Clair" would be a better translation than "Effacer"? Than I can update the translation.

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.

Merry Christmas to you!

ConvarDeutschland commented 10 months ago

@starkillerOG

"Clair" is a better version as "Effacer". But would it no be better to use "main strean" and "sub stream" like "Flux principal" and "Flux secondaire"

starkillerOG commented 10 months ago

I updated the translations to "Clair".

I decided to step away from main, sub, ext and go to Clear, fluent, balanced instead. So in englisch it will now also be Clear, Fluent and Balanced. This because in the Reolink App/Client it is called Clear/Fluent/Balanced. Main is only referred to in the API but since users are not aware of the API, they will know the streams as Clear, fluent, balanced from the Reolink App/Client/Web interface.