Thanks, Gary. I'll try posting this in its own thread now that things seem to be a little more stable.
Barry On Thursday, May 12, 2022 at 6:40:25 p.m. UTC-4 gjr80 wrote: > Barry, > > I don't use the forecast extension but it has had some issues for a while > now. If you have a search through the forums you should find some threads > that will provide links to one or maybe two forks of Matthews repo that > have been working. Not sure whether they continue to work or not. > > Gary > > On Friday, 13 May 2022 at 08:30:12 UTC+10 Barry wrote: > >> Thanks Gary, the last message stayed, so I'll plod on. I probably should >> start a new topic, but I don't want to tempt fate! >> Now looking for some assistance with installing a Weather Forecast >> display on the Belchertown skin. Again I have looked through various posts >> and sites but haven't found a definitive install process that works here. >> >> I am running Linux Mint on a dedicated Intel NUC for the moment, I'll >> move it across to a RPi when I have the basics working. >> This is what I’ve done so far: >> >> Got the “stock” BelcherTown skin. Weewx and WeatherFlow-UDP all playing >> nicely together and uploading data to my weather page. >> Setup PSW account and got an API key >> Setup forwarding to PSW >> [[PWSWeather] >> enable = true >> station = STRANDHERDMEADOWS >> password = xxxxxxxxxxxxxxxxx >> Data is being sent to PWS OK. >> >> Setup Aeris weather account and got both the ID and Secret key. >> >> Downloaded the forecast extension “weewx-forecast-master.zip” from >> https://github.com/matthewwall/weewx-forecast >> Then installed it >> sudo wee_extension --install weewx-forecast-master.zip >> >> There were no errors on install. >> >> When I then restarted weewx it seems to go through a cycle of data >> collection and then syslog gets a whole slew of messages: >> >> May 12 18:07:18 linux /weewxd: weatherflowudp: MainThread: raw packet: >> {'serial_number': 'ST-00062106', 'type': 'rapid_wind', 'hub_sn': >> 'HB-00071538', 'ob': [1652393236, 1.24, 196]} >> May 12 18:07:18 linux weewx[545399] INFO weewx.manager: Added record >> 2022-05-12 18:07:00 EDT (1652393220) to database 'weewx.sdb' >> May 12 18:07:18 linux weewx[545399] INFO weewx.manager: Added record >> 2022-05-12 18:07:00 EDT (1652393220) to daily summary in 'weewx.sdb' >> May 12 18:07:18 linux weewx[545399] INFO weewx.engine: Main loop exiting. >> Shutting engine down. >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: Caught >> unrecoverable exception: >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** '>' not >> supported between instances of 'float' and 'NoneType' >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> Traceback (most recent call last): >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 214, in run >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet)) >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> callback(event) >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 634, in check_loop >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> raise BreakLoop >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> weewx.engine.BreakLoop >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** During >> handling of the above exception, another exception occurred: >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> Traceback (most recent call last): >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 650, in post_loop >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> self._catchup(self.engine.console.genArchiveRecords) >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 697, in _catchup >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** for >> record in generator(lastgood_ts): >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/drivers/__init__.py", line 30, in genArchiveRecords >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> raise NotImplementedError("Method 'genArchiveRecords' not implemented") >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> NotImplementedError: Method 'genArchiveRecords' not implemented >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** During >> handling of the above exception, another exception occurred: >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> Traceback (most recent call last): >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewxd", line 153, in main >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> engine.run() >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 221, in run >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> self.dispatchEvent(weewx.Event(weewx.POST_LOOP)) >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> callback(event) >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 652, in post_loop >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> self._software_catchup() >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 715, in _software_catchup >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD, >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> callback(event) >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** File >> "/usr/share/weewx/user/forecast.py", line 1212, in update_forecast >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** elif >> time.time() - self.interval > self.last_ts: >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** >> TypeError: '>' not supported between instances of 'float' and 'NoneType' >> May 12 18:07:18 linux weewx[545399] CRITICAL __main__: **** Exiting. >> >> Anyone any thoughts on what the problem may be, I have never done any >> programming with Python, which is where the errors appear to be coming >> from. Even better, is there an idiots guide to installing the forecast >> capability out there. >> >> Many thanks, >> Barry >> >> >> >> On Thursday, May 12, 2022 at 3:20:44 p.m. UTC-4 gjr80 wrote: >> >>> Barry, >>> >>> I have no idea. Since I have been a group manager I have not seen one >>> quarantined post that actually was spam, all have been legitimate. I just >>> looked at the weewx-user group settings and the spam settings are as >>> relaxed as we can make them. Interestingly, there is a setting for >>> notifying users by email if their post is quarantined as spam, that setting >>> is enabled for weewx-user but clearly is not being applied. >>> >>> I have no idea what is likely triggering the spam filter, perhaps others >>> with wider Google groups knowledge have some idea. I don't know if there is >>> any difference in handling email based or web page based posts, nor do I >>> know if including the previous posts in a reply (the default) has an effect >>> (for brevity purposes I often delete/trim post history from my replies). I >>> only post via web page and have had only one of my posts go to quarantine, >>> fortunately it was relatively short so I just reworded the text and >>> re-posted and it went through fine the second time. >>> >>> My advice would be to keep at it, start a new thread and keep your posts >>> as succinct as possible. We will eventually see quarantined posts and deal >>> with them. >>> >>> Gary >>> >>> On Thursday, 12 May 2022 at 23:30:27 UTC+10 Barry wrote: >>> >>>> Thanks again Gary, any clue as to why my posts get quarantined? Is it >>>> something to do with the content, length etc or is it just on the whim of >>>> Google. It's frustrating as I'd like to try and get some help on including >>>> the forecast on my Web page (now, with help, I have got other parts >>>> working). >>>> >>>> Barry >>>> >>> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/887d3649-5f10-498f-968c-d194f69c305en%40googlegroups.com.
