I have the same problems since yesterday…
Several thermostats - all unavailable.
The my_home enitiy - where i can set the heating schedule - is working (as well as i usually does - considering the problems with the update of the state)
My Netatmo cameras are working.
Tried everything as above - enable/disable, reinstall integration…
An observation… my thermostats became unavailable right after i switched my RPI3 from wired network to wifi - at that time HA changed IP address … don’t know if that helps.
Was running 2022.11.x
Just upgraded to 2023.1.4
I have same problem - Netatmo climate devices are working for some time and then after reboot unavailable for many days and then coming back again till I restart or upgrade HA. Now It become real problem as Netatmo is discontinuing with IFTTT and I need HA to start to work to get mine automations working- please help
Same issue here and ticket is stale on github, @cgtobi are you still working on it? Is a very annoying issue unfortunately…
The odd thing is that it affects only climate entities, cameras, select, light, anything else from Netatmo integration works perfectly.
My Netatmo Weather Station works with HA 2023.11.0 but not with 2023.11.3. However, these are two separate installations connected to the same Netatmo service. Saying that, I am not sure whether Netatmo stopped working on the second HA server while I upgraded to 2023.11.3. Netatmo is still working on the other HA server with 2023.11.0.
In my case the connection to Netatmo is lost in the HA integration. Restart of all kinds incl. HA host does not solve the problem. Renaming devices and further recommendations here in the discussion do not work.
The problem with the valves being unavailable remains. Strangely enough I can see the battery percentage of all of them. Just not the temperature settings.
Logger: homeassistant.config_entries
Source: config_entries.py:504
First occurred: 29 March 2024 at 20:31:47 (1 occurrences)
Last logged: 29 March 2024 at 20:31:47
Error setting up entry Home Assistant Cloud for netatmo
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 504, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/components/netatmo/init.py”, line 113, in async_setup_entry
await data_handler.async_setup()
File “/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py”, line 176, in async_setup
await self.async_dispatch()
File “/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py”, line 315, in async_dispatch
await self.subscribe(HOME, signal_home, None, home_id=home.entity_id)
File “/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py”, line 278, in subscribe
await self.async_fetch_data(signal_name)
File “/usr/src/homeassistant/homeassistant/components/netatmo/data_handler.py”, line 233, in async_fetch_data
await getattr(self.account, self.publisher[signal_name].method)(
File “/usr/local/lib/python3.12/site-packages/pyatmo/account.py”, line 79, in async_update_status
await self.homes[home_id].update(raw_data)
File “/usr/local/lib/python3.12/site-packages/pyatmo/home.py”, line 141, in update
self.rooms[room[“id”]].update(room)
~~~~~~~~~~^^^^^^^^^^^^
KeyError: ‘212197570’
I’m having the same issue. It appeared a few days ago, randomly. To add some more info:
The integration is working fine in an Home Assistant development environment I set up for testing
I have two different setups, one on a Raspberry Pi 3B, one on a Raspberry Pi 4, both update to the latest versions of o.s., core, …
I tried to uninstall and reinstall the integration on both Raspberries. Sometime I got “unknown” both for temperatures and for batteries. Sometime I got “unknown” for the temperatures, and a percentage for batteries
Here are the attributes for one of the entities working ok in the development environment:
hvac_modes: auto, heat
min_temp: 7
max_temp: 30
target_temp_step: 0.5
preset_modes: away, boost, Frost Guard, Schedule
current_temperature: 22
temperature: 21
hvac_action: idle
preset_mode: Schedule
selected_schedule: Scuola e smart working
heating_power_request: 0
attribution: Data provided by Netatmo
friendly_name: Termoarredo bagno grande
supported_features: 401
Here are the attributes for the same entity from one of the Raspberry installation:
hvac_modes: auto, heat
min_temp: 7
max_temp: 30
target_temp_step: 0.5
preset_modes: away, boost, Frost Guard, Schedule
attribution: Data provided by Netatmo
friendly_name: Termoarredo bagno grande
supported_features: 401
As you can see, some attributes (besides the state) are missing. Hope this gives you some hints. Please consider me available for further testing.
Could it be really linked to having more than one home assistant instances connected to netatmo? I have this same issue since years and indeed I have two instances
It all (magically) started working again a few weeks after my previous post. It seemed to work for a few months (or, to be fair, I didn’t check since the thermostats were turned off in summer…). Now, since it’s almost time to switch the thermostats on again I realized they are suddenly giving “unknown” both for temperature and for batteries. Since a few months I have a single instance of Home Assistant on a Raspberry Pi4.
Hello Fabiano, same situation here. I don’t think its something related to Raspberry, ad i have HA running in docker on a Synology. I can’t figure out how to put them back online, as everything else of the Netatmo integration is fine. I also can’t understand why they are correctly showed in HomeKit and Energy App by Netatmo…. I’m now thinking to pair them via HomeKit and bridging them through HA to HomeKit devices….
same problem here as well. Netatmo integration says entities not available but if you click on entity it does show actual values.
This netatmo stuff is highly unreliable and decided never buying it again. It’s quit expensive but the netatmo App is a bit unclear to me about what is exactly reported and the app sometimes also losses contact with the netatmo device.
Since the HA integration is also unreliable I gave up on Netatmo. Rather buy Ikea (air quality) sensors next time. No problem at all with those and costs less then halve the price of Netatmo.