This object is in archive! 

Status of virtual devices after reboot

acteck shared this problem 3 years ago
Known

Situation:


I use several virutal devices as indicator for some status. I.e. "Daylight" is on during the day and triggered through a rule. "Summertime" is on during warm period of the year for better steering my thermostats. And some more.

Every hour I send myself a mail to inform me about the status of my system (some crucial windows and doors, garden pump etc.). Also included are the status of some of the virtual devices.


Problem:


After a reboot, all virtual devices have in the Web UI the same position as before. But in my status mail some of this virtual devices are undefined. This is true for "Summertime" but not for "Daylight". Both are virtual devices. Summertime also after a reboot correct, Dailight not. It is in a undefined status after reboot.

Comments (3)

photo
1

Have you managed to solve this Andreas? I still have this problem myself :-(

photo
1

No,

there is no way to safe a status over a reboot. One has to check. Most virtual switch stay in their status. But not all.

photo
photo
1

Same issue for me

photo
1

Andreas,


I once opened a ticket regarding this problem, zipato support told me that when you use message puzzle to send attributes the rule looks in the historic of the sensor, not at the current state (last state sent), this means that if the box rebooted and the device didn't have any change then it will show that looong non-sense status in your messages until it updates the box with current status. I don't understand why zipato cannot use the last status received as they do in device browser... unfortunatelly this is the way is set up and they are not willing to change it.