Hello!
I’ve been encountering an issue with one of my dimmers and hope that some of you might be able to help me figuring it out.
The latest addition to my smart home is a Namron zigbee dimmer which seemed to work fine like the other Namron dimmers I have (none of which is this particular model). However, when turned on or off via Home Assistant the state of the device/entity is not updated. Turning it off in HA does indeed turn the light off, but it keeps displaying as on and vice versa. Setting the light level works fine. Adjusting the lights via the built in knob on the unit also updates the state in HA just fine.
While attempting to figure out the issue I tried calling the zha service using the entity configuration ui.
Doing this turns the light on just like hitting the button otherwise inside HA. But this time I get an error message:
Looking at the HA logs I believe this is the cause
Logger: homeassistant.components.websocket_api.http.connection
Source: components/zha/core/device.py:727
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: March 12, 2023 at 21:16:47 (5 occurrences)
Last logged: 07:22:53
[2557127312]
[2682289816]
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 199, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1808, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1845, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 762, in admin_handler
await result
File "/usr/src/homeassistant/homeassistant/components/zha/api.py", line 1336, in issue_zigbee_cluster_command
await zha_device.issue_cluster_command(
File "/usr/src/homeassistant/homeassistant/components/zha/core/device.py", line 727, in issue_cluster_command
response = await getattr(cluster, commands[command].name)(
File "/usr/local/lib/python3.10/site-packages/zigpy/zcl/__init__.py", line 324, in request
return await self._endpoint.request(
File "/usr/local/lib/python3.10/site-packages/zigpy/endpoint.py", line 237, in request
return await self.device.request(
File "/usr/local/lib/python3.10/site-packages/zigpy/device.py", line 313, in request
return await asyncio.wait_for(req.result, timeout)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError
I should mention that I have a friend, who also bought the exact same model and otherwise has pretty much the same setup as I do (HA on a pi using the ConBee II for zigbee radio), has the exact same issue. So I don’t think my unit is defect.
Update 1:
I was able to make a (hopefully) temporary workaround by using zha_toolkit to update the device state after performing an action. Incorporating that into some scripts does allow for fairly normal operation of the unit through HA but it’s certainly not optimal.