-
Notifications
You must be signed in to change notification settings - Fork 30
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
Sonoff adapter not correcly supporting dimmer control #282
Comments
Does no one else have the same problem? I just can't seem to get the issue solved. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
I use the sonoff adapter (Version 2.5.1) with an idino zigbee dimmer which ist connected to a sonoff zigbee bridge. The bridge is running on Tasmota 12.1.1 and if I use the console command zbsend() to switch or dim the lights everything works as expected. The dimmer shows up correctly on the object view and the current state (on/off) or dimmer value (0..254) is updated as expected in the object <sonoff.0.zbbridge.xxx.SENSOR.ZbReceived.0x3180.power> (or .dimmer) datapoints. So far so good. The issue is, that I cannot control the dimmer through the adapter/iobroker. The ...power/.dimmer datapoints senn to be read only. If I set them to "writeable" in the datapoint properties they still don't update. It seems like there is no command implemented to react to a change in the datapoint and send the corresponding command via MQTT / zigbee to the dimmer.
Everytime I change a value i get the log entry <Client "zbbridge.xxx.SENSOR.ZbReceived.0x3180" not connected>
There are no other ojects within the object tree that would allow for control of the dimmer.
Can this be easely fixed or is there a work around?
Thanks for any help
The text was updated successfully, but these errors were encountered: