Netatmo Thermostat

Good morning,
I have a Netatmo thermostat and I have received an update to the relay firmware (going from release 210 to 222) and to the thermostat itself (going from 72 to 75). After this update, the Thing relating to the thermostat is OFFLINE and in the openhab.log file I have the following exception: java.lang.IllegalStateException: Expected an int but was BOOLEAN at line 1 column 233 path $.body.devices[0].plug_connected_boiler.
I tried to delete the Thing and do a new search, but nothing. I re-entered it manually but I still have the same error. I have a second thermostat that hasn’t received the update yet but it works fine. The Thing related to the Relay instead works correctly. Do you have any suggestions?
Thanks Matteo

As a matter of fact in current version of the API this was an int and it apparently changed to be a boolean (that is by the way quite normal). Please file an issue in github.

I have the same problem. Is there any solution?

Thank you

You can test the version currently in PR

It has also happened to me, the thermostat has stopped working, since they updated the firmware relay.

Hi @glhopital where can I find the jar to test?
Thanks a lot.

Download available in the beginning of this PR

I tried the jar but I have the following error:
Exception occurred while calling thing handler factory ‘org.openhab.binding.netatmo.internal.NetatmoHandlerFactory@1dc6df7’: NetatmoHandlerFactory could not create a handler for the thing ‘netatmo:netatmoapi:b65545aa’

This jar his a complete rewrite, so you can not use previously existing things, you’ve got to create new ones.
In order to get started :

  • remove previous binding installation
  • comment or remove previously defined things
  • drop the jar in addons folder
  • go in add things, and configure the netatmo binding to access your account
  • launch discovery of things

This is commented in the PR discussion (documentation is not up to date).

Sorry my fault, I didn’t read the entire thread. I followed the procedure and everything is working. Thanks a lot. for your work.

Please, keep me posted with your tests, you’re one of the first testing energy part of the binding.

I’ll do. Thanks again.

@glhopital I sawa small problem with the welcome camera. Every time the binding make a refresh, items are switched to UNDEF and then to the current value. This way the log is flooded with unnecessary updates.

Thanks for noticing, I’ll have a look at this. @Rickytr : can you provide me with some log examples ?

This is what I have in my log every minute:

2021-02-02 17:16:55.705 [vent.ItemStateChangedEvent] - Item ‘Latest_event’ changed from PERSON_AWAY to UNDEF

2021-02-02 17:16:55.710 [vent.ItemStateChangedEvent] - Item ‘EventPersonID’ changed from yyyy to UNDEF

2021-02-02 17:16:55.716 [vent.ItemStateChangedEvent] - Item ‘Latest_event_time’ changed from 2021-02-02T16:53:50.000+0100 to UNDEF

2021-02-02 17:16:55.726 [vent.ChannelTriggeredEvent] - netatmo:NAPerson:xxx:xxx:home-event triggered PERSON_AWAY

2021-02-02 17:16:55.734 [vent.ItemStateChangedEvent] - Item ‘Latest_event’ changed from UNDEF to PERSON_AWAY

2021-02-02 17:16:55.738 [vent.ItemStateChangedEvent] - Item ‘Latest_event_time’ changed from UNDEF to 2021-02-02T16:53:50.000+0100

2021-02-02 17:16:55.742 [vent.ItemStateChangedEvent] - Item ‘EventPersonID’ changed from UNDEF to yyyy

The problem is more serious…

2021-02-03 01:00:07.144 [vent.ItemStateChangedEvent] - Item ‘Latest_event’ changed from PERSON to UNDEF
2021-02-03 01:00:07.150 [vent.ItemStateChangedEvent] - Item ‘EventPersonID’ changed from d57caa5b-1bd7-45da-b908-9e519bddab63 to UNDEF
2021-02-03 01:00:07.166 [vent.ItemStateChangedEvent] - Item ‘Latest_event_time’ changed from 2021-02-02T21:51:03.000+0100 to UNDEF
2021-02-03 01:00:07.179 [vent.ChannelTriggeredEvent] - netatmo:NAPerson:xxxxx:xxxxx:home-event triggered PERSON
2021-02-03 01:00:07.187 [vent.ItemStateChangedEvent] - Item ‘Person1’ changed from ON to OFF
2021-02-03 01:00:07.195 [vent.ItemStateChangedEvent] - Item ‘Person1’ changed from OFF to ON
2021-02-03 01:00:07.200 [vent.ItemStateChangedEvent] - Item ‘Latest_event’ changed from UNDEF to PERSON
2021-02-03 01:00:07.203 [vent.ItemStateChangedEvent] - Item ‘Latest_event_time’ changed from UNDEF to 2021-02-02T21:51:03.000+0100
2021-02-03 01:00:07.205 [vent.ItemStateChangedEvent] - Item ‘EventPersonID’ changed from UNDEF to d57caa5b-1bd7-45da-b908-9e519bddab63
2021-02-03 01:00:08.508 [vent.ItemStateChangedEvent] - Item ‘Person1_lastseen’ changed from 2021-02-03T00:58:12.383610+0100 to 2021-02-03T01:00:08.499740+0100
2021-02-03 01:00:10.145 [vent.ItemStateChangedEvent] - Item ‘Person1_lastseen’ changed from 2021-02-03T01:00:08.499740+0100 to 2021-02-03T01:00:10.137161+0100

After ‘Person1’ (person#at-home channel) is switched away by the camera (after 4 hours) the OFF/ON switch is happening at every refresh cycle (and stays ON wrongly).

Noticed, I’ll have a look at this.

Hi Gaël,
Hope you’re fine ?
I have Openhabian 2.5 .
I add the new binding
inside the
and i meet an issue, see the log bellow

Do you have an idea to solve this ?
Best regards,

Hi @LouisD , unfortunately, this version is not backward compatible with OH2.5

Thanks @glhopital ,
Meaning I need to upgrade to OH3 to make Netatmo binding work?
Thanks again