Issue with driver not sure how to report it

hi im having an issue with the zigbee switch mc driver and the (zigbee switch driver )but dont know where to report it .
the issue is the sonoff zbmini has a conection for a switch on it when the switch is used the device works but does not show the change in status in smartthings .
here is a log if anyone could help point me in the right place that would be great
thanks
martin
│ 21 │ bc53adfe-d18f-4ea4-9610-6aade6696b7a │ Zigbee Switch Mc │
└────┴──────────────────────────────────────┴───────────────────────────────────────┘
? Select a driver. 21
2022-07-25T11:39:43.546212654+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
2022-07-25T11:39:48.715929697+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T11:39:48.722407322+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -41, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x02, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T11:39:48.734180863+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T11:39:48.737590155+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T11:39:48.741175697+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 1
2022-07-25T11:39:48.746434697+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -41 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T11:39:48.759856280+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T11:39:52.670050322+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T11:39:52.674785822+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -41, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T11:39:52.684637697+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T11:39:52.688042364+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T11:39:52.691210197+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 0
2022-07-25T11:39:52.694524156+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -41 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T11:39:52.705232114+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T11:39:59.113449990+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T11:39:59.120309240+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -40, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T11:39:59.146196906+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T11:39:59.150396031+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T11:39:59.153535281+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 1
2022-07-25T11:39:59.157681823+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -40 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T11:39:59.168472823+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T11:40:02.290304990+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T11:40:02.294889698+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -44, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x05, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T11:40:02.305691365+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T11:40:02.308778032+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T11:40:02.311946490+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 0
2022-07-25T11:40:02.315267657+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -44 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T11:40:02.326028823+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T11:40:07.165524282+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T11:40:07.172094491+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -40, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x06, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T11:40:07.183743324+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T11:40:07.187244657+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T11:40:07.192147032+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 1
2022-07-25T11:40:07.198735282+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -40 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T11:40:07.210510074+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T11:40:08.631057074+00:00 TRACE Zigbee Switch Mc Received event with handler device_lifecycle
2022-07-25T11:40:08.638709699+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received lifecycle event: infoChanged
2022-07-25T11:40:08.649240866+00:00 TRACE Zigbee Switch Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-07-25T11:40:08.652169366+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 5.0
2022-07-25T11:40:08.655080657+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= Switch
2022-07-25T11:40:08.658151491+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 0
2022-07-25T11:40:08.661097157+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 1.0
2022-07-25T11:40:08.664109949+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 10
2022-07-25T11:40:08.666990282+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]=
2022-07-25T11:40:08.669878116+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 10
2022-07-25T11:40:08.672797324+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= No
2022-07-25T11:40:08.675734366+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 255
2022-07-25T11:40:08.678644741+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 0
2022-07-25T11:40:08.681604074+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 0.0
2022-07-25T11:40:08.684456241+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 1.0
2022-07-25T11:40:08.687384949+00:00 PRINT Zigbee Switch Mc device.preferences[infoChanged]= 10.0
2022-07-25T11:40:08.690436324+00:00 PRINT Zigbee Switch Mc Device ID <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)>
2022-07-25T11:40:08.693228116+00:00 PRINT Zigbee Switch Mc Manufacturer >>> SONOFF Manufacturer_Len >>> 6
2022-07-25T11:40:08.696488407+00:00 PRINT Zigbee Switch Mc Model >>> 01MINIZB Model_len >>> 8
2022-07-25T11:40:08.699451657+00:00 PRINT Zigbee Switch Mc Memory >>>>>>> 990.6083984375 Kbytes
2022-07-25T11:40:08.702242491+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T11:40:13.556217450+00:00 DEBUG Zigbee Switch Mc driver device thread event handled
listening for logs… done

Tagging @Mariano_Colmenarejo

1 Like

Hi @montyfert

I remember that the problem that existed with the sonoff switch zigbee Mini was that it sent duplicate messages:

  • For On send one with value = true and another with value = 1
  • For Off it sent one with value= false and other with value=0

