Gotcha. It came up after DM’ing my location ID to nayelyz and she said the developers asked if I could delete the invisibile device to see if that was causing an issue.
On another note, they did use my location ID for the fix bc I was able to “import” all my hue devices with your driver. I don’t seem to have any conflict issues but I currently have duplicates for all my lights. Would it be safe to delete the ST Hue hub (from their default driver)? I’d like to keep things clean.
Hi, @leonardo
So, were you able to install all of the Hue devices now? The bridge is the parent and the connected devices are the child devices.
About seeing duplicated devices, I think it’s because you have the official Cloud-To-Cloud integration.
You can identify them in the Advanced users’ app > Devices, one instance of the device will have a type of “VIPER”. After confirming that, you can delete all of them if you follow these steps:
I have two Hue lights in a room and one Hue scenes, one that turns one light red and the other that turns one light green. Both leave the second light off. I have created two scenes manual routines in ST, each of which just turns on the Room lights (a device created by this edge driver) with Play a Favourite set to the Hue scene name. They work fine, except that the second light briefly flashes white before going off again. When I switch between the two scenes in the Hue app, the second light never comes on, as expected. Is this a feature of the driver or is there something I can do to fix this?
It’s not limited to one room or scene as I noticed a similar behaviour in a bathroom nightlight automation which plays a Hue scene with a single light at 1% but which initially comes on bright before dimming, which doesn’t happen when I play the scene from the Hue app.
Yes. If you are happy with this driver, you can unlink your official ST integration to get rid of the duplicates.
It’s not a feature of the driver 
I’m guessing your automation turns the room “ON” before playing the scene. ST defaults that to ON for some reason, and you have to un-click it if you don’t want to change the on/off state. That is probably the cause of your brief flash before the scene kicks in.
The API was just published for Hue contact sensors and Hue cameras. If anyone want to buy me one, I’ll happily integrate them
Ah, yes, that is indeed the issue. It looks like an option group and it never occurred to me that I could untick ON and leave all options blank. I should have tried that, so apologies and thanks.
I’m not sure what you mean with the device having a type of “VIPER”. I do not see that anywhere in my device list.
Go to the Advanced page in the web interface.
On the devices list, Choose a device by clicking on its name label and go to its details page.
You will see a line with the columns manufacturer code, model, and type.
If it’s a cloud to cloud integration, it will say “viper“ under type. (That’s just smartthings terminology, you won’t see it anywhere else.)
In this screenshot for a device named “Atomic,”, it’s just to the right of the fields that were marked in red.
I guess I’m confused then because both of my hue hubs (beta driver from blueyeti and the ST built in) are showing type “LAN”.
I’d still like to kill the ST default hub unless this changes something.
I have the same setup @leonardo, a Hue bridge with ST integration and the device created by the edge driver in this thread. Like you, both report as “LAN” not “VIPER”, though my Arlo and Konnected devices do report as “VIPER” (in case that helps @nayelyz).
To your other point, I have two Hue bridges and having used this driver for a week or so, and after using it to add Hue Rooms and Zones, I killed one of the native ST devices yesterday. The only consequence was that a couple of Routines showed up as as broken where I was still referring to individual bulbs. Easily fixed with either a reference to “[room] Lights” or by “Play a favourite” to play a Hue scene. All working fine for me and reduced my device count by around 40! (more applause for @blueyetisoftware 
)
SmartThings currently offers two official Hue integrations.
One, type VIPER, is a cloud to cloud integration that can be used even if you don’t have a smartthings/Aeotec hub.
The second, type LAN, is a local integration that does require a smartthings/Aeotec hub. this is handled with a stock edge driver.
The edge driver discussed in this thread, the one from @blueyetisoftware , is a local community-created custom edge Driver. It also has type LAN and it also requires a smartthings/Aeotec hub.
There will shortly be a fourth possible integration method, the third official one, which will use a matter edge driver running on a SmartThings/Aeotec hub. I think its type is going to be “Matter” rather than LAN, but I’m not sure on that.
Anyway, so far it is possible to use all four of these methods independent of the others, which means the hue bridge and bulbs will be duplicated in your device list if you have more than one of these integrations active at the same time. 
Deleting one of the integrations shouldn’t have any impact on any of the others. But, as was already noted a routine that referred to a device connected through that specific integration might be disabled or even deleted when the integration is removed.
@black-paladin and @leonardo I think we are over complicating this. If you are happy with this driver, you can delete the ST version. There are two ways to do that depending on how you connected it:
LAN - Delete the ST Hue hub device that they created. You can tell this one because it has no functionality on its page
Viper - Unlink it from your connected accounts page
Philips Hue Beta 2023-09-02.21.17.10.71
Keep in mind that users will still see issues adding new devices until ST resolves their issue with creating child devices.
Can anyone provide further advise. I can see the hub with the new driver but it wont import anything. I even cleared out the hub of scenes and extra stuff and it still wont import anything into smart things. Even my other hue hubs (I have 3) wont import which led me to this attempt to fix.
I had this driver working perfectly for months until this update was pushed to my hub. It killed my entire integration. All 27 of my Hue devices stopped working so it doesn’t seem that this is because of onboarding lights from a new driver. I was forced to go back to the stock driver.
There isn’t much to go on from this report without logs. If you feel like moving back, and want to grab log files, let me know. If everything stopped working, the mostly likely cause would be something at the networking level with the Hue hub (ip address change, network change). The other cause would be if the driver was unable to startup (too many scenes, ST didn’t init the driver).
Any clue in as to what functionality will be available from the hue camera? Local access to video stream interests me the most.
The motion sensor on the camera will be local. They haven’t published information on the video stream, but I believe it will cloud based since the stream is encrypted. In addition, ST Edge doesn’t have the ability to hit a cloud service, so I’m not sure how video will pan out yet.
For motion sensing, the battery based cameras use PIR sensors. The wired versions use video tracking for motion. Both of these look like they will be local, but hardware isn’t available yet.
