i made a childapp thingy named with the animation app, now it shows in the list but there is no device adde... searched all of them and tried 'test' and 'conn' to find 'connector'... nothing.
If I hit the shild app I get a error pointing to the logs... where i find this...
running a C5... made the animation hours before i tried looking for it... rebooted the hub... nothing.
then i deleted the color animation main app, reboot... reinstall animation app... reboot... again create 'test' child app... nothing... reboot... nothing...
Meaning by 'nothing' that the same error/message was showing... no new device.
tried philips hue collor bulb as wel with a non philips hue ledstrip (rgb)...
Probably nothing you can do if waiting or a hub reboot didn't fix it (unless maybe a downgrade and re-upgrade helps? grasping at straws at this point). Tagging @support_team so they are aware.
There's another post now where someone is missing one of the new drivers, so something must be off with .152 with respect to missing stuff (I'm still missing this Animations app too).
That's really odd because I installed .152, read the notes, clicked into apps, didn't see Animations, clicked back out, clicked back in about two minutes later and it was there.
I'd suggest using a high (at or near 100), non-random value for saturation, or small degree of randomness that would still keep it pretty close. If you go fully random, you're likely to get low saturation values lots of the time, which will look closer to white (so washed out if you're expecting colors).
Of course, that's ignoring any bulb-specific oddities, like if they just don't do certain hues well. "Hard-coding" what you know to work well is certainly fine too!
I installed the build in 'color animation' app...
Created a 'child instance' or rule if you may call it.
What i have seen online i should get a new device called like i named it in my case 'testing' or connector but that doesn't happen.
When I click the gear icon from 'testing' in the app list I get some error.
Can you reboot the hub and see if that fixes it? My hunch is that the activator device type (new driver) isn't loaded for some reason.
Also, I can take a look at the engineering logs if you PM me the hub id.