Issue with FGT-001

[Belgacom 0]

Hello everybody, 

 

It's makes now 2 years that I used FGT thermostatic valve to manage my heating in my house. During these years no issues at all. 

And following the upgrade of firmware of my HC 2 and of my FGT, ( HC2 4.6 and FGT 4.7 ) all my FGT are no more usable. 

 

I do see a change of temperature when I reuqest it, but motors are not moving every time. If I move from 19 to 21 for example, nothing move. I have to put the valve at maximum, to hear the motor moving, or to close it. 

Sometimes when I request a change of temperature, the valve do a calibration sometime not. 

The external button to pilot the valve is no more working on all my valves. Not possible to request a manual calibration for example. 

I tried to reset to factory, reinstall it, it worked for a couple of hours, and again, no possibility to use external button, and very strange behavior. 

 

I started with one FGT, and weeks after all my FGT start to show the same issues. 

I can't add a sensor on it, because the external button is not working. 

 

On the HC2 interface,  expect some calibration failure I don't have any alarms. 

Currently I removed all FGT head, because the manage was no more possible. 

Did someone experience this kind of problem, or have an Idea of what I can test, do ? 

 

thanks for your help. 

Arnaud 

 

[MariusRN 0]

Well, I have a similar issue. The valve stays open all the time. If I try to calibrate, the menu button pushed continuously cycles the menu, but when trying to calibrate it does not take the command. Sometimes (veey rarely and randomly) it takes the calibration command, it calibrates, remaines closed and after a few hours or until next day it goes all open again. It is like it goes in a software hang but only one of the execution threads, or in a logical deadlock.

 

Mine came already with FW 4.7 installed. Bought ~2 years ago.

 

I had to pull it out too. I just couldn't stand it out anymore! Just a piece of rubbish. There are so many unhappy posts about this valve! Some users say they never had a problem. Do they have the 'same' 4.7 FW? Or do we have some hardware issue that is not compatible to this FW? Who knows? Everything is closed at Fibaro, even firmware updating. I couldn't even find the FW changelog (not saying it doesn't exist, but my many trials to find it were unfruitful).

 

I've got another one, but did not test it yet. New, sealed in the box. I would test it without registering it to HA. Maybe the Z-Wave thread gets deadlocked and the device works weirdly so I suppose not being in a Z-wave network may help... I don't know... it sucked so much energy from my nerves that I almost feel sick to even try. If I exclude it from the network, HA will delete all the settings and when I include it back I need to manually redo eveey setting and its plugin in the UI Dashboard in HA. Probably it would have been easier with HC2 or some more comeecial device but, in your case, you already have HC2 and same issue.