Support/Issues with GEZW4203

I’ll be out of town till Friday so I won’t be able to try this till then.

Also wondering if @harobinson has a different hub than I do hence not seeing the Z-Wave transmit errors that I’m seeing. Perhaps on a v2/v3 hub it looks like the transmit happened successfully even if it didn’t vs on my Connect Home/Wi-fi hub, I’m actually seeing the transmission errors. It could also explain the Transmit Complete No Ack messages if the hub sent the message unencrypted and the device never responded.

Suffice to say, it’s too coincidental that both of our devices were 1) working fine on a Groovy DTH for years; 2) things stopped working upon moving to an Edge driver; 3) are using S2 security; and 4) exhibit the same behavior of the hub being able to receive messages but seemingly not transmit them.

Is there any way you can tweak the driver to actually send the commands with the S2 encap instead of Auto for those devices that are authenticated with S2?

Looks like a problem on the backend of the channel subscription service to me.

I think the common thread is that you both excluded and re-joined devices and you’re both having z-wave radio issues. It could be some fundamental issue with the ST z-wave implementation (I have my doubts about it - I found it impossible to keep several S2 sensors alive on my mesh), but I’m not convinced of that at this point.

You’re getting NO_ACK and FAIL which means the device didn’t receive the message. He’s getting an ACK but the device isn’t acting on it. You have a battery powered device that is notorious for comms issues, while his is mains powered. I’m thinking root cause is going to end up being different.

It’s the same channel as the zwave lock driver. Are you able to get in through the driver menu in the app?

Yes, if I were at home and could reach my hub to install it. Plus the lock went offline after several hours yesterday.

Try the channel link to the top of the thread below:

Same problem. Internal server error.

Found a different way. Went into the ST app, then to my hub, and clicked on the Drivers in the three dot menu. I was able to install it by clicking on your Z-Wave drivers channel and logging in with my Samsung device vs my login ID.

Now, if only the lock were online :-/

Yeah, the part where they don’t let you change drivers on an offline device is frustrating. I think I’ve tricked it before by swiping down to refresh and then quickly going to the driver menu. Maybe Todd’s API+ or the CLI let’s you do it?

Well, what do you know. API Browser let me change it and as soon as it did, the device came back online. Here are the screenshots of the explorer. Just about every command class is secure. I’m guessing that your explorer uses something like the ZWAVEPLUSINFO command class which is not secure and would explain why the device came back online when the hub was able to communicate with the lock.

I still think your issue is probably the direct routing to the hub. Though I don’t know whether the source that I’m pulling the [71]<->[01] from is completely reliable.

Unless you’re also seeing ACK’d messages with no action. You don’t have too many failed showing up there.

Well, to test your theory, I ordered a Minoston Z-Wave Plus Outlet that supports S2 and uses a 700 Z-Wave chip. Gonna put it roughly in between the hub and the lock when I get home.

I’m somewhat skeptical since the lock has been working fine for over 3 years and this only started once I switched it over to Edge.

2 Likes

Well @philh30 and @h0ckeysk8er, this is above my skill level. I was going to take a small project over the next few days to see if I can write a custom driver for the device that is basic enough to turn the switch on and off.

But if you want to retrieve any log files or anything else from my device, I’ll be happy to.

@harobinson Sorry - most of that was a sidebar regarding his lock. If you’re able to get that other driver to install so we can look at which command classes are secure, that’d be good. There were a bunch of people complaining yesterday about channel links not working, so that appears to be a platform issue but I don’t know whether it’s been resolved.

Otherwise, try excluding and then re-joining the switch. If trouble persists that time then I would try again while skipping the prompts to enter the DSK during inclusion so the switch joins at a lower security level.

1 Like

That’s happening to Lots of people. :disappointed_relieved:

Unable to join channels (25 Jan 2023)

Here’s the test I just ran.

  1. I downloaded the Z=Wave Explorer driver to my hub.
  2. I removed the device from Smarthings, did a full exclude from the hub, did a Z-wave repair
  3. Reset the device to factory configuration.
  4. Add the device, the UI gave me no choice but to add it in secure mode, and selected the “GE Z-Wave Switch/Dimmer/Fan/Outlet” driver.
  5. I selected the Z-Wave Explorer driver.
    Here is the output from that point on with annotations about actions that I tried. It is now in a state where pressing any button from the UI will give a “Network/Server error”.

-------- Log attached

2023-01-25T21:33:20.099274604+00:00 TRACE Z-Wave Explorer  Setup driver zwub-explorer with lifecycle handlers:
DeviceLifecycleDispatcher: zwub-explorer
  default_handlers:
    init:
    added:
    doConfigure:
    removed:
    driverSwitched:
  child_dispatchers:

2023-01-25T21:33:20.106711937+00:00 TRACE Z-Wave Explorer  Setup driver zwub-explorer with Capability handlers:
CapabilityCommandDispatcher: zwub-explorer
  default_handlers:
    refresh:
      refresh
  child_dispatchers:

2023-01-25T21:33:20.107714604+00:00 TRACE Z-Wave Explorer  Setup driver zwub-explorer with Z-Wave handlers:
ZwaveDispatcher: zwub-explorer
  default_handlers:
    WAKE_UP:
      NOTIFICATION
  child_dispatchers:

2023-01-25T21:33:20.155208604+00:00 TRACE Z-Wave Explorer  Z-Wave Device: e36c7b5a-b4db-499e-bc05-f097492cfc6a
Manufacturer: 0x0063 Product Type: 0x4F50 Product ID: 0x3034
	[0]: SWITCH_BINARY, ASSOCIATION, ASSOCIATION_GRP_INFO, VERSION, MANUFACTURER_SPECIFIC, DEVICE_RESET_LOCALLY, POWERLEVEL, CENTRAL_SCENE, CONFIGURATION, SCENE_ACTUATOR_CONF, SCENE_ACTIVATION, FIRMWARE_UPDATE_MD, ZWAVEPLUS_INFO, TRANSPORT_SERVICE, SUPERVISION, SECURITY_2, APPLICATION_STATUS
2023-01-25T21:33:20.156271604+00:00 TRACE Z-Wave Explorer  Received event with handler _resync
2023-01-25T21:33:20.157846604+00:00 TRACE Z-Wave Explorer  Received event with handler environment_info
2023-01-25T21:33:20.187385937+00:00 TRACE Z-Wave Explorer  Found DeviceLifecycleDispatcher handler in zwub-explorer
2023-01-25T21:33:20.190780604+00:00 ERROR Z-Wave Explorer  GE Plug In Switch 14298 thread encountered error: [string "st/dispatcher.lua"]:232: attempt to concatenate a userdata value (local 'value')
2023-01-25T21:33:20.199555937+00:00 TRACE Z-Wave Explorer  Received event with handler environment_info
2023-01-25T21:33:20.200567937+00:00 DEBUG Z-Wave Explorer  Z-Wave hub node ID environment changed.
2023-01-25T21:33:20.202081937+00:00 TRACE Z-Wave Explorer  Received event with handler device_lifecycle
2023-01-25T21:33:20.211544604+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received lifecycle event: added
2023-01-25T21:33:20.213494937+00:00 TRACE Z-Wave Explorer  Found DeviceLifecycleDispatcher handler in zwub-explorer
2023-01-25T21:33:20.215013271+00:00 TRACE Z-Wave Explorer  Found CapabilityCommandDispatcher handler in zwub-explorer
2023-01-25T21:33:20.220114604+00:00 ERROR Z-Wave Explorer  GE Plug In Switch 14298 thread encountered error: [string "st/dispatcher.lua"]:233: Error encountered while processing event for <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)>:
    arg1: added
    arg2: table: 0x1344f28
