I have two Ring devices set up using v0.1.25 of the plugin: a doorbell, and a floodlight cam. I'm looking to set up some automations triggered by motion detected at a particular device using a trigger off of the lastMotionTime.
Unfortunately, it looks like the lastMotionTime state gets updated on all devices whenever motion is triggered on any one device. For example, if I walk past my doorbell, my Ring app on my iPhone dutifully notifies me of the motion detected at my Front Door. In Indigo, the Ring Doorbell plugin eventually updates the device states based on the polling frequency. Because it is nondeterministic exactly what order polling will fire for the Ring devices in Indigo, whichever device happens to have its state updated first after the motion event will trigger the lastMotionTime changing. Then at some time after that, the other devices will also see their lastMotionTime changed the next time they are polled and updated. That is, regardless of where the motion was triggered, all devices will see their lastMotionTime updated when that device is next polled.
Not sure if this is a bug in how the plugin is polling the states (perhaps not correctly indexing the device lookup?) or if it is a limitation of the reverse engineered Ring "API" (such as it is).