home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.06k stars 31.08k forks source link

Netatmo integration still not working.... #118046

Closed sdudulon2 closed 3 months ago

sdudulon2 commented 6 months ago

The problem

Hi, I am moving from Jeedom to Hass and i can't manage to integrate netatmo. In jeedom, the process is similar (via dev account) and it's working fine. In home assistant, i have followed the process (create a new app on netatmo dev website - integrate it in HA). i have of course tried many many times to delete the integration, unregister / register webhook / tried via HA cloud..... still the same result : not working. I have 2 Netatmo Welcome + 1 presence + 1 thermostat and several valves + 1 netatmo Station. What's working : - netatmo Station and presence Light what's not working : everything else Could you please have a look to it ?

What version of Home Assistant Core has the issue?

core-2024.5.4

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

2024-05-24 13:46:47.350 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration ui_lovelace_minimalist 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-05-24 13:46:47.353 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration adaptive_lighting 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-05-24 13:46:47.355 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration tahoma 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-05-24 13:46:47.360 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration virtual 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-05-24 13:46:47.364 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration meross_cloud 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-05-24 13:46:47.367 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration alarmo 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-05-24 13:46:47.369 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration asusrouter 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-05-24 13:46:47.371 WARNING (SyncWorker_5) [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-05-24 13:46:47.373 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration cover_rf_time_based 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-05-24 13:46:47.379 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration heatzy 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-05-24 13:46:47.385 WARNING (SyncWorker_5) [homeassistant.loader] We found a custom integration landroid_cloud 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-05-24 13:46:48.144 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly 2024-05-24 13:46:48.180 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=126 from 2024-05-23 13:09:06.541017) 2024-05-24 13:46:52.704 WARNING (MainThread) [py.warnings] /usr/local/lib/python3.12/site-packages/aiocoap/transports/tinydtls.py:165: UserWarning: DTLS module did not shut down the DTLSSocket perfectly; it still tried to call _write in vain warnings.warn("DTLS module did not shut down the DTLSSocket "

2024-05-24 13:46:52.731 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module with args ('custom_components.heatzy',) in /usr/src/homeassistant/homeassistant/loader.py, line 1041: ComponentProtocol, importlib.import_module(self.pkg_path) inside the event loop 2024-05-24 13:46:59.100 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues 2024-05-24 13:47:01.548 WARNING (MainThread) [custom_components.meross_cloud] Skip MQTT cert validation option set to: False 2024-05-24 13:47:01.795 WARNING (MainThread) [custom_components.meross_cloud]

Meross Cloud Custom component Developed by Alberto Geniola Low level library version: 0.4.7.2b3

This custom component is under development and not yet ready for production use. In case of errors/misbehave, please report it here: https://github.com/albertogeniola/meross-homeassistant/issues

If you like this extension and you want to support it, please consider donating.

List of devices reported by HTTP API:

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

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

sdudulon2 commented 6 months ago

I can add that when I listen to netatmo_event, events come to home assistant ent_type: netatmo_event data: type: setpoint_event data: user_id: XXXXXX home: id: 5XXXXXX rooms:

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.