The new devices do not appear in my device list (the Front Pillar E and W are Zigbee bulbs that I am trying to replace...they had the same name, just renamed them)
I am unable to replicate the issue. I am thinking that it might be related to this:
If the bulb was previously discovered, it might be already authorized. The bulbs are added based on their id. Check the Hue Bridge Integration app Settings and see if the ids are already listed in the "selectedBulbs" (you can identify the name for each id by looking up the bulbs in the HashMap (under Application State).
I added 4 new Hue bulbs after I did this post (total of 6 new ones)...I can select all 6, but when I hit "Done" none of the lights are added as Hubitat devices...the app log just gives "Initializing".
The previous Hue devices (prior to adding the 6) are still there and and be controlled just fine.
So - said differently - the Child devices are not being added.
Edit:
This screen shot shows the selected bulbs, and the IDs match the Hashmap on the previous screenshot:
I think that both integrations are well done. I have the most experience with CoCoHue since I have used it since the 1.0 release a few years ago. It works perfectly for being able to import Hue scenes and also using Hue groups for dimming up/down smoothly as opposed to having to select all of the individual bulbs. You can use Hubitat Package Manager to install.
Correct, but it does not implement the "Start Level Change" and "Stop Level Change" commands on group devices (which I assume is what was meant with the "dimming up/down smoothly" reference). There are indeed no scenes.
Ahhh, now that one little feature might just be enough to convince me to switch over to CoCoHue! I have a couple of areas where I use Pico remotes to adjust the level of a pair of Hue bulbs (e.g. nightstands in bedrooms.) it has annoyed me that I have to use the individual bulbs for the startChanging/stopChanging commands…