Skip to content
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

Gledopto ct colormode stopped working #2840

Closed
Jolle666 opened this issue May 28, 2020 · 8 comments
Closed

Gledopto ct colormode stopped working #2840

Jolle666 opened this issue May 28, 2020 · 8 comments

Comments

@Jolle666
Copy link

Hi,

Since deCONZ v2.05.76 ct colormode stopped working with my Gledopto lights (GL-C-006 and GL-C-008). API error in Node-RED/Home Assistant. 2.05.75 is fine.

Maybe it's related to #2798?

Thanks!

@SwoopX
Copy link
Collaborator

SwoopX commented May 28, 2020

Update to .77, there's a fix for ct as I recall

@ebaauw
Copy link
Collaborator

ebaauw commented May 28, 2020

Only for IKEA. What type of GLEDOPTOs are these? Could you list the resources and screenshots of the Color Control cluster (after reading the attributes)?

@Jolle666
Copy link
Author

The Gledopto GL-C-006 is the WW/CW LED controller (firmware 1.0.6). The GL-C-008 is the RGB+CCT LED controller (firmware 2.0.0).

I run Home Assistant with the Phoscon app on a RPI4 with Conbee II. I'm sorry, but not sure where to find resources and Color Control cluster.

@ebaauw
Copy link
Collaborator

ebaauw commented May 28, 2020

Hm, both should expose state.ct and work?! Did you happen to try .77?

What API error do you see? Can you find out what API requests are sent?

@ebaauw
Copy link
Collaborator

ebaauw commented May 28, 2020

Double-checked the GL-C-008: it's working in 2.05.77:

$ ph get /lights/5
{
  "ctmax": 65535,
  "ctmin": 0,
  "etag": "34b94379dede7d32b61d6d6d480b7b11",
  "hascolor": true,
  "lastseen": "2020-05-28T19:55:36.214",
  "manufacturername": "GLEDOPTO",
  "modelid": "GL-C-008",
  "name": "GL-C-008",
  "state": {
    "alert": "none",
    "bri": 1,
    "colormode": "hs",
    "ct": 153,
    "effect": "none",
    "hue": 0,
    "on": true,
    "reachable": true,
    "sat": 0,
    "xy": [
      0.3125,
      0.3333
    ]
  },
  "swversion": "1.0.6",
  "type": "Extended color light",
  "uniqueid": "00:12:4b:00:1b:91:ec:83-0b"
}
$ ph put -v /lights/5/state '{"ct": 500}'
{
  "ct": 500
}
$ ph put -v /lights/5/state '{"ct": 153}'
{
  "ct": 153
}

@Jolle666
Copy link
Author

@ebaauw thank you so much.

Just testet once more. This is the JSON in Node-RED:
image

With 2.05.75 the LED controller is working and with no error in Node-RED:
image

With 2.05.77 the LED controller is not working and I get this API error in Node-RED:
image
with this debug message:
image

This is the info in the Phoscon app:
image

@ebaauw
Copy link
Collaborator

ebaauw commented May 28, 2020

Ah OK: you cannot set colormode: it's a read-only attribute. It's set automatically when you set the colour (temperature) trough xy, hue and sat (hs), or ct.

It has never worked, but was silently ignored. I fixed the handling of errors for a PUT of the light state, so you're only seeing the error since v2.05.76.

@Jolle666
Copy link
Author

@ebaauw Ah, now it all makes sense and is working perfect. Thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants