This kind of “false alert” is something I (and others) have seen before. In my case, I’ve seen it on a number of devices when I was away from the particular location. For two of these—after I concluded the device state was incorrect—I loaded a modified DTH that returned the current state of the device the next time it woke up. In both cases, the errant state returned to normal, as expected. Swapped the DTH back to the original handler and all was well.
The wet paper towel trick—or opening/closing a door or walking in front of a motion detector—causes the device state to be updated, effectively clearing the problem.
Here’s more (with links to previous observances). Good Luck!