Climate Unavailable For All Rooms

[kneave]

I recently updated to the 3.0 release and have started seeing the climate entity become unavailable for all rooms, it seems to be all or nothing, it's not just one room that loses the entity. If I delete the hub and reconnect it, it seems to come back for a while, though if I enable any of the entities that aren't enabled by default it's a bit of a lottery as to if the climate entities will all disappear.

For example, I just enabled the differential control on my living room device and the climate entities immediately disappeared, I'm not sure if this is a coincidence or if there's a link.

I still seem to be getting live data from all the devices, two of the rooms have floor sensors for example and those are continuing to update, but the rest of the room thermostats no longer are able to be controlled or provide their status. I do still get "current temperature" if I separately enable those entities.

I'm relatively new to Home Assistant but I am a software engineer, I'm happy to grab anything elses needed to troubleshoot this but in the context of HA I'm not sure what is needed. If you could let me know I'd be happy to help though.

addon version: 3.0.0-release
Core: 2025.1.4
Supervisor: 2024.12.3
Operating System: 14.1

Hub: Neohub v2
Thermostats: 12 of NeoStat v2

[ocrease]

Hi @kneave could you download diagnostics (from one of the device pages). Ideally when its working (eg before the entities disappear) and when its not. Do the logs show anything?

[kneave]

Will do, when I was troubleshooting this yesterday I did see this error but can't reproduce it now:

2025-01-25 23:33:17.908 ERROR (MainThread) [homeassistant.components.climate] Error while setting up heatmiserneo platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/heatmiserneo/climate.py", line 83, in async_setup_entry
    neo_devices[config].available_modes,
    ~~~~~~~~~~~^^^^^^^^
KeyError: 'Front Room_NEOHUB-SN:000000-NeoHub.megadodo.int_d6f0019e7f468_heatmiser_neostat'
2025-01-25 23:37:01.691 ERROR (MainThread) [homeassistant.components.climate] Error while setting up heatmiserneo platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/heatmiserneo/climate.py", line 83, in async_setup_entry
    neo_devices[config].available_modes,
    ~~~~~~~~~~~^^^^^^^^
KeyError: 'Front Room_NEOHUB-SN:000000-NeoHub.megadodo.int_d6f0019e7f468_heatmiser_neostat'
2025-01-25 23:37:41.511 ERROR (MainThread) [homeassistant.components.climate] Error while setting up heatmiserneo platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/heatmiserneo/climate.py", line 83, in async_setup_entry
    neo_devices[config].available_modes,
    ~~~~~~~~~~~^^^^^^^^
KeyError: 'Front Room_NEOHUB-SN:000000-NeoHub.megadodo.int_d6f0019e7f468_heatmiser_neostat'
2025-01-25 23:43:38.915 ERROR (MainThread) [homeassistant.components.climate] Error while setting up heatmiserneo platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/heatmiserneo/climate.py", line 83, in async_setup_entry
    neo_devices[config].available_modes,
    ~~~~~~~~~~~^^^^^^^^
KeyError: 'Front Room_NEOHUB-SN:000000-NeoHub.megadodo.int_d6f0019e7f468_heatmiser_neostat'

I was getting a bunch of these for each room, will keep an eye on it and see if it returns.

[ocrease]

Did you make changes using this screen?

If you have used it, I would recommend you don't. It shouldn't be necessary for NeoStat v2 thermostats (only relevant for NeoStat HC, and even then likely not working well)

Also you said you "delete the hub and reconnect it", just checking you mean this:

[kneave]

I had indeed clicked configure and gone through that, it did cause the "unavailable" error to occur, also I did indeed click that delete button and then re-add it. I have also seen this happen when enabling different sensors and config options, you're probably right that the errors above were from selecting the config though I can't reproduce it now.

I've got the diagnostics from it working, will keeping an eye on it to get the same if this happens again.

[ocrease]

Ok, as I said, the configure stuff is not required for your thermostats, so just keep clear and it should be fine. If you've played with it since you last deleted the hub, I recommend deleting and re-adding it again.

Enabling sensors and changing the advanced parameters (such as switching differential etc) should all work fine if you haven't touched the configure window.

[kneave]

I have played around with it just to see if I can reproduce it, I'll leave it as is just so I can get the logs if it occurs so we can confirm what's going on. Happy for this to be closed until/if it reoccurs if you'd prefer?

[ocrease]

You can leave it open. Thanks for reporting it. I think I've reproduced it on my side too, so I'll see if I can do a fix

[ocrease]

v3.1.0-beta.4 has been released which updates the Configure flow. Unless you have NeoStat HC devices, you should now see a note telling you that you don't have any thermostats that can be configured.

@kneave If you are willing to try it, let me know how it goes.

[ocrease]

Closing this in favour of #78. Please report any issues in that ticket instead.

[kneave]

v3.1.0-beta.4 has been released which updates the Configure flow. Unless you have NeoStat HC devices, you should now see a note telling you that you don't have any thermostats that can be configured.

@kneave If you are willing to try it, let me know how it goes.

Installed beta 4 and for the first time had the hub detected which was a pleasant surprise! I've deleted and added the hub fresh and will report back if anything goes amiss. Thanks for the quick turnaround on this