Measuring Hubspace/Hampton Bay HB-10521-HS String Lights with Effect List

[challgren]

Hi,

So I previously did a measure on a smart bulb and everything went great. I now want to measure my Hubspace/Hampton Bay String lights.

One thing with the string lights is they have built in effects such as Christmas, Valentines day, 4th of July. These are basically WLED effects and I was wondering is there a way to measure these effects so when I have an effect active powercalc will record the correct wattage. I was reading that I would basically need to create playbooks for each effect. The docs about playbook mention the ability to create them using the measure script which I don't see.

[bramstroker]

playbooks would be far too complex for this use case.
There are no power profiles with effects support yet in powercalc library, but I suggest following approach.
As these effects actually loop I would say much simpler approach to just measure average for each effect during 60 seconds.
I might extend the measure tool in the future so it can cycle automatically through all available effects or something like that.
You can use states_power in the profile to map certain effect to certain power value in W.
https://docs.powercalc.nl/strategies/fixed/#power-per-state

You can also used this configuration in model.json, but don't have example for that yet in the docs.
But should be straight forward. When you get stuck on that please let me know than we will work out an example.

[challgren]

Bummer :-( Ok I'll do that, is there a way to contribute that states_power along with the color_temp measurement?

Also I can't say for sure but I think the power-per-state may not work because you can apply an effect and then a brightness level. But I need to confirm after my color_temp measure is done.

[bramstroker]

There is also https://docs.powercalc.nl/strategies/composite/, which I added support for that in model.json lately.
That should make it possible to combine LUT (color_temp.csv) with the states_power.
But it's really a complex use case, with many variables, espescially with the brightness level.
So essentially to get this "right", it needs further extension in measure tool and integration to also cycle possible effects and brightness levels and create some kind of lookup mechanism for that.
But it will take a lot of development effort, and don't have that on the roadmap short term.