No Update of netatmo items

Add-ons Bindings
31

I think updating the thing is basically the same as restarting the binding. So it’s somewhat expected behavior.

32

Installed Version: 2.4.0.SNAPSHOT

33

I’ve noticed problems with this binding (or API) lately aswell (last couple of weeks perhaps), had to restart the binding many times and it keeps coming messages like deladus posted (Unable to connect Netatmo API : 500 Internal Server Error).
Using the latest testbuild M6…

34

I believe this is due to Netamo server. I have seen these errors as well a few times, mainly around midnight. I think it´s because Netamo is messing around.
Also the last 2-3 days, I have not been able to reach my Netamo weather station. It turned out to be due to new firmware. Had to force it to reconnect and then the message about new firmware popped up. After updating the firmware last night, it has been running fine again.

35

i’ve installed version 2.3.0 of netatmo binding via paper ui.
how i can install snapshot 2.4.0 and where i can download snapshot 2.4.0?

36

you can try M6: [OH 2.4.0 M6] Testing Results

edit: no… this PR was merged 2 days ago, so you need the latest Snap

Read in that FAQ about Snap also

37

I have similar problems. So far I could identify 2 reasons when no data appear in OH:

  1. binding stopped working
  2. Netatmo server issues

Mainly I’m faced with no. 1, thus my question is if this is the right area to investigate since no. 2 is out of influence area.

Are there alreay any issues raised to stabilize the binding?

38

Just to report that I am having refreshing issues too, since about 10 days on OH 2.3.0.
I have to restart the binding several times per day :cry:
I saw that also the Netatmo App had sevaral disconnections.
To get aware of Netatmo refresh failure I implemented a notification rule, so I can do a manual restart of the binding. (I know it’s not PRO and in some way it could be done with items previous state, still it works).
If anyone is interested in annoying notifications :wink: …

var Netatmo_Prev_Out_Temp  = null
var Netatmo_Prev_In_Temp  = null
var Netatmo_Prev_Indoor_CO2 = null
var Netatmo_Watchdog_Counter = 0

rule "Netatmo watchdog"
    when
	   	Time cron "0 0/10 * 1/1 * ? *"
    then
        if(Netatmo_Outdoor_Temp.state.toString != Netatmo_Prev_Out_Temp || Netatmo_Indoor_Temp.state.toString != Netatmo_Prev_In_Temp || Netatmo_Indoor_CO2.state.toString != Netatmo_Prev_Indoor_CO2)
        {
			Netatmo_Prev_Out_Temp  = Netatmo_Outdoor_Temp.state.toString 
            Netatmo_Prev_In_Temp  = Netatmo_Indoor_Temp.state.toString
            Netatmo_Prev_Indoor_CO2  = Netatmo_Indoor_CO2.state.toString
            Netatmo_Watchdog_Counter=0
        }
        else
        {
			if(Netatmo_Watchdog_Counter>=4)
            {
             sendNotification("xxx@gmail.com", "Neatmo non si aggiorna!")
			 playSound("Netatmo_non_si_aggiorna_consiglio_il_riavvio_manuale.mp3", new PercentType(15))	
		    }
			else
            {
             Netatmo_Watchdog_Counter = Netatmo_Watchdog_Counter + 1
            }
        }
end
2 Likes
39

HI,
I’ve same Issue. I updated the github issue with this info:
https://forum.netatmo.com/viewtopic.php?f=5&t=6912
It seems Netatmo’s API have been changed
:\

40

That is a topic from 2016!

41

sorry, my fault. wrong link.
someone complain last week about netatmo servers and he linked this to the API’s change:
https://forum.netatmo.com/viewtopic.php?f=5&t=14936&start=30

PS: Dim (Angelo) a few post before said same thing. Sorry again.

1 Like
42

After quite 2 days of good working order, today I had to restart the binding 8 times :disappointed_relieved:

43

What I mean, this is non an OH Binding issue
I think are Netatmo’s weather servers fault

I have also two Netatmo thermostats and they working very well

1 Like
44

It is truly a Netatmo issue, still restarting the binding works for a while. It would be wonderful if OH could easily autorestart bindings in these cases.
Failure detection is easily done with the rule I have posted above, I am missing just the autorestart, then we could run through with no sorrows.

45

You can add to your rule a step to restart the bundle using a console command (check the forum for examples, there are some)

If I am not wrong: The binding code already tries to re-connect in case of remote failure but I would expect that it gives up after some number of retries (otherwise you would have a spam of retries).

The latest (03/Dec) report from Netarmo forums is that their downtime was more than 3 hours: Source

Even if you make a rule that restarts the bundle you don’t really want to do this continuously over a 3 hours period…

46

Netamo updates fine here every 10 minutes. There has been a few hickups lately from Netamo and their server. And a few days ago I totally lost all communication to my weather station and module. It turned out to be a new firmware update for the weather station, which for some reason locked the whole system up. After installing that firmware, it has been running fine again.
I use openhab 2.3 stable.

47

Wich firmware do you have now installed (outdoor- and indoor module)?

48

Indoor (station) 137
Outdoor module 46

49

Thanks! I obviously missed some updates. Indoor is 134, outdoor 46 also. But I had no trouble the last days. Perhaps someone (e.g. @deladus) with persisting problems could check his firmware?

50

I believe the weather station should update itself. I have had this station for 1½ year now, and have never done any firmware update manually.
But, as mentioned, a few days ago, I suddenly had to because I lost all communication with the station. When I re-installed the station, it did pop up with a message about a new firmware. After installing that firmware, things has been working just fine again.