Noticed that my hub has many devices dubled, meaning some are correctly placed to rooms and some of those devices have clone and that copy is placed to ‘No room’
Noticed that devices that are placed to correct rooms have Type: EDGE_CHILD
Noticed that devices that are placed to ‘No room’ have Type: VIPER
Why some devices have EDGE_CHILD and VIPER twins?
Can I delete extra copys?
VIPER devices are usually those that come from a cloud-> cloud integration. Did you convert some devices from cloud integration to Edge? Or perhaps they were moved to a native Edge driver during the migration.
The VIPER device type is for devices implemented using a cloud to cloud schema integration. So we are talking about WiFi devices linked to the manufacturers cloud, or Zigbee/Z-Wave devices linked to the manufacturers hub and in turn to the manufacturers cloud, with the integration to SmartThings at the cloud to cloud level. Either way the integration is likely to appear as a ‘Linked Service’ in the app.
The EDGE_CHILD type is used for Zigbee/Z-Wave devices connected directly to the SmartThings hub that have multiple components that are presented as separate devices. So the EDGE_CHILD devices are the equivalent of the child devices that were created for device handlers and they will have a ZIGBEE or ZWAVE parent device.
Why do you have both? Difficult to speculate without knowing what the particular devices are and what you have done in the past to integrate them with SmartThings. Should you delete one? Not until you know which one and why.
I have HUE hub and Smartthings hub.
Now looks like devices that are connected to HUE are cloned to VIPER type and EDGE_CHILD type devices.
I have not done any merging or driver updating… except installed some drivers to connect Lidl and Tuya zigbee devices to Smartthings hub.
I did delete 2 devices that were VIPER type and their EDGE_CHILD versions are still working ok.
My HUE lamps are visible in Smartthings hub as EDGE_CHILD and VIPER, both Execution Location is CLOUD.
Do you have Execution Location : LOCAL ?
I would like to have all possible as LOCAL, but never bothered to check how-to-make-devices-local or is that even possible.
I have zigbee, z-wave and Tyua Wifi devices, manufacturers are IKEA, Shelly, Philips HUE, Lidl, Fibaro and Tyua (AliExpress cheap sensors).
I have not installed Lidl hub in my system, but some Lidl devices are in use.
Mine are showing Cloud, but I read that Edge drivers always run local. This label is wrong in my opinion. The LAN driver is just that… LAN (local). Local Area Network!
As Paul_Olivier is saying, it does not add up.
Also, looking at your screenshot, I see the bedroom-lamp as OFFLINE in C2C mode (VIPER) and ONLINE in the LAN mode (EDGE_CHILD). I had the same behaviour.
Since, I have deleted my VIPER ones, my HUE lamps show ONLINE even if they are not powered. An issue with the BETA LAN driver, I would guess. But not problematic for me. That they respond quick is important.
The executingLocally flag in the device object is a boolean that is defined in the API reference as being true if the device executes locally on the hub. The API reference has nothing to say on what false means.
I don’t know whether an EDGE_CHILD device having that flag set to false (assuming that is the source of the Local/Cloud info) is correct or not.
I do consider that assuming false means Cloud is incorrect as the API is documented.
We reported the issue mentioned here: TYPE: Edge_child vs. Viper - #10 by Pk1 about the “cloud” execution for the “EDGE_CHILD” device type since we saw that in some samples of child devices we have the “executingLocally” flag is set to “true” but the Advanced Users app says otherwise.
Thank you for sharing it
The team hasn’t provided feedback about this, I would think they’re still checking what happened in your case, if you delete any devices they won’t be able to see what happened. But, it’s also up to you.
I don’t have enough information to confirm this. I know both are different types of integration (Viper - Cloud connected and Edge-child/LAN - Hub connected) but I don’t know which one was there first in your case and what made it both to be included in your account…
Hi @nayelyz I’m having the same issue with all my Hue devices. It feels like this occurred during the recent migration. Also, since the migration, I feel like we have a lot less control to edit the devices to fix them ourselves possibly? I have many devices where if I could just edit their “type” or “device profile” I could fix a lot of issues. What’s the best way now to edit handlers and things like we could before this migration?
Currently, only devices of protocols Zigbee or Z-Wave are the ones that support a change in the driver which could be considered similar to changing the device type.
However, it will only work if the new driver contains the device’s fingerprints which wasn’t the case with a DTH.
Now, LAN (the type of the parent device - Hue bridge) and VIPER integrations don’t support a change in the driver, the first can show the option to do so but you can make devices become unresponsive.
VIPER doesn’t use drivers so, that one won’t have an option to change what controls it because it is the only option.
Those devices of type “VIPER” should work correctly, the ones using the Edge driver are the only ones with the issue. So, have you tried using those?
For example, this one: