I recently Tasmotized my Sonoff Zigbee Bridge after struggling with some Issues I finally got it up-and-running.
I noticed that after Tasmotizing the Bridge the Blue LED indicators on the Bridge doesn’t lit anymore.
If I power-up the Bridge then the green led blinks a few times, but the Blue one doesn’t lit.
Could it be that the led is disabled? if that’s the case can it be enable again becaue now you cannot see if the Bridge is powered.
I searched for a command that maybe could e used at the Console of the Tasmota Bridge but unfortunately I can’t find it.
No lights on my unit either after tasmota’ed but is working fine. You can still get to the web UI via browser to reboot and it is ping’able. I to looked for tasmota command for lights but came up empty.
I just updated my SONOFF zigbee bridge uart (6.7.8) and tasmota firmware (10.1) and the LED lights where working but HA was unable to connect. I reapplied the command to enable TCP port 8888, the LEDS light went out but HA could connect again. I like the LEDs on as well, went searching for how to enable them and found this dead thread.
Probably something in the GPIO numbers disabled them. Hopefully someone more knowledgeable can chime in.
Did anyone solved this issue. I am having the same issue. First time tasmotized Sonoff Zigbee Bridge with 10.0 all the LEDs stopped working after zigbee starts.
I found this to be the same on mine as well. I did however discover that if you press the Pairing button on the back of the bridge that the green light comes on and you get an MQTT state change in the console for POWER On. No idea why or what it means though.
Just a follow up to this, I managed to figure out the LED’s however I do not have any Zigbee devices just yet only the bridge so if someone wants to apply the following template and let me know if the bridge still works as expected? This is the template for using it with ZHA not for using Zigbee2Tasmota
Final update. My zigbee remote arrived today. With the changes I made the LEDs both work and the remote paired and performed perfectly. I guess it’s just an error in the template that incorrectly sets the LEDs inverted causing them to go off.