-
Notifications
You must be signed in to change notification settings - Fork 508
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 D1 ZCL command "Move to level" fails 50% #2234
Comments
|
You got me on the right track. I experimented with the byte length and with 9 bytes it worked just fine. 😃 👍 |
Here is the right code. I forgot to mention that I edited the length of the ZCL template.
|
Dear o-live-r, I was so happy to find this thread. Been looking for a way to do this! Best regards, |
I did it the same way as sheineme commented on 9 Jan 2019 #360 (comment) |
I am looking for a working solution for programming the two switch inputs.
My goal is that switching input 1 dims up to 20%:bulb: when switched on via a static switch (toggle switch) and dims down to 0%:bulb: when switched off.
Switching input 2 should dim up to 100%:bulb: when switched on and dim down to 20%:bulb: when switched off.
The function is to use a twilight switch at switch input 1 to switch on a night light and when a motion detector is triggered, the light at switch input 2 is to be raised to 100%:bulb:.
As soon as the run-on time of the motion detector has expired, the light should then be dimmed back down to 20%:bulb:. The twilight switch is to switch off the light completely dimmed at a certain brightness. The motion detector has also integrated a twilight switch and will then no longer trigger even with the same brightness. All switching operations should be dimmed.
All of this should work without a zigbee connection and be programmed in advance on the D1.
I have already tested the following ZCL commands with 50% success rate 😞 :
Unfortunately I can't get any further without help, because I don't understand why calling the "Move to level" function for input 0x00 works for both switching operations at switch 1 and the function completely fails for input 0x01 (switch 2).
The values from the table only describe my approach. The above-mentioned goal remains. Unfortunately I did not find any further explanations in the technical reference. Where is the mistake?:thinking:
The text was updated successfully, but these errors were encountered: