Netatmo - Error during webhook registration
The problem
Hello,
My Bubendorff shutters are not visible from HA.
I suspect the following error during HA startup to be the root cause which I'm not able to solve:
Error during webhook registration - ("400 - Bad request - Invalid url parameter (21) when accessing 'https://api.netatmo.com/api/addwebhook'",)
Also, integration diagnostic file shows "webhook_registered false".
Own app has been created on Netatmo developer portal and Netatmo weather station devices are successfully imported which seemingly means that my token is valid. As described in the documentation, I ensured 'redirect URI' and 'webhook URI' parameters were not set.
SSL is enabled on HA side; SSL port is opened on firewall side and forwarded to HA
I tried to
- (temporarily) put my HA in DMZ, to ensure that there was no issue with my firewall
- delete / re-import Netatmo integration
- change external / internal HA URL ... but got no luck to remove above error message and have my shutters imported
Any idea of what is wrong here? Did I misconfigure anything? Is there any other useful information I could provide to help understanding where the issue comes from?
Many thanks,
What version of Home Assistant Core has the issue?
2024.9.1
What was the last working version of Home Assistant Core?
No response
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
config_entry-netatmo-01J7K24YR110VWKJHD5FC417N4.json config_entry-netatmo-01J7K24YR110VWKJHD5FC417N4.json config_entry-netatmo-01J7K24YR110VWKJHD5FC417N4.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
2024-09-12 14:19:36.102 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-12 14:19:36.108 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-12 14:19:36.110 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-12 14:19:53.969 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to load_verify_locations with args (<ssl.SSLContext object at 0xffff79406450>, '/usr/local/lib/python3.12/site-packages/pyoverkiz/overkiz-root-ca-2048.crt', None, None) inside the event loop by integration 'overkiz' at homeassistant/components/overkiz/__init__.py, line 239: return OverkizClient( (offender: /usr/local/lib/python3.12/ssl.py, line 708: context.load_verify_locations(cafile, capath, cadata)), please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+overkiz%22
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#load_verify_locations
Traceback (most recent call last):
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 189, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/setup.py", line 165, in async_setup_component
result = await _async_setup_component(hass, domain, config)
File "/usr/src/homeassistant/homeassistant/setup.py", line 461, in _async_setup_component
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/setup.py", line 463, in <genexpr>
create_eager_task(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45, in create_eager_task
return Task(coro, loop=loop, name=name, eager_start=True)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 752, in async_setup_locked
await self.async_setup(hass, integration=integration)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 604, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/overkiz/__init__.py", line 64, in async_setup_entry
client = create_local_client(
File "/usr/src/homeassistant/homeassistant/components/overkiz/__init__.py", line 239, in create_local_client
return OverkizClient(
2024-09-12 14:20:09.802 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - ("400 - Bad request - Invalid url parameter (21) when accessing 'https://api.netatmo.com/api/addwebhook'",)
2024-09-12 15:00:10.551 ERROR (MainThread) [homeassistant.components.mobile_app.notify] Timeout sending notification to https://mobile-apps.home-assistant.io/api/sendPush/android/v1
2024-09-12 15:36:37.392 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 362, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 563, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadHttpMessage: 400, message:
Pause on PRI/Upgrade:
b''
^
2024-09-12 15:57:20.348 DEBUG (MainThread) [pyatmo.auth] The Netatmo API returned b'{"error":{"code":7,"message":"Nothing to drop"}}' (406)
2024-09-12 15:57:20.349 DEBUG (MainThread) [homeassistant.components.netatmo] No webhook to be dropped
2024-09-12 15:57:20.349 INFO (MainThread) [homeassistant.components.netatmo] Unregister Netatmo webhook
2024-09-12 15:57:20.358 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather removed
2024-09-12 15:57:20.904 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher account added
2024-09-12 15:57:21.060 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather added
2024-09-12 15:57:21.161 DEBUG (MainThread) [pyatmo.helpers] Server response (tag: devices): {'body': {'devices': [], 'user': {'mail': '[email protected]', 'administrative': {'lang': 'fr', 'reg_locale': 'fr-FR', 'country': 'FR', 'unit': 0, 'windunit': 0, 'pressureunit': 0, 'feel_like_algo': 0}}}, 'status': 'ok', 'time_exec': 0.0185549259185791, 'time_server': 1726149441}
2024-09-12 15:57:21.162 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] No device data available
2024-09-12 15:57:21.162 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher air_care added
2024-09-12 15:57:21.323 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher home-645b86f3ff51c00xxxxxxxx added
2024-09-12 15:57:21.382 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher air_care removed
2024-09-12 15:57:21.575 DEBUG (MainThread) [pyatmo.auth] addwebhook: <ClientResponse(https://api.netatmo.com/api/addwebhook) [200 OK]>
<CIMultiDictProxy('Server': 'nginx', 'Date': 'Thu, 12 Sep 2024 13:57:21 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-09-12 15:57:21.579 INFO (MainThread) [homeassistant.components.netatmo] Register Netatmo webhook: https://exxxxxxxx.duckdns.org/api/webhook/29aa3463a54939cc8be4e914dedbc501xxxxxxxxxxxxxxxx
2024-09-12 15:58:20.947 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 299
2024-09-12 15:58:22.466 DEBUG (MainThread) [pyatmo.auth] dropwebhook: <ClientResponse(https://api.netatmo.com/api/dropwebhook) [200 OK]>
<CIMultiDictProxy('Server': 'nginx', 'Date': 'Thu, 12 Sep 2024 13:58:22 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-09-12 15:58:22.466 INFO (MainThread) [homeassistant.components.netatmo] Unregister Netatmo webhook
2024-09-12 15:58:22.478 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather removed
2024-09-12 15:58:22.597 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher account added
2024-09-12 15:58:22.740 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher weather added
2024-09-12 15:58:22.852 DEBUG (MainThread) [pyatmo.helpers] Server response (tag: devices): {'body': {'devices': [], 'user': {'mail': '[email protected]', 'administrative': {'lang': 'fr', 'reg_locale': 'fr-FR', 'country': 'FR', 'unit': 0, 'windunit': 0, 'pressureunit': 0, 'feel_like_algo': 0}}}, 'status': 'ok', 'time_exec': 0.030803918838500977, 'time_server': 1726149502}
2024-09-12 15:58:22.852 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] No device data available
2024-09-12 15:58:22.853 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher air_care added
2024-09-12 15:58:23.036 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher home-645b86f3ff51c003xxxxxxxx added
2024-09-12 15:58:23.095 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Publisher air_care removed
2024-09-12 15:58:27.188 DEBUG (MainThread) [pyatmo.auth] The Netatmo API returned b'{"error":{"code":21,"message":"Invalid url parameter"}}' (400)
2024-09-12 15:58:27.189 ERROR (MainThread) [homeassistant.components.netatmo] Error during webhook registration - ("400 - Bad request - Invalid url parameter (21) when accessing 'https://api.netatmo.com/api/addwebhook'",)
2024-09-12 15:59:22.719 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 298
Additional information
No response
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 closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign netatmoRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove 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)
Same here, thanks for reporting
Same here as well.
With so many people now reporting more or less exactly the same problem (here and in different other forums), we are eagerly awaiting feedback from @cgtobi 😶
Netatmo integration worked for long time - now I cant acccess my devices:
Logger: homeassistant.components.netatmo Quelle: components/netatmo/init.py:151 Integration: Netatmo (Dokumentation, Probleme) Erstmals aufgetreten: 13:20:05 (1 Vorkommnisse) Zuletzt protokolliert: 13:20:05
Webhook not registered - https and port 443 is required to register the webhook
Hello this is is a different issue. If you can’t reach port 443 from outside it’s possible that your reverse proxy has some issues. The issue in this thread is about the error “invalid parameters”
On 16 Sep 2024, at 13:23, Haifi58 @.***> wrote: Netatmo integration worked for long time - now I cant acccess my devices: Logger: homeassistant.components.netatmo Quelle: components/netatmo/init.py:151 Integration: Netatmo (Dokumentation, Probleme) Erstmals aufgetreten: 13:20:05 (1 Vorkommnisse) Zuletzt protokolliert: 13:20:05 Webhook not registered - https and port 443 is required to register the webhook
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Thanks for feedback
- opened dev Account in netatmo
- added credentials in home assistant
- added netatmo Integration
- could link Integration to dev Account
- works now 😀
Hey there, I have been able to move ahead thanks to this thread: the webhook now looks successfully registered but I get plenty of weird errors messages afterwards (see log below) and my Bubendorff shutters are still not showing up. I'll keep digging but it would be much appreciated if anyone could help me fixing this... Many thanks,
2024-09-16 19:28:20.454 INFO (MainThread) [homeassistant.components.netatmo.data_handler] Netatmo webhook successfully registered
2024-09-16 19:29:14.716 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 282
2024-09-16 19:29:27.342 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 362, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 563, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadHttpMessage: 400, message:
Pause on PRI/Upgrade:
b''
^
2024-09-16 19:30:11.939 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 208
2024-09-16 19:31:11.256 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 159
2024-09-16 19:31:17.139 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 362, in data_received
messages, upgraded, tail = self._request_parser.feed_data(data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "aiohttp/_http_parser.pyx", line 563, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadHttpMessage: 400, message:
Pause on PRI/Upgrade:
b''
^
2024-09-16 19:32:12.598 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 148
2024-09-16 19:33:11.396 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 131
2024-09-16 19:34:14.529 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 128
2024-09-16 19:35:13.137 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 119
2024-09-16 19:36:11.293 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 119
2024-09-16 19:37:14.924 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 112
2024-09-16 19:38:12.588 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 113
2024-09-16 19:43:10.994 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 87
2024-09-16 19:45:10.996 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 81
2024-09-16 19:46:11.139 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 79
2024-09-16 19:47:11.187 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 78
2024-09-16 19:48:12.481 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 80
2024-09-16 19:49:12.694 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 79
2024-09-16 19:50:12.597 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 81
2024-09-16 19:51:14.458 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 80
2024-09-16 19:52:12.131 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 82
2024-09-16 19:53:16.213 DEBUG (MainThread) [homeassistant.components.netatmo.data_handler] Calls per hour: 81
One step further!
2024-09-17 19:44:48.104 INFO (MainThread) [homeassistant.components.netatmo.data_handler] Netatmo webhook successfully registered
No more errors BUT... my Bubendorff shutters remain not visible from Netatmo integration while they are from iDiamant!
Also nothing is received when listening to netatmo_event from development tools section.
I guess something is still misconfigured, but I must say I have no further idea of what might be wrong, now... so if any one has any suggestion, it will be much appreciated!
Side note: I'll write details about settings changed somewhere here as soon as possible
Here's my experience: I have two Home Assistant instances - one is HA-OS based using NabuCasa, the other is HA Container Core exposed to the internet through a Reverse Proxy. Both have the Netatmo integration and both have indoor as well as outdoor cameras. Netatmo Webhooks worked well with both for a long time. Then, sometime this summer, it started to get hickups. Now, neither of my HA instances are able to trigger on motion or any other event, except if a camera incidentally drops off-line, which some of them do from time to time (it's always been a bit unstable), not knowing why. They usually come back on-line again by themselves after a short while (less than an hour). However, those off-line/on-line events do generate a proper webhook trigger, not randomly, but persistently, so it seems the communication does work as it should. Why no other events comes through, is beyond me. On both my HA instances I can run the register/un-register Netatmo webhook service successfully. No error messages.
I'm giving up: I'm finally using HomeKit to drive my Bubendorff shutters...
Anyone found a solution? I get the same error about invalid webhook parameter so my cameras haven’t worked for 2 weeks now
Still don't work on my side. I think I will drop the netatmo stuff into recycle bin...
Anyone found a solution? I get the same error about invalid webhook parameter so my cameras haven’t worked for 2 weeks now
What do you mean by "haven't worked"? Netatmo cameras work perfectly even if the webhook integration fails. So what exactly do you mean by "haven't worked"? If that means that you no longer have a video stream from your camera, then there's something wrong with your camera.
Anyone found a solution? I get the same error about invalid webhook parameter so my cameras haven’t worked for 2 weeks now
What do you mean by "haven't worked"? Netatmo cameras work perfectly even if the webhook integration fails. So what exactly do you mean by "haven't worked"? If that means that you no longer have a video stream from your camera, then there's something wrong with your camera.
They work in Netstmo App and in the Apple Home App, but in Home Assistant there is a red error mark next to all the camera entities
So, what Integration are you using (trying to use) in Home Assistant to get access to your cameras? Also, be aware that camera entities can only be registered once. You cannot have a camera in several integrations at the same time.
@cgtobi - I am desperately waiting for some advise or guidelines from you in these matters (and I think several others are too). Please give us a sign of hope. The Netatmo Integration has become critical for me.
Here's my latest observations: Suddenly one day, my indoor camera in my location named "EMA" began sending webhook events. I managed to capture the last one before it went quiet again:
Event 0 fired 09:16:
event_type: netatmo_event
data:
type: person
data:
user_id: 564de4f4XXXXXXX461b21eba
persons:
- id: cbf2e42c-9b57-XXXX-94e2-XXXXd76f2309
face_id: 64fb5cXXXXXXbe0111087149
face_key: 377d748c13dcXXXXXXd85c98710521ab742526e3b10a6dacdc5fc92fbb641ae
is_known: true
face_url: >-
https://netatmocameraimage.blob.core.windows.net/production/64fb5c411888be0111087149377d748c13XXXXXXXXXXXXXXX8710521ab742526e3b10a6dacdc5fc92fbb641ae?sv=2017-11-09&sr=b&se=2024-09-29T07:21:42Z&sp=r&spr=https&sig=4t3KiR9qNnukI1mVUepMTDv9Lw4%2F9RL6yT87EkNe55c%3D
snapshot_id: 66f8fedXXXXX5c083020fc709
snapshot_key: bee1f4aff258368f247XXXXXXXcdea229ec38803606269fce7ee0057cbea8d
snapshot_url: >-
https://netatmocameraimage.blob.core.windows.net/production/66f8feda3655c083020fc709beXXXXXXXXXXXX368f247b06204068cdea229ec38803606269fce7ee0057cbea8d?sv=2017-11-09&sr=b&se=2024-09-29T07:21:42Z&sp=r&spr=https&sig=RaAa0Qppo5b9KbLfaF2lEqQ5a0iPkl54gaGruwKMXX0%3D
event_type: person
camera_id: 70:ee:XX:XX:XX:d6
device_id: 70:ee:XX:XX:XX:d6
home_id: 64fb57XXXXXX21467d0aaeaf
home_name: EMA
event_id: 66f8fedXXXXXXX83020fc708
message: Ewa seen by Camera02
push_type: NACamera-person
id: cbf2e42c-XXXX-XXXX-94e2-c329d76f2309
name: Ewa
is_known: true
face_url: >-
https://netatmocameraimage.blob.core.windows.net/production/64fb5c4118XXXXXXXXX7149377d748c13dc5c83923d85c98710521ab742526e3b10a6dacdc5fc92fbb641ae?sv=2017-11-09&sr=b&se=2024-09-29T07:21:42Z&sp=r&spr=https&sig=4t3KiR9qNnukI1mVUepMTDv9Lw4%2F9RL6yT87EkNe55c%3D
device_id: null
origin: LOCAL
time_fired: "2024-09-29T07:16:50.667348+00:00"
context:
id: 01J8YA79BXXXXXX9JQSYXACJ
parent_id: null
user_id: null
(I have X'd out all the key-ID's for confidentialty purpose) As can be seen from this event capture, it is 100% correct. It even identifies my wife (who's name is Ewa) correctly as well as the name of my second home - which is "EMA" (let's refer to this as 'home_2') On this particular morning, nothing special took place. My wife just walked by the camera a couple of times and the integration reported 3 or 4 webhook events before going dead silent again. I have doublechecked the Netatmo dev page, and there's no ban.
Then, several days later when I returned to my other home (let's refer to it as 'home_1'), I suddenly one day received webhook events in home_1 from the camera in home_2 (!?!?)
event_type: netatmo_event
data:
type: human
data:
user_id: 564de4XXXXXX08461b21eba
event_type: human
camera_id: 70:ee:XX:XX:XXd6
device_id: 70:ee:XX:XX:XX:d6
home_id: 64fb572XXXXXX1467d0aaeaf
home_name: EMA
message: Person seen by Camera02
push_type: NACamera-human
device_id: null
origin: LOCAL
time_fired: "2024-10-02T07:37:12.678808+00:00"
context:
id: 01J962JQQ6XXXXXXWM6J2HHX5
parent_id: null
user_id: null
I received several such webhook events consecutively, before it again went dead silent. The event data looks 100% correct, but why did events from a camera in home_2 get sent to HA in home_1 all of a sudden???
I'm beginning to suspect that the either the Netatmo HA integration and/or the Netatmo API platform isn't able to correctly handle two homes linked into one and the same Netatmo account? I do of course have two differently named apps created on the dev platform with separate distinct client_id's and client_secret's which has been used when linking into each HA instance. But thinking about it, there's no field anywhere in the App creation process that clearly links an App to a specific home. So how does the platform know which camera's belongs where? Maybe I shouldn't use two apps, but only one? And maybe I shouldn't (cannot) link the Netatmo dev API into more than one of my HA instances, since all cameras from both homes are present in both HA instances simultaneously. Come to think of it - it appears as if the Netatmo platform wasn't designed with recurring customers buying Netatmo Equipments for more than a single home - in mind.
Those are two distinct issues. Please open a separate issue for the missing Bubendorff shutters. Please also provide detailed information about the exact device type that is missing.
About the webhook issue, if the registration has been successful and no events are being received there is not much we can do as this is completely in the hands of Netatmo.
About the webhook issue, if the registration has been successful and no events are being received there is not much we can do as this is completely in the hands of Netatmo.
Unfortunately this is not an issue of non receiving events. I'm still experiencing the issue
Error during webhook registration - ("400 - Bad request - Invalid url parameter (21) when accessing 'https://api.netatmo.com/api/addwebhook'",)
And from me a well: it is not about not receiving webhooks at all. It's about receiving those webhooks unreliability, randomly or for the most part - not at all. All my attempts to talk to Netatmo support about it, they just say that the HA integration is not their work, and therefor they cannot help me. They advice me to contact the maintainer of the integration 🙄 So, where does that leave us?
If it may help, I have read somewhere (I can’t remember where) that the issue with the webhook registration happens when you have multiple houses setup in Netatmo. This is my case, but I don’t know if that’s the reason
I don't have an issue with webhook registration. I can register and deregister Netatmo webhook in both my HA instances without any error messages. My problem is that those webhook events themselves comes in completely randomly, or not at all - for long period of times.
Hi,
I am the same problem.
My Bubendorff shuttle are not visible in HA.
I try, after remove Netatmo integrate, to add an app account manually but, with this account or the principal, my shuttle are not visible.
any idea ?
So, I cleaned up and removed all unused Dev Apps from my online Netstmo account, including also the Home Assistant Cloud App instances. Then I deleted and re-installed the Netatmo Integration in HA and linked it to the App that I created in dev.netatmo.com with correct client_id and client_secret entered in Apllication Credentials in HA. During re-installation of the Netatmo Integration I fid not choose Home Assistant Cloud, but my own App. But in URL field I typed the Cloud link for remote access. Now webhook events work as it should.
Thx @oywino
and after that all bubendorff shuttle are visible in HA ?
Yes, but as I said - I never had any problems with the shutters. They were always present and working. My problem was the missing webhook events.
@oywino : Thx. So, the situation with @edenis875 was different !
like me, the bubendorff shunters are not visible.
Webhook events it’s another problem
HI all, as you i have the same issue wit the webhook, tried to delete integration, re-connect it, delete webhook and redo a new, but nothing changes. On Netatmo app i receive thenotification of the events but nothing on Home assistant, sometimes seems randomly i receive some event 2 o 3 in one day and after the silence. I took contact with netatmo for this issue and they say that if we receive evento on app, is not a problem netatmo side. If i try to listener netatmo_event in home assistan i receive nothing event instead on android app i receive face notification etc. I my case i use nabucasa if it's could be usefull..... I don't know how to check thw webhook connection between netatmo and nabucasa/hassio we are stucked, need help.
“Help Me @cgtobi, You’re My Only Hope.” (cit) :)
@asvel78
[https://www.home-assistant.io/integrations/netatmo/#webhook-events]
(())