For now only buttons and motion sensors. All other things are using WiFi.
I hadn’t found a button with Wi-Fi that is fast and has long running batteries. Sonoff Zigbee Dongle is quite cheap so this is a good alternative.
Most mains powered devices should act a router. Smart plugs fill the role here.
I can’t speak personally about the Tradfri repeater, but I’ve seen reports it has a stronger signal than the Tradfri smart plug, but they both work as a router.
Aqara end devices reportedly seem the most problematic about not liking certain routers, but that seems to be more an issue with the Aqara devices than the with routers. Aqara seems happy with the Tradfri line by all reports.
If you’re going with Sonoff for sensors, I haven’t noticed any negative comments with regard to Sonoff S31 Lite as a router.
Yes, got three IKEA Tradfri Signal Repeater E1746 acting as act core of my Zigbee “backbone network”.
I highly recommend them. Personally, I have a two-story house with a basement and an attic so have hidden one each in the middle of the house on each floor that does not contain the Zigbee Coordinator.
+1 but if you have a larger house with radio killing building obstructions/materials and do not also have other devices that act as Zigbee routers, such as Zigbee plugs, then consider dedicated router devices.
IKEA Tradfri Signal Repeater E1746 works great as Zigbee Router, however, the IKEA Tradfri Wireless Control Outlet (IKEA’s smart Zigbee plug) does not work good as a repeater, but yes it is also a router.
They both work OK as Zigbee routers for battery-operated Aqara, Xiaomi, and Tuya sensors, but as mentioned those an infamous for being incompatible or losing connection with most Zigbee routers.
I instead recommend ITead’s Sonoff Zigbee sensors even though their enclosure looks is not as good:
The general recommendation is actually not to use Zigbee lightbulbs as Zigbee routers because they are often installed within an existing light/lamp fixture with a manual switch (wall switch or cord switch).
It is therefore common that some human comes along and simply flick that switch and it loses power.
Zigbee router devices are meant to be permanently powered devices that are always on.
For this reason, some smart manufacturers of Zigbee lightbulbs have chosen to configure their firmware as an end-device instead of a router in order to avoid bad experiences to prevent the wrong usage.
PS: Personally I only use Zigbee lightbulbs in my window-lamps/window-light fixtures and for those, I made sure that they are always permanently powered by physically removing their cord-switches. As for my ceiling lights/lamps I only use relay or dimmer modules connected controlled via existing wall switch.
This adds automatic USB auto-discovery in ZHA if USB dongle has unique custom product description, but this only applies to newer batches of shipped dongles as initial batches is missing an ID in CP2102.
That is, there is an issue with the dongle reporting a unique description, so if you got shipped an early version of the dongle then the fix should be to write the new custom description of its CP210x firmware for the USB-to-Serial Bridge chip, (and not just a simple firmware upgrade of dongle’s CC2652P chip)
If your dongle does not have this unique description then it will be discovered as dongle for Z-Wave JS.
ITead has posted a script/program that should let users themselves update the product description on already shipped dongles to supposedly match the description already written to latest batch of dongles:
I had the Z-wave issue and the “unknown manufacturer” issue with the Sonoff Zigbee 3.00 also, BUT:
I today have (re-)installed HA with HA OS 7.2 with HA 2022.2.0 and afterwards with HA 2022.2.1.
HA now sees it directly as a Zigbee and after “Configure” I get a message:
CC1352/CC2652 Z-stack 3.30+ (build 20211217) (Texas Instruments) .
NO more Z-wave or “unknown manufacturer” issue, seems resolved.
The Sonoff now works fine under ZHA (can pair all my devices and they work), same as with the manual install before (and ignore z-wave).
The Sonoff does NOT work under Zigbee2MQTT, It installs fine (with change config. Z2M to /dev/ttyUSB0), but cannot pair any device (was also the case with previous versions HA OS, HA and firmware for the Sonoff. No errors/warning in the logs for Z2M. I run on a old X86/64 N3150 motherboard 8GB and an SDD.
Strange that the Dongle works fine under ZHA but cannot pair any device under Zigbee2MQTT on HA.
(I did a total new HA OS/HA install on same hardware, with flash of the Zigbee dongle and then only install for Z2M, when that did not work I removed of all Z2M stuff and installed ZHA without problems and with a working/pairing etc ZHA!)
Any suggestions.
I got my dongle today.
When I opened it, the PCB reads v1.3, with a date in July 2021, so definitely one of those old batch.
Did the firmware update to CC1352P2_CC2652P_launchpad_coordinator_20211217, went fine. I did have to update the cp210x driver via windows update before I could proceed with the TI Programmer tool.
I ran the name change tool also, using my Win10 laptop. It went fine. The name is now usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-xxxx-port0, instead of Silicon Lab something.
Update to the latest Z-Stack firmware and make sure to use a long USB extension cable to get it away from any sources of electromagnetic fields it like most Zigbee adapters are susceptible to interference.
… so I did that, the command line window popped with 3 lines. It was instant and I saw the second line saying gpfn28 config success.
Plug the dongle back to my HAOS, and I got this:
Note that is only the parts regarding the "Product Description String” that applies in that tutorial as only that will write new product description to USB chip (and not the part about flashing Z-Stack firmware).
"As the “Product Description String” of the dongle plus’ CP2102N serial chip has been customed to a unique identifier “Sonoff Zigbee 3.0 USB Dongle Plus”, which has been also added to Home Assistant’s whitelist of auto-discovered devices, the configuration of the dongle in Hass can be very simple. Just plug the dongle into your computer, it will be automatically discovered, click “CONFIGURE” to complete the configuration automatically, and then add sub-devices to use.
If your dongle’s descriptor hasn’t been customed, you can use the tool linked below to change it to “Sonoff Zigbee 3.0 USB Dongle Plus”.
If your dongle still can’t be auto-discovered, it may be because your version of Hass hasn’t integrated this feature yet, you can follow the normal configuration steps below."
I can however still not get that to work on my Windows 10 computer with the latest Silabs CP210x drives from https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers (including rebooting Windows after and checking that the USB dongle is discovered as a COM port).
I first tried to run the included ManufacturingTool.exe binary executable after inserting the dongle into a USB port and seeing it discovered, then also tried installing Python for Windows and running the .py Python script provided without any luck with it writing the new product description to the CP2102 chip.
Might be a stupid question here, but do you guys use a separate PC to flash the dongle?
I have HA installed on a Ubuntu OS natively, was wondering if I can just flash it while HA is running ?
I know I should shutdown HA to be safe but cant seem to find the shutdown option, just restart.
Yes, I run Home Assistant Operating System on Home Assistant Blue, (could disable ZHA but I usually shutdown the whole host), and update both Zigbee and Z-Wave dongles on a Windows 10 computer.
Yes you can flash serial adapters such as a Zigbee coordiantor while Linux while Hone Assistant is running but you first need to stop the specific application/service/deamon (like the ZHA integration or Zigbee2MQTT) connected to the serial device because serial devices can only have one connection.
For what it’s worth, I did the above (on Fedora Linux) using cc2538-bsl and the instructions at Supported Adapters | Zigbee2MQTT and it worked fine. I had a bit of a panic as it didn’t come back up and work immediately — not sure exactly why, but after some reboots and restarts and poking (but with no real changes) it suddenly showed up as detected in HA and then everything worked. But other than that — which I think may have just been me not knowing what to expect — it was easy and painless.