[weewx-user] Re: Has WU changed its API Key length
I did some more checking and the WU API keys and calls have changed. If you upload to WU you can get a new key. But until the forecasting code is updated they will not work because they change the API calls. Any timeline for issuing a new forecasting addon WeewX? For those that have not seen the WU notice, here it is: If you have a personal weather station that uploads to Weather Underground and have been waiting to get a key for the new API, here are the instructions. Please note that if you do NOT download data from the Weather Underground API, you probably don't need a key. Uploading data to Wunderground from your PWS is not the same thing. Dear PWS uploaders, thank you for your continued loyalty and patience! *The gateway for the new API keys for PWS uploaders is open.* Cut and paste this URL into your browser: https://www.wunderground.com/member/api-keys <https://www.wunderground.com/member/api-keys?_ga=2.114409799.196118847.1554163090-199462139.1554163090> If you are not logged in, you will be asked to. The system will also verify that you have a PWS uploading to the system. You will then see a blank box below “Your API keys”. Agree to the new Terms and Conditions by clicking in the small box next to “I agree”, click on the blue “GENERATE” box, and your new key will be created. The key will be masked on the screen, but you can use the “Show” link below the box to see it. There is also another blue box, which, when clicked, copies the key to your clipboard. If you have any problems, log out and log back in again. If that does not resolve the problem, *please email me at victoria.gard...@ibm.com <https://mail.google.com/mail/?view=cm=1=1=victoria.gard...@ibm.com>* . *Next*, once you have your new key, you can use it in the NEW (not old!) API’s commands. The documentation for those commands is here: https://docs.google.com/document/d/1eKCnKXI9xnoMGRRzOL1xPCBihNV2rOet08qpE_gArAY/edit The new API should work immediately once you have the new key in the new commands. Remember that the new keys work on the new API only, and the old keys work on the old API only. Old API keys that are associated with a PWS will be kept working until *March 22, 2019.* However, that will be *the very last day for those API keys to work*, so you should transition as quickly as you can to the new API. Victoria Gardner Weather Underground API customer service On Monday, April 1, 2019 at 6:43:14 PM UTC-4, Paul Oversmith wrote: > > Have been using Weather Underground to download forecasts for several > years. > Stopped working with a key error end of March, 2019. So I got a new API > key, but now getting the following messages: > Apr 1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: > download forecast from ' > http://api.wunderground.com/api/cbc1/hourly10day/q/34231.json > ' > > Apr 1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: > error in response: keynotfound: this key does not exist > > Seeing that the last 4 characters are outside the block out text, I was > wondering if they increased the key length and that is what is preventing > getting the forecast. Or perhaps I need to delete some of the API key. my > key is: d7xcbc1 > > Uploads to WU work. > > Tried to download a current version of the forecasting code, but the site > seems to be down. > > Any suggestions on how to fix? > > > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Has WU changed its API Key length
Have been using Weather Underground to download forecasts for several years. Stopped working with a key error end of March, 2019. So I got a new API key, but now getting the following messages: Apr 1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: download forecast from 'http://api.wunderground.com/api/cbc1/hourly10day/q/34231.json' Apr 1 17:54:19 WEATHER weewx-vantage[10772]: forecast: WUThread: WU: error in response: keynotfound: this key does not exist Seeing that the last 4 characters are outside the block out text, I was wondering if they increased the key length and that is what is preventing getting the forecast. Or perhaps I need to delete some of the API key. my key is: d7xcbc1 Uploads to WU work. Tried to download a current version of the forecasting code, but the site seems to be down. Any suggestions on how to fix? -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Lightning Strikes on weewx-sdr Issue
Thanks so much for the quick response. I felt it was something I missed in the setup. Changes made. Need the next thunderstorm to make sure it is working. Also thanks for the suggestion on LightningDistance. I changed the field to REAL. On Saturday, September 23, 2017 at 7:03:21 PM UTC-4, mwall wrote: > > > > On Saturday, September 23, 2017 at 5:40:05 PM UTC-4, Paul Oversmith wrote: >> >> I am having a real problem with the graph for lightning strikes using an >> Acurite 6045 lighting detector and the weewx-sdr driver. >> >> The total number of strikes and distance reports correctly, the strikes >> (delta) is not right (the strike are reported as .02 to .06 rather than an >> integer count, please see attached image). >> I have put monitors in the _calculate_delta(label, newtotal, oldtotal) >> routine and the values for newtotal and oldtotal are correct and show a >> difference of 1 when there is a strike. >> >> I tried several different setup options, but none fixed the situation. I >> suspect it has something to do with the time frame and the averaging of >> strikes over an interval rather than just reporting the quality, >> >> But I am at a loss to see what I have setup incorrectly. >> >> Hope someone has a suggestion to fix the problem. >> > > paul, > > thank you for the detailed problem description. you need to set the > accumulator for the lightning database field. as of weewx 3.7, you can do > this in the weewx configuration file, like this: > > [Accumulator] > > [[LightningStrikes]] > extractor = sum > > [[LightningStrikesTotal]] > extractor = sum > > you probably want 'REAL' instead of 'INTEGER' for the 'LightningDistance' > field (that will require re-creating the database, or manually modifying > the schema in sql) > > m > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Lightning Strikes on weewx-sdr Issue
I am having a real problem with the graph for lightning strikes using an
Acurite 6045 lighting detector and the weewx-sdr driver.
The total number of strikes and distance reports correctly, the strikes
(delta) is not right (the strike are reported as .02 to .06 rather than an
integer count, please see attached image).
I have put monitors in the _calculate_delta(label, newtotal, oldtotal)
routine and the values for newtotal and oldtotal are correct and show a
difference of 1 when there is a strike.
I tried several different setup options, but none fixed the situation. I
suspect it has something to do with the time frame and the averaging of
strikes over an interval rather than just reporting the quality,
But I am at a loss to see what I have setup incorrectly.
Hope someone has a suggestion to fix the problem.
My setup:
Schemia:
# AcuRite Lightning
('OutTempBalcony', 'REAL'),
('OutHumidityBalcony', 'REAL'),
('LightningStrikes', 'INTEGER'),
('LightningStrikesTotal', 'INTEGER'),
('LightningDistance', 'INTEGER'),
Acurite.conf (a seperate instants and database; I also have a Davis Pro):
[SDR]
driver = user.sdr
cmd = /usr/local/bin/rtl_433 -q -U -F json -R40 -R41
log_unknown_sensors = False
log_unmapped_sensors = True
OutTempBalcony = temperature.E76F.AcuriteLightningPacket
OutHumidityBalcony = humidity.E76F.AcuriteLightningPacket
LightningStrikes = strikes.E76F.AcuriteLightningPacket
LightningStrikesTotal = strikes_total.E76F.AcuriteLightningPacket
LightningDistance = distance.E76F.AcuriteLightningPacket
[[deltas]]
LightningStrikes = LightningStrikesTotal
Skin configuration [Image Generator]:
[[[dayLightningStrikes]]]
LightningStrikes
plot_type = bar
color = 0x4242b4
label = Lightning Strikes
[[[dayLightningDistance]]]
plot_type = bar
yscale =0, 50, 5
color = 0x4242b4
LightningDistance
Label = 'Storm Head Distance'
Skin.tmpl:
Lighting Strikes(Last Hour)
$hour($hours_ago=1).LightningStrikes.sum
#if ($day.LightningStrikes.sum.formatted == "0")
0
0
#else
$day.LightningStrikes.sum
$day.LightningDistance.min
#end if
strikesmiles
Storm Head(Last Hour)
#if ($day.LightningStrikes.sum.formatted == "0")
0
#else
$hour($hours_ago=1).LightningDistance.min
#end if
miles
Lighting StrikeCount
$current.LightningStrikesTotal
Last StormHead Distance
$current.LightningDistance.formatted
miles
Units.py:
bs_group_dict = ListOfDicts({"altitude" : "group_altitude",
"TempFreezer":
"group_temperature",
"LightningStrikes" : "group_count",
"LightningStrikesTotal" : "group_count",
"LightningDistance" : "group_distance",
--
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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
