Hi,
I just have an IKEA Bulb explode a few days ago. I took it apart and found a capacitor burned in the mainboard. I decided to make use of the ZigBee module from the bulb so I de-soldered it from the mainboard it appear to be Trådfri ICC-A-1 Module
The following is what I have done so far
solder wires to the module on the pads swdiotms, swclktck, VDD, GND
Connect the wire to a jlink clone pcb I bought cheap from aliexpress
Solder wires to the module PB14, PB15, PA0 then connect it to a ttl serial to usb module
connect to the module from putty with 115200,n,8,1 it was connected after I short PA0 to GND then I presented wit boot loader screen. I then upload gbl file NCP_USW_115k2_F256_678_PB14-PB15-PA0.gbl via xmodem
at this poit everything look ok but I can not connect it via bellows
The goal is to build a new zigbee coordinator or gateway with the module and firmware available to the module. I just try it in my test instance of home assistant with ZHA integration and I manage to have it working in ZHA now. btw. I’m not really sure why I can not get information of the coordinator using bellows and also (I using docker to run home assistant) mapping usb serial /dev/ttyUSB0 to /dev/ttyUSB0 did not work in home assistant docker remap it to /dev/ttyUSB0:/dev/ttyACM0 working without knowing why.
Regardless, suggest also start thread on the project here → https://github.com/zigpy/zigpy/discussions as zigpy/bellows devs, tube0013 and MattWestb who all have experience with this reads threads there.
You might specifically also want to check out and read through these existing threads/discussions there:
OK, this is all interesting stuff, but to what extend are we sure this new bridge is compatible with the Sonoff Zigbee sensors and (mains powered) Zigbee switches?
I have an order in and plan to replace my ZBBridge with it. I dont have a ton of Zigbee devices so it wont be a hard migration.
ZBBridge has been working fine now for over a year, but thinking I want to go back to a stick connected to my NUC vs a seperate box sitting on wifi.
Yah, I also do not like a Zigbee gateway depending on a wifi connection to your home LAN.
I currently use the Sonoff ZBBridge now for a year or so and face little issues. Weird behaviors are rare, also bcs of following reasons:
My wifi router is pretty good and only about 4-5 meters away from the Sonoff Zigbee Bridge.
I have a number of Zigbee Mini Switches of Sonoff which also act as Zigbee repeaters
I standardised almost completely on Sonoff devices/sensors, and even modified a few if a particular sensor function doesn’t exist in the standard product line.
This really helps: do not mix too many different makes: the less the better (although they all claim they are Zigbee 3.0 compatible).
For instance, I have an old hard-wired alarm system in my house with door and window proximity switches fully integrated in the wood work. This is now hard-wired to a number of Sonoff Zigbee door sensors.
Practically all Sonoff Zigbee sensors in my house do not run on battery power anymore. Those I modified too and are hardwired powered with 3V DC from a power adapter plugged in mains.
I even have Sonoff Zigbee motion sensors at various places in the garden. Also there a 3V DC line is powering these sensors hard-wired.
The same “SM-011 V1.0” Zigbee radio modules by CoolKit Technologies is also used inside some Zigbee gateways/hubs like this popular ITead Sonoff ZBBridge and ZB-GW03 eWeLink Ethernet Zigbee Gateway sold by EACHEN and SmartWise, so could perhaps be that the same Zigbee Router firmware could maybe also be used on the SM-011 Zigbee module in all or some of those products as well?
FYI, xsp1989 has uploaded a signed Zigbee Router firmware for ITead’s Sonoff ZBBridge which could possibly make it a Tasmota/ESPHome connected Zigbee Router (instead of as a Zigbee Coordinator):
PS: Have not tried this myself as I got rid of my ITead Sonoff ZBBridge because being WiFi-based it did not work any good as a remote Zigbee Coordinator, but might reconsider buying one if it worked as a Zigbee Router device that can be paired/joined and restarted/reset remotely via Tasmota and/or ESPHome. So that Tasmota/ESPHome is basically only used to initiate virtual join/pair button and restart/reset the device similar to a remote power-cycle it hangs.
