YahueV2 (Yet another Hue app, using Hue API v2)

[Sjakie 156]

ok will try.

Why 429 I can't understand yesterday I modified almost all my light (90) excecution id,....: value = ... instead off

id:on

id:value = ...

Seems to me I give now 505 of the command and before only one time 429.

If the 429 happens in the evening I could understand because much more light are switching on/off in the morning only a few.

I deleted around 100 rlighting rules 

 

Edited May 11 by Sjakie
delete

[Sjakie 156]

Jan,

V0.2.49 let my bedr- and guest room light flood the system back on v0.2.47  0.2.45

It has probally something to do with the Hue dimmer?

Sorry was something wrong added this morning is corrected and going back to v0.2.49

Edited May 11 by Sjakie
typo

[Sankotronic 2,370]

Hi Jan,

 

question:

 

Is it possible to send combined command to Yahue like:

Please login or register to see this code.

and if not, then I guess each separate command set to Yahue is immediately sent to HUE bridge?

 

I'm asking because my solution for HC2 is accepting complete set of actions at once and then sends them in a single command to HUE bridge or when necessary in multiple commands, but as less as possible depending on HUE CLIP API v2 possibilities.

[jgab 2,647]

1 hour ago, Sankotronic said:

Hi Jan,

 

question:

 

Is it possible to send combined command to Yahue like:

Please login or register to see this code.

and if not, then I guess each separate command set to Yahue is immediately sent to HUE bridge?

 

I'm asking because my solution for HC2 is accepting complete set of actions at once and then sends them in a single command to HUE bridge or when necessary in multiple commands, but as less as possible depending on HUE CLIP API v2 possibilities.

So there is a rawCmd that can be used to send raw clip data to the Hub (targeting a device)
Ex.

Please login or register to see this code.

Yahue tries to be smart when sending multiple commands, so that's also a possibility.

[Sjakie 156]

Jan,

I found the cause of the 429 error.

I created a light show:

Please login or register to see this code.

it starts and don't switch from sene to the next scene.

At night it should stop but it continues. Is this to fix?

I use some similar idea in my hall it show, the color of the lights represents the state of my arming. It don't follow the reality.

Thanks in advance

 

[jgab 2,647]

The new/recent firmwares for the old and the new Philips Hue hub has set a rate limit on number of requests/second.

The old firmwares also had practical limits but it was possible to "push" them harder.

This means that we get HTTP 429 Too Many Requests

if we send commands too fast to the Hub.

 

Initially, Yahue was focused on rooms/zones as a way to send command efficiently to groups of lights, trying to avoid 429.

It's possible to still send commands too fast, ex. we have 5 zones and turn them on at the same time, or we send many commands to a single zone rapidly.

 

What are the limits? typically 10 requests/second. 

In hue v2 protocol, we open an http 1.1 eventstream to the hub that allow us to get state changes from the hub in realtime without polling. But for sending commands we need to make individual HTTP GET and PUT requests.
If we had also been forced to poll the hub for events we would have had a hard time not running into 429.

Yahue tries to be smart about commands sent, but in general it's impossible to avoid sending commands too fast.

One approach is to queue all commands and send them with the proper delays, but that can create strange/unwanted effects as all commands becomes "visible". Ex. setting color and then dimming up.
Better then to do it all in one command to the hub, but the Fibaro lights don't have these combined commands in their API, making Hue lights special in what commands we can send - which is unfortunate, but maybe necessary.

 

For Yahue we can send these combined commands using "rawCmd".
Ex, fibaro.call(id, "rawCmd", {on={on=true}, dimming={brightness=50}, dynamics={duration=3000}})

[Sjakie 156]

Jan, what is wrong in my settings up?

Same behavior for room and zone. I tested 505 & 591

It will switch on with previous setting and when it should be one light red it don' do it

Please login or register to see this code.

In debug

Please login or register to see this code.

 

Edited May 14 by Sjakie

[jgab 2,647]

Fix:

Please login or register to see this code.

The two key changes:

1. wait(2) before the dim — lets the scene apply completely (scene events arrive ~2s after recall)

2. setDim(20) instead of setValue(20) — changes brightness without sending on:true, so lamp3 stays off as the scene intended
 

The cleanest solution though: if the scene is already configured with 20% brightness in the Hue app, drop the setDim call entirely and just do turnOn("Warm"). Scenes store per-light brightness — let the scene own it.

General rule is to not mix scenes and individual commands to lights. Toggle between scenes...
Of course, sometimes you may want to adjust brightness of a scene and turn on/off.

Edited May 14 by jgab

[Sjakie 156]

Jan ok will change.

To avoid flikkering of the light all my scenes are on 1% si now I understand it was a wrong choice?

Will set in Hue app 40-50%  100%  I will use setDim.

So only switch on must use SetValue.

It will reduce traffic between HC3 and Hue bridge

Thanks for this valuable advice

Edited May 14 by Sjakie
set Hue app 100%

[Sjakie 156]

Jan,

The problem seems to be at nicht when appartement goes to sleep.

All off commands are replaced with :value = 0.

Hue app brightness set for the most common values so setDim or setValue are often removed.

I grouped the living part together in one zone (was 3), 22 lights.>>>>> does't work!

There is only a warning but I can't trace the light? Is it possible you can add the name or id in the warning message?

Please login or register to see this code.

 

Please login or register to see this code.

It don't reconnect only if I restart Hue bridge!!!!!!!!

Can you give me something if this error occur to restart Hue bridge?

 

Please login or register to see this code.

 

 

Thanks again for this beautifull QA lights are smooth changing!

