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
71.14k stars 29.82k forks source link

Camera : unavailable stream on one of two Netatmo Presence cameras #124627

Open mguyard opened 2 weeks ago

mguyard commented 2 weeks ago

The problem

I've 3 cameras (2 Netatmo Presence and 1 Netatmo Welcome) connected with my own client ID. All stream works except one Presence (camera_terrasse - 70:ee:50:85:42:78) I've tested to call Netatmo API to retrieve id in vpn_url and access to http:////live/files/high/index.m3u8 with success. So stream is able to be retrieve from HA and working from Netatmo App

What version of Home Assistant Core has the issue?

core-2024.8.3

What was the last working version of Home Assistant Core?

core-2024.7.1

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

netatmo

Link to integration documentation on our website

https://next.home-assistant.io/integrations/netatmo

Diagnostics information

config_entry-netatmo-01J672ABTXBJ4685HS5RNK2G4V.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-08-26 12:11:44.015 ERROR (MainThread) [homeassistant.components.camera] Timeout getting stream source

Only have this error in logs. But not sure if it's relevant to this camera



### Additional information

Tried to delete, recreate device => Without success
Tried to delete all configuration and switch to Nabucasa Auth link => Without success
Tried to delete all configuration and come back to my ClientID auth => Without success
home-assistant[bot] commented 2 weeks ago

Hey there @cgtobi, mind taking a look at this issue as it has been labeled with an integration (netatmo) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `netatmo` 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 netatmo` 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)


netatmo documentation netatmo source (message by IssueLinks)

subbiesub commented 1 week ago

I have the same problem

Killator commented 1 week ago

Hi, +1

I have 5 smarts cameras: 3 OK / 2 KO... And I can reach all m3u8 streams without issue.

This may be a clue, but the 2 KO cameras have a space in their Netatmo name / an underscore in their HA IDentity... Portail > camera.portail > OK Bureau > camera.bureau > OK Garage > camera.garage > OK Parking AV > camera.parking_AR > KO Parking AR > camera.parking_AV > KO

Capture d’écran 2024-09-05 à 00 49 06
mguyard commented 1 week ago

For me, camera came back without actions.

I don't know if Netatmo rate limit api request based on user-agent like to have done by blocking all Synology NAS to API as they have find that to many request are coming from Synology NAS 🥲

For me it will be my last issue, Synology blocking was the last example of bad camera management by Netatmo with only cloud solution (where they are blocking what they want without notice someone), next week all my Netatmo cam will be replaced with real RTSP cam