[solved]hue-zll error

---

I installed the Philipps hue-zII plugin. Added my spots and now I am getting this error all the time:

error [pimatic-hue-zll]: 153 <= ct <= 500

I use these
Philips Hue LED Lampe 6,5 W GU10

Did the auto discovery selected the wrong type??? I willcheck this later

wrong setting in auto discovery

SOLVED

what did you do to solve it? Got the same problem now.

Changed the device class Everything is set up AS extendedcolorlight. You need to delete the extended by yourself. Maybe an error in the Plugin??

I had the same error today after some serious faults within my intranet and needed restarts of the backbone components (the plugin has been working before since months without any errors now) .

Root couse & how fixed:
Looking into the variables pages (values of hue lights), one of the extended color light has had a ‘ct’ value of ‘null’ which isn’t in the expected range of 153-500 of course (i guess this happenend due to not reachable or somethig like this). BTW: This is the only hue light which is behind a switchable power socket-outlet and therefore most times disconnected from the power-net).

Switching the light on resolved the issue.

it was my problem. i can solved it after read the post. many thanks guys

I think this is fixed in pimatic-hue-zll 0.3.1 which I just published. I wasn’t seeing this with older Hue bridge firmware but it appeared recently when I upgraded my bridge.

After updated my pi with version 0.3.1 I got the following error:

error [pimatic-hue-zll]: Error during poll of all lights Hue API request (attempt 1/9): Object function Object() { [native code] } has no method ‘assign’

Any idea how to fix this?!

I am seeing errors not as much as before the 0.3.1 update, but I still experience the following:

I use multiple types of hue bulbs, and I am not sure which one is causing these errors. Is there a way to find out? Or do you have a clue what is causing these errors?

The error came Form the unsupported light temperature level from the bulbs. There are 2 different types, 1 is the only color and the second is the extended color where you can choose also the light Temperaturen level. To avoid this check all your bulbs/led stripes and choose your right type in the configuration manually.
Or if your bridge was switched off while pimatic was running simply restart pimatic while your bridge is on.

Regards

Thnx @temp for your reaction, but I still have the problem with version 0.8.107 of Pimatic. I’m using Philips Hue White Ambiance leds.

The error occurs after latest update. Therefore no problem with my configuration:

}
  "plugin": "hue-zll",
  "host": "192.168.1.1",
  "username": "blablablablablablablablablablablabla"
},

"devices": [
{
  "id": "hue_color",
  "class": "HueZLLColorTempLight",
  "hueId": 1,
  "name": "Dressoir"
},

You definitley should update to v0.9.
This may solve your issue. V0.8 is no longer supported.

Hi,
I have a very strange phanomaen here with the zll-plugin:
I try to read-out the status (are they on or off) of one (or more) hue-lights which are integrated via the plugin to handle rules.
The attribute of “$hue_color-light.state” is a boolean (true/false) and visible in the variables page, but all attempts to read out this via rules are not working.

I tried different variants;

when state of hue_color-light-8 is on then..
doesn’t work (I guess because the ‘state’ is for switches and as I understand the bulbs class is not derived from this…

2. Defined an expression variable (e.g. $hue-state") which includes “$hue_color-light.state” -> this generates a text-variable including “true” or “false”.
   For 2. I tried a normal rule
   when $hue-state = "true" then..

Funny: nether 2. works! The value is switching from false to true as expected if I switch the bulbs, but the rule doesn’t fire.

I get the impression, that the Hue-attributes are shown and are updated as expected, but pimatic (or the zll-plugin) doesn’t work with them as normal.

This might be a similar issue as here with the milight:
https://forum.pimatic.org/topic/1758/react-on-milight-actions

I also implemented the described workaround from this post with

$licht_kueche.state is increasing //triggers on change to true $licht_kueche.state is decreasing //triggers on change to false $licht_kueche.state > 0 //evaluetes true for true

which works for now. but I like to read out the attributes in a normal way.

Pimatic Version is 0.9.38
pimatic-hue-zll is the actual 0.3.1 (but same behaviour in the release before)

PLS help!

@temp I haven’t had the time to look at it, until now.

The bulb I’m using is a Philips Hue clone (brand = Kudled), which is broadcasting stuff like this:

even when it’s state is ‘off’. Now I’m not sure why, but it’s annoying. Maybe I will spend a couple of bucks and buy me an original Philips bulb