In my ISY 5.3.0 firmware with Z-Wave at version 6.81.00, my August locks each show as two devices in Admin Console - one is the "ZW ### Door Lock" (which has read/write control over the lock status + operation), and the other is "ZW ### Access Control Alarm" (which has a read-only status of 'Access Control' [ALARM], and 'User Number' [USRNUM]).
I can reliably use both in programs, as well as notification messages through substitution.

For the "ZW ### Access Control Alarm", I currently have a very convoluted setup for sending the string value that shows in Admin Console, rather than the integer value that comes from ${sys.node.ZW###_XXX.ALARM}. 
I do not love it, however. Seems to be it should be easier to get the enumerated string value that shows in admin console, but I cannot figure out how to do so.

 

For instance, here are my ZW004 node details as listed in the REST format:

And if using Admin Console, I see a string of "Auto Locked" rather than the value of '9', as above:

It is also available in Programs:

But when the notification comes in from this setup:

it comes in as the integer value of '9':

I have not been able to come up with a different way to access the corresponding string enumeration directly (like I said, I do have it solved via some rather silly and complex setup).

Does anyone know if there is something along the lines of ${sys.node.ZW###_xxx.ALARM.STR} or something that could be used in Notifications to return the corresponding string to the values below? Or some other fancy way to turn integers into strings without having a program or virtual device or Notification customization for each individual integer value?
From what I have been able to determine:
1 = Manual Lock
2 = Manual Unlock
3 = RF Lock
4 = RF Unlock
5 = Keypad Lock
6 = Keypad Unlock
9 = Auto Lock
11 = Lock Jammed

 

Edited December 31, 20204 yr by residualimages
extra screenshot

I was able to find this information at /rest/zwave/node/ZW004_306/def/get:

Seems like ALARM is using a Status Names thing (the property id of "uom=25" corresponds to 'indexed values') / specific encoded Editor in the Admin Console?
Maybe:

• UOM indexed = 25
• Precision = 0
• ?? = S
• lowMask = 0A7E
• ?? = N
• nls = IXA_AC

In any case, feels like an opportunity for Universal Devices to handle the "formatted" aspect of the properties on these _306 nodes more in line with other nodes (the actual indexed string / name that corresponds to the raw value) - @Michel Kohanim, is this something you would be able to consider updating?

Through REST download, I have found \core\f4\i1\nls\en_US.txt and the relevant location. Seems like I should be able to get IXA_AC-rawValue into a Notification somehow. 

# --- 0x06 - 306 - Access Control (0x00-0x3F)
NDN-306-ICON = Alarm
ST-306-ALARM-NAME = Access Control
#   ALARM uses these
IXA_AC-0 = Idle
IXA_AC-1 = Manual lock
IXA_AC-2 = Manual unlock
IXA_AC-3 = RF lock
IXA_AC-4 = RF unlock
IXA_AC-5 = Keypad lock
IXA_AC-6 = Keypad unlock
IXA_AC-7 = Manual not fully locked
IXA_AC-8 = RF not fully locked
IXA_AC-9 = Auto locked
IXA_AC-10 = Auto lock not fully locked
IXA_AC-11 = Lock jammed
IXA_AC-12 = All user codes deleted
IXA_AC-13 = Single user code deleted
IXA_AC-14 = User code added
IXA_AC-15 = User code not added (duplicate)
IXA_AC-16 = Keypad temporary disabled
IXA_AC-17 = Keypad busy
IXA_AC-18 = New program code entered
IXA_AC-19 = Manual code entry limit
IXA_AC-20 = Unlock by RF with invalid user code
IXA_AC-21 = Locked by RF with invalid user code
IXA_AC-22 = Window/door is open
IXA_AC-23 = Window/door is closed
IXA_AC-24 = Window/door handle is open
IXA_AC-25 = Window/door handle is closed
IXA_AC-32 = Messaging User Code entered via keypad

 

Edited January 1, 20214 yr by residualimages
/core/f4/i1/nls/en_US.txt findings

I would suggest using @ notification system to bring UD's attention to your request. You can type "@" symbol,then start typing Michel's name and when it appears, select it from the list. This will notify him to read this post.

@Michel Kohanim - I saw you <3'd Dennis's post, and I did edit to mention you in the post above.

I assume this is pretty low on the list of development tasks to consider?

@residualimages,

As you have noticed, we are migrating nodes/properties, to node servers which would make the "formatted" tag obsolete. 

With kind regards,
Michel

On 3/19/2021 at 9:35 AM, Michel Kohanim said:

migrating nodes/properties, to node servers

even Z-wave?

@residualimages,

Yes.

With kind regards,
Michel