Netatmo webhooks and lights unavailable.

djfanatix commented 7 months ago

The problem

Since the update to 2024.5.x Netatmo webhooks and lights don't work anymore. (they keep marked as offline) They have been working fine for long time.

What version of Home Assistant Core has the issue?

core-2024.5.1

What was the last working version of Home Assistant Core?

core-2024.4.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Netatmo

Link to integration documentation on our website

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

Diagnostics information

home-assistant_netatmo_2024-05-04T07-12-34.322Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-05-04 09:11:57.403 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'\x16\x03\x03'
      ^

Additional information

I did try:

reboot HA and OS
delete and reinstall netatmo integration
Power off/on netatmo devices
delete and add webhook again

home-assistant[bot] commented 7 months 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)}}

cgtobi commented 7 months ago

There are too many errors in that log to make reliable sense of it, especially since many com from custom components. I doubt that the excerpt is related to the Netatmo webhook.

djfanatix commented 7 months ago

Sorry, I put the wrong log, I edited a log and I have replaced it

propi62 commented 7 months ago

Same problem

Alomon31 commented 7 months ago

Same problem here. Reported on HA forum by other users as well: https://community.home-assistant.io/t/how-to-setup-netatmo-integration-using-webhooks-to-speed-up-device-status-update-response-times/385898/15 and https://community.home-assistant.io/t/netatmo-camera-light-issue-since-2024-05/724560/3

nrenou-git commented 7 months ago

problem seems to be on netatmo side. Dev portal is not woking for more than a week for me. dev Apps stays "desactivated" https://helpcenter.netatmo.com/hc/fr/community/posts/18630944611730-Dev-portal-issues

Alomon31 commented 6 months ago

True. Does anyone know a solution to continue using Netatmo integration fully on Home Assistant? Thanks

djfanatix commented 6 months ago

I think once you have the key, you can send local commands to the ip address of your camera.

crazykiwi2003 commented 6 months ago

