Glad I found this threat, I didn’t even know there was a web interface for the SLZB-06M. After upgraded the firmware to dev26 I got the web interface to work on my Mac.
I’m running ZHA. Only received and installed SLZB-06 yesterday. Woke up this morning and tried to check the web page. No luck.
The web ui issues have been solved. Make sure you upgrade to the latest firmware.
I did. Yesterday. When I installed it. Latest and greatest firmwares. Web interface fails to load correctly. Tried restarting from integration. Still not fixed.
Now it’s completely died. No ping response. No integration communication so mDNS dead. Tried starting on USB-C then plugging in LAN cable.
Can this thing be that bad after all the great reviews?
If anyone can provide any assistance to my dilemma I would be incredibly grateful.
stop ZHA, remove from PoE, then reconnect PoE, then try accessing via the IP (not hostname), if you can access webui, make sure your on the latest Core Firmware (2.7.1), then make sure your running the latest Zigbee firmware, then restart ZHA (maybe consider moving to Zigbee2MQTT).
Still no joy. Contacting the manufacturer for help. Thanks for the suggestions. May have a dud on my hands. No mDNS, can’t ping, not picking up an ip address from my DNS server.
Reflashed with V2.3.6. Logs read as below.
[00:00:00] setup | Starting firmware: v2.3.6
E (1121) esp_littlefs: ./components/esp_littlefs/src/littlefs/lfs.c:1367:error: Corrupted dir pair at {0x0, 0x1}
E (1122) esp_littlefs: mount failed, (-84)
E (1125) esp_littlefs: Failed to initialize LittleFS
[00:00:01] ConfigHelper | LittleFS mounted
[00:00:01] ConfigHelper | load config
[00:00:01] ConfigHelper | config open: InvalidInput
[00:00:01] ConfigHelper | config open err
[00:00:01] setup | Creating a new config
[00:00:01] ConfigHelper | write config
[00:00:01] ConfigHelper | config saved
ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13232
load:0x40080400,len:3028
entry 0x400805e4
Is that normal to have "E (1121) esp_littlefs: ./components/esp_littlefs/src/littlefs/lfs.c:1367:error: Corrupted dir pair at {0x0, 0x1}
" in the logs?
The recent chatter on this thread got me to take a look at the new 2.7.1 core firmware, which I updated to yesterday. This morning I woke up to Zigbee remote buttons (the Hue dimmer switch ones) and motion sensors not being responsive.
Zigbee2MQTT’s web interface, along with the SLZB’s web interface were all working just fine, and Uptime Kuma didn’t show any downtime for either web interfaces. HA displayed consistent temperature data from the temp sensors, however flipping Zigbee lights on and off were extremely sluggish or unresponsive.
In my blurry eyed state I didn’t have the spoons to debug any further. So I restarted Zigbee on the SLZB-06 and Zigbee2MQTT. Everything started working nominally again.
I hit the issue again. Zigbee2MQTT started to spit this out anytime I tried to switch on a light…
error 2025-01-24 17:34:11z2m: Publish 'set' 'brightness' to 'Sunroom 1' failed: 'Error: ZCL command 0x00178801042ac835/11 genLevelCtrl.moveToLevelWithOnOff({"level":232,"transtime":10}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: AF - dataRequest - {"dstaddr":15422,"destendpoint":11,"srcendpoint":1,"clusterid":8,"transid":156,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[1,118,4,232,10,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))'
error 2025-01-24 17:34:11z2m: Publish 'set' 'color_temp' to 'Sunroom 1' failed: 'Error: ZCL command 0x00178801042ac835/11 lightingColorCtrl.moveToColorTemp({"colortemp":500,"transtime":10}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: AF - dataRequest - {"dstaddr":15422,"destendpoint":11,"srcendpoint":1,"clusterid":768,"transid":157,"options":0,"radius":30,"len":7,"data":{"type":"Buffer","data":[1,119,10,244,1,10,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))'
Again the SLZB-06’s UI was responsive, running 2.7.1. I triggered a reboot of the whole thing from inside the UI and now everything is working again.
I was running 2.5.8 previous to this update. Sadly I don’t see 2.5.8 available for download and manual flash. I’ve flashed mine to 2.5.6.
Is there a way to get more logging from the SLZB?
Looking forward to a fix. Thanks!
Finally apparent success. Reflashed via the website with 2.7.1 and has been solid. Hope this doesn’t jinx it but thought I would post a follow up.
2 Likes