The best thing to do would be to check the event history and see what it reports. Or setup a rule to send a notification with the value.
When you are configuring the Trigger for that devices, if you are seeing a drop-down of options for the values, those are the values that the device reported that it supports, but it wouldn’t surprise me if the device doesn’t follow that. For whatever reason, some of the ‘walled garden’ integrations like Ring and Arlo either don’t expose all their features or do things in esoteric ways.
Here’s an example of setting up a rule to try to catch all the changes for a button attribute and then send the attribute name and value in an email notification (using context variables). Note that it’s looking for the trigger to ‘change to’ a value or ‘change and is not’ that same value.
