Closed codyc1515 closed 10 months ago
That is an interesting approach. Are you interested in implementing this yourself?
I could but wanted to feel out the idea first to make sure that you and the team would be okay with it. This issue doesn't happen particularly often but when it does it's especially frustrating.
The current solution is not as sophisticated. I'd welcome this implementation.
Astounding. I still have not heard back from Netatmo in some 4 months.
I'm having an issue with one of my two cameras not showing in Home Assistant (no issues in the Security app or the Netatmo website) and, on checking, it's this issue again.
There appears to be some checks for the presence of an 169.254.x.x IP address which should exclude the local_url
from being retunred; however, my instance appears to not be falling back to the VPN. Need to do some sleuthing.
Never heard back from Netatmo until I tried to return my cameras to the retailer then silent again. Proceeded with the refund and no issues since :)
Hi. I did a little probing today to see if it may be possible to add a workaround for the 169.254 IP Address issue referenced in #347. I lodged an issue with them earlier today about this too as I strongly believe this is a Netatmo device firmware to cloud API integration bug. However, I have experienced first hand the delays from Netatmo in the past.
I understand that the process today is now roughly:
My suggestion is instead of 4, let's:
We can now match the mDNS mac_address attribute to the /homestatus MAC address and substitute in the IP address from mDNS over the top of the http://169.254.x.x address. This will preserve the security key in the path of the URL and allow us to continue to connect to the device locally.