Add Air Quality Index

[stevehoyt]

I just installed this Node Server. Install went with no problems. I noticed in the writeup and upon testing, that no values are available for the Air Quality Index monitors. I have 2 of them. One inside and one outside. Any chance of adding these in the future. No rush. Thanks

AirLink Air Quality Monitor by Davis Instruments

BY DAVIS INSTRUMENTS

SKU 7210

[stevehoyt]

@bpwwer

Good Morning

Just wondering if you had an thoughts on my initial post?

Thanks

Steve

[bpwwer]

Does the node server detect the sensors?  If so, do you see anything in the log (probably need debug enabled) showing the data from them?

I don't have any Davis equipment so I can only add support for something if I have enough info.

[stevehoyt]

Hi @bpwwer

I think your question points out the problem. I don't think the nodeserver is seeing the sensors (and some other available info). I have included a debug log file which shows what it is seeing. Some items are obvious some are not to me. I have included 2 screen shots of all the variables that I see looking at my weatherlink. Note the list on the right side of the screen shots. In addition I went to the Davis website and got info on retrieving the airlink info via an API. It looks like they have opened up a lot more info now. I don't know anything about api's hopefully that might mean something to you. here is the link. Thanks https://weatherlink.github.io/airlink-local-api/

 

WeatherLink_5-15-2023_84731_AM.zip

[bpwwer]

Ahh, it looks like that data may be available via the Version 2 API, but not the Version 1.  The node server current uses the Version 1 API. 

I have it on my list to convert the node server to use Version 2 of the API, but that's basically a full re-write of the node server and I don't have a time frame yet as to when I'll be able to do that.

[stevehoyt]

Thanks for checking. If there is anything you need from me to help, let me know

[bpwwer]

@stevehoyt Would you be willing to share your station's data with me?  I'm attempting to use the WeatherLink V2 API, but I don't have any way to test anything.  Possibly sharing a station with me will allow my WeatherLink account to access the data via the new API and I'll be able to test.   My WeatherLink account username is "bpaauwe".

[stevehoyt]

@bpwwer No problem sharing info. Not sure if you need my API key and login info or not. 

For now I set the station to public and here is my URL 

https://www.weatherlink.com/bulletin/a4cf142c-4278-4caa-8f2a-075ff6aef066

 

[bpwwer]

@stevehoyt I can look at public stations with the website, but I can't access them via the API.  I believe that if a station is "shared" then I can access that station's data via the API.   When I look at a station there's a link at the top to share and uploads

When I click on that it has a search for username to share the station with.  I think that if you share your station with me, it will show up in my list of stations (which is currently empty). 

Otherwise, I think you'd have provide me both your API secret and API token which you're not really supposed to share.

[stevehoyt]

@bpwwer

I think I got it setup. Sent you a private message with the info.

Let me know if it does not work.

[stevehoyt]

@bpwwer

Hi

 I was thinking about asking you how your test was going. Before I did however, I looked in the nodeserver non production store thinking I might find the same version you are testing and try installing it

I did not see one...no big deal. I then saw the notice that 2.0.4 was available. I installed it. It says it started but did not. Also I get a log file error if I try to look at the log. 

Any ideas?

Software versions below.

[bpwwer]

Testing is going well.  Here's a bit of preview:

The PG3 log might shed some light on why the node server's not starting.  There is a known issue with PG3 where it will occasionally fail to install all of the node server files and that will typically cause the node server to not run. Since no new development (or even bug fixes) are happening to PG3, the current recommendation from UDI is to migrate to PG3x.

Having access to your station's data has been a huge help so thanks again for that.

[stevehoyt]

Any idea why I get the message log file not found when I try and look at it?

Thanks

[bpwwer]

6 hours ago, stevehoyt said:

Any idea why I get the message log file not found when I try and look at it?

Thanks

The PG3 log or the node server log?

Since the node server isn't starting, there isn't a node server log to display, so that's expected to say not found.  If there's no PG3 log, then PG3 isn't running and that's a very different problem

When PG3 tries to start the node server, it should report any errors to the PG3 log.  So you may want to attempt to start the node server and then switch to the PG3 log (Log menu, not the Log tab on the node server details page), download the log and PM or attach here.  I'll take a look.

[stevehoyt]

I restarted it and this is the error I got. See info below. I'll try and update to PG3X this afternoon or tomorrow. So don't spend a lot of time worrying about this error. It might be fixed with PG3X.

8/23/2023, 11:11:58 [pg3] info: [WeatherLink(15)]: Restarting Nodeserver
8/23/2023, 11:11:58 [pg3] warn: [WeatherLink(15)]: Was not running. Starting...
8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink
8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink is valid
8/23/2023, 11:12:01 [pg3] info: checkLicense:: WeatherLink Valid perpetual license found.
8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink finished update check
8/23/2023, 11:12:01 [pg3] info: [WeatherLink(15)] :: Starting NodeServer - Version 2.0.4
8/23/2023, 11:12:01 [pg3] info: startNs:: WeatherLink updating database (enabled, timestarted)
8/23/2023, 11:12:01 [pg3] info: MQTTS: Client Connected: pg3frontend_fFNiD
8/23/2023, 11:12:02 [pg3] error: [WeatherLink(15)] :: STDERR:   File "/var/polyglot/pg3/ns/000db9594020_15/./wll.py", line 1
    V8', 'value': 0, 'uom': 56, 'name': 'Wet Leaf 1'},
      ^

