WTH - ZHA (ZigBee) better progress like (BT & ZWave integrations)

Would be possible to finally make some progress on ZHA integration (when I can see later progress on BT and Z-Wave ) it is sad to see super stable and working ZHA integration not to be also so well maintained, more features could be ported from Z2MQTT (OTA repository, better device support, better device to ha device conversion) i think user base of ZHA is way to big to be soo left behind, not all users me my self really like integrating MQTT servers and just prefer amazing way how to native integration works :slight_smile:

What you think ?

I think decoupling using mqtt is the best possible solution. besides many other pros, it gives to devs stable API they can rely on, and in result quicker development and more reliable final solution.

or in other words: development of core integrations is usually slower and more dependent on core development (may introduce unexpected issues)

I cannot understand you guys why you refusing mqtt so much. believe me it’s more proper solution not only because of potential income, but it’s better pattern in building complex systems architectural-wise

I agree that would be really nice, firmware updates should be easy to do for everyone. With Z2MQTT i think it’s not as easy to setup for new users, they sometimes just want to add their devices and not setup a MQTT broker as well. Even more new users are guided to ZHA with the new integration brand selection.

2 Likes

For me the few of problem are foloving:

  1. Slower transmit cycles compared to (CoAP). using more than 250 devices.
  2. Resource discovery. MQTT operates on a flexible topic subscription system
  3. Lack of security.

But need to say I admire Z2M developer for what they achieve :slight_smile:
All technologies have this advantages and disadvantages :slight_smile:

I can’t use ZHA because I run HA as a virtual machine (usb passthrough was unreliable) so I have to use deconz. Wish zigbee worked like jszware2mqtt with a separate gateway

of course there are separate zigbee gateways. Including those which provides ethernet communication to the server. Not sure ZHA supports any of them. Afaik Z2M does.

True, there is an objective delay. Definitively you won’t notice that .

Yes it does i think one with tasmota FW

I definitely noticed the delay with up to 260 devices on MQTT once :smiley: I know this is the ed case bud for example COAP is way better at least from my point of view #noHate

I would be willing to use zigbee2mqtt if it supported my zigbee stick (HUSZBZ-1).

It would be even better if it had the option to use webhooks like zwavejs2mqtt does.

it’s not a show-stopper tho since I’m comfortable with MQTT. But it’s one less moving part to fail.

I’m with HA for 3 years. I don’t remember mqtt failed once.
In fact I registered 2 issues: broken mqtt integration (but it did not impact separate mqtt servers) and expiration logic being broken by ‘reload manually configured mqtt entities’ features.
So both was bugs in HA, not mqtt. The second one did not impact Z2M

I’m not aware about Z2M issues which break my devices work.
Worth to mention that no HA release breaks that (unless devs break/change discovery part of HA)

Tell me ZHA or any other integration is more reliable :wink:

1 Like