Wow, that's a GREAT - Zigbee

[wojtas810 17]

It works exceptionally well!!!
I also heard from support over the phone today that an update will be coming soon, saying that ZigBee won't freeze, and that you're delivering the promised items from 5 years ago - well done.

Thank you - finally!!!

[awlieser 19]

What has been improved? I just started fiddling with some HA implentation on a Pi to manage Zigbee devices - no longer needed? thanks!

[awlieser 19]

I did play around with HA for a bit. How is it possible that an open source implementation like Home Assistant is able to identify,configure and make use of Zigbee devices (e.g. Moes Presence Detector, Humidity & Temerature Sensors, Tuya devices, etc.) while a „professional“ software like HC3 is unable to make any use of them? Very strange!

[SmartHomeEddy 1,005]

I think a lot more "developers" around HASS to make the Zigbee device work with HASS. 

[tinman 1,070]

On 12/5/2025 at 10:53 AM, SmartHomeEddy said:

I think a lot more "developers" around HASS to make the Zigbee device work with HASS. 

depends how one see it, HASS is using Zigbee2MQTT, which is acutually using zigbee-herdsman/zigbee-herdsman-converters to communicate with zigbee devices.

Fibaro is using as well zigbee-herdsman/zigbee-herdsman-converters, so from the zigbee hardware perspective, and the zigbee driver, there is no difference - modules that can be properly added or properly working with HASS, can be added and could work properly with Fibaro.

 

