Momos

As far as my understanding of this device goes, parameter 13 is when the device will update it's status to the controller. 0 means it will update it's status only when changed (from Idle to Heating or the other way - the thermostatOperatingState, or from Off to Heat - the thermostatMode). 0 setting for parameter 13 should work fine. And parameter 15 is to be able to use the thermostat for cooling - so when temp goes above setpoint it will turn the relay on, instead of off as default. I think your issue is that the controller - HC3 does not receive the temperature from the thermostat. Try set the group 2 associations to the controller - multichannel. At least all my Ztemp-2 are configured this way and they work. My problem with them is that they drain the batteries in 3 weeks 😅

I would start with this one ! and 100% agree with all the others.

ok cheers

@m.roszak Hi, same issue with MCO MH8 - 4 pipe. But polling / reboot does nothing. Soft reconfig, add/remove still nothing. Time will not sync. MCO version 3.2 Template 883 HC3L version: 5.130.64. Zwave engine 2.0 tried with HC3 and HC2 also. same thing. no time sync. any ideas please ?

Nope. No offest possible in FGT-001

There is also another integration for Fibaro - HA, using MQTT. It is rock solid and you get a lot of goodies into HA, including battery status, power, energy . Maybe it's worth checking it out. https://github.com/alexander-vitishchenko/hc3-to-mqtt

@m.roszak Hi Michal, can you please elaborate on that a little bit ? there is no refference in the manual about the position of the USB port and i was under the impression that it does not matter. Also, are the FGT's with a button also affected by this ?

also check the battery. Do not use other compatible batteries as they have very poor performance. Use the original EVE ones.

http://update.fibaro.com/hcl/4.620/patch.tar.gz

Did you check the voltage on the internal CMOS battery? Also, is the HC2 on UPS ? I'd say it is power related, not HC2 related.

i think you have to be on ZWave 3.0 engine on the HC3 to be able to upload the firmware file for the device. And that requires a full reset of the HC3.

@Kage i tried for many hours to get those filter to work. Multiple interface filters does not work. Single filter you can do like this: {"filters": [{"filter": "type", "value": ["com.fibaro.FGR223"]}],"attributes": {}} try it out in swagger

Well cheers for the answers @petergebruers. I kinda knew the answer to all. In my personal opinion , Yubii app is unusable, period. It works kinda OK if you have a small network and you are logged in through LAN, but if you have a big network and use remote then you are screwed. Not to mention i think the old app looked way better - but that's subjective. I tried at least 3-4 other ZWave gateways, none came close to HC3. I tried 2-3 apps, all were far ahead of Yubii app.

did you zniff it? As i was in the same boat some time ago and after trying some of the repeaters mentioned by you i found out that they spammed my network, causing more harm then good. Ended up relocating my HC3 in the middle of the house in the ceiling lol

@petergebruers OMG i'm getting close to 10 years also.. Gratz for holding on for so long and being an inspiration and true source of help for many of the people here ! @Theo in my view, Fibaro still makes the best Zwave gateways. And to be honest that is the hardest part, not the devices. HC3 is a huge jump from HC2 and believe it or not, it will not be so hard to recode all scenes. Plus the migration tool works very well now so you will not have to dig into the wall for those devices. And now questions for Peter: 1. Do you still remember where all the devices are placed ? As sometimes, when an old 300 series dies on me.. it takes me a long time to find it 2. Did Fibaro ever approached you to offer you a serious job ? 3. What mobile app do you use for your house automation ? 🤗 And finally i can say i'm very glad i "met" you and some more peeps around this forum - they know who they are !!!! 🍻