Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wgust history error rtgd version 0.5.5 #27

Open
kskenyon opened this issue Apr 26, 2022 · 6 comments
Open

wgust history error rtgd version 0.5.5 #27

kskenyon opened this issue Apr 26, 2022 · 6 comments

Comments

@kskenyon
Copy link

windGust data should be coming into the buffer but...

INFO user.rtgd: rtgdthread: **** Traceback (most recent call last):
INFO user.rtgd: rtgdthread: **** File "/usr/share/weewx/user/rtgd.py", line 1889, in process_packet
INFO user.rtgd: rtgdthread: **** data = self.calculate(cached_packet)
INFO user.rtgd: rtgdthread: **** File "/usr/share/weewx/user/rtgd.py", line 2157, in calculate
INFO user.rtgd: rtgdthread: **** wgust = self.buffer['windGust'].history_max(ts, age=600).value
INFO user.rtgd: rtgdthread: **** AttributeError: 'NoneType' object has no attribute 'value'

@gjr80
Copy link
Owner

gjr80 commented Apr 26, 2022

I'm going to need more information. What version of WeeWX? What station and driver? Does the error occur immediately on startup or sporadically? Is this a new install or has it been working in the past? A debug log will help answer a number of these questions - refer to this WeeWX Wiki entry on how to get a good log extract.

@kskenyon
Copy link
Author

kskenyon commented Apr 29, 2022

Weewx 4.8.0
rtgd.py 0.5.5
MQTTSubscribe.py in Driver mode.
python 3.7.3

Everything is working fine without rtgd.py. This error seems to stop the loop.

@msman0
Copy link

msman0 commented Apr 2, 2023

Hi, is a solution for these problem? I have changed my weatherstation and now I have the same error.
With TE923 it works, with Weatherflow not.
weeWX 4.10.2
latest RTGD version 0.6.2
Thank you!

@gjr80
Copy link
Owner

gjr80 commented Apr 2, 2023

No there is no solution, happy to look into it but I will need more information. With your system set to use weather flow can you:

  1. Provide a log extract with debug = 1. To do this edit weewx.conf, set debug = 1, save weewx.conf and restart WeeWX. Let WeeWX run for at least a couple of archive periods or until the error occurs. Take a WeeWX log extract covering from when you restarted WeeWX through until the the two archive periods have elapsed or the error occurred. Please provide the full log extract, don't edit/delete anything. If you need help getting a log extract this WeeWX wiki entry may help.
  2. Stop WeeWX and run WeeWX directly. This will display loop packets (LOOP: lines) and archive records (REC: lines) on screen. Let WeeWX run for at least one archive period and then copy and post the screen output here. If WeeWX hits an error the output will stop, in that case post the output from when WeeWX starts until it hits the error.

@gjr80
Copy link
Owner

gjr80 commented Apr 3, 2023

Actually, I think I may have found the issue. Can you try rtgd.py v0.6.3 as follows:

  1. rename you existing rtgd.py to rtgd_orig.py or something else, rtgd.py should be in /home/weewx/bin/user or /usr/share/weewx/user depending on your WeeWX install

  2. download rtgd.py v0.6.3 and save it in place of the old rtgd.py using the following command:

$ wget -P /home/weewx/bin/user https://raw.githubusercontent.com/gjr80/weewx-realtime_gauge-data/master/bin/user/rtgd.py

changing /home/weewx/bin/user to /usr/share/weewx/user if required, you may also need to prefix wget with sudo, again depending on your install

  1. restart WeeWX

  2. monitor the WeeWX log for errors, if any occur please make a copy of the log and post back here

@msman0
Copy link

msman0 commented Apr 3, 2023

Thank you very much. I have done the steps and until now no error message appeared.
Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants