[ST Edge] EDGE_CHILD devices lose connectivity

[jds13 (Jonathan)]

I’m using the SmartThings Drivers (Beta) channel zwave-switch driver. Maybe this report will help a developer somewhere… Is this the right place to report it?

For the last week or so, when I “include” a Qubino Flush 2 dual relay I get two devices - the primary, named “Qubino Switch 1” (QS1), is a conventional switch with type ‘ZWAVE’. The secondary, QS2, has type ‘EDGE_CHILD’. QS2 has an edgeChild section with the same driver as QS1 (2cbf55e3-dbc2-48a2-8be5-4c3ce756b692) and a parentDeviceId that points to QS1. Similarly, QS1 has one entry in a childDevices section that points to QS2.

This new model is all great, and much easier to use than the old model which required a paired virtual switch and synchronizing routines. Changing to this driver always creates a new child (confusing!) but that’s OK.

Everything works fine… for a while. But after some interval - six hours? Maybe certain intervening events? - QS2, the child device, becomes unresponsive in certain ways: on/off commands don’t work, and status changes aren’t reported.

Running logcat on the driver shows no activity when I execute a command (on or off) from the Android app or Google Assistant. Using the physical switch attached to the relay does trigger a (threshold-triggered?) new power report - but the change is not reflected in the Android app.

I have a V2 hub firmware 45.11. I’d be pleased to provide any logs that might be helpful.

Thanks for an amazing set of products and a smooth transition. All of my devices are now on Edge and everything works great except this one issue.

[orangebucket (Graham)]

That’s interesting, when I was messing with Edge drivers as a local VIRTUAL device I had a broadly similar experience. Worked fine to start with but when I revisited a few hours later they had completely stopped responding. The difference in my case is that no one had ever said they were supposed to work and I was just guessing. That’s probably digressing though.

I’ll tag @nayelyz and @andresg as they’ll know who to nudge and it may have implications for developers who have their eyes on EDGE_CHILD for their own purposes.

[nayelyz (SmartThings Developer Support)]

Hi, @jds13!

The team mentioned they need to analyze this further, so, please share the following:

1. Is the child device still faulty?
   • If so, can you replicate executing a command for the device and use the physical device, please? This is to get the logs about that registered in the Hub, this would be different than the driver’s log.
2. After replicating the steps in #1, send the logs from the IDE:

1. In the IDE, enter “my hubs”
2. Enter the corresponding Hub and go to “view utilities”
3. Click on “send” below "send hub logs

3. Confirm the email account registered in the forum is the same one you use for SmartThings.
4. Provide access to your account:

1. Go to the SmartThings Web (my.smartthings.com)
2. Log in to your Samsung Account
3. Select Menu (⋮) and choose Settings
4. Toggle on Account Data Access
5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

Thanks for tagging me, @orangebucket!

[jds13 (Jonathan)]

Is the child device still faulty?

Yes

If so, can you replicate executing a command for the device and use the physical device, please? This is to get the logs about that registered in the Hub, this would be different than the driver’s log.

All times are UTC. 2022-11-02:

• 21:51 Turn child on with physical button (child turns on)
• 21:52 Turn child off with physical button (child turns off)
• 21:53 Turn child off with app (“A network or server error occurred. Try again later.” Child stays off.)
• 21:54 Turn parent off from web app (parent goes off)
• 21:55 Turn child off from web app (No error. Child stays off.)

After replicating the steps in #1, send the logs from the IDE:

Done.

Confirm the email account registered in the forum is the same one you use for SmartThings.

Yes

Provide access to your account:

Done.

[nayelyz (SmartThings Developer Support)]

Thank you for the info, @jds13.
Can you share the name of those devices, please? I thought they remained to be QS1 and QS2.
It can be through a DM

[jds13 (Jonathan)]

QS1 = “Desk”
QS2 = “Floor”

[nayelyz (SmartThings Developer Support)]

Thank you, @jds13, I already created the report for the team about this. Once we get more info, we’ll let you know.

[nayelyz (SmartThings Developer Support)]

Hi, @jds13
Following up on your case, the team mentioned they need your help by reproducing the issue, this means:

1. Remove the device, and its children (to “start fresh”)
2. Re-add the device
3. Switch drivers as you previously did

This is because they enabled more logging in the Hub because they need extra information.
Please, let me know when you finish.

[jds13 (Jonathan)]

At 11:50 PST I removed Qubino Switch 2 (Floor) (No confirmation required)
At 11:51 Next I removed Qubino Switch 1 (Desk) (It took two tries of triple-pressing button 1)

At 11:53 I added the device. Two devices appear. Shortly afterward I switched the driver on Qubino Switch 1. I now have two Qubino Switch 2’s - one in the room where I added/switched the driver (“Downstairs”) and the other in “No Room Assigned.”

I sent the logs.

To be clear: the problem I was reporting wasn’t about switching drivers. It was that the second relay - Qubino Switch 2 - “Floor” - stopped responding to hub commands after a while.

[btrial (Bartek)]

@nayelyz
I have the same problems with Neo Coolcam double switch, and described it in here:

[ST Edge] Issues with multi-component devices and third-party integrations

Hi @nayelyz I have noticed that my Neo Coolcam double switch after repairing have been added as two separate components instead one multi component as before. I also see some commits into zwave-dual-switch which is used by Neo coolcam fingerprint, which would suggest such change too: History for drivers/SmartThings/zwave-switch/src/zwave-dual-switch - SmartThingsCommunity/SmartThingsEdgeDrivers · GitHub It is a great information that those multicomponent switches are going to be handled as separate components but for now it doesn’t seem to work as expected. Problems which I have noticed so far are: child “Switch 1” elements are still shown in main component (but unusable) as shown below on first screenshot even though child component “Loo mirror light” is seperated as shown on screens…

as I haven’t seen this topic before.

[nayelyz (SmartThings Developer Support)]

@jds13

To be clear: the problem I was reporting wasn’t about switching drivers. It was that the second relay - Qubino Switch 2 - “Floor” - stopped responding to hub commands after a while.

Yes, we have this in mind, but reproducing all your steps with the new logging enabled can provide more info about what caused the device to stop working.

[nayelyz (SmartThings Developer Support)]

@btrial

I have the same problems with Neo Coolcam double switch, and described it in here:

Hi, @btrial. Sorry for the delay.
I checked your description and I need the following details, please:

@btrial

child “Switch 1” elements are still shown in main component (but unusable) as shown below on first screenshot even though child component “Loo mirror light” is seperated as shown on screenshot 2:

1. which driver is the device using?
2. Do you know the fingerprints of the device? This is to know which device profile is assigned to it.
   There are two double-switch Neo Coolcam devices: https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/blob/main/drivers/SmartThings/zwave-switch/fingerprints.yml#L128
3. Access to your account to see the details of your devices:

1. Go to the SmartThings Web (my.smartthings.com)
2. Log in to your Samsung Account
3. Select Menu (⋮) and choose Settings
4. Toggle on Account Data Access
5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

[btrial (Bartek)]

Hi @nayelyz

1. the driver used is edge “zwave-switch” from smarthings edge beta channel,
2. the fingerpring will be this one:

• id: 0258/0003/108B
  deviceLabel: NEO Coolcam Switch 1
  manufacturerId: 0x0258
  productType: 0x0003
  productId: 0x108B
  deviceProfileName: dual-switch

3. “Account Data Access” granted.

[btrial (Bartek)]

Hi @nayelyz
Any update so far ? Or is anything else needed from our side.

[jds13 (Jonathan)]

My Qubino EDGE_CHILD switches just started working again. Thanks!

[nayelyz (SmartThings Developer Support)]

Sorry for the delay, @btrial, the team mentioned they made a modification for the issues with child devices being unresponsive after a while. So, they should be working now, if you still see issues, please try to install the device again and let us know your results.

Thank you for the feedback, @jds13

[btrial (Bartek)]

Hi @nayelyz
Yes, all devices work fine now and they don’t loose connection. But the main switch still shows child “Switch 1” element even though it is not usable here. It is not a problem though from usage point of view.

[Mariano_Colmenarejo]

@btrial

But the main switch still shows child “Switch 1” element even though it is not usable here. It is not a problem though from usage point of view.

Hi @btrial

If you use Android App that should be solved by clearing the cache of the app

[btrial (Bartek)]

Yes I am on android, but neither clearing the cache nor the whole storage helps.

[Mariano_Colmenarejo]

@btrial

Yes I am on android, but neither clearing the cache nor the whole storage help

In fact, it was not corrected because smartthings forgot to delete the switch1 component in the dual-switch profile or create a single switch profile for it.

name: dual-switch
components:
  - id: main
    capabilities:
    - id: switch
      version: 1
    - id: refresh
      version: 1
    categories:
    - name: Switch
  - id: switch1
    capabilities:
    - id: switch
      version: 1
    categories:
    - name: Switch