Davis WeatherLink Live plugin

I uploaded the latest version of Weatherlink plugin but still get the same error. In Indigo I can see it is receiving the correct data from the weather station.

Any ideas?

Not a clue. I've never tried to use weather data with Siri.

Just to clarify, Siri just gets it from the Home app and simple announces the data passed from the plugin.

OK, I've never done anything with weather stations and HomeKit.

It's coming in via Davis Weatherlink, see page 2 -3 of this thread.

This is not going to work going back and forth on the forums. Please open an issue on GitHub, and explain exactly what you changed, and what changed in your plugin devices.

https://github.com/FlyingDiver/Indigo-W ... ive/issues

I can work on issues with the WLL plugin, and any issues using Masquerade to make specific sensor devices. If those are all working properly, and it's just an issue with getting HKB to publish the sensors to HomeKit, I can't help.

This is great, just what I was looking for. Have had a VantageVue for awhile now and recently added the WeatherLink Live due to adding sensors for air quality (AirLInk). I've been using WeatherSnoop to send data to Wunderground and others but it does not include air quality data. Is this something you might consider adding?

Davis does not include the ability to send .xml and .jason files via. FTP... adding this would be icing on the cake so as to style ourselves on a website.

https://www.weatherlink.com/embeddablePage/show/c37b5fe3b2d1400ba92fd2302e063a88/summary

This is great, just what I was looking for. Have had a VantageVue for awhile now and recently added the WeatherLink Live due to adding sensors for air quality (AirLInk). I've been using WeatherSnoop to send data to Wunderground and others but it does not include air quality data. Is this something you might consider adding?

I don't have an AQ sensor, so I've never been able to write any code for it. Maybe I'll get one.

Best thing to do would be to create an issue in GitHub with your request.
Run this menu command and include the results in the issue:

Screen Shot 2021-06-04 at 8.03.40 AM.png (183.31 KiB) Viewed 4818 times

Davis does not include the ability to send .xml and .jason files via. FTP... adding this would be icing on the cake so as to style ourselves on a website.

I don't think I understand this request. Send which files to where? And when? The upload protocols to all the services the plugin supports are defined by the service. None of them include uploading static files anywhere. Open a separate issue for this, and give specific examples of where the files are coming from, and where they need to go. Note that there's already an FTP plugin for uploading files to FTP servers by Indigo.

https://github.com/FlyingDiver/Indigo-W ... ive/issues

Hmm. Maybe never mind. I just grabbed the User's Manual for the AirLink and it's not going to work.

The plugin communicates directly with the WeatherLink Live on your local network. No cloud connection. It can get the data from any sensor that is paired with the WLL box, usually an ISS and the sensors inside the WLL itself. It also supports moisture sensors that are reporting directly to the WLL.

The AirLink has NO connection to the WLL. It reports directly to the Davis cloud servers via Wifi. So it sort of runs in parallel to the WLL. So the WLL plugin has no way to communicate with it.

However, it appears that the AirLink has it's own local API (https://weatherlink.github.io/airlink-local-api/). Hmm. Maybe there's a way to do both. That'll require some research.

Although it appears to not be needed due to AirLink writing directly to the cloud, this is what I get when running "Write known devices to log" using your plug-in.

Code: Select all

Jun 4, 2021 at 10:07:06 AM
   WeatherLink Live                Known device list:
{'409841': {'type': '3', 'lsid': '409841'}, '409843': {'type': '1', 'lsid': '409843'}, '409842': {'type': '4', 'lsid': '409842'}}


The FTP upload is a feature from the WeatherSnoop Agent along with WU, WeatherBug, WOW, PWS...etc. It allows you to send to a sever/subfolder that you have access. An example of the .xml file generated that I publish is: https://www.alaskafamily.net/weather/weather.xml
I have WeatherSnoop running from my IP Datalogger which is apparently now discontinued, which does not include air quality data.

The only issue is that it does not include the air quality data, perhaps due to the reason you indicated is that it writes directly to their cloud. I was hoping to find a way to collect all data and then publish a .json file or .xml file that then could be styled for a website rather than using the widgets Davis provides.

OK, the Type 1 device is the ISS, Type 3 is the WLL barometric sensor, and Type 4 is the WLL temperature sensor. Why the WLL has two different internal devices is a mystery. FYI, Type 2 is the Leaf/Soil Moisture sensor. AQ sensors are Type 5 (older firmware) or Type 6 (current firmware).

I have the AirLink on order. I'll be able to try it out this weekend, I think. In the meantime, an interesting experiment would be to create a second WeatherLink device but give it the IP address of the AirLink. You might actually get valid data.

The only issue is that it does not include the air quality data, perhaps due to the reason you indicated is that it writes directly to their cloud. I was hoping to find a way to collect all data and then publish a .json file or .xml file that then could be styled for a website rather than using the widgets Davis provides.

Hmm. Once I actually have the AirLink working, it should be a fairly trivial Python script to collect the data you want from the different devices and generate JSON data. Then you could upload it from the Python script or use the FTP plugin to do it.

Great to hear on the senor.

I tried adding a new device for the AirLink (using Fing to find IP address) and the state results in an HTTP Error followed by JSON error. When I ping the IP or look for open ports using the IP address of the AirLink I don't get any results.

Log when restarting plug-in:

Code: Select all

Comm(WeatherLink AirLink): 1179749524
   WeatherLink Live                Shutting down WeatherLink Live
   Stopped plugin "WeatherLink Live 0.2.0"
   Starting plugin "WeatherLink Live 0.2.0" (pid 63771)
   Started plugin "WeatherLink Live 0.2.0"
   WeatherLink Live                Starting WeatherLink Live
   WeatherLink Live                WeatherLink Live: Polling WeatherLink Live
   WeatherLink Live                WeatherLink AirLink: Polling WeatherLink Live
   WeatherLink Live Error          WeatherLink AirLink: http_poll RequestException: HTTPConnectionPool(host='192.168.1.88', port=80): Max retries exceeded with url: /v1/current_conditions (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x10cccc790>, 'Connection to 192.168.1.88 timed out. (connect timeout=3.0)'))
   WeatherLink Live Error          WeatherLink AirLink: udp_start() RequestException: HTTPConnectionPool(host='192.168.1.88', port=80): Max retries exceeded with url: /v1/real_time (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x10cccc8d0>, 'Connection to 192.168.1.88 timed out. (connect timeout=3.0)'))

Huh. The docs say that first request should work. Well, I'll play with it when my unit arrives.

Pre-release 0.3.0: https://github.com/FlyingDiver/Indigo-W ... /tag/0.3.0

Support for Davis AirLink devices. Create device with IP address of the AirLink.

This version does not include AQ information in uploads to weather collection sites. I need to see which sites support it.

Hi, I have been running the WLLIve plugin for quite some time now and here lately it has been giving me:

WeatherLink Live Error Davis WeatherLink Live Base: http_poll RequestException: HTTPConnectionPool(host='192.168.0.225', port=80): Read timed out.

I'm not sure what to make of this, since my triggers seem to continue to work, and everything usually appears OK, although sometime the sensor in Indigo
seems to have a lapse in updating.

Any thoughts?

Many thanks,
Greg