[ST EDGE] Edge Developer needed: MCOHome MH-S312 and MH-S314

martin.borg · August 24, 2022, 4:02pm

Ok so - first results that I can report right away - whilst the new switch changed to the new driver without problems, the old ones (both S312 and S314) seemed to complain. The new S314 switch only had a warning:

2022-08-24T15:54:52.244720173+00:00 WARN MCOHome Z-Wave Switch Test 3  Changed to new profile. App restart required.

Whereas the older switches gave an error during driver change:

2022-08-24T15:58:38.699300614+00:00 ERROR MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)>:
    arg1: {args={value="OFF_DISABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x00", src_channel=0, version=1}
[string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)>:
    arg1: {args={value="OFF_DISABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x00", src_channel=0, version=1}
[string "mcohome/init.lua"]:48: attempt to perform arithmetic on a nil value (field '?')
2022-08-24T15:58:38.708868614+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler device_lifecycle
2022-08-24T15:58:38.740519948+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> received lifecycle event: infoChanged
2022-08-24T15:58:38.755814948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found DeviceLifecycleDispatcher handler in zwave_switch
2022-08-24T15:58:38.762945281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=1, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2022-08-24T15:58:38.779255614+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(ccff7a14) queued for radio transmission: CC:Association, CID:0x04
2022-08-24T15:58:38.788986614+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=1}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2022-08-24T15:58:38.806507948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(ab211203) queued for radio transmission: CC:Association, CID:0x02
2022-08-24T15:58:38.813610281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=3, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2022-08-24T15:58:38.829918948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(73a59400) queued for radio transmission: CC:Association, CID:0x04
2022-08-24T15:58:38.836685948+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=3}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2022-08-24T15:58:38.850871948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(6ad13a5c) queued for radio transmission: CC:Association, CID:0x02
2022-08-24T15:58:38.858062281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=4, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2022-08-24T15:58:38.874085948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(08b13e4d) queued for radio transmission: CC:Association, CID:0x04
2022-08-24T15:58:38.883014281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=4}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2022-08-24T15:58:38.897725948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(ccff7a14) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:38.908822614+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(b99c5e63) queued for radio transmission: CC:Association, CID:0x02
2022-08-24T15:58:38.915964281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=2, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x02", src_channel=0, version=1}
2022-08-24T15:58:38.932697281+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(5d28d7f0) queued for radio transmission: CC:Association, CID:0x04
2022-08-24T15:58:38.939411948+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> sending Z-Wave command: {args={grouping_identifier=2}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x02", src_channel=0, version=1}
2022-08-24T15:58:38.954207281+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(afd29420) queued for radio transmission: CC:Association, CID:0x02
2022-08-24T15:58:38.965861948+00:00 WARN MCOHome Z-Wave Switch Test 3  Changed to new profile. App restart required.
2022-08-24T15:58:38.973360948+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-24T15:58:39.113171615+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(ab211203) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:39.162222281+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-24T15:58:39.169607281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> received Z-Wave command: {args={grouping_identifier=1, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x01\x05\x00", src_channel=0, version=1}
2022-08-24T15:58:39.177952615+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-24T15:58:39.312989615+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(73a59400) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:39.524963615+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(6ad13a5c) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:39.562589948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-24T15:58:39.569915281+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> received Z-Wave command: {args={grouping_identifier=3, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x03\x05\x00", src_channel=0, version=1}
2022-08-24T15:58:39.578277948+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-24T15:58:39.712891948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(08b13e4d) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:39.912979282+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(b99c5e63) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:39.962184948+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-24T15:58:39.970674948+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> received Z-Wave command: {args={grouping_identifier=4, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x04\x05\x00", src_channel=0, version=1}
2022-08-24T15:58:39.979116282+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-24T15:58:40.113234615+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(5d28d7f0) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:40.313047282+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(afd29420) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T15:58:40.359369949+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-24T15:58:40.366770949+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (WYFY Switch 1: Old S314)> received Z-Wave command: {args={grouping_identifier=2, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x02\x05\x00", src_channel=0, version=1}
2022-08-24T15:58:40.375402949+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled

I am guessing this on its own might cause some problems later. Should I test the old switches nonetheless? (To be fair - this is the first time I am actually monitoring during a driver change, though).

philh30 · August 24, 2022, 4:23pm

Someone in the community posted that as a feature request several months ago, and we haven’t heard anything about progress on it. Renaming components would definitely be helpful if/when they work out the voice assistant multi-component issues.

Currently the labels have to be hard coded in the profiles in the driver. It’s possible that you could set up a different profile for each of your switches and then have a toggle to choose which one to use just like the current one between large and small dashboards. That’s outside my scope, but you’re welcome to try once we have a working driver and I post it to GitHub.

Not sure offhand what’s happening there, but I can trace the line number when I get home.

martin.borg · August 24, 2022, 4:31pm

First switch tested - the new MH-S314:

Test 1. Multi-Encap:Binary: Pressing Main - nothing happens. Switching on Switch 1 produces an error in the log as per below.

2022-08-24T16:08:29.066353820+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-24T16:08:29.075412820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"switch1","positional_args":{}}
2022-08-24T16:08:29.083992820+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-24T16:08:29.092615820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> sending Z-Wave command: {args={duration=0, target_value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="SET", dst_channels={1}, encap="AUTO", payload="\xFF\x00", src_channel=0, version=2}
2022-08-24T16:08:29.123112486+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(c2f0f8fb) queued for radio transmission: CC:Switch Binary, CID:0x01
2022-08-24T16:08:29.133894153+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: New S314 device thread event handled
2022-08-24T16:08:29.142141486+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: New S314 device thread event handled
2022-08-24T16:08:29.286866487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(c2f0f8fb) transmit status: TRANSMIT_COMPLETE_OK
2022-08-24T16:08:29.353236820+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-24T16:08:29.363020153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
2022-08-24T16:08:29.371341487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-24T16:08:29.387536153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-08-24T16:08:29.414509487+00:00 ERROR MCOHome Z-Wave Switch Test 3  WYFY Switch 1: New S314 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
[string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
[string "mcohome/init.lua"]:48: attempt to perform arithmetic on a nil value (field '?')
2022-08-24T16:08:29.433115820+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-24T16:08:29.441687820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\xFF", src_channel=1, version=1}
2022-08-24T16:08:29.467010153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-24T16:08:29.477857820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch1","state":{"value":"on"}}
2022-08-24T16:08:29.514732153+00:00 ERROR MCOHome Z-Wave Switch Test 3  WYFY Switch 1: New S314 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\xFF", src_channel=1, version=1}
[string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\xFF", src_channel=1, version=1}
[string "mcohome/init.lua"]:48: attempt to perform arithmetic on a nil value (field '?')
2022-08-24T16:08:30.144750487+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> sending Z-Wave command: {args={}, cmd_class="SWITCH_BINARY", cmd_id="GET", dst_channels={1}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-24T16:08:30.175121487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(f0608a3e) queued for radio transmission: CC:Switch Binary, CID:0x02
2022-08-24T16:08:30.180531820+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: New S314 device thread event handled
2022-08-24T16:08:30.282232487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(f0608a3e) transmit status: TRANSMIT_COMPLETE_OK

Pressing Switch2 & 3 produces a similar error. Pressing Switch4 does not produce an error and Main turns on as all switches are now on.

Then - pressing Main to turn it off produces a log but nothing happens.

2022-08-24T16:11:58.739550996+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-24T16:11:58.843943997+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
2022-08-24T16:11:58.855911663+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-24T16:11:58.862265997+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: New S314 device thread event handled

It does not go off, nor do any of the 4 buttons.

Test 2: Multi-Encap:Basic

Pressing Main - once again nothing happens. Some entries in log, but no effect on other buttons. Pressing the 4 switches one after the other turns them on, without errors this time. Main goes on when all four are on. Then - trying to tuen Main off produces an entry in the log, but nothing goes off: neither Main, nor any of the four buttons. Turning off any of the buttons also turns off Main (as it should).

Test 3: SwitchAll Exactly same as previous Test, Test 2, above.

Test 4: Individual:Binary Exactly same as previous Tests, Tests 2 & 3, above.

I restarted the app every time in between tests - to be sure the new setting worked well. Thing is that, whichever choice I made, the Main switch is not functioning as well as it was on the previous driver. So something’s not right with the current code…

I will await from your end before testing more switches as it appears likely that something is amiss.

philh30 · August 24, 2022, 4:32pm

K. Bug in the code. Hold off until I can look at it.

martin.borg · August 24, 2022, 4:34pm

Sure - thanks - I’ll have a look at your code and try to create profiles… this will only be useful for a handful of switches so I might give it a go… But yes - agreed, it’s not a priority right now. Thank you!

Sure - thanks,no worries, let me know what you find.

philh30 · August 24, 2022, 10:27pm

Same driver (Test 3), but new version is pushing out dated 2022-08-24T22:15:27.099516108.

That error was in a place that I didn’t change, so my best guess is that it’s because I’m pulling the cached most recent capability state and that the cache is cleared out with a driver swap. I’ve put in trapping so it doesn’t error out again, but it might be that the main switch doesn’t properly show state after a driver swap until each button has reported its state at least once (or been toggled a few times).
The main switch wasn’t emitting any z-wave commands because the logic to choose which type of command to send was comparing a string to an integer. Fixed and tested now, so you should actually see commands being sent.

martin.borg · August 25, 2022, 8:39am

Many thanks. Driver updated on its own this time round.

Performed some testing and looks good overall. The new S-314 works perfectly with the first three options of MAIN Switch Testing. The last option gives the expected popcorn effect.

The older MH-S314 and MH-S312 switches, the Main button does not work well for options 1 and 2 (Main still seems bound to Switch1). Option 3, on the other hand (SwitchAll) seems to work best, though a little slower than the newer MH-S314 - this may be because they are further from the hub, but also, these switches have worked notoriously slowly for me with Smartthings since the very start. (With another competing hub they worked better, admittedly). Still, option 3 works best and switches on all buttons simultaneously when Main is switched on, and switches off all buttons simultaneously when Main is switched off. The last option gives the popcorn effect, as expected.

I noticed some noticeable delays when using the switches through the app, but to be fair, this has always been the case. When using the switches through physical interaction with the switch, the state updated very quickly (not instantly but let’s say after a second or so) on the app. When used through automations, it was a bit slower but acceptable. When used via the app - it was the slowest. I would say, off-hand, that our switch-toggling activity originates 60% through physical interaction, 30% through Routines, and 10% via the app - so we will live with a slight delay. In any case, it seems the app suffers the most - e.g. if a Routine is supposed to turn on one button, it does so say after a second or so, but on the app it could easily take 5 seconds to reflect the new state. (All of this has to be taken in the context of these switches being quite far from the hub and therefore likely needing a few hops to reach the hub every time, and the routines were run using an Aeotec Wallmote Quad in the same location or via Edge virtual switches - but using the app. I could only afford to dedicate a couple of switches in the basement for this exercise.)

Given all of the above, I would say I will try to make use of associations as much as possible for 2/3-way lighting, as this will certainly induce better performance unless it requires more complex rules (e.g. depending on time), but in most cases it’s just switches mirroring each other. For other non-very-time-sensitive applications, such as switching on a pump somewhere, I will do it by way of Routine, as the effect will barely be felt even if I know about it.

So I would say that by default, the newer fingerprint switch should take Option 1, whereas the older fingerprints should by default take Option 3. If it is possible to leave those MAIN switch command options visible and adopt a default option based on the fingerprint, it would be great. If not, I guess you can hardcode an option based on the fingerprint.

The only remaining flaws would be:

That spiral - keeps happening when trying to use the switches from the app, but as i said - this is rare, and as you said, this is likely an app issue. Hope it is fixed soon as I do not see why I am getting that spiral even after the switch has toggled on the app itself - so the app knows that the state has already changed. Mind-boggling, but not your issue.
The polling. Not sure this will even work with 1-hour polling. I have seen the switch go offline even say 15 minutes after last being used. Perhaps that’s why the old DTH had those refreshes and defaulted to one minute, but a refresh seems to be taxing on the hub (from what I could see from the logs) and I had no option to disable it for the old switches - which certainly do not seem to require it, but at least set it to every 1 hour for every switch (still, that’s over 40 refreshes an hour which I will happily avoid in future). Not sure what a happy medium can be here.

Anyhow - sorry for the long post, but I am very pleased with the outcome, many thanks!

martin.borg · August 25, 2022, 8:57am

I will try to do some testing of associations by this weekend, though that will involve converting more switches to the latest Edge driver and taking care of any associated Routines, so it will take me some time.

If I understood Associations correctly, if I want button 1 on Switch with Zwave ID 46 to mirror itself to buttons 1 and 2 on switch with Zwave ID 4B, as well as to buttons 3 and 4 on switch with Zwave ID 3E then in the Association Group 1 of the triggering Switch (46), I will need to enter something as follows:

4B:1,4B:2,3E:3,3E:4,1

The latter 1 being the ZWave ID of the hub. Is this correct? @JDRoberts might correct me on this one

JDRoberts · August 25, 2022, 10:25am

Before we get too far down the rabbit hole (and I understand it may already too late), in the zwave specification, Main would be referred to as endpoint 0. Not endpoint 1. But based on previous conversations I suspect that ST has always changed this in its abstraction layer, adding a lot of confusion.

philh30 · August 25, 2022, 11:36am

If you’re just testing, you could set up association on any of the devices already on this driver and have them control any other device (DTH or Edge). The association groups may get wiped out when we swap to the last driver version though, and node IDs will change for any devices that you exclude/include, so don’t try to set everything up permanently until everything is on the final Edge driver.

One thing to be aware of is that Association doesn’t work between devices of different security levels (most new z-wave devices will support S2). None of these switches, including the newer one, support any security, so you won’t run into this problem when the MCOHome devices are controlling each other. But if you bring any newer devices into the mix you might run into this roadblock.

The hub should only need to be added to the lifeline association group (normally association group 1, but group 1, 3, or 5 with these devices). I didn’t open up access to the lifeline association group in settings, so you shouldn’t need to add the hub to any groups. The rest looks correct:

philh30 · August 25, 2022, 11:46am

My preference would be to hardcode the best option for each, since the setting is a bit technical and might confuse someone else who uses this driver. I can leave it in though if you feel strongly about it.

My plan is to put an option in settings for the interval in minutes between polls. Setting it to 0 will disable polling.

martin.borg · August 25, 2022, 12:39pm

Thank you very much for the info… Will certainly put in some time before the end of the weekend to get this finally tested. I am certain that this was the case - i.e. these switches were paired through associations when they were connected to a different-brand hub, because the mirroring was instant, and any delay was not humanly detectable. We’ll see how it goes.

Then leave it as it is, no worries, I don’t feel too strongly about it, just thought it might be useful for users who got different versions of these switches as I know there are some other fingerprints out there for these switches. Hardcoded is good enough for me - I tried enough testing to make sure that is the best setting for each model.

Yes! That would be great, thank you! I will start off with a 15minute interval and see how that works out.

I am so very grateful for all this work. I hope other users out there who have suffered in the past will manage to find this thread and install this driver.

martin.borg · August 25, 2022, 1:45pm

Hi @philh30, went ahead and tested associations, but the result is not clear, at least to me.

SoI went ahead and used the old S314 (ID: 46) and the old S312 (ID: 4B) already using your latest test driver. I set up the Association Group 1 of the S314 switch to 4B:1, and tested. nothing happened, like there was no change at all.

Then I thought I should test without the endpoint, so I set it to just 4B. Curiously, button 1 of the S314 was now able to turn on and off button 1 of the S312 - instantly. Then I tried again, and to be fair (just in case I understood anything wrong), I tried a number of options: 4B:0, 4B:1, 4B:2 etc. through 4B:6. nothing worked. Only 4B (the node on its own) seems to work.

I mean - yes, at least I got it to work, but I am a bit limited now in terms of what is achievable. So I am not sure the older switches can take associations in this manner. Let me know what you think please.

philh30 · August 25, 2022, 1:53pm

Could you capture logs while changing the association group in the settings menu? I’ve used my association function with no endpoints in multiple drivers, but adding the endpoints is new (and I don’t have a device to test on). For the logs, try changing the group to something that includes a combination of endpoint and non-endpoint such as 4B:1,3E,4B:2. I just want logs from the setting being changed - no need to toggle any switches.

martin.borg · August 25, 2022, 2:21pm

Will do, but here’s a curious finding in the meantime.

I decided to ramp up the testing and I changed the setting “4B:2” to “4B,4B:2”. Curiously, it worked for me, and flicking switch 1 on the old S314 now turned on Switch1 and Switch2 on the old old S312. Obviously - this is not convenient as it would mean I have to include the first button of the destination switch ay time I wanted to remotely control a button on a switch.

I then had the idea to change 4B to 1, so that the settings are now, for the old S314, as follows:

Association group 1: “1,4B:1”
Association group 2: “1,4B:2”
Association group 3: No setting
Association group 4: No setting

And now it works. Button 1 of the S314 turns on/off Button 1 of the S312, and Button 2 of the S314 turns on/off Button 2 of the S312. How and why this works - I simply have no clue.

Still - I will send the logs, but even if you do not manage to resolve it, I now know that by including “1,” at the start of the Association Group setting, I should be fine.

martin.borg · August 25, 2022, 2:40pm

Just did this, and the following is the result (setting the Asociation Group 1 setting only, no toggling):

? Select a driver. 7
connecting... connected
2022-08-25T14:36:30.864582252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler device_lifecycle
2022-08-25T14:36:30.899120252+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received lifecycle event: infoChanged
2022-08-25T14:36:30.911285585+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found DeviceLifecycleDispatcher handler in zwave_switch
2022-08-25T14:36:30.924192919+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=1, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2022-08-25T14:36:30.940603585+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(990ead6a) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:36:30.949800919+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=1, multi_channel_nodes={{bit_address=false, end_point=1, multi_channel_node_id=75}, {bit_address=false, end_point=2, multi_channel_node_id=75}}, node_ids={62}}, cmd_class="MULTI_CHANNEL_ASSOCIATION", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x01\x3E\x00\x4B\x01\x4B\x02", src_channel=0, version=2}
2022-08-25T14:36:30.965701252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(b5bb7e42) queued for radio transmission: CC:Multi-Channel Association, CID:0x01
2022-08-25T14:36:30.972605585+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=1}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2022-08-25T14:36:30.987367252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(bf919741) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:36:30.994361919+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=4, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2022-08-25T14:36:31.010731585+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(7f2dbb61) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:36:31.020111585+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=4}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2022-08-25T14:36:31.036347919+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(0d32c706) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:36:31.043328252+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=3, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2022-08-25T14:36:31.059787919+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(e9645a0e) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:36:31.066631585+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=3}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2022-08-25T14:36:31.081500252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(1a14a5da) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:36:31.088823252+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=2, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x02", src_channel=0, version=1}
2022-08-25T14:36:31.105089919+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(320e09a5) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:36:31.112634919+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=2}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x02", src_channel=0, version=1}
2022-08-25T14:36:31.127072252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(abda5837) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:36:31.147051252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(990ead6a) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:31.149341585+00:00 WARN MCOHome Z-Wave Switch Test 3  Changed to new profile. App restart required.
2022-08-25T14:36:31.157521919+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:36:31.350367919+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(b5bb7e42) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:31.540321585+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(bf919741) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:31.624637252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:36:31.633745919+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=1, max_nodes_supported=5, node_ids={62}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x01\x05\x00\x3E", src_channel=0, version=1}
2022-08-25T14:36:31.642050919+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:36:31.750426252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(7f2dbb61) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:31.940250919+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(0d32c706) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:31.999869252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:36:32.008107252+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=4, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x04\x05\x00", src_channel=0, version=1}
2022-08-25T14:36:32.015562252+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:36:32.150294252+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(e9645a0e) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:32.340288253+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(1a14a5da) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:32.399820253+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:36:32.409017586+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=3, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x03\x05\x00", src_channel=0, version=1}
2022-08-25T14:36:32.416492919+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:36:32.550292253+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(320e09a5) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:32.740301253+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(abda5837) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:36:32.796348253+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:36:32.805853586+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=2, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x02\x05\x00", src_channel=0, version=1}
2022-08-25T14:36:32.814551586+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled

Hope this helps. Meanwhile, though, note that it works. Pressing button one on the switch I just set to have the 4B:1,3E,4B:2 setting now turns on switches 1 & 2 on the S312 switch, and switch one on node 3E. Funny. Seems like the only way it does not work if it has one node and one endpoint set up.

philh30 · August 25, 2022, 2:43pm

Interesting. It looks like it’s only not working when your list is just endpoints. If you could send logs with just endpoints then that’ll be good.

martin.borg · August 25, 2022, 2:44pm

Ok - reset the same setting to just “4B:1” for now, will send logs.

martin.borg · August 25, 2022, 2:48pm

This is when I set the association group setting to “4B:1”:

? Select a driver. 7
connecting... connected
2022-08-25T14:46:05.999734877+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler device_lifecycle
2022-08-25T14:46:06.097650211+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received lifecycle event: infoChanged
2022-08-25T14:46:06.111240211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found DeviceLifecycleDispatcher handler in zwave_switch
2022-08-25T14:46:06.131654544+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=1, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2022-08-25T14:46:06.167091211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(b3218988) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:46:06.191271544+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=1}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x01", src_channel=0, version=1}
2022-08-25T14:46:06.206741877+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(a7606b30) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:46:06.220489877+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=4, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2022-08-25T14:46:06.245603877+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(552502c9) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:46:06.263852877+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=4}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x04", src_channel=0, version=1}
2022-08-25T14:46:06.285279544+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(231b0814) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:46:06.301517877+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=3, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2022-08-25T14:46:06.328428544+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(cd4601ec) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:46:06.339205211+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=3}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x03", src_channel=0, version=1}
2022-08-25T14:46:06.367718211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(46d3d28b) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:46:06.389295211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(b3218988) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:06.398858544+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=2, node_ids={}}, cmd_class="ASSOCIATION", cmd_id="REMOVE", dst_channels={}, encap="AUTO", payload="\x02", src_channel=0, version=1}
2022-08-25T14:46:06.419849211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(e374b89c) queued for radio transmission: CC:Association, CID:0x04
2022-08-25T14:46:06.440950878+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={grouping_identifier=2}, cmd_class="ASSOCIATION", cmd_id="GET", dst_channels={}, encap="AUTO", payload="\x02", src_channel=0, version=1}
2022-08-25T14:46:06.476311211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(56e857d5) queued for radio transmission: CC:Association, CID:0x02
2022-08-25T14:46:06.493958878+00:00 WARN MCOHome Z-Wave Switch Test 3  Changed to new profile. App restart required.
2022-08-25T14:46:06.505317878+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:46:06.551458211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(a7606b30) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:06.610862544+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:46:06.618172878+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=1, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x01\x05\x00", src_channel=0, version=1}
2022-08-25T14:46:06.625512878+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:46:06.760198211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(552502c9) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:06.950268544+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(231b0814) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:07.019507211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:46:07.027754878+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=4, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x04\x05\x00", src_channel=0, version=1}
2022-08-25T14:46:07.035389878+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:46:07.340262211+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(cd4601ec) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:07.550246545+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(46d3d28b) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:07.599479545+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:46:07.608008545+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=3, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x03\x05\x00", src_channel=0, version=1}
2022-08-25T14:46:07.616422878+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:46:07.760273878+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(e374b89c) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:07.950238878+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(56e857d5) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:46:07.996340545+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:46:08.004422545+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={grouping_identifier=2, max_nodes_supported=5, node_ids={}, reports_to_follow=0}, cmd_class="ASSOCIATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x02\x05\x00", src_channel=0, version=1}
2022-08-25T14:46:08.012939878+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled

And this is when I toggled to on:

2022-08-25T14:47:42.676537590+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-25T14:47:42.685339923+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received command: {"args":{},"capability":"switch","command":"on","component":"switch1","positional_args":{}}
2022-08-25T14:47:42.691724590+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-25T14:47:42.699238923+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={duration=0, target_value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="SET", dst_channels={1}, encap="AUTO", payload="\xFF\x00", src_channel=0, version=2}
2022-08-25T14:47:42.714192257+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(1a0bf6fc) queued for radio transmission: CC:Switch Binary, CID:0x01
2022-08-25T14:47:42.726654923+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:47:42.733368923+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:47:42.980504924+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(1a0bf6fc) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:47:43.026989257+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:47:43.035690590+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
2022-08-25T14:47:43.044479590+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-25T14:47:43.051474590+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-08-25T14:47:43.069593924+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-25T14:47:43.126079257+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:47:43.133101924+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:47:43.142117257+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\xFF", src_channel=1, version=1}
2022-08-25T14:47:43.163750257+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-25T14:47:43.169870590+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch1","state":{"value":"on"}}
2022-08-25T14:47:43.187640590+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-25T14:47:43.203906590+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:47:43.740364591+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> sending Z-Wave command: {args={}, cmd_class="SWITCH_BINARY", cmd_id="GET", dst_channels={1}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-25T14:47:43.756673257+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(6cd56bfe) queued for radio transmission: CC:Switch Binary, CID:0x02
2022-08-25T14:47:43.762119924+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled
2022-08-25T14:47:43.954161924+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(6cd56bfe) transmit status: TRANSMIT_COMPLETE_OK
2022-08-25T14:47:44.008154257+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-25T14:47:44.019554591+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> received Z-Wave command: {args={value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={0}, encap="NONE", payload="\xFF", src_channel=1, version=1}
2022-08-25T14:47:44.038272924+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-25T14:47:44.044480591+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch1","state":{"value":"on"}}
2022-08-25T14:47:44.059731591+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: c5da609d-2a53-4e90-a4c0-d640d1f5ac19 [46] (MCOHome: Old MH-S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-25T14:47:44.077108591+00:00 DEBUG MCOHome Z-Wave Switch Test 3  WYFY Switch 1: Old S314 device thread event handled

Hope it helps.

JDRoberts · August 25, 2022, 2:57pm

As I mentioned at the very beginning, it is common to add the hub to every association group to reduce the amount of polling needed and help keep app status up to date. That way any button press does get communicated to the hub.

For example, there have been multiple members over the years who had zwave switches where dimming from the auxiliary switch wasn’t affecting app state. The fix was almost always adding the hub manually to the dimming group.

But it doesn’t work for all devices, and I don’t know about this one specifically.

Topic		Replies	Views
MCO Home MH-S312 and MH-S314 - Anyone has these working properly? Devices & Integrations	61	4077	October 22, 2021
[Edge drivers] MCO Home switch MH-S311, MH-S312 & MH-S314 Support	51	1996	June 20, 2024
[ST Edge] Issue with the Z-Wave Switch driver Support	61	3995	August 24, 2023
[ST Edge] Issues with multi-component devices and third-party integrations Support edge-device	44	5609	November 9, 2022
[OBSOLETE] MCO Z-Wave switch (DTH in post 31) Devices & Integrations dth_lighting	80	13888	November 4, 2021

[ST EDGE] Edge Developer needed: MCOHome MH-S312 and MH-S314

Related topics