I have setup a rule in 5.1 to turn off fans at a certain time. The interest part is inside the rule if I hit the run actions it works but if I wait for the rule to run with criteria being certain time in my log it looks the same as if I push the run actions with no error but it doesn't turn off the fan? Is there something I'm doing wrong.
The best thing you can do to troubleshoot a rule is to enable all logging,then look at Logs filtered to that rule (or share them here, along with the rule itself).
But as a quick guess without knowing more: try opening the rule and hitting "Done," just to make sure the scheduled job actually got scheduled.
Thanks I copied the logs from last night. As you can see I setup the trigger for 11:52pm and the action followed to set the Bond Fan to off. There is no error but the fan stays on. Then in the rule if I click on run action at 11:52:52.681 it looks like it sends the same action but this time it shuts the fan off properly. Is there any other logs or information I can send so we can troubleshoot? Thanks.
app:10792025-11-05 11:53:18.068 PM
info
Action: Set Fan Speed: Master Bedroom - BOND Fan to off
app:10792025-11-05 11:52:52.681 PM
info
Action: Set Fan Speed: Master Bedroom - BOND Fan to off
app:10792025-11-05 11:52:00.396 PM
info
Action: Set Fan Speed: Master Bedroom - BOND Fan to off
app:10792025-11-05 11:52:00.374 PM
info
Triggered: Triggered at Certain Time
app:10792025-11-05 11:52:00.308 PM
info
Event: Triggered at Certain Time
app:10792025-11-05 11:51:07.470 PM
info
Initialized
app:10792025-11-05 11:51:07.415 PM
info
Scheduled: 11:52 PM
app:10792025-11-05 11:50:32.781 PM
info
Initialized
app:10792025-11-05 11:50:32.715 PM
info
Scheduled: 11:52 PM
OK, so those logs say that the rule is working as it should, so I don't think the rule is the problem. If it says it sent a command, it should have. You can look at the "Events" tab on your fan to verify that it did. Don't look for events there but rather commands (it shows both, so yo want ones where the "Type" column has "command"). If you see it there, then you know it did. If it works manually, it's not going to matter whether it's you or an app sending the command, so it should work either way; if it doesn't, that would just suggest good luck when you tried but not when the app did. You'd probably get it to fail if you tried at some point, too.
How to troubleshoot that would be interesting, but at least you'd know where the problem lies. Any LAN problems (communicating with the Bond Bridge) at that time? Any relation to the current state of the fan (maybe it only works for off from some specific other state? I wouldn't doubt that some fans only support cycling and not setting a specific speed, though that's much more common with lights that can only cycle instead of setting to a specific level -- one of the disadvantages of Bond where you don't get two-way feedback but also a shortcoming in the remote capabilities of these devices, to name one possibility).
I got this error message now from the rule. If i go in and run action it works. Any suggestions?
So app:792 is the rule, not the integration? What is the rule (i.e., share it here)?
1 Like
