Unexpected Mapped Values Behavior

[Nestor]

As per the pics, the Aeotec ZW187 door sensor (middle icon) does not seem to want to display color and status when closed like the other two. 

The two gates (first and last icons) are Yo-Link sensors that seem to perform correctly. 

All three use the same rules for open and closed (color, icon, etc) 

The fourth pic shows the available values for Aeotec and FWIW, the last two pics are properties for the Yolink and Aeotec nodes. 

Any ideas? 

Edited Tuesday at 01:25 PM by Nestor
Aeotec, not Ecolink

[Javi]

A little hard to follow, but I don't think "Access Control" is an open closed property. If I remember correctly this is something like how it was controlled manual/keypad/etc..  My guess is there are multiple nodes for this device and the Favorite is using the wrong node.

[Nestor]

(Edit: In the second screenshot in my first post, the garage door is closed. I would expect the icon to match the other two, however it reverts to the default icon values. )

You're correct that there are multiple nodes, however Access Control is the only one that appears to respond to state changes of the sensor and is useable in my programs. 

I created a test program and tried the different nodes in the (if) and confirmed this is the case. Access control is the only node that will change the variable when I open and close the door.

 

New Program - [ID 0080][Parent 0001]

If
        'Door Sensor - Int Garage / ZY 030 Door-Window Sensor' Status is On
 
Then
        $Int_Door_Var_Test  = 0
 
Else
        $Int_Door_Var_Test  = 1
 

 

The node in the third screenshot is similar to the others, save the "wake up" node which has status values, but not relevant for the sensor's main purpose. 

 

I have four ecolink door sensors and they all behave the same way. 

 

Hope all of this makes sense. 

 

 

Edited Tuesday at 12:50 PM by Nestor

[Javi]

I have a similar "Access Control" node and have verified (1) the status mappings are incorrect and (2) formatted values are not being displayed in UDM (subscription formatted).  I'll submit a bug report, however it is at firmware level so may be some time before a fix makes it to production.

I also think the Node may not have installed correctly or may require a compatibility mode.   The Binary Door/Window Sensor has a status on my end and is the Node I use to verify status.  If unsure how to do this please open a ticket as it's not my specialty.  If you open a ticket, let me know the number and I'll attach notes.

[Nestor]

Slight correction: The door sensor is an Aeotec ZW187. Apologies for any confusion this may have created. 

Ticket #27243 started. Will add more details to ticket as required. 

[Javi]

Thanks