Gledopto LED Controller: homebridge-deconz v0.1.19

[darkmc80]

Problems with Gledopto LED Controller GL-C-008P/RGBCCT Pro. With v0.1.19, control via homebridge, HomeKit and even phoscon does not work. Downgrading to v0.1.18 brings back functionality again. (Some releases ago, there was a problem with Gledopto, but update brought functionality again.) Raspberry Pi4, 8Gb, Raspbian 6.1.21-v7+ #1642, Homebridge v1.6.1, node.js v18.16.1., Conbee/Phoscon: 2.22.02 / 26400500

thanks a lot for your effort developing this plugin!

Kind regards

[ebaauw]

If it doesn’t work in Phoscon, it’s likely an issue with deCONZ, not with Homebridge deCONZ.

if you think there’s an issue with Homebridge deCONZ, please describe what is not working: what you’re trying to do, what happens, and what you expect to happen. Also please attach the debug dump file, run Homebridge in DEBUG mode, set LogLevel for the controller to 2 and capture and attach a debug log file.

[darkmc80]

Hi Erik

The strange thing is, that it works again with downgrading to homebridge-deconz v0.1.18. There was no deconz update in the last 14days. That’s why I’m bringing this issue here.

Switching light on and off does not work. Dimming and white color testing was not possible, because switching on and off was not possible.

I managed to switch on Debug mode on home bridge, but...

I try hard to set LogLevel for the controller to 2, even with google I don’t have a clue, how to do it… sorry

Jan

Am 09.07.2023 um 12:21 schrieb Erik Baauw @.***>:

If it doesn’t work in Phoscon, it’s likely an issue with deCONZ, not with Homebridge deCONZ.

if you think there’s an issue with Homebridge deCONZ, please describe what is not working: what you’re trying to do, what happens, and what you expect to happen. Also please attach the debug dump file, run Homebridge in DEBUG mode, set LogLevel for the controller to 2 and capture and attach a debug log file.

— Reply to this email directly, view it on GitHub https://github.com/ebaauw/homebridge-deconz/issues/150#issuecomment-1627671151, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIGFWWDIWTQL666VY36GDNDXPKA33ANCNFSM6AAAAAA2DMVJOE. You are receiving this because you authored the thread.

[MSL-DA]

I try hard to set LogLevel for the controller to 2, even with google I don’t have a clue, how to do it… sorry

https://github.com/ebaauw/homebridge-deconz/wiki/Dynamic-Configuration#configuration-api

The configuration API of Homebridge deCONZ responds to local http requests to a random port. On startup, Homebridge deCONZ issues a log message with this port

Then

https://github.com/ebaauw/homebridge-deconz/wiki/Dynamic-Configuration#example-3

[darkmc80]

thanks a lot for the input!

so then, hopefully I have enabled logLevel 2 correctly... the problem occurs with /lights/4 and also /lights/6

hopefully this helps

Thanks a lot

Jan

230709_Homebridge Data.txt

[ebaauw]

As far as I can tell, Homerbridge deCONZ is working as it's supposed to. The issue seems to be the connectivity between deCONZ and the light (which would explain why you cannot control the light from Phoscon either).

You're setting the light off, from HomeKit:

[09/07/2023,    16:04:10]   [Conbee] Fernsehbeleuchtung: On: changed to false (from true)

Homebridge deCONZ sends the command to deCONZ to turn the light off:

[09/07/2023,    16:04:10]   "[Conbee] Fernsehbeleuchtung: PUT /lights/4/state {""on"":false}"
[09/07/2023,    16:04:10]   "[Conbee] Conbee-GW: request 17: PUT /lights/4/state {""on"":false}"
[09/07/2023,    16:04:10]   [Conbee] Conbee-GW: request 17: 200 OK

But deCONZ returns an API error, because the light is not (yet) reachable:

[09/07/2023,    16:04:10]   "[Conbee] Conbee-GW: request 17: PUT /lights/4/state {""on"":false}"
[09/07/2023,    16:04:10]   [Conbee] Conbee-GW: warning: request 17: /lights/4/state: api error 202: resource, /lights/4/state, is not modifiable. Device is not reachable.

On second attempt, deCONZ accepts the command, and reports back that the light state has changed:

[09/07/2023,    16:05:22]   [Conbee] Fernsehbeleuchtung: On: changed to false (from true)
[09/07/2023,    16:05:22]   "[Conbee] Fernsehbeleuchtung: PUT /lights/4/state {""on"":false}"
[09/07/2023,    16:05:22]   "[Conbee] Conbee-GW: request 28: PUT /lights/4/state {""on"":false}"
[09/07/2023,    16:05:22]   [Conbee] Conbee-GW: request 28: 200 OK

This is confirmed when Homebridge deCONZ next polls deCONZ:

[09/07/2023,    16:05:26]   "[Conbee] Fernseh Stripe: /lights/4: polled: {""capabilities"":{""alerts"":[""none"",""select"",""lselect""],""color"":{""ct"":{""max"":65279,""min"":0},""effects"":[""none"",""colorloop""],""modes"":[""ct"",""effect"",""hs"",""xy""]}},""colorcapabilities"":31,""config"":{""groups"":[""0"",""6""]},""ctmax"":65279,""ctmin"":0,""etag"":""2128829f95a1ca08af08bdecd0edb26b"",""hascolor"":true,""lastannounced"":""2023-07-09T14:04:38Z"",""lastseen"":""2023-07-09T14:04Z"",""manufacturername"":""GLEDOPTO"",""modelid"":""GLEDOPTO"",""name"":""Fernseh Stripe"",""state"":{""alert"":""none"",""bri"":25,""colormode"":""ct"",""ct"":580,""effect"":""none"",""hue"":0,""on"":false,""reachable"":true,""sat"":0,""xy"":[0.3125,0.3333]},""swversion"":""1.0.2"",""type"":""Extended color light"",""uniqueid"":""00:12:4b:00:19:e8:fb:5d-0b""}"

But then, deCONZ reports the light as unreachable, which Homebridge deCONZ reflects in Status Fault.

[09/07/2023,    16:06:27]   "[Conbee] Fernseh Stripe: /lights/4: changed: {""state"":{""alert"":""none"",""bri"":25,""colormode"":""ct"",""ct"":580,""effect"":""none"",""hue"":0,""on"":false,""reachable"":false,""sat"":0,""xy"":[0.3125,0.3333]}}"
[09/07/2023,    16:06:27]   [Conbee] Fernsehbeleuchtung: Status Fault: set to 1 (from 0)

[darkmc80]

Ok, thanks a lot for your investigation! So then, I’m going to search @ deConz or Gledopto!

Thank you Jan

[darkmc80]

Mistakenly suspected an error in the plugin. It seems that everything is working as intended.