r/ZigBee

Hello all,

I have several Innr bulbs I expected to act as Zigbee routers, but I can't confirm they're actually forwarding traffic. They show up as "Router" in the device list, but Z2M's network map doesn't show any other devices hopping through them.

Anyone else run into this? Are Innr bulbs known to be unreliable routers, or is there a better way to verify actual routing (beyond just trusting the network map)?

Thanks!

Basically the title the thing is indoors kept cool and it just wont boot, the dang orange light is on and windows detects it with no driver, it is getting really hot over usb. Is this normal, I was having an awesome time with this.

Hi all,

Pretty new to home assistant etc. so please bear with me.

I bought Sonoff ZBM5 switches to replace all of my light switches (20+) and I have home assistant green with the ZBT-2 to control them. My problem is getting them working in home assistant. I'm using the ZHA integration and I have neutral wires at the switches but when I go to add them it's very intermittent. Most of the time it just doesn't find them. At first I thought it was a range problem so I used the closest switch which is in the same room and about 2 meters from the ZBT-2 (I also have the ZBT-2 on an extension lead so it's 1.5m from any routers etc.). That does seem to help as it does sometimes find them but If I do manage to get home assistant to find the switch it works maybe once then becomes "unavailable".

I then decided to try some Sonoff smart plugs and the first one I plugged in showed up on home assistant instantly without me even searching so I thought it must be the switches. However, when I tried the second smart plug I had the same issue with the switches and couldn't find it in home assistant.

I got very frustrated and bought a Sonoff ZigBee hub to see if that worked and it did! I know have 5 switches working perfectly with different automations etc. through the ewelink app.

Am I doing something wrong in home assistant, should I try 2MQTT instead of ZHA?

Thanks for your help

My current problem: I bought a set of 4 Sengled color changing lights for my college apratment off facebook marketplace ( was blinded by the 10$ price, did not check anything else). however, come to find out Sengled doesnt exisit anymore and these cloud based lightbulbs are basically just normal lightbulbs.

After some digging i find that its possible to jailbreak the light bulbs and control them without the app. ok, so i tried doing that but was hit with the fact that these arent wifi light bulbs, but zigbee ones.

what the fuck is zigbee bro.

all i want is to be able to control the light colors and brightness via my phone ( or laptop ). i dont need to integrate it into any kind of home assisstant or anything fancy. after some digging, i found it was possible to use python and a Zigbee dongle to do that. i need the zigbee dongle to read and transmit the proper zigbee frequencies i think ( and a flipper zero cant do that due to their lower frequency range)

what exactly does a dongle do? am i right to think that this is a possible fix? what are good dongle recommendations?

Hello guys. It’s possible to repeat a zinger signal using an Ethernet device such as the dongle max or the SLZB but without creating a new MQTT HA line? I have areas where zingbee arrives very low and switch looses connection multiple times, but I do have Ethernet. Is I possible?

Setup:

**•**	Sonoff Mini Duo (2-channel Zigbee relay, **with neutral wire** version) installed inline behind my wall switch.  
**•**	Device is still in **complete factory state** — not paired with eWeLink, ZHA, Zigbee2MQTT, or anything. I don’t even have internet in the house yet, so no HA/coordinator running.  
**•**	One channel is wired to my bathroom light fixture.  
**•**	Just installed brand new smart bulbs (Zigbee) in that fixture, intending to use them purely as “dumb” on/off bulbs via the physical wall switch for now, until I get my Zigbee network and HA set up later.

Problem:
Flipping the physical wall switch does nothing at all — no light, not even a default warm-white glow, nothing.

What I’m trying to understand:

**1.**	Does a Sonoff Mini Duo need to be commissioned/paired first before the relay will physically pass power through at all, or should it work as a basic pass-through switch straight out of the box in factory state?  
**2.**	In factory state, is the relay possibly defaulting to “off,” or sitting in some kind of idle/unconfigured mode that blocks power entirely?  
**3.**	Since mine has the neutral wire connected, is there anything different about factory behavior compared to the no-neutral version?  
**4.**	Is there a way to manually force it into a simple passthrough on/off state without pairing it to anything yet — or do I basically need to at least do local setup via the eWeLink app before it’ll function as a switch?

Any guidance appreciated — trying to rule out whether this is a relay commissioning issue before I start troubleshooting the bulbs themselves.

Thankyou in advance!!! <3

