Thanks for getting back to me. > On Dec 3, 2020, at 5:42 AM, 'Michael Waldor' via weewx-user > <weewx-user@googlegroups.com> wrote: > > I've pulled your change and waited for some days: Now the temperatures shown > look much better. No longer constant values. And the values match with our > weather😊 > > Thanks for your support, > > Michael > > jo...@johnkline.com schrieb am Dienstag, 1. Dezember 2020 um 15:47:50 UTC+1: >> This is now released as 3.4.0b11: >> https://github.com/chaunceygardiner/weewx-forecast/releases/tag/v3.4.0b11 >> >>>> On Nov 30, 2020, at 3:23 PM, John Kline <jo...@johnkline.com> wrote: >>>> >>> >> >>> Thanks, I was just looking for you to confirm that you were seeing the >>> issue in the forecast skin itself. >>> >>> I looked at forecast_compact.inc. It is looking for temperatureMin and >>> temperatureMax (which are in the beginning section of the WU forecast). >>> Furthermore, when I looked at the tempMin and tempMax columns in the >>> database, they were wrong. There was a bug in parsing for these values. >>> I’ve fixed that now. >>> >>> Please pull forecast.py at head and give it a try. Copy it to >>> <weewx-home>/bin/user. >>> >>> You’ll need to wait for a new WU forecast to download and then for a report >>> to generate. This download may take some time. If you’re comfortable >>> mucking with the database, you could delete the latest WU forecast. If >>> you’re not comfortable doing that, and you don’t want to wait, you could >>> simply delete the forecast.db file and then restart weewx (which you have >>> to restart anyway after you copy over the new forecast.py file). >>> >>>>> On Nov 30, 2020, at 8:20 AM, 'Michael Waldor' via weewx-user >>>>> <weewx...@googlegroups.com> wrote: >>>>> >>>> Regarding missing icon... I already copied it from your zip, and it's >>>> working fine. I just thought that the missing icon might be a hint that >>>> some important code might be missing, too. But probably not. >>>> >>>> I did use the original forcast skin creating the subfolder forecast within >>>> HTML area. And it, too, contains the "wrong" temperature values. Identical >>>> to those values as been shown within my usecase of forecast_compact. >>>> >>>> Yesterday I've validated that forcast.sdb contains the "correct" forecast >>>> temperatures within the SQL database field temperature (there are >>>> 12entries per timestamp for 6days). Hopefully my forecast.sdb.txt posted >>>> yesterday is still a valid binary SQL database, then you can inspect it e. >>>> g. using sqlbrowser. >>>> >>>> Thus I assume that somewhere within weewx/forecast the wrong data are >>>> forwarded into HTML output. >>>> >>>> jo...@johnkline.com schrieb am Montag, 30. November 2020 um 16:15:24 UTC+1: >>>>> frzngdrzl.png was added to the repository after the b10 release. If you >>>>> want it, you’ll have to download the repository at head. >>>>> >>>>> I cannot decipher from your reply if the compact forecast is correct in >>>>> the forecast skin. Is it? >>>>> >>>>>>> On Nov 30, 2020, at 12:10 AM, Michael Waldor <michael...@gmx.de> wrote: >>>>>>> >>>>>> >>>>> >>>>>> Yes, I did diff both - they are identical. But there is a minor issue: >>>>>> You did update install.py to include frzgrain.png. This is still missing >>>>>> within your >>>>>> https://github.com/chaunceygardiner/weewx-forecast/releases/tag/v3.4.0b10 >>>>>> - the png is include but it will not be installed. Is there any other >>>>>> important change maybe missing within your last zip release? >>>>>> >>>>>> Of course that does not explain the wrong temperature numbers. I've >>>>>> checked also the foreground skin. The data are in sync with my change >>>>>> within Seasons skin. But the data do not contain the values from >>>>>> temperature field within forecast.sdb. >>>>>> >>>>>> Don't know the internal flow of weewx/forecast. I assume that first you >>>>>> fetch json contents from WU. Then that data is uploaded into >>>>>> forecast.sdb. Afterwards during creation of HTML output the data from >>>>>> forecast.sdb is read and added into the HTML templates by forecast.py. >>>>>> If my assumption is correct there might be a problem during the step >>>>>> from forecast.sdg into the HTML output. >>>>>> >>>>>> >>>>>> jo...@johnkline.com schrieb am Sonntag, 29. November 2020 um 14:36:07 >>>>>> UTC+1: >>>>>>> > Maybe I'm using the wrong forecast_compact.inc (see my included >>>>>>> > file)? And see als my forecast.sdb and 5day.json with the presumably >>>>>>> > correct temp values, but not shown within the rendered window. >>>>>>> >>>>>>> Did you diff forecast_compact.inc with the like named file in the >>>>>>> latest forecast extension? Are they identical? If not, please provide >>>>>>> the diff. >>>>>>> >>>>>>> Does the compact forecast in the forecast skin have the correct values? >>>>>>> >>>>>>>>> On Nov 29, 2020, at 1:27 AM, Michael Waldor <michael...@gmx.de> wrote: >>>>>>>>> >>>>>>>> Sorry for posting multiple times - but google did abort any post if >>>>>>>> containing *.json or *.inc files:-( >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Michael Waldor schrieb am Sonntag, 29. November 2020 um 10:26:00 UTC+1: >>>>>>>>> Tried to rename forecast.sdb into forecast.sdb.txt .... >>>>>>>>> >>>>>>>>> Michael Waldor schrieb am Sonntag, 29. November 2020 um 10:23:34 >>>>>>>>> UTC+1: >>>>>>>>>> Sorry, but google doesn't allow me to append the data. Thus I try >>>>>>>>>> again ... >>>>>>>>>> >>>>>>>> >>>>>>> >>>>>>>> -- >>>>>>>> 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/23bc8b05-639e-4a2b-9860-0e9b92ca6e8cn%40googlegroups.com. >>>>>>>> <forecast_compact.inc.txt> >>>>>> >>>>>> -- >>>>>> 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/86d6d50c-6653-41fb-ac02-ece43c399a0bn%40googlegroups.com. >>>> >>>> -- >>>> 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/85ee7fca-1645-4f35-9d65-7665c978a59en%40googlegroups.com. > > -- > 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/5c2482e8-ff38-4e72-8243-21145d3daaebn%40googlegroups.com.
-- 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/F9FA379B-8448-45BC-B3BD-0972A6BBEA27%40johnkline.com.
