Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ubisys S1-R Series2 (5601) stop responding to certain actions from Zigbee2MQTT after a few days #26748

Open
emagnier opened this issue Mar 15, 2025 · 0 comments
Labels
deconz Issues related to deconz driver problem Something isn't working

Comments

@emagnier
Copy link

What happened?

I have several Ubisys S1-R (5601) (Series 2). Once installed, after a few days without issues, they stop responding to certain actions from Zigbee2MQTT. Specifically:

  • Manually retrieving or updating the state (On/Off).
  • Retrieving or updating the "Power-on behavior" option.
  • The "Identify" action.

However, they continue to work normally when controlled via physical buttons.

Some actions still work correctly:

  • Physical buttons function properly, and the state updates instantly in Zigbee2MQTT.
  • Power and Energy values are also reported correctly. Clicking the refresh button (the blue button with two circular arrows) also works fine.

Workaround: Deleting and re-pairing these devices solves the issue, but this is far from ideal. Clicking the orange "Reconfigure" button does not resolve the problem.

What did you expect to happen?

Being able to modify the state (On/Off) from Zigbee2MQTT, as well as update the "Power-on behavior" and "Identify" actions.

How to reproduce it (minimal and precise)

Wait a few days (or weeks?), and they eventually stop functioning entirely from Zigbee2MQTT.

Zigbee2MQTT version

2.1.3-1

Adapter firmware version

0x26720700

Adapter

ConBee2

Setup

Add-on on Home Assistant OS, ODROID-N2/N2+

Debug log

error 2025-03-15 17:31:07z2m: Publish 'get' 'power_on_behavior' to 'Pallier lumière' failed: 'Error: ZCL command 0x001fee000000ac1d/0 genOnOff.read(["startUpOnOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (83) Error: waiting for response TIMEOUT)'
error 2025-03-15 17:31:47z2m: Publish 'get' 'state' to 'Pallier lumière' failed: 'Error: ZCL command 0x001fee000000ac1d/0 genOnOff.read(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (89) Error: waiting for response TIMEOUT)'
error 2025-03-15 17:32:03z2m: Publish 'set' 'state' to 'Pallier lumière' failed: 'Error: ZCL command 0x001fee000000ac1d/0 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (93) Error: waiting for response TIMEOUT)'
error 2025-03-15 17:32:14z2m: Publish 'set' 'identify' to 'Pallier lumière' failed: 'Error: ZCL command 0x001fee000000ac1d/0 genIdentify.identify({"identifytime":3}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (95) Error: waiting for response TIMEOUT)'
error 2025-03-15 17:32:26z2m: Publish 'set' 'power_on_behavior' to 'Pallier lumière' failed: 'Error: ZCL command 0x001fee000000ac1d/0 genOnOff.write({"startUpOnOff":2}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (96) Error: waiting for response TIMEOUT)'
@emagnier emagnier added the problem Something isn't working label Mar 15, 2025
@Nerivec Nerivec added the deconz Issues related to deconz driver label Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deconz Issues related to deconz driver problem Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants