app:1762025-11-25 05:55:00.310 PMinfoDelay Over: Off: Basement
app:1762025-11-25 05:30:00.207 PMinfoAction: Off: Basement --> delayed: 0:25:00
app:1762025-11-25 05:30:00.134 PMinfoAction: On: Basement
app:1762025-11-25 05:30:00.114 PMinfoTriggered: Triggered at Certain Time
app:1762025-11-25 05:30:00.112 PMinfoEvent: Triggered at Certain Time
What actually happened:
dev:1932025-11-25 06:16:19.225 PMinfoBasement was turned off [physical]
dev:1932025-11-25 06:05:01.071 PMinfoBasement was turned on [digital]
I originally tried using the Room Lighting app to accomplish the same thing with two lights and a chime. I tried a lot of variations with no success and thought that incorporating periods would get me across the finish line using Room Lighting, but that didn't do it.
After extensive testing, the only way I could get a reliable daily 7:00 AM activation was to abandon Room Lighting entirely and switch to Rule Machine:
Trigger: Certain Time → On Sun–Sat at 7:00 AM
Action: Dim: BR Headboard: 50
That’s it – one trigger, one action, fires every morning without fail.
Room Lighting’s Periods table (and even the old “Activate when time is…”) both leave the job stuck on “PENDING” forever in my setup. So for a simple daily wake-up light, Rule Machine is the solution that's now working for me.
Let me add one more wrinkle. On the two lights, I use the fade function to have the lights (one is directly above my eyes) slowly brighten to 50% over 3 minutes...sweet. See the screenshot.
I do have the trigger set to 2 times a day. the issue isnt that the trigger is not firing. the trigger does fire according to the logs but the action doesnt always happen immediately.
In my logs above you can see the trigger happened at 5:30 but the action didnt happen until 6:05
I found this function Command Retry. once i enabled that it seems to have fixed the issue. its been 2 days and its right on time every time. what can cause the command to not work and then work on a retry?
With some Zigbee lights I have had similar issues over the years. My fix at the time was to send the ON command twice. I have also had success using the set color temperature and level command instead of the ON command. I never dug into it much and these days things are working much better so I never really thought about it.
As a workaround try Set Level or Set ColorTemperature instead of ON. Or run the ON command twice. Not the best solution, but it would be interesting to see if it makes a difference.
I wasn't referring to Hub Mesh (which is Hubitat's protocol for two or more hubs to interact). I was referring to the zigbee and z-wave mesh networks that are formed by a single hub and the devices connected to it.
Z-meshes that are not "solid" will tend to have symptoms such as those you describe, assuming the device in question is either a zigbee or z-wave device.
The Hubitat documentation has instructions on how to build robust z-wave and zigbee mesh networks:
