5- Describe the issue: I’m trying to set my defult state as Fuze. When chat chages the color of the lights with dynimic defult for Eg: !red. they go red but they dont change untill somone chanages them to green thats cool and all but i have a slow chat. and i want the dufult state to go back to fuze but even after 10 seconds of idel nothing in que they stay red and dont go back to fuze.
When your lights are red then they are not considered idle as they are doing red.
If you want to keep dynamic default, but not forever, I suggest you make an automation that triggers all “your duration” seconds/minutes with a lights off command. Just make a chat command with a lights-off type and a duration of 0.1 seconds to trigger it. Then the idle triggers the Fuze default.
Also, I would suggest for Fuze to set the default state to “Lights off” and the Idle state to Fuze with a delay of 1 second. That makes sure all your lights return to Fuze. Lumia doesn’t really know in what state your lights are and won’t turn them off to fuze. So it could be they stay red.
I get that but the work around dosent seam to work when certan commands are active. and i cant understand why i see the lightsoff command in the que log but the lights dont turn off and the dufult state wont come back.
unless its a bug? im not sure
i did an automation to start fuze so i guess thats a work around aswell but something with the lights off and the lights off not going off and going back to defult must be a bug or one of the other commands override the lights off? will the “skip luima actions” check box stop that?
nanoleaf. i think they are gettting stuck on a intence activity then they bug out. even the check box back to defult after intence activity if they get stuck dosent work. only option it to refresh evetying to get them to go back to idel