As you can see there it shows that as false but there has been no motion for sometime. Looking at the events each contact sensor shows active and has been for over 25 minutes. One has even reported changes in humidity and temperature in that time but never shows inactive.
I've never downgraded to a prior version of FW but I think a test maybe in order.
The sensors here are Zigbee but another one doing the same thing is Z-Wave.
If I were to want to go back to 147 (the last version I was on where I was not seeing this) how do I go about that? Is it as simple as restoring a backup from that version?
Also seeing some light groups misbehaving. Right now I have a Light Group that is 2 RGB light strips, both Z-Wave that currently show on but both devices show off and are indeed off. This has also started recently. Going to give it another day and then I'll go back to 147 and see if things work better for me. Just trying to eliminate what is suddenly causing all the trouble.
I assume you mean motion sensor here, rather than contact sensor? Contact sensors are usually open/closed rather than active/inactive.
If these are battery powered multi-sensors, I would recommend checking/replacing the batteries.
I have seen several sensors that will continue to report temp on low battery but the motion reporting stops a bit earlier.
I did just downgrade to 147. My kitchen pantry has 3 lights and they have also been acting weird. One or more will either not turn off or not turn on randomly. I'm beginning to wonder if I have a device failing. The pantry ceiling light did fail last week and I replaced it with another of the same model. When I said it failed it would not stay on. By default it will stay on when the power is pulled from it but if I did that it just came on for about 1/2 second and then turned off. But the other 2 lights are LED strips and both are Z-wave. Will see what happens on 147. I doubt that's the problem but it's easy enough to make that change and rule it out.
So saw the problem once last night after going back to 147. The rule had been changed to remove a stand alone wait for elapsed time 1 minute to incorporate the delay to the motion sensor being inactive for 1 minute. There are two motion sensors on this rule at either end of a hall. When the rule was still waiting I looked at both sensors and they both still showed active. Once the humidity or temperature changed and that was sent to the hub then that specific sensor turned inactive. Could I have a corrupt database? I changed the rule back to separate the delay into its own step and since the I haven’t had any issues. But probably not long enough to draw any conclusions.
