I’m a little bit confused about what you’re trying to accomplish. It’s easy to use a Hue light coming on as a trigger in smartthings. But SmartThings cannot communicate with the Hue motion sensor Unless you have directly paired it to the SmartThings hub.
You could certainly do something with a virtual motion sensor when the hue light comes on, but there wouldn’t be any way to then communicate on to the actual Hue motion sensor unless, again, that hue motion sensor was directly paired to the smart things hub, in which case you wouldn’t need the virtual.
What exactly is it that you’re trying to accomplish with the virtual motion sensor?
Depending on what you are trying to accomplish, there is one other possibility, Mike Maxwell has a very cool universal device type translator which can have a switch report as a motion sensor. And a bulb can be treated as a switch. Normally, you probably wouldn’t need that but if, for example, you are trying to get a Hue motion sensor to work with smart home monitor (which doesn’t respond to a light coming on) you could set up something like this:
- have a Hue motion sensor connected to the hue bridge, not the smartthings hub. Also have a Hue Bulb connected to that bridge.
Two) set up the integration between that hue bridge and SmartThings. Smartthings will be able to see the bulb, but not the motion sensor.
Three) have the motion sensor turn on the bulb using the Hue bridge.
Four) use the universal device type handler and have the bulb Report as a motion sensor.
Five) now smart home monitor can respond to that bulb coming on, and since the bulb is coming on because the Hue motion sensor is coming on, smart home monitor is now responding to the Hue motion sensor.
Obviously, this is a lot of work, so the only reason to do this would be if you also wanted to use the Hue motion sensor with the hue bridge for other purposes. Otherwise, you should just connect the motion sensor directly to the smartthings hub