New Zigbee coordinator on the market

[pipiche]

for your information a new product https://3reality.com/product/3-0-usbc-dongle/ is currently in beta on the Z4D rc 7.1.23

[waltervl]

Thanks, anything special with this device or just the same specs and functionality of other common zigbee coordinators?

[gizmocuz]

It supports Zigbee 3.0 and Zigbee2MQTT ... making it already working with Domoticz

[Thorgal789]

It supports Zigbee 3.0 and Zigbee2MQTT ... making it already working with Domoticz

But not yet if you want to avoid the MQTT solution.

[jannl]

Why would you avoid MQTT (or some other message queue)?

[Thorgal789]

Me ?
For me it's just because everything that is done with MQTT can be done without with some work.
For my use I have no interest in using it (I have only 1 home automation application, so all requests can be direct, no need messages queues, and there is so much natives protocoles already supported by Domoticz), except having one more layer, so I prefer solutions that don't use it.

And I know how to code, so prefer code my own esp32 firmware to connect my mitsubishi air conditionner with native protocol to domoticz for exemple, than using existing project using this useless layer just because "it's easier".

Using MQTT is something easier for devs, because they don't need to work on the whole project, Domoticz devs just have to manage MQTT requests, and Z2M devs just create standard requests (In fact this is wrong, HA is so important now, and some requests are now "HA specific")
But the result is a a result more "generic", the Z4D integration is more devices specific.

[waltervl]

It supports Zigbee 3.0 and Zigbee2MQTT ... making it already working with Domoticz

A little bit non constructive comment here @Gizmocuz...
There are lots of happy python script managed zigbee users with Domoticz. Zigbee2mqtt is not the only and best solution....

[gizmocuz]

Well I think it is the most easiest AND best solution... It is a very good maintained project. Sure there are many roads to Rome, but taking the plane from Amsterdam is much quicker and better for your feet.
For Domoticz, why would you put so much work in a separate project that is not needed and will always be steps behind?
And zigbee2mqtt does not only work with Domoticz
And it runs under docker (compose), which means you can update Zigbee2MQTT separate from Domoticz, you can even spawn multiple instances

Imagine that all this python development time was put into enhancing Zigbee2MQTT (if needed), or Domoticz?

so, for me, definitely not a non constructive comment. And you should have seen me post about this many many times.

And yes, I had the exact same issue with OpenZWave, hundreds of hours and sweat went into supporting this, also did some additions to the library itself.
Now there is ZWaveJS-UI (ZWave was a great platform 10 years ago)

[waltervl]

Ah common Gozmocuz, there is a Domoticz Python framework so why push every time to MQTT AD for zigbee? The zigbee4domoticz plugin is already for a long time available, way before MQTT AD in Domoticz and works just fine. Also the Deconz Python plugin works just fine. And these authors, all programming enthousiasts, also made a lot of effort getting the work done.

It is good that you made MQTT AD available for zigbee2mqtt and other AD projects around there. And yes, for most the zigbee2mqtt is the easy way to go.

But please respect the plugin authors for doing their work.... It is their decision to keep maintaining this, so please stay neutral on this.

[lost]

Also agree with solutions that avoids labyrinthine stuff when useless: MQTT, one docker recommended per external useless SW pile to help cope with versions/dependencies nightmare for systems with everything running on same localhost is no good design nor help finding where something could go wrong considering the various layers and projects involved:

If this is just going in the same way HA goes, there would be no more specifics to Domoticz we are IMO many to appreciate: Historically a clean integration and clever design able to run on light hardware. All the opposite of HA.

For HA, better use a small server configuration now if you have to handle several protocols. My PI3 hosting Domoticz is now close to 9 years 24/7 usage, still smooth on CPU side rarely exceeding 8/10%, 1GB DDR will probably be the 1st limit I'll reach. In 10 years, HA will probably need a refurb Proliant server and it's 2x800W power supplies server to reliably run...

[jvdz]

But please respect the plugin authors for doing their work.... It is their decision to keep maintaining this, so please stay neutral on this.

To me, this isn't very respectful, and it's also a huge misrepresentation of what was said.
Everyone's allowed to have their own opinion, and there's no disrespect, just his opinion.
...but hey, that's just my two cents... and guess also a bit offtopic.

[waltervl]

It is disrespectful when a plugin owner states that a coördinator is being implemented for his plugin and someone else promotes to use another solution. Problem is also that this is not the first time this happens....
So hopefully Pipiche wont get too upset by these kind of remarks and in the end stops maintaining its Z4D plugin.

[waltervl]

Thanks, anything special with this device or just the same specs and functionality of other common zigbee coordinators?

@pipiche?

[jvdz]

It is disrespectful when a plugin owner states that a coördinator is being implemented for his plugin and someone else promotes to use another solution.

Let's agree to disagree and move on.

[gizmocuz]

NO, everyone has a right for his/hers opinion, and my opinion you can read above.

So Walter, next time read better and allow others to have opinions!

[waltervl]

I can read very well...

[gizmocuz]

Good! Than you would have seen that I wrote this as "My" opinion ...
And instead of flaming on the forum, you could also have send me a message on slack first?

[Thorgal789]

NO, everyone has a right for his/hers opinion, and my opinion you can read above.

Yeah, but you are the project owner, not the same impact.

On my side I m seing the project owner saying :
- Don't loose time to code something that can be used on this application.
- Better to use other solution, external one if possible, they are easier, try HA for exemple.
- Domoticz is something too lighter, better to use other server to manage other protocol, than using native one already supported, with dockers, because it's better.
- Why have you choosed Domoticz ? stupid reason, there is better elsewhere.

Sure there are many roads to Rome, but taking the plane from Amsterdam is much quicker and better for your feet

And if I leave at 10km from Rome ? Remember we have not all the same needs.

Imagine that all this python development time was put into enhancing Zigbee2MQTT (if needed), or Domoticz?

Yes, I can understand your position, and you are right, but there is still a small community that knows other home automation applications and has reasons to stay on Domoticz, for me it's the lightness, the ease of adding functions, and the ease to custom it (no, dockers are not easier).

I think you are able to understand if we are liking Domoticz it's exactly because it have some things specific to it, not present on other project. We are loving specific stuff, so pls never say us it's better to use the "most used" solution.

[gizmocuz]

Well, it is not that there are no other ways to Rome, but as said, I think there is a good and fast way to do it.
And not to mention all the questions we get on this forum for those other two Zigbee gateway solutions.

Sometimes you have to move on... There are better solutions, also for Home Automation.

Some like HASS, some like Homeseer, some like FHEM and some like Domoticz or other platforms

The reason I like Domoticz is because it's flexibility and has awesome scripting support, things I miss in other platforms

So yes, in case of Zigbee, I do think it is wise to use Zigbee2MQTT.
It is very well supported, has a large community, and there is absolutely no reason not to use it.

Getting the other solutions to work with Python also involves installing additional library dependencies (and of course we create a "venv" environment for this so your system does not get polluted.....),
installing everything via Docker Compose is very easy, very good to maintain, easy to make backups and to do version management.

And the good part, both these projects are used by other home automation software, meaning, you can use the best of both worlds and you do not have to start from scratch again if you ever decide to switch or use multiple solutions.

So I do recommend to use Zigbee2MQTT but everyone if free to use whatever they want.

[waltervl]

So I do recommend to use Zigbee2MQTT but everyone if free to use whatever they want.

And then it would be nice you stop pushing this particular opinion in Z4D topics. The other zigbee plugin authors also don't push their plugins in Z2M topics......

They both can live perfectly next to each other without any rivalry.