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

Devices & Integrations Community Created Device Types
81

Thanks @JDRoberts. In this case, though, the problem was not whether it gets communicated to the hub. The hub invariably was informed with all key presses, whether or not I included the “1” in the Association group setting.

But- curiously, what we are seeing here is that if the list of “members” of the group are all endpoints, then it simply does not work. If you include at least one “member” that is just a node, but not an endpoint, then all the other members will work and will mirror what happens on the source endpoint.

Not sure this is clear.

To be honest - it doesn’t affect me much if I know that just adding the hub in each group will mean it actually works. It just means a few additional key presses for me to set the thing up, but gives us near-instant lighting control for any 2/3-way lighting in our home.

83

I also tested populating an Association Group with members being endpoints from the same switch. Say, for example, that I want button 4 of a switch to switch on buttons 1, 2, and 3 of the same switch.

Unfortunately, I don’t think it is possible and it did not work for me, and so, something like this would need to be done through a Routine or other mechanism - but not a direct one like Association Groups.

84

New version dated 2022-08-25T15:36:26.209323602 should work with a list of only endpoints.

2 Likes
85

Yes! Tested and works perfectly without the need to enter a non-endpoint node. Also - hub is gettting informed about any state change that happens, whether it is on the source switch or the destination switch - I see the changes happening on the app every time (with some delay, sometimes, but at least it’s reflected.)

I guess it’s time to go around the house and re-install all switches with this driver :slight_smile: I am sure everyone will be pleased with the performance of the 2/3-way lighting - though it’s sad to see us being happy about something that was available since I was a kid, but stopped working well when our house went smart :sweat_smile:

2 Likes
86

Excellent! Thanks for bearing with me through bug fixes. We’ll have one more driver swap to get the setting for polling added to the profile, a bit of clean up, and then we should be done!

2 Likes
87

Hi @philh30 - came across a new problem, regrettably.

I converted 3 of these switches over to your latest driver (the Test 3 version) - one MH-S314 and two MH-S312s. I am not sure of the fingerprint they had (perhaps a slightly different Zwave version?) and I don’t know how to get the fingerprint with Edge yet. However, I am 100% sure they were the ones ending with 1302 because I went through all my MCOHome switch devices on the IDE before this exercise, and only one of the fingerprints was the one ending 5102 - and that is the one we have been calling “New”, and the one we used for testing.

Anyhow, of these 3 switches I converted yesterday, the first one, an MH-S312 converted without problems and after a few clicks worked well - as well as the ones I had been testing on. Now, this was at the lower end of a staircase, and so I went up to convert the other (corresponding) switch as well. It did pair, and it paired as Edge, and I changed to the latest driver. However, after setting it up like all the others, I noticed Main is not working well. the switch behaves fairly well when I click the individual buttons, but the moment you try to click Main, it goes haywire. The action might very well work (e.g. turns on all switches), but you never get to see that on the app. Moreover, associations work - but are super slow - like 10 to 20 seconds late, and yet the app is still showing both Main as well as all the child buttons as off. I thought that was weird, so I tried with another switch - this time an MH-S314. And funnily, this too behaved in the same manner. So I am not sure whether to keep converting as yet, since it seems any touch of he Main switch puts the switch in a funny mode and remains in that funny mode for at least several minutes (everything becomes slow).

Could you guide me on how to diagnose his please?

88

Hi again, so let me send you a couple of logs. This is what happens when I turn Main ON and OFF, with say a 5-second interval, on the first switch I converted yesterday, the one that worked well:

? Select a driver. 7
connecting... connected
2022-08-26T07:45:01.884180152+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-26T07:45:01.894350819+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-08-26T07:45:01.901035152+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:01.907428152+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> sending Z-Wave command: {args={}, cmd_class="SWITCH_ALL", cmd_id="ON", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-26T07:45:01.925028152+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(208fb84e) queued for radio transmission: CC:Switch All, CID:0x04
2022-08-26T07:45:01.931437819+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:02.102164819+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(208fb84e) transmit status: TRANSMIT_COMPLETE_OK
2022-08-26T07:45:02.343208152+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-26T07:45:02.487180153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> 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-26T07:45:02.527488819+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:02.573154153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-08-26T07:45:02.674922153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-26T07:45:02.817614153+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:02.902015153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-26T07:45:03.057634486+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> 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-26T07:45:03.130326819+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:03.156059153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch1","state":{"value":"on"}}
2022-08-26T07:45:03.223515486+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-26T07:45:03.245834486+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:03.255614819+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-26T07:45:03.275108819+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> 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-26T07:45:03.307833153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:03.315168819+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-08-26T07:45:03.351023486+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-08-26T07:45:03.379158486+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:10.282017153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-26T07:45:10.313309153+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
2022-08-26T07:45:10.321284153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:10.328336487+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> sending Z-Wave command: {args={}, cmd_class="SWITCH_ALL", cmd_id="OFF", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-26T07:45:10.358787487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(5838fc74) queued for radio transmission: CC:Switch All, CID:0x05
2022-08-26T07:45:10.366493820+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:10.502654487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(5838fc74) transmit status: TRANSMIT_COMPLETE_OK
2022-08-26T07:45:10.559014820+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-26T07:45:10.568665820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x00", src_channel=0, version=1}
2022-08-26T07:45:10.592711487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:10.598809820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-26T07:45:10.618310820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-08-26T07:45:10.638339820+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:10.647791487+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-26T07:45:10.656883820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> 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-26T07:45:10.707038153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:10.713360820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch1","state":{"value":"off"}}
2022-08-26T07:45:10.735878820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-26T07:45:10.756310487+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled
2022-08-26T07:45:10.763259153+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler unnamed
2022-08-26T07:45:10.773606820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> 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-26T07:45:10.799229820+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found ZwaveDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:45:10.805714820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"off"}}
2022-08-26T07:45:10.824973820+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: 1de949ab-fda9-4c2f-848a-ae62a48b7508 [56] (Base2Ground Light Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-08-26T07:45:10.841311487+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Base2Ground Light Switch device thread event handled

I am now going to paste what happens when I try the same thing, but using the Main switch of the second MH-S312 I converted yesterday, the one not working well:

? Select a driver. 7
connecting... connected
2022-08-26T07:51:21.780639872+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-26T07:51:21.790398206+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: f5b7617f-0845-4728-9be5-1e88a363cb6a [57] (Ground2Base Light Switch)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-08-26T07:51:21.796776872+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:51:21.803757872+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: f5b7617f-0845-4728-9be5-1e88a363cb6a [57] (Ground2Base Light Switch)> sending Z-Wave command: {args={}, cmd_class="SWITCH_ALL", cmd_id="ON", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-26T07:51:21.820663539+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(0513f78c) queued for radio transmission: CC:Switch All, CID:0x04
2022-08-26T07:51:21.825803206+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Ground2Base Light Switch device thread event handled
2022-08-26T07:51:21.982469206+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(0513f78c) transmit status: TRANSMIT_COMPLETE_OK
2022-08-26T07:53:16.056209927+00:00 TRACE MCOHome Z-Wave Switch Test 3  Received event with handler capability
2022-08-26T07:53:16.064809927+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: f5b7617f-0845-4728-9be5-1e88a363cb6a [57] (Ground2Base Light Switch)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2022-08-26T07:53:16.071347593+00:00 TRACE MCOHome Z-Wave Switch Test 3  Found CapabilityCommandDispatcher handler in zwave_switch -> MCOHome Switch
2022-08-26T07:53:16.078089593+00:00 INFO MCOHome Z-Wave Switch Test 3  <ZwaveDevice: f5b7617f-0845-4728-9be5-1e88a363cb6a [57] (Ground2Base Light Switch)> sending Z-Wave command: {args={}, cmd_class="SWITCH_ALL", cmd_id="ON", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2022-08-26T07:53:16.095169260+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(a1131ebb) queued for radio transmission: CC:Switch All, CID:0x04
2022-08-26T07:53:16.100378260+00:00 DEBUG MCOHome Z-Wave Switch Test 3  Ground2Base Light Switch device thread event handled
2022-08-26T07:53:16.182710927+00:00 TRACE MCOHome Z-Wave Switch Test 3  Z-Wave command(a1131ebb) transmit status: TRANSMIT_COMPLETE_OK

Actually, during this test, the lights did go on on the switch when I pressed Main on the app, but the app never reflected this - it just showed a spiral on main for minutes. When that stopped, I pressed it a second time, so what you see in the last batch of log entries above is two presses of Main, with buttons going on during the first press, but the app never shows any button as on.

If I operate the switch manually or by using the individual buttons only from the app, then it is fine (a bit slow, but generally fine) - they even turn on Main when all switches are on and off when one button goes off. It is clear from the log that after the transmit, nothing else happens as far as the hub is concerned, and I have tried all the MAIN Switch Testing options, but none of them works. I find this awkward for 2 switches, included only 5 minutes apart from each other, with the same fingerprint (though not sure they have the exact same spec like Zwave version, etc.), to be behaving so differently. The MH-S314 I installed this morning also behaves in the same exact manner as the latter MH-S312 as described in the latter batch of log entries above, i.e, log entries end with “TRANSMIT_COMPLETE_OK” and no response from the device. Strange, to say the least.

Not sure if I was unlucky and had 2 seemingly faulty switches included one right after the other - however, they were operating normally with the DTH - that is with some delays as all the other switches, usually delays associated mostly with the cloud.

89

Ok - so it was not luck, or the lack of it. It seems like there will be more of these switches. I added another MH-S314 right now. Seems to suffer from the same ills as the previous 2. I will stop adding for now as it will severely impact our lighting.

One new thing I have found is that the hub is likely never receiving any signal from these switches (but it was before installing this driver). Basically, when you press any key on this switch - physically - the app never seems to get to know about this. If you start off with all four switches off, and ou physically press all four buttons, turning each one ON, on the switch, the app keeps showing them as OFF (hence not even routines will work).

I know this with certainty because I opened a new logging session with no entries to start monitoring this driver, then monitored whilst pressing all four buttons on the latest switch I added: there were zero entries in the log, which of course is absolutely not normal. Unless Smartthings has changed something and maybe now - because of that change, all my MCOHome switches will be included in this new mode which seems to provide only one-way communication: hub to switch, but not vice versa. This sounds improbable to me though.

90

For the record - all switches with the problem highlighted in the previous 3 posts (yes, sorry for the numerous posts) were previously working decently (but with some lag, ranging from acceptable to sometimes unbearable) with the Groovy DTH. I have no idea how they seemingly are not transmitting their state back to the hub when operated from Main switch (app) or physically.

Also, for the record, before even the Groovy DTH, back when they were used with an alternative-brand hub/controller, all 3 impacted switches had associations configured on them, and they were near-instant. You couldn’t tell there they weren’t conventional 2-way lighting. But yes, that was before Smartthings. Still, I would expect associations to be as instant as they were in the past as the concept is the same, but it seems like the switch is taking a while before advising the target node’s endpoint to go on or off - as I said this is taking 10 to 20 seconds, which is pretty much useless when you need it for 2-way lighting.

So basically, now I have:

  1. On newer-type MH-S314 - working properly

  2. One older-type MH-S314 - working properly

  3. Two older-type MH-S312s - working properly

  4. Two older-type MH-S314s - not working properly

  5. One older-type MH-S312 - not working properly

All using the same driver (Test 3).

91

It sounds like the lifeline association group failed to set up properly when these joined. Could you try swapping one to the other driver, waiting a minute, and then swapping back? That should give it 2 opportunities to get the association correct.

1 Like
92

To be honest - one of these switches I had excluded and included like 3 times already, and tried changing drivers a few times. But I just re-did it, twice, on 2 different switches, and the behaviour is still the same.

Is there any way to verify this lifeline association suspicion? And is there any way to force it besides a driver change?

93

There’s a driver in the channel below called “Associator”. I haven’t updated it since they made some breaking changes to the app, but the part where it queries association groups still works. Install it and swap to it, then drag down on the screen to trigger a refresh. You’ll probably have to exit to the dashboard and then go back into detail, but it should populate the top capability with all the association group info.
https://account.smartthings.com/?redirect=https%3A%2F%2Fapi.smartthings.com%2Finvite%2FY723nEARKnMr%3F

Right now driver tries to set the lifeline during the added lifecycle, which gets called on install and when driver swapping. I can add in a call to do it in other places, but can’t get to that until tonight.

94

I downloaded it and went into the detail, these are the screenshots, but not knowledgeable enough on Zwave to draw any conclusions from it:

image
image738×1600 69.4 KB

image
image738×1600 60 KB

Not sure if Group 3 is the lifeline association you have been mentioning: here it is showing Nodes as EE.

Actually, I set up all 6 switches which are now on Edge to the Associator driver, and I realised this: all switches have an additional Association Group (5 for the 4-button switches, 3 for the 2-button switches). And - tellingly, the Nodes on all the switches working well was set to “01”, whereas the Nodes on all switches not working well was set to EB, E7, and EE. This with one exception - the new MH-S314 which did not manage to query the switch, seemingly, and remained like this after 2 attempts to set it to the Associator driver:

image
image738×1600 71 KB

But - yes, it seems your suspicion is correct, and likely I have no means of setting that Nodes field of the last Association group to 01.

Not to worry about it, I am just very grateful for all your work on this, so do it at your pace.

95

It is. There’s our problem. I don’t know why EE is already in there, but the device will reject any other association groups until we remove it. I’ll work out some more robust logic to wipe and set the lifelines.

1 Like
96

Thanks - appreciate it, light at the end of the tunnel, again :slightly_smiling_face: :pray:

2 Likes
97

For context: I have no idea where those EB, E7, and EE are coming from - but it is possible they are coming from the previous, very first installation. The switches are on three different levels (basement, ground, first) in the house, and all devices on each level were joined together through a cluster of “controllers” (hubs) - one on each level in the house. Still, the device (according to all documentation I have seen) is supposed to factory reset upon exclusion and re-inclusion, but I doubt this is truly happening. I have also tried factory resetting through various methods I found (at least 3 different methods) online, but still, the EE (or other association) remains after inclusion. I even tried sending the value 85 to parameter 255 which should force the device to factory reset - and yet, no luck.

Or else, my version of these switches is so old that none of the methods I found online works for their specific model.

Worth noting that all the devices that had this lifeline association were initially set up for two-way lighting - they were at the top and bottom of staircases.

I thought about using the “Z-Wave Tweaker 2” to try to set up the Lifeline Association via DTH before assigning the Edge driver, in case in cannot be done through code, but ideally it works through code, of course.

Meanwhile, when I can, today, I will join another couple of switches that have no automations linked to them, and that were never part of a 2-way lighting setup, to see what happens with those.

98

I joined 2 switches, one joined with Lifeline Association EE, and one ED. I am pretty sure there were no associations set up with the intention of 2-way lighting on these switches, ever, unless the previous installers moved the switches around which I think is a little unlikely. And the one with EE is not on the same level as the other one with EE. So my assumptions in the previous post are incorrect, and I have no idea of what the pattern is here. The only thing for sure is that it appears that most switches will have this Lifeline Association set to something or other. All the previous symptoms apply in these cases, namely that any associations created for the purposes of 2/3-way lighting are painfully slow (slower than routines) and that physical interactions with the switch are never reflected on the hub (or sometimes they are after a very, very long time.

So yes, enough testing and theorising from my end :slightly_smiling_face: I’ll wait for the code and divert my efforts onto other types of devices in the meantime.

1 Like
99

My guess (just a guess) is that at some point these devices were connected to a secondary controller (not the previous primary hub). That could have been a handheld remote, a wall mounted scene controller, even a diagnostic tool. :thinking:

@martin.borg , when you excluded them, did you do a general exclude? That might work better on these. I don’t know exactly how the ST implementation handles this: you might have to delete them from ST and THEN do a general exclusion to clear everything.

Otherwise going back to Groovy and using the zwave tweaker to manually clear everything would be worth a try.

There’s a very small possibility that these devices have firmware that force assigns them to a secondary controller (which may not even exist anymore) if they were sold as part of a set with either a handheld remote or a diagnostic tool. That kind of approach is more common in zigbee than zwave, but you did sometimes see it back before almost everyone had a smartphone. :thinking:

I’m thinking along these lines specifically because EE and ED are both invalid zwave device ID’s unless used for network admin purposes. Regular device id’s only go up to E8. So definitely something weird is going on,

1 Like
100

Thanks @JDRoberts - it appears you are right about the invalid IDs. Not sure about the firmware part. yes, the devices were bundled along in one sale along with a Zipato cluster (one Zipato tablet and two Zipato controllers - all of which were individual hubs with their own Zwave radio, but clustered together to form one network). You are likely right that those IDs were something strange that happened during that (original) implementation, or perhaps something Zipato-specific… However they were bundled up together (controllers + switches), I believe, by the local supplier, not by Zipato themselves, so the likelihood of a firmware change specifically to bind them to a specific Zipato controller seems unlikely to say the least.

I will wait for @philh30’s new code that tries to wipe and update the Lifeline Association - otherwise, it would mean having to swap the driver on all already-converted switches to say the ST-provided Zwave Switch driver, then removing all compatible drivers installed thus far, then excluding and re-including each device and hope everything goes well with re-including them with a DTH, assign them the Zwave Tweaker 2, assigning the Lifeline Association, re-exclude them, install the Edge drivers again, then re-include them. It just seems like a lot with plenty of room for error. So I’d rather wait a bit and see whether the change can be forced through code.

1 Like
101

It’s coming. I just need to figure out the logic for the configurable wake-up poll. I think I’ve got the lifeline group worked out where it’ll keep trying to clear and set it until the device reports that it’s set correctly. It should work on the first try though - what’s missing from the current version is just clearing it first (but I don’t want the driver to automatically clear it until it knows it’s incorrectly set). I’ll maybe have something ready tomorrow if I can find time to work on it. Hold off on migrating more devices for now.

2 Likes