Wlink Driver Not Getting Archive Records to build database

[John Cheesbrough]

I have been running the wlink driver on a MacBook Pro successfully for a number of months but stopped doing so about a month ago when I deleted the database 

I recently decided to run it on my Raspberry Pi However I thought I would just check it still ran on the Mac first and also upgraded the weewx from 3.7.1 to 3.8.2.

Having done this I found that I could not get Archive records but could get Loop records but they were different under each version of weewx.

The console activity report showed the following:

16:09:44.267649 +0100 Python 1546 default engine: Internal error detected. Catchup abandoned

16:09:44.267714 +0100 Python 1546 default **** Unknown archive type: 0x73

16:11:46.001392 +0100 Python 1546 default wlink: download failed attempt 1 of 5: timed out

16:14:09.797006 +0100 Python 1546 default wlink: download failed attempt 1 of 5: timed out

16:16:47.311177 +0100 Python 1546 default wlink: download failed attempt 1 of 5: timed out

16:17:32.765074 +0100 Python 1546 default engine: Internal error detected. Catchup abandoned

16:17:32.765225 +0100 Python 1546 default **** Unknown archive type: 0x73

The Loop record running 3.7.1 was 

LOOP:   2018-09-17 15:12:04 BST (1537193524) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1537193524, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 473.579132861, outTemperature: None, pressure: None, rainRate: 0, usUnits: 1, windchill: None

The Loop record running 3.8.2 was

LOOP:   2018-09-17 15:46:38 BST (1537195598) dateTime: 1537195598, maxSolarRad: 402.739164053, outTemperature: None, rainRate: 0, usUnits: 1

I also tried getting data and header from http://weatherlink.com/webdl.php?. The header was OK and I have included a file of the .php output.

The weewx data base has no entries and whilst the public_html directory has entries they do not contain plots nor and index file.

I have attached the syslog file and also the config file with is that same as it was when it ran successfully. 

I am aware that weatherlink have been making changes but my weatherlink software is able to download as it has for the last 3 years.

I am sure that I must be missing something simple but have now come to the point where I need another pair of eyes to look at what I have done.

Thanks in anticipation 

John

[mwall]

On Monday, September 17, 2018 at 11:56:22 AM UTC-4, John Cheesbrough wrote:

I have been running the wlink driver on a MacBook Pro successfully for a number of months but stopped doing so about a month ago when I deleted the database 

I recently decided to run it on my Raspberry Pi However I thought I would just check it still ran on the Mac first and also upgraded the weewx from 3.7.1 to 3.8.2.

Having done this I found that I could not get Archive records but could get Loop records but they were different under each version of weewx.

hi john,

which version of the wlink driver are you using?  i seem to recall making some changes in the past year to deal with the change to weatherlink 2.

your failed download attempts appear to be due to timeouts, which could be due to local (or remote) network failures.  but if that is a bogus/misleading error message, lets figure it out.  weatherlink.com/webdl.php is only one of the URLs - data are obtained from www.weatherlink.com/user/xxx/index.php (i think that is the url that changed?)

one of the changes from 3.7.x to 3.8.x was to eliminate useless data in the loop packets - we got a bit more precise about the difference between None and nothing.  notice that all of the 'missing' fields in the packets you posted have observations with value of 'None'.

search for 'None' in the changelog:

http://weewx.com/downloads/README.txt

also see the issue that brought the changes:

https://github.com/weewx/weewx/issues/291

[John Cheesbrough]

Thanks for the reply

I am using wlink 0.14

I had migrated from Weatherlink 1.0 to 2.0 successfully prior to stopping using weewx-wlink on the Mac. I was using it when the user change from account ID to station iD and password remaining as the account holders. 

For your information I recently received the attached from weatherlink:

Hello John Cheesbrough,

Thank you for requesting Davis Instruments API access. I have provided examples for both JSON and XML formats below. 

Please do not distribute your code to anyone outside of your private business. Note that your unique apiToken will be used with the EnviroMonitor Gateway, Vantage Connect or WeatherLink IP DID into “user=” and system owners Password into “pass=” as demonstrated below. The API call for an EnviroMonitor system will only output the Sensor Suite data that is attached to the EnviroMonitor Gateway. 

Here is an example of the API call and a link to the XML format using a sample apiToken. Data will be available at a rate equal to your Archive Interval or Service Plan Update Interval. We request a maximum poll rate of ten minutes per station through the API. Please note that the password required in the API calls below is the password of the system owner, not shared users. 

https://api.weatherlink.com/v1/NoaaExt.xml?user=DID&pass=ownerPW&apiToken=tokenID 

Also, here is an example of the API call for station status info and meta data and a link to the XML format. The station status should not be polled but can be grabbed when needed for human initiated setup or diagnostic efforts. 

https://api.weatherlink.com/v1/StationStatus.xml?user=DID&pass=ownerPW&apiToken=tokenID 

Here is an example of the API call and link to the JSON format using a sample apiToken. Data will be available at a rate equal to your Archive Interval or Service Plan Update Interval. We request a maximum poll rate of ten minutes per station through the API. Please note that the password required in the API calls below is the password of the system owner, not shared users. 

https://api.weatherlink.com/v1/NoaaExt.json?user=DID&pass=ownerPW&apiToken=tokenID 

Also, here is an example of the API call for station status info and meta data and a link to the JSON format. The station status should not be polled but can be grabbed when needed for human initiated setup or diagnostic efforts. 

https://api.weatherlink.com/v1/StationStatus.json?user=DID&pass=ownerPW&apiToken=tokenID 

Please let us know if you have any difficulties or any other questions about this API. 

Many Thanks,
Tech Support 

– 
TechSupport 
O: 510-732-7814

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/vkkejQrZFp4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Cheesbrough]

I have found a workaround.

I re-installed weewx using the Simulator driver and then stopped Weewx and changed  weewx.conf to the wlink driver. Now working without problems and updating the Archive and Public_Html files. 

I still do not know the root cause.

John

To unsubscribe from this group and all its topics, send an email to weewx-user+unsubscribe@googlegroups.com.