This is just an error message, could you please describe what the actual issue is?
Sorry i didn’t mentioned that. It’s the same as described by dietlman in the github issue : no picture of preview in the livestream (grey picture as below). The livestream does’nt work either.
To all who are missing webhooks since 0.105… the new beta has them. Happy testing.
4 Likes
Hi @cgtobi I still can’t get netatmo webhooks working in the latest beta, I’m not seeing any netatmo_human events being registered and am still seeing the ‘Received message for unregistered webhook’ error in the logs
In addition, the service ‘netatmo.set_light’ has disappeared
The event is called netatmo_event. Sorry, I still am working on the documentation.
See here for an example.
Thanks, that makes sense. Doesn’t the “unregistered webhook” error that correlates to movement on the camera suggest that the webhook isn’t registered correctly though?
2020-03-14 14:52:48 WARNING (MainThread) [homeassistant.components.webhook] Received message for unregistered webhook a2361a3ee5aebe33fdff4a16546ae65a35f46e52ba62d57465a9474fa515096f
Also have we lost the ability to control the floodlight on the Presence cameras as the following services have disappeared: netatmo.set_light_off, netatmo.set_light_on and netatmo.set_light_auto
Thanks
Are you a Nabu Casa user? If so, check the webhook in the settings panel. If not, please set logging for the netatmo integration to INFO to see when the webhook is registered. Also double check the dev portal from Netatmo in case the webhook got banned.
Yes, the services were removed since they went against the HA rules. It will come back soon. PR is already in the works: https://github.com/home-assistant/core/pull/32374
1 Like
Thanks @cgtobi I’ve just had another crack at it and the webhook has registered fine and am seeing netatmo_event events being registered which I can use to rebuild my automations. Not sure what the issue was yesterday but at least it’s working now.
Also thanks for your work on the lights, it’s much appreciated 
1 Like
Thanks for the feedback. Just for completeness sake, are you a Nabu Casa user?
No, I don’t use Nabu Casa, just a local install with remote access…Hass.io docker container running on a Ubuntu VM
Ok. Great. Thanks.
i cant get this to work 
camera.disable_motion_detection
Because it is not implemented.
Actually, it is not implemented yet. Progress can be tracked here. So please be patient a little while, this wont happen before 0.108.
Thanks for info, I’ll wait… 
…
@cgtobi I’m having an issue after upgrading from 0.104 to 0.107.1. I used to have everything up and running via the old Netatmo integration with an app created in Netatmo Dev environment.
Setup
- 3x Netatmo Presence cameras
- Nabu Casa
- Removed every reference to ‘netatmo’ from configuration.yaml
What does work
After going through “Integrations”, authentication at Netatmo is successful (when I log into my account I also see it registered under 3rd party apps) and the cameras are visible as entities in Home Assistant with all kind of attributes.
What does not work
- No image, none.
- No webhook events. Though the logs show “Received message for unregistered webhook xyzxyz”
- Entity attributes contain “entity_picture: /api/camera_proxy/camera.netatmo_voortuin?token=xyz”, calling this URL in the browser gives ‘500: Internal Server Error’
- Logs show multiple times “Welcome/Presence VPN URL is None”
I tried numerous combinations, restarts, deactivated the old My app in Netatmo Dev. Nothing.
Help?
1 Like
When you ran the integration dialogue, did you select “configuration.yaml” or “HA Cloud”?
The webhook based event is called “netatmo_event”, just in case you’re listening for another one.
First time configuration.yaml as I still had some configuration in there for netatmo but got a plain-text error that the return url was not correct. Then tried HA Cloud and that didn’t give error. Since then I removed all netatmo items from configuration.yaml and since then I’m not getting the option anymore, it goes straight through the HA Cloud process.
You have to remove the integration, add Netatmo to your configuration.yaml and restart HA. Then you should be able to use that in the integrations dialogue.
Thanks for the advice @cgtobi! No succes, unfortunately. I removed everything and restarted. Added (and then restarted again):
netatmo:
client_id: !secret netatmo_client_id
client_secret: !secret netatmo_client_secret
When adding the integration I’m getting the dialog for configuration.yaml or HA Cloud.
When chosing configuration.yaml option, I get send to Netatmo, authenticate and return at HA with a 500:
https://.ui.nabu.casa/auth/external/callback?state=<long_string>&code=<long_string>
500 Internal Server Error
Server got itself in trouble
The log in HA shows the following:
Log Details (ERROR)
Logger: aiohttp.server
Source: helpers/config_entry_oauth2_flow.py:167
First occurred: 7:35:57 AM (2 occurrences)
Last logged: 7:36:11 AM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 123, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 154, in get
return await super().get(request, flow_id)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 80, in get
result = await self._flow_mgr.async_configure(flow_id)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 130, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 172, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 246, in async_step_creation
token = await self.flow_impl.async_resolve_external_data(self.external_data)
File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 142, in async_resolve_external_data
"redirect_uri": self.redirect_uri,
File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 167, in _token_request
resp.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 946, in raise_for_status
headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 400, message='', url='https://api.netatmo.com/oauth2/token
After this all, the integration is not added.
Then, when retry adding the integration but chosing the Home Assistant Cloud option, it works (Success! Successfully authenticated with Netatmo. Created configuration for Home Assistant Cloud. We found the following devices:) and I see my devices. But no images, and following state:
access_token: <access_token>
model_name: Presence
brand: Netatmo
motion_detection: true
id: <mac_address>
status: on
sd_status: on
alim_status: on
is_local: null
vpn_url: null
friendly_name: Netatmo Voorgevel
entity_picture: /api/camera_proxy/camera.netatmo_voorgevel?token=<access_token>
supported_features: 2
After that, the error “Welcome/Presence VPN URL is None” appears in the logs whenever I try to view the camera.
What I notice, by the way, is that when send to Netatmo for authentication, the ‘scope’ does not include: ‘access_presence’ and ‘access_camera’. Shouldn’t these be in scope? Those were in scope for the previous integration, which worked for me. I’m pretty sure this is causing the issue as I see what that scope authorizes for.