This object is in archive! 

State of virtual switches in rules after reboot

acteck shared this problem 3 years ago
Known

Virtual switches do show their status correctly after a reboot in the UI. But in status mails sent by rules status of virtual switches are undefined after a reboot. After setting the virtual switch manually it will be shown correct.


If virtual switchs are shown correct in the UI, please also update the status for reading in rules and emails.


An "renew everything" in a rule does not work after reboot. One has to set every single virtual switch or value manually. But how do I know what the status was before the reboot?

Comments (1)

photo
1

Andreas,

As the 3G Stick which attached to the Backup Battery has a slot for a MicroSD card, I guess it would be an easy task for Zipato DevTeam to either automatically write property data/values on all virtual devices whenever some of these change, and to check for, and if exists, load the saved property data/values.

A more complex approach could be to leave the save/reload to the user in an Action block (Pro-mode of course), where you could check for a STARTUP event and load whatever you would need...

Brgds,

Robert

photo
1

should be very easy to have these status recorded and reloaded after a reboot. No different to a variable and they are stored.

photo
1

Adrian,

In case you'd have a power outage you can risk that the internet access is down or takes longer to be established than the Zipabox takes to boot, in which case the "retrieve from server" fails. IMO, the best would therefore be to have these loaded locally, rather than from the remote servers.

photo
1

Variables are not stored during a reboot!

photo
1

agreed they should be stored locally. and I thought variables were stored. I have had rules trigger on a variable after a reboot. I'll check this out again to make sure. Thanks for pointing it out andreas.

photo
1

I reported this to Zipato support on 20 October and they qualified this as a bug but no update since that time and there were two FW upgrades. To be honest - if they implement it only as reading device states from cloud then 80% of problem is solved with 20% of effort. Cloud allows you to store values in virtual meters and read them as they were variables, and those values are actually stored in cloud because mobile app and web ui show them even when box has null values assigned and rules don't see them.


In my opinion we should insist on quick repair even if it requires cloud connection.

photo