Jim Easterbrook
Jim Easterbrook
No idea, sorry. It sounds as if your weather station is defective. Can you try it with "EasyWeather" on Windows?
Won't this break existing setups? Other mqtt users appear to be happy with it as it is, and any user can customise the data sent by editing their weather.ini.
Thanks. The whole mess of timezone computations needs an overhaul anyway. I'll add the pytz dependency as part of that.
I agree. pywws uses UTC for all time stamps etc, with conversions to/from local time where needed. Things get a bit more complicated with things like graph axes, where gnuplot...
Looking at that commit to tzlocal it seems that they're dropping pytz in favour of `zoneinfo`, which appears to be backported from Python 3.9. I'm only using pytz directly for...
I'm going to try and strip out everything pywws doesn't need, then decide what's needed for a useful test routine. `tzlocal` is the simplest way to get the user's time...
Yes, a lot of the reasons for using tzlocal and pytz disappear with PEP 495 which is implemented in Python 3.6 and after. https://www.python.org/dev/peps/pep-0495/
Commit 952dd9e switches everything over to using a new `time_zone` object introduced in commit ad58ca0. If anyone wants to test this (particularly if you live a long way from Greenwich)...
I haven't removed the old timezone stuff yet, just in case I need a fallback. Eventually the only dependency on pytz will be via tzlocal, if using a version before...
Which pywws data file? (raw, hourly, ...) What period is the station console showing? (hour, 24 hour, ...)