sebk-666
(Sebastian)
October 27, 2023, 3:00pm
1
Hi,
I updated from 2023.10.3 to 2023.10.5 a few hours back and now reverted to the .3 release.
With .5, all my Z-Wave devices started to toggle constantly between “unavailable” and their acutal state.
Example:
This is exceptionally annoying when sensor state changes trigger automations.
I’m using the latest Z-Wave-JS-UI container for my devices and I’m running HA as docker container as well.
Has anyone else seen this? Did I miss some breaking change?
Sebastian
EDIT: ok, I should have checked the issues on GitHub first. Apparently, this is already known and I’m not the only one affected:
opened 06:45AM - 24 Oct 23 UTC
integration: zwave_js
### The problem
HA is losing contact with all Z-wave devices every 30-40 seco… nds. Just drops, and reconnects.
Running ZwaveJS UI 2.2.3 - tested with 2.2.1 and 2.2.2, and same issue there...
Example (it is the same on all z-wave devices....)
![Screenshot 2023-10-24 at 08 40 37](https://github.com/home-assistant/core/assets/49139069/461dd097-386a-475a-b59d-85c185e264f6)
### What version of Home Assistant Core has the issue?
2023.10.5
### What was the last working version of Home Assistant Core?
2023.10.3
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Z-Wave JS UI
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
```txt
Logger: homeassistant
Source: components/zwave_js/climate.py:265
First occurred: 08:26:33 (50 occurrences)
Last logged: 08:37:05
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 752, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1057, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 779, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 879, in _async_write_ha_state
state, attr = self._async_generate_attributes()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 822, in _async_generate_attributes
attr.update(self.state_attributes or {})
^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 323, in state_attributes
self.target_temperature,
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zwave_js/climate.py", line 322, in target_temperature
) or not self._current_mode_setpoint_enums:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/zwave_js/climate.py", line 265, in _current_mode_setpoint_enums
return [ThermostatSetpointType(int(self.info.primary_value.property_key))]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/enum.py", line 712, in __call__
return cls.__new__(cls, value)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/enum.py", line 1128, in __new__
raise ve_exc
ValueError: 3 is not a valid ThermostatSetpointType
```
### Additional information
_No response_