Testers needed for Netatmo climate (multiple thermostats or valves)


#188

Try the following script (to modify accordingly, of course):

heat_bedroom:
  alias: Turn on bedroom valve heating
  sequence:
    service: climate.set_temperature
    entity_id: climate.netatmo_bedroom
    data_template:
      temperature: '{{ states.climate.netatmo_bedroom.attributes.current_temperature|float + 1 }}'

#189

Unfortunately this doesn‘t work either.


#190

This works:
temperature: ‘22’

filling in {} doesn‘t work:
temperature: ‘{{ 22 }}’

So maybe does sign are not allowed?


#191

This is kind of weird, because the script works for me (I set to “Comfort priority” operating mode in Netatmo Energy app).


#192

I also have “comfort pririty” but I don’t think it has something to do with that.

This my automation:

- alias: Cube - shake
  initial_state: 'on'
  trigger:
    platform: mqtt
    topic: 'zigbee2mqtt/Zigbee Cube'
  condition:
    condition: template
    value_template: "{{ 'shake' == trigger.payload_json.action }}"
  action:
    - service: climate.set_temperature
      data:
        entity_id: climate.netatmo_schlafzimmer
        temperature: '{{ states.climate.netatmo_schlafzimmer.attributes.current_temperature|float + 1 }}' #'22' works 
    - delay: 00:15:00  
    - service: climate.set_operation_mode
      data:
        entity_id: climate.netatmo_schlafzimmer
        operation_mode: Schedule    

As I said the weird thing is that '22' works and adding brackets will disable it ‘{22}’. Don’t know why the brackets work for your data input


#193

I think you should use data_template instead of data.


#194

I missed that, thanks a lot. Works now!


#195

Hi guys, it works for me too, thanks to the people who allowed this. Very good job

But I noticed that the history does not work. Is it the same for you?

And I noticed that since the installation, I no longer have the global history.

Thx


#196

Hi, this is a screenshot of the history of one of my valves. So my history works. It evens shows the heating periods. Or do you mean something else?

I don’t know whoch global history you mean. Do you mean the history of the thermostat?


#197

In your configuration.yaml, make sure you have:

history:


#198

Yes Baosong_Shan, i have.


#199

I never saw this. You may want to dig into the log file to see if there is anything abnormal logged.


#200

If you have a more elaborate history configuration with excludes/includes you might have to adjust that to fit the new entities.


#201

Hey,

Thx for the job done it s really great.

Did anyone try to export those entities to homekit ? because it works for me (1thermostat and 3 valves) except for the status which doesn’t sound to be updated. Let’s say the thermostat is heating on hass i see it as inactive on homekit. It s not big deal but still weird


#202

try to delete the home-assistant_v2.db from the config folder and restart home assistant.


#203

Hi, thanks for this awesome custom component. I’ve 2 netatmo thermostat in the same home but with this component I just see one of this, and the other is called correctly but shows the same parameter of the first one… Could you give me an help to solve this problem? Thanks in advance.


#204

Use this https://gist.github.com/shanbs/526b6cd424e7f1f872cbd320887a2f4a
From @Baosong_Shan


#205

About the naming of the operation modes, I would like to listen to your opinions. The operation modes in Netatmo most have not been localised in HA as a STATE of climate device: schedule, max, hg. So I have two options to resolve this:

  1. Map the modes to what HA has, like:
    schedule -> auto
    max -> high_demand
    hg -> eco
    The good point of this option is that the localisations have been done for the above words.

  2. Used Netatmo own as display:
    schedule -> Schedule
    max -> Max
    hg -> Frost guard
    The good point is this is more accurate, but it can only be displayed as above for the moment, as no localisations for them.

Which one sounds better for you guys? Thanks!

BTW, I’ve submitted a PR for the pyatmo library (codes in fact written by gieljnssns), but not yet merged.


#206

Hi, the second one will be better for me!


#207

thanks a lot! It works flawless!!!