[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Thanks for taking the time and putting in the effort to troubleshoot. On Tuesday, June 30, 2020 at 8:47:25 AM UTC-4, Jacques Terrettaz wrote: > > HI, > > I checked with my Davis station and I am observing exactly the same kind > of differences. I think the problem is coming from the vantage

Re: [weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Thanks Gary. I have an application that reads the console values which are pushed to a Mosquitto MQTT server in real time so this will address the issue until the update is out. On Wed, Jul 1, 2020 at 01:20 gjr80 wrote: > Just to close this off I installed the updated vantage driver on my

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Just to close this off I installed the updated vantage driver on my system and sunrise/sunset from the console is spot on today. If the anomaly bothers you and you can't wait for 4.1.2 to be released you can download the patched vantage driver here

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Fixed at commit e8a5015 . Gary On Tuesday, 30 June 2020 22:55:52 UTC+10, gjr80 wrote: > > Ah, well spotted. This will be a python2/python3 issue. In python 2 / is > integer division if both operands are integers.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Ah, well spotted. This will be a python2/python3 issue. In python 2 / is integer division if both operands are integers. But in python3 / is floating point division irrespective of the operands. So the vantage driver would have worked correctly for WeeWX v3.x as well as for v4.x under python2.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

HI, I checked with my Davis station and I am observing exactly the same kind of differences. I think the problem is coming from the vantage weewx driver : Here are my data concerning sunrise : - the console displays 05:46 for sunrise. This is correct - the raw loop data for sunrise, as

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Not much else to check, timezone and daylight saving could affect it but you would expect to see variations of an hour (or perhaps 30 minutes if you are in a weird timezone). Out of interest I just checked the loop sunrise and sunset values for my console. Sunrise according to the console is

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

I did what you suggested (settings where fine to begin with) but still getting 20min discrepancies which are not explained by the loss of accuracy on the lon/lat. Wondering what to try next. On Tuesday, June 30, 2020 at 6:44:53 AM UTC-4, gjr80 wrote: > > No problems, it's just that

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

No problems, it's just that sunrise/sunset can come from up to three different sources and you need to to know which source is the problem in order to troubleshoot. You are right that the sunrise/sunset in loop packets comes from the console. So in this case pyephem does not come into play

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

My bad, I should have been more thorough with details. I was under the impression that the sunrise/sunset times were provided directly by the Davis console and not calculated. The values I am getting are coming from the LOOP when running weewxd LOOP: 2020-06-30 06:07:56 EDT (1593511676)

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

Hi, I think we need to sort the apples from the oranges and bananas. Exactly what are you showing us? Is that the sunrise/sunset times as displayed on the console or as displayed in loop packet/archive record or as returned by a tag in a report? What latitude/longitude do you have set in your