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

[philh30]

Excellent progress!!!

@martin.borg

The newer switch - the single MH-S 314 (newer Z-wave Plus model) - 015F/3141/5102, is sometimes appearing offline/disconnected

There’s a chance this will be resolved once we get the Lifeline association group set correctly, or when I get the driver cleaned up. The next driver version I post will support all three models, and if you continue having this problem at that point then we’ll start troubleshooting.

@martin.borg

not so perfectly when used from the app

If you’re stress testing with multiple operations at once, there are a few possibilities. It could be the device getting overwhelmed, the timing of the commands getting to the device in a different order than expected, or something in the driver logic. We really need turning all 4 on or off over z-wave to work properly though, so what I’ll do is program the switch on the main component to send SWITCH_ALL commands.

Next version will also allow you to set up device to device association, since I think I remember you saying in your older thread that you had that set up in the old system for virtual 3-way switches.

[martin.borg]

@philh30

Next version will also allow you to set up device to device association, since I think I remember you saying in your older thread that you had that set up in the old system for virtual 3-way switches.

Thank you!

I do have some reservations about switch-to-switch associations as I was given to understand that when a switch with an association is switched on, the hub might never get to know about it (not sure about this point), and sometimes, besides 2/3-way lighting, I might need a switch to do something else (e.g. switch on a hot water circulation pump in my basement). But it will certainly be very useful in some situations where nothing beyond 2/3-way lighting is required.

[JDRoberts]

@martin.borg

@philh30

Next version will also allow you to set up device to device association, since I think I remember you saying in your older thread that you had that set up in the old system for virtual 3-way switches.

Thank you!

I do have some reservations about switch-to-switch associations as I was given to understand that when a switch with an association is switched on, the hub might never get to know about it (not sure about this point), and sometimes, besides 2/3-way lighting, I might need a switch to do something else (e.g. switch on a hot water circulation pump in my basement). But it will certainly be very useful in some situations where nothing beyond 2/3-way lighting is required.

If you set up direct association with the auxiliary switch as the trigger and the master switch as the target, you could still add the hub to that association group as long as there is space in the list for it, and that way it would know.

Separately, the hub is aware of the switch whether you have association lists set up or not, so that’s not an issue.

The purpose of direct association was to give a device permission to send a basic (again that has a very specific meaning in zwave) command directly to another device without going through the hub. That was good for the days before smart phones, but it did mean that the hub didn’t know what happened and so the app wasn’t kept up-to-date.

The solution to that is to add the hub to the list of target devices, just like it was another switch. That way the hub would receive a “basic“ command when the switch was pressed. The hub has to know what to do with that, but I’m pretty sure that works in smartthings.

There’s still the problem that there’s no filter option for direct Association: it happens every single time the switch is pressed and sometimes you want more control than that.

So the next evolution in the Z wave specifications was the introduction of “central scenes” in which a button press sends a scene number to the hub and then the hub knows what to do with that.

So with the newer devices there are quite a few people who set up direct association only for auxiliary switch as a trigger and master switch as a target because they do want that to happen every single time. And anything else they do with a central scene. But that’s not an option on your older switches.

In order for the hub as a target device option to work, the hub has to be added to the association group for every association group. Not just the lifeline.

MULTILEVEL SWITCHES

dimmers are called “multilevel devices “ because they have a dimlevel, usually 0 to 99. It’s a percentage in this case. The percentage of full on bright.

Anyway, multilevel association means you send both a “basic“ command and a level. So basic 50 tells the target to turn on to 50% bright. Basic 75 tells the target to turn onto 75% bright.

Typically in a device with the form factor of the MCO panels, Dimming is accomplished by a long press on the button. The longer you hold the button down, the brighter the light gets.

In order to allow the same device to be used as a trigger for either dimming or plain basic, the device will have multiple association groups. One association group only sends the basic command. Another sends the multilevel two part command to a different list of targets.

[martin.borg]

