I thought Last Update was the last time Save was clicked.
If Last Update, 1/15, is the last time Hubitat got data from Netatmo, why are there Event entries dated 3/23?
Hmm, I think you are right .... getting my wires crossed with the Ecowitt integration.
EDIT: There is a "Lastupdate" state that is the last time your Netatmo sent data to the servers. It's not the last time the driver/app got data from Netatmo, that is last activity.
I'm asking because I use 'Device Activity Check' to alert when a device goes offline and I believe it monitors Last Activity - and it appears this driver isn't conforming to the normal usage of this field.
Could the driver be modified such that Last Activity matches Lastupdate?
Yes that shouldn't be hard - Im going away tonight for a week to see family, and I've added it to my "when I get bored" to-do-list. 
1 Like
So thinking about this, Lastupdate does what you want - if your Netatmo goes offline, this won't update until it comes back online. I use this myself with a smart outlet to power cycle it when this happens.
You can test this by pressing the capacitive touch button on top of the main unit, and then hitting refresh in the driver.
The ecowitt weather station driver works the same way:
The 'Device Activity Check' app doesn't check Lastupdate; it checks Last Activity.
My preference is to use a single app (Device Activity Check) to monitor all devices.
To the best of my knowledge, this driver is the only one that doesn't use Last Activity to indicate the last time that the device reported info to the hub.
Ok, I’ll have a look at that app and see what’s it’s looking for.
Most of the weather integrations report Lastupdate as the last time the weather station reported data back to the cloud servers, but I’ll duplicate the state if needed.
Ok, I've released v1.6 with a few bug fixes and a "Last Activity" state mirroring Lastupdate - let me know how this goes for you.
v1.6 - Bug fixes: OAuth token parsing, stray syntax error, capability names, namespace/author update
1 Like
Awesome, thanks! I'll test it out and report back.
If you add importURL to your definition (), the Import Code from Website dialogue will always be populated making manual updates easier:
metadata {
definition (
name: "Netatmo Additional Module",
namespace: "dJOS",
author: "Derek Osborn",
importUrl: "https://raw.githubusercontent.com/dJOS1475/Hubitat_Netatmo/refs/heads/main/Netatmo_Additional_Module_Driver.groovy"
)
1 Like
Ah good point, I have now updated the files with importURL populated.
UGH. This update broke my connection to Netatmo and the Authorize link times out.
Ah crap, I’m out ATM, but I’ll have a look tonight.
It might not be you. I can't get to dev.netatmo or my.netatmo. DNS resolves just fine too. I'm at a loss ATM.
I just checked and mine isn’t updating either, and hasn’t since I made the changes last night.
Oh. Maybe I can put some hair back in then?
Still doesn't explain why I can't get there from my browser on my PC.
1 Like
That is odd, but yeah I clearly broke it without realising it. 
Note to self, don’t attempt to revise code after driving 500 kms. 
1 Like
Looks like it is my firewall killing the connection to dev and auth.
Now to figure out why and allow it.
1 Like
Mine might be doing the same thing. 
I'll cross my fingers on it, but I'm not sure it is. This error is from a FW log entry where I filtered the source traffic as my PC and not the Hubitat.
1 Like
I’ve clearly screwed up the oauth, rather than improving it.