How best to do this?

Some background:

I have a program that sets an INT variable based on whether certain combinations of doors / gates are open. (0 = secure ; 1 = not secure. ) The monitoring program is used with a door chime so that I receive an alarm if a gate is not secure when I let my dog out into the back yard. It's a straightforward program with lots of ORs so I won't bore anyone with it unless someone feels it's relevant.

Along with this program, I created a folder in UD Mobile with mapped values based on the status of said variable. Inside the folder are mapped-value icons of the various doors and gates being monitored. If the folder icon/colour indicates "not secure", I can tap on the folder to reveal which gate / door is open.

Everything has been working well until one day when I just happened to open the folder (which was "secure" status) only to find one door was indicating the blue "default" icon prior to mapping. Further investigation revealed to be a dead battery, which after replacing, restored communication however this has revealed two issues:

1. The default icon/colour of the sensor with the dead battery indicates an indeterminate third value which I haven't mapped, but I can't figure out what that value is and I don't know how the EISY got to that state.

2. The indeterminate state described in (1.) will not cause my program to indicate "not secure." I tried simulating the node loss by removing the battery while the sensor was indicating the door was "closed" however the variable doesn't change. EISY still thinks the door is closed even after forcing a run-if.

Forcing a query in either UD Mobile or the admin console while the door sensor battery is removed gives an error message, but it doesn't change the output of my program.

Any ideas how I can integrate this node comm loss into my monitoring program?

Thanks

6 hours ago, Nestor said:

How best to do this?

Some background:

I have a program that sets an INT variable based on whether certain combinations of doors / gates are open. (0 = secure ; 1 = not secure. ) The monitoring program is used with a door chime so that I receive an alarm if a gate is not secure when I let my dog out into the back yard. It's a straightforward program with lots of ORs so I won't bore anyone with it unless someone feels it's relevant.

Along with this program, I created a folder in UD Mobile with mapped values based on the status of said variable. Inside the folder are mapped-value icons of the various doors and gates being monitored. If the folder icon/colour indicates "not secure", I can tap on the folder to reveal which gate / door is open.

Everything has been working well until one day when I just happened to open the folder (which was "secure" status) only to find one door was indicating the blue "default" icon prior to mapping. Further investigation revealed to be a dead battery, which after replacing, restored communication however this has revealed two issues:

1. The default icon/colour of the sensor with the dead battery indicates an indeterminate third value which I haven't mapped, but I can't figure out what that value is and I don't know how the EISY got to that state.

2. The indeterminate state described in (1.) will not cause my program to indicate "not secure." I tried simulating the node loss by removing the battery while the sensor was indicating the door was "closed" however the variable doesn't change. EISY still thinks the door is closed even after forcing a run-if.

Forcing a query in either UD Mobile or the admin console while the door sensor battery is removed gives an error message, but it doesn't change the output of my program.

Any ideas how I can integrate this node comm loss into my monitoring program?

Thanks

Instead of testing for a known value, can you include a "if it is not" and add all of the known values?