Added support for Vaillant Thermostat, how to integrate in official release

huuub · April 11, 2019, 12:20pm

Seeing the same thing. Were you able to fix this?

ffontana · April 18, 2019, 8:14am

Is this component still working for Spanish Migo servers on 0.91.4 system version?

Thanks.

scote · April 23, 2019, 2:39pm

It still works for Vaillant. I’ve just upgraded to 0.91.4 and I had to follow the renaming and moving of the two files mentioned a few posts up and edit the import lines and it is working again.

huuub · April 25, 2019, 8:30am

Since today it is not working anymore ? Anybody else having the same issue?

schford · April 25, 2019, 9:08am

yes me too latest HA assistant has broken it

huuub · April 25, 2019, 9:55am

I reverted to 0.91.4 and it is working again… pffff

pjmaenh · April 25, 2019, 4:32pm

@huuub @schford
I rewrote the code, and I have the component now working again with Home Assistant 0.92.0 and my Bulex Migo. Code is still messy, will first do some cleanup and then publish it somewhere on GitHub. Stay tuned.

@Dixietoom just pinning your name here

huuub · April 25, 2019, 7:36pm

eagerly waiting my friend

pjmaenh · April 25, 2019, 10:30pm

The custom component is now available on GitHub.

To use the component, copy the vaillant directory to your custom_components folder and add the following lines to your configuration:

vaillant:
  api_key: <API_KEY>
  secret_key: <SECRET_KEY>
  username: <USERNAME>
  password: <PASSWORD>
  discovery: False
  app_version: <APP_VERSION>
  user_prefix: <USER_PREFIX>

climate:
  - platform: vaillant

Replace <USERNAME> and <PASSWORD> by your Vaillant / Bulex / Saunier Duval credentials.
Replace <API_KEY>, <SECRET_KEY>, <APP_VERSION> and <USER_PREFIX> by the correct keys for either Vaillant or Bulex / Saunier Duval. These values can be retrieved by decompiling the official mobile app (and most can of them can be found in this thread). Note that the values are different for vSMART and MiGO.

schford · April 26, 2019, 8:40am

Fantastic work

To make it easy for Vaillant guys

app_version: 1.0.4.0
user_prefix: vaillant

Thanks so much for this!

huuub · April 26, 2019, 8:58am

Thanks @pjmaenh and @schford!
Maybe another hint to not have to copy the files over and over…
Mount it as a volume in docker.
…/GIT/home-assistant-vaillant/custom_components/vaillant:/usr/src/app/homeassistant/components/vaillant

ooh and maybe for them still not able to find the secret_key.
I don’t know why it would be a secret so,

vaillant:
  api_key: na_client_android_vaillant
  secret_key: 929a......745f0
  username: in your app
  password: in your app
  discovery: False
  app_version: 1.0.4.0
  user_prefix: vaillant

climate:
  - platform: vaillant

schford · April 26, 2019, 9:00am

I think the worry is they might change it - if we make the secret key public…

huuub · April 28, 2019, 10:32am

BTW… Was testing away mode.
{“away_mode”:“False”}
Make sure you use capital. It works.

januszjm · April 30, 2019, 6:08am

could you please send me secret_key ? thanks

januszjm · May 1, 2019, 11:52am

could you please send me secret_key ? thanks
JJ

januszjm · May 1, 2019, 1:17pm

eventually I managed to decompile apk and found secret_key … now time to test in HA.
JJ

rudgr · June 7, 2019, 6:34am

hmmm, after upgrading to HA 0.94 the vaillant component fails to load:

Unable to install package https://github.com/samueldumont/netatmo-api-python/archive/v1.4.1-vaillant.zip#pyatmo==1.4.1-vaillant: ERROR: Could not satisfy constraints for 'pyatmo': installation from path or url cannot be constrained to a version

Derk · June 10, 2019, 7:19pm

Got the same message since upgrading to HA 0.94.

pjmaenh · June 13, 2019, 11:19pm

I have been looking into this and found a possible solution. Will do some further testing first, stay tuned…

pjmaenh · June 16, 2019, 11:42am

@rudgr, @Derk

A quick update: I got the component working again with HA >= 0.94, after refactoring the pyatmo-vaillant component a bit.

However, since a few days, the pyatmo library stopped working for me, and produces the following error:

  self.temp = self.modList[0]['measured']['temperature']
  KeyError: 'temperature'

I have looked into this, and it seems like the netatmo API no longer returns the measured temperature and the preferred temperature for my MiGo device. The only ‘measured’ value I still got is the estimated preferred temperature, but I have not found a workaround yet for getting the actual inside temperature.

I am not sure if this is a problem with my MiGo device, or if it is a general problem. It could be that netatmo changed its API, which broke support for Bulex and Vaillant. As a side note, the official MiGo API also no longer shows the inside temperature, so the error has nothing to do with the HA integration.

I will wait a few days to see if Bulex/Vaillant fix this issue. I already modified the code a bit, to get rid of the error (just take 0 when there is no temperature available) but off course this makes the component kind of useless as the thermostat needs to know the inside temperature in order to know when to turn the heating on or off.

Will keep you posted…