Re: [weewx-user] Weewx 5.0.2 and Interceptor driver problem
Yup, station_type was left as Simulator! Changing it to Interceptor corrected that problem. Weewx still crashed with a permissions error, but I was able to get it up and running by changing the Interceptor listening port to 2055; ie above 1024. All working now. Thanks. Mike On Sunday 18 February 2024 at 15:31:04 UTC Tom Keffer wrote: > Check the value of option "station_type" and make sure it says > "Interceptor". > > If there's no obvious problem, then use the utility "weectl debug" to > create a sanitized version of weewx.conf. Post it. > > -tk > > On Sun, Feb 18, 2024 at 4:34 AM Redanman wrote: > >> Hi. I decided to upgrade to Weewx 5.0.2 this morning.The upgrade >> itself seemingly ran without errors. My system is a virtual machine >> running Debian 11 - Bullseye. >> >> However, on checking Weewx status, the program has exited with this error >> sequence in the syslog file >> >> Feb 18 12:16:08 debian weewxd[323]: INFO __main__: WEEWX_ROOT: /etc/weewx >> Feb 18 12:16:08 debian weewxd[323]: INFO __main__: Configuration file: >> /etc/weewx/weewx.conf >> Feb 18 12:16:08 debian weewxd[323]: INFO __main__: User module: >> /etc/weewx/bin/user >> Feb 18 12:16:08 debian weewxd[323]: INFO __main__: Debug: 1 >> Feb 18 12:16:08 debian weewxd[323]: DEBUG __main__: Initializing engine >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: Caught >> unrecoverable exception: >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: 'driver' >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: >> Traceback (most recent call last): >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File >> "/usr/share/weewx/weewxd.py", line 160, in main >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: >> engine = weewx.engine.StdEngine(config_dict) >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File >> "/usr/share/weewx/weewx/engine.py", line 77, in __init__ >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: >> self.setupStation(config_dict) >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File >> "/usr/share/weewx/weewx/engine.py", line 99, in setupStation >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: >> driver = config_dict[station_type]['driver'] >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File >> "/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__ >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: val >> = dict.__getitem__(self, key) >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: >> KeyError: 'driver' >> Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: Exiting. >> Feb 18 12:16:08 debian weewxd[323]: Traceback (most recent call last): >> Feb 18 12:16:08 debian weewxd[323]: File "/usr/share/weewx/weewxd.py", >> line 265, in >> Feb 18 12:16:08 debian weewxd[323]: main() >> Feb 18 12:16:08 debian weewxd[323]: File "/usr/share/weewx/weewxd.py", >> line 160, in main >> Feb 18 12:16:08 debian weewxd[323]: engine = >> weewx.engine.StdEngine(config_dict) >> Feb 18 12:16:08 debian weewxd[323]: File >> "/usr/share/weewx/weewx/engine.py", line 77, in __init__ >> Feb 18 12:16:08 debian weewxd[323]: self.setupStation(config_dict) >> Feb 18 12:16:08 debian weewxd[323]: File >> "/usr/share/weewx/weewx/engine.py", line 99, in setupStation >> Feb 18 12:16:08 debian weewxd[323]: driver = >> config_dict[station_type]['driver'] >> Feb 18 12:16:08 debian weewxd[323]: File >> "/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__ >> Feb 18 12:16:08 debian weewxd[323]: val = dict.__getitem__(self, key) >> Feb 18 12:16:08 debian weewxd[323]: KeyError: 'driver' >> Feb 18 12:16:08 debian systemd[1]: weewx.service: Main process exited, >> code=exited, status=1/FAILURE >> Feb 18 12:16:08 debian systemd[1]: weewx.service: Failed with result >> 'exit-code'. >> >> I am using the Interceptor driver, listening on port 55, so I shouldn't >> have to run Weewx as root? >> [Interceptor] >> # This section is for the network traffic interceptor driver. >> >> # The driver to use: >> driver = user.interceptor >> port = 55 >> device_type = observer >> >> I can run 5.0.2 if I use the simulator, so it just seems to
[weewx-user] Weewx 5.0.2 and Interceptor driver problem
Hi. I decided to upgrade to Weewx 5.0.2 this morning.The upgrade itself seemingly ran without errors. My system is a virtual machine running Debian 11 - Bullseye. However, on checking Weewx status, the program has exited with this error sequence in the syslog file Feb 18 12:16:08 debian weewxd[323]: INFO __main__: WEEWX_ROOT: /etc/weewx Feb 18 12:16:08 debian weewxd[323]: INFO __main__: Configuration file: /etc/weewx/weewx.conf Feb 18 12:16:08 debian weewxd[323]: INFO __main__: User module: /etc/weewx/bin/user Feb 18 12:16:08 debian weewxd[323]: INFO __main__: Debug: 1 Feb 18 12:16:08 debian weewxd[323]: DEBUG __main__: Initializing engine Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: Caught unrecoverable exception: Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: 'driver' Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: Traceback (most recent call last): Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File "/usr/share/weewx/weewxd.py", line 160, in main Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: engine = weewx.engine.StdEngine(config_dict) Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File "/usr/share/weewx/weewx/engine.py", line 77, in __init__ Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: self.setupStation(config_dict) Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File "/usr/share/weewx/weewx/engine.py", line 99, in setupStation Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: driver = config_dict[station_type]['driver'] Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: File "/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__ Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: val = dict.__getitem__(self, key) Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: KeyError: 'driver' Feb 18 12:16:08 debian weewxd[323]: CRITICAL __main__: Exiting. Feb 18 12:16:08 debian weewxd[323]: Traceback (most recent call last): Feb 18 12:16:08 debian weewxd[323]: File "/usr/share/weewx/weewxd.py", line 265, in Feb 18 12:16:08 debian weewxd[323]: main() Feb 18 12:16:08 debian weewxd[323]: File "/usr/share/weewx/weewxd.py", line 160, in main Feb 18 12:16:08 debian weewxd[323]: engine = weewx.engine.StdEngine(config_dict) Feb 18 12:16:08 debian weewxd[323]: File "/usr/share/weewx/weewx/engine.py", line 77, in __init__ Feb 18 12:16:08 debian weewxd[323]: self.setupStation(config_dict) Feb 18 12:16:08 debian weewxd[323]: File "/usr/share/weewx/weewx/engine.py", line 99, in setupStation Feb 18 12:16:08 debian weewxd[323]: driver = config_dict[station_type]['driver'] Feb 18 12:16:08 debian weewxd[323]: File "/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__ Feb 18 12:16:08 debian weewxd[323]: val = dict.__getitem__(self, key) Feb 18 12:16:08 debian weewxd[323]: KeyError: 'driver' Feb 18 12:16:08 debian systemd[1]: weewx.service: Main process exited, code=exited, status=1/FAILURE Feb 18 12:16:08 debian systemd[1]: weewx.service: Failed with result 'exit-code'. I am using the Interceptor driver, listening on port 55, so I shouldn't have to run Weewx as root? [Interceptor] # This section is for the network traffic interceptor driver. # The driver to use: driver = user.interceptor port = 55 device_type = observer I can run 5.0.2 if I use the simulator, so it just seems to be the issue with the Interceptor driver. Any ideas, what might have gone wrong? Mike -- 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/73c36018-632f-479b-8dd2-95eb01e94eban%40googlegroups.com.
[weewx-user] Weewx 4.1 and forecast extension
I've updated my Weewx to 4.0 and then 4.1 in the last few days and in doing so I've noticed that on each archive cycle there are 174 consecutive log messages of the type shown below : Jun 1 17:40:55 raspberrypi weewx[9275] DEBUG user.forecast: ReportThread: _get_stats: '>' not supported between instances of 'NoneType' and 'float' Jun 1 17:40:56 raspberrypi weewx[9275] DEBUG user.forecast: ReportThread: _get_stats: '>' not supported between instances of 'NoneType' and 'float' Weewx seems to be running fine and the forecasts are generated from Dark Sky, but I was wondering what is causing all these "errors". The forecast extension is version 3.4.0b. Weewx debug file is attached. Mike -- 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/f23d19b8-3d64-4b88-ac39-0e7377fa93f9%40googlegroups.com. weewx.debug Description: Binary data
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
Thank you. Problem solved (hopefully). Mike -- 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/405a6317-7bc8-40a5-9970-5d33d08e837c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
OK, that's done and I've checked that the cmon parameters are being written to the syslog. Let's see what happens. Mike -- 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/bd737b0c-6f4f-40f9-8294-b81e16022adf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
My system configuration is : Weewx version 3.9.1 running on a Raspberry Pi Zero Aercus Weathersleuth weather station with Weewx using Interceptor driver over local network PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=raspbian ID_LIKE=debian Kernel = 4.14.62+ #1134 Tue Aug 14 16:58:07 BST 2018 armv6l GNU/Linux cmon version = 0.16 Hope that helps. Mike -- 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/23f3e30d-5716-4edc-ad03-1842fb5247c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
Weewx crashed again tonight with what seems to be the same root cause.
Here is the syslog just at the moment it crashed. Again, looking at the
data, I cannot see any spurious text/numbers. Out of interest, is accum.py
run every iteration of the engine or only on an interval?
May 6 20:20:30 raspberrypi weewx[333]: interceptor: MainThread: raw
packet: {'wind_speed': 0.0, 'humidity_in': 43.0, 'temperature_in': 68.4,
'barometer': 30.15, 'windchill': 46.9, 'dewpoint': 40.5, 'battery': 0.0,
'humidity_out': 78.0, 'uv': 0.0, 'radiation': 0.15, 'rain': 0.0,
'dateTime': 1557170426, 'temperature_out': 46.9, 'wind_dir': 143.0,
'rain_total': 4.49, 'usUnits': 1, 'wind_gust': 0.0}
May 6 20:20:30 raspberrypi weewx[333]: interceptor: MainThread: mapped
packet: {'barometer': 30.15, 'windchill': 46.9, 'dewpoint': 40.5,
'outHumidity': 78.0, 'UV': 0.0, 'radiation': 0.15, 'rain': 0.0, 'dateTime':
1557170426, 'windDir': 143.0, 'outTemp': 46.9, 'windSpeed': 0.0,
'txBatteryStatus': 0.0, 'inTemp': 68.4, 'windGust': 0.0, 'inHumidity':
43.0, 'usUnits': 1}
May 6 20:20:30 raspberrypi weewx[333]: manager: Added record 2019-05-06
20:20:31 BST (1557170431) to database 'cmon.sdb'
May 6 20:20:30 raspberrypi weewx[333]: engine: Main loop exiting. Shutting
engine down.
May 6 20:20:30 raspberrypi weewx[333]: engine: Shutting down StdReport
thread
May 6 20:20:30 raspberrypi weewx[333]: engine: StdReport thread has been
terminated
May 6 20:20:30 raspberrypi weewx[333]: restx: Shut down WOW thread.
May 6 20:20:30 raspberrypi weewx[333]: restx: Shut down PWSWeather thread.
May 6 20:20:31 raspberrypi weewx[333]: restx: Shut down Wunderground-PWS
thread.
May 6 20:20:31 raspberrypi weewx[333]: restx: Shut down StationRegistry
thread.
May 6 20:20:31 raspberrypi weewx[333]: interceptor: MainThread: shutting
down server thread
May 6 20:20:31 raspberrypi weewx[333]: interceptor: MainThread: stop tcp
server
May 6 20:20:31 raspberrypi weewx[333]: engine: Caught unrecoverable
exception in engine:
May 6 20:20:31 raspberrypi weewx[333]: accum:
ScalarStats.addHiLo expected float or int, got 710464
May 6 20:20:31 raspberrypi weewx[333]: Traceback (most recent
call last):
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/engine.py", line 890, in main
May 6 20:20:31 raspberrypi weewx[333]: engine.run()
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/engine.py", line 202, in run
May 6 20:20:31 raspberrypi weewx[333]:
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
May 6 20:20:31 raspberrypi weewx[333]: callback(event)
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/engine.py", line 574, in post_loop
May 6 20:20:31 raspberrypi weewx[333]:
self._software_catchup()
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/engine.py", line 646, in _software_catchup
May 6 20:20:31 raspberrypi weewx[333]:
self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
record=record, origin='software'))
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
May 6 20:20:31 raspberrypi weewx[333]: callback(event)
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/user/cmon.py", line 704, in new_archive_record
May 6 20:20:31 raspberrypi weewx[333]:
self.save_data(self.get_data(now, self.last_ts))
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/user/cmon.py", line 711, in save_data
May 6 20:20:31 raspberrypi weewx[333]:
self.dbm.addRecord(record)
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/manager.py", line 246, in addRecord
May 6 20:20:31 raspberrypi weewx[333]:
self._addSingleRecord(record, cursor, log_level)
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
May 6 20:20:31 raspberrypi weewx[333]:
_day_summary.addRecord(record, weight=_weight)
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/accum.py", line 256, in addRecord
May 6 20:20:31 raspberrypi weewx[333]: func(self, record,
obs_type, add_hilo, weight)
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/accum.py", line 314, in add_value
May 6 20:20:31 raspberrypi weewx[333]:
self[obs_type].addHiLo(val, record['dateTime'])
May 6 20:20:31 raspberrypi weewx[333]: File
"/usr/share/weewx/weewx/accum.py", line 77, in addHiLo
May 6 20:20:31 raspberrypi weewx[333]: raise
ValueError("accum: ScalarStats.addHiLo
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
Sorry, negative on both counts. I've looked back in the syslog files and I cannot see any problems with the parsing of the interceptor data, or any sign of the value 645138 or 667872. The weewx.sdb file is full of numbers or null. The other thing i can mention is that a restart of weewx did not clear the problem, it needed a sudo reboot to get back to normal. Mike On Sunday, 28 April 2019 12:26:02 UTC+1, mwall wrote: > > On Sunday, April 28, 2019 at 2:29:41 AM UTC-4, Redanman wrote: >> >> I had Debug=1 when it crashed. I've gone back into the syslog archives >> and pulled out the section starting roughly 5 minutes before the last >> crash. At that point everything seems to be running fine. See attached. >> > > i do not see the value 645138 anywhere in that log snippet. could you see > if it is anywhere in the log prior to the exception you posted at the > beginning of this discussion? > > we're looking for it in one of the 'raw packet' lines > > also, you might want to query your database to see if there are any > strings in there. if you find one, then the timestamp of the record with > the string should give you some idea of when in the logs to look > > m > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
I had Debug=1 when it crashed. I've gone back into the syslog archives and
pulled out the section starting roughly 5 minutes before the last crash.
At that point everything seems to be running fine. See attached.
Mike
On Sunday, 28 April 2019 04:28:14 UTC+1, mwall wrote:
>
> could you set debug=1 then let weewx run until it crashes. we need to see
> the intercepted data and how those data are parsed and/or mapped to weewx
> database fields. tom is probably right - somehow the data are coming in as
> a string instead of an integer.
>
> m
>
--
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.
For more options, visit https://groups.google.com/d/optout.
Apr 25 18:55:11 raspberrypi weewx[331]: interceptor: MainThread: raw packet:
{'wind_speed': 2.24, 'humidity_in': 48.0, 'temperature_in': 69.8, 'barometer':
29.63, 'windchill': 57.4, 'dewpoint': 46.2, 'battery': 0.0, 'humidity_out':
66.0, 'uv': 1.0, 'radiation': 298.29, 'rain': 0.0, 'dateTime': 1556214910,
'temperature_out': 57.4, 'wind_dir': 165.0, 'rain_total': 4.16, 'usUnits': 1,
'wind_gust': 4.92}
Apr 25 18:55:11 raspberrypi weewx[331]: interceptor: MainThread: mapped packet:
{'barometer': 29.63, 'windchill': 57.4, 'dewpoint': 46.2, 'outHumidity': 66.0,
'UV': 1.0, 'radiation': 298.29, 'rain': 0.0, 'dateTime': 1556214910, 'windDir':
165.0, 'outTemp': 57.4, 'windSpeed': 2.24, 'txBatteryStatus': 0.0, 'inTemp':
69.8, 'windGust': 4.92, 'inHumidity': 48.0, 'usUnits': 1}
Apr 25 18:55:21 raspberrypi weewx[331]: interceptor: MainThread: empty queue
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: ServerThread: GET:
ID=Dummy==57.4=66=46.2=57.4=224=4.70=7.61=0.00=0.08=0.11=0.33=4.16=297.33=1=69.8=48=29.64=0=2019-04-25%2017:55:26=WH2600GEN_V2.2.7=updateraw=1=5
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: raw data:
ID=Dummy=dummy=57.4=66=46.2=57.4=224=4.70=7.61=0.00=0.08=0.11=0.33=4.16=297.33=1=69.8=48=29.64=0=2019-04-25%2017:55:26=WH2600GEN_V2.2.7=updateraw=1=5
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: using
rain_total 4.16 from yearlyrainin
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: firmware
WH2600GEN_V2.2.7: using baromin as barometer
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter rainin=0.00
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter monthlyrainin=0.33
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter realtime=1
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter rtfreq=5
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter PASSWORD=dummy
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter ID=Dummy
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter softwaretype=WH2600GEN_V2.2.7
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter action=updateraw
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: ignored
parameter weeklyrainin=0.11
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: raw packet:
{'wind_speed': 4.7, 'humidity_in': 48.0, 'temperature_in': 69.8, 'barometer':
29.64, 'windchill': 57.4, 'dewpoint': 46.2, 'battery': 0.0, 'humidity_out':
66.0, 'uv': 1.0, 'radiation': 297.33, 'rain': 0.0, 'dateTime': 1556214926,
'temperature_out': 57.4, 'wind_dir': 224.0, 'rain_total': 4.16, 'usUnits': 1,
'wind_gust': 7.61}
Apr 25 18:55:27 raspberrypi weewx[331]: interceptor: MainThread: mapped packet:
{'barometer': 29.64, 'windchill': 57.4, 'dewpoint': 46.2, 'outHumidity': 66.0,
'UV': 1.0, 'radiation': 297.33, 'rain': 0.0, 'dateTime': 1556214926, 'windDir':
224.0, 'outTemp': 57.4, 'windSpeed': 4.7, 'txBatteryStatus': 0.0, 'inTemp':
69.8, 'windGust': 7.61, 'inHumidity': 48.0, 'usUnits': 1}
Apr 25 18:55:27 raspberrypi weewx[331]: manager: Added record 2019-04-25
18:55:28 BST (1556214928) to database 'cmon.sdb'
Apr 25 18:55:27 raspberrypi weewx[331]: manager: Added record 2019-04-25
18:55:28 BST (1556214928) to daily summary in 'cmon.sdb'
Apr 25 18:55:37 raspberrypi weewx[331]: manager: Added record 2019-04-25
18:55:00 BST (1556214900) to database 'weewx.sdb'
Apr 25 18:55:37 raspberrypi weewx[331]: manager: Added record 2019-04-25
18:55:00 BST (1556214900) to daily summary in 'weewx.sdb'
Apr 25 18:55:42 raspberrypi weewx[331]: forecast: MainThread: WU: not yet time
to do the forecast
Apr 25 18:55:42 raspberrypi weewx[331]: forecast: MainThread: Zambretti:
starting thread
Apr 25 18:55:42 raspberrypi weewx[331]: forecast: MainThread: DS: not yet time
to do the forecast
Apr 25 18:55:42 raspberrypi weewx[331]: restx: StationRegistry: wait interval
(340500 < 604800) has not passed for record 2019-04-25
[weewx-user] Re: Weewx crashing with error associated with ScalarStats.addHiLo
For me it's an Aercus WeatherSleuth. The section of my config pertaining to this device is : [Interceptor] # This section is for the network traffic interceptor driver. # The driver to use: driver = user.interceptor port = 55 device_type = observer On Saturday, 27 April 2019 01:14:15 UTC+1, mwall wrote: > > On Friday, April 26, 2019 at 6:34:50 PM UTC-4, pliggen.is wrote: >> >> I also got the issue two days ago. Strange because I've been running for >> quite some time now and just the other day was my first crash. >> > > what kind of weather station? > > what is your interceptor configuration? (please post the [Interceptor] > section from your weewx configuration file) > > m > -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Weewx crashing with error associated with ScalarStats.addHiLo
Thank you for any possible insights into what might be causing Weewx to
occasionally crash. The relevant part of the syslog is :
Apr 26 08:20:32 raspberrypi weewx[7715]: File
"/usr/share/weewx/weewx/manager.py", line 1216, in _addSingleRecord
Apr 26 08:20:32 raspberrypi weewx[7715]:
_day_summary.addRecord(record, weight=_weight)
Apr 26 08:20:32 raspberrypi weewx[7715]: File
"/usr/share/weewx/weewx/accum.py", line 256, in addRecord
Apr 26 08:20:32 raspberrypi weewx[7715]: func(self, record,
obs_type, add_hilo, weight)
Apr 26 08:20:32 raspberrypi weewx[7715]: File
"/usr/share/weewx/weewx/accum.py", line 314, in add_value
Apr 26 08:20:32 raspberrypi weewx[7715]:
self[obs_type].addHiLo(val, record['dateTime'])
Apr 26 08:20:32 raspberrypi weewx[7715]: File
"/usr/share/weewx/weewx/accum.py", line 77, in addHiLo
Apr 26 08:20:32 raspberrypi weewx[7715]: raise
ValueError("accum: ScalarStats.addHiLo expected float or int, got %s" % val)
Apr 26 08:20:32 raspberrypi weewx[7715]: ValueError: accum:
ScalarStats.addHiLo expected float or int, got 645138
Apr 26 08:20:32 raspberrypi weewx[7715]: Exiting.
I have Weewx running on a Raspberry Pi Zero and my weather station is an
Aercus WeatherSleuth, so I am using the interceptor driver. The
installation was very stable until I upgraded to rev 3.9.1 a few weeks
ago. Now, every few days Weewx crashes on me.
--
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.
For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: FineOffset Hang ups
For anyone else struggling with this problem, the behaviour pattern of USB lock-ups has completely changed when I swapped the Pi power supply for a different one. My system was locking up at 1 to 2 day intervals on the old power supply; I am now at 10 days without a problem on the new power supply. It seems that the USB interface on the WH1080 is voltage (or current) sensitive. This would be consistent with the recommendation to use a powered USB hub. -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: FineOffset Hang ups
The insides didn't really tell me much. The 433Mhz cable was pinched by the case as I've seen already mention here already, but not such that it was cut. The USB connectors are permanent covered by the lead plugs, so there is no reason why grime would get in. I had a look anyway and they are immaculate. I changed the USB cable a little while back, but that had no effect. I'll try a different power supply for the Pi as their performance can drop off with time or maybe I'll try and find a powered hub from somewhere. On Monday, 11 December 2017 22:54:03 UTC, Redanman wrote: > > My old WH1080 is getting more more and more USB hang-ups. I have to reset > the unit (remove the USB cable) to reboot the it. I obviously lose the > data in the circular buffer, so, depending on when I notice the hang-up, it > leads to data loss of several hours or even days. > I power the WH1080 through the USB cable connected to my Pi, but I do not > have a USB hub, so cannot cycle the power through the hub. I have noticed > that if I reboot the Pi it cycles the power on the Pi's own USB ports, so > resetting the WH1080. Is it possible to do this automatically within Weewx > if it detects a USB hang-up? > Mike -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: FineOffset Hang ups
I'll have a look inside the console, I must admit that I have a habit of taking things to bits to see what's inside, but the weather station has sat there for 5 years and I've never taken a screwdriver to it. On Monday, 11 December 2017 22:54:03 UTC, Redanman wrote: > > My old WH1080 is getting more more and more USB hang-ups. I have to reset > the unit (remove the USB cable) to reboot the it. I obviously lose the > data in the circular buffer, so, depending on when I notice the hang-up, it > leads to data loss of several hours or even days. > I power the WH1080 through the USB cable connected to my Pi, but I do not > have a USB hub, so cannot cycle the power through the hub. I have noticed > that if I reboot the Pi it cycles the power on the Pi's own USB ports, so > resetting the WH1080. Is it possible to do this automatically within Weewx > if it detects a USB hang-up? > Mike -- 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. For more options, visit https://groups.google.com/d/optout.
[weewx-user] Re: FineOffset Hang ups
I've already tried 2 and 3. I could procure a powered hub but I assumed that the power_cycle_station code in fousb.py was there for all those people for whom your 3 steps did not resolve the problem. For the time being I've modified my config to pretend that I have a powered USB hub and rather than calling power_cycle_station when the console hangs I have added a line to reboot the Pi. I'll see what that does. On Tuesday, 12 December 2017 14:16:36 UTC, Andrew Milner wrote: > > 1. Do not use the rpi usb port directly, use a powered hub to power the > station (but I also keep batteries in the station)- even if you cannot > switch the port on and off > 2. Ensure the usb cable to the station goes nowehere near power supplies > or screens - route it carefully away from all sources of possible > interference. > 3. Consider magnetic rings for the usb lead - again to reduce interference > issues > > Following the above 'rules' my Fine Offset very rarely 'locks up', and in > fact I cannot remember when I last had a problem - so have never needed to > use the powered hub reset method. > > It seems to me that one is better solving the cause, or minimising the > chances of lock up occurring, rather than focussing on recovery methods. > > > > On Tuesday, 12 December 2017 14:31:42 UTC+2, Redanman wrote: > >> Yes, I did look at the Wiki on FineOffset lock-ups, but as I mentioned in >> post I do not have a powered hub. A solution for me seems to be intimated >> in the latter part of the post with a dedicated scripted to look at the >> syslog file and react to the specific message related to USB hang-ups. The >> Pi shuts downs in a coordinated fashion and then a 555 watchdog restarts >> the Pi. That would work for me although I would prefer to just do "sudo >> reboot" rather than mess with a 555 circuit. I was hoping for some more >> details on this solution. >> >> On Tuesday, 12 December 2017 08:58:16 UTC, Thorsten Wöll wrote: >>> >>> Take a close look here: >>> >>> https://github.com/weewx/weewx/wiki/FineOffset-USB-lockup >>> >>> Am Montag, 11. Dezember 2017 23:54:03 UTC+1 schrieb Redanman: >>>> >>>> My old WH1080 is getting more more and more USB hang-ups. I have to >>>> reset the unit (remove the USB cable) to reboot the it. I obviously lose >>>> the data in the circular buffer, so, depending on when I notice the >>>> hang-up, it leads to data loss of several hours or even days. >>>> I power the WH1080 through the USB cable connected to my Pi, but I do >>>> not have a USB hub, so cannot cycle the power through the hub. I have >>>> noticed that if I reboot the Pi it cycles the power on the Pi's own USB >>>> ports, so resetting the WH1080. Is it possible to do this automatically >>>> within Weewx if it detects a USB hang-up? >>>> Mike >>> >>> -- 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. For more options, visit https://groups.google.com/d/optout.
