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

[jgab 2,647]

8 minutes ago, Sjakie said:

Please login or register to see this code.

Still the same

 

1. Two Yahue parent QAs (560 and 606). Find which one is the parent of CHILD567 (the device the trigger checks). HC3: open the device, look at the parent ID.

2. Upgrade that Yahue parent to v0.2.19+ as well, or delete the duplicate one entirely if it's leftover from an older install.

3. After upgrading, CHILD567's debug should also start showing [diag v0.2.x] lines — once it does, the trigger will stop seeing false-OFF.

 

Edited April 26 by jgab

[Sankotronic 2,370]

Till now I was updating manually and this last update I did with QA Dist Manager to v0.2.20 and all get well. 👍

 

Problem with changing color temperature is corrected and also changing color is working nicely. 👍

 

The only thing is that if grouped light is turned off then it is not turned on when color temp or color is selected.

 

Also, if grouped light is turned off and HUE scene is selected then lights are turned on, but brightness is not updated properly and shows previous setting even actual brightness is shown properly in HUE app and updated. Note that scenes has their own brightness set and if it is changed by quick app then scene is not active anymore, but bulbs keep last color set on them and change brightness.

 

Is there a way to remember last selected HUE scene for the grouped lights?

 

 

 

[jgab 2,647]

v0.2.21

1. Color/CT when group is off — setColor, setColorComponents, setColorTemperature now send on=true together with the color/CT change, so the group turns on and you see the result.

2. Brightness not updating after scene recall — added a brightness aggregator on the per-member dimming subscriber. The room's displayed value is now the average of on-members' brightness, so when a Hue scene sets each member to a new level the QA reflects it.

3. Remember last selected scene — sceneChanged now stores the picked scene id in QA var lastSceneId. loadScenesForRoom (run at startup) restores it via updateView("sceneSelect", "selectedItem", ...). the previously chosen scene preselected in the dropdown next time the QA starts.

Please login or register to see this attachment.

The value is the Hue scene id. Can't use names as they are not unique.
Only works if scene selected on QA, not Hue app.

[Sjakie 156]

Jan, sorry I was in the car and realized myself I did something wrong but you discovered it also.

I deleted yahueV2

Updated V.0.2.21

Sorry have to drive now come back later can't see what changed due to other rules now.

 

[Sankotronic 2,370]

Hi @jgab,

 

This last version solved most of the issues. 👍

 

Just one more observation. Currently all grouped lights (rooms) are added as fibaro.colorController and in most cases that is OK. Still, there can be some grouped lights that contain only dimmable bulbs, like in my case Entrance or colorTemperature bulbs like my kitchen. 

 

While color temperature bulbs still must be added as colorController is it possible to check what bulbs types are part of the grouped lights and if only dimmable are found add as multilevelSwitch?

 

I know this can be pain in the a... since code has to check all lights included in the group if there is "color_temperature" and/or "color" existing in their metadata. Is it worth the effort?

[jgab 2,647]

23 minutes ago, Sankotronic said:

Hi @jgab,

 

This last version solved most of the issues. 👍

 

Just one more observation. Currently all grouped lights (rooms) are added as fibaro.colorController and in most cases that is OK. Still, there can be some grouped lights that contain only dimmable bulbs, like in my case Entrance or colorTemperature bulbs like my kitchen. 

 

While color temperature bulbs still must be added as colorController is it possible to check what bulbs types are part of the grouped lights and if only dimmable are found add as multilevelSwitch?

 

I know this can be pain in the a... since code has to check all lights included in the group if there is "color_temperature" and/or "color" existing in their metadata. Is it worth the effort?

It was not so difficult, I think... v0.2.22 (Also updated the User manual in the first post with all the new features)

