Publishing Issue

[Douglas Cote]

After upgrading to weewx 4.7.0, it seems I can only publish to Weather Underground whereas before I was publishing to PWSweather as well. I thought maybe because I had tried to add OpenWeatherMap as another publishing location it broke the PWS RESTful service. When I commented out the user.owm.OpenWeatherMap RESTful service definition and restarted weewx it was still refusing to publish to PWS. I did have debug = 3 set for a bit but when looking at the output, weewx isn't even attempting to publish to PWSweather...it's ignoring it completely. Anyone see this behavior before?

Thanks,

Doug

[Tom Keffer]

Hard to debug without seeing the log. 

Most likely you have a configuration problem. Take a careful look at the [StdRESTful] section of weewx.conf. In particular, the [[PWSweather]] subsection. Is it enabled? Is the station and password correct? 

Also, make sure you have the number of brackets "[[..]]" correct. Is it running on into the next subsection?

-tk

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c16fea41-b95f-4956-9efd-55cd03e9019bn%40googlegroups.com.

[Douglas Cote]

Thanks. I can't see where the issue is but I've attached debug output and a bit of syslog. 

[Tom Keffer]

Everything looks normal.

How about a little more of the system log? Make sure debug=1, then stop and restart weewxd. Wait until the first reporting cycle is finished (usually 5 or 10 minutes), then post the log from startup. 

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/be6099b7-f84c-4738-9300-d5e475649230n%40googlegroups.com.

[Douglas Cote]

Attached an updated log. The most recent start events are around 12:21 PM ET. I can see it reference posting to PWSweather but doesn't seem to actually do it. Thanks.

[Tom Keffer]

This is a good example of why it's so important to include the log.

Your problem is corrupted memory in your Vantage logger. It has nothing to do with PWSWeather. If you take a close look, you'll see that your HTML pages are not getting updated either. 

To fix, see the wiki section WeeWX generates HTML pages, but it does not update them.

Incidentally, your archive interval is 30 minutes. Did you want it that long?

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/631a7bca-ed25-4181-a39b-14f082492b0en%40googlegroups.com.

[Douglas Cote]

Thanks very much. I got it to send updates to PWS but still seeing some odd behavior. I think the 30 minute interval is the default in the VPro2 and have no need to change it. The other thing I noticed is the PWS update will only send when archive processing runs. Thanks again.

[Tom Keffer]

I'm not following. What is the odd behavior? That all sounds normal. 

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1f56c882-b19b-4a7b-8dcc-74e911bd1819n%40googlegroups.com.

[Douglas Cote]

Previously, I was getting conditions posted to my PWSweather page every minute or so. Now it only updates every 30 minutes, which appears to coincide with the 30 minute archive interval. So, it's at least posting new data to the site but not at the frequency I was expecting. The attached is a filtered syslog showing the PWS publishing events today. I was going to try changing the record_generation parameter to software to see if it makes a difference. Thanks.

[John Kline]

You must have been using a shorter archive interval when you observed more frequent PWS updates.  The updates happen, at most, every archive interval.  There is an option to make them less frequent, by setting post_interval (see: https://weewx.com/docs/usersguide.htm#%5B%5BPWSweather%5D%5D).

On Apr 17, 2022, at 6:56 PM, Douglas Cote <decot...@gmail.com> wrote:

Previously, I was getting conditions posted to my PWSweather page every minute or so. Now it only updates every 30 minutes, which appears to coincide with the 30 minute archive interval. So, it's at least posting new data to the site but not at the frequency I was expecting. The attached is a filtered syslog showing the PWS publishing events today. I was going to try changing the record_generation parameter to software to see if it makes a difference. Thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9cdf69c2-440b-49b3-9d2d-e04cc4f3a251n%40googlegroups.com.

[Douglas Cote]

Yeah, I can't figure out why WU updates every few seconds, but PWS waits for the archive every 30 mins. If the PWS update is specifically tied to the hardware archive interval then that makes sense. I guess I didn't notice what the hardware might have been set to when PWS was updating more frequently. If I can figure out how to adjust the Vantage pro hardware setting that might get things back to how they behaved previously. Thanks for all the assistance.

[John Kline]

> Yeah, I can't figure out why WU updates every few seconds

WU has a rapid fire setting:

See:

https://weewx.com/docs/usersguide.htm#Wunderground

PWSweather has no such equivalent

> If I can figure out how to adjust the Vantage pro hardware setting…

See:

https://weewx.com/docs/hardware.htm#vantage_notes

wee_device --set-interval=MINUTES [config_file] [-y]

On Apr 19, 2022, at 5:46 PM, Douglas Cote <decot...@gmail.com> wrote:

Yeah, I can't figure out why WU updates every few seconds, but PWS waits for the archive every 30 mins. If the PWS update is specifically tied to the hardware archive interval then that makes sense. I guess I didn't notice what the hardware might have been set to when PWS was updating more frequently. If I can figure out how to adjust the Vantage pro hardware setting that might get things back to how they behaved previously. Thanks for all the assistance.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b28f9a10-9f9c-4841-a5dc-65d105a779ddn%40googlegroups.com.