Dual Gang Yagusmart Zigbee Switch goes offline after an hour and needs reset

Devices & Integrations
21

No they are not.

I have “create single device” enabled and “single tile switch”.

Interestingly switch 1 is the one that seems to lose connectivity, whereas switch 2 seems to be working fine well, the 2nd device anyway. Neither work on the page that shows the two switches and the “all” toggle button

22

@Mark_McGee

I forgot, which hub are you using v2, v3 or smartthings smart wifi?

23

I’m using the Aeotec hub

1 Like
24

@Mark_McGee

This device has nothing non-standard and has been added to the driver a long time ago, more than a year and no one has complained.

Try to reboot the hub.

You can also try installing this version Zigbee Multi Switch and Child Mc-(OLD).
NOTE: Before changing to this version of the driver you must delete the child device for switch2, they are incompatible

1 Like
25

Hub has been on and off many times.

I originally was using the old driver and changed to the new one today.

26

I can’t think of anything that could happen.
If you want to send me some logs with the CLI when it is failing, I can analyze them to see if anything can be seen

27

Would love to…how do I fire up the CLI?

28

This is a tutorial to install CLI in Windows and how see the driver logs

29

Ok, thanks. Will try that tomorrow.

1 Like
30

Hi

I have been logging today I turned the power off then on again to get the switch to be responsive, and turned the 2 switches (2-gang) on and off from the smartthings app.

Then at 9:12 tried again and I got a network error, and unresponsive.

31

log file:
2023-02-07T08:51:29.565606727+00:00 DEBUG Zigbee Multi Switch and Child Mc driver device thread event handled
2023-02-07T08:51:59.566801741+00:00 DEBUG Zigbee Multi Switch and Child Mc driver device thread event handled
2023-02-07T08:52:21.967806419+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2023-02-07T08:52:21.980157086+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> received lifecycle event: infoChanged
2023-02-07T08:52:21.981517419+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2023-02-07T08:52:21.982704752+00:00 PRINT Zigbee Multi Switch and Child Mc Device ID <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)>
2023-02-07T08:52:21.983882752+00:00 PRINT Zigbee Multi Switch and Child Mc Manufacturer >>> 3A Smart Home DE Manufacturer_Len >>> 16
2023-02-07T08:52:22.000795086+00:00 PRINT Zigbee Multi Switch and Child Mc Model >>> LXN-2S27LX1.0 Model_len >>> 13
2023-02-07T08:52:22.001643752+00:00 PRINT Zigbee Multi Switch and Child Mc Memory >>>>>>> 972.134765625 Kbytes
2023-02-07T08:52:22.002995086+00:00 PRINT Zigbee Multi Switch and Child Mc <<<<< Firmware Version >>>>> Unknown
2023-02-07T08:52:22.004224752+00:00 DEBUG Zigbee Multi Switch and Child Mc 3A Smart 2 Switch device thread event handled
2023-02-07T08:52:22.005879752+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2023-02-07T08:52:22.007067419+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> received lifecycle event: doConfigure
2023-02-07T08:52:22.039657752+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2023-02-07T08:52:22.040775419+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB866, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: D8220211E00BFDB0, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D970002090FEC, dest_endpoint: 0x01 > > >
2023-02-07T08:52:22.088756752+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB866, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2023-02-07T08:52:22.144740086+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB866, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: D8220211E00BFDB0, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D970002090FEC, dest_endpoint: 0x01 > > >
2023-02-07T08:52:22.209154752+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xB866, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2023-02-07T08:52:22.270344752+00:00 DEBUG Zigbee Multi Switch and Child Mc 3A Smart 2 Switch device thread event handled
2023-02-07T08:52:22.271731752+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2023-02-07T08:52:22.272969086+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xB866, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCA, rssi: -40, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x43 >, < BindRequestResponse || status: 0x00 > > >
2023-02-07T09:12:20.633822756+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2023-02-07T09:12:20.672712756+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2023-02-07T09:12:20.680480422+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2023-02-07T09:12:20.698357089+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< On command Handler >>>>
2023-02-07T09:12:20.699207422+00:00 DEBUG Zigbee Multi Switch and Child Mc 3A Smart 2 Switch device thread event handled
2023-02-07T09:12:29.849273090+00:00 DEBUG Zigbee Multi Switch and Child Mc driver device thread event handled
2023-02-07T09:12:39.223241758+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2023-02-07T09:12:39.302698758+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xB866, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -46, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2023-02-07T09:12:39.335871091+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2023-02-07T09:12:39.336733091+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2023-02-07T09:12:39.338549424+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2023-02-07T09:12:39.339742758+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/02/07 Time: 09:12
DNI: 0xB866 LQI: 208 RSSI: -46dbm
”},“visibility”:{“displayed”:false}}
2023-02-07T09:12:39.371742758+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2023-02-07T09:12:39.405440091+00:00 DEBUG Zigbee Multi Switch and Child Mc 3A Smart 2 Switch device thread event handled
2023-02-07T09:12:39.406316424+00:00 DEBUG Zigbee Multi Switch and Child Mc 3A Smart 2 Switch device thread event handled
2023-02-07T09:12:41.420257758+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2023-02-07T09:12:41.431281758+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: d0488395-8315-4fe2-89d8-9314f46e3d6f [0xB866] (3A Smart 2 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2023-02-07T09:12:41.450161425+00:00 DEBUG Zigbee Multi Switch and Child Mc 3A Smart 2 Switch device thread event handled
2023-02-07T09:12:41.794350758+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee

32

@Mark_McGee
I see in the logs:

  • The configuration is sent at 08:52 to the two switches and it responds well to the binding but does not reply anything to the configuration.
  • At 09:12:20 an On command is received from app for switch main, and the driver sends it. The device doesn’t receive or nor execute it and there is no response from the device.
  • At 09:12:39 a message is received from the switch2 device reporting that it is Off and the driver emits the event for switch2 and 2 seconds later for the “All Off” switch.

Does this correspond to the actions you have taken?

Either it is a network problem with this device or the device does not work correctly on the receiving side.

I would try to pair it and test it near the hub or change the zigbee channel in the Hub from the IDE

33

Thanks for looking. I don’t recall hitting the “all” switch. Network issues with this device seem to be prevelant.

I’ve paire/deleted repaired many times and it is 5m from the hub.

How do I change the channel?

34

in IDE, hub, utilities

Screenshot_20230207-145439
Screenshot_20230207-1454391023×2048 335 KB

do not use Channel 25, some devices does not work with it

1 Like
35

So…I gave up on that and swiched to a Aeotec Dual Nano switch.

This seems to have its own issues now. Have tried the new and old MC driver. It’s showing “Main” and “Switch1” but they both seem to control the same output.

It’s not showing 2 switches in the multi-tile either, so seems to not be picking up the endpoints properly?

When pressing the physical switch, I can switch the individual circuits just fine.

Screenshot_20230207-161749
Screenshot_20230207-1617491080×2280 237 KB

Screenshot_20230207-161744
Screenshot_20230207-1617441080×2280 229 KB

36

@Mark_McGee

Are you tried with stock driver Zwave Switch?

37

That didn’t come up as a driver option.

I could change on the IDE. Is it just a standard Zwave switch then - that will pick up the dual and energy reading?

38

You need install stock driver Z-Wave Switch stock driver from smartthing beta channel

39

ok, thanks

40

Ok I did that. Only shows one switch unfortunately