• All existing room/zone children get recreated once. UID stays so mapping in mappedUids is preserved, but per-child QA vars (scene, sceneMode, lastSceneId, dimdelay, transition) are lost — need to reselect a default scene on rooms where one was set.
• In your case, Entrance and Kitchen will come back as multilevelSwitch / colorController (CT-only) respectively, so the device tile in HC3 will look different (no colour wheel where it doesn't belong).

[Sankotronic 2,370]

Hi @jgab,

 

I upgraded Yahue with QA Dist Manager to v0.2.22 and then Yahue get into the loop of deleting and recreating children.

Here is console output:

Please login or register to see this spoiler.

 

Hope it helps.

[jgab 2,647]

Oops, revert to 0.0.21 and I hope it works. I’ll fix it as soon as I’m home again (out shopping…)

[Sankotronic 2,370]

I tested it again. First I downgrade Yahue to 0.2.21 and then I removed both Kitchen and Entrance children.

After that I upgraded again to 0.2.22.

Adding Kitchen child that is actually colorController was added without problem.

Adding Entrance child that is [RoomZoneDim] failed:

Please login or register to see this code.

 

I just removed it from now from the drop down list to avoid further errors and looping, but I didn't downgrade Yahue.

 

[jgab 2,647]

Ok, v0.2.23 has some fixes to not loop, I hope...
The main problem though is that you have some child device that throws an error when created.

Please login or register to see this code.

but I can't see which one. in 0.2.23 I made a better error message so I can see what type it is so I can find it in the code.

[Sankotronic 2,370]

Hi Jan,

 

I have upgraded to 0.2.23.

Then I checked in drop down list Entrance [RoomZoneDim] and clicked on "Apply selection" button.

This is console output:

Please login or register to see this spoiler.

 

Note that child device is added, just drop down list for scenes is not populated. In that room there are 5 scenes added: Nightlight, Relax, Read, Dimmed and Bright.

 

Let me know if there is more info needed.

[jgab 2,647]

17 minutes ago, Sankotronic said:

Hi Jan,

 

I have upgraded to 0.2.23.

Then I checked in drop down list Entrance [RoomZoneDim] and clicked on "Apply selection" button.

This is console output:

Please login or register to see this spoiler.

Is this a room with only dimmable, or color lights, or switches, or a mix?

[Sankotronic 2,370]

Now when you asked, yes there is a switch added to this room.

 

I have also switch added to Barbecue room, but there are all color bulbs. Still, maybe from there are coming those clip errors?

 

[jgab 2,647]

26 minutes ago, Sankotronic said:

Now when you asked, yes there is a switch added to this room.

 

I have also switch added to Barbecue room, but there are all color bulbs. Still, maybe from there are coming those clip errors?

 

The clip and smart scene are just warnings that they are not handled by Yahue and ignored.
The problem may have been the switch in the room when trying to subscribe to events.
I think I fixed it in v0.2.24 🤞

[Sankotronic 2,370]

Hi Jan,

 

First I deselected everything and removed all child devices.

I have moved all switches to Other room which I do not add as a child. There are only plugs and HUE Festavia which I add as devices.

Installed latest version.

I selected again all rooms and devices as before and clicked on Apply selection.

All children are added, but Entrance [RoomZoneDim] still reported same error:

Please login or register to see this code.

Here is Entrance room resource:

Please login or register to see this spoiler.

 

it might help you to find what goes sideways?

[jgab 2,647]

Thanks for the info.
It's a real bummer that Fibaro don't allow us to have Lua's debug function.
If we had this I could print a stack trace when I encounter the error - now it's a real pain having logs in the right place - it's like debugging using punch cards - 2026!!!!

Anyway, I pushed v0.2.25 adding belts and suspenders to the code.
Please upgrade and share the new log lines for the Entrance child. The output will contain a RoomZoneQA __init start uid=… line followed by a warning naming the failing phase (e.g. __init stage 'loadScenes' failed: …), which will pinpoint the nil-call.

[Sankotronic 2,370]

after updating Yahue, I get this console output:

Please login or register to see this spoiler.

 

Unfortunately I do not see in console what you mention.

Note that update is made with QA Dist Manager and Entrance child was still on the system. After Entrance is added and Yahue restarted, it started repeating same debug output, deleting and re-adding Entrance child.

I manage to exit loop by removing check for Entrance and apply changes, so didn't downgrade version.

 

 

[jgab 2,647]

Case in point - the bug was not where I added the debugs 🤯
Can you try v0.2.26, that will pinpoint it...🤞

[Sankotronic 2,370]

It seems that will be third a charm. After updating, I put check on Entrance and clicked on Apply.

His is what I get in console:

Please login or register to see this spoiler.

 

Ready to test further, and thank you for the effort.

[jgab 2,647]

59 minutes ago, Sankotronic said:

It seems that will be third a charm. After updating, I put check on Entrance and clicked on Apply.

His is what I get in console:

Please login or register to see this spoiler.

This was really tricky... my debug statements missed it again(!)
Can you upgrade to v0.2.27 and re-add Entrance and see what the log says?