Problem with sonoff usb zb-micro plugs

🛎️ Get Help
1

Hi everyone.

I purchased a few of the sonoff usb plug model zbmicro to control when my cameras charge (like while the sun is shining) instead of charging all the time. The cameras I am charging with this setup only needs 3-4 hours of sun a day to charge to 100%. They are solar cameras buuuuut, I am not using the small solar panel that came with it.

So, my 18v 35w solar panel feeds my 12v 20a solar controller (it provides power for mesh router and usb plug zigbee repeater), 10a bms with 8ah lithium battery, usb power outlet (sonoff with built in repeater), a wifi mesh router, 2 cameras (one pointed fixed and another ptz facing the other way, a self contained motion solar light mounted to the pole.

All this is mounted in a outdoor box originally made for a solar water pump. The box had 8ah lithium battery with a 10a bms, 3 leds, a switch, 2 cord grips, and a controller board. I tried to use the well pump solar controller but the parameters built into it, are not conducive to this particular situation. I programmed my solar controller to 14.6v max cutoff, 11.7 re-power output, and 11.4 cutout voltage. My lithium battery likes this setup so far. I would have used lifepo4 but the battery that came in the box is a lithium-ion battery with bms, so I left it in there.

Front

17339805862784808149099424585266
173398058627848081490994245852661920×2560 323 KB

Back

17339808842427605424649023348278
173398088424276054246490233482783120×4160 565 KB

And inside

1733980976975421787816399111466
17339809769754217878163991114664160×3120 687 KB

I am using the zigbee- sonoff generic relays/outlets driver

  • application: 10
  • driver: v1.09 (7th December 2023)
  • firmwareMT: 1286-0007-00001004
  • inClusters: 0000,0003,0006,FC57,FC11
  • manufacturer: SONOFF
  • model: ZBMicro
  • outClusters: 0003,0019
  • profileId: 0104
  • softwareBuild: 1.0.4

Here is the log

dev:3452024-12-11 10:25:44.423 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 0F0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0F, 00, 00], cluster:0005]

dev:3452024-12-11 10:25:41.223 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 0E0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0E, 00, 00], cluster:0005]

dev:3452024-12-11 10:25:37.963 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 0D0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0D, 00, 00], cluster:0005]

dev:3452024-12-11 10:25:22.494 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 0C0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0C, 00, 00], cluster:0005]

dev:3452024-12-11 10:25:05.756 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 0B0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0B, 00, 00], cluster:0005]

dev:3452024-12-11 10:24:49.077 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 0A0000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0A, 00, 00], cluster:0005]

dev:3452024-12-11 10:24:45.956 PMwarnUSB Power For Rear Camera : New unknown Cluster0005 Detected: [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 090000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[09, 00, 00], cluster:0005]

As you can see, I get a lot of messages from them and they fall off the network often, even with the wifi router turned off or on, the sonoff device does the same.

Thanks for the help..

2

Try this driver - it handles some Sonoff ‘specifics’.

You can also use the HE inbuilt 'Generic Zigbee Switch' driver.

3

Thanks for the quick reply. I will try them both and let you know whick one works best. Lol. I know the one Iam using is not great.

4

You can also try configuring the ZBMicro in 'Power Turbo Mode' :

image

5

Ok, I used the tuya zigbee switch and with the sonoff zbmicro device, and it is working great.

I will keep in mind the other driver for future reference.

Btw, what would power mode do for me or is it something kin to sliced bread? Hehehe

6

Ok, got rid of the warnings in the logs, now i have debug lines.

Logs

  • Live logs
  • Past logs
  • Device stats
  • App stats
  • Location events
  • Hub events
  • Scheduled jobs
  • Running jobs
  • Hub actions

Show events

Resume logClear logClear filters

Level

USB Power For Rear Camera

Temp Power House (Digital

USB Power For P/House camera

Presence Sensor Dining Room

USB Power For Rear Camera

Middle Light Family Room

Hobby Light Family Room

dev:3452024-12-12 02:29:01.143 AMdebugUSB Power For Rear Camera sendZigbeeCommands: sent cmd=[he raw A39D 0 0 0x8005 {00 00 00 00 01 01} {0x0000}]

dev:3452024-12-12 02:29:01.138 AMdebugUSB Power For Rear Camera Received ZDO Active Endpoints Request (0x0005) status Success, data=[73, 00, 00] (Sequence Number:73, data:[73, 00, 00])

dev:3452024-12-12 02:29:01.121 AMdebugUSB Power For Rear Camera parse: descMap = [raw:catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 730000, profileId:0000, clusterId:0005, clusterInt:5, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A39D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[73, 00, 00]] description=catchall: 0000 0005 00 00 0040 00 A39D 00 00 0000 00 00 730000

@kkossev
Any ideas on how to fix this one? Thanks again.

Paul

7

From the debug logs I see that all is OK!

The Sonoff switch periodically sends a 'keep alive' Zigbee message, which the driver acknowledges. This 'heartbeat' schema is a bit unusual and Sonoff-specific, but it is how they have understood and implemented the Zigbee specs.

You don't need this detailed debug logging anymore, so simply turn the debug logging preference off. If not turned off manually, it will switch off automatically after 24 hours.

8

You may also want to upgrade the firmware to 1.0.5. Firmware 1.0.4 is quite spammy, and 1.0.5 fixes that.

9

Thanks everyone. I will give it a try for a couple days and I will let you know how it works out.

10

@JDC

How do you do that? I have two on 1.0.4 and one on 1.0.5.

I do not see a button to upgrade the device on the device page.

Thanks.

11

I had success with the update when I changed the driver to Device, then updated the firmware, and finally changed the driver back.

12

Thanks, i will try that.

1 Like