The only difference is that Fibaro is using own engine, similar to Zigbee2MQTT on HASS, and not Zigbee2MQTT. That engine recieve all the data, and can do all the fun stuff as well - the only difficult thing are class, settings and events mappings (what in zigbee is what as Fibaro device classes, and what can't be added, what should happens when specific data comes in, what shall i send to change params, etc.).

 

To get HC3 zigbee certifed and develop support for more devices one need:

- developers who knows Fibaro insides - now to what you said, i think the majority of HASS contributors (who cares how many are really doing sthg) have no idea about Zigbee nor Zigbee2MQTT, most of what Zigbee2MQTT is doing (460 contributors) is based on properly working zigbee-herdsman (180 contributors). Fibaro could allow the "community" to help out here with Zigbee, but honestly how many ppl here on the forum knows really Fibaro internals? 2?, 3? 4?

- hardware to test

- time

 

Fibaro have skilled developers - they know what they doing and know Fibaro insides. Fibaro have strick rules - even if i'm under NDA they would still not take my work and implement it, as someone has to maintain it later.

 

"hardware to test" is same no issue as for HASS - someone has to click and report what's wrong - due to similarity one can use shortcuts here, re-using Zigbee2MQTT solution for specific devices to get them running.

 

The real issues are therefor:

- time (try to convince your boss to be able to spend more on Zigbee, instead on x, y or z which are actually the money makers for the company)

- business (why should Fibaro spent time to add cheap zigbee radar/motion senor, while they working on own radar/pir z-wave version?)

- devices with ugly to convert endpoints (however this is generally zigbee crap, things like same hardware with 6 product revisions, each behaves different is "standard" due to no certification for 99% of zigbee devices on the market)

- time once again (even if Fibaro is using zigbee-herdsman/zigbee-herdsman-converters, they on 1+ yrs old version from what i see, probably due to lack of time)

 

While i would love to help a bit with some devices, i do not have time as well - and if i would get some spare time, it would be only for devices which my company is using in our project.

Lack of not yet implemented things, or outdated herdsman, makes it not easier, example:

Occupany sensor with radar and pir and few mandatory to set setting to make it properly running, while i can only map occupancy or pir, well maybe 3-4 extra things, but i need more, things like detection distance etc. which should typically mapped to device get/set properties and on Fibaro as device property (which is not yet implemented anyway, one need to use swagger or api calls)

Then i need to set some parameters, which i can't set as only 6 or so setting types are allowed today on Fibaro ... and finally outdated herdsman-converters breaks proper inclusion of that specific device

 

On the other hand i see over 2600 zigbee devices has been already implemented (more or less properly, depending on what is generally possible or usefull on HC3), so it is not that Fibaro is not doing anything, this is already great number, but i agree "we need more".

 

As time is money, and money++ means time++, let try following: how much money could you guys (i mean Forum users) spend to get Fibaro dev team things implemented?

 

 Ehm "i paid 400eur for HC3 so i expect my 8eur device from one-hung-low to be working properly on it!" is not proper answer, because that device is not working properly even on Zigbee certified gateways like smarthings, bosch or ubisys anyways, and these costs as well between 100-400eur.

 

[Sankotronic 2,370]

Hi @tinman,

 

Thank you for this explanation. Recently I buy new HC3 and few Fibaro DW sensors. I also plan to buy some more Fibaro sensors and actuators in near future to replace some very old ones to be ready for transfer from HC2 to HC3.

 

To be honest I like more Z-wave than Zigbee, but that is just me. I get HC3 because my HC2 served my family for years and not because it has Zigbee.

I do not plan to include any Zigbee devices to HC3 in the future anyway.

 

Since 2015 when I start with Fibaro HC2 and Fibaro z-wave devices I still have it all functional. Since then I just replaced 2 Fibaro CO sensors because they expired.

I did replace also some DW sensors and one eye, but replaced ones are still functional and I use them for testing.

 

4 hours ago, tinman said:

(why should Fibaro spent time to add cheap zigbee radar/motion senor, while they working on own radar/pir z-wave version?)

I do hope that Fibaro is really working on their z-wave radar/pir device and I know that I will be first to buy when they became available!

[DJ6971 1]

W dniu 2.12.2025 o 23:44, awlieser napisał:

What has been improved? I just started fiddling with some HA implentation on a Pi to manage Zigbee devices - no longer needed? thanks!

I personally own a Pi with a Zigbee antenna, plus I have Node-RED and zigbee2MQTT. The Fibaro central unit listens to Node-RED, which sends personalized messages via HTTPS.

What's annoying is that it's a pity there's no available Fibaro API. Also, Zigbee is not well supported by Fibaro manufacturers. In my opinion, this is a mistake, a huge mistake.

[Fyase 11]

On 12/9/2025 at 10:24 PM, DJ6971 said:

I personally own a Pi with a Zigbee antenna, plus I have Node-RED and zigbee2MQTT. The Fibaro central unit listens to Node-RED, which sends personalized messages via HTTPS.

What's annoying is that it's a pity there's no available Fibaro API. Also, Zigbee is not well supported by Fibaro manufacturers. In my opinion, this is a mistake, a huge mistake.

 

I'm using this one:

Please login or register to see this link.

a bit modified to works with very latest zigbee2mqtt. If you want I can share you. credits obviously to the developer. I just made some changes to get it working back

 

Please login or register to see this attachment.

 

I have around 30 device connected in zigbee....

Edited December 12, 2025 by Fyase

[minsad79 19]

피아세 @

최신 zigbee2mqtt와 호환되도록 약간 수정되었습니다.

저와 공유해 주세요

감사합니다

 

 

Edited December 14, 2025 by minsad79

[Fyase 11]

On 12/14/2025 at 7:29 AM, minsad79 said:

피아세 @

최신 zigbee2mqtt와 호환되도록 약간 수정되었습니다.

저와 공유해 주세요

감사합니다

 

 

 

As already said I just modified a bit the QuickApp to works back with Zigbee2MQTT from version 2.0.0 and above. All credits to QuickApp developer: 

Please login or register to see this link.

  Fell free to pay him a beer on his account links.

 

I'm now using with mosquitto and around 30 devices integrated on Fibaro.

 

Raffaele

Please login or register to see this attachment.

Edited December 15, 2025 by Fyase

[rwiesel 0]

I  developped similar quickapp and virtual devices for HC2 and HC3 - it works very well - I already integrated door sensors and presence sensors 

Please login or register to see this image.

/monthly_2026_02/image.png.0f84d1035510df32681fc43e5fdb8bdc.png" />

[awlieser 19]

Hi rwiesel, where can this qa be downloaded? Thanks!

[rwiesel 0]

I answered in private

[rwiesel 0]

in HC2 I created a virtual device with 3 labeles and the code needs HA token and our HA ip. I created 3 global variables that this code updates for scenes.   HC3 is more complicated. for some reson it is not storing the value (example LUX) as a value but as a string and it creates a challenge for scenes. I'm working on a work around unles Fibaro will release a version where you can define a global variable as a value or string

 

Please login or register to see this image.

/monthly_2026_02/image.png.402e118d76911d5dce6e7b3c9e9b5a61.png" />

Please login or register to see this attachment.

[awlieser 19]

On 2/5/2026 at 10:00 AM, rwiesel said:

I answered in private

Hi rwiesel, I didn't receive any PM ... thanks! Your attachment seems to be for HC2, but I would need a HC3 version.

Edited February 23 by awlieser