I recently acquired a Sonoff Dongle-E to try and use as a Zigbee dongle. Updated to Coordinator 8.2, 8.02 or whatever the most recent version is and all I get is Initializing. There are 2 ports that show that, one shows “if01-port0” and the other “if00-port0.” They both vanish if I pull the dongle so I believe they are the dongle ports. RPi 5 4mb running V5.2.1 Openhabian using only Zwave.
dongle-e sitting on Initializing with both if00 and if01 showing up usually means the zigbee binding hasnt actually grabbed a working serial endpoint yet. those two ports are normal for that dual-interface stick.
on openhabian/rpi for me:
- use the ember coordinator thing (dongle-e is silabs), not the old telegesis path
- point it at /dev/serial/by-id/… instead of the if0x labels, baud 115200
- if both stay Initializing, try the other interface, only one is the real console side
- make sure nothing else (z2m / zigpy) has the stick open
- after a firmware flash i usually full unplug power cycle before openhab sees it clean
id start by installing the zigbee binding, add ember coordinator, by-id path, then watch openhab.log while it comes online
These are the ports I see available in Openhab, any suggestions on which to try?
* /dev/ttyUSB1
* /dev/ttyUSB0
* /dev/ttyAMA0
* /dev/ttyAMA10
* /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_012B9F5B-if01-port0
* /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_012B9F5B-if00-port0
* /dev/serial/by-id/usb-0658_0200-if00
* /dev/ttyACM0
for the sonoff stick ignore ttyUSB* and the AMA ones for now. use the by-id Silicon Labs ones. try if01-port0 first as the ember coordinator path, baud 115200. if it stays Initializing, swap to if00-port0. leave the 0658_0200 one alone, thats probably your zwave stick. unplug/replug once after you pick a path so nothing holds the wrong interface.
I seem to always get these responses:
09:33:35.760 INFO
openhab.event.ThingStatusInfoChangedEvent
Thing 'zigbee:coordinator_ember:599643451b' changed from UNINITIALIZED to INITIALIZING
09:33:36.912 INFO
openhab.event.FirmwareStatusInfoEvent
Firmware status of thing zigbee:coordinator_ember:599643451b changed to UNKNOWN.
Followed soon after by all my rules updating which there seems to be no good reason for. Because the RPi is across the house, I’m just rebooting it between tries. Do you think I might really need to also unplug the dongle?
Hi you may consider reflashing back to what is confirmed as supported for OpenHAB. version 6.10.3_V1.0
I recall the binding developer mentioning he had also done a 7 version but the 6.10 works perfectly for the multiple dongles I have attached to various OpenHAB installs of all flavors.
There have been many posts on the foroum with your exact issue and all seem to be whn using the later firmware.
here is the official ITlead repo
At the time of writting (2022-06-30) EmberZNet Zigbee version 6.10.3.0 firmware is recommended for the ZHA integration in Home Assistant (which depends on the open source zigpy and bellows libraries):
- ncp-uart-sw_EZNet6.10.3_V1.0.1.gbl
The same firmware version has also been confirmed to work with OpenHAB Zigbee Binding, Zigbee2MQTT, IoBroker, Zigbee Plugin for Domoticz, and Zigbee Plugin for Jeedom.
Also, oddly for a real Sonoff Itlead dongle I do not see an offering for a version 8.xx you mentioned.
Are you sure you did not get a P or a china knock off?
Well, I installed 6.10.3 with no change. I purchased it from the Sonoff store on Amazon so I assume it’s real, the Sonoff Dongle Flasher claims it’s a Dongle-E. When I go to Sonoff Dongle Flasher - SONOFF Dongle and plug in my dongle it offers me 8.02 so I assumed that was current.
And I keep forgetting to say, thanks so much for offering to help. When I had an earlier version of Openhab on a RPi 3 my previous Zigbee dongle just worked, when I upgraded to 5 and tried it again I got this same problem so I gave up. I want to put a bunch of switches in my new building and I thought I’d try Zigbee again so I picked up what seemed like it should be a good choice and it also won’t work so I’m at kind of a loss.
so, I am assuming you did all the linux stuff to make sure your serial ports are configured correctly?
like is mentioned here.
And after you reflashed the firmware you unplugged the dongle and power cycled the Rpi or at least rebooted it?
I didn’t think I had to do anything with the ports when using Openhabian, certainly my Zwave dongle just worked. When I tell it to use a unavailable port, it just fails really fast and turns red, but with these ports it just sits at initializing forever and when I try to delete it, if sits at deleting forever. I was rebooting the RPi between every different attempt and now I reboot and unplug with no change. I did find that it’s assigning the two CP2105 ports to ttyUSB0 and ttyUSB1 but trying both of them gives me the same result as the CP2105 ports.
I cannot say what you should or should not have to do when using openhabian other then there are options in openhabian as well for changing system settings for use with dongles at least on the Rpi 4 I have and the OS is still a linux build so just a thought. Also there was some notes on the sonoff web site discussing the baud rate 115200 for one version uart and 57600 for the other version and that supposedly is determined based on your serial number run of the dongle.
Ok so I built out a new image on my Rpi4 with 5.2.1 and did the 30 system settings in openhabian-config then 35 serial port then option 2 to move bluetooth (you may not need to on yours but I did it for gp’s) added the binding then took a brand new fresh sonoff dongle E with the 6.10.3.0 firmware straight out of box plugged it in and manually selected ember coordinator under add things. I then selected 115200 baud and when I pulled down serial it populated the port with 2 options /dev/tty/usb0 or the long /dev/serial/by id (btw works with either) then it went to initializing I saved then I toggled the initializing switch and it stuck on that like yours did.
I then rebooted the Rpi and same as you no help. I then unplugged the dongle and then plugged it back in it switched to offline I then marked it disabled then I waited for it to come back as thing disabled then I enabled and it switched to initializing for a second then it came online and works fine. with that being said it does not seem like an OpenHAB 5.2.1 version issue. Or a zigbee binding issue.
as the below picture shows
and this is what I am running it on
Also, I did check and it does look like openhabian does do the linux needed tweaks as it show as openhab already a member of dialout and tty
Hope this helps
Even when I unplug the dongle the ports seem to still be there. Is there a way to remove them so they are not there and reappear when I next plug the dongle in.
I am not sure I understand your question.
still seem to be showing up where? In the binding configuration? or at the OS level?
If the dongle is removed, then when you clear the entry in the binding it should not repopulate with what you had selected previously as the device is no longer present. If you are still seeing the same resource appearing even after restarting the Rpi and no dongle installed, then you have configured the binding to attach to something other than your ZigBee dongle.
Turns out I had something else plugged in that I forgot about, so I unplugged that and started over. I have tried every possible sequence of rebooting the RPi, rebooting Openhab, installing, uninstalling, disabling and enabling the Ember coordinator and flashing the dongle with both 6.10.3 router and coordinator firmware and no matter what I try, I still get “Firmware status of thing zigbee:coordinator_ember:b6bb8fee76 changed to UNKNOWN.”
I’m lost. The only difference I can see between mine and yours is I have a Zwave dongle installed and I have an RPI 5.
I guess I can back it up, install a fresh OpehHABian image and see if I can get the dongle alive if nothing else is there yet.
Your dongle needs to have the coordinator version of the firmware not the router version. You may want to grab a spare flash card pop in a fresh load then get dongle working with that once you have it working then note all the settings then put your previous build in and match the settings disable the binding reboot then when it comes back up enable binding and then plug in dongle and see if settings stick and dongle goes on line..