search

ilcato / homebridge-Fibaro-HC2

Homebridge plugin for Fibaro Home Center 2 (and Home Center Lite ...)
Apache License 2.0
67 stars 27 forks source link

Fibaro ZXT120 issue #126

Closed batalhaca closed 3 years ago

batalhaca commented 5 years ago

In my case i have 8 ZXT 120 in the HC2 while imported to Homebridge some funny think happend. Some Thermostate in Homekit the mode and the temperature setpoint are controlling different ZXT120. Example: i had a Bed Room and a Living room while i control the Living Room in Homekit to set Cool in the Living Room but the Bed Room ZXT 120 responded and if i control the Living Room setpoint and Living Room responded correctly.i can confirm that the devices in HC2 are named unique no overlaping.

batalhaca commented 5 years ago

Using 2.1.7

ilcato commented 5 years ago

Will check it.

ilcato commented 5 years ago

Can you try expose only one device to Homebridge and see if it works?

batalhaca commented 5 years ago

Hi,

I found that the issue only occurs when Fibaro systems had a few remote gateways. Only the ZXT120 from the remote gateway will have this issue and will be fine if all other ZXT are on the main gateway.

Carlos

Sent from my iPhone

On 9 Mar 2019, at 05:10, ilcato notifications@github.com wrote:

Can you try expose only one device to Homebridge and see if it works?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

ilcato commented 4 years ago

can you test now?

Mx-Razvan commented 3 years ago

Hi ilcato!

Seems that on 2.3.6 the zxt-120 doesn't work anymore as before. Now only the temperature set is working, not the op mode.

[22/08/2020, 11:18:37] [FibaroHC2] Setting value to device: 640 parameter: Target Heating Cooling State [22/08/2020, 11:18:37] [FibaroHC2] Command: setSetpointMode, value: 2, to: 640 [22/08/2020, 11:18:37] [FibaroHC2] There was a problem sending command setMode to 642641 [22/08/2020, 11:18:39] [FibaroHC2] Setting value to device: 640 parameter: Target Heating Cooling State [22/08/2020, 11:18:39] [FibaroHC2] There was a problem sending command setMode to 642641

the same behaviour is on 2 fibaro systems. I saw that if I perform a soft reconfiguration of the ZXT it works for 30' then nothing.

any ideea how to fix it?

Thanks, R

fjosepose commented 3 years ago

Hi Same issue for me with the missing operational mode and fan..didn’t find this issue before now so I already created an new issue https://github.com/ilcato/homebridge-Fibaro-HC2/issues/199

baafonso commented 3 years ago

the current release version of this plugin has a bug in file shadows.js. this bug is not present in the source file shadows.ts.

to fix open the console on homebridge and edit the file shadows.js on directory :

/usr/local/lib/node_modules/homebridge-fibaro-hc2/dist/

change:

                controlService.subtype = (controlService.subtype || device.id + "---") + "-" + t.id;

to:

// controlService.subtype = (controlService.subtype || device.id + "---") + "-" + t.id; if (controlService.subtype) { controlService.subtype = controlService.subtype + "-" + t.id; } else { controlService.subtype = device.id + "----" + t.id; }

after editing the file, restart homebridge.

this fixes the problem.

if it doesn't, remove the thermostats from homebridge, restart and try again.

ilcato commented 3 years ago

@baafonso, it should be fixed in 2.3.7

baafonso commented 3 years ago

@ilcato , confirmed. you can close this issue...