Integrating AirLink - no sensor data

[thunderstorm]

Hi,
I got my airlink today and added it as station #2 (#1 is my DYI particle sensor using a plugin).
I can access my airlink through the local IP (http://<ip>/v1/current_conditions), but my nano-sd is not showing any values from the airlink.

I tried the poor men's fix and rebooted my nano-sd, but no success.

Anything I can do to check or any idea how I can get it working ?

Thanks
Bernd

Screenshot 2020-09-24 at 16.51.52.png (160.98 KiB) Viewed 4273 times

Screenshot 2020-09-24 at 16.53.17.png (135.84 KiB) Viewed 4273 times

Code: Select all

test5m (24.09.2020 16:40:42): weathernet daemon stalled, will be restarted now.
wnetd  (24.09.2020 16:40:42): process started.
test5m (24.09.2020 16:40:42): logger stalled, will be restarted now.
system (24.09.2020 16:40:42): stop of logging process initiated.
wnetd  (24.09.2020 16:40:42): send data thread started (pid:1967 tid:1968)
database (24.09.2020 16:40:47): process started.
database (24.09.2020 16:40:47): Content of RAM database restored.
system (24.09.2020 16:40:51): start of logging process initiated.
logger (24.09.2020 16:40:52): databases connected. Update interval 3600 seconds.
logger (24.09.2020 16:40:52): data logger (version 5.1d, build 3369) started.
logger (24.09.2020 16:40:53): connect station 0 (Vantage via USB serial).
logger (24.09.2020 16:40:53): connect station 1 (User-defined via Plug-in).
logger (24.09.2020 16:40:53): connect station 2 (AirLink via SW Driver).
logger (24.09.2020 16:40:53): connect station 9 (System Data via Plug-in).
logger (24.09.2020 16:40:53): station 0 (Vantage), wakeup sent.
logger (24.09.2020 16:40:55): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (24.09.2020 16:40:55): services paused.
logger (24.09.2020 16:40:55): station 0 (Vantage), no need to update console date/time.
logger (24.09.2020 16:40:55): station 0 (Vantage), setup script executed.
logger (24.09.2020 16:40:55): station 0 (Vantage), internal logger activated.
logger (24.09.2020 16:40:56): station 0 (Vantage), syncing.
logger (24.09.2020 16:41:06): station 0 (Vantage), gettime request sent.
logger (24.09.2020 16:41:06): station 0 (Vantage), no Vantage time offset.
logger (24.09.2020 16:41:06): station 0 (Vantage), eeprom request sent.
logger (24.09.2020 16:41:06): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (24.09.2020 16:41:06): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (24.09.2020 16:41:06): station 0 (Vantage), firmware version request sent.
logger (24.09.2020 16:41:06): station 0 (Vantage), firmware version 3.15 (supports LOOP2)
logger (24.09.2020 16:41:06): station 0 (Vantage), no reading of Vantage's internal logger.
database (24.09.2020 16:41:08): database sync done (33 tables, 108/2640 writes).
logger (24.09.2020 16:41:10): sensors are now providing data.
logger (24.09.2020 16:41:10): services started.

[admin]

When IP is correct it should work, at least it does for others.
If you send remote access credentials to "info(at)meteobridge.com" I can have a closer look.

[admin]

BTW, can you please post a current_condition JSON sample? There might a syntax change regarding old and new firmware versions - when I remember correctly. I would like to rule out any incompatibilities on that side first.

[thunderstorm]

Here's the output of my current conditions

Code: Select all

{ "data": { "did": "001D0A10015F", "name": "Partikel", "ts": 1601126904, "conditions": [{ "lsid": 349259, "data_structure_type": 6, "temp": 41.7, "hum": 96.5, "dew_point": 40.8, "wet_bulb": 41.3, "heat_index": 41.9, "pm_1_last": 0, "pm_2p5_last": 0, "pm_10_last": 0, "pm_1": 0.00, "pm_2p5": 0.00, "pm_2p5_last_1_hour": 0.00, "pm_2p5_last_3_hours": 0.01, "pm_2p5_last_24_hours": 0.40, "pm_2p5_nowcast": 0.03, "pm_10": 0.00, "pm_10_last_1_hour": 0.08, "pm_10_last_3_hours": 0.26, "pm_10_last_24_hours": 0.69, "pm_10_nowcast": 0.23, "last_report_time": 1601126904, "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 }

[jasonmfarrow]

Here's the output of my current conditions

Code: Select all

{ "data": { "did": "001D0A10015F", "name": "Partikel", "ts": 1601126904, "conditions": [{ "lsid": 349259, "data_structure_type": 6, "temp": 41.7, "hum": 96.5, "dew_point": 40.8, "wet_bulb": 41.3, "heat_index": 41.9, "pm_1_last": 0, "pm_2p5_last": 0, "pm_10_last": 0, "pm_1": 0.00, "pm_2p5": 0.00, "pm_2p5_last_1_hour": 0.00, "pm_2p5_last_3_hours": 0.01, "pm_2p5_last_24_hours": 0.40, "pm_2p5_nowcast": 0.03, "pm_10": 0.00, "pm_10_last_1_hour": 0.08, "pm_10_last_3_hours": 0.26, "pm_10_last_24_hours": 0.69, "pm_10_nowcast": 0.23, "last_report_time": 1601126904, "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 }

I think the raw data is showing that you have really clean air? *OR* the AirLink has stopped recording particles (despite the 100% data record) and the 3-hr and 24-hr averages are now decreasing as a result. Have you verified whether the unit is defunct?

[thunderstorm]

It's working and I see the data in weather-link.

Code: Select all

{ "data": { "did": "001D0A10015F", "name": "Partikel", "ts": 1601287871, "conditions": [{ "lsid": 349259, "data_structure_type": 6, "temp": 49.9, "hum": 82.6, "dew_point": 44.8, "wet_bulb": 47.0, "heat_index": 49.9, "pm_1_last": 11, "pm_2p5_last": 13, "pm_10_last": 13, "pm_1": 10.52, "pm_2p5": 12.71, "pm_2p5_last_1_hour": 15.16, "pm_2p5_last_3_hours": 11.33, "pm_2p5_last_24_hours": 10.26, "pm_2p5_nowcast": 12.30, "pm_10": 13.42, "pm_10_last_1_hour": 17.66, "pm_10_last_3_hours": 12.92, "pm_10_last_24_hours": 11.76, "pm_10_nowcast": 14.18, "last_report_time": 1601287871, "pct_pm_data_last_1_hour": 100, "pct_pm_data_last_3_hours": 100, "pct_pm_data_nowcast": 42, "pct_pm_data_last_24_hours": 21 }] }, "error": null }

And yes, yesterday and the day before it was very clean

[Taralas]

I seem to be in the same boat. From the API:

Code: Select all

{ "data": { "did": "001D0A10026D", "name": "Indoor", "ts": 1601302748, "conditions": [{ "lsid": 350246, "data_structure_type": 6, "temp": 61.3, "hum": 70.0, "dew_point": 51.4, "wet_bulb": 54.8, "heat_index": 60.6, "pm_1_last": 1, "pm_2p5_last": 2, "pm_10_last": 2, "pm_1": 1.91, "pm_2p5": 1.97, "pm_2p5_last_1_hour": 2.86, "pm_2p5_last_3_hours": 2.86, "pm_2p5_last_24_hours": 2.86, "pm_2p5_nowcast": 2.86, "pm_10": 3.41, "pm_10_last_1_hour": 3.45, "pm_10_last_3_hours": 3.45, "pm_10_last_24_hours": 3.45, "pm_10_nowcast": 3.45, "last_report_time": 1601302748, "pct_pm_data_last_1_hour": 53, "pct_pm_data_last_3_hours": 17, "pct_pm_data_nowcast": 4, "pct_pm_data_last_24_hours": 2 }] }, "error": null }

And Logger output:

Code: Select all

database (28.09.2020 09:06:53): process started.
database (28.09.2020 09:06:53): Content of RAM database restored.
database (28.09.2020 09:07:29): database sync done (37 tables, 5/2924 writes).
wnetd  (28.09.2020 09:07:31): process started.
system (28.09.2020 09:07:31): start of logging process initiated.
wnetd  (28.09.2020 09:07:31): send data thread started (pid:2101 tid:2102)
logger (28.09.2020 09:07:32): databases connected. Update interval 3600 seconds.
logger (28.09.2020 09:07:32): data logger (version 5.1d, build 3378) started.
logger (28.09.2020 09:07:33): connect station 0 (Vantage via serial).
logger (28.09.2020 09:07:33): connect station 1 (AirLink via SW Driver).
logger (28.09.2020 09:07:33): connect station 9 (System Data via Plug-in).
logger (28.09.2020 09:07:34): station 0 (Vantage), wakeup sent.
logger (28.09.2020 09:07:36): station 0 (Vantage), no need to update console date/time.
logger (28.09.2020 09:07:36): station 0 (Vantage), setup script executed.
logger (28.09.2020 09:07:36): station 0 (Vantage), internal logger activated.
logger (28.09.2020 09:07:36): station 0 (Vantage), syncing.
logger (28.09.2020 09:07:37): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (28.09.2020 09:07:37): services paused.
logger (28.09.2020 09:07:46): station 0 (Vantage), gettime request sent.
logger (28.09.2020 09:07:46): station 0 (Vantage), no Vantage time offset.
logger (28.09.2020 09:07:46): station 0 (Vantage), eeprom request sent.
logger (28.09.2020 09:07:46): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (28.09.2020 09:07:46): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (28.09.2020 09:07:46): station 0 (Vantage), firmware version request sent.
logger (28.09.2020 09:07:46): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (28.09.2020 09:07:46): station 0 (Vantage), no reading of Vantage's internal logger.
logger (28.09.2020 09:07:50): sensors are now providing data.
logger (28.09.2020 09:07:50): services started.
system (28.09.2020 09:20:29): Access point operation disabled 917 secs after boot.
system (28.09.2020 09:22:15): stop of logging process initiated.
logger (28.09.2020 09:22:15): parent process received termination signal (15).
logger (28.09.2020 09:22:15): child process received termination signal (15).
logger (28.09.2020 09:22:15): disconnect station 0 (Vantage): exit
logger (28.09.2020 09:22:15): disconnect station 1 (AirLink): exit
logger (28.09.2020 09:22:15): disconnect station 9 (System Data): exit
system (28.09.2020 09:22:16): start of logging process initiated.
logger (28.09.2020 09:22:16): databases connected. Update interval 3600 seconds.
logger (28.09.2020 09:22:16): data logger (version 5.1d, build 3378) started.
logger (28.09.2020 09:22:16): error (22) while doing bind (port 22222): Invalid argument
logger (28.09.2020 09:22:17): data logger stopped.
logger (28.09.2020 09:22:17): databases disconnected.
logger (28.09.2020 09:22:17): parent process to be terminated.
logger (28.09.2020 09:22:46): databases connected. Update interval 3600 seconds.
logger (28.09.2020 09:22:46): data logger (version 5.1d, build 3378) started.
logger (28.09.2020 09:22:47): connect station 0 (Vantage via serial).
logger (28.09.2020 09:22:47): connect station 1 (AirLink via SW Driver).
logger (28.09.2020 09:22:47): connect station 9 (System Data via Plug-in).
logger (28.09.2020 09:22:47): station 0 (Vantage), wakeup sent.
logger (28.09.2020 09:22:49): station 0 (Vantage), no need to update console date/time.
logger (28.09.2020 09:22:49): station 0 (Vantage), setup script executed.
logger (28.09.2020 09:22:49): station 0 (Vantage), internal logger activated.
logger (28.09.2020 09:22:49): station 0 (Vantage), syncing.
logger (28.09.2020 09:22:50): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (28.09.2020 09:22:50): services paused.
logger (28.09.2020 09:22:59): station 0 (Vantage), gettime request sent.
logger (28.09.2020 09:22:59): station 0 (Vantage), no Vantage time offset.
logger (28.09.2020 09:22:59): station 0 (Vantage), eeprom request sent.
logger (28.09.2020 09:22:59): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (28.09.2020 09:22:59): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (28.09.2020 09:22:59): station 0 (Vantage), firmware version request sent.
logger (28.09.2020 09:22:59): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (28.09.2020 09:22:59): station 0 (Vantage), no reading of Vantage's internal logger.
logger (28.09.2020 09:23:03): sensors are now providing data.
logger (28.09.2020 09:23:03): services started.

[thunderstorm]

Seems to work with the Meteobridge 4.4 (Sep 29 2020, build 3407) release

Screenshot 2020-09-29 at 19.33.39.png (252.89 KiB) Viewed 4110 times

Thanks for fixing

Bernd

[Taralas]

Screenshot 2020-09-29 130517.jpg (45.31 KiB) Viewed 4107 times

No joy on my end. I don't know if this version should be enumerating the new Station, but it doesn't seem to be doing so.

[admin]

The beta "thunderstorm" is testing with will soon be released.

[jasonmfarrow]

My Airlink arrived today. Sensor is detected but no data on the Meteobridge.
SW Version: Meteobridge 4.4 (Sep 26 2020, build 3378)

Clearly I'm waiting for build 3407 or better as well to get this working.

[admin]

New version is out. Please give it a try.

[jasonmfarrow]

The sensor is now collecting data. SW Version: Meteobridge 4.4 (Oct 2 2020, build 3436), FW 1.4

However the mapping of the Airlink physical sensors to the logical air quality sensor is the reverse of what I expected:

Capture3.PNG (20.76 KiB) Viewed 4052 times

The Airlink has PM_1, PM_2.5 and PM_10 in that order but the logical has air0pm as PM_10, air1pm as PM_2.5 and air2pm as PM_1.
I'm hoping that this is as designed for some reason or are air0pm and air2pm logical sensor descriptions the wrong way round?

Like the others with a new Airlink i'm mostly getting zero values at present so it's difficult to tell, compared to the live data, where the truth lies.

Code: Select all

{ "data": { "did": "001D0A100352", "name": "JMFweatherAQI", "ts": 1601650065, "conditions": [{ "lsid": 351579, "data_structure_type": 6, "temp": 69.1, "hum": 56.7, "dew_point": 53.1, "wet_bulb": 57.9, "heat_index": 68.3, "pm_1_last": 0, "pm_2p5_last": 0, "pm_10_last": 0, "pm_1": 0.00, "pm_2p5": 0.00, "pm_2p5_last_1_hour": 0.00, "pm_2p5_last_3_hours": 0.01, "pm_2p5_last_24_hours": 0.01, "pm_2p5_nowcast": 0.01, "pm_10": 0.10, "pm_10_last_1_hour": 0.10, "pm_10_last_3_hours": 0.15, "pm_10_last_24_hours": 0.15, "pm_10_nowcast": 0.13, "last_report_time": 1601650065, "pct_pm_data_last_1_hour": 100, "pct_pm_data_last_3_hours": 91, "pct_pm_data_nowcast": 22, "pct_pm_data_last_24_hours": 11 }] }, "error": null }

[admin]

Assigning of sensors to air0pm to air2pm can be one way or another. I don't see a reason to change that to any personal preferences. How reliable this data from the Airlink is at all remains to be seen. The tons of zero measurements don't give me indication that these sensor comes any way close to professional measurement devices. Please don't blame Meteobridge for that.

[jasonmfarrow]

Boris,

Not blaming you at all. Just asking for confirmation that the software is reading the Airlink PM values, PM_1.0, PM_2.5 and PM_10.0 and assigning them to airX!0pm, airX!1pm, airX!2pm respectively. That way we are sure that when we're mapping to logical sensors we're matching up correctly.

FYI. I think my Airlink is under-reading the PM levels compared to other sensors. Here's the comparison. My Nova SDS011 on the left and the Airlink on the right. The sensors are right next to each other and thus should be reading the same.

Screenshot 2020-10-03 at 3 October 2020 13.54.38 pm.png (80.61 KiB) Viewed 4019 times

PM2.5: SDS=3.5 vs AL=0.1 PM10: SDS=10.9 vs AirL=1.8. That's quite a difference by a factor of 10. My SDS011 values seem to be much more aligned to the wider airmass around where I live. https://aqicn.org/station/united-kingdo ... basings39/

The Airlink might be £179 of wasted cash...