Steve, I think Tom covered it pretty well. One thing to note is the new API takes a different approach to how you specify the location for which you want the forecast. Previously you could specify a PWS code now its geocode (lat/long), ICAO code, IATA code, place ID and postal key (limited countries). Rtgd should default to your stations lat/long if no valid location setting is found so the easiest thing is probably to just remove the location = xxxxx line altogether. I suspect Tom's PWS code is a hang over form the and old rtgd. As you noted there is useful info in the comments in rtgd.py,it is likely more up to date than anything in the associated wiki.
You asked about commenting out the SteelGauges section in weewx.conf. The reason we do this is that you have two services producing gauge-data.txt; the SteelSeries skin will produce gauge-data.txt each report cycle and the rtgd extension will produce gauge-data.txt (up to) on receipt of every loop packet. That in itself is not a problem but if you have both of those services set to save gauge-data.txt in the same location you might see some off behaviour on your gauges (gauges jumping around at odd times etc). Worst case you could have both services try to write to the same file at the same time and that could cause WeeWX to complain. It also makes it easier to fault find if you only have one service creating a file. The other approach you can take is to have the SteelSeries skin save it's version of gauge-data.txt somewhere WeeWX won't see it, eg /var/tmp. One final thing, the SteelSeries skin also serves some other purposes, on startup it copies the javascript and css files required by the SteelSeries Gauges to your public_html directory as well as generating the html page the gauges are displayed on. You may wish to keep some or all of these running. So my advice is to just disable the generation of gauge-data.txt rather than the whole skin. The rtgd documentation probably does not make that point very clearly. Gary On Thursday, 11 April 2019 03:28:36 UTC+10, Steve2Q wrote: > > Tom..Thank you! I am not sure why my 1st attempt at using my new API > didn't work. Maybe because I used my lat/long instead of my PWS ID? Anyway, > you are correct that WU is much more detailed than DS. Now to change back > the HTML file so the bottom left attributes are correct. > > Steve > > On Wed, Apr 10, 2019 at 1:05 PM Tom Robertson <[email protected] > <javascript:>> wrote: > >> Steve, >> I assume you are using the latest RTGD version 0.3.7 released 7 days >> ago. I found the WU forecast to be more detailed than the DarkSky forecast. >> >> This is what my weewx.conf looks like under the [RealtimeGaugeData] >> [[WU]]. It is slightly different from before. I believe my API key is >> around 32 characters now. Gary told me to use the PWS name instead of the >> coordinates for the location. >> >> [[WU]] >> api_key =XXXXXXXX >> units = e >> language = en-US >> interval = 1800 >> api_lockout_period = 60 >> max_tries = 3 >> location = pws:KALALBER13 >> debug = 0 >> >> ----- >> Tom >> >> On Apr 10, 2019, at 10:14 AM, Steve Meltz <[email protected] <javascript:>> >> wrote: >> >> Hi Tom. When I saw that the key I had was no longer working, I went >> through the steps as stated in your email to generate a new key (I have >> been registered with WU as a PWS for several years). When I plugged this >> new key into the rtgd configuration, I still had no info in the scroller. >> Maybe I had to wait longer? For now, DarkSky is working and I will see how >> accurate it is. I may go back to giving WU a try. >> >> Thans, Steve >> >> On Wed, Apr 10, 2019, 10:55 AM Tom Robertson <[email protected] >> <javascript:>> wrote: >> >>> Hi Steve, >>> If you supply data to WU then you can get a new API from them. Gary has >>> update RTGD to use the new API and properly display the forecast on the LED >>> ticker. Here are the instructions for getting a new key: >>> >>> First, if you are not logged into Weather Underground, you will need to >>> do so. You must log in using the same email address as the PWS. To do >>> that, go to wunderground.com, click on “my profile”, click on “member >>> settings”, and log in if you are not already. >>> >>> Then navigate on the screen to My Profile => Member Settings => API >>> Keys. >>> >>> If you have a PWS registered, you will 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. Also on this page is a link to >>> the documentation. >>> >>> If you do not have a PWS registered to your email address, you will not >>> be able to get a key. >>> >>> >>> >>> ----- >>> Tom >>> >>> On Apr 10, 2019, at 9:39 AM, Steve Meltz <[email protected] <javascript:>> >>> wrote: >>> >>> G'day Gary! Its been a while. As you know I was having a memory leak >>> problem which seems to be coming from the driver used with my Ultimeter. >>> Although the memory still increases, it is much less using an old version >>> rather than the one included with the Weewx update. Anyway, in trying to >>> track things down, I uninstalled Steel Gauges and RTGD. I spent several >>> hours yesterday getting them to work, but I found the help included in the >>> rtgd.py file very useful, so thank you. I think you may have to remove >>> the ability to use the Wundeground API, however. Mine no longer works, and >>> the WU website states that they no longer support personal weather station >>> API's (which I think is a terrible corporate decision..we supply a lot of >>> their data). I signed up for DarkSky and they allow free use of an API as >>> long as no more than 1000 requests/day are made. I am now watching memory >>> growth, and my next experiment may be (I saw how to do this somewhere on >>> the net) to put in some code which will stop/start Weewx when the memory >>> use exceeds some user defined level. More fun! >>> >>> Oh, as part of the re installation of the Gauges, I commented out the >>> Steel Gauges section in weewx.conf, and everything seems to be working just >>> fine. Any reason to un-comment it? >>> >>> Cheers, Steve >>> >>> On Wed, May 23, 2018 at 7:20 PM gjr80 <[email protected] <javascript:>> >>> wrote: >>> On Thursday, 24 May 2018 08:37:50 UTC+10, Steve2Q wrote: >>> Gary..its working now!! Thank you. I plugged in my zipcode, >>> >>> That's good to hear, ended up taking a bit longer than we thought but >>> got there in the end. I need to make sure I capture all of this in the rtgd >>> wiki. >>> >>> and also added units = us as it appears to default to metric. >>> >>> Sorry, the price you pay I guess for someone from Australia writing the >>> code :) >>> >>> Now let see how long WU keeps sending out the data! >>> >>> Yes, will be interesting to see. I have already started work on sourcing >>> the forecast text from elsewhere. Would ideally like to support our own >>> Bureau of Meteorology (not much use for those outside of Australia though) >>> but unfortunately BoM has very restrictive copyright terms. Plenty of other >>> free sources available though. >>> >>> Gary >>> >>> -- >>> 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/reHbE13IoyU/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected] <javascript:>. >>> 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] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> 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/reHbE13IoyU/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected] <javascript:>. >>> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> 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/reHbE13IoyU/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> 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.
