Open mguyard opened 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!
(message by CodeOwnersMention)
netatmo documentation netatmo source (message by IssueLinks)
I have the same problem
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
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
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?
Only have this error in logs. But not sure if it's relevant to this camera