It's always said that -- I never explicitly requested "hardware generation" 
-- I'll try adding  record_generation = software   explicitly

last restart before "upgrade" when all was well:    Aug 14 15:17:11 
raspberrypi weewx[654]: engine: Record generation will be attempted in 
'hardware'
post-upgrade:                                                        Aug 15 
22:01:18 raspberrypi weewx[29842]: engine: Record generation will be 
attempted in 'hardware'

hardware is the default and comments suggest it will use hardware in 
devices that support it -- software if not...    But I've added the 
following:

    # 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
*    record_generation = software*

Log now reports this:

Aug 16 09:56:18 raspberrypi weewx[2791]: engine: *Record generation will be 
attempted in 'software'*

No change in behavior -- still getting data, storing records and generating 
web pages -- but no publish...

I'm wondering if something in all the linux updates (not updated for 
several months) changed -- python or some library weewx uses...


On Thursday, August 16, 2018 at 8:15:00 AM UTC-4, gjr80 wrote:
>
> Let's try that again.
>
> Hi,
>
> Any reason you are using hardware record generation? As far as I am aware 
> the AcuRite stations only emit loop packets (in fact the AcuRite driver 
> does not have a genArchiveRecords() method necessary to generate archive 
> records from the hardware). Suggest you try setting record_generation = 
> software under [StdArchive] in weewx.conf. Once you make  the change you 
> will need to restart weeWX.
>
> 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.

Reply via email to