Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4017) - 17 March 2024

Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

AirLink In/Out.

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

User avatar
mcrossley
Posts: 12689
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: AirLink In/Out.

Post by mcrossley »

It is running discovery twice, once for indoor, the again for outdoor - they get loaded as independent instances.

For indoor which gets a valid discovery message you get...

Code: Select all

2021-10-01 09:59:09.392 Extra Sensor = Davis AirLink (Indoor) - stand-alone=True
2021-10-01 09:59:09.490 ZeroConf Service: Attempting to find AirLink via zero-config...
2021-10-01 09:59:09.952 ZeroConfig Service: AirLink found 'DeWilgenEsp', reporting its IP address as: 192.168.178.221
2021-10-01 09:59:10.490 ZeroConf Service: Auto-discovery found the AirLink, reporting its IP address as: 192.168.178.221
Everything works.

For outdoor which does not respond to discovery you get...

Code: Select all

2021-10-01 09:59:10.493 Extra Sensor = Davis AirLink (Outdoor) - stand-alone=True
2021-10-01 09:59:10.499 ZeroConf Service: Attempting to find AirLink via zero-config...
2021-10-01 09:59:10.738 ZeroConfig Service: AirLink found 'DeWilgenEsp', reporting its IP address as: 192.168.178.221
2021-10-01 09:59:11.499 ZeroConf Service: *** Discovered more than one potential AirLink device.
2021-10-01 09:59:11.500 ZeroConf Service: *** Please select the Host name/IP address from the list and enter it manually into the configuration
2021-10-01 09:59:11.500 ZeroConf Service: *** Discovered AirLinks = DeWilgenEsp/192.168.178.221 
The message "Discovered more than one potential AirLink device" is wrong, I had already fixed that for 3.13.4 to read "Discovered one or more potential AirLink devices" Note potential, MX does not know what to use so leaves it up to you.

v3.13.4 also honours disabling auto-discovery for both AirLinks and WLL devices.
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: AirLink In/Out.

Post by HansR »

OK, that should be better.

But if I have an IP and a hostname you could also give a message that you are using that as an AirLink. Now it comes up the second time with the first IP/Hostname and says I must fill in the correct parameters which has already been done. Because I filled it in MX DOES KNOW what to use.

But anyway... It works.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
Phil23
Posts: 884
Joined: Sat 16 Jul 2016 11:59 pm
Weather Station: Davis VP2+ & GW1000 (Standalone)
Operating System: Win10 Pro / rPi Buster
Location: Australia

Re: AirLink In/Out.

Post by Phil23 »

Don't know if it's relevant, but is there anything to be gained by pulling the "Did" & "Name" from a device when it's detected for identification purposes.
Not sure that I consider my "Name" in the a Airlink to be that valid, but the AQM names have a better relevance.

The Jsons from my 3 devices.
{ "data": { "did": "001D0A1001B0", "name": "Inverell", "ts": 1633120362, "conditions": [{ "lsid": 361501, "data_structure_type": 6, "temp": 50.8, "hum": 84.9, "dew_point": 46.4, "wet_bulb": 48.3, "heat_index": 50.8, "pm_1_last": 17, "pm_2p5_last": 22, "pm_10_last": 26, "pm_1": 9.72, "pm_2p5": 13.19, "pm_2p5_last_1_hour": 10.98, "pm_2p5_last_3_hours": 6.80, "pm_2p5_last_24_hours": 10.31, "pm_2p5_nowcast": 7.95, "pm_10": 15.54, "pm_10_last_1_hour": 12.94, "pm_10_last_3_hours": 8.05, "pm_10_last_24_hours": 12.02, "pm_10_nowcast": 9.43, "last_report_time": 1633120362, "pct_pm_data_last_1_hour": 100, "pct_pm_data_last_3_hours": 100, "pct_pm_data_nowcast": 100, "pct_pm_data_last_24_hours": 100 }] }, "error": null }
{"data":{"did":"001D0A100021","name":"AQM-III_Outdoor","ts":1633120298,"conditions":[{"lsid":0,"data_structure_type":6,"temp":67.73,"hum":44.01367,"dew_point":45.02713,"wet_bulb":54.96626,"heat_index":67.73,"pm_1_last":5.772875,"pm_2p5_last":6.104597,"pm_10_last":6.104597,"pm_1":5.772875,"pm_2p5":6.104597,"pm_2p5_last_1_hour":5.177411,"pm_2p5_last_3_hours":4.442666,"pm_2p5_last_24_hours":39.9524,"pm_2p5_nowcast":3.8,"pm_10":6.104597,"pm_10_last_1_hour":5.224448,"pm_10_last_3_hours":4.555088,"pm_10_last_24_hours":44.67476,"pm_10_nowcast":3.9,"last_report_time":1633120298,"pct_pm_data_last_1_hour":100,"pct_pm_data_last_3_hours":100,"pct_pm_data_nowcast":100,"pct_pm_data_last_24_hours":100}]},"error":0}
{"data":{"did":"001D0A100021","name":"AQM-III_Indoor","ts":1633120398,"conditions":[{"lsid":0,"data_structure_type":6,"temp":64.88754,"hum":50.23879,"dew_point":45.92104,"wet_bulb":54.03717,"heat_index":64.88754,"pm_1_last":4.304328,"pm_2p5_last":5.536955,"pm_10_last":6.493855,"pm_1":4.304328,"pm_2p5":5.536955,"pm_2p5_last_1_hour":4.918017,"pm_2p5_last_3_hours":4.356451,"pm_2p5_last_24_hours":16.65969,"pm_2p5_nowcast":4.1,"pm_10":6.493855,"pm_10_last_1_hour":5.234211,"pm_10_last_3_hours":4.644019,"pm_10_last_24_hours":20.23073,"pm_10_nowcast":4.3,"last_report_time":1633120398,"pct_pm_data_last_1_hour":100,"pct_pm_data_last_3_hours":100,"pct_pm_data_nowcast":100,"pct_pm_data_last_24_hours":100}]},"error":0}
And having just posted those strings, I now notice that the did is the same in the two Duino devices.
I was assuming it was a MAC.
:Now: :Today/Yesterday:

Image

Main Station Davis VP2+ Running Via Win10 Pro.
Secondary Stations, Ecowitt HP2551/GW1000 Via rPi 3 & 4 Running Buster GUI.
:Local Inverell Ecowitt Station: :Remote Ashford Ecowitt Station:
User avatar
mcrossley
Posts: 12689
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: AirLink In/Out.

Post by mcrossley »

The DID should be a unique identifier - it is generated by wl.com when the sensor is added - but it is not used by auto-discovery. That uses the host name, the AirLinks host name does incorporate the MAC address (or at least part of it) so it is unique and can be used by MX to identify the specific device.

I do not use the DID with AirLinks, but do use the LSID when talking to wl.com to sort out which is what!
ibucdi
Posts: 2
Joined: Tue 19 Oct 2021 7:36 am
Weather Station: AirLink
Operating System: Win 10

Davis AirLink Settings in Cumulus

Post by ibucdi »

Hi there,
I am a very beginner to use cumulus.
I would like to use cumulus to collect data from Davis Airlink (Air Quality Sensor) only without connected to its weather station, so how can I do in the cumulus settings page?
There is no Davis Airlink option when I want to enter the station type in settings.
or I must connect to Davis Vantage weather station and then connect Airlink?
Much appreciate if anyone can help!
Post Reply