Same problem here - lights unavailable... :-(

nrenou-git commented 6 months ago

netatmo dev website is working again, but i m still not getting any data from the webhooks lights entities unavailable from presences cameras and no data from the welcome camera ( tags detectors etc ... )

log info : service call : unregister webhook 2024-05-15 09:37:59.994 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 71 2024-05-15 09:38:06.168 DEBUG (MainThread) [homeassistant.components.netatmo] Unregister Netatmo webhook (d0...) 2024-05-15 09:38:06.168 INFO (MainThread) [homeassistant.components.netatmo.data_handler] Netatmo webhook unregistered 2024-05-15 09:38:06.291 DEBUG (MainThread) [pyatmo.auth] dropwebhook: <ClientResponse(https://api.netatmo.com/api/dropwebhook) [200 OK]> <CIMultiDictProxy('Server': 'nginx', 'Date': 'Wed, 15 May 2024 07:38:06 GMT', 'Content-Type': 'application/json; charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache, must-revalidate', 'Expires': '0', 'X-XSS-Protection': '1; mode=block', 'Access-Control-Allow-Origin': '*', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Powered-By': 'Netatmo', 'Content-Encoding': 'gzip')> 2024-05-15 09:39:01.218 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 71 2024-05-15 09:40:00.288 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 74 2024-05-15 09:40:25.342 DEBUG (MainThread) [homeassistant.components.netatmo] Unregister Netatmo webhook (d0...) 2024-05-15 09:40:25.342 INFO (MainThread) [homeassistant.components.netatmo.data_handler] Netatmo webhook unregistered 2024-05-15 09:40:25.443 DEBUG (MainThread) [pyatmo.auth] The Netatmo API returned b'{"error":{"code":7,"message":"Nothing to drop"}}' (406) 2024-05-15 09:40:25.443 DEBUG (MainThread) [homeassistant.components.netatmo] No webhook to be dropped for d0...

service call : register webhook 2024-05-15 09:42:01.825 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 72 2024-05-15 09:42:02.331 DEBUG (MainThread) [pyatmo.auth] addwebhook: <ClientResponse(https://api.netatmo.com/api/addwebhook) [200 OK]> <CIMultiDictProxy('Server': 'nginx', 'Date': 'Wed, 15 May 2024 07:42:02 GMT', 'Content-Type': 'application/json; charset=utf-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache, must-revalidate', 'Expires': '0', 'X-XSS-Protection': '1; mode=block', 'Access-Control-Allow-Origin': '*', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains', 'X-Powered-By': 'Netatmo', 'Content-Encoding': 'gzip')> 2024-05-15 09:42:02.332 INFO (MainThread) [homeassistant.components.netatmo] Register Netatmo webhook: https://hooks.nabu.casa/gAAA...

Alomon31 commented 6 months ago

I've got webhooks working here again, did you try to regenerate your client id+secret? Then delete your integration and your credential information in HA, and set it up again. But my lights are still unavailable after multiple reboots and hours waiting... Any help?

nrenou-git commented 6 months ago

Yes i did all this, still the same, no data from netatmo servers.

RealGandy commented 6 months ago

Same issue here.

Cameras and webhooks are back but light is still showing as unavailable.

As the integration between HA and Netatmo is owned by HA, can someone do some investigations into what request is made and what response is expected for the light to be active again?

Or share info with consumers so we can approach Netatmo directly with evidence of what is going wrong.

Cheers

Alomon31 commented 6 months ago

According to Netatmo dev team (https://helpcenter.netatmo.com/hc/fr/community/posts/18630944611730/comments/18981824506258), the issue is now on HA side. @cgtobi , would you mind having a look at it? Thank you very much.

RealGandy commented 6 months ago

I was going to post this to help wth working out what the problem was, but having just run through this sequence, the light is now no longer showing as unavailable... and seems to be working as expected for me.

======================================================= Here are some entries in log with netatmo in debug mode:

I restarted the integration - and you can see a successful webhook activation. I went outside and the camera spotted me.

followed by me turning the light on, off and back to auto via the netatmo app, you can see incoming webhooks from netatmo showing those activities.

nrenou-git commented 6 months ago

I was finally able to get webhooks working again. The problem came from my configuration but it was not obvious, because I had to configure the client ID and secret in a homeassistant menu that I had never had to use. Previously my netatmo configuration was declared in configuration.yaml then as home assistant was updated the installer asked me to remove the identification information from configuration.yaml. I never had to add my credentials in the new "application credentials" menu. On the other hand, I don't understand that when registering the webhook via the netatmo.register_webhook service I didn't get an error message in the log? this would have allowed me to understand that something was missing in my configuration. The only message I got was "<ClientResponse(https://api.netatmo.com/api/addwebhook) [200 OK]>"

djfanatix commented 6 months ago

Indeed many thanks. I assume the problem is for users who don't use the Nabu Casa cloudservice. Steps to make it working:

add app credentials (integrations page)
delete Netatmo integration
add Netatmo again, don't choose 'home assistant cloud', but your own credentials
following the links

Princeless74 commented 5 months ago

Hello, It works and the light works great, but no more events are triggered when someone or a car is detected.

If you run in debug mode, the webhook seems to work since the event detected is received on the log, but it doesn't trigger anything in my automations (that were working before and also one more I created just for testing purpose)

oywino commented 3 months ago

My attempt to run the service Netamo:Register webhook only results in this error message:

Failed to call service netatmo.register_webhook. Unknown error

I see the following on the log:

homeass-homeass-1  | 2024-08-30 21:05:15.417 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1: Handler is already defined!
homeass-homeass-1  | Traceback (most recent call last):
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 525, in _async_step
homeass-homeass-1  |     await getattr(self, handler)()
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 764, in _async_call_service_step
homeass-homeass-1  |     response_data = await self._async_run_long_action(
homeass-homeass-1  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 727, in _async_run_long_action
homeass-homeass-1  |     return await long_task
homeass-homeass-1  |            ^^^^^^^^^^^^^^^
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/core.py", line 2763, in async_call
homeass-homeass-1  |     response_data = await coro
homeass-homeass-1  |                     ^^^^^^^^^^
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/core.py", line 2806, in _execute_service
homeass-homeass-1  |     return await target(service_call)
homeass-homeass-1  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/components/netatmo/__init__.py", line 157, in register_webhook
homeass-homeass-1  |     webhook_register(
homeass-homeass-1  |   File "/usr/src/homeassistant/homeassistant/components/webhook/__init__.py", line 54, in async_register
homeass-homeass-1  |     raise ValueError("Handler is already defined!")
homeass-homeass-1  | ValueError: Handler is already defined!

The Netatmo Integration as such works and I have all entities available. I have established correct Application credentials and re-installed the integration, but to no avail; Webhooks persistently refuse to work. I run HA Core Docker 2024.8.3

radokristof commented 2 months ago

I also have some problems with custom webhook and the Presence Light switch is unavailable.

I receive this in the log:

2024-09-09 22:02:47.924 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - ("400 - Bad request - Invalid url parameter (21) when accessing 'https://api.netatmo.com/api/addwebhook'",)

The home assistant instance is reachable publicly through a web proxy (port 443)

Princeless74 commented 2 months ago

@cgtobi Since my last message, I still have issues with triggering events. I tried to create a new App on dev.netatmo, and also deleted my cameras and recreated them on a new email account. Still the same : Webhooks are ok, handling of light is working, but no event like human detected or car detected are triggered in HA.

From my logs, I could see the event infos received, but it seems they are received with wrong user_id / snapshot_id / home_id. Is it maybe due that at a point (with my old account, not wit hthe new one) I clicked on reset keys and generate token ?

2024-08-07 15:05:49.561 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 179 2024-08-07 15:06:32.153 DEBUG (MainThread) [homeassistant.components.netatmo.webhook] Got webhook data: { 'user_id': '63bxxxxxxx', 'snapshot_id': '66b3xxxxxxx', 'snapshot_key': '39d8daaxxxxxxx', 'snapshot_url': 'xxxxxxx', 'vignette_id': '66b3xxxxxxx', 'vignette_key': 'b19a697xxxxxxx', 'vignette_url': 'xxxxxxx', 'event_type': 'human', 'camera_id': '70:ee:50:30:15:ac', 'device_id': '70:ee:50:30:15:ac', 'home_id': '63d8xxxxxxx', 'home_name': 'Hery', 'event_id': '66b3xxxxxxx', 'subevent_id': '65eaexxxxxxx', 'message': 'Personne détectée', 'push_type': 'NOC-human' } 2024-08-07 15:06:32.154 DEBUG (MainThread) [homeassistant.components.netatmo.webhook] human: {'user_id': '63bxxxxxxx', 'snapshot_id': '66bxxxxxxx', 'snapshot_key': '39d8daa24xxxxxxx', 'snapshot_url': xxxxxxx', 'vignette_id': '66b3xxxxxxx', 'vignette_key': 'b19axxxxxxx', 'vignette_url': 'xxxxxxx', 'event_type': 'human', 'camera_id': '70:xxxxxxx', 'device_id': '70:xxxxxxx', 'home_id': '63dxxxxxxx', 'home_name': 'Hery', 'event_id': '66b3xxxxxxx', 'subevent_id': '65eaexxxxxxx', 'message': 'Personne détectée', 'push_type': 'NOC-human'}

2024-08-07 15:06:50.131 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 164

Thanks for your help :)

oywino commented 2 months ago

What do you mean by "Webhooks are ok" ? Can you listen for netatmo_event in the developer section and actually se something there?

Princeless74 commented 2 months ago

Hi @oywino, By "webhooks are ok" I mean it is correctly setup as described on the guide. As the light works, it means that the webhook correctly communicate. Moreover, we can see in HA log that it receive the events, so webhook communication between netatmo and HA is ok.

If i suscribe the events, it correctly receive the detection event and I can see it correctly.

My hint is that the netatmo send data with wrong ID somehow...

oywino commented 2 months ago

I still don't understand. If webhook is correctly set up and you can see in the HA log that events are received, and you can subscribe to see Netatmo events, then what more do you need? As you describe, everything seems to work perfectly for you.

Princeless74 commented 2 months ago

Hi, I know, but if I create on both cameras an automation "when a person is detected", thing is never triggered. It used to work for one year and it stopped working from may when netatmo integration had some issues (and from this date also I reseted the key on dev.netatmo portal).

I am pretty sure that it doesn't trigger the automation because the event received contains wrong IDs and then, because of this, it doesn't trigger the automation.

oywino commented 2 months ago

If your Netatmo camera's are integrated using the Netatmo Integration, then i doubt that you have presence detection sensor. As far as I know, this integration does not support such entities. But if you have your cameras integrated using the HomeKit Integration, then you will have such sensors. However, under normal circumstances you cannot have the same camera integrated in two integrations simultaneously (but it has been known to happen). If you want to use event detection to trigger based on the Netatmo Integration via netatmo_event then you must use the event platform as your trigger. Here's an automation that just reads a text out loud on a mobile phone speaker whenever a Netatmo event happens (any Netatmo event):

alias: "Test: Netatmo Event"
description: ""
trigger:
  - platform: event
    event_type: netatmo_event
condition: []
action:
  - metadata: {}
    data:
      message: TTS
      data:
        tts_text: Netamo event detected!
        media_stream: alarm_stream_max
        ttl: 0
        priority: high
    action: notify.mobile_app_sm_g996b
mode: single

Just replace the action entity with the correct one for your mobile phone (assuming you have integrated your mobile phone with Home Assistant).

If you had motion detection working earlier, it must have been because your HomeKit integration was live and working with your Netatmo cameras. That I think was removed (bug-fixed) during one of the more resent updates (so you can no longer have a Netatmo camera device integrated twice).

Princeless74 commented 2 months ago

Yes, my Netatmo cameras are integrated using Netatmo integration. If you create an automation, you can trigger your automation based on the camera detection car/human/animal/other. It used to work fine before for months :)

Actually, my issue is that when netatmo_event, theses automations are not trigered anymore.

I will try to create manually something like you mentioned, but in parallel, I think there is a bug somethere ;)

Is there a way to compare reveiced IDs with my cameras IDs ?

oywino commented 2 months ago

I see what you do. You could (should) use entity instead of device in all your automations because devices use id as a reference while entities use names. If you delete and reinstall a device, it will get a new device_id and all your automations has to be rewritten. While an entity maintains its name. Try this instead:

trigger:
  - platform: state
    entity_id:
      - camera.camera01
    attribute: motion_detection
    to: "on"
condition: []
action: []
mode: single

Princeless74 commented 2 months ago

I would agree with you, but using entity means, only trigger when a motion is detected : I need to distinguish car/human vs animal/other and that's why I need to use device.

The idea behind is to send me alert is my home alarm is ON and a car/human is detected, without beoing annoyed by animals like cats ;)

oywino commented 2 months ago

Well, that at least re-create your automation so that you get the correct ID updated. Also, carefully examine the trace before you conclude that it doesn't trigger. Don't trust the last_triggered variable.

Princeless74 commented 2 months ago

OK, I found a trick to make it working, but I can confirm there is a but and the webhook still send data with an old ID...

here is my trick on my automation :

¨alias: alarme ON detection humain après 5min description: "" trigger:

platform: event event_type: netatmo_event event_data: type: human
platform: event event_type: netatmo_event event_data: type: vehicle condition:
condition: template value_template: "{{ trigger.event.data['data']['camera_id'] == '70:xx:XX:xx:XX:xx' }}"

then it works fine and it perfectly filter event type on human or vehicle and it also filter it per camera_id to get a different notification message/photos

Princeless74 commented 2 months ago

I did a nice trick to make it working as I want, but I can confirm that webhook of dev.netatmo send messages using some old IDs and this is why it doesn't work. I think deleting/re generate/disconnect/reconnect webhook stuff at a moment created this mess.

Here is my trick to only get human detection from only one camera 👍

trigger:

platform: event event_type: netatmo_event event_data: type: human condition:
condition: template value_template: "{{ trigger.event.data['data']['camera_id'] == '00:xx:00:00:xx:00' }}"

oywino commented 2 months ago

Happy to hear that it works again for you 👍 My problem is that I no longer receive any Netatmo events. If I try to listen to netatmo_event it is now totally silent. It used to work just fine. Then it worked sometimes and was silent for a long time, then worked sometimes again, but less and less. Now it's been completely silent for the past 2 months. I have checked the dev console and and everything looks ok. No banning. I have checked the application credentials which are ok. The Android security App gets all events all the time, but Home Assistent no longer gets anything. Very frustrating.

Princeless74 commented 2 months ago

Have you checked on dev.netatmo if your webhooks are with « Green check box » ?Obviously the issue is on your webhook configuration. You should recheck the installation guide. Do you use nabucasa ? If not you need to open your ports and configure them :)Le 13 sept. 2024 à 18:39, oywino @.***> a écrit : Happy to hear that it works again for you 👍 My problem is that I no longer receive any Netatmo events. If I try to listen to netatmo_event it is now totally silent. It used to work just fine. Then it worked sometimes and was silent for a long time, then worked sometimes again, but less and less. Now it's been completely silent for the past 2 months. I have checked the dev console and and everything looks ok. No banning. I have checked the application credentials which are ok. The Android security App gets all events all the time, but Home Assistent no longer gets anything. Very frustrating.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

RealGandy commented 2 months ago

@oywino

Strange as it may sound but I've found turning the light on, off and back to auto for the outside camera using the netatmo security app allows HA to register for webhooks (and get the light entity back).

Try that, followed by running the 'unregister' and 'register' webhooks service/actions.

oywino commented 2 months ago

Well, Thanks for your suggestions, but my event issue is primarily with the indoor cameras (which have no flood light switch). My outdoor camera always had the flood light switch, and it works (always). Still, I did the unregister/register procedure, with no errors reported.

oywino commented 2 months ago

Have you checked on dev.netatmo if your webhooks are with « Green check box » ? Yes, that part is OK. Always has been. I do not use NabuCasa and I do use NabuCasa, meaning - I have two Home Assistant instances installed (in two different countries). One use NabuCase. The other doesn't and that one is available from the internet through a reverse proxy. Netatmo webhooks used to work with that one for years - until quite recently, it stopped. The other instance (that use NabuCasa) works sometimes, but mostly not. It appears very intermittent.

edenis875 commented 2 months ago

I also have some problems with custom webhook and the Presence Light switch is unavailable.

I receive this in the log:
2024-09-09 22:02:47.924 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - ("400 - Bad request - Invalid url parameter (21) when accessing 'https://api.netatmo.com/api/addwebhook'",)
The home assistant instance is reachable publicly through a web proxy (port 443)

@radokristof, I get similar issue as you: is it still happening on your side or were you able to fix it? If so, how? If not, FYI, I raised https://github.com/home-assistant/core/issues/125833 few days ago.

radokristof commented 2 months ago

Hi @edenis875 no, unfortunately not, I was unable to fix this yet. Wonder why others are able to at least receive something on the webhooks. I tried recreating the app on netatmo site, but same result.

oywino commented 2 months ago

I notice that I do get webhook event from Netatmo when any of my cameras are disconnected from the network. So obviously, webhooks event does work. But I never get any webhook events as a result of any other situations like movement detection, flood lights etc. which I used to get earlier. Perhaps Netatmo is no longer sending such events? Perhaps the "burden" of sending webhook events for thousands of cameras around the world became too much for them to handle, and they cut back on all of it (without telling us?) and are now only sending webhook events on critical events? I'm just guessing.....

gibbo520 commented 2 months ago

Hello everyone, I have a MyHomeServer 1 that I’ve configured correctly, and it’s working seamlessly with the Control app. I’ve developed APIs to read and write, and I’m able to send commands and receive the status of lights and thermostats without any issues. I’ve activated a webhook and registered it successfully, as evidenced by the following event I receive:

INFO:__main__:Webhook received: {'user_id': '**********', 'user': {'id': '**********', 'email': '**********@gmail.com'}, 'push_type': 'webhook_activation'}
INFO:__main__:Received PushType ********** with status webhook_activation

However, when I turn lights on and off, these events do not reach the webhook. I’m not receiving any notifications corresponding to the light state changes.

I already posted this issue on the Netatmo forum, but unfortunately, I haven’t received any responses yet. I’m hoping someone here might have experienced a similar issue or could provide some insight into why the webhook isn’t receiving these specific events. Is there an additional configuration step required to enable light on/off events to be sent via webhook?

Any assistance would be greatly appreciated. Thank you!

oywino commented 2 months ago

This Netatmo webhook thing is turning me crazy! I have made an small automation that sends a spoken message to my smartphone if any Netatmo event is detected by HA.

alias: Test - Netatmo Event
description: ""
trigger:
  - platform: event
    event_type: netatmo_event
condition: []
action:
  - metadata: {}
    data:
      message: TTS
      data:
        tts_text: Netamo event detected!
        media_stream: alarm_stream_max
        ttl: 0
        priority: high
    action: notify.mobile_app_sm_g996b
mode: single

As I've reported earlier in this thread, it does work occasionally - when a camera for some unknown reason is disconnected from the network, which does happen now and then. But it was not consistent. One night I woke up by several consecutive messages being sent to my phone. I checked the camera, and certainly, it had lost connection. Trying to capture such messages to see every detail in the event stream, is difficult because the "Listen to Events" feature under the development tab in HA times out after a while. There doesn't seem to be a way to keep it running (listening) forever (until switched off). After that nightly encounter, it's been completely silent - even though I know for a fact that the camera has been offline several times. So, as I said - it's not consistant. Then, today - suddenly - it began frenetically to send event messages again, one after the other. I noticed that every time my wife walked in front of the camera, it generated a webhook event. I jumped on the keyboard and managed to kick start the listener and capture the last event stream before it again went dead silent:

Event 0 fired 09:16:

event_type: netatmo_event
data:
  type: person
  data:
    user_id: 564de4f46xxxxx461b21eba
    persons:
      - id: cbf2e42c-9b57-xxxx-xxxx-c329d76f2309
        face_id: 64fb5c41xxxxxx111087149
        face_key: 377d748c13dc5cxxxxxxxx98710521ab742526e3b10a6dacdc5fc92fbb641ae
        is_known: true
        face_url: >-
          https://netatmocameraimage.blob.core.windows.net/production/64fb5c411888be01110871493xxxxxxxxc5c83923d85c98710521ab742526e3b10a6dacdc5fc92fbb641ae?sv=2017-11-09&sr=b&se=2024-09-29T07:21:42Z&sp=r&spr=https&sig=4t3KiR9qNnukI1mVUxxxxxxxw4%2F9RL6yT87EkNe55c%3D
    snapshot_id: 66f8fedaxxxxxx3020fc709
    snapshot_key: bee1f4aff258368f247b06xxxxxxxxxx229ec38803606269fce7ee0057cbea8d
    snapshot_url: >-
      https://netatmocameraimage.blob.core.windows.net/production/66f8feda3655c083020fxxxxxxxxx4aff258368f247b06204068cdea229ec38803606269fce7ee0057cbea8d?sv=2017-11-09&sr=b&se=2024-09-29T07:21:42Z&sp=r&spr=https&sig=RaAa0Qppo5b9xxxxxxxxqQ5a0iPkl54gaGruwKMXX0%3D
    event_type: person
    camera_id: 70:xx:50:xx:5c:d6
    device_id: 70:xx:50:xx:5c:d6
    home_id: 64fb572xxxxx1467d0aaeaf
    home_name: EMA
    event_id: 66f8fedaxxxxxx020fc708
    message: Ewa seen by Camera02
    push_type: NACamera-person
    id: cbf2e42c-9b57-xxxx-xxxx-c329d76f2309
    name: Ewa
    is_known: true
    face_url: >-
      https://netatmocameraimage.blob.core.windows.net/production/64fb5c411888be01110xxxxxxxxxc13dc5c83923d85c98710521ab742526e3b10a6dacdc5fc92fbb641ae?sv=2017-11-09&sr=b&se=2024-09-29T07:21:42Z&sp=r&spr=https&sig=4t3KiR9qNnukI1mVxxxxxxxxx4%2F9RL6yT87EkNe55c%3D
  device_id: null
origin: LOCAL
time_fired: "2024-09-29T07:16:50.667348+00:00"
context:
  id: 01J8YA79BBSxxxxxxQSYXACJ
  parent_id: null
  user_id: null

(I deliberately x'ed out part of all key-data to make the message confidential) The above proves beyond doubt that my webhook communication setup works. So my main "accusation" is still that there is something fishy going on at the Netatmo dev side where their API endpoints are located. Webhook events are simply not generated as they should - only randomly and occasionally. But when they do, they are correct. Just for the record, I regularly check the Netatmo dev site for banned IP, and it has never been the case for me. So that's not where the problem lies. Also, running the service 'registering and unregistering' Netatmo webhooks works without any error messages, but doesn't make any difference as far as this problem goes.

Also, as @Princeless74 commented above, building an automation like this;

alias: Test - Netatmo movement
description: ""
trigger:
  - platform: device
    device_id: fc5c9e6ffc4xxxxxxx950bf5da612
    domain: netatmo
    entity_id: 4a09b8d5c4xxxxxxecc489151502fe
    type: movement
condition: []
action:
  - metadata: {}
    data:
      message: TTS
      data:
        tts_text: Netamo detected movement!
        media_stream: alarm_stream_max
        ttl: 0
        priority: high
    action: notify.mobile_app_sm_g996b
mode: single

It doesn't work! Never triggered.

andys003 commented 1 month ago

Den ganzen Zirkus mehrmals durch, Licht taucht einfach nicht auf. Für die aufgewendete Zeit (in Geld) könnte ich mir gescheitere Kameras kaufen, die funktionieren. Das Problem haben wohl einige siehe Video https://www.youtube.com/watch?v=wU0VNMwUW5M&t=19s Min 2:23

home-assistant / core