The point of running Weewx directly was to see the loop and archive data that Weewx is processing and you can then reconcile this against what is appearing on WU. If you set debug=2 you will see the data posted to WU on the log. This was never going to fix anything, rathet if will provoke a complete picture of what data is being received/processed by WeeWX and posted to WU.
Suggest you set debug=2 if not already done, restart WeeWX and post a log extract covering a good 2 to 3 archive intervals. A sanitised copy of weewx.conf would help too. You can use wee_debug for this just check the output before posting. 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/a7cfa0ae-326d-4ff8-9fb0-8f17b5ecdf73%40googlegroups.com.