The standard is true and false.

The solution I applied was not to emit events when a value=0 or value=1 was received.

In the logs that you send, only values 1 and 0 are received and therefore no on and off events are emitted.

Will they have changed the firmware of the newer switches?

With the stock zigbee switch driver it doesn’t work either, does it?

Have they changed something in the lua zigbee libraries?

@Paul_Oliver please, Do the sonoff mini still work well for you?

1 Like

Mariano, I currently have 2 Sonoff ZBMini in operation using your driver and the work really well.

2 Likes

hi but do they work with a switch attached. phisaccaly they do but it does not change the status in the app.even the physical switch on the mini didnt change the status in the app.

this is the log of on/off with the physical switchon the zbmini neither on nor off altered the status of the app (mc driver)

│ 22 │ bc53adfe-d18f-4ea4-9610-6aade6696b7a │ Zigbee Switch Mc │
└────┴──────────────────────────────────────┴───────────────────────────────────────┘
? Select a driver. 22
2022-07-25T16:31:31.942036551+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T16:31:31.951838259+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -60, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x53, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T16:31:31.979480051+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T16:31:31.982645967+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T16:31:31.986099592+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 1
2022-07-25T16:31:31.993606759+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -60 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T16:31:32.020372717+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
2022-07-25T16:31:39.351814010+00:00 TRACE Zigbee Switch Mc Received event with handler zigbee
2022-07-25T16:31:39.358265010+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -63, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x54, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T16:31:39.371390760+00:00 TRACE Zigbee Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-07-25T16:31:39.374612093+00:00 INFO Zigbee Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T16:31:39.378246593+00:00 PRINT Zigbee Switch Mc value.value >>>>>>>>>>> 0
2022-07-25T16:31:39.382659885+00:00 INFO Zigbee Switch Mc <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 255 … RSSI: -63 dBm”},“visibility”:{“displayed”:false}}
2022-07-25T16:31:39.398987426+00:00 DEBUG Zigbee Switch Mc SONOFF Switch device thread event handled
listening for logs… done

