2.4Ghz band Zigbee, WIFI, BT, Microwave, Cordless Phones Interferences. What Zigbee channel to pick?
Genuinely impressed with Zigbee and HA / Reactor
-
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
-
The migration has started. Pulling Z-wave devices and replacing them with Zigbee. Really successful so far. Much much snappier response. No range issues as each socket I'm adding acts as a router. Gonna have a play later see if I can flash the Tuya cloud plugs I bought to Tasmota....
C
-
So far just keeps getting better. I thought I'd hit a snag yesterday wit the newly installed garage light switch being slow to trigger (IRO 6 seconds) but realised I was using the wrong HASS sensor attribute (durrr) once I sorted that, it's all sorted. Typical response times are sub second.
Some oddities in where I've migrated with some hacky virtual switches which I need to track down. I'd get rid of them but trying to expose HA entities to Alexa seems a bit hit and miss...
C
-
I tried different things and after all I’ve just switched to my own emulated hue bridge, calling reactor HTTP endpoints. I was toying with the idea of sending MQTT commands, but HTTP just works. I did my own bridge because I have 100 switches/scenes/virtual switches mapped to Alexa and ha-bridge has not the ability to define multiple bridges on the same host, so I wrote mine
But ha-bridge should just work. Never tried HASS native hue emulation. I tried matter bridge and unfortunately Alexa will only see 20 devices.
SONOFF Universal Zigbee 3.0 USB Dongle Plus ZBDongle E Gateway with Antenna for Home Assistant, Open HAB etc, Support Data Flow Control : Amazon.co.uk: Computers & Accessories
