I'm not sure what happened but I did reply to this topic a few days ago with an explanation of what was happening. So here I go again....
Firstly - please DON'T delete the historical records from the console. While that does get WeeWx to again read the current data, it is not necessary given the faults I've found. As long as the console is powered on and working, it will be storing the historical records that can be retrieved by the fixed driver. True, you won't get the data into WeeWx right now but you will soon. The issue seems to stem from the HP1000 console firmware showing 0 historical records for 2024 - there are valid record counts for previous years (at least on my console back to 2017). Of course these are only used when WeeWx tries to 'catch up' any historical records it has missed since the last time it was connected to the console. (Normal, on-going data is not affected.) When the driver saw the '0' record count, it was not expecting this and mishandled the requests for historical record. Basically it sent a request that was never responded to the console but it also never timed out while waiting for that response. The historical are actually there but just not reported by the console when asked for the year-by-year historical record count. I now detect when that situation arises and use the current date to 'guess' at the number of records. I also allow for a timeout if there is not response from the console. All this seems to work OK (at least for me). I'm now looking at the code changes needed to make the driver V5 compatible and I'm hoping the new driver will be available in the next few days. Susan On Wednesday 17 January 2024 at 8:32:59 am UTC+11 Susan Mackay wrote: > A problem has recently been found with the HP1000 (WS1001, XC0422) driver. > While the driver will continue to work correctly, if it is restarted then > it will hand trying to retrieve the 'historical' records from the console.. > (A 'solution' has been mentioned by some that involves deleting the > historical records form the console and relying on the data held in the > WeeWx database. I don't recommend this approach.) > I am looking into the issue and I will post an updated version of the > driver as soon as I can. > I also will bring the driver into compliance with the WeeWx V5 driver > requirements. I've heard that it does work under V5 but that it is missing > something for a new installation. > Susan > -- 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/e4975658-9a4c-4240-b37b-4a06c4cc5988n%40googlegroups.com.
