You can use Hue motion sensors via the Hue Bridge and CoCoHue as long as you have the new/experimental "eventstream" or v2 API option enabled (or really use them either way, but they won't work well via the v1/polling-only API). I think this answers question 1?
For question 2, you don't need to do anything on the Hue Bridge (except push the button on top to "link" the app when prompted, like you've probably had to do for Alexa and other integrations already).
Finally, for the "bundle" option in question 3: you can just download the ZIP, go to "Bundles" (under "Developer Tools" on the left--expand that section if you don't see it), and upload the ZIP file there. Bundles install apps, drivers, or libraries for you; no need to mess with them individually after that. So, that's one option to install rather than doing everything manually. Many users prefer Hubitat Package Manager, often known as HPM, which is an app that can install apps, drivers, or libraries for you as well and assist with keeping them updated going forward. Either would be my recommendation over a fully manual install, though any option can work.
The switch state is irrelevant to the driver regardless of what method you use, i.e, an "on" will also activate it even if the "switch" attribute already reports as "on."
If that's not what's happening for you, what's likely getting in your way is the "command optimization" setting in webCoRE, which as the name might suggest, will cause this not to happen when the above state is the case. (Some other apps also have similar settings, e.g., Groups and Scenes.) Using the the push() command instead of on() is one way to avoid this, though it is also a setting you can change on the piston. Without one of these, the command won't even make it out of the app and to the driver in the first place.
I'm trying to add buttons in CoCoHue, but they disappear right away... I have 2 buttons in the Hue app (wall switch module and a Sunricher FOH module), and I can find and add them under Buttons... But when i try to use them I can't find them and when I add, it says 'No added button devices found'. I can add them again, but to no avail.
I have enabled push-updates from Hue bridge.
Any ideas on how to get them operational?
I'll have to check this out later to be sure, but it sounds like I may have just forgotten to include the button driver in the bundle ZIP (it's a new addition and was probably not there in the original one I created, and I may have not checked the box after adding it, etc.). I will need to re-upload a corrected bundle ZIP if that's it.
It does, thanks! Progress, at least.
I can now get both buttons in rules, and they're working fine for switching.
The FOH switch does not seem to register button held - It registers push only.
The Hue wall switch module registers both push and held... I'll fiddle some more with it and see if I can fix them.
So I've managed to get a dimmer somewhat working now, just a few issues.
When i push and hold a the momentary switch (A wall switch module can actually be configured as momentary in Hue app!), it registers both pushed and then later held.
So it toggles the light, then runs the automation that sets=0 and starts raising.
Is there a way to make it wait for release to detect short press?
On the FOH switch, I can't get it to register 'Held' or 'Released'.
These all behave a bit differently, so it's difficult unless I actually have the device, but the way I wrote things now works with any (official) Hue device I own but makes what seemed like reasonable assumptions for the any such device that should work for most.
In general, the driver reports any event it can based on what the device sends to the Bridge/network. There are different ways some of these events could be parsed, some involving timers that I'm not fond of in general (especially for Zigbee or Z-Wave devices, but Hue is reliable enough it might work...), and some may generate both push and hold rather than, say, just a hold if that's what the device supports. In such cases, for now, you may need to implement logic on then app side to detect the difference (time) or choose which events you actually want to use. It's possible I'll revisit this at some point...
I am finding that if I try adding my four Hue movement sensors to the cocohue bridge integration it causes a fatal error and the integration fails. Is this a known error or something wrong at my end?
No known issues with that. If it's the app or driver causing this problem, you should see something in "Logs" when it happens, and I could use that to figure out what's going on.
app:432023-04-04 00:44:42.593errorcom.hubitat.app.exception.UnknownDeviceTypeException: Device type 'CoCoHue Motion Sensor' in namespace 'RMoRobert' not found on line 1143 (method pageManageBridge)
That error message means that the "CoCoHue Motion Sensor" driver was not installed. If you used HPM or the bundle ZIP, it should have been part of either. If you installed it manually, make sure this is one that you got.
I installed the drivers from the links on your GitHub page and the motion sensor driver isn't included as a link as far as I can tell which is why I missed it. I have it now.
Thanks for your help, your support is excellent and much appreciated, particularly by a newbie like me who only got the hub yesterday.
hey im trying to make a scene that i made in the philips hue app to flash the Scenes on motion active Is this possible because it's not working for me the only one thats working is on "ALL Hue Lights" Which is a default white
All Hue Lights is a group, not a scene, and will work for that. Were you also looking to use a group to flash? That will work. A scene will not. The API does not have a way to do that (though there might be some way if it was created as a "dynamic scene" and this was just part of that).
If you really did want something like that, I suppose you could activate the scene and then flash a group corresponding to the devices in the scene.
