[feature request] boiler_status

[lboue]

Hello,

Could you add the boiler_status status to the netatmo2MQTT.py script:?
I would be able to be notified when boiler is turning on.

Here is my getHomeStatus json result

{   'body': {   'home': {   'id': '**************************',
                            'modules': [   {   'firmware_revision': 197,
                                               'id': '70:ee:50:xx:xx:xx',
                                               'rf_strength': 107,
                                               'type': 'NAPlug',
                                               'wifi_strength': 26},
                                           {   'anticipating': False,
                                               'battery_level': 3753,
                                               'battery_state': 'high',
                                               'boiler_status': False,
                                               'boiler_valve_comfort_boost': False,
                                               'bridge': '70:ee:50:ab:cd:ef',
                                               'firmware_revision': 71,
                                               'id': '04:00:00:xx:xx:xx',
                                               'reachable': True,
                                               'rf_strength': 39,
                                               'type': 'NATherm1'},
                                           {   'battery_level': 3213,
                                               'battery_state': 'full',
                                               'bridge': '70:ee:50:ab:cd:aa',
                                               'firmware_revision': 73,
                                               'id': '09:00:00:xx:xx:xx',
                                               'reachable': True,
                                               'rf_strength': 82,
                                               'type': 'NRV'},
                                           {   'battery_level': 3081,
                                               'battery_state': 'full',
                                               'bridge': '70:ee:50:ab:cd:bb',
                                               'firmware_revision': 73,
                                               'id': '09:00:00:xx:xx:xx',
                                               'reachable': True,
                                               'rf_strength': 55,
                                               'type': 'NRV'}],

Regards,

[seblucas]

I'm currently switching from getthermostatsdata (deprecated) to homesdata API call.

I was not going to use homestatus mainly because I never got a clear answer from Netatmo about when the data is updated (I tried through the forum and with a mail without any answer in both case). Does each call of homestatus directly contact my thermostat at home to get latest information ? Is there some kind of cache involved, in that case what is the refresh rate ? Is there a status somewhere in case my Internet connection is down or Netatmo servers have a problem ?

Did you test this API call and can confirm it's real time (that it connect directly to your device at home) ?

For now I take everything coming from Netatmo with a grain of salt especially if it's not documented properly and prefer to use getmeasure (at least it's clear it does use not any kind of cache, data come from netatmo servers, ...).

[lboue]

Hello,

Yes. I can confirm that boiler_status is True from homesdata API call when the boiler is on. I checked that many times.
To check that I am using this script: PyAtmo.

Regards,

[lboue]

It take 1 minute to report the new boiler_status to False when boiler is going down. Same when it goes up.

[seblucas]

Thanks for the test, that mean it's possible to have almost live data from Netatmo (because I guess the temperature therm_measured_temperature is also updated within 1 minute).

I'll test that and if it works I'll drop getmeasure (it complicates things a lot) and use homestatus. That way I will include many more data in the mqtt payload (battery state and level, rf strength for all modules, wifi strength, and of course boiler status).

I'll create a branch tomorrow and will keep you updated.

[lboue]

Hello,

Did you take the time to give a try?

Regards,

[lboue]

Check PR #7

[seblucas]

I was away for work all past week, I just had time to code it but I never tested it. will do this week.

Thanks for the PR, I'll check that after testing.

[seblucas]

I tested it for 2 days and it really seems to provide live data .... cool. At least it's comparable to what getmeasure gives.

I'll merge my branch at the end of the week to be fully sure.

[lboue]

Thanks. that's great news. I look forward to that.

[lboue]

J'ai remarqué un nouveau commit ici: 16b9108
Le fait d'utiliser comme séparateur un point-virgule va poser problème sous Linux.

netatmo2mqtt/netatmo2MQTT.py

Line 116 in 16b9108

help='The information to send and the MQTT topic on which to publish the message (if it was a success) separated by a ;. Can be call many time')

En effet, cela indique au shell d’exécuter une 2ème commande qui se trouve après ce point-virgule. De fait le script Python ne passera pas la fin de l'argument.