New pimatic plugin for integration with Philips Hue

---

@djmvt said:

Ok for now I’ll leave my installation as it is, for some reason when I try to update to the latest hue-zll my pimatic goes berzerk with “number of api calls exceeded” errors.

Ok, that sounds like the queue that is overflowing. Did you install the master branch or the global_polling branch?

It appears that too many requests for the Hue API are being sent at once, probably due to your rules setup. Perhaps I should make the maximum queue length configurable, so you can simply increase it if it doesn’t suffice.

Will wait for the next official update.

Heh, I understand. Alternatively, could you send me your config.json file (with irrelevant parts like passwords removed)? That might allow me to replicate your issue. I’ll need information to debug this as well - otherwise there will either be no new release or one which has the issues you’re currently seeing. Thanks!

Tried installing the global_polling branch but this also gave me errors, same as the master branch. Must be something in my setup.
Only way to get the plugin working for now is to install the previous test with npm install git+https://github.com/markbergsma/pimatic-hue-zll.git#issue_picker_overload

@djmvt said:

Tried installing the global_polling branch but this also gave me errors, same as the master branch. Must be something in my setup.
Only way to get the plugin working for now is to install the previous test with npm install git+https://github.com/markbergsma/pimatic-hue-zll.git#issue_picker_overload

I just pushed a commit to both branches that introduces a plugin configuration option “hueApiQueueMaxLength”. Just increase the (auto calculated default) value mentioned in the error (double it maybe) until you no longer get the errors. If you need to increase it a lot, that’s not a healthy sign.

Don’t know why or what is happening when I install the master or global_polling branch but this is an exerpt of what is going on when I monitor in linux:

17:32:54.293 [pimatic-mobile-frontend] rendering theme: graphite/water
17:33:01.148 [pimatic-mobile-frontend] rendering theme finished
17:33:47.231 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded
17:33:47.246 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded
17:33:47.272 [pimatic] rule eettafel-uit error executing an action: Hue API maximum queue length (30) exceeded
17:33:55.646 [pimatic] Error on evaluation of rule condition of rule eettafel-uit: Hue API maximum queue length (30) exceeded
17:33:55.664 [pimatic] rule eettafel-uit error executing an action: Hue API maximum queue length (30) exceeded
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
17:34:13.858 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded
17:34:13.870 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded
17:34:13.895 [pimatic] rule eettafel-aan error executing an action: Hue API maximum queue length (30) exceeded
17:34:13.990 [pimatic] Error on evaluation of rule condition of rule eettafel-aan: Hue API maximum queue length (30) exceeded
17:34:14.007 [pimatic] rule eettafel-aan error executing an action: Hue API maximum queue length (30) exceeded
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
17:34:20.410 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded
17:34:20.422 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded
17:34:20.444 [pimatic] rule eettafel-uit error executing an action: Hue API maximum queue length (30) exceeded
17:34:20.589 [pimatic] Error on evaluation of rule condition of rule eettafel-uit: Hue API maximum queue length (30) exceeded
17:34:20.606 [pimatic] rule eettafel-uit error executing an action: Hue API maximum queue length (30) exceeded
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
Unhandled rejection Error: Hue API maximum queue length (30) exceeded
at Error (<anonymous>)
at HueQueue.pushTask (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:33:31)
at BaseHueLight.pollAllLights (/home/pi/pimatic-app/node_modules/pimatic-hue-zll/hue-zll.coffee:127:26)
at wrapper [as _onTimeout] (timers.js:252:14)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

This goes on and on. Tried 30, 60 and even 100. It just takes a little longer to start the errors but it is not working. None of the commands seem to reach the bridge and lights stay unresponsive.
When going back to this:
npm install git+https://github.com/markbergsma/pimatic-hue-zll.git#issue_picker_overload

Everything is working again.

No clue what I am doing wrong here…

@djmvt said:

Don’t know why or what is happening when I install the master or global_polling branch but this is an exerpt of what is going on when I monitor in linux:

17:32:54.293 [pimatic-mobile-frontend] rendering theme: graphite/water
17:33:01.148 [pimatic-mobile-frontend] rendering theme finished
17:33:47.231 [pimatic-hue-zll] Hue API request failed: Hue API maximum queue length (30) exceeded

[snip]

This goes on and on. Tried 30, 60 and even 100. It just takes a little longer to start the errors but it is not working. None of the commands seem to reach the bridge and lights stay unresponsive.
When going back to this:
npm install git+https://github.com/markbergsma/pimatic-hue-zll.git#issue_picker_overload

Everything is working again.

Strange. With this broken branch global_polling, does pimatic-hue-zll still report the Hue API / bridge version information at startup, before the excerpt above? That would prove it’s able to connect to the bridge at all (and doesn’t use the queue).

Connected to bridge Philips hue, API version 1.11.0, software 01030262

These errors you pasted are what you get if it can’t reach the bridge at all (e.g. if you configure the wrong IP or something), but then why would it work with an older branch.

No clue what I am doing wrong here…

More likely I’m doing something wrong, just need to figure out what it is.

