Just updated to 2.0.4.117
One of the fixes was for Sunrise and Sunset with offset . I created new triggers after the update to test. I was able to create a Sunset trigger with a minus offset
with no error logged... I was able to create a Sunrise trigger with a plus offset with no error logged... but if I use a minus offset to a sunrise trigger, I get an error logged.
I will find out tomorrow morning if the triggers are functional. This started when
my morning trigger didn't activate ... I had played with renaming the rules and
I hadn't updated the firmware... so I updated the firmware and started experimenting with creating new triggers... Below are the errors logged
names of the Rules H1_SRm17 (Module H1 Sunrise minus 17) and H1SRm10D1t5On (Module H1 Sunrise minus 10 Restricted to Monday thru Friday on)
These errors only show up if I have a minus offset to a Sunrise event.
All other scheduling working fine...
Any feedback as to the meaning of the error?
That's a very odd error, and I don't immediately know its source. Could you take a look at the App Status for that trigger, and see what it's Scheduled Jobs are. A screenshot of those might reveal something.
I have been able to reproduce the error, and that should lead in short order to finding the bug causing it.
I found the bug. What's going to happen is that it will fail tomorrow morning, and then work after that (assuming you don't hit Done). If you look at App Status, you should see an Event Subscription for sunriseTime. That's what is going to schedule it for day after tomorrow. That event happens at sunrise, giving the sunrise time for the next day, So tomorrow morning it will miss because that happens after your trigger should fire.
A fix will be in the next release. We may put out a hot fix for this, not sure yet.
@bravenel all my rules with Sunset failed to fire after the .117 update.
Strangely logs are empty as if Hubitat simple lightning was not even triggering anything.
Are you saying that motion did not trigger this rule? The recent change had nothing to do with Restrictions involving Sunset and Sunrise. When did you take that screenshot? It shows the rule not being restricted. Was that after sunset?
I Had to check... But you might be right. This could have another route cause.
So after I did the update. None of ALL my motion Sensors triggered anything.
This is the last log for two examples
app:392019-01-17 04:25:43.775 infoKitchen Light Motion anti-Turn On & Set Level
app:382019-01-17 05:57:55.353 infoLight Tv Motion anti-Turn On & Set Level
I will need to dig a little more into it. Is odd that all my motion sensors that are connecting to lights stop reporting before 6:00 am
You can look at device events for the motion sensors from their device page. See if they are reporting events or not.
Ok..
So not sure what caused 2 motion sensors connected to sunset/sunrise rules (might have nothing to do with it or can, I can't pinpoint) to stop communicating. Event logs doesn't help, he does show another 1h later check in after the ones I just posted
Reboot made 1 of them comeback online the other had to rediscover it again.
Will need to monitor this. Is odd to say the least. So let's park this case of mine and see what happens.
I daresay the Xiaomi sensors are not very reliable, and them falling offline would have nothing to do with sunrise/sunset.
I don't know why they did drop-off. Sadly I can't ask them and they can't respond. So it's always a guess.
What I do know is that they have worked flawlessly in ST in the exact same location with the exact same setup.
Further to clarify those that drop-off were in exact opposite of the house. Not any other device drop-off. Both hapoen to drop at almost same exact time. So for me is not a problem with each individual Sensor.
When I moved over to HE, after a couple of months some of my Xiaomi sensors started to play up. "Never had this with ST I thought". Re-associate them and they would fall off the grid again after 24hrs.
Then I realised that the battery reporting on Xiaomi devices is flakey to say the least, I started changing batteries and hey presto, all is good in the world again.
I've had some of the devices for over 18 months with no battery changes.
Now I'm not saying this is the issue you are seeing, but, it might be worthwhile changing the batteries to see if this is the issue.
Good luck.
Same thought I had, but then I saw they went offline with just a few seconds apart.
After reboot and rediscover they are again working ok.