Thank you @JDRoberts - very useful information, and also makes me feel much more hopeful now thaat maybe I can finally get these switches to work as I always wanted them to albeit without the dimming.

@JDRoberts

Typically in a device with the form factor of the MCO panels, Dimming is accomplished by a long press on the button. The longer you hold the button down, the brighter the light gets.

I am, almost sure this is the case judging from the description in the pdf - though I don’t think I will spend too much time on it since only one of my many switches supports this. Pity… Perhaps in the future, I will consider changing switches to something more functional, but that should not be at gunpoint (as the current situation feels with the impending deadline.)

Also, if @philh30’s driver works (I feel very confident it will at this stage ) - I have a feeling this will mean the substantial reduction of devices (by about 80 devices!!) from my overall device tally. That is massive, given I have been hittng the 200 device limit a lot recently, and have been constantly chasing workarounds to keep adding devices I have needed to add over time.

[philh30]

The user manual you posted for the newer one has me convinced it’s just an on/off relay with no dimming. Anywhere it mentions dimming is in reference to association commands that it’s sending to other devices, which is probably more complicated than it’s worth. It also only mentions association groups 1, 2, 5, 8, and 12 as being supported. Thanks - good resource.

[philh30]

@martin.borg New version to test with all three models - name is MCOHome Z-Wave Switch. This will hopefully be the last time where a driver swap is required. Changes are:

• Lifeline association should be set on the newer model, hopefully improving performance
• Main switch on/off should send a single command to turn all of the real switches on/off
• Settings menu:
  • Choose Profile - Swap between large 5 tile dashboard and smaller 1 tile icon (you may need to close/reopen the app and clear cache to get the new display)
  • Main Switch Behavior - The switch on the main component can either show as ON once one switch turns on, or continue to show as OFF unless all switches are on.
  • Association Groups - Enter as a comma delimited string of hex z-wave node IDs, such as 5,1C,2A. If the command needs to be sent to an endpoint (such as to one of these types of switches), enter it as node:endpoint (for example, 32:2). These can be mixed together, with some nodes specifying an endpoint and others not.

I don’t have a device that matches too well with these to be able to test too much, so there could be bugs. Let me know how it works!

[martin.borg]

Hey @philh30 - I will admit I am blown away. Didn’t even know having larger tiles was a possibility. I have just tested a little, and am happy to report as follows:

• Physical interaction with the device is flawless. I have carried out pretty hardcore testing, like pressing a multitude of keys at random - and by multitude I mean a lot… The final state of the switch always reflects on the app. it might take a couple of seconds if you’ve just hit the various buttons about twenty times between them, but the app always updates to reflect the final state, and pretty fast too. iI daresay it was never this good with the Groovy DTH, not even with the refresh from Groovy and the added refresh from Webcore, which indeed make it clunky… And also, I have to take into consideration that the app needs to get information through the cloud, even if the device driver runs locally - but still, the result is very acceptable and I am very pleased with the outcome.

• Interaction via automations (e.g. the switches turned on through motion or via other switches) is also very fast, and indeed very acceptable.

• Interaction via the app is also very fast - I am not too sure it is perfect but it might be. will require a bit more testing as I seem to have suspected a few missed key presses, but could have been me.

The flaws that persist are the following:

1. From the app: often I press a button on the five-tile dashboard - and the switch responds right away. The app too reflects the new button state right away (almost instant - normally takes a fraction of a second). But - sometimes I get the spiral shape circling around the button (the exact word eludes me but I know it sort of signified “loading”), and it keeps circling even though the button state has indeed changed, for a really long time, and I mean minutes. Indeed haven’t tested how long - likely it keeps going like that until you force the button to change state again, and then perhaps it will stop. It is cosmetic, yes, but slightly annoying since if there’s trouble with a switch you will never know once you get used to so many of these buttons having that spiral going round perpetually. See Image 1 below - In that image, I had turned off buttons 2 & 3, and the switch did that, the app too reflected the new correct state, but the spiral keeps going on forever. (This applies also to Main switch).

2. In the case of the Main switch, I cannot seem to control it from the dashboard. I have to click on the tile, go into the longer, vertical format, and turn it on/off from there.

3. The Main switch - I have not figured this one out yet, but it is not working well. It seems to me that on the MH-S314s (both the old and the new) it is strangely connected to Switch4. If you toggle Main and Switch4 is off, then Switch4 will go on. If Switch4 is, however, already on, and you toggle Main, nothing happens at all. Toggling Switch4 directly seems not to have any effect on Main. These tests were carried out with Main Switch Behavior set to “ON when one switch is on”.

4. in the case of the MH-S312 switches, there seems to be something funny going on - some kind of loop between Main and the other switches when Main Switch Behavior set to “ON when one switch is on”. I couldn’t really figure out what was happening, but I could see Main going on on its own when a switch is on, but if I continue playing about, Switch1 or Switch2 might actually revert to their initial state after a button press. I then set Main Switch Behavior set to “ON when all switches are on” - but here too there was trouble, sometimes (especially from dashboard) it goes on when only Switch1 goes on.

Image 1:

Hope I gave explained it all very well above. Do you need me to send any CLI logs, and if so, in which specific situations please? As otherwise it will get very confusing and overwhelming for you.

[martin.borg]

Btw, I have not tested associations yet. I will do that later as these are completely new to me - if I get them to work it will be my first ever, and they will save me a few routines for sure, besides making 2/3-way lighting near instant.

Is there any way off getting the ZWave ID of a device without having to monitor its logging in the CLI, please?

[martin.borg]

I never really replied to my favourite way of having the Main switch work (assuming a four-button switch, but the 2-button would work in a similar manner):

1. I turn on the Main switch when all Switches (1-4) are off - everything will go on.

2. I turn off the Main switch when all Switches (1-4) are on - everything will go off.

3. If all switches are off and I turn on one switch, nothing happens. 2 switches - still nothing. 3 switches - still nothing. But when turn on the 4th switch (therefore all are on) - then Main goes on. If I then turn any of the 4 switches off, Main goes off too.

4. If 2 of the switches (of 4) are on, and I press Main, the other 2 switches go on. If only 1 (of the 4) switches is on, and I press Main, the other 3 switches go on. etc.

I am not sure the above is achievable, or whether it is a reasonable amount of coding or not, but it is how I perceive the “ON when all switches are on” option should work. If it is too much work, then don’t worry, I hate asking you for so much work and am really appreciative of all you have done. Many, many thanks!

[philh30]

Great! The larger dashboard tile is a nice feature - I just wish there was more flexibility in the size besides the small and large options we have now.

Let’s skip posting logs for now. They would’ve been helpful if we got stuck somewhere, but with the buttons communicating well now they’re not really necessary.

@martin.borg

it keeps circling even though the button state has indeed changed, for a really long time, and I mean minutes

The driver doesn’t know whether an on/off command is coming from the dashboard, the detail view, an automation, or a third-party integration like Alexa. They’re all treated the same, so if things are working well on detail view then these issues on the dashboard are most likely a problem with the ST app itself. The test would be to watch live logs and toggle a switch through detail view, then toggle it on the dashboard. If the logs look the same and post in a similar timeframe between the two, then it’s the app’s fault. You’ll find plenty of commentary regarding app performance if you look around the forum.

@martin.borg

The Main switch… is strangely connected to Switch4

I probably had the bitmask backwards on that z-wave command, which would make it toggle endpoints 4-7 instead of 1-4 (and 6-7 instead of 1-2 for the 2-button device). I’ve pushed out an update that flips the bitmask. I also noticed a typo in the handling of the state of the main switch, which I think would’ve caused both of the setting options to act like “ON when all are ON”. Let’s test again and if you’re still seeing inconsistent results then we’ll dig deeper. The updated driver has timestamp 2022-08-22T11:16:28.822297787. It should push automatically to your hub within the next 12 hours (though maybe much faster), or you can immediately push the new version to your hub through the CLI with the smartthings edge:drivers:install command. No driver swap needed this time. You should also go ahead and delete the earlier test versions from your hub using smartthings edge:drivers:uninstall.