Edited May 16 by Sjakie
No reconnect!!!!

[jgab 2,647]

56 minutes ago, Sjakie said:

What I don't understand is that with old Yahue / Hue bridge I never had any problem with a remark that there where much more commands given for each seperate room or even lights.

The new Yahue is the same code base as the new, just added individual lights.

The "problems" we have is because Philips have added API rate limits in the latest firmware (for the new and old hub).

The old Yahue had the same problem but it was not as visible as we could only manipulate rooms/zones in a limited way.

[Sankotronic 2,370]

Just out of curiosity I have made a following test:

 

HC3 - Yahue latest version just listening to the bridge

HC2 - HUE2 Home zone that includes 28 lights and plugs grouped in 10 rooms.

iPhone with UHE app running.

 

ACTION

On HC2 using my virtual device that controls Home zone (28 lights) activated HUE scene "Bright". VD activated scene that actually sends command(s) to HUE bridge.

Next action was to turn off all lights in Home zone.

 

RESULT

All 28 bulbs turned on in a second.

Yahue received all events with no warnings or errors and show proper state for all lights that are grouped in 10 rooms.

iPhone app also changed state of those rooms/zones

On HC2 scene that send this command to bridge didn't report any warnings or errors. Next run of the same scene properly get state of all lights and show it on my virtual devices.

Same successful result I get when lights were turned off.

 

NOTE - my HC2 HUE2 system refreshes lights state by pulling complete set with the scene and then updating all virtual devices with code from HUE2 Preview main loop. This is done every 10 seconds. This never failed even when HUE app was running on two Phones at the same time.

 

I know that HC3 with its devices (color controller, multilevel switch and binary switch) gives different approach to the light control than virtual devices on HC2, but I see it as an improvement, so I guess it all falls down to the code.

 

@Sjakie,

 

What are you using to send commands to Yahue, is it Event runner? Isn't Event runner something that still needs to be programmed. by users (write all kinds of rules) and need to know how?

 

@jgab

 

My solution for HC2 never encountered such problems, but I guess this is because I never send individual commands to the HUE bridge, I always use HUE scenes either static or dynamic and in some cases effects. To be honest I do not remember when we used HUE app or even Fibaro Center app to control our lights. Just in rare cases when needed we use remote buttons.

 

I guess you are currently busy and have no time to do what I reported and requested for Yahue. That is OK. Yubii UHAS must be simple to install and easy to configure by users. Yahue in its current version is missing few things to fulfill that condition as I mentioned in my request.

 

[Sjakie 156]

@Sankotronic

I use Eventrunner6 for all light commands.

In Hue app I have rooms and zones. HC3 switch rooms and zones.

With previous system off Jgab no problems at all.

Jgab his Eventrunner6 and Yahue works fine my problem is that for the kitchen lights I have Rexense (Zigbee).

This f.... light is pulling my leggi! It's because it was very expensive around 800, euro it is still in others I should have replaced it with HUE.

If it will pull even harder than the last days are counted.

So today's problem is I reorganized my zones in Hue app and by accident changed the color setting of this light and then you are lost. You must try different settings before Hue and HC3 are synchrome.

 

@jgab -1-how to retrieve present color setting?

-2-communication error how to tackle

Please login or register to see this code.

 

[Sjakie 156]

@Jgab, just a few minutes ago I saw in debug the connection warning so I corrected what triggered just before that error apear.

The lines in debug are too manny to see what is executed just before the warning.

Can you create a kind of post to another QA with fa 20 lines before the warning apear?

 

[jgab 2,647]

On 5/16/2026 at 5:22 PM, Sjakie said:

@Jgab, just a few minutes ago I saw in debug the connection warning so I corrected what triggered just before that error apear.

The lines in debug are too manny to see what is executed just before the warning.

Can you create a kind of post to another QA with fa 20 lines before the warning apear?

 

That's non-trivial...

[jgab 2,647]

On 4/27/2026 at 11:23 AM, Sankotronic said:

Hi Jan,

 

thanks for the tip for sseWatchdog variable. Just to be sure, I add this variable to Yahue variable tab?

 

I continue to test Yahue.

It seems that adding drop down list and button on the same row looks nice only in the web GUI.

This is how it looks on my iPad (added red box around button):

Please login or register to see this spoiler.

v0.2.55
1. Added effects button (don't check if light actually supports it, just need to be color)
2. Translation for "en", "pl", "hr", "de", "nl", "fr". Set with quickvar 'language'. defaults to english
3. Sets manufacturer and mode
4. ALC can read 'colormode' from light QA. The value is always a string: "xy", "ct", "scene:<scene_name>", "effect:<effect_name>", or "" (effect stopped).

[Sankotronic 2,370]

Hi @jgab,

 

This morning I upgraded Yahue to the latest version and I must say I'm impressed. Unfortunately I do not have enough time to test it because soon I'm leaving home for my work, but will definitely do comprehensive test when I'm back home in 6 weeks.

 

Thank you for your excellent work and contribution! 🙏

[XTeK 15]

Good thing I had a backup because all the lights were removed and added back. I would have had to change all the scene IDs.

[jgab 2,647]

18 minutes ago, XTeK said:

Good thing I had a backup because all the lights were removed and added back. I would have had to change all the scene IDs.

Yes, every time the UI changes (lights got effect buttons and better popup placement), the child QA is recreated to get the new UI.
Hopefully it will not happen anymore...

[XTeK 15]

Everything's fine, but I have too many scenes to do it all at once. Maybe this weekend.

Thanks for taking this on. You're doing a lot of good work.