Closed Schlurcher closed 2 years ago
Hey @Schlurcher,
thanks for providing the information. There's already a feature freeze on the net version 1.0, so the support is probably landing in 1.1 then.
Hey @Schlurcher,
as far as I can see this device doesn't have a local temperature calibration field, right?
I don't exactly know what you mean by calibration field? I assume in the attributes "temperature" means the temp that the thermostat is set to and "current_temperature" is the measured temperature. A quirk of the integration seems to be if you set the thermostat to MAX it jumps from 28 to 30 degrees.
I can do some tests tomorrow what gets reported as what.
Hey @Schlurcher,
sorry for being not that clear.
If you select the device under devices in HA, there are several fields under "Configuration".
Is there one that is called something in the realm of "local_temperature_calibration"?
set the thermostat to MAX
Can you show me where you would set it to MAX? In HA or in some FritzBox app?
You can set it in the admin ui of the box:
Or on a connected handset:
Or directly on the valve:
Behaviour is consistent across those methods. You can dial it in by .5 degrees up to 28 degrees. Then it jumps to MAX, which gets reported by the integration as 30 degrees.
Setting it in HA is a little bit different. There you can control it up to 27,5 degrees. Anything above that gets corrected to to 30 degrees, regardless of what you dial in. This then gets displayed as MAX in the ui, on the valve and on the handset.
Another quirk is that the valve only polls every 15 minutes for changes. Meaning if you set it by any of those methods (except of course directly on the valve, which broadcasts changes immediatly), it can take up to 15 minutes before the valve pulls in the change. I guess thats a limitation inherent to all battery powered Han-Fun devices.
I assume local temperature calibration is the same thing as an offset to correct for the temp sensor being directly connected to the valve and as such being next to useless in actually measuring the room temperature? :)
If so, that can be done in the admin ui of the fritz box: There you can also specify an external temperature sensor, but it has to be paired via dect to the box.
Either of those methods changes the temperature reported for the TRV by the fritzbox API (https://avm.de/fileadmin/user_upload/Global/Service/Schnittstellen/AHA-HTTP-Interface.pdf). I think there is no way to get a seperate measurement just for the offset.
It sports a "Window Open" detection which works by detecting a temperature drop of 0.7-1.9 degrees within 2 mins. For my case this doesn't work, since all my radiators set up like this or across the room from a window. As such the valve is nicely shielded from sudden temperature drops, and consequently this feature simply doesn't work 99% of the time. The fritzbox integration only reports the current state of window open, but provides no way to set it, even though the API allows for this (also outlined in the above pdf). Regardless, this would be out of scope for this project and has to be handled by the integration anways.
P.S.: Judging by your name I assume you can read german, but if you need me to provide translations for the screenshots I would be happy to oblige. ;)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity.
I'm using FRITZ!DECT 301 TVRs via the AVM FRITZ!SmartHome Integration, would be awesome if they can be supported.
If you can give me a pointer on where to look I may be able to contribute this myself.