On Sunday, April 16, 2017 at 7:47:21 PM UTC-4, Nicolas Cazan wrote: > Apr 16 15:08:28 raspberrypi weewx[1802]: engine: Record generation will be > attempted in 'hardware' > Apr 16 15:08:28 raspberrypi weewx[1802]: engine: The archive interval in > the configuration file (300) does not match the station hardware interval > (60). > Apr 16 15:08:28 raspberrypi weewx[1802]: engine: Using archive interval of > 60 seconds (specified by hardware) >
there it is, as gary suggested. the archive interval is 60 seconds, so if any of the sensors do not report within a 60 second window, the corresponding archive record will have None/NULL values for that sensor. you can change the hardware archive interval to 300 seconds, or set record_generation=software and archive_interval=300 in the weewx configuration. or run weewx directly in order to figure out why some of your sensors are not reporting within every 60 seconds. > Apr 16 15:08:52 raspberrypi weewx[1802]: wmr200: MainThread: W Clock time > unsynchronized > the unsynchronized clock will probably cause problems with historical data. this might be the source of all the 'NOT NULL constraint failed' messages (perhaps someone more familiar with the wmr200 driver could say more?) > Apr 16 15:08:52 raspberrypi weewx[1802]: wmr200: MainThread: W Wind > sensor: Battery low > if the console is not receiving wind data properly, this could be the reason. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
