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

[Sankotronic 2,370]

Hi @jgab,

 

it is definitely that event listener stops working after those warnings for missing resources.

You wrote:

23 hours ago, jgab said:

Missing resources are just Hue resources not mapped (yet) by the engine.

Is there a way to find out which device resources are missing and correct it?

Also, why event listener stops on this warnings?

I know that answer is in your code, but it will take me some time to go through it before I can do any changes and suggestions.

[jgab 2,647]

1 hour ago, Sankotronic said:

Hi @jgab,

 

just tested Yahue version 0.2.10 and now works almost like a charm.

It updates properly zones and individual plugs and now even color rings are showing color when light is turned on 👍, but it stopped updating at one point and this was printed in console before that:

Please login or register to see this code.

Don't know if that has anything to do with event listener thou.

 

There is one type of lights that is not properly supported with current version and it is HUE Festavia light string.

I guess you do not own one, so here is this light resource data:

Please login or register to see this spoiler.

I think I narrowed down something that could have killed the event handler... fixed in 0.2.11.

Isn't the festavia mapped as a colorLight? What else is needed?

The standard fibaro status for the child devices are there, value, status, color, temperature etc Read with getValue. What other status would you need?
I can add the Hue properties (vendor, model etc) to the child.

Is a drop down for effects something users use? it feels like a pure automation action...? I let my users only set scenes directly (that can incl effects)... but it's not too difficult to add...
Actually, my users control the lights using the Hue app 99.99% of the time.

Edited April 25 by jgab

[Sankotronic 2,370]

29 minutes ago, jgab said:

I think I narrowed down something that could have killed the event handler... fixed in 0.2.11.

 

Great, will test as soon as I answer your questions.

29 minutes ago, jgab said:

Isn't the festavia mapped as a colorLight? What else is needed?

Yes it is mapped properly, and I guess it is missing drop down menu for HUE scenes since I never added any HUE scenes since I use only effects.

 

31 minutes ago, jgab said:

The standard fibaro status for the child devices are there, value, status, color, temperature etc Reda with getValue. What other status would you need?
I can add the Hue properties (vendor, model etc) to the child.

Yep, no complaints on that.

What I need is that quick app remembers last activated HUE scene, its type 'static' or 'dynamic' and also speed if it is dynamic.

For effects it is a bit easier because it is possible to get last selected effect from the HUE bridge. but drop down with list of available effects and means to activate them will be appreciated.

 

it would be nice to also add button to toggle selected HUE scene between 'static' and 'dynamic' and slider to set speed if it is activated as 'dynamic' only on quick app children for room/zone of course. it is not something that will be used and needed often, but will eliminate need to use original HUE app and also will give means for making solution that does not need users to code in LUA.

 

45 minutes ago, jgab said:

Is a drop down for effects something users use? it feels like a pure automation action...? I let my users only set scenes directly (that can incl effects)... but it's not too difficult to add...
Actually, my users control the lights using the Hue app 99.99% of the time.

Users usually use what is provided to them. I guess that most of the users does not even know that besides HUE scenes there are also effects available because they are not really presented in the HUE original app. What is even more strange is that we can get from HUE bridge what effect was last used, but not HUE scene.

 

What I would add to your already nice solution and only for children that control room/zone:

1. button to toggle selected HUE scene dynamics
2. slider to change speed of dynamic scenes
3. drop down list of available effects

If any scene or effect is activated from the child device to be stored so can be read from other quick apps and used to control those lights.

 

With my solution if I manage to make it again for HC3, users will not need to even use quick apps that much since they will be able to learn system how to control lights at different parts of day and specific states except during learning.

 

Difference between your solutions and mine is that you provide excellent libraries for users which they can use to code their own stuff. Still, to do it properly they still need to read manual how to use those libraries and then learn how to write code in LUA.

 

On the other hand, I like to provide finished product that does not require user to write single line of code, but use solution out of the box with just easy setup using mobile app and sitting comfortably on the sofa. Can't say that they still do not need to read my manuals thou. Installation and user manual for UHAS for HC2 has 515 pages  

 

 

[Sankotronic 2,370]

Hi @jgab,

 

Installed version 0.2.11 and now testing.

I noticed that brightness is always 100% when i set HUE scene "Dimmed" either from HC2 or from Yahue when actually should be 30%.

[Sjakie 156]

Jan,

0.2.11 

Please login or register to see this code.

Did't see this in 0.2.7

[Sankotronic 2,370]

Hi @jgab,

 

I have same error here as @Sjakie.

had to restart Yahue and after restart there was one error:

Please login or register to see this code.

after loading existing child UID. After that error i get series of events for lights.

 

I guess that there must be a reason for:

10 hours ago, jgab said:

Actually, my users control the lights using the Hue app 99.99% of the time.

 

[Sjakie 156]

For me HC3 is checking if lights are on or off if they should be off and are still on >>>retry to switch off and sms to inform me.

So I need that HC3 is also actual in on/off.

Still using old YahueV2 to use this valuable checks for me.

If HUE app light 1% >> HC3 is off!!!

[jgab 2,647]

13 hours ago, Sjakie said:

Jan,

0.2.11 

Please login or register to see this code.

Did't see this in 0.2.7

429 is the bridge having too many requests - I've implemented a backoff mechanism.  

 

10 hours ago, Sankotronic said:

Please login or register to see this code.

 

Yes, this is the standard handling when the bridge closes the connection - retrying (and then it worked...?). I changed it to a warning to not scare people too much  

If HUE app light 1% >> HC3 is off!!!

I think I fixed that now....

v0.2.13 pushed.

[jgab 2,647]

13 hours ago, Sjakie said:

Jan,

