"No data" warning

[jsteggall]

I've been running weewx for about a year with using the weewx-weatherlink-live driver (version 1.0.11. Hardware: Vantage Pro2 with indoor & outdoor Airlinks). I've been getting this type of message repeatedly in my /var/log/syslog from the beginning:

WARNING user.weatherlink_live.driver: No data since 2 iterations

Yet, I seem to be collecting data without any apparent problems. After noticing a new version posted (1.1.0), I decided to try upgrading the driver. Couldn't find any documentation on best practices for upgrading the driver so decided to

1. Stop weewx service
2. wee_extension --uninstall=weatherlink-live
3. wee_extension --install=/path-to/weewx-weatherlink-live-release.zip

Had to rename the driver in the weewx.conf file (add "_driver" to "user.weatherlink_live") but weewx seem to restart okay. But, still getting the same "No data" errors in the syslog.

Tried increasing the polling_interval to 20 seconds but that didn't help. Of course, setting log_failure = False stops the syslog entries.

So, is the "Warning: No data" something I can ignore?

BTW, I also occasionally get the following in syslog:

ERROR user.weatherlink_live.davis_http: HTTPConnectionPool(host='weatherlink', port=80): Max retries exceeded with url: /v1/real_time?duration=1500 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f644cab4b20>: Failed to establish a new connection: [Errno 111] Connection refused'))

but I'm guessing that it's a temporary problem relating to glitches in my wifi network.

[michael-slx]

Your update procedure is correct. I don't see any issues there.

The "HTTPConnectionPool" errors can be ignored. If network connectivity is glitchy it will try multiple times.

---

Regarding the "no data" log, that means your WeeWX is not receiving data in time. The messages were probably there from the beginning, just the last update changed the log level so you started seeing them.

I think your WeeWX is not receiving the live data updates every 2.5 seconds. Please take a look at the UDP section of the troubleshooting guide and follow the steps.

Firstly, install netcat. Then, run it as mentioned in the guide.

The exact output isn't important, just that you get a new message every 2.5 seconds.

Judging from your issue, I assume you won't be seeing any messages.

If that's the case, your WeeWX device and your WeatherLinkLive are probably in different Subnets/VLANs. They both have to be in the same subnet as broadcast network messages are only sent within the same subnet.

You wrote you're connected via WiFi. Are both devices connected wirelessly or just one? Maybe try connecting both using the same method.

[jsteggall]

Thanks for the quick reply. I should have mentioned that all devices are on the same local subnet, bridged wifi & ethernet (no VLANS or virtual machines). Actually, the weatherlink-live device is on my house's ethernet and I can ping it. I've been having problems with my network after multiple issues with the local ISP and I suspect that something is misconfigured. I also should have mentioned that I have weewx running on two machines -- a desktop and a laptop, both running the latest Linux Mint OS (21.1).

The curl output for current conditions seems to work fine. "nc -nvulp 22222" produces similar output to the example on the troubleshooting page, but only a single iteration (no output after the first set). Both weewx machines do this.

[michael-slx]

The lack of nc output shows that there's a problem with the network setup as packets aren't coming through.

If I'm understanding you correctly, your WeatherLink is connected wired (Ethernet) and your two WeeWX machines are connected wirelessly. In that case, try connecting both using Ethernet.

If you are using your router as an Ethernet switch, it could also be blocking the packets. In that case, a simple external Ethernet switch would help.

[gary-hammer]

From either of your Pis, or any other computer with a desktop, try this a few times in a browser. Replace the xx with the IP of the WLL
http://xx.xx.xx.xx/v1/current_conditions

If you get data each time you refresh the browser, then move on to requesting live data.
http://xx.xx.xx.xx/v1/real_time

That should give you
{"data":{"broadcast_port":22222,"duration":1369},"error":null}

Now, you can use the python code I'm attaching from CLI to see if and how often the data gets to your machines.
This does require requests to be installed (pip3 install requests) and you should edit the script to set the URL address to your WLL.
You'll need to rename the file as github does not allow .py attachments so it's uploaded as .txt

python3 check_broadcast.py

Then, it is up to your network.
check_broadcast.txt

[jsteggall]

Thanks for all the help. Definitely above and beyond the call troubleshooting my home network!

Note: connecting the laptop to ethernet does not change the "nc -nvulp 22222" output.

Here's what I got with further testing:

http://192.168.88.101/v1/current_conditions
Web browser output updates properly.

http://192.168.88.101//v1/real_time
Web browser output:

data | null
error |  
code | 404
message | "HTTP Page Not Found"

and python code:

$ python3 check_broadcast.py
Output:

Traceback (most recent call last):
File "check_broadcast.py", line 28, in
main()
File "check_broadcast.py", line 13, in main
comsocket.bind(('',22222))
OSError: [Errno 98] Address already in use

The real_time errors seem pretty relevant!

Again, ping finds the weatherlink-live, and here's mtr output:

$ mtr --report weatherlink
Start: 2023-04-19T08:09:31-0700
HOST: XPS-13-9370 Loss% Snt Last Avg Best Wrst StDev
1.|-- weatherlink 0.0% 10 0.2 0.3 0.2 0.4 0.0

[gary-hammer]

You'll have to stop any other device calling for that address from the machine you run the python script on.
Probably have the driver running in weewx.

[jsteggall]

Okay, after I stopped the weewx service on both machines, "nc -nvulp 22222" still gives a single iteration of output but Gary's python script outputs a steady stream of output.

What's the significance to the http://192.168.88.101//v1/real_time webpage showing a 404, page not found?

Again, I'm still getting data into my SQLite database and it displays okay in my Belchertown webpage, and the weatherlink.com webpage for my Vantage Pro2 system. I'm planning to replace my 12 year old router, so maybe that will fix the network glitches.

[gary-hammer]

Well, now I'm confused. You say you get data in WeeWX and it shows in the Belchertown skin. I'd think weatherlink has nothing to do with WeeWX, but I'm uncertain as I just use the local API to get info into WeeWX. My WLL takes care of the weatherlink data itself.

So, I think all is well regardless of the logs. If it is not a constant error and does not affect operations, it's good in my book.
If you have wireless issues (I gave up on RPI 3 and 4 wireless) Either use a small 5 port switch to wire the devices, or get an AP in the same area as the Pi.

[gary-hammer]

What's the significance to the http://192.168.88.101//v1/real_time webpage showing a 404, page not found?

That only starts the API sending data, there is nothing for a browser to see, so 404

[jsteggall]

Thanks for all the help Gary & Michael (and for all your work on the weatherlink-live driver!). Sorry for the confusion on mentioning weatherlink.com -- just wanted to show that my Vantage Pro2 system is sending out data, more or less properly. For the record, the "WARNING user.weatherlink_live: No data since 1 iterations" errors appeared in my syslog regularly well before the recent weatherlink-live driver upgrade. But despite the syslog warnings, data seem to be flowing into the SQLite database so I'll ignore the warnings for now and hope they disappear when I replace my old router.