Weatherlink not showing archive related data. **solved**

[staze]

Figured I'd start a new thread for this. Recently got my MB Nano SD uploading to Weatherlink. Works pretty well, but certain data isn't populating. Namely the barometer and windrose. From looking online, these are apparently tied to archive data rather than the live data.

https://www.manula.com/manuals/pws/davi ... leshooting

Specifically:

For example, the wind rose or barometer graph is not displaying. The key here is to remember that two distinct types of data are being uploaded to weatherlink.com: Current conditions data (which provides most of the real-time readings for the Bulletin) and archive data. Graphics like the wind rose and pressure chart are actually sourced from the archive data so in this scenario it is likely that current conditions data is being uploaded correctly but archive data is not.

I don't see any issues with MB. There is a recommendation to reboot the console linked off that page, which I haven't tried, but I wasn't sure if MB negates that recommendation. Looking at the update for adding support, it does look like maybe it's still applicable:

adds support for a new personal weather data upload service named "WL Cloud". This feature is only available for Meteobridges connected to a Davis data logger (Console or Envoy, not Envoy8x). It directly uploads data from the logger (not data from the Meteobridge) to an URL of your liking. Data consists of LOOP, HILOWS and DMPAFT data sets as provided from the Davis logger

Has anyone else seen this? Will gladly reboot my Envoy (firmware 3.15, btw), but I'd like to cleanly shut down my Nano SD first. I actually can't find any way to do that. lol. Oh, think I may have found it. "poweroff" command via ssh. Though maybe not. Seems like it started back up after that.

[staze]

Hmm... came back up, and MB is showing the th0 sensor is out of range.

Second reboot of the MB resolved. That's... odd. Wonder if the Envoy wasn't fully sync'd prior to it providing bad data? Should the delay boot setting be set for situations like this?

Anyway, that SEEMS to have solved the issue. I now see windrose data, and barometer data. And a gigantic buffer out of nowhere (350 items, slowly decreasing). Looks like MB is now sending a bunch of backed up data (judging by the large number of logged entries for WL Cloud).

So... not sure if it was the reboot of the Envoy, or the reboot of the MB (or both) that finally got it going. Is there any way to tell if the MB wasn't receiving some piece of the LOOP2 prior to reboot? Or in the future?

Related: Is it possible to have the MB trigger a console reboot somehow? Also related: I see there's a new firmware out for the Envoy. Is it possible to have the MB push that, or will I need to dig out my old USB logger? If that case, would be good to know a way to get the MB to shutdown and stay down.

Thanks!

[staze]

Just had a realization.

Cloud this be related to the fact I use an external application (Weathercat) that utilizes the weatherlink functionality (port 22222) and that takes over some part of the LOOP process that prevents those records from being uploaded? That would mean console reboots were not what fixed it, but instead quitting Weathercat.

Thanks!

[staze]

Seems like this is the case. While Weatherlink started showing windrose, it's now gone after a day or two and I've had WC running. Suppose that makes sense.

Guess this is one more reason to stop using LOOP2 integration. =/

[admin]

Forcing Meteobridge into slave mode by taking over with a PC program on port 22222 will indeed impact Weatherlink data. I think that is the root cause.

Good finding by the way... I did not thought this direction.

[staze]

Yup. stopped using WC a few weeks ago, and Davis Weatherlink now works. =)