I was using Chrome, but I haven't had this issue again.... I don't believe this is a Weewx issue but was hoping there was someone that had seen this type of symptom before. We'll see if it happens again....
Thanks everyone. Troy On Saturday, February 15, 2020 at 10:05:18 PM UTC-7, Andrew Milner wrote: > > what browser are you using?? I have found recently that microsoft edge > seems to have entered a world of its own and now appears to require > frequent forced refresh of pages to get the png's to update (Using shift/ > refresh) This has been happening for the past 2-3 weeks and was never > needed before. > > > > On Sunday, 16 February 2020 02:05:37 UTC+2, Troy Lass wrote: >> >> Ok, let me start over. It's working properly now and it worked properly >> for 2 days then froze, the page was stuck with on the previous day and >> time. The images were being written but the data was not updating. >> >> I did the following.... >> weewx stop >> wee_device --info >> wee_device --start >> weewx start >> >> After this the data was pulled from the data logger as expected but for >> something like 2 hours the png files were not updated for the base >> index.html file, even though the images for the /mobilephone were being >> updated. after some time, over an hour, the images started to be updated >> with no further action from me. If it just takes a while for it to get >> caught up I'm good, however I don't understand why I keep getting the page >> frozen on a day/time. This is what started the whole debugging process >> before and caused me to think the data logger was bad. >> >> When I ran on the console bypassing the datalogger with the following in >> the weewx.conf it ran without freezing but that was only while I was >> waiting for the new datalogger so only a couple days. >> >> record_generation = software >> no_catchup = True >> >> When I opened this post the png images were not updating, but now they >> are and have been for a day. >> >> What could cause the base page to keep from updating and it seems that a >> wee_device --start fixes? I'm wondering if there may be an issue with the >> envoy I'm using now that could cause it to stop updating that would need a >> --start? >> >> -- 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/3144be19-bc49-4e30-857d-24cc4a93af1b%40googlegroups.com.
