eTRV-C-2 Valve_state is Too_tight

[jpvisser]

Hello,

I have more than 15 actuator in function controled by direct connentions and monitored by ccu3. but some times a few are going into error with valve state too tight message. (Seen in the hidden menu of my ccu3)
The valve itself however is not tight, easy to move. Anyone has an idea why these eTRV are going into error?

The other thing is, when the eTRV is in error, no message is set in the CCU3 and the actuator stops responding. It stays in it current position and room are getting realy hot. Is there a way to activate adaption run of the actuator by a script command sended from the CCU3?

Thanks.
JP

[Henke]

Try to loose the mounting of the eTRV a little bit. Maybe this fix the problem.

Is there a way to activate adaption run of the actuator by a script command sended from the CCU3?

Nope

[blueznl]

Is that triggering a CAL message on the valve?

[jpvisser]

No. Valve state = too tight. It does not react on any RF command and no message in ccu webui. Only in the hidden menu. The only way to reset is open/close the battery tray. It looks like it has something to do with valves who have kind of elastic end limit when completly closed. I made a ‘hat’ on the valve pin to make sure it has a defined end limit just before it becomes elastic. Did not see the error again until now. ???? fingers crossed.

[Lars M]

No. Valve state = too tight. It does not react on any RF command and no message in ccu webui. Only in the hidden menu. The only way to reset is open/close the battery tray. It looks like it has something to do with valves who have kind of elastic end limit when completly closed. I made a ‘hat’ on the valve pin to make sure it has a defined end limit just before it becomes elastic. Did not see the error again until now. ???? fingers crossed.

This is exactly the same problem I often run into. Can you pls explain your solution? I don´t understand what you did with the valve pin.
Thanks in advance.

[jpvisser]

Hi. I am still experimenting to find the root cause. Also with the “hat” the fault came back. Now i replaced the batteries delivered with the device with new ones (duracell) and that seems to help. The e-Q3 helpdesk confirmed bad batteries could be a cause. The batteries supplied by e-Q3 are of bad quality with high internal resistance. The other thing i did is spray a little WD40 on the valve. Please give me feedback when you found something.

[Karamike]

I hate to add a "me too" to this thread... but I have to.

I use CuXD to log the events from my devices.

Every 3 to 4 months I see the following in the log:

Code: Alles auswählen

2023-10-16T21:30:16+0200 XXXXXXXXXXXX:0_LOW_BAT 0
2023-10-16T21:30:16+0200 XXXXXXXXXXXX:1_SET_POINT_TEMPERATURE 18.000000
2023-10-16T21:30:16+0200 XXXXXXXXXXXX:1_LEVEL 1.000000
2023-10-16T21:30:16+0200 XXXXXXXXXXXX:1_VALVE_STATE 4
2023-10-16T21:30:16+0200 XXXXXXXXXXXX:1_ACTUAL_TEMPERATURE 19.300000

2023-10-16T21:32:30+0200 XXXXXXXXXXXX:0_LOW_BAT 0
2023-10-16T21:32:30+0200 XXXXXXXXXXXX:1_SET_POINT_TEMPERATURE 18.000000
2023-10-16T21:32:30+0200 XXXXXXXXXXXX:1_VALVE_STATE 5
2023-10-16T21:32:30+0200 XXXXXXXXXXXX:1_ACTUAL_TEMPERATURE 19.500000

• The Valve_State jumps from 4 (Adaption Done) to 5 (Too Tight).

• The sensor stops reporting valve level

• And yes, changing batteries helps... for 3-4 months.

On the other hand, the reported voltage was still at 2.9 V (down from 3.0 V with fresh batteries) which is more than the other thermostats.

The other thing i did is spray a little WD40 on the valve.

Did it help?