You never said that it recovered by itself after 0100 - in fact you gave the impression that it only started working again after you stopped weewx, restored an old database and restarted weew and that then it did the backfill and recovered. Well that is how I understood your posts anyway.
On Wednesday, 7 August 2019 14:33:05 UTC+3, Michi Kaa wrote: > > > > Am Mittwoch, 7. August 2019 09:20:27 UTC+2 schrieb Andrew Milner: >> >> do you have a rogue dateTime in the database? >> >> > Not that I'm aware of. > > >> The log you posted ONLY has database records added at 22:00, 23:00, 24:00 >> and a message every 10 minutes saying there is no new data - press SET to >> resynch. I repeat - how do you know that it has reconnected?? >> > > Well, the log tells me so, if I understand it correctly. At 22:00 it tells > me it added the 21:05 record. After that (22:10:21) it tells me it didn't > have contact with console for 617 seconds. Before that (21:51:14) it didn't > have contact to console for 3071 seconds so it was connected in between > because it resetted the "no contact since" value. After 01:00 there where > records added every 5min again and the problem hasn't shon up again since. > > >> No new data implies that it has NOT connected. I see no evidence of a >> record being generated every 5 minutes. >> > > This part of the log I didn't consider relevant. But take a look at the > graph in post #2: you can see that there are beiing records up unti 20:00, > the three single values between 20:00 and 01:00 and after 01:00 everythings > looks normal again. > > >> >> I believe you have not, despite what you think, actually regained normal >> communication - either that or there is a record with an 'in the future' >> dateTime in the database. The fact that you can recover by restoring an >> old backup implies that your problem is probably caused by the wrong >> dateTime associated with a record, and no data can be found with a dateTime >> greater than what is in the database - so no backfill is performed. >> > > I believe, better: I know normal connection was regained at 01:00 - this > part of the log I didn't consider relevant. > > >> >> You could try running with debug = 1 set to see if more information can >> be found or you can keep a backup of the database which will not backfill >> and investigate what the last record contains for dateTime. >> > > I think I'd be better off reproducing a connection loss by moving console > out of range of the USB dongle but in range of the outside unit which > transmitts wheather data to console. > > >> >> >> >> On Wednesday, 7 August 2019 09:33:12 UTC+3, Michi Kaa wrote: >>> >>> >>> >>> Am Montag, 29. Juli 2019 13:19:05 UTC+2 schrieb Andrew Milner: >>>> >>>> are you certain it has reconnected?? >>>> >>>> >>> Yes. The log portion above is copied "as is" from weewx.log and I didn't >>> touch anything before or after. >>> >>> >>>> the archive records are only being generated at 1 hr intervals - is >>>> this correct?? >>>> >>>> >>> No, records are beeing generated every 5 mins. But since the connection >>> to the console was interrupted, there was no data available hence no >>> records being generated in the affected time window. >>> >>> >>>> there does not appear to be any communication between archive events - >>>> very strange. >>>> >>> >>> No connection - no communication. It is a 868MHz USB dongle which >>> connects the Raspi to the console OTA. Y >>> >>> >>>> The log message instructs you to resynch by pressing SET - did you do >>>> that?? >>>> >>>> >>> No, I didn't, I didn't touch anything. Connection was regained without >>> resynch. >>> >>> >>>> I am far from convinced this is running as you intend - generating >>>> updates only once per hour?? >>>> >>> >>> It is running as intendend for over four years now with > 99,9% data >>> completeness every 5 mins. I observed connection losses like this maybe >>> once or twice before and backfilled the missing data as described above. >>> I'd expect weewx to backfill data after connection loss and connection >>> regain without any interaction. But something in the database prevents >>> weewx from getting the missing data from the console. It acts like there is >>> no data, When you restore the database to a point before the connection >>> loss happened, weewx reads console data from the affected time windows >>> without any problem. >>> >>> >> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2e8a5a77-995b-4268-a9d5-0857c1d72ee6%40googlegroups.com.
