gdt
commented
4 months ago Thanks very much for merging the big fix and addressing the two buglets. I upgraded to v1.1.5. This log snippet shows both fixes in action. This has happened twice in the last 6h.
Jun 22 12:56:23 ${HOSTNAME} -: weewx[846] ERROR user.weatherlink_live.davis_http: HTTPConnectionPool(host='weatherlinklive.lan', port=80): Max retries exceeded with url: /v1/real_time?duration=1500 (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x68ef3410>: Failed to establish a new connection: [Errno 61] Connection refused'))
Jun 22 09:15:53 ${HOSTNAME} -: weewx[846] ERROR user.weatherlink_live.davis_http: HTTP broadcast start request failed. Retry #1 follows shortly
Jun 22 09:15:56 ${HOSTNAME} -: weewx[846] ERROR user.weatherlink_live.davis_http: Successfully sent broadcast start request after 2 attempts
Obviously we don't want to loudly log every successful fetch, but after there are N/N timeouts and a log message indicating failure for now, there should be a log message at that same priority when there is a successful fetch. More or less, separate from the timeout messages, a high-priority "Communications lost" and "Communications restored".