Well I am stumped. The repeat packets seem to be in a reasonably regular routine, a few HTTP GETs followed by a HTTP POST. I can accept that since you are fooling your station into thinking the interceptor driver is WU your weather station may not be seeing the exact response it expects and that causes it to resend the data or try HTTP POST.
Looking at that last log extract I can see the 8pm archive record being saved, so that accounts for 8pm appearing on your page. The interceptor started deeming some of those duplicate packets as out of order and discarding them (interceptor accepts packets if the timestamp is greater than or equal to the last packets timestamp, anything else is dropped). I can’t see why it suddenly started dropping packets. Since no packets are getting through (after 8pm) no archive records are generated and hence no report cycle and the generated Seasons page doesn’t change. I expect that later some packets will be accepted and things will seem to work for a while. Noteworthy that this is a different symptom to yesterday where the page date-time was jumping ahead. Would be good to get Matthew’s view (interceptor author) but I know he is busy with other things. Only other suggestion I have is to maybe reconfigure your network to have your weather station update WU and have WeeWX use the interceptor driver to sniff the packets being sent to WU. Haven’t done that myself so I am not sure how feasible it is. 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ae8daaaf-ceab-4e82-b52f-9b141b8ff3af%40googlegroups.com.