[string "st/dispatcher.lua"]:232: attempt to concatenate a userdata value (local 'value')
2023-01-25T21:33:20.221772604+00:00 TRACE Z-Wave Explorer  Received event with handler device_lifecycle
2023-01-25T21:33:20.223396271+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received lifecycle event: driverSwitched
2023-01-25T21:33:20.225432604+00:00 TRACE Z-Wave Explorer  Found DeviceLifecycleDispatcher handler in zwub-explorer
2023-01-25T21:33:20.227213937+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:33:20.255559604+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:33:20.579031604+00:00 TRACE Z-Wave Explorer  Received event with handler device_lifecycle
2023-01-25T21:33:20.582433271+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received lifecycle event: infoChanged
2023-01-25T21:33:20.589753604+00:00 TRACE Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received unhandled lifecycle event: infoChanged
2023-01-25T21:33:20.593150938+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:33:50.006588952+00:00 TRACE Z-Wave Explorer  Received event with handler device_lifecycle
2023-01-25T21:33:50.014755618+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received lifecycle event: infoChanged
2023-01-25T21:33:50.025184618+00:00 TRACE Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received unhandled lifecycle event: infoChanged
2023-01-25T21:33:50.026741952+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
---------- PRESSING BUTTON ON SWITCH
2023-01-25T21:35:12.757395067+00:00 TRACE Z-Wave Explorer  Received event with handler unnamed
2023-01-25T21:35:12.765687401+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received Z-Wave command: {args={current_value=0, duration=0, target_value=0, value=0}, cmd_class="BASIC", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\x00\x00\x00", src_channel=0, version=2}
2023-01-25T21:35:12.767231734+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:35:14.751670735+00:00 TRACE Z-Wave Explorer  Received event with handler unnamed
2023-01-25T21:35:14.753141402+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received Z-Wave command: {args={value="OFF_DISABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\x00", src_channel=0, version=1}
2023-01-25T21:35:14.756302068+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:35:14.808608402+00:00 TRACE Z-Wave Explorer  Received event with handler unnamed
2023-01-25T21:35:14.816674068+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received Z-Wave command: {args={key_attributes="KEY_PRESSED_1_TIME", scene_number=1, sequence_number=23, slow_refresh=true}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="S2_AUTH", payload="\x17\x80\x01", src_channel=0, version=3}
2023-01-25T21:35:14.818210068+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:35:21.834827405+00:00 TRACE Z-Wave Explorer  Received event with handler unnamed
2023-01-25T21:35:21.839487738+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received Z-Wave command: {args={value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\xFF", src_channel=0, version=1}
2023-01-25T21:35:21.846399405+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:35:21.995643405+00:00 TRACE Z-Wave Explorer  Received event with handler unnamed
2023-01-25T21:35:22.003501405+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received Z-Wave command: {args={key_attributes="KEY_HELD_DOWN", scene_number=1, sequence_number=24, slow_refresh=true}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="S2_AUTH", payload="\x18\x82\x01", src_channel=0, version=3}
2023-01-25T21:35:22.005061738+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
2023-01-25T21:35:22.195718072+00:00 TRACE Z-Wave Explorer  Received event with handler unnamed
2023-01-25T21:35:22.204139738+00:00 INFO Z-Wave Explorer  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (GE Plug In Switch 14298)> received Z-Wave command: {args={key_attributes="KEY_RELEASED", scene_number=1, sequence_number=25, slow_refresh=true}, cmd_class="CENTRAL_SCENE", cmd_id="NOTIFICATION", dst_channels={}, encap="S2_AUTH", payload="\x19\x81\x01", src_channel=0, version=3}
2023-01-25T21:35:22.205646072+00:00 DEBUG Z-Wave Explorer  GE Plug In Switch 14298 device thread event handled
---------- ABOVE ACTIONS HAD NO EFFECT ON THE ON/OFF INDICATOR IN THE APP
----------- NOW PRESSING ON BUTTON ON UI
NOTHING IN THE LOG


Hope this helps.

BTW: My device is on a plug, so easy to reset the power to the device.

Did this get fixed over night? Tried to reproduce for support and it magically worked.

Thanks @philh30, I saw the driver was updated recently. Good to know what you found.

Thanks

Not my doing. Not sure what to make of that…

1 Like

Ok, so I wanted to give the final details on the GE Plug-in outlet that didn’t work and then magically worked a few days later.

  1. My hub was updated on 2023-01-25 9:15 PM UTC.
  1. My log when I did an on/off from the UI.
2023-01-27T15:36:31.617986012+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Received event with handler capability
2023-01-27T15:36:31.660875113+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(eb21bece) queued for radio transmission: CC:Basic, CID:0x01
2023-01-27T15:36:31.673201273+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> received command: {"args":{},"capability":"switch","command":"on","component":"main","positional_args":{}}
2023-01-27T15:36:31.677140908+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found CapabilityCommandDispatcher handler in ge-zwave-switch
2023-01-27T15:36:31.689782559+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> sending Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\xFF", src_channel=0, version=1}
2023-01-27T15:36:31.707338666+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:31.713938965+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:31.823710823+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(eb21bece) transmit status: TRANSMIT_COMPLETE_OK
2023-01-27T15:36:31.924798342+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Received event with handler unnamed
2023-01-27T15:36:31.929042129+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> received Z-Wave command: {args={value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\xFF", src_channel=0, version=1}
2023-01-27T15:36:31.955035786+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:36:31.956030283+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2023-01-27T15:36:31.958149009+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:36:31.959451993+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:32.728500325+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(bb621048) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-01-27T15:36:32.735137976+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> sending Z-Wave command: {args={}, cmd_class="SWITCH_BINARY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-01-27T15:36:32.736842494+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:33.014458900+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(bb621048) transmit status: TRANSMIT_COMPLETE_OK
2023-01-27T15:36:33.036574619+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Received event with handler unnamed
2023-01-27T15:36:33.044114387+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> received Z-Wave command: {args={current_value="ON_ENABLE", duration=0, target_value="ON_ENABLE", value="ON_ENABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\xFF\xFF\x00", src_channel=0, version=2}
2023-01-27T15:36:33.065830573+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:36:33.066813064+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2023-01-27T15:36:33.069186917+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:36:33.070498239+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:58.711420323+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Received event with handler capability
2023-01-27T15:36:58.743767989+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(f2081438) queued for radio transmission: CC:Basic, CID:0x01
2023-01-27T15:36:58.747158656+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> received command: {"args":{},"capability":"switch","command":"off","component":"main","positional_args":{}}
2023-01-27T15:36:58.748660656+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found CapabilityCommandDispatcher handler in ge-zwave-switch
2023-01-27T15:36:58.750221989+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> sending Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="AUTO", payload="\x00", src_channel=0, version=1}
2023-01-27T15:36:58.763118989+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:58.769751989+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:58.902311989+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(f2081438) transmit status: TRANSMIT_COMPLETE_OK
2023-01-27T15:36:59.045266989+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Received event with handler unnamed
2023-01-27T15:36:59.048713656+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> received Z-Wave command: {args={value="OFF_DISABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\x00", src_channel=0, version=1}
2023-01-27T15:36:59.073687990+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:36:59.074885990+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2023-01-27T15:36:59.082813656+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:36:59.146339990+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:36:59.781499323+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(127fba75) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-01-27T15:36:59.788152323+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> sending Z-Wave command: {args={}, cmd_class="SWITCH_BINARY", cmd_id="GET", dst_channels={}, encap="AUTO", payload="", src_channel=0, version=1}
2023-01-27T15:36:59.789812990+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled
2023-01-27T15:37:00.124578657+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Z-Wave command(127fba75) transmit status: TRANSMIT_COMPLETE_OK
2023-01-27T15:37:00.155232990+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Received event with handler unnamed
2023-01-27T15:37:00.156624657+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> received Z-Wave command: {args={current_value="OFF_DISABLE", duration=0, target_value="OFF_DISABLE", value="OFF_DISABLE"}, cmd_class="SWITCH_BINARY", cmd_id="REPORT", dst_channels={}, encap="S2_AUTH", payload="\x00\x00\x00", src_channel=0, version=2}
2023-01-27T15:37:00.194314323+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:37:00.195300990+00:00 INFO GE Z-Wave Switch/Dimmer/Fan/Outlet  <ZwaveDevice: e36c7b5a-b4db-499e-bc05-f097492cfc6a [43] (Deck)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2023-01-27T15:37:00.197482323+00:00 TRACE GE Z-Wave Switch/Dimmer/Fan/Outlet  Found ZwaveDispatcher handler in ge-zwave-switch
2023-01-27T15:37:00.198776323+00:00 DEBUG GE Z-Wave Switch/Dimmer/Fan/Outlet  GE Plug In Switch 14298 device thread event handled

I didn’t see a change in the log, but now it works. @h0ckeysk8er … did your Schlage lock also start working?

I have a Connect Home/Wi-Fi hub, so mine did not receive new firmware. But apparently, there will be one starting today.

1 Like