I do use Netatmo valves for the second year now and I have to set manually the true temperature many times to match the real room temperature.
To check the temperature, I use 2 LYWSD03MMC in each room (one near heater, one at the opposite) and I use the average value as reference. Of course All my LYWSD03MMC are set so that they match (temperature and humidity) to a single master thermometer.
Now, as I am lazy, I wish to find a way to set “True Temperature” on each valve using a script (or some scripts) in Hassio.
Unfortunately, the official Netatmo API doesn’t offer this possibility for now. But I found this thread using google taday and wonder if some of you that are used to developp could port it to Hassio.
It is done on Jeedom (some alternative ot Hassio) and it may be alose done on Hassio. It uses PHP commands sent to the official web service (as if you use the real web interface to set truetemperature) :
ok, so I am trying to do the same and become a bit furious with it. So let’ do it together.
My case - I open the doors for two hours to change the air, the temperature drops to 7°C but when it becomes heating, valve shows 11°C while my temp sensor shows 18°C and there is definitely something closer to 18°C
I tried to set the attribute in climate entity but that sets it for HA not for NETATMO, so it is rewritten quickly and as it does not influence the way netatmo works, making a script doing this every 5s does not change anytning. This is not the way.
We can try to ask @cgtobi but he likes to let me dig this rabbit hole first before telling me how he is doing it
So I played with it a bit and get used to the post commands to the API. Setting true temperature is not documented in the API or if it is, not in the visible part of API. However, the API apparently reacts on the command.
I got lost in the moment when I need to produce a token and use it in the command. That probably require some coding instead of formatting a simple post command. Setting modes such as away were surprisingly easy but setting true temperature returns error:
{"error":{"code":1,"message":"Access token is missing"}}
The truetemperature endpoint is not available for third parties and even if it would work it is not officially endorsed by Netatmo. So, this wont get implemented neither in the Netatmo integration nor the underlaying library.
I will contact them and ask for a possibility to use Netatmo room temperature measurement to control the heating. In my case the true temperature is most of the time much warmer than the thermostat suggests. Maybe the listen and implement such a feature.
What’s frustrating for me is that on Jeedom the netatmo plugin really brings us the equivalent of the functionalities we have on the mobile app.
It’s rare but for once I feel limited by Home assistant when it comes to heating.
As I’m in the middle of a migration, I’m obliged to keep jeedom to manage my heating, as all the rest of my home automation will migrate to Home assistant.
I’m also missing the choice of schedule with this official plugin, as well as the choice of modes (frost protection, absent, etc.).
As @maehmann correctly stated, the mentioned API endpoint is for setting the room temperature and is used by the integration. I understand your frustration. Apart from the truetemperature setting, could you elaborate what you are missing? The Integration does support presets for frost guard, away and so on.