and if it helps this is the log for the zigbee switch driver (not mc) using physical switch
thanks for the help in advance much apreciated
│ 21 │ f2e891c6-00cc-446c-9192-8ebda63d9898 │ Zigbee Switch │
│ 22 │ bc53adfe-d18f-4ea4-9610-6aade6696b7a │ Zigbee Switch Mc │
└────┴──────────────────────────────────────┴───────────────────────────────────────┘
? Select a driver. 21
2022-07-25T16:34:48.142621607+00:00 DEBUG Zigbee Switch driver device thread event handled
2022-07-25T16:34:48.691889482+00:00 TRACE Zigbee Switch Received event with handler zigbee
2022-07-25T16:34:48.697089649+00:00 INFO Zigbee Switch <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -72, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x65, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T16:34:48.710578941+00:00 TRACE Zigbee Switch Found ZigbeeMessageDispatcher handler in zigbee_switch
2022-07-25T16:34:48.713606232+00:00 INFO Zigbee Switch Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T16:34:48.717511732+00:00 INFO Zigbee Switch <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-07-25T16:34:48.727634649+00:00 DEBUG Zigbee Switch SONOFF Switch device thread event handled
2022-07-25T16:34:51.740331066+00:00 TRACE Zigbee Switch Received event with handler zigbee
2022-07-25T16:34:51.747761149+00:00 INFO Zigbee Switch <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDD27, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -75, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x66, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >
2022-07-25T16:34:51.760094441+00:00 TRACE Zigbee Switch Found ZigbeeMessageDispatcher handler in zigbee_switch
2022-07-25T16:34:51.763167774+00:00 INFO Zigbee Switch Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-07-25T16:34:51.767124941+00:00 INFO Zigbee Switch <ZigbeeDevice: 63da800a-1c98-43a7-8e3a-122180c5fa5d [0xDD27] (SONOFF Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-07-25T16:34:51.777168524+00:00 DEBUG Zigbee Switch SONOFF Switch device thread event handled
listening for logs… do

I have switches attached to both of my ZBMinis and the app updates almost instantly when the switches are manually operated.

I am using ZigBee Switch MC as my driver.

The ZBMini did not work right with the stock ZigBee Switch driver for me.

mine have been used on ewelink so perhapse a firmware update .

My models numbers are 01MINIZB. I don’t know the firmware version.

┌───────────────────┬──────────────────────────────────────┐
│ Name │ single-switch │
│ Id │ e2a6d58e-9c00-4d44-89c2-a2f16ca1705f │
│ Label │ SONOFF Switch │
│ Manufacturer Code │ SONOFF │
│ Location Id │ 99c131a4-42fa-4c93-bade-a013f5c02732 │
│ Room Id │ │
│ Device Type Id │ │
│ main component │ switch │
│ │ legendabsolute60149.randomOnOff2 │
│ │ legendabsolute60149.randomNextStep2 │
│ │ powerMeter │
│ │ energyMeter │
│ │ legendabsolute60149.energyReset1 │
│ │ legendabsolute60149.getGroups │
│ │ legendabsolute60149.signalMetrics │
│ │ legendabsolute60149.driverVersion1 │
│ │ refresh │
│ │ firmwareUpdate │
│ Child Devices │ │
│ Profile Id │ 4c047ab6-084f-3161-857e-0550a4e1820b │
│ Installed App Id │ │
│ External App Id │ │
│ App Profile Id │ │
└───────────────────┴──────────────────────────────────────┘

@montyfert

As I was telling you, the status in the app is not updated because the on and off events are not emitted when the message with value 1 or 0 is received, which is your case.

If it works fine for you with the stock zigbee switch, you can use that one.

I can’t change anything at the moment.
When I get access to the cli I’ll try to make it work with your device as well without messing up the ones that work fine. It will be in August

will do thanks

Same problem here. How can i fix it? Can i disable the automatic edge driver? Please help me. I have a old zbmini installed with the normal drivers with IDE and it works fine. But i can not add a now one. The edge driver install automatic. Cant do anything about it. .
Thanks a lot.

Hi @Denz_Modz

If it is installed automatically, does it mean that it is installed with the smartthings driver stock zigbee Switch?

I dont know. I just want to add the sonoff zbmini and it comes as a placeholder. Is there a way i can change that so its like before? So i can edit it in the IDE?

The edge driver cannot be edited in IDE

You could try this:
In the App open the device and enter the menu three points, top right and click on driver
It will show you the name of the edge driver used by the switch

  • If it is Zigbee Switch, I would have to give it a smartthings solution since the problem is in its stock driver

  • If you want to use the DTH again, the only thing I can think of is this:

    • Create your custom DTH zigbee Switch:
      • Enter IDE and click on MY Device Handlers
      • Click on + Create New Device Handler
      • Click on From Example and in the list look for the DTH Zigbee Switch
      • In the code look for: definition (name: “ZigBee Switch”,
      • In name add -1 to show ZigBee Switch-1"
      • Click on Create: It will generate a DTH with that name
      • Click on Publish and Publish for me
  • Now uninstall the switch with the app

  • Enter in app HUB and open the Driver menu, top right

  • Find the Zigbee Switch driver and remove it

  • Add the device with search nearby and see if you are lucky and it pairs with this DTH

1 Like

Hi,

I did it, but always get back the edge driver automatically.
Is there any way to disable permanently?

Hi

It seems I have found the solution.
I just added this new fingerprint to the SONOFF section in DTH driver:

    fingerprint profileId: "0104", inClusters: "0000, 0003, 0004, 0005, 0006, FC57", outClusters:"0019", manufacturer:"SONOFF", model:"01MINIZB", deviceJoinName: "SONOFF 01MINIZBv2"

After that there is no more automatically installed edge driver. :slight_smile:

BR
peterdif

just be aware that DTHs will be phased out by Oct. 15th