Replies: 3 comments 14 replies
-
|
Please try the new Beta 51 and there the AI Based calibration option, maybe that will help. Otherwise the new Beta also has a improved way with the fix_calibration mode. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
@wtom there is no AI based calibration option. There is just target temperature based calibration. |
Beta Was this translation helpful? Give feedback.
-
|
I have now installed 51 - I initially set the new Calibration mode to Aggressive, and left the simulated Off mode disabled for now. I've had that running for a couple of days now. The valves are still changing a lot. This morning when the heating was running it did a great job maintaining the target temperature, but it adjusted the TRV 18 times in a 1 hour period, jumping from about 8% up to 60% frequently, only to drop back again a minute later. Overnight it's been seemingly more settled than on 50, though has still adjusted every hour. On that second point, is the "heat_available" setting in Z2M unique to these TRVs or is it common? I was hoping that if that was off, that the valves would essentially stay dormant. I take it it's not quite as simple as checking for that option though? If I could have the valves settle down at night, then I could at least use BT in bedrooms. The other oddity I'll mention is that, under 50, adjusted the BT set point using the card would set the actual TRV set point differently, which I assume is intended behaviour to force the valve to react faster. However initially with 51, the set point on the BT card itself would change, meaning I'd lose the actual set point I'd entered. It doesn't seem to have done that today though... I'm switching to the AI Time based option now, so will see how that goes. |
Beta Was this translation helpful? Give feedback.
-
|
@Nuuki9 hmm.
It have to changing because BT modifiing target temperature of real trv to make temperature sbout setted. When i not using agressive mode there is problem with not reaching target temperature and overheating. So for me its fine. |
Beta Was this translation helpful? Give feedback.
12 replies
-
|
@wtom Just responding to my own query, I see reference in some issues to the |
Beta Was this translation helpful? Give feedback.
-
|
It's not anymore as a configuration option. I just added it as default. Could you try beta 51 and activate the configuration and check if that solves your problem? |
Beta Was this translation helpful? Give feedback.
-
|
@wtom I updated BT and deleted and re-added the devices (rebooting between steps). I saw the calibratrion setting so have enabled that, but otherwise left it on AI Time Based - if you'd prefer me to switch to Aggressive let me know. I'll leave it for a couple of days and then provide an update. |
Beta Was this translation helpful? Give feedback.
-
|
@wtom OK I think I've found an issue with this TRV, though hopefully not an insurmountable one. When I checked the BT logs I was continuing to see it publishing messages to set the TRV to max (35 degrees), and yet the TRV wasn't budging from 22. I was seeing correct MQTT messages being published, so it didn't look like a BT issue. What I've discovered is that the TRV won't respond to a setpoint above 32 degrees. Any 0.5 degree increments up to that work fine and result in a change within a few seconds, but setting to 32.5 or above is ignored. I've checked this by publishing MQTT using Node-Red, by setting it directly in Z2M, and also by adjusting the climate entity (not the BT one) in HA - same for all of them. I currently have two of these TRVs setup and they both exhibit the same behaviour, so I'm confident this is a limitation of the TRV itself. I see from some diagnostic logs in some other issues that others have Anyway not sure if this explains everything, but I guess its not helping. |
Beta Was this translation helpful? Give feedback.
-
|
@wtom Here's the graph for an hour this afternoon:
Throughout this period the measured room temperature is very consistent - between 16.2 and 16.5. Looking at the period 16:04 to 16:35, the valve changed once per minute on average - when the measured room temperature is 16.2, the TRV temp is set to 19.5 and when its 16.3 it drops back to 18.5. Here are the logs for this same period: I don't see any issues in the logs, so as far as I can tell its working as its intending to. One issue I think is the frequency with which its responding to temperature changes. The temperature sensor updates every 30 seconds, and even though as we see its very consistent, those frequent 0.1 swings are resulting in needless updates to the TRV. Wouldn't it be better to limit temperature readings to every 5 minutes, and ideally take an average for that period? If that were a configurable setting then that would allow it to be tuned. Anything else I can do so have it "calm down"? |
Beta Was this translation helpful? Give feedback.
-
|
I've just logged a more offical Feature Request (#812) in relation to finding out that these TRVs don't respond to setpoints above 32 degrees, as noted above, as that's somewhat separate to the original issue I was raising here. It also looks like Beta 55 includes rounding to 0.5 degrees, so I'm going to try that out for a bit. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a bunch of Hive TRV001 TRVs - they don't appear on the official BT list, but I do see a bunch of posts about them.
They're running the latest firmware and are connected through zigbee2mqtt. I enabled "If your TRV has trouble with not recheating the target temperature or overheating, this option can help", as it seemed like that worked well with these TRVs. I also have external room thermometers, which was the main reason for looking at BT - the built in temperature sensing of the TRVs was bad, and they don't support setting external temperatures directly in Z2M.
Right now I don't have the TRVs turning the boiler on - that's the plan but I need to ensure its working well on all the rads before I do that. I'm enabling "heat_available" on the TRV only when the boiler is actually running.
I'm seeing BT doing a generally much better job of reaching and holding the setpoint. However, it seems to be adjusting the valve an awful lot - not just to hold the temperature, but even when the set point is way below the current temperature.
Here's my office for the last 12 hours:
The blue line is the target temperature and the orange is the actual. The red blocks are when the heating was on, and the blue blocks show the valve open %.
If you look between 1:30am and 4am, the room was above the setpoint, and yet the valve was adjusted many times. Similar between 7am and 9am, when the heating was running and it had to gain about 4.5 celcius, the valve fluctuates quite a lot, from 15% up to 100%. That therefore limited how fast the room heated up, meaning it was a couple of degrees behind the rooms with basic TRVs in them. Right now its 1.5 degrees below the setpoint and the valve is only at 13%. It also meant I had to swap out the one in the bedroom, as it was just too noisy overnight.
Am I doing something wrong here? I'm aware that these TRVs lack some of the functions that others have, so may be more limited, but I guess I'd assumed that if no heat was needed they'd be pretty dorment.
Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions