Fibaro's head works as he wants

[Fibber 1]

Ohřívače s externím snímačem jsou pro mě stále velkým zklamáním ... Jednou noc nastavte hlavu na 20 ° C a OK, držte ji.

 

Hlavy kalibrované, spárován s teplotním čidlem

 

Druhá noc znovu nastavila, ale ta se roztavila tak hloupě jako 23,4 ° C!

 

Při nastavení všech žádných teplotních snímačů vysílá data o teplotách ve velkých intervalech, viz obr. Grafy od firmy ImperiHome, protože v aplikacích. Fibaro nikde nepředstavuje teplotní historii.

 

Kromě toho je hlava nastavena na Vypnuto, motor se slyší a možná po 20-30 minutách motor opět bzučí. Proč? Mělo by však být v pozici Off, kde a proč se pohybuje?

 

Nyní snímač teploty ukazuje 20 ° C, nastavil jsem hlavu na 22 ° C a zajímalo by mě, jak se topení netýká ani po 15 minutách. Teprve když si na chvíli přidám MAX a pak ho nastavím na 22 ° C, tak to je. PROČ?

 

Co dělám špatně? Děkuji za radu, zkušenosti.

Please login or register to see this attachment.

[meute 2]

The problem is know and seems to impact 100% of the user, this Heat controller is totally useless for now and worst that a manual valve that you will let opened half or an hold mechanical thermostatic head, we are all waiting for a firmware update from Fibaro but not announced before March ...

The only solution to work with it is to crush the regulation by force it to open or close from the home controller with script or scene

Edited January 20, 2018 by meute

[Fibber 1]

Do they do all the heating valves, or is there a valve, or someone who has no problem with it, and the head works as it should?

[meute 2]

So far I have not seen any users on any forum who said "I have no problem with this product"

All opinions are the same: the valve does not regulate anything properly and even works against common sense.

 

So I do not know if this product works on some models of valves and not on others but for having spent enough time trying to analyze their behavior there is no reason to think that it would work on some type Valve.

 

I know that generally users who are happy with a product do not come to say it on a forum but I frequent forums where people are active in home automation because it is their passion and where they make thus returns and also when returns are positive ...

[evanbeem 2]

Hi there,

 

So far I am lucky to have no issues with the heat controllers that use an adapter for the valves. I must say that I don't use the accompanying external temp sensors with them.

The only one I do have a problem with is a mechanical problem. One HC is used without any adapter and when screwing it on the valve, it pops out the entire knob.

Need to find a fix for that, but it is unrelated to your problem.

 

Regards!

[meute 2]

42 minutes ago, evanbeem said:

So far I am lucky to have no issues with the heat controllers that use an adapter for the valves. I must say that I don't use the accompanying external temp sensors with them.

Hi,

You are the first "happy" user I see , can I make a selfie with you ? 

Since how many time do you use yours ?

 

For your mechanical problem, all the "standard" M30x1.5 valves are not standard unfortunately, I have the invert problem on only one of mine, the stem was too short and the screw of the heat controller have not enough stroke to close it completely so calibration fail too. I have changed the valve for the same model as my other radiators.

And I have some older M30x1.5 valves in a drawer and it's the same as your, it's not possible to screw the Heat controller completely without pop out the entire knob, on mine it's because the first hexagonal shape is too big.

Edited January 22, 2018 by meute

[Reve 3]

I have equipped six rooms with the TVR FGT-001. The function is a pure disaster. The following errors occur.

The heating plan works in advance and the setpoint values ??are transferred to the FGT-001. The following scenarios are now created using the example of the bedroom:

 

1) The FGT-001 remains cold the vetil will not open, although the temperature is not reached. For example, Target 18 ° is 15.5 °

2) The FGT-001 heats up through the valve does not switch off

3) At night, the valve keeps opening and closing (about every 30 minutes) although the room temperature is much higher than the setpoint temperature.

 

A connection is not recognizable, other rooms have similar reservations. After several attempts delete, resete and everything you can do so. Today I have the first FGT-001 removed again, because the function is unbearable.

Especially when I bedroom at a time are tempeturen the sauna and the constant whirring of the engine annoying (see point 3).

Therefore the specific question:

When will an update for the devices or what solution approach can Fibaro offer? (The alternative over scene 0 or 100% to use is out of the question).

[evanbeem 2]

@meute Selfie will only possible via virtual device....don't have the coding background for it.

 

I'm using the units (4 in all in different rooms) for about a month. Still no issues.

But, I see the most of the issues are regarding the FGT-001 in combination with the external sensor. I don't have the extra sensors.

 

I've seen some issues before in communicstion between two Zwave devices that are associated (so they communicate with eachother without the home center), due to the different sleep time defined.

The effect being that the devices only have a connection occassionally. That could explain the temperature overshoots and failing to respond, but I'm no expert on this.

Changing the sleep time adversely influences the battery life of these devices. so you'll end up between a rock and a hard place. Fibaro will need to issue a firmware update for that, I suppose.

 

The mechanical issue with the adapter is still not solved, so I'm looking for another valve as well. The Danfoss types where you need the extra rings supplied with the FGT-001 don't have the problem of popping the knob out, so I'll check with my local dealer.

 

[petergebruers 1,268]

12 hours ago, evanbeem said:

I've seen some issues before in communicstion between two Zwave devices that are associated (so they communicate with eachother without the home center), due to the different sleep time defined.

The effect being that the devices only have a connection occassionally. That could explain the temperature overshoots and failing to respond, but I'm no expert on this.

 

Clever thinking. That effect certainly exists! But it does not apply to the FGT and also not to the FGT temperature probe:

1. The probe is a BLE device, not Z-Wave. It talks to the FGT, not your controller.
2. The probe sends data every 10 minutes to the FGT over BLE.
3. The FGT reports over Z-Wave, but this does not influence open/close unless you wrote some Lua script to use this value.
4. If the FGT does not receive data from the probe, it will send a notification, you'll have a message on your home page. I own two FGT + sensor and this does not happen, unless I take out the coin cell...
5. I monitor the reporting of the FGT. The external probes match my DS18B20 sensors to within +/- 0.25 degrees C.
6. None of the existing TRVs uses Z-Wave to obtain sensor data.
7. I did a quick test, and even without external sensor one of my FGT got "stuck". It is a very unscientific test. I'm guessing it occurs less without external sensor, but I cannot tell because the test time was too short.

[evanbeem 2]

@petergebruers:Thanks for clearing that up.   I'm not that deep into the hardware, so I'm glad you are!

So far I am still running my setup without any issues, but your post made me check on the FGT's every few days in case they get 'stuck'.

[petergebruers 1,268]

1 hour ago, evanbeem said:

:Thanks for clearing that up.   I'm not that deep into the hardware, so I'm glad you are!

 

Thanks! You can show your infinite gratitude  by clicking the "like" button on that post.

 

Have fun with automation!