0.2.11 

Please login or register to see this code.

Did't see this in 0.2.7

Ok, thinking a bit more on this.
What's happening is that the bridge gets too many commands - it is specified to handle 10/s, but when you start your QA and send out commands to turn off, set value and color, they could easily be more than 10/s I guess. Also if you have the old Hue QA also sending commands to the hub. The old QA was also polling so it's even worse.
A solution is that you make a small wait between commands sent, but that is not so user friendly....

So in, v0.2.14 I have implemented a buffering of commands and I send them out in a pace of max 1 per 100ms. This should minimize the overruns of the bridge.

In general, sending commands to rooms or scenes is more effective as we don't have to send commands for each light...

[Sjakie 156]

Jan,

I use YahueV2 temporary.

v0.2.14

If HUE app light 1% >> HC3 is off!!! >>>

nope still on!

 

 

Edited April 26 by Sjakie

[jgab 2,647]

18 minutes ago, Sjakie said:

Jan,

I use YahueV2 temporary.

v0.2.14

If HUE app light 1% >> HC3 is off!!! >>>

nope still on!

OperatingHUE lights:

HC3

Dimmer

HUE app

HC3 and dimmer are in my rules.

Problem is when someone operates lights by HUE app

Is there a possibility that HC3 can know light is switched on by HUE app?

 

I also have individual lamps and zones and rooms.
If I set the dim level to 1% in the Hue app the corresponding QA on the HC3 is still on.
If I turn the light off the corresponding QA on the HC3 becomes off

If I turn the light on the corresponding QA on the HC3 becomes on.

You are saying that you set the dim level to 1% in the hue app but the HC3 QA show off?
Does it switch from on to off when you set the level to 1% ?

I need more info as I can't reproduce your problem.

[Sjakie 156]

Jan,

I have rooms and zones.

Scenes I have for lights on/off

Brightness in HUE app is standard 1% others the light brightness will jump

Brightness set >> HC3

I don't switch individual lights. If necessary it's in a scene fa in hal I have 6 color spots and 5 scenes who set different color or on/off.

Basic HC3 is doing the job complete.

Manual intervention needed for fine tuning if we need something more bright or less color.

on/off is not a problem you see it in HUE app and HC3.

The problem is if slider HUE app goes minimum HC3 respond in debug light >>off

So my trigger light:isOn does't function anymore because light isOff.

See debug

dim level 0.0 >>> in HUE app 1% see picture.

I hope this is clear?

Please login or register to see this code.

Please login or register to see this image.

/monthly_2026_04/Schermafbeelding2026-04-26om10_01_50.png.fcea1fc1c5130b51fcb3c54c6c803118.png" />

Edited April 26 by Sjakie
light on/off

[jgab 2,647]

47 minutes ago, Sjakie said:

Jan,

I have rooms and zones.

Scenes I have for lights on/off

Brightness in HUE app is standard 1% others the light brightness will jump

Brightness set >> HC3

I don't switch individual lights. If necessary it's in a scene fa in hal I have 6 color spots and 5 scenes who set different color or on/off.

Basic HC3 is doing the job complete.

Manual intervention needed for fine tuning if we need something more bright or less color.

on/off is not a problem you see it in HUE app and HC3.

The problem is if slider HUE app goes minimum HC3 respond in debug light >>off

So my trigger light:isOn does't function anymore because light isOff.

See debug

dim level 0.0 >>> in HUE app 1% see picture.

I hope this is clear?

Please login or register to see this code.

Please login or register to see this link.

Just to be sure, what version of Yahue did you run this log on?

[Sjakie 156]

v0.2.14

[jgab 2,647]

If you update to latest 0.2.18, does it improve?

Note, 0.2.18 recreates roomzone children (you get new deviceIds), because the UI for them has changed.

[Sankotronic 2,370]

Hi @jgab,

 

I installed latest v0.2.14 and was playing with color and colorTemperature on grouped lights for living room and found that is not working.

This is what I get in console if I try to use colorTemperature:

Please login or register to see this code.

 

This is a bit strange since in tools code there is a function to recalculate color temperature to mirek and vice versa.

For colors I do not get any warnings, but clicking on colorwheel soes not change color on the grouped light.

 

Will try now latest version.

[Sjakie 156]

Jan, no change

Please login or register to see this code.

 

[jgab 2,647]

10 minutes ago, Sjakie said:

Jan, no change

Please login or register to see this code.

 

I made a new version 0.2.19 specifically for you  
It has some more debug statements to better see what's happening on your system.
Please upgrade and show me the logs.

[jgab 2,647]

22 minutes ago, Sankotronic said:

Hi @jgab,

 

I installed latest v0.2.14 and was playing with color and colorTemperature on grouped lights for living room and found that is not working.

This is what I get in console if I try to use colorTemperature:

Please login or register to see this code.

 

This is a bit strange since in tools code there is a function to recalculate color temperature to mirek and vice versa.

For colors I do not get any warnings, but clicking on colorwheel soes not change color on the grouped light.

 

Will try now latest version.

QA UI sends kelvin but Hue expects mirek, and I sent kelvin to hue. Fixed that.

The current code skips silently when self.group.rsrc.color is missing on the grouped_light. Hue v2 does expose color on a group only when ≥1 member supports xy color. Could be group has no color-capable lights, or the group resource hasn't been refreshed?
Added a diagnostic line setColor [diag v0.2.20] group rsrc.color=yes/no that fires before the gating check, so we see why setColor is dropped.

v0.2.20 contains the fix/improv.

Edited April 26 by jgab

[Sjakie 156]

Please login or register to see this code.

Still the same

Edited April 26 by Sjakie
v2.19