Hello,
What happened to this case?
Did it come to a conclusion why there are cloned Hue lights in Smartthings?
I too have a lot of cloned Hue lights in Smartthings.
One is a Edge_Child and one is a Viper.
The Edge_Child is local and the Viper is Cloud.
And to that extent, the Hue lights are also transferred over, from Smartthings, to Google Home so I have there a lot of devices that are in the “Linked to you” section.
How to proceeded to delete the proper one?
One more thing,
The Viper devices also have options to “Wake up” and “Sleep” that the Edge_Child do not have,
You have to Hue integrations. Edge_Child Devices are using local Hue integration and Viper Devices are using cloud to cloud integration. You have to delete the integration which you didn’t want to keep.
I’m not using Hue integration and I can not give more instructions.
Thank you for the clarification.
How come I have two HUE integrations?
In linked services in Smartthings I only have one integration with Philips Hue and looking into that integration I can see only one of each HUE light, not two of each.
How to delete one of the integrations?
Or do I have to manually delete each and everyone of the clones that I do not want to keep?
As @TapioX mentioned above, there are two integration types supported for hue: Hub-Connected (can be identified by type LAN or Edge_Child) and Cloud-Connected (identified by “Viper”).
The Hub-Connected integration is pre-installed in your hub, so, if you put the Hue Hub and ST Hub in discovery mode, it will be detected.
The option seen in the app’s device catalog belongs to the Cloud-Connected integration and can be identified because it asks you to log in to your Philips Hue account. No other integration type requires this authentication.
I don’t know why you have two now but if you connected the Hue Hub with the ST Hub but then went to the App’s catalog, selected the Hue integration and logged in, this added the other instance of devices (the order could be different).
As they are two different integration types, they can co-exist in your account but they will be counted as extra devices (despite physically being the same) and remember there’s a limit of devices that can be added to your location.
Deleting one depends on your preferences, if one has an option the other doesn’t or you want local execution instead of Cloud.
To delete the Cloud-connected integration:
Open the ST app and go to “Menu”
Go to “settings” (Gear icon in the upper-right corner) and enter “Linked services”
Click on the three-dot icon in the upper-right corner and select “unlink”. This will display a red dash/minus symbol next to each service.
Find the one you want to delete (Philips Hue in this case) and tap on the dash symbol
Fantastic reply. I guess I missed that along the journey.
It is interesting as I guess I realized this dilemma and didn’t know which way to turn and probably forgot.
Ultimately perhaps I try both options but need a starting point.
Note I also have Alexa integration and that also has duplicates.
Does it make sense to stay with hub only and remove Hue Cloud from both ST and Alexa and leave local on ST and only have the ST integration in Alexa or vise versa?
I’m not sure I understand your question, but if you leave the Hub-Connected integration, you can also have Alexa, the difference is that if there’s an Internet outage, the devices will continue working on the SmartThings side. For example, in locally executed Routines because the app requires Internet access and you won’t be able to send commands to the devices and from Alexa either.
On the contrary, if you leave the Cloud-Connected integration, the Routines won’t execute because there’s no Internet access and the devices can’t be reached.
Does this clarifies your question?
Thank you for a detailed explanation.
As I have my Smartthings routines created in the “cloud connection” I’m planning on keeping the cloud connection.
(I have made use of the brighten or fade gradually feature)
A word of caution, HUE switches are not cloned to the cloud and there are only one set of each switch in Smartthings.
Meaning that if I were to delete the Hue Bridge I fear that the switches will also disappear as there are only shown in the Hue Bridge.
That can however be a fare trade off as I can set the switches behavior directly in the Hue app.
This is not about Edge vs. Viper issue… but include VIPER now my Smartthings has done something strange.
I have 4 Wifi temp sensors and they are connected to Smartthings using Tuya Smart Life.
They have been working great before, but now… first noticed that 2 of them was changed to ‘SmartThings-smartthings-c2c-switch’ and there is now power button and no temp / humidity information.
Today noticed that all my wifi temp sensors are ‘SmartThings-smartthings-c2c-switch’ and VIPER they do no longer show any temp / humidity information, they only have power buttons.
I did as per your instruction: “To delete the Hub connected integration:”
It worked for awhile…
The Hue lights are now back in Smartthings under the “No room assigned”
Any suggestions why the lights are back in Smartthings?
Hi, @arcspin
Before they appear did you enable the discovery mode in the SmartThings Hub? I mean clicking the “scan nearby” button. I just wanted to confirm if that could’ve been the trigger.
Hello, @nayelyz
Thank you for answering my question.
When I think of it. In the near past I have had a Smartthings button going offline and I do not remember if I in trying to get it online have tried to scan nearby devices.
I will therefore delete the newly repapered items as per your earlier instruction and pay more attention to the circumstances if they appear again.
Yes, please.
LAN drivers start whenever the Hub is in discovery mode to see if there’s something to discover as they are not like Zigbee or Z-Wave devices with a fingerprint that can be compared to find the best match to control them. If the Hue bridge is constantly “announcing” itself, it could have caused the joining of the other devices.
Let me know if it happens again and submit the Hub logs as soon as you realize, please:
