I am curious why the need to do the "virtual" Motion Sensor and connect it to the Phillips?
I tested my programming off the actual sensor and the virtual version and it seems to work fine either way? So, it's just not immediately obvious to me since the properties in the Device Manager of the virtual Motion Sensor aren't particularly useful and neither are the query (example, you can't get the battery voltage from the virtual version, but can from the actual sensor).
So far, so good. I wouldn't mind helping these folks out with their documentation. It's better than most by a large margin but could still use some TLC and updates. I got confused more than once trying to sort out the connections between the Gateway, the Sensor, and the "virtual Sensor" that could of been easily avoided with some more consistency in the level of detail provided and where screenshots are placed.
The instructions also just has some errors and typos, presumably from trying to translate it from German?
Either way, it does work pretty well so far. I am testing one of these and one of the C4/Card Acesss motion sensors right now and for a few days before I decide which way to go. It's nice of them to allow a trial period on the driver and even if I don't go this way, I'm still a fan.
-V
PS: My test case is O3 with Hue Bridge v1.