Since my update to 2.0.0.104 I've had issues with my Motion Lighting apps not coming on when they should, but then later on would start working OK. It's only today that I've been able to investigate and work out what's going on.
I have 4 Motion Lighting apps and they are all set up to come on only in Evening mode. They all use Aeon Multisensor 6s, 2 trigger TKB TZ68 switches and 2 trigger TKB TZ67 dimmers. Under 2.0.0.104 they now don't come on the first time the motion is triggered after the mode changes to Evening. It doesn't seem to matter how much later after the mode change the first trigger doesn't activate the lamp. Once that first trigger has been "cleared" and the motion is triggered again they work as expected.
If someone can let me know what info you would want to see about them, I can do this tomorrow as the mode changes, or manually test it with a forced mode change. As I say, all 4 of my ML apps are doing the same thing and 2 of them haven't had any changes for a long while, so I'm pretty sure this isn't self inflicted.
The same behaviour today. Mode switched to Evening at 3.04PM (based on light level outside - it's gloomy here in the UK)
mode Hubitat Thistledown is now in Evening mode Evening LOCATION_MODE_CHANGE 2018-11-23 03:04:18.680 PM GMT
At around 3.30 I started walking around to trigger the ML app lights. I triggered 3 of them and, as before the light did not come on. Before I triggered the 4th one I took the following screenshots of the Motion Lighting details for it:
Interestingly, when I then triggered the sensor for that room, the light came on first time, so it looks as if going into the app in itself changes the behaviour.
I'm getting in the neck from SWMBO about the lights not coming on so I've temporarily gone back to 1.1.8.111 and can confirm that the same rules run fine first time after mode change in that. Happy to go to 2.0 again for further testing if needed.
Can you look at the device events for the motion sensor in question, and see if it is going active when you think it should, especially at the time you see the app not responding?
Yes that was the first thing I checked. The sensors are picking up the movement fine. This is the event log for the Bed 2 Sensor that I tripped at 3.23pm
Yes, I realise I've posted from 2 different ML apps. I had "test tripped" 3 of my 4 ML apps and they all failed, so the plan was to take screenshots of the 4th one (Bed 1 , which i posted above) and then trip it to show the error. However the act of going into the app seems to have fixed it and that one did come on when tripped. So I posted the events from one of the failed apps to show what happened (or didn't) I'm hoping it is easily repeatable for someone to test as it happened consistently for me with 4 different ML apps and has worked fine again since I went back to 1.1.8.111.
I have now also had the same failure in 1.1.8.111 but also some more information. I hadn't realised that the ML app itself generates a log and now looking at the Bed2 one it says it's not turning it on because it's already on. It isn't as can be seen from the event log.
OK. I'm really pleased about that because I'm getting a bit fed up spending so much time trying to work out why they aren't working. I have tried recreating my ML apps in RM, but never quite got it to work in the way I wanted. Hopefully the new release will sort it once and for all.
