(EDGE Driver-Mc): Z-Wave Edge Drivers and others with FIBARO devices:

Mariano_Colmenarejo · January 22, 2023, 3:05pm

Sorry, I don’t know this matter

William_Engel · January 22, 2023, 3:58pm

No problem. I will post my question in the appropriate message board. Regards.

John_K · January 22, 2023, 6:46pm

Hi Mariano,
Below are logs from one of the switches changing state using the physical switch, then from the app. For both test I changed the state from OFF to ON, then back to OFF again.

Switch:
2023-01-22T18:39:51.695656367+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T18:39:51.710778200+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={command_class=" %“, dynamic=false, end_point=2, generic_device_class=16, specific_device_class=1}, cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”, dst_channels={}, encap=“NONE”, payload=”\x02\x10\x01\x20\x25", src_channel=0, version=2}
2023-01-22T18:39:51.718013867+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:39:51.730897409+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T18:39:51.736594284+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T18:39:51.747091284+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T18:39:51.788884617+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T18:39:51.792722450+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T18:39:51.821590117+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:39:53.956177658+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T18:39:53.960794866+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={command_class=" %“, dynamic=false, end_point=2, generic_device_class=16, specific_device_class=1}, cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”, dst_channels={}, encap=“NONE”, payload=”\x02\x10\x01\x20\x25", src_channel=0, version=2}
2023-01-22T18:39:53.975484991+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:39:53.978771200+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T18:39:53.984476200+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T18:39:53.994835116+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T18:39:53.997812783+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T18:39:54.001369450+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T18:39:54.014689950+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled

App:
2023-01-22T18:42:20.840862915+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler capability
2023-01-22T18:42:20.851203206+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch1”,“positional_args”:{}}
2023-01-22T18:42:20.860134081+00:00 TRACE Z-Wave Switch and Child Mc Found CapabilityCommandDispatcher handler in zwave_switch
2023-01-22T18:42:20.863374123+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_on_handler in main driver >>>>>>>
2023-01-22T18:42:20.866559415+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_set_helper in main driver >>>>>>>
2023-01-22T18:42:20.884238498+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> 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}
2023-01-22T18:42:20.894902748+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(c69413b2) queued for radio transmission: CC:Switch Binary, CID:0x01
2023-01-22T18:42:20.907950415+00:00 INFO Z-Wave Switch and Child Mc <ZwaveChildDevice: f30e95d8-e9b6-4822-a928-5cb0e2e84e5b [bcaf48eb-c235-401c-be4a-4d9e57dd8e52][switch1] (switch1-Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2023-01-22T18:42:20.929354540+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:20.935566123+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:21.013485206+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(c69413b2) transmit status: TRANSMIT_COMPLETE_OK
2023-01-22T18:42:21.915843873+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={2}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-01-22T18:42:21.923987039+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(e7aa3164) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-01-22T18:42:21.926983331+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:22.065752748+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(e7aa3164) transmit status: TRANSMIT_COMPLETE_OK
2023-01-22T18:42:22.074038998+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T18:42:22.079106914+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\xFF”, src_channel=2, version=1}
2023-01-22T18:42:22.097005873+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T18:42:22.100060789+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T18:42:22.103532914+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch1”,“state”:{“value”:“on”}}
2023-01-22T18:42:22.117385373+00:00 INFO Z-Wave Switch and Child Mc <ZwaveChildDevice: f30e95d8-e9b6-4822-a928-5cb0e2e84e5b [bcaf48eb-c235-401c-be4a-4d9e57dd8e52][switch1] (switch1-Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2023-01-22T18:42:22.127035206+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:56.070207031+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler capability
2023-01-22T18:42:56.076114323+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“switch1”,“positional_args”:{}}
2023-01-22T18:42:56.084130156+00:00 TRACE Z-Wave Switch and Child Mc Found CapabilityCommandDispatcher handler in zwave_switch
2023-01-22T18:42:56.087035156+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_off_handler in main driver >>>>>>>
2023-01-22T18:42:56.090061406+00:00 PRINT Z-Wave Switch and Child Mc <<<<< switch_set_helper in main driver >>>>>>>
2023-01-22T18:42:56.095086365+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> sending Z-Wave command: {args={duration=0, target_value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“SET”, dst_channels={2}, encap=“AUTO”, payload=“\x00\x00”, src_channel=0, version=2}
2023-01-22T18:42:56.103585740+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(c5e8f814) queued for radio transmission: CC:Switch Binary, CID:0x01
2023-01-22T18:42:56.113251281+00:00 INFO Z-Wave Switch and Child Mc <ZwaveChildDevice: f30e95d8-e9b6-4822-a928-5cb0e2e84e5b [bcaf48eb-c235-401c-be4a-4d9e57dd8e52][switch1] (switch1-Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T18:42:56.122692615+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:56.127704490+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:56.245556240+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(c5e8f814) transmit status: TRANSMIT_COMPLETE_OK
2023-01-22T18:42:57.115183031+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_BINARY”, cmd_id=“GET”, dst_channels={2}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-01-22T18:42:57.123271531+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(590f2219) queued for radio transmission: CC:Switch Binary, CID:0x02
2023-01-22T18:42:57.126264656+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T18:42:57.265912864+00:00 TRACE Z-Wave Switch and Child Mc Z-Wave command(590f2219) transmit status: TRANSMIT_COMPLETE_OK
2023-01-22T18:42:57.276469323+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T18:42:57.286405906+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={0}, encap=“NONE”, payload=“\x00”, src_channel=2, version=1}
2023-01-22T18:42:57.304641656+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T18:42:57.307646406+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T18:42:57.311202573+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch1”,“state”:{“value”:“off”}}
2023-01-22T18:42:57.344732906+00:00 INFO Z-Wave Switch and Child Mc <ZwaveChildDevice: f30e95d8-e9b6-4822-a928-5cb0e2e84e5b [bcaf48eb-c235-401c-be4a-4d9e57dd8e52][switch1] (switch1-Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T18:42:57.358087489+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled

Thanks,
John

Mariano_Colmenarejo · January 22, 2023, 7:01pm

Hi @John_K

In these logs I see that all has works well.
You have powered on and off the physical main switch and the states have been updated.

You have turned switch1 on and off in the app and the on and off commands have been sent and the child and multicomponent states have been updated with the response from the device

Mariano_Colmenarejo · January 22, 2023, 7:55pm

@John_K
If you can send me the logs by clicking on the physical switch that does not update the status in the app.
Next week I will not be able to change anything

John_K · January 22, 2023, 8:32pm

Below are logs from a few of the switches that are not showing status change in the app when I toggle physical SW2.

2023-01-22T20:24:14.243990720+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T20:24:14.290496997+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:24:14.296536892+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T20:24:14.306464634+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:24:14.309668865+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:24:14.313797757+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T20:24:14.334634459+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T20:24:17.907491428+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:24:17.912017331+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={command_class=" %“, dynamic=false, end_point=2, generic_device_class=16, specific_device_class=1}, cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”, dst_channels={}, encap=“NONE”, payload=”\x02\x10\x01\x20\x25", src_channel=0, version=2}
2023-01-22T20:24:17.927186034+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled
2023-01-22T20:24:17.930476430+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:24:17.936490546+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T20:24:17.947475468+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:24:17.950562965+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:24:17.954189234+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: bcaf48eb-c235-401c-be4a-4d9e57dd8e52 [51] (Basement Stairs Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T20:24:17.967357147+00:00 DEBUG Z-Wave Switch and Child Mc Basement Stairs Relay device thread event handled

2023-01-22T20:26:59.980579238+00:00 DEBUG Z-Wave Switch and Child Mc John Office Fan Relay device thread event handled
2023-01-22T20:26:59.983770404+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:26:59.989622279+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ba9fb664-cd31-42c1-940b-a7357785f7fb [60] (John Office Fan Relay)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-01-22T20:27:00.000091279+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:27:00.003084529+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:27:00.006495154+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ba9fb664-cd31-42c1-940b-a7357785f7fb [60] (John Office Fan Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2023-01-22T20:27:00.019460779+00:00 DEBUG Z-Wave Switch and Child Mc John Office Fan Relay device thread event handled
2023-01-22T20:27:01.615951363+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:27:01.620525780+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ba9fb664-cd31-42c1-940b-a7357785f7fb [60] (John Office Fan Relay)> received Z-Wave command: {args={command_class=" %“, dynamic=false, end_point=2, generic_device_class=16, specific_device_class=1}, cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”, dst_channels={}, encap=“NONE”, payload=”\x02\x10\x01\x20\x25", src_channel=0, version=2}
2023-01-22T20:27:01.634798030+00:00 DEBUG Z-Wave Switch and Child Mc John Office Fan Relay device thread event handled
2023-01-22T20:27:01.681918446+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:27:01.687614030+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ba9fb664-cd31-42c1-940b-a7357785f7fb [60] (John Office Fan Relay)> received Z-Wave command: {args={value=“ON_ENABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\xFF”, src_channel=0, version=1}
2023-01-22T20:27:01.697589321+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:27:01.700956238+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:27:01.704417155+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ba9fb664-cd31-42c1-940b-a7357785f7fb [60] (John Office Fan Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2023-01-22T20:27:01.717634613+00:00 DEBUG Z-Wave Switch and Child Mc John Office Fan Relay device thread event handled

2023-01-22T20:29:02.887278736+00:00 DEBUG Z-Wave Switch and Child Mc Dining Room Relay device thread event handled
2023-01-22T20:29:02.890845611+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:29:02.896812528+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: afdf9e61-bed4-4b6b-b760-0053b839d5bb [58] (Dining Room Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T20:29:02.907466278+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:29:02.910822944+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:29:02.914582236+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: afdf9e61-bed4-4b6b-b760-0053b839d5bb [58] (Dining Room Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T20:29:02.934249861+00:00 DEBUG Z-Wave Switch and Child Mc Dining Room Relay device thread event handled
2023-01-22T20:29:04.665844820+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:29:04.670460486+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: afdf9e61-bed4-4b6b-b760-0053b839d5bb [58] (Dining Room Relay)> received Z-Wave command: {args={command_class=" %“, dynamic=false, end_point=2, generic_device_class=16, specific_device_class=1}, cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”, dst_channels={}, encap=“NONE”, payload=”\x02\x10\x01\x20\x25", src_channel=0, version=2}
2023-01-22T20:29:04.685098903+00:00 DEBUG Z-Wave Switch and Child Mc Dining Room Relay device thread event handled
2023-01-22T20:29:04.688304320+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:29:04.694114695+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: afdf9e61-bed4-4b6b-b760-0053b839d5bb [58] (Dining Room Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T20:29:04.703541361+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:29:04.706476695+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:29:04.709960486+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: afdf9e61-bed4-4b6b-b760-0053b839d5bb [58] (Dining Room Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T20:29:04.723271820+00:00 DEBUG Z-Wave Switch and Child Mc Dining Room Relay device thread event handled

2023-01-22T20:30:50.510531166+00:00 DEBUG Z-Wave Switch and Child Mc Master Bathroom Relay device thread event handled
2023-01-22T20:30:50.513936791+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:30:50.519906124+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ed61995b-75a5-433d-ae14-137bb02734c9 [5E] (Master Bathroom Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T20:30:50.530510207+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:30:50.533721624+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:30:50.537412041+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ed61995b-75a5-433d-ae14-137bb02734c9 [5E] (Master Bathroom Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T20:30:50.554307249+00:00 DEBUG Z-Wave Switch and Child Mc Master Bathroom Relay device thread event handled
2023-01-22T20:30:52.196908582+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:30:52.201473249+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ed61995b-75a5-433d-ae14-137bb02734c9 [5E] (Master Bathroom Relay)> received Z-Wave command: {args={command_class=" %“, dynamic=false, end_point=2, generic_device_class=16, specific_device_class=1}, cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”, dst_channels={}, encap=“NONE”, payload=”\x02\x10\x01\x20\x25", src_channel=0, version=2}
2023-01-22T20:30:52.285533082+00:00 DEBUG Z-Wave Switch and Child Mc Master Bathroom Relay device thread event handled
2023-01-22T20:30:52.288712916+00:00 TRACE Z-Wave Switch and Child Mc Received event with handler unnamed
2023-01-22T20:30:52.294515374+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ed61995b-75a5-433d-ae14-137bb02734c9 [5E] (Master Bathroom Relay)> received Z-Wave command: {args={value=“OFF_DISABLE”}, cmd_class=“SWITCH_BINARY”, cmd_id=“REPORT”, dst_channels={}, encap=“NONE”, payload=“\x00”, src_channel=0, version=1}
2023-01-22T20:30:52.304891332+00:00 TRACE Z-Wave Switch and Child Mc Found ZwaveDispatcher handler in zwave_switch
2023-01-22T20:30:52.307882166+00:00 PRINT Z-Wave Switch and Child Mc <<<<< zwave_handlers_report in main driver >>>>>>>
2023-01-22T20:30:52.311401332+00:00 INFO Z-Wave Switch and Child Mc <ZwaveDevice: ed61995b-75a5-433d-ae14-137bb02734c9 [5E] (Master Bathroom Relay)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2023-01-22T20:30:52.324895791+00:00 DEBUG Z-Wave Switch and Child Mc Master Bathroom Relay device thread event handled

Mariano_Colmenarejo · January 22, 2023, 8:40pm

@John_K

All these that do not work is by pressing switch 2 on the device?

John_K · January 22, 2023, 9:21pm

I can control the relay from the switch and the app. The app only shows a state change when toggled from within the app. If I toggle the physical switch, there is no state change recognized by the app.

John_K · January 22, 2023, 9:24pm

My use case: Turning on switch 2 would also turn on desk lamps, or a series of outdoor flood lights, based on the state change from one of these switches. The original load works when toggling the switch, but since there is no state change in the app, I’m unable to use it to trigger other devices.

Switch 1 is working as expected.

Mariano_Colmenarejo · January 22, 2023, 9:30pm

Sorry, the device is sending the status with the cmd_class=“MULTI_CHANNEL”, cmd_id=“CAPABILITY_REPORT”,

I don’t know how to handle this command class.

I will try to see it in the lua libraries, but this next week I will not be able to do anything.

If someone who knows how to handle it wants to comment on something, they will be welcome.

Mariano_Colmenarejo · January 26, 2023, 11:48pm

Hi @John_K

I have checked with smartthing and it seems that it is very rare for commands to be sent in this way.

This device has been working fine for other users since September 2022. @Cleon @kwichma @greenzkool

Your devices may be older and need to be updated to another firmware version.

This is the version that those that work well have

ver:17.02 zwv:3.67

Please, could you check your firmware version pairing one device with DTH to see the device data?

Mariano_Colmenarejo · January 27, 2023, 2:05pm

@Sediento

Added profile with 6 parameter configuration Siren and DoorBell in preferences.
Try if works

───────────────────────────────────────────────────
 Name         Z-Wave Siren Mc
 Version      2023-01-27T13:57:03.011637006        
───────────────────────────────────────────────────
- id: 0131/0003/1083
    deviceLabel: Zipato Siren
    manufacturerId: 0x0131
    productType: 0x0003
    productId: 0x1083
    deviceProfileName: zipato-alarm-battery # Modified by M. Colmenarejo

Sediento · January 27, 2023, 7:15pm

@Mariano_Colmenarejo, you nailed it!
I can change every single option.

I’ve noticed that this siren can’t work as “only strobe” or “only siren” so when you presses any of those buttons it defaults to “Siren and strobe”.

sflamm · January 29, 2023, 11:43am

Can you please support the Fibaro Smart Implant FGBS-222? I need a driver that works with the external temperature probes (like the ones you have created for the older devices)

The driver at the link below is NOT working at all for anything but a switch and there is no active work being done on it

https://community.smartthings.com/t/st-edge-driver-for-fibaro-smart-implant-beta/247654

Mariano_Colmenarejo · January 29, 2023, 2:16pm

Hi @sflamm

Sorry, developing driver for a complex device like this, without physically having one to debug with is very difficult.

I also already have too many drivers to maintain at the moment.

I hope they finish developing the existing driver

sflamm · January 29, 2023, 7:48pm

We can solve that problem - either send you your own or money to buy one … this is very important to many (need such to monitor an aquarium or pool etc)

Would you be willing to do so if I provide it to you ?

Mariano_Colmenarejo · January 29, 2023, 10:24pm

Hi @sflamm

As I also told you, I have many other drivers to keep, more than I would like to have.

And on the other hand, I already told other users that in this transition Fibaro is not doing anything at all for its customers who use smartthings. Unlike other manufacturers who are investing in migrating their old and new products.

Fibaro only to sell their products and others who do the job by the face.

I’m sorry, it’s nothing personal, but at the moment I won’t be able to dedicate time to this.

Other developers may have time to dedicate to this.

sflamm · January 29, 2023, 11:48pm

Thanks for your thoughtful reply.

A couple questions if you do not mind:

Is there a device that supports an external temp probe DS18B20 that we can still buy (that you have a driver that supports)?
Does your driver work for: Fibaro FGK-107 - Z-Wave Door/Window Sensor
I believe it does from reading the thread… but wanted to confirm… not sure where or if this can still be bought if it can it will meet my needs (instead of the Fibaro Smart Implant)
Would you be willing to create the Fibaro Smart Implant driver or a driver for a device that supports an external probe as a consulting project ?

Mariano_Colmenarejo · January 30, 2023, 12:16pm

Hi @sflamm

Indeed, it is not the same to create a driver for all the possible functions of this device, than to create a profile to use the internal temperature probe, an external probe and the 2 output switches.

But my ignorance, I see in the documentation that you can use 6 temperature probes placed in parallel to the input. Does this show the average temperature of the connected probes?
Are you going to use it only with an external probe?

I ask because it seems to reserve 6 endpoints from 8 to 13 for the 6 possible probes. I don’t know how to identify them, if they are multiplexed or how

This week I will not be able to do anything, until Saturday or Sunday.

Since capabilities cannot be repeated within the same component, I propose a profile with 4 components:

main: external temperature
Internal Temp
out 1
out 2

Out1 and Out2 are necessary?

As it would be inside the Z-wave sensor driver, a virtual child thermostat could be created for the external temperature probe

TapioX · January 30, 2023, 2:02pm

To 1-wire bus (multidrop serial bus) is possible to connect multiple temperature measurement devices. Each device has unique address.
Smart Implant is supporting 6 separate temperature measurements.

More
1 wire protocol basics | Powering Modes,Signaling Modes (rfwireless-world.com)

(EDGE Driver-Mc): Z-Wave Edge Drivers and others with FIBARO devices:

Customers

Developers

Download the SmartThings App