Not able to control GLEDOPTO devices any longer

[saxn-paule]

Today I updated to the .57 firmware. Its not possible to control GLEDOPTO devices via Phoscon any longer.

The controllers are shown and could be added to groups but the sliders don't appear.

EDIT: After a little time the sliders appear again. But I'm not able to turn the light on. No reaction on changing the dimlevel or clicking on/off the group.

It's a GLEDOPTO 009

[manup]

I have only the GLEDOPTO RGBW version with SMILB brand here for testing, this one works fine.

Version: 1.0.2 Datecode: 20131206

You may try to force Phoscon App cache refresh by appending some random search query in the URL bar.

http://<gateway-ip-address>/pwa/index.html?12345

[saxn-paule]

Still no change. If I click the lights icon of a group, the dim slider jumps to ~50% but the lights stay off.

Do you live in DD? Then I could give you a 009 for testing.

[saxn-paule]

007 and 008 still work like before.

[manup]

Test devices are always welcome but for now a few more details about the device should help as well.

Can you please provide some screenshots as described here:

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support

The GLEDOPTO controllers seem to have a quite different endpoints and clusters between versions.

The issue with missing modelid and manufacturername is now fixed and will be available in 2.05.58. It might be related to this issue here, since the Phoscon App relies on modelid in some parts.

[saxn-paule]

I use Deconz in headless mode, so I can't make any screenshots. With .55 controlling the 009 was still possible.

I only updated the firmware. Nothing else.

[saxn-paule]

With the .58 version the 009 isn't detected at all any longer:

[saxn-paule]

After restarting the service the 009 is detected again. But with new Ids:

Controlling is still not possible and the second zombie device is also present.

[saxn-paule]

I changed the controller. The new one is controllable again. So, my fault. Sorry.

[manup]

:) I guess these require a bit patience, the missing modelid and manufacturer names are populated in an idle timer which takes a bit. But once set these should be directly available in further restarts.

[saxn-paule]

What I can see now, dimming the device to 0% doesn't turn it off.

The only chance to turn the light off is to click the bulb icon of the group where the light is assigned to. Whats the difference there?

I would like to turn the device off by API too, but it's the same effect. Dimming to 0% doesn't turn it off.

[ebaauw]

As I understand, the GL-C-009 is a Dimmable Light (no colour nor colour temperature)? I suspect it has both a ZLL and a ZHA endpoint doing the same, like the GL-C-007 (RGBW), see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/952. Could you post a screenshot from the deCONZ GUI and the resources as exposed by the REST API?

The GL-C-008 (RGB+CCT) doesn't seem to react turn on nor off on Move to Level (with On/Off), see https://github.com/ebaauw/homebridge-hue/issues/424. If the 009 does the same, PUTting {"bri": 0} wouldn't turn it off. Also, it wouldn't turn on if you PUT {"on": true, "bri": 254}.

[saxn-paule]

Yes it's only a dimmer. I use deconz in headless mode. How could I provide these screenshots?

It turns off, when I use the bulbs icon of a group where the controller is attached to.

It also turns off, if I assign a switch to the group and define a corresponding rule.

[ebaauw]

Yes it's only a dimmer. I use deconz in headless mode. How could I provide these screenshots?

You need to run the GUI for that. I use VNC on a headless Raspberry Pi to share the graphical screen to my Mac.

[saxn-paule]

My pi boots into shell. No gui.

[nagyL]

Some sample images related to my GL-C-009:

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.