I currently use the SmartLife android App where i have a cheap Multi modal Zigbee Hub (BT/Zigbee 3.0) and this in turns acts as the hub for my zigbee sockets/switches etc.

Is there any Wifi Switch that has built in zigbee hub that i can use to replace this?

I came across Amazon Eero but i guess that will be stuck with the Amazon ecosystem?

I just wanted to consolidate my current Wifi Switch/Router and the Zigbee Hub i already have . I also have the Philips Hue Bridge Pro which has Zigbee but I'm guessing that is vendor locked with Philips ecosystem and i won't be able to use it as hub within the Smart life app.

I searched online/YouTube and subreddit but I can't seem to find anyone asking this question specifically so hoping this also helps someone else having the same requirement as me.

Hey all

Having major issues with Zigbee network, tried ZHA and Z2M. I'm using:

~75 Zigbee2MQTT devices (61 Aqara, 13 Nous), coordinator is an SMLIGHT SLZB-MR5U over Ethernet (`ember` adapter), HA OS.

My previous coordinator (an SLZB-MR6U) had the same instability — crash-looping, `TABLE_FULL` binding errors, chunks of the mesh going unresponsive. I assumed hardware fault and replaced it. Set the new one up **completely fresh** — no backup restore, every device re-paired from scratch. **Same failure class came back anyway.** Two different physical coordinators, same symptoms — that rules out "just bad hardware" for me.

Radio disconnects/restarts with varying reasons (`RESET_SOFTWARE`, `RESET_POWERON`, `ECONNRESET`). Specific devices repeatedly fail to bind with `Status 'TABLE_FULL'`. Occasional sweeps where nearly every router fails a routing-table query at once. Command delivery intermittently fails for a shifting set of devices.

### What I've tried

Cleared a stale `coordinator_backup.json` (helped once, not permanently); moved off a noisy Zigbee channel after an RF scan (reduced routing failures, didn't stop crashes); power-cycled the coordinator (no lasting help); reflashed firmware dev→stable (no help); power-cycled individual problem devices (fixed their presence reporting, binding issue unclear). Partial wins across the board, nothing's been a full fix.

Every device with a confirmed problem today (11 of them) is Aqara — zero of my 13 Nous devices affected. Worst offenders are three Aqara Presence Sensor FP300 mmWave sensors specifically, which have a reputation for being binding-hungry. Doesn't fully explain it though — the routing-table failures hit some non-Aqara routers too.

I'm weighing up 3 options:

-Move Aqara devices to my Aqara M3 Hub**, keep the SLZB for everything else. Free, but splits the network and I'm unsure how solid the M3 Hub's HA integration is (local vs. cloud).

- Replace Aqara devices with IKEA** (Zigbee/Matter-Thread). Cheap (~£250 all-in), but real time, and a big Thread network is unfamiliar territory.

-Replace Aqara devices with other Zigbee brands.** Similar cost, avoids a second protocol, but keeps one large single-coordinator network — which may not fix anything if this is coordinator/RF-related rather than Aqara-specific.

- Has Aqara flakiness followed anyone across two different coordinators like this? What actually fixed it?

- Anyone running an Aqara M3 Hub with HA who can speak to how local/reliable that integration is?

- Anyone beaten FP300-caused `TABLE_FULL` without replacing the sensor?

Cheers in advance

Hi! I have some Shelly 1 PM (Mini and "normal") that control Zigbee light groups. They are set to detached mode and I used to do the control logic through Home Assistant automations. With FW 2.0.0 and the info from this thread I was able to bind the Shellies directly to the respective light groups and set them to toggle instead of sending sequential "on" and "off" commands. Yay!

Since I once had trouble with Z2M crashing and my significant other (rightfully) freaking out about lights not working, the intention was to increase resilience. Light switches should work whether HA/Z2M is running or not.

This evening, for some reason my coordinator (Smlight SLZB-MR1) stopped working. No problem, I thought. I can try my Zigbee bindings. This is exactly what I created them for.

Well. They kind of worked. Only not in a way that I would consider useful. I think it took them nearly a minute between the switch/button being pressed and the lights toggling.

Is this a possible device (the Shellies, the Paulmann bulbs...?) issue, or is this somehow to be expected? Do devices need time to figure out how to talk to each other when the coordinator is suddenly AWOL? If so, how long should this take?

After rebooting the coordinator, everything worked fine. I then stopped Zigbee2MQTT (but kept the coordinator powered), and the bindings fired as expected. Overall not quite what I expected from bindings.