One more thing, are you presently running under python 3? if so make sure you have the pulled down the latest from the master branch, I pushed a fix for report timing under python 3 on 15 Feb. If this is your problem it will be quite evident when you look at a debug log.
Gary On Saturday, 22 February 2020 09:26:49 UTC+10, gjr80 wrote: > > The report timing mechanism has no involvement with any skin code, it > simply looks at the report_timing option and the timestamp of the current > record and determines whether to call the skin or not. > > Mike, can you set debug = 1 in weewx.conf then restart WeeWX. Let WeeWX > run for 15 minutes and post a log extract showing at least two consecutive > report cycles, in this case the report cycle portion rather than the > startup portion of the log is important. > > Gary > > On Saturday, 22 February 2020 09:11:59 UTC+10, vince wrote: >> >> On Friday, February 21, 2020 at 2:52:39 PM UTC-8, Mike Revitt wrote: >>> >>> I have created a skin to backup my sqlite database file daily but it >>> runs every archive period. Any advice on what to change to make this work >>> >>> >>> >> Can't say without seeing your skin's python code, but I'd "guess" that >> it's not reading your report_timing values and acting accordingly. >> >> You also have "attempts" spelled incorrectly in your logging :-) >> >> Personally I'd just do this from cron outside weewx as a far simpler >> solution, but it would be interesting to see your code. >> > -- 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/11fb2457-d37e-422c-8ea8-257324c5b0a5%40googlegroups.com.
