Hue motion sensor is on Hue bridge.
I want it to be there, as 1) using Philips bulbs as mesh repeaters being on same Zigbee network for great connectivity and 2) Philips to take care for formware updates via its bridge.
Currently only Philios Hue bulbs can communicate in Hubitat via built-in app, but not motion sensors.
Why is that and will it change? Meanwhile, anyone knows a way to be "added" in Hubitat just like the Philips Hue bulbs connected via Hue bridge?
This is because the V1 Hue API, which Hubitat has long used, does not provide any way for instant status updates, making motion sensors basically useless for that purpose via the API.
This will change in the next platform release, version 2.4.0, which is currently in beta testing (and you can join if you want). It will also likely be released soon, though as usual, no guarantees on the timing.
There are at least two community integrations (one of which I wrote) that will also allow this in the meantime.
The new (beta) Hue integration is awesome. Join the beta now or wait for its general release - you won't be disappointed.
Hat tip to Robert 
Hi mate, perhaps a stupid question but how to join this beta - cannot find it in app, neither in forums or Internet...
Presuming these details are still current....
Oh, I see Simon, just applied! Meanwhile installed CoCoHue via HPM, just no attributes appear for Hue Motion Sensor but playing with it. Indeed seems prob is Hue API v2 vs v1 implementation, hope will get updated soon in Hubitat as it will be great step forward.
If you haven't already, you may want to trigger the motion sensor and see if the attributes appear then.... Alth I would have expected them to appear straight away...
Will it be easy to switch from your app to the new one you mentioned? Does it entail switching device drivers for each device?
You will have to manually swap any devices you have in use by apps. (Changing drivers alone will not work; these are all child devices of the parent integration app, which there is no way to change.)
In a word to answer whether it's easy, I suppose mostly "no," but that depends on how many devices and apps you have. 
OK, thanks. Dare I ask if you think there is an advantage to putting forth that effort (I do have a fair number of hue things in rules)? I guess I did ask ... I have noticed before that the swap app feature didn't seem to work on your child devices.
Didn't you just ask this yesterday? I can't answer if anything is worth it for you, but if that's all the longer it took to set up, it would be similar or less work to convert (apps are already there, just have to switch out the devices).
There are some features the (new) built-in app supports that may or may not make their way back to the custom integration. Contact sensors are one. But if either is working for you, no need to change.
I didn't suggest that as an option for a reason. 
This is an intentional limitation of the tool for all child devices, regardless of what particular app or driver might be their parent. See: Swap Apps Device | Hubitat Documentation
Thanks!
I'm sorry - I think my last question - is it an all or nothing kind of deal, or will both apps cooperate running together so I could move devices piecemeal over a period of time? I hope that makes sense.
There’s no reason you can’t run both at the same time. It would definitely be better to settle on one at some point because it’s more load on both the Hubitat hub and the (rate-limited) Hue Bridge. But there’s nothing to technically stop you from doing it.
A feature request would be to have Hue devices both on the new built in app as well as CoCoHue show up in the Swap Device feature in Settings. It's no fun making the changeover to the new app ... and it probably (hopefully) would be a whole lot easier with that working.
This isn't specific to either integration but rather a design decision made at the platform level due to these being "child devices" (of a parent app or driver, app in this case). This tool works at a fairly drastic level that will not end well for many such devices, hence they are not eligible for this tool. You can find lots of forum discussion with a search, but ultimately it's the design decision documented here: Swap Device | Hubitat Documentation
I'm not sure what to say except that making the switch to the new app is not easy - and it sure would have been nice if that difficulty, which is, as you point out, well documented, had been taken into consideration at whatever level was necessary.
That is unlikely to change for the reasons mentioned above. But it's always possible to manually swap out the device in any app. That's how we all had to do it before this feature was around at all. If any app is particularly difficult (e.g., say you have a rule with lots of device references), the "Clone" feature available to most apps is another way you can swap devices, this being at a per-app level rather than platform wide.
Currently running version: 2.4.0.145
All looks great after several days, works flawlesly so far.
Just a bit strange that newely added motion sensors didnt appear at the swap devices list, would of make the life a lot easier, still it's 1-time swap job so don't regret at all as now motion sensors dont loose connection being in the same net with the bulbs who act as signal retranslators.
Download the Hubitat app
