[qurren]

> Nowhere did I had even half an hour of disconnection.

Well my garage door opener sensor has been disconnected for two 30 minute gaps today and my plant humidity sensors go offline for 2 weeks at a time.

So yeah, it's not ready for prime time.

> LORA

No, let's not even go there. Tech nerd protocol here that's an awkward middle ground that creates even more problems. Average Joes aren't going to set that crap up.

[Arch-TK]

Are you using a phoscon coordinator? ConBee 2 has a lot of firmware problems in my experience.

There are also some devices which advertise ZigBee compatibility but the manufacturers don't seem to test them against coordinators other than their own (and ConBee 2 seems to have the most problems in this regard).

The protocol is complex, they all are, implementing it correctly isn't a given, but I think the issues people have are more often a factor of how long a protocol has been in use than any fundamental aspect of it.

As soon as cheap hardware manufacturers get on board you get this problem.

Quality hardware works fine with ZigBee. It's by no means perfect technology, if you want that, use copper wires, but it doesn't work as badly as you claim if you are not unlucky with coordinators and devices.

[robocat]

Is your zigbee running at 2.4GHz? Everything interferes with that.

[watermelon0]

Practically all consumer Zigbee devices only support 2.4GHz. You would need to go for ZWave for the sub-GHz range.

Also, it's not like 860-930 MHz (depending on the country) is without interference.