Thanks, much appreciated!

Got a log from the moment I installed the global_polling branch untill it goes in error mode, can I send this to you @markbergsma?

@djmvt
You can use pastebin.com for posting larger code.

@leader21 said:

You can use pastebin.com for posting larger code.

I’ve since received his log by private email, and we’re debugging it there.

I’m very curious in the mean time if any others are seeing similar problems.

Have sent both my config.json and a log from my pimatic when starting to Mark via private mail.

Tried already several suggestions (removing homeduino and smartmeter, changed max api calls and hue concurrency settings) but nothing seems to work for now.

@djmvt said:

Have sent both my config.json and a log from my pimatic when starting to Mark via private mail.

Tried already several suggestions (removing homeduino and smartmeter, changed max api calls and hue concurrency settings) but nothing seems to work for now.

Found it I think. I wasn’t calling the reject() callback from the Queue, so if a Hue API request was failing (e.g. due to a light non existing or any other reason) it was silently blocking the queue without error message until timeout.

The global_polling branch now has a fix for that issue.

Thanks for testing

I was wondering: could this also be a reason why one of my lights went blinking last night? As far as I noticed it went blinking (switching between 100% and 30% or so) for about 10 seconds, 3 times last night. Never seen that behaviour before.
Could this have been the bridge reporting an error through a blinking bulb?

Anyway installed the global polling branch: looks like it’s working!
Do get some errors during startup but after that everything seems fine.
Going to test it out in the next days.

Thanks! 👍

@djmvt said:

I was wondering: could this also be a reason why one of my lights went blinking last night? As far as I noticed it went blinking (switching between 100% and 30% or so) for about 10 seconds, 3 times last night. Never seen that behaviour before.
Could this have been the bridge reporting an error through a blinking bulb?

I highly doubt it, the Hue bridge doesn’t alert for errors using the light itself that I’m aware of. Perhaps you had Pimatic trigger a rule doing that? If so, you should be able to see that in the logs around that time.

@markbergsma no there was no rule involving that light. Also had an update of the bridge fw so maybe something went wrong there. Didn’t happen anymore last night.

I just released pimatic-hue-zll version 0.1.1 and published it to npm. It should improve/fix most issues people have reported here so far.

Changes:

• Fix set ct of rules with the for <X> <time> suffix
• Add CSS rules for better layout on small screen/mobile devices (thanks to Wiebe Nieuwenhuis)
• Catch errors from UI input control methods
• Send only one Pimatic REST API request at a time from the color picker
• Improve behaviour of the color picker
• Implement polling for all lights and all groups in a single Hue API request
• Send all Hue API requests through a FIFO queue with configurable concurrency and maximum queue length

I don’t know if it’s a bug but when a light is off and I do something like:

set color of woonkamer-bank to hue 75% sat 95% for 10s

The light goes back to the color before but remains on.

@sweebee said:

I don’t know if it’s a bug but when a light is off and I do something like:

set color of woonkamer-bank to hue 75% sat 95% for 10s

The light goes back to the color before but remains on.

Yes, I suppose that’s a bug. It’s caused by the implicit turning on when you change any other light attribute.

And I guess if e.g. color temp was used before the “for” rule, it may also not restore to the correct ct.

There are a couple of ways to fix it, will experiment a bit later.

Getting a lot of “Client error: Uncaught TypeError: Cannot read property ‘toggleClass’ of undefined” errors in the new update.
But otherwise it is working fine so far.

When I’m controlling 4 colored bulbs at one time i get:

error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: Error on evaluation of rule condition of rule scene-normaal: Hue API maximum queue length (12) exceeded
16:22:59error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic]: Error on evaluation of rule condition of rule scene-normaal: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic]: rule scene-normaal error executing an action: Hue API maximum queue length (12) exceeded
16:22:58error [pimatic-hue-zll]: Hue API request failed: Hue API maximum queue length (12) exceeded
16:22:58

rule:

set ct of woonkamer-schilderij to 2700K and dim woonkamer-schilderij to 80% and set ct of woonkamer-ornamenten to 2700K and dim woonkamer-ornamenten to 80% and set ct of woonkamer-bank to 2700K and dim woonkamer-bank to 80% and set ct of woonkamer-zithoek to 2700K and dim woonkamer-zithoek to 80% and dim Wandkast to 30% and $scene = 0

@sweebee said:

When I’m controlling 4 colored bulbs at one time i get:

Best increase the maximum queue length then.

set ct of woonkamer-schilderij to 2700K and dim woonkamer-schilderij to 80% and set ct of woonkamer-ornamenten to 2700K and dim woonkamer-ornamenten to 80% and set ct of woonkamer-bank to 2700K and dim woonkamer-bank to 80% and set ct of woonkamer-zithoek to 2700K and dim woonkamer-zithoek to 80% and dim Wandkast to 30% and $scene = 0

Also if you want to set multiple hue lights to the exact same value, it’s more efficient to use a light group.

@markbergsma Yea also thought about that. Create some more groups, also easier to make scenes.