8/23/2023, 11:12:02 [pg3] error: [WeatherLink(15)] :: STDERR: SyntaxError: invalid syntax

8/23/2023, 11:12:02 [pg3] info: [WeatherLink(15)] :: Exit cause code: 1 - signal: null
8/23/2023, 11:12:02 [pg3] info: startNs:: WeatherLink starting polls
8/23/2023, 11:12:02 [pg3] info: Starting WeatherLink Info timer 0
8/23/2023, 11:12:02 [pg3] info: Starting WeatherLink Version Check timer
8/23/2023, 11:12:17 [pg3] warn: MQTTS: keepaliveTimeout: pg3frontend_fFNiD
8/23/2023, 11:12:17 [pg3] error: MQTTS: clientError: pg3frontend_fFNiD keep alive timeout
8/23/2023, 11:12:17 [pg3] info: MQTTS: Client Disconnected: pg3frontend_fFNiD
8/23/2023, 11:12:22 [pg3] info: MQTTS: Client Connected: pg3frontend_fFNiD
8/23/2023, 11:12:54 [pg3] info: [00:0d:b9:59:40:20_12] controller reporting command DON
8/23/2023, 11:12:54 [pg3] info: [RainMachine 12] :: STDOUT: PING 192.168.0.34 (192.168.0.34): 56 data bytes

8/23/2023, 11:12:54 [pg3] info: [RainMachine 12] :: STDOUT: --- 192.168.0.34 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss, 1 packets out of wait time
round-trip min/avg/max/stddev = 5.673/5.673/5.673/0.000 ms

8/23/2023, 11:12:55 [pg3] info: [00:0d:b9:59:40:20_14] setup reporting command DOF
8/23/2023, 11:13:31 [pg3] warn: MQTTS: keepaliveTimeout: pg3frontend_fFNiD
8/23/2023, 11:13:31 [pg3] error: MQTTS: clientError: pg3frontend_fFNiD keep alive timeout
8/23/2023, 11:13:31 [pg3] info: MQTTS: Client Disconnected: pg3frontend_fFNiD
8/23/2023, 11:13:36 [pg3] info: MQTTS: Client Connected: pg3frontend_fFNiD
8/23/2023, 11:13:54 [pg3] info: [00:0d:b9:59:40:20_12] controller reporting command DOF
8/23/2023, 11:13:54 [pg3] info: [RainMachine 12] :: STDOUT: PING 192.168.0.34 (192.168.0.34): 56 data bytes

8/23/2023, 11:13:54 [pg3] info: [RainMachine 12] :: STDOUT: --- 192.168.0.34 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss, 1 packets out of wait time
round-trip min/avg/max/stddev = 6.564/6.564/6.564/0.000 ms

8/23/2023, 11:13:55 [pg3] info: [00:0d:b9:59:40:20_14] setup reporting command DON
 

[stevehoyt]

@bpwwer

You can ignore the message above....Got updated to pg3x 3.2.2 and it has now started.

Thanks

[bpwwer]

Yeah, that was the problem with PG3.  Sometimes it wouldn't unzip all the files from the package and sometimes it would end up unzipping only part of the file.  In your case, it looks like it didn't unzip correctly so the files wasn't complete or was corrupted.   I think I might have this fixed but UDI isn't releasing new versions of PG3, only PG3x.

[larryllix]

15 hours ago, bpwwer said:

Yeah, that was the problem with PG3.  Sometimes it wouldn't unzip all the files from the package and sometimes it would end up unzipping only part of the file.  In your case, it looks like it didn't unzip correctly so the files wasn't complete or was corrupted.   I think I might have this fixed but UDI isn't releasing new versions of PG3, only PG3x.

Can you tell me the difference between PG3 and PG3x please?

[bpwwer]

6 hours ago, larryllix said:

Can you tell me the difference between PG3 and PG3x please?

One has an 'x' at the end of the name

PG3x started as an experiment to see if we could use an external MQTT broker instead of the internal broker library being used in PG3.  There were some reported issues that we believed were caused by bugs in the internal MQTT broker library code.  This was basically an internal change with no change in functionality.

Once we were certain the external MQTT broker would work, it made it possible to do some things that weren't really possible before.

• Run node servers under separate/unique user accounts for additional security
• Allow for remote access (currently used by UD Mobile) to PG3
• Allow node servers to access remote authentication mechanisms (Ring)

That's really it for differences.  Everything else remained the same.

As of PG3 version 3.1.23, UDI is no longer maintaining PG3.  Bug fixes and new features have only been applied to PG3x.  Many of the features are targeted at node server developers but there have been a few UI enhancements in PG3x.

I've been maintaining the PG3 code by applying all the bug fixes and enhancements made to PG3x, but since UDI isn't releasing it, it's been just for my personal use.