Desktop or phone app: Can click on someone else's station and change there displays.
What do you mean by change their displays?
Change graph settings and hide tiles. I'm assuming this only effects my view and not there's.
Ah, this will be the problem. And one I can solve.
Like you have seen, all the main features of the driver work without an Internet connection, receiving data from the EcoWitt Gateway locally and processing it. There is a feature that aims (at least I expect this is the intention) to provide an alternative method to find out there is an update available for the drivers on GitHub. Your Gateway device in HE records the driver version, like I showed in my screenshot, then a periodic check (once a day) which calls out to my GitHub repo to check the version currently available there, comparing that to the local version recorded on your HE hub. If it can't call out to my GitHub repo, then this driver version will likely never have been created in the first place, and so the check that happens each time new data is being parsed will produce the error you are seeing in the logs. Note, the check each time data is processed is not calling out to my repo, this is still all happening locally, it is the initial creation of the driver attribute that is affected, which then has the flow-on effect of the local check failing.
I'll need to think about it a bit, but should be able to come up with something relatively easily.
If you want to stop the error from occurring, you can comment out the line of code in the gateway driver, changing lines 1246 - 1251 from:
// If the driver has been updated on the HE hub, check that this is reflected in the driver attribute
// If not, run the version update to record the correct details
if(!(device.currentValue("driver").startsWith(versionExtract(version()).desc))) {
logDebug("Driver on HE Hub updated, running versionUpdate() to update the driver attribute");
versionUpdate();
}
to
// If the driver has been updated on the HE hub, check that this is reflected in the driver attribute
// If not, run the version update to record the correct details
//if(!(device.currentValue("driver").startsWith(versionExtract(version()).desc))) {
//logDebug("Driver on HE Hub updated, running versionUpdate() to update the driver attribute");
//versionUpdate();
//}
It may be worth posting / searching on the EcoWitt forum, unless someone else is familiar with it... I haven't used the EcoWitt App myself.
I have only used Ecowitt’s WS view app, so I can’t say from personal experience. But I very much doubt you’re changing anything other than your own view of the data other weather stations are exporting.
1 Like
Actually, I see it now, it's available on the EcoWitt.net site as well. Not sure to tbh about updating other's view, but I would be surprised if that was the case.
@ShaneAllen - I have released an update this morning to (hopefully) resolve your issue of not having an Internet connection to your hub, and the complications this caused with how the driver treated checks for updates on my Github repository. In short, when you have some time, and access to your hub, can you please update the gateway driver code, and turn off the new setting I refer to below.
For anyone else, this release should not introduce any change in behaviour, but if you notice anything, please let me know.
Read on if you are interested in what the change is all about...
The gateway device includes a driver attribute in the current states, showing both the current driver version being used on the HE hub, plus an optional indicator for any updates available in the Github repository, e.g.:
This release (1.34.12 and 1.34.13) introduces a new Preference Setting for the gateway device on HE, allowing control of whether to monitor the Github repository for any driver updates. The calls out to Github normally occur on a Sunday at 2am, plus any time the Preference Settings are saved. If the new setting is turned on (the default setting), these checks will continue to occur as they have done in the past. If this setting is turned off, these checks of Github will not happen, and the driver attribute will simply store the current version recorded in the driver code currently installed on the HE hub.
@ShaneAllen - While I said earlier that the checks of GitHub would normally only occur once a week and when settings are updated, in your case, the combination of an additional version check that is done each time a data feed is processed, plus the fact the driver attribute was likely not recorded on your gateway device, meant that, under the old driver, an attempt was being made to check GitHub each time a data feed was being processed. This situation is now being handled by the driver and won't call out to Github if you turn off the new preference setting for monitoring Github.
@sburke781 Thank you for the quick response, and taking care of this for me. The updated driver corrected the problem!
Much appreciation
1 Like
Just took delivery of a WittFlow smart tap timer. What would be involved in getting it controllable from Hubitat?
Sorry @steve007 , I saw this then forgot to get back to it. I had seen they thad released this, looks interesting. I'm not sure at this stage what options there may be to control it, I will need to do some investigation.
I was curious to see how close I could get to one of these tiles using Tile Builder Grid. This is what I came up with, its 888 bytes.
3 Likes
Are those values fixed (to do the prototype), or are you also calculating the high's and low's?
They are just values pulled from a device.
I don't know whether to be more envious of the great looking, highly functional tile you created, or the fact that you're reporting those temps in Celsius and I'm living through the same values in Fahrenheit. But seriously, nice work. Very similar to what one gets directly from the Ecowitt app, which I really like.
3 Likes
Not sure if it’s related, but the last few weeks, I’ve been getting the following error message from the parent Ecowitt device in my logs:
exception in versionupdate(): java.net.socketexception: connection timed out (read failed)
I don’t see any resulting problematic behavior with the device. I had left the Monitor Git Driver Version set to ON since I have cloud connectivity and rely on HPM to get periodic driver updates. My driver is 1.34.13 and firmware 3.0.8.
Thoughts?
Hi Mark,
I'll try and take a look at this for you tomorrow.
1 Like
I'd like to make a clarification of an observation of my little console, WN1980, during a recent power outage.
Yes, it did keep WiFI communication running, but for only a pretty short time.
WiFi router was on battery so it was running. Perhaps if it too was without power, the console's batteries would've lasted longer.
Now, I did not check the battery voltage (on the app only) either; actually I've never. So, I don't know where it started.
I think it sends readings every minute.
@sburke781 - I log all my error messages and I can see the same message going back to 20222 (only once) but lately this has been much more frequent (at least once per day or every other day). Let me know if you want exact numbers or frequency.
Thanks. This will be more likely something I look at over the weekend. May be useful to know what version of the drivers you are running.
