Hi,
since the update to 2023.6.1 (I skipped .0) my Fibaro Door Window Sensor 2 behaves strange. After every activation it becomes unavailable and directly fires the event again.
Before 2023.6 I used the “Fibaro Door Window Sensor 2 Access Control Door state” which is no longer available now, so this is what my “Fibaro Door Window Sensor 2 Window/door is open” sensor shows:
I think I’m experience similar behavior as you are describing. But I see that ALL Z-Wave entities are set as “unavailable” for some seconds when this happens.
The issue was introduced after updating to 2023.6.
I looks like this might be connected to state changes for the “access control door state” as I’m getting this error at the same time:
2023-06-12 09:46:41.119 ERROR (MainThread) [homeassistant.components.zwave_js] Unexpected exception: Sensor sensor.1bad_dor_access_control_door_state provides state value '22', which is not in the list of options provided
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/zwave_js/__init__.py", line 778, in client_listen
await client.listen(driver_ready)
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/client.py", line 261, in listen
await self.receive_until_closed()
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/client.py", line 329, in receive_until_closed
self._handle_incoming_message(data)
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/client.py", line 412, in _handle_incoming_message
self.driver.receive_event(event) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/driver.py", line 83, in receive_event
self.controller.receive_event(event)
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/controller/__init__.py", line 813, in receive_event
node.receive_event(event)
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/model/node/__init__.py", line 424, in receive_event
self.emit(event.type, event.data)
File "/usr/local/lib/python3.11/site-packages/zwave_js_server/event.py", line 63, in emit
listener(data)
File "/usr/src/homeassistant/homeassistant/components/zwave_js/entity.py", line 233, in _value_changed
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 590, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 654, in _async_write_ha_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 596, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 563, in state
raise ValueError(
ValueError: Sensor sensor.1bad_dor_access_control_door_state provides state value '22', which is not in the list of options provided
I’m also seeing this message in ZwaveJS UI log at the same time:
2023-06-12 09:46:41.163 INFO Z-WAVE-SERVER: Client disconnected
I “solved” the issue by disable the “access control door state”-entities that triggered the failed connection.
Thank you, that worked for me as well!