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
deconz V2.25.3 - Signify LTW012 show ON (in phoscon) even though it is OFF #7579
Comments
Could you please check what happens when:
If these don’t correct the state, please attach screenshots of these clusters. |
I will check that if you can provide a little more information about where i can find - attributes of Hue Effects and On/Off cluster in the (deconz?) GUI as i am running deconz on a headless system and therefore i am not familiar with the GUI at all. |
That confirms the light reports as off (and 25% brightness and My LTW012 (E14 candle) is (still?) on 1.108.5; I didn't realise there's a newer firmware, but looking at the screenshots, that part hasn't changed. Does the GUI show the LTW012 as supported by DDF? Do you see any errors in the deCONZ log, when enabling ERROR, DDF, and JS in the debug view? What's the debug log when reading the Hue Effects cluster? Just to be sure: did you check other API clients than Phoscon (to rule out browser cache issues)? |
@ParanoidiordnA Please change the issue name to something more suited to describe what you want to report. It should allow the devs as well as other users to find and follow what's discussed here. Thanks! 🙂 |
Done :) |
I have same "issue" with LTW010 (I have only one) (the 3 LCT015 's are OK) . Both seem to be on 1.101.2 Firmware. Environment It dosent botther me to much since IRL with the switches and the sensors, all seem to work OK But software side , Phoscon App (web and mobile) and Homebridge (also google home) report this Light ON (when it OFF IRL) : When I switching it OFF in this software's (Bulb is already OFF IRL), the attributes of the On/Off cluster in the GUI stay the same as the screenshoot from ParanoidiordnA above. Then, 15sec or so after, those software report this light ON again (The Light stay OFF IRL) When switching if ON/OFF with real switch/sensor, those attributes of the On/Off cluster in the GUI change to the right stance. In 2.24.3 (and bellow) I never have this EDIT: Debug log when trying to play around (OFF/ON Software side and reading ON/OFF & Hue Effects Attributes) |
The "good" new: I can reproduce the issue, for an LTW010 and for a LTW012 (ZLL white ambiance). But not for the LCT015 (ZLL white and color ambiance, gamut C). All three have the same firmware image, 0x010C, but different DDFs. Looking at the diff between those DDFs. I don't see anything that could cause the different behaviour. Looking at the deCONZ log, when parsing the 0xFC03/0x0002 attribute for the white ambiance:
So the FC03_state.js script returns
|
I haven't checked in detail, but is this right?
|
Hmm not sure where this comes frrom, the script doesn't set |
Missed that line before. Checked the log: it appears for the white ambiance lights, but not for the white and color ambiance. Not with other value ( |
Feeling a bit experimental, I hacked the DDF files, so LTW010 is exposed by Find the 10 differences in DDF:
|
I noticed |
What confuses me is that why doesn't the script actually set the 'state/on' value by something like |
Normally, the DDF wrapper sets the item to the script's return value, doesn't it? EDIT No, it doesn't - I assumed that because of #7576. Apparently, that's caused by the same or similar magic as this issue? |
No, this is only used for "write" function to get a value to write (but not actually set it)
|
This is higher-level magic to me, but I now have a version of the DDF and the JS that seems to work for all Hue lights. Will create a PR shortly. |
Add `state/effect`, as these lights do support `candle`. Also miraculously solves dresden-elektronik#7579.
Revert changes to handling `state/on` from dresden-elektronik#7576, solving dresden-elektronik#7579.
Oh, joy, a new value for mode. I think it's a bitmap, but that's for another time. Also note that you cannot set |
Add support for new mode (on, bri, ct, effect), see dresden-elektronik#7579.
That's great. |
@ParanoidiordnA I'm building a test version with the new fix, would be cool if you can try it in your setup. Do you have a 32-bit or 64-bit Raspbian? |
32-bit armhf test version with the applied fix can be found here http://deconz.dresden-elektronik.de/raspbian/beta/deconz_2.25.3_07714f-debian_armhf.deb |
It's a 64bit Raspbian i'm using. |
Ok I'm compiling a version for 64-bit takes a sec. http://deconz.dresden-elektronik.de/debian/beta/deconz_2.25.3_07714f-debian_arm64.deb |
Same behaviour on my LTW001 and LTW010 lamps indeed. |
That fixed it for me. Thanks you |
Bug fixed. Works like a charm :-) |
LTW010@FW1.101.2 and 64bit arm works again. thank you |
LTW012@FW1.88.1 and 32bit armhf works again. thank you |
Thanks everyone for testing, big 👍 |
Does the issue really belong here?
Is there already an existing issue for this?
Describe the bug
After Updating from version 2.24.3 to version 2.25.3 i experienced that two (of two) Signify LTW012 (FW 1.108.7) light bulbs appear in phoscon as ON even though they aren't. Turning the devices OFF in phoscon doesn't help. After a short time phoscon shows the devices as ON again.
Reverting back to 2.24.3 brings back normal behavior of the devices.
Steps to reproduce the behavior
Connect a Signify LTW012 to phoscon, use deconz 2.25.3, wait for a few seconds
Expected behavior
Same behavior of the devices as in deconz 2.24.3
Screenshots
No response
Environment
deCONZ Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: