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

[orangebucket (Graham)]

@btrial

child component “Loo mirror light” is working only for a day after pairing it with smartthings hub. Next day it stops working (main is still working) and is not responsive at all, and following error shown when trying to change the state:

Sounds like:

[ST Edge] EDGE_CHILD devices lose connectivity

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 …