Yeah, probably was overthinking it a little, KISS is always a good approach.
And in the end, if the hub is offline for a period or does not have the data feeding through, there's not much I can do about it. That said, I might include a data value to record the date/time of the last overnight reset, so if the hub is offline overnight and comes back online I will perform the reset, otherwise will wait for the next scheduled reset at 12:01am.
I think that a logical approach. I’m not sure I’d worry about hubs going offline, ppl have bigger issues to worry about if that happens.
True, it is only a nice thing to have (min's / max's) for display, can't imagine too many automations driven off them.
I can, I use the days maximum temp, combined with the forecast overnight low, to determine if my upstairs reverse cycle AC should be in heat, cool or Auto mode.
Then I think I might at least put the check on the to-do list, but perhaps start with the simpler option you described.
Cheers, much appreciated.
Then I can decommission the rest of my Netatmo PWS.
1.34.08 and 1.34.09 Updates
1.34.08 - Wittboy Battery Readings and Firmware
Thanks to @xcguy for his work on changes relating to Wittboy weather stations. For users of these weather stations (not other EcoWitt weather stations):
1.34.09 - Unrecognized Attributes - Runtime, DateUTC and gain30_piezo
When turning on Debug or Trace logging, for a long time now entries would appear in the HE logs indicating unrecognized attributes were found in the data feed. These are now being dealt with.
My Ecowitt GW2000 updated to GW2000B_V3.0.7 last night. I can look under the app and Live Data and see the sensors. But the sensors are not reporting on Hubitat. I just update the driver to the new version in HPM, but that doesn't seem to have helped.
So the sensors were reporting to Hubitat prior to the firmware update on the gateway? Try turning on Trace / Debug logging on the gateway device in HE, then monitor the logs in HE.
Also, confirm the data feed is still configured in the EcoWitt app on your phone / tablet.
Feeling stupid but I don't see where to turn on Trace/Debug logging in HE.
The router appears to be still configured in the app on my phone.
No worries, I probably should start referring to it as the Log Verbosity. It's in the Preference Settings of the Gateway device.
Do you get a station type at the start of the trace logs? Oh and thanks for checking on these.
Yeah, I know. In my thermostat driver I am considering taking the setting out of the parent device and placing it into each child device, but in that instance the child devices operate mostly independently of one another. In the EcoWitt drivers most things, i.e. the data, are funneled through the gateway driver, with just the values passed down to each sensor device to be recorded, so it kind of makes more sense to manage and record the logging through the parent device.
Ok, cool. That confirms that the gateway version (the V3.0.7 in the stationtype value) and the Wittboy weather station firmware version (the 126 in ws90_ver) are two separate things. So recording the firmware version on the weather station device was the right place to record it, and not just a change in the way Wittboy data was being captured.
Now I've discovered that there's a firmware update, I'm going to update the firmware in the Witboy. 
You dont need the gw2000 ypu can use any receiver i have the gw1100b for my wittboy
I havent updated drivers as id have to integrate
As i have some custom attributes to keep track of individual sensors that get orphaned such as rain,wind that when bundled are not normally tracked.
Obviously i also have 4 other multichannel temp/humitidy that are reporting in the above dump.
That's fine. It's only if you need the changes, and even then, I'm sure you could merge them into your own if you needed to.
