-
Notifications
You must be signed in to change notification settings - Fork 631
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
[Device Support Request] LEDVANCE Panel TW Z3 #1760
Comments
Thanks for creating the dedicated issue. The LEDVANCE "Z3" products are (thankfully) entirely different from the old OSRAM/LEDVANCE Lightify series. zha-device-handlers/zhaquirks/ledvance/__init__.py Lines 8 to 18 in a072ca3
However, I know that some LEDVANCE products still support setting standard Zigbee 3 attributes but don't allow reading of them at all. The values are:
If this works, great! Ignore the rest of my comment then (and let me know that it worked). It's also possible that your device still supports the I've quickly thrown together a custom quirk (could be completely broken/not working at all because I haven't had time to properly write or test it but maybe you can fix the remaining issues if there are any). To install it:
zha:
custom_quirks_path: /config/zha_custom_quirks (assuming your HA config directory is at
Through the Edit: Just updated the quirk because I've noticed an issue (please make sure the name of the ZIP file contains "version 3") |
Julian, first of all thank you very much for the prompt reply. :) I had already spent all evening trying with the standard cluster/attributes, but it didn't work, that's why I then looked on the repo for other solutions, when I found your issue. I also made a script trying to set the service: zha.set_zigbee_cluster_attribute
data:
value: 0xff
ieee: f0:d1:b8:00:00:13:d6:9b
endpoint_id: 1
cluster_id: 0x0006
cluster_type: in
attribute: 0x4003 So now I downloaded your v2 zip, and configured ZHA. Unfortunately on restart I have this error regarding
|
If that happens, you can always remove the custom quirk (the Change the imports at the top to this (notice the added Basic,
GreenPowerProxy,
Groups,
Identify,
LevelControl,
OnOff,
Ota,
Scenes, Or just download the updated quirk file here: ledvance_panel_tw_z3.py version 3.zip and replace the old file. (Also, I'm not sure if it's actually needed, but when changing the custom quirk, always delete the |
I simply commented the quirks line in zha section and restarted. :)
Ok, now I modified the quirk adding the line and it started fine. I opened up the clusters and I don't see Should I execute the command anyway? |
I tried it anyway, it didn't work, the panel turns on when power comes back on. I guess |
Ah, that was the first thing I changed (in the "v2 version"). I originally had the LedvanceCluster but that has a different cluster id. The signature of your device reports Can you check if it saves some defaults at all? Like, turn the brightness to 1% (but leave the light on), execute |
Maybe since the fw was updated in late 2021, they switched to Osram clusterId instead of ledvance?
Set at 2%, powered off, powered on, and it turned on full bright. :( There's no chance to "read" what is the power on config? It's so annoying...
No errors... |
Can you click the "Add device" button in ZHA to permit joins and then reset the LEDVANCE device (so it re-joins and re-interviews and reports all possible "new clusters"). Also, you might have tried this too but does setting |
Also try to execute the |
Reconfiguration (button on the left, under device info) doesn't do exactly that? not reliable?
I think I tried it...it didn't work, but I'll try again. |
I'm pretty sure it doesn't re-interview the device (but only does binding and reporting). It would be nice if you could reset one panel to see if the signature changes when re-pairing after the firmware update. |
Tried both manuf. codes, doesn't work. Tried also initializing one of the three panels and rejoined the zigbee network, made no difference.
Nothing. I'm starting to lose hope...:) |
Likely not fixable, as the device doesn't seem to have any attributes for saving power-on-state. |
Is your feature request related to a problem? Please describe.
I'm unable to set the power on state on LEDVANCE Panel TW Z3. I have 3 of them in the bedrooms and when power goes off and on during the night they turn on and I must make sure they remain off, otherwise my wife and kids get mad at me and my "smart" automation stuff...:)
Describe the solution you'd like
Quirk to add the
0x01
(save_defaults
) command in the0xfc01
cluster to save the default power on state. Like in #459 (commented in #449) by @TheJulianJES. That seems to be working for all LEDVANCE lights.I'd like to do a PR starting from #459, but I need a little bit of guidance regarding the light type differences, how does the quirk match the ID of the device, etc. would love to learn how to do it, if you have the patience to guide me a little bit.
Thanks for any help on this.
Device signature
The text was updated successfully, but these errors were encountered: