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
On Monday, 17 September 2018 18:30:12 UTC+1, John Cheesbrough wrote: > > 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 > > <https://api.weatherlink.com/v1/NoaaExt.xml?user=001D0A00DE6A&pass=demo&apiToken=demo0a002bc5272033001d0a002bc527> > > 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 > > <https://api.weatherlink.com/v1/StationStatus.xml?user=001D0A00DE6A&pass=demo&apiToken=demo0a002bc5272033001d0a002bc527> > > 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 > > <https://api.weatherlink.com/v1/NoaaExt.json?user=001D0A00DE6A&pass=demo&apiToken=demo0a002bc5272033001d0a002bc527> > > 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 > > <https://api.weatherlink.com/v1/StationStatus.json?user=001D0A00DE6A&pass=demo&apiToken=demo0a002bc5272033001d0a002bc527> > > 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 > > On 17 Sep 2018, at 18:19, mwall <[email protected]> wrote: > > > > 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 > > -- > 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 > [email protected]. > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
