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
On Saturday, 30 January 2021 at 20:03:59 UTC+10 sbar...@gmail.com wrote:
> 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.
> On Sunday, January 24, 2021 at 9:44:24 PM UTC+1 gjr80 wrote:
>
>> 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
>>
>>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/36149b85-3a29-4cba-b81d-3fbb94dc18c5n%40googlegroups.com.
