I will preface this up front that I am not a TE923 user but I think the use of hardware record generation may be contributing to the problem... reading the TE923 <http://weewx.com/docs/hardware.htm#te923_notes> section in the Hardware Guide <http://weewx.com/docs/hardware.htm> I see that it says
The TE923 driver will read history records from the station when weewx > starts up, but it does not support hardware record generation. But in the weewx.conf you posted you have told weewx to use hardware record generation: [StdArchive] > > # If the station hardware supports data logging then the archive > interval > # will be downloaded from the station. Otherwise, specify it (in > seconds). > archive_interval = 300 > > # How long to wait (in seconds) before processing new archive data. > Must > # be greater than zero. > archive_delay = 15 > > # If possible, new archive records are downloaded from the station > # hardware. If the hardware does not support this, then new archive > # records will be generated in software. > # Set the following to "software" to force software record generation. > record_generation = hardware > > # Whether to include LOOP data in hi/low statistics > loop_hilo = True > > # The data binding used to save archive records > data_binding = wx_binding > I am not sure of the exact impact this would have on weewx. But I suspect it would have some difficulty in producing an archive record and the archive record is what is stored in your archive and the WU updater will be looking at the archive record for updating WU. I could certainly see this causing problems for updating WU. If you have a look at a log extract you posted early on there are long periods of time when no actual archive record is produced and saved to the database. My suggestion is to: 1. stop weewx 2. set record_generation = software in weewx.conf [StdArchive] 3. set debug = 1 in weewx.conf 4. clear the TE923 memory using wee_device (refer to the TE923 <http://weewx.com/docs/hardware.htm#te923_notes> section in the Hardware Guide <http://weewx.com/docs/hardware.htm>) 5. start weewx 6. monitor the logs/WU and see how that goes. If posts to WU fail again, post the log from weewx startup until the failure. To make reading the logs a bit easier you might want to consider setting your system to use a separate log file for weewx. The steps are quite simple and are described in the weewx wiki here <https://github.com/weewx/weewx/wiki/logging> (if you do implement this make sure you setup the logrotate part as well). 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.