@martin.borg

Is there any way off getting the ZWave ID of a device without having to monitor its logging in the CLI, please?

Run smartthings devices in the CLI. Find the number in the left hand column for the device you’re targeting - let’s say it’s 25. Now run smartthings devices 25 and look for the Network ID field, which will be the node ID in hex.

@martin.borg

it is how I perceive the “ON when all switches are on” option should work

What you laid out matches what I was intending. Hopefully works that way after these updates!

[philh30]

I can also add the z-wave node ID to the detail view as another capability at the bottom. Probably a waste of space though unless you think you’ll be doing a lot of associations.

[JDRoberts]

@philh30

I can also add the z-wave node ID to the detail view as another capability at the bottom. Probably a waste of space though unless you think you’ll be doing a lot of associations.

I have suggested in another thread that all tiles for zwave devices display the ID as part of the details as a best practice.

It’s not just used in associations: it’s essential in troubleshooting network health, such as in reviewing a zwave repair report.

[martin.borg]

@philh30

The updated driver has timestamp 2022-08-22T11:16:28.822297787

Hi @philh30 - thank you for the updated driver. It seems to have already updated in my app, though the timestamp ends with 97887 on mine, so I suspect that could be a type at your end - is this the case or was your timestamp actually correct?

I will test later on today as right now I’m working…

[philh30]

Just a typo. Your timestamp is correct

[martin.borg]

Great - thanks, will test later as advised.

Regrettably, the lifeline association has not helped much for the newer model has not helped with the device appearing as offline (see pic below). I am not sure why this happens - the device is not really offline and instantly comes back to life if activated physically or via automation - a fraction of a second later it re-appears as normal and online. So it will have little effect really other than that you cannot operate it either from the dashboard or from the detail view from the app - has to be physical interaction or automation.

As I said above, this used to happen also with the old DTH… So much so that I abandoned it for a custom DTH. The custom DTH actually ran a refresh every so many minutes (not sure if this really worked but I could see it actually happening in the logs - so I thought it did). I think that might have helped keep the device alive, but am not technical enough to say this with certainty.

[philh30]

I’m at work now, and I think with time zone differences you’ll be able test more before I’m able to do any changes in code. The couple of things that you can try on the new switch are:

• Post logs. Maybe there’s something that will turn up that can help. It doesn’t need to be extensive - just capture turning a button on and off both through the app and physically.
• Run a z-wave repair. Since you had this issue previously, I doubt it’ll turn out to be a mesh issue, but you should probably run a repair anyways since you’ve been excluding and including repeaters.

When I’m able to update the driver, one thing we can try is changing parameter 8 from the default setting of 0 to 1. If the unsolicited Basic Reports mentioned in that setting work like I hope, they might be enough to keep the device alive.

Otherwise… We can set up polling for that one.

[martin.borg]

@philh30

Post logs. Maybe there’s something that will turn up that can help. It doesn’t need to be extensive - just capture turning a button on and off both through the app and physically.

Hi @philh30 - I will see to this shortly, starting from this post. I will only post logs from the new MH-S314 switch for now. All switches seem to be behaving differently, so perhaps better to diagnose one at a time as there will be a substantial amount of logs.

This test involves turning on all four switches (from all 4 being off) - without touching the main switch - and I did this using the mobile app:

? Select a driver. 6
connecting... connected
2022-08-22T20:00:24.043891282+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:00:24.074018949+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:00:24.083183282+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:24.092489282+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:00:24.110584615+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(631d99d4) queued for radio transmission: CC:Switch Binary, CID:0x01
2022-08-22T20:00:24.124277949+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:24.131879282+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:24.977746616+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:00:25.045066949+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"switch2","positional_args":{}}
2022-08-22T20:00:25.077710616+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:25.110491949+00:00 INFO MCOHome Z-Wave Switch  <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={2}, encap="AUTO", payload="\xFF\x00", src_channel=0, version=2}
2022-08-22T20:00:25.171388949+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(121ca9a0) queued for radio transmission: CC:Switch Binary, CID:0x01
2022-08-22T20:00:25.283409616+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:25.299173282+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:25.413071616+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:00:25.456412949+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(8a760171) queued for radio transmission: CC:Switch Binary, CID:0x02
2022-08-22T20:00:25.471197283+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:25.884384616+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:00:25.892931949+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"switch3","positional_args":{}}
2022-08-22T20:00:25.899464949+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:25.907056283+00:00 INFO MCOHome Z-Wave Switch  <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={3}, encap="AUTO", payload="\xFF\x00", src_channel=0, version=2}
2022-08-22T20:00:25.920556616+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(045da853) queued for radio transmission: CC:Switch Binary, CID:0x01
2022-08-22T20:00:25.931603616+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:25.938176283+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:26.279812616+00:00 INFO MCOHome Z-Wave Switch  <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={2}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-22T20:00:26.294870616+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(d0fa44e2) queued for radio transmission: CC:Switch Binary, CID:0x02
2022-08-22T20:00:26.300138616+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:26.908908950+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:00:26.917037950+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"switch4","positional_args":{}}
2022-08-22T20:00:26.923641617+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:26.931337950+00:00 INFO MCOHome Z-Wave Switch  <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={4}, encap="AUTO", payload="\xFF\x00", src_channel=0, version=2}
2022-08-22T20:00:26.945409950+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(dcc77799) queued for radio transmission: CC:Switch Binary, CID:0x01
2022-08-22T20:00:26.956823950+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:26.963689283+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:26.972898283+00:00 INFO MCOHome Z-Wave Switch  <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={3}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-22T20:00:26.987112617+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(5187d5b2) queued for radio transmission: CC:Switch Binary, CID:0x02
2022-08-22T20:00:26.992711283+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:27.969487950+00:00 INFO MCOHome Z-Wave Switch  <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={4}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-22T20:00:27.984278950+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(775efc34) queued for radio transmission: CC:Switch Binary, CID:0x02
2022-08-22T20:00:27.989714950+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:00:31.332200285+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(631d99d4) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:31.353521619+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:00:31.364034285+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:00:31.373174952+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:31.379513952+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:00:31.414130619+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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"]:229: 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"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:00:31.622953285+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(121ca9a0) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:31.641925619+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:00:31.650661619+00:00 INFO MCOHome Z-Wave Switch  <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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
2022-08-22T20:00:31.685676285+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:31.694080285+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-08-22T20:00:31.719151285+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:00:31.761136286+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(8a760171) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:31.923120286+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(045da853) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:31.965276952+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:00:31.977752619+00:00 INFO MCOHome Z-Wave Switch  <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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
2022-08-22T20:00:31.997765619+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:32.004267619+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch3","state":{"value":"on"}}
2022-08-22T20:00:32.024141619+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:00:32.061350619+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(d0fa44e2) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:32.192363952+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(dcc77799) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:32.227044952+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:00:32.235978619+00:00 INFO MCOHome Z-Wave Switch  <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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
2022-08-22T20:00:32.253547286+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:00:32.259545952+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch4","state":{"value":"on"}}
2022-08-22T20:00:32.278442286+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:00:32.362178952+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(5187d5b2) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:00:32.461172953+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(775efc34) transmit status: TRANSMIT_COMPLETE_OK

It took a couple of seconds I believe for the switch to react. That, I believe, is because of the spiral going round on all four buttons on the app (this was the state of all 4 switches before I started the test), which seems to slow down any further interaction from within the app.

The next part is turning off all four switches through physical button presses on the switch itself. When done through the switch, the state of each button (Switch1 through 4) changes on the app near instantly, and I do not get the spiral effect.

? Select a driver. 6
connecting... connected
2022-08-22T20:09:27.163040126+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:27.181027793+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={key_attributes="KEY_RELEASED", scene_number=1, sequence_number=96, slow_refresh=false}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="NONE", payload="\x60\x01\x01", src_channel=0, version=3}
2022-08-22T20:09:27.196949460+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:09:27.202540793+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:27.212645126+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\x00", src_channel=1, version=1}
2022-08-22T20:09:27.221335793+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:09:27.227434460+00:00 INFO MCOHome Z-Wave Switch  <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":"off"}}
2022-08-22T20:09:27.247020793+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\x00", src_channel=1, version=1}
[string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={1}, encap="NONE", payload="\x00", src_channel=1, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:09:27.548290793+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:27.557757460+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={2}, encap="NONE", payload="\x00", src_channel=2, version=1}
2022-08-22T20:09:27.573739793+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:09:27.580034460+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"off"}}
2022-08-22T20:09:27.599307793+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={2}, encap="NONE", payload="\x00", src_channel=2, version=1}
[string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={2}, encap="NONE", payload="\x00", src_channel=2, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:09:27.608416793+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:27.621828460+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={key_attributes="KEY_RELEASED", scene_number=2, sequence_number=96, slow_refresh=false}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="NONE", payload="\x60\x01\x02", src_channel=0, version=3}
2022-08-22T20:09:27.638340460+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:09:28.008482460+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:28.018172793+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={3}, encap="NONE", payload="\x00", src_channel=3, version=1}
2022-08-22T20:09:28.026553126+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:09:28.032563126+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch3","state":{"value":"off"}}
2022-08-22T20:09:28.052507793+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={3}, encap="NONE", payload="\x00", src_channel=3, version=1}
[string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={3}, encap="NONE", payload="\x00", src_channel=3, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:09:28.061575793+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:28.074937127+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={key_attributes="KEY_RELEASED", scene_number=3, sequence_number=96, slow_refresh=false}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="NONE", payload="\x60\x01\x03", src_channel=0, version=3}
2022-08-22T20:09:28.090280460+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:09:28.448095127+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:28.457502460+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={4}, encap="NONE", payload="\x00", src_channel=4, version=1}
2022-08-22T20:09:28.465534127+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:09:28.471537793+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch4","state":{"value":"off"}}
2022-08-22T20:09:28.490270793+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={4}, encap="NONE", payload="\x00", src_channel=4, version=1}
[string "st/dispatcher.lua"]:229: Error encountered while processing event for <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)>:
    arg1: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={4}, encap="NONE", payload="\x00", src_channel=4, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:09:28.500948127+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:09:28.515442793+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received Z-Wave command: {args={key_attributes="KEY_RELEASED", scene_number=4, sequence_number=96, slow_refresh=false}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="NONE", payload="\x60\x01\x04", src_channel=0, version=3}
2022-08-22T20:09:28.532521127+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled

Hope the above starts to help a little.

[martin.borg]

@philh30

I can also add the z-wave node ID to the detail view as another capability at the bottom. Probably a waste of space though unless you think you’ll be doing a lot of associations.

Actually this would be a great help- I have three staircases, a garage, a landing and 2 corridors at minimum with two way lighting, and many of the rooms have lighting from different sides of the room. if it works for me and the hub is informed as @JDRoberts indicated, I will certainly test and use them. It’s just not something I want to do right away whilst we’re still trying to fix the UI issues.

[martin.borg]

Hi again @philh30

this is a test I just carried out: pressing the Main switch from the dashboard when all four switches are off. The result is thatthe Main switch on the dashboard gets the spiral for about a minute and remains showing OFF, but al 4 switches go off instantly (both physically and on the app), no spiral or anything. So works perfectly except that the main never goes on:

? Select a driver. 6
connecting... connected
2022-08-22T20:20:20.763975331+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:20:20.772954664+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-08-22T20:20:20.784266664+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:20:20.820477664+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> sending Z-Wave command: {args={bit_address=true, command=1, command_class=37, destination_end_point=15, parameter="\xFF", res=false, source_end_point=0}, cmd_class="MULTI_CHANNEL", cmd_id="CMD_ENCAP", dst_channels={}, encap="AUTO", payload="\x00\x8F\x25\x01\xFF", src_channel=0, version=2}
2022-08-22T20:20:20.840657331+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(395d91e5) queued for radio transmission: CC:Multi-Channel, CID:0x0D
2022-08-22T20:20:20.846519664+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:20:21.104948998+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(395d91e5) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:20:21.130219664+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:20:21.148831998+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:20:21.168184998+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:20:21.174168331+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:20:21.263626331+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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"]:229: 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"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:20:21.312330331+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:20:21.323956664+00:00 INFO MCOHome Z-Wave Switch  <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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
2022-08-22T20:20:21.464239331+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:20:21.588269998+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-08-22T20:20:21.704178331+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:20:21.721773331+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:20:21.771058665+00:00 INFO MCOHome Z-Wave Switch  <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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
2022-08-22T20:20:22.022598331+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:20:22.033516665+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch3","state":{"value":"on"}}
2022-08-22T20:20:22.079520998+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:20:22.096081665+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:20:22.154108332+00:00 INFO MCOHome Z-Wave Switch  <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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
2022-08-22T20:20:22.214828665+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:20:22.233881332+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch4","state":{"value":"on"}}
2022-08-22T20:20:22.264909332+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)

Now, I just pressed the Main switch (from the dashboard again) whilst all 4 switches were on (and of course Main was off as per earlier text in this post). The result was - nothing happened. everything remained on:

? Select a driver. 6
connecting... connected
2022-08-22T20:25:18.593929560+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:25:18.618673894+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-08-22T20:25:18.633217894+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:25:18.646403894+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> sending Z-Wave command: {args={bit_address=true, command=1, command_class=37, destination_end_point=15, parameter="\xFF", res=false, source_end_point=0}, cmd_class="MULTI_CHANNEL", cmd_id="CMD_ENCAP", dst_channels={}, encap="AUTO", payload="\x00\x8F\x25\x01\xFF", src_channel=0, version=2}
2022-08-22T20:25:18.660738560+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(398dbf21) queued for radio transmission: CC:Multi-Channel, CID:0x0D
2022-08-22T20:25:18.666688560+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:25:18.914950227+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(398dbf21) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:25:18.939970227+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:25:18.959079560+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:25:18.977264560+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:25:18.983418227+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:25:19.003300894+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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"]:229: 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"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:25:19.011622227+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:25:19.022915560+00:00 INFO MCOHome Z-Wave Switch  <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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
2022-08-22T20:25:19.039810894+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:25:19.045927560+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-08-22T20:25:19.068280227+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:25:19.076146894+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:25:19.086273894+00:00 INFO MCOHome Z-Wave Switch  <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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
2022-08-22T20:25:19.105376227+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:25:19.111300227+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch3","state":{"value":"on"}}
2022-08-22T20:25:19.131371894+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:25:19.141616560+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:25:19.150705227+00:00 INFO MCOHome Z-Wave Switch  <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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
2022-08-22T20:25:19.168415227+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:25:19.174413560+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch4","state":{"value":"on"}}
2022-08-22T20:25:19.196975894+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)

So, yes, mostly working but something is wrong with the Main switch.

I will now post wht happened in the next test. I start this test with buttons 1 and 4 ON, and buttons 2 & 3 OFF. And then I press the Main switch from the dashboard in the app. The result is: 2& 3 go on as expected (note this is not a consistent result though, it does not always happen):

? Select a driver. 6
connecting... connected
2022-08-22T20:30:06.343992960+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler capability
2022-08-22T20:30:06.363194627+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-08-22T20:30:06.370220627+00:00 TRACE MCOHome Z-Wave Switch  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:30:06.383184627+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> sending Z-Wave command: {args={bit_address=true, command=1, command_class=37, destination_end_point=15, parameter="\xFF", res=false, source_end_point=0}, cmd_class="MULTI_CHANNEL", cmd_id="CMD_ENCAP", dst_channels={}, encap="AUTO", payload="\x00\x8F\x25\x01\xFF", src_channel=0, version=2}
2022-08-22T20:30:06.405093294+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(766ad9d9) queued for radio transmission: CC:Multi-Channel, CID:0x0D
2022-08-22T20:30:06.414105960+00:00 DEBUG MCOHome Z-Wave Switch  WYFY Switch 1 device thread event handled
2022-08-22T20:30:06.614725294+00:00 TRACE MCOHome Z-Wave Switch  Z-Wave command(766ad9d9) transmit status: TRANSMIT_COMPLETE_OK
2022-08-22T20:30:06.640569627+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:30:06.659432294+00:00 INFO MCOHome Z-Wave Switch  <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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
2022-08-22T20:30:06.686818294+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:30:06.692775627+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch3","state":{"value":"on"}}
2022-08-22T20:30:06.711576627+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "st/dispatcher.lua"]:229: 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={3}, encap="NONE", payload="\xFF", src_channel=3, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:30:06.720951627+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:30:06.731647960+00:00 INFO MCOHome Z-Wave Switch  <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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
2022-08-22T20:30:06.748998294+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:30:06.754911627+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch4","state":{"value":"on"}}
2022-08-22T20:30:06.777414627+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "st/dispatcher.lua"]:229: 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={4}, encap="NONE", payload="\xFF", src_channel=4, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:30:06.784722960+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:30:06.794949294+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:30:06.813591294+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:30:06.819695627+00:00 INFO MCOHome Z-Wave Switch  <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-22T20:30:06.840191294+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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"]:229: 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"]:46: bad argument #2 to 'format' (no value)
2022-08-22T20:30:07.226192960+00:00 TRACE MCOHome Z-Wave Switch  Received event with handler unnamed
2022-08-22T20:30:07.238805627+00:00 INFO MCOHome Z-Wave Switch  <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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
2022-08-22T20:30:07.366714961+00:00 TRACE MCOHome Z-Wave Switch  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-22T20:30:07.382632627+00:00 INFO MCOHome Z-Wave Switch  <ZwaveDevice: 0990b7a6-a1fa-4673-acc8-943309fbff50 [3E] (WYFY Switch 1: New S314)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-08-22T20:30:07.473696961+00:00 ERROR MCOHome Z-Wave Switch  WYFY Switch 1 thread encountered error: [string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "st/dispatcher.lua"]:229: 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={2}, encap="NONE", payload="\xFF", src_channel=2, version=1}
[string "mcohome/init.lua"]:46: bad argument #2 to 'format' (no value)

Hoping I am not overwhelming you with the logs (I was afraid this would be the case as I always thought the logs from these switches were always massive).

Let me know whether you need me to send more logs.

[martin.borg]

@philh30

Run a z-wave repair. Since you had this issue previously, I doubt it’ll turn out to be a mesh issue, but you should probably run a repair anyways since you’ve been excluding and including repeaters.

I have done this a few times as I converted some devices to Edge drivers over the weekend. I prepared a spreadsheet with all types of devices I own, and my intention was to test every single device I have before 30 September so I will be prepared (and braced) for whatever is going to happen on that day. As I converted some devices, I rebuilt the Zwave mesh at least twice… But I have no problem doing it again. Will start it just before we sleep tonight so as not to have everything stop working for 45 minutes (yes - it takes this long with about 105 Zwave devices).

I will test again after the rebuild and let you know. Many thanks.