Fibaro fgt001 heat controller support

Configuration
1

Ive been trying to connect the fibaro fgt001 to HA but it looks like it requires a recent commit to openzwave to add support.
I have HA setup as a docker. Does anyone know how to update to the latest openzwave version in docker?

1 Like
2

same problem here.

3

Yeah, same here…

Maybe this is updated with the next release of HA?

4

+1.
I’ll check how the docker container is built…

5

Let’s see what kind of response I get here: https://github.com/OpenZWave/open-zwave/issues/1401
Afterwards, it seems that python openzwave wrapper needs to be released first. Last release is a few months old.

6

I got it up and running: updated the Docker container to download the latest

7

Can you share details about the changes you’ve made? Is everything working as it should now?

8

it’s all working. I had to delete the devices and re-add them.

I’ve just forked and committed my changes:

Clone the repo, then “docker build .” on your synology and start the image with your old configuration.

Enjoy!

9

I’m running hassbian, how can i get this to work? @Tobias_Schlottke

10

Me too!

Could anybody help with steps to activate on hassbian?

/Johan

11

Hi there @Tobias_Schlottke and others…!

So, finally installed my heat controller which doesn’t work very well. I would love some help with steps to take.

Regards,
/Johan

12

My product experience so far is also mediocre. What are your issues? Do you think it’s the software or the hardware?

Tobias

13

Hi Tobias! Well, I don’t know how to make it work at all… I just installed on my radiator, and just as you and others mentioned it isn’t usable at the moment. I haven’t actually tried anything yet, I use hassbian and don’t really know what the equivalent of “update docker container” is.

Thanks
/Johan

14

Did anyone get this to work? I just installed 4 FGT-001 thermostats but home assistant is not really detecting them well.
This is how the dashboard looks like:

[Album] Imgur

[Album] Imgur

And the Z-Wave settings:

[Album] Imgur

Its rather a mess. I can switch heating on and off, and I can hear the thermostats turning, but a) I can’t seem to set a specific temperature b) the dashboard shows 7 thermostats while only 4 are installed and added to the network.

I would really like to stick to HA and not switch to e. g. openHAB, so maybe this will work somehow?

Other option for me would be to send back the fibaro thermostats and get e. g. homematics instead.

15

I have to add that I somewhat got it to work. After several (non-related) HA uninstalls/installs the thermostats now get detected properly, and I’ll get somewhat working climate entities.

I can change operation mode and temperature, however the overview in HA will not get updated properly. E. g. right now it shows one thermostat in “Heat” mode while it is clearly off since last night.

Also, none of the thermostats temperature sensors seem to report anything.

Anyone got this to work?

16

I have got this semi-working, it reads the values i manually set it to. It will also send the new setpoint if set from hass, but it wont update the info in hass.
I worked around it with these 2 bits that refreshes the node every 15 minutes:

automation:
  - alias: zwave_refresher
    trigger:
      - platform: time
        minutes: "/15"
        seconds: 00
    action:
      - service: script.rescan_zwave

script:
  rescan_zwave:
    alias: refresh_zwave
    sequence:
      - alias: refresh zwave 35
        service: zwave.refresh_node
        data:
          node_id: 35
17

Tried your script, but while it kinda works, it makes HA crash after a while:

â—Ź hass.service - Home Assistant
   Loaded: loaded (/etc/systemd/system/hass.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Tue 2018-02-27 10:15:05 CET; 8h ago
  Process: 19051 ExecStart=/srv/homeassistant/bin/hass -c /home/homeassistant/.homeassistant (code=killed, signal=SEGV)
 Main PID: 19051 (code=killed, signal=SEGV)

Feb 27 10:15:00 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=1971303408-16>
Feb 27 10:15:00 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=1971303408-12>
Feb 27 10:15:00 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state script.rescan_zwave=off; friendly_name=refresh_zwave, last_triggered=2018-02-27T10:
Feb 27 10:15:00 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state automation.zwave_refresher=on; friendly_name=zwave_refresher, last_triggered=2018-0
Feb 27 10:15:01 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state zwave.fibaro_system_fgt001_heat_controller=ready; receivedUnsolicited=0, receivedTS
Feb 27 10:15:02 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state zwave.fibaro_system_fgt001_heat_controller_2=ready; receivedUnsolicited=0, received
Feb 27 10:15:04 pi3HA hass[19051]: INFO:homeassistant.core:Bus:Handling <Event state_changed[L]: old_state=<state zwave.fibaro_system_fgt001_heat_controller_3=ready; receivedUnsolicited=0, received
Feb 27 10:15:05 pi3HA systemd[1]: hass.service: Main process exited, code=killed, status=11/SEGV
Feb 27 10:15:05 pi3HA systemd[1]: hass.service: Unit entered failed state.
Feb 27 10:15:05 pi3HA systemd[1]: hass.service: Failed with result 'signal'.

This is the script:

rescan_zwave:
  alias: refresh_zwave
  sequence:
    - alias: refresh zwave 5
      service: zwave.refresh_node
      data:
        node_id: 5
    - alias: refresh zwave 6
      service: zwave.refresh_node
      data:
        node_id: 6
    - alias: refresh zwave 7
      service: zwave.refresh_node
      data:
        node_id: 7
    - alias: refresh zwave 8
      service: zwave.refresh_node
      data:
        node_id: 8

Not sure though if this crash is caused by executing the script or by calling the zwave refresh service.