forecast WU/OWM, and SteelSeries Gauges not working with latest version

[sbar...@gmail.com]

Hello,

I have been struggling a bit with my update to 4.3. So I ended uninstalling everything, 

upgrading to raspbian 10, and reinstall from setup.py with all latest versions.

I got station back up and running then added things and what I find : 

 - OWM forecasts seems to work  and store data in DB, but no forecast come in the forecast skins. Actually any report referencing OWM forecasts will die and not produce teh report (but can seem to find a way tp get a stack trace or some debug info in the logs)

 - SS skin seem to reference an older version of WD, so I had to change the skin.conf to match wd new names 

 - WU does not work at all. URL uses an old version of the API which return 404 or 401 at the moment for me.

Am I missing something important there? Like these are not used and supported anymore? Or have I the wrong source for these components?

I am updating the WU forecast to get what comes form V3 API. 

Is this the way to go? Should I PR all these changes?

Regards,

[John Kline]

What versions of the forecast and steel series extensions are you using?

On Jan 24, 2021, at 8:12 AM, sbar...@gmail.com <sbar...@gmail.com> wrote:

Hello,

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e050fbb5-dd53-4f2c-be65-53a6eaca580en%40googlegroups.com.

[sbar...@gmail.com]

Hi, 

I have this in my skin.conf for ss : 

# $Id: skin.conf 1210 2015-01-01 17:01:08Z mwall $

is this the proper information or should I paste something else?

[gjr80]

On Monday, 25 January 2021 at 02:12:46 UTC+10 sbar...@gmail.com wrote:

 - SS skin seem to reference an older version of WD, so I had to change the skin.conf to match wd new names 

Can you elaborate on this please, I am not aware of the need for any change to the SteelSeries skin under 4.3.0

Gary

[John Kline]

As for the forecast extension, please install:

https://github.com/chaunceygardiner/weewx-forecast/releases/tag/v3.4.0b11

On Jan 24, 2021, at 11:26 AM, gjr80 <gjrod...@gmail.com> wrote:

--

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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/fdacd5ea-81f2-4456-9ffa-b22663d22ec2n%40googlegroups.com.

[sbar...@gmail.com]

Well well, it took a me a little while.

but I found that while I though I had a clean copy from github for that template, there is more in mine than on the github template/

Here is what I have now : 

[CheetahGenerator]

    encoding = html_entities   

search_list_extensions = user.forecast.ForecastVariables,user.wdsearchlist.WdTimeSpanTags, user.wdsearchlist.WdWindRunTags, user.wdsearchlist.WdLastRainTags, user.wdsearchlist.WdSundryTags, user.wdsearchlist.WdSkinDict, user.wdsearchlist.WdAvgWindTags, user.wdsearchlist.WdWindRunTags, user.wdsearchlist.WdHourRainTags

    [[ToDate]]

        [[[index]]]

            template = index.html.tmpl

        [[[data]]]

            template = gauge-data.txt.tmpl

And the version I had last night was referencing the old name of wdSearchX3, and I kept having exceptions the function did not exist.

Should I just remove this line? right now, my skins does not generate the gauge-data.txt.

[sbar...@gmail.com]

Regarding Version 3.4.0b11 of the forecast skins, maybe it should be referenced in the wiki as well.

That's where I found 3.4.0b1, which obviously has issues with WU.

https://github.com/weewx/weewx/wiki/forecasting

[gjr80]

Any WdXxxxxx search list extensions are part of WeeWX-WD which has absolutely nothing to do with the generation of gauge-data.txt via the SteelSeries skin (WeeWX-WD did previously generate a data file, customclientraw.txt, for use by the SteelSeries Gauges but that was before direct WeeWX support was included in the SteelSeries Gauges via the SteelSeries skin/gauge-data.txt). If any of the search list extensions generate an error it will likely prevent the templates being processed, whether the templates require the search list extension products or not.

My advice is that if this skin.conf extract is from a plain vanilla install of the SteelSeries skin then remove all of the search list extensions from the skin and try that. If you have substantially modified the SteelSeries skin then you will need to provide details on your modifications so we know which search list extensions are required and which are not.

Gary

[sbar...@gmail.com]

@gjr80. You are right, the wd search is not part of ss skins. I need to add these to the skin to customize it, and have a little bit of forecasts on my page.

Now I just need to figure out why the report do not get generated.

Is there a way to get additional information from the report generator as to why the file does not get generated?

Regards,

[gjr80]

On Monday, 25 January 2021 at 06:32:00 UTC+10 sbar...@gmail.com wrote:

@gjr80. You are right, the wd search is not part of ss skins. I need to add these to the skin to customize it, and have a little bit of forecasts on my page.

I could understand adding forecast details to gauge-data.txt as it currently includes none but I don’t understand why you would want the WeeWX-WD data.

 

Now I just need to figure out why the report do not get generated.

Is there a way to get additional information from the report generator as to why the file does not get generated?

The best you can do is set debug = 1 in weewx.conf, restart WeeWX and then look in the log. Cheetah error messages sometimes pinpoint the error and at other times are notoriously unhelpful, it really depends on where and what the error is. 

Gary

[sbar...@gmail.com]

Hi,

It took me a little while, but I reverted by steelserreis folder to what is in the repo, and it works. But I indeed lost my forecast line.

To explain, I forgot about it, but when I first customized the steel series for me, changed the zambretti forecast with the WU one.

I added the following code to my gauges-txt : (the zambretti part is from the original file to help figure where put the code)

## if forecasting is installed, report the Zambretti forecast

#if $varExists('forecast.zambretti')

#set $fc = $forecast.label('Zambretti', $forecast.zambretti.code)

#else

#set $fc = 'forecast is not available'

#end if

#set $periods = $forecast.weather_periods('WU')

#if len($periods) > 0

  #set $wts = ''

  #set $wloc = ''

  #set $fc = ''

  #set $Loops = 0

  #for $period in $periods

    #set $wts = $period.issued_ts

    #set $wloc = $period.location

#if $period.event_ts is not None

#set $fc +=$period.event_ts.string('') + ' '

#end if

#if $period.temp is not None

#set $fc += $period.temp.string('') + ' '

#end if

#if $period.clouds is None

#set $fc += 'N/A'

#else

#set $fc += $forecast.label('Weather', $period.clouds)

##set $fc += $period.clouds

#end if

#set $fc += '     '

#if $Loops > 10

#break

#else

#set $Loops += 1

#end if

  #end for

#else

  #set $fc='No forecast available'

#end if

##

Would anyone be able to point out what is wrong with that and makes it fail with the current version of Weewx? Or point me to a document explaining how this can be run in debug mode. It does not give any error with debug=1 run in daemon or app mode.

[gjr80]

Perhaps there is nothing wrong with it. Is that the only change you made to the gauge-data.txt template? If so the following search list extensions are not used and one of them could well cause the failure:

user.wdsearchlist.WdTimeSpanTags, user.wdsearchlist.WdWindRunTags, user.wdsearchlist.WdLastRainTags, user.wdsearchlist.WdSundryTags, user.wdsearchlist.WdSkinDict, user.wdsearchlist.WdAvgWindTags, user.wdsearchlist.WdWindRunTags, user.wdsearchlist.WdHourRainTags

If they are not required then I suggest you remove or disable them.

As yet you haven’t given us any details on ‘the failure’. Is there an error in the log or does the template just not work as you expect? If there is an error in the log what is it? CheetahGenerator errors often don’t pinpoint the error but they almost always give you clues.

Gary

[sbar...@gmail.com]

Thank you @gjr80. Your last comment told me what I should have done from the start. I diffed the files, and found that quite a few subtles changes where performed in the template since the original version I had (new variables and renamed variables)

 

So I updated my working file, with the WU forecast code I updated before, and now it works.

 

Many thanks again for the help. And I am happy to report that my Weewx, that needed restart every other day, seems now to work without any problem since upgrade to 4.3.0.

FWIW, I had already removed the WD extension that did not seem usefull, and it does not do any harm not to have them?