On Tuesday, 19 March 2019 07:57:06 UTC+10, engolling wrote: > > Hi Gary, > thanks for your patience. > > This is not normal operation. Because something it triggering an archive >> record to be saved every few seconds the NEW_ARCHIVE_RECORD event is also >> triggered which causes your service to fire as well. The issue here is not >> your service but whatever is causing this archive record to be written >> every few seconds. I suggest we step back a bit and get a clear picture of >> how your system is configured and what it is running. >> > > I was wondering where these errors where coming from and I already tried > to get more information about it. I found somewhere a statement that is not > too bad and might happen if a very narrow saving interval is used. But now > I increasingly understand... >
Errors involving 'Unable to add record' are not good and are a sign something is wrong, at the very least you are wasting processor time, something you probably should avoid with such a short archive interval. A short archive interval should not be the cause in itself On Tuesday, 19 March 2019 08:21:12 UTC+10, engolling wrote: > One more thing - I do not own a original davis station - I'm using a > WeatherDuino, emulating a davis station for import of "standard" data. > https://www.meteocercal.info/forum/index.php > OK, not saying that is the issue but it is another complicating factor. Your weewx.conf looks fine and I don't see anything in your service that would be causing the archive record problem. Let's step right back to basics and disable your service so that you have WeeWX running just the vantage driver to talk the WeatherDuino. To do this: 1. edit weewx.conf, and change: [Engine] [[Services]] # This section specifies the services that should be run. They are # grouped by type, and the order of services within each group # determines the order in which the services will be run. prep_services = weewx.engine.StdTimeSynch data_services = user.WeeWx_WeatherDuino_Logger_plugin.WeeWxService, process_services = weewx.engine.StdConvert, weewx.engine. StdCalibrate, weewx.engine.StdQC, weewx.wxservices.StdWXCalculate to [Engine] [[Services]] # This section specifies the services that should be run. They are # grouped by type, and the order of services within each group # determines the order in which the services will be run. prep_services = weewx.engine.StdTimeSynch data_services = , # user.WeeWx_WeatherDuino_Logger_plugin.WeeWxService, process_services = weewx.engine.StdConvert, weewx.engine. StdCalibrate, weewx.engine.StdQC, weewx.wxservices.StdWXCalculate 2. save weewx.conf 3. restart WeeWX and let it run for 10 minutes or so then take a copy of the log from when WeeWX was restarted and post it here, make sure you capture the full WeeWX startup This should show us whether the WeatherDuino/vantage driver is causing the problem or if it is your service. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
