-
Notifications
You must be signed in to change notification settings - Fork 3
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
(removed) #3
Comments
(removed) |
Is this happening for every single report cycle or only sometimes? For me the reporting is working properly, w/ debug=2 I see entries like this:
Can you please set your instance to debug=2 and provide relevant excerpts from your own logs that show the call and hopefully include the error response from windguru? As suggested in the Google group, does seem like there might be a configuration issue on your end, since no data is being sent. Though Why that would only apply to this one publisher, I'm not sure. |
Ok - thank you for responding so quickly - I updated weewx.conf to debug = 2, then pi@kruse-pi:~$ sudo /etc/init.d/weewx restart and then immediately pi@kruse-pi:~$ sudo tail -f /usr/share/hassio/share/weewx.log | grep -E "uru" resulted in: pi@kruse-pi:~$ sudo tail -f /usr/share/hassio/share/weewx.log | grep -E "uru" Around the same time, here are some of the others - that ARE getting data =- Nov 15 23:00:29 kruse-pi weewx[286087] DEBUG weewx.restx: Wunderground-PWS url: 'https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=##########&PASSWORD=########&softwaretype=weewx-4.9.1&dateutc=2022-11-16%2004%3A00%3A00' Thoughts? How can I debug on the fly - where would the source be and not sure if I would be able to determine this issue - but ? It worked for a little while. I weas thinking of just reinstalkling Weewx from scratch, but I have alot of customizations such as moving the weewx log to usr/share/hassio/share/ alopng with the systelog so that Home assistant in a docker container can use it for log scraping etc.... ugh I can just do a full backup and then try to resintalkl from scratch and just copy over my suctomizations from the backup copy... but then I was thinking what is the problem stll remains? Thoughts? There must be a "next step" for debugging.... doe the WindGuru rely upon anything that the others do notr such as some kind of an environment variable that got changed somehow? What do you think? |
The other uploaders aren't erroring out, but it seems like no data is being provided there, either, they're all only getting meta data, not observational data. I think you're using an interceptor style setup? You should be seeing log entries for when that data is received. Is any being received, at all? Perhaps the data mapping has a problem? There should be log entries that tell you what data weewx has in its current loop for submission. |
Yikes I just realized that, I'm going to do a full backup and then uninstall and reinstall (and then just get config files from the backup). Thanks for your help - I am surprised all the other sites don't reject the messages as empty - |
Nevermind, there is an issue I have already logged (109) that is the source of this, so closing this for now |
No description provided.
The text was updated successfully, but these errors were encountered: