Can confirm the instructions provided above by jadragescu works perfectly for getting this device added to vera and having motion reported independently. Thanks for that jadragescu.
Any idea what 3 Generic I/O Device that is created does? Any way to delete it?
Any way to get the 2 Secondary Dimmable Light that is created to update when the light turns on/off from motion? I’m guessing when the switch itself handles turning on the light from motion, the device does not get updated until it is polled (because vera has no idea that the light was turned on by the motion until it is polled), however, there is a LoadLevelStatus variable in the parent device (which is now configured as the motion device) that correctly and immediately has the value of the light when it is turned on from motion by the switch. I’m wondering if there is any way to link that variable to the 2 Secondary Dimmable Light that is created.
If any one was wondering, no matter what mode the switch is in, manual, vacancy, or occupancy, motion is reported by switch. Therefore, you can keep the switch in manual mode and still get motion triggers (if you just want motion triggers that do not turn the light on). It makes for a nice mains powered and clean looking motion sensor for a room.
Update
I was able to get the 2 Secondary Dimmable Light to update when the light turns on/off from motion. Using pleg, I monitor the LoadLevelStatus variable in the parent device (the one configured as the motion device) and when it changes I have a pleg action send the new value to the 2 Secondary Dimmable Light using luup.variable_set(“urn:upnp-org:serviceId:Dimming1”, “LoadLevelStatus”, TheNewValue, TheDeviceNumOf2SecondaryDimmableLight). As a bonus, when you manually change the dim at the switch, it also updates the 2 Secondary Dimmable Light. It appears as though this switch has instant status updates. If anyone wants some more details how to do this just let me know.