When I go to www.kq5s.com/weewx/ss/post_gauge-data.php I don't get a 404
error so it would appear that post_gauge-data.php is accessible on your web
server. Next thing to check is to see what (if any) error rtgd is getting
when it tries to post gauge-data.txt. To do this edit weewx.conf, set debug
= 1, save weewx.conf and restart weeWX. Assuming the post fails rtgd should
come up with an error message that should be logged. It probably won't mean
much but will give us a pointer to the issue.
Now look at your web servers error log. How you do this will depend on your
web server; is it hosted for you or self hosted, what web server software
is used and how is the logging configured. I host locally using nginx and I
have my error log in /var/log/nginx/error.log on my nginx machine. Yours
will almost certainly be different. What you need to look for are entries
in the log from each time rtgd tries to post gauge-data.txt, this should
tell us what error your web server is seeing.
For WU forecast units just put units = US somewhere under [[WU]], then
either do a config reload or restart weeWX and the WU forecast will be
downloaded with US customary units next time the forecast is downloaded.
[[WU]]
api_key = 123345567
...
units = US
...
Gary
On Monday, 14 January 2019 02:00:37 UTC+10, Tom Robertson wrote:
>
> OK I'm making progress. I have RTGD creating the gauge-data.txt file
> every loop and placing it in the html_public directory and it is uploaded
> at the archive interval. I also have the WU forecast showing on the LED
> screen.
>
> I can not get the post_gauge-data.php to work. It is not uploading. I
> placed the php file in the same directory as the SS gauges,
> www.kq5s.com/weewx/ss. This is from my weewx config file:
>
> [RealtimeGaugeData]
> date_format = %Y.%m.%d %H:%M
> scroller_source = WU
> rtgd_path = /home/weewx/public_html
>
> # Remote URL to which the gauge-data.txt data will be posted via HTTP
> POST.
> # Optional, omit to disable HTTP POST.
> remote_server_url = http://www.kq5s.com/weewx/ss
> # timeout in seconds for remote URL posts. Optional, default is 2
> timeout = 1
> # text returned from remote URL indicating success. Optional, default
> is no
> # response text.
> response_text = success
>
> From RTGD.PY
>
>
> # Path to gauge-data.txt. Relative paths are relative to HTML_ROOT. If
> # empty default is HTML_ROOT. If setting omitted altogether default is
> # /var/tmp
> rtgd_path = /home/weewx/public_html
>
> # File name (only) of file produced by rtgd. Optional, default is
> # gauge-data.txt.
> rtgd_file_name = gauge-data.txt
>
> # Remote URL to which the gauge-data.txt data will be posted via HTTP
> POST.
> # Optional, omit to disable HTTP POST.
> remote_server_url = http://www.kq5s.com/weewx/ss
>
> Any help please?
>
> Tom
>
> ------------------------------
> *From:* [email protected] <javascript:> <[email protected]
> <javascript:>> on behalf of gjr80 <[email protected] <javascript:>>
> *Sent:* Saturday, January 12, 2019 8:13 PM
> *To:* weewx-user
> *Subject:* Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series
>
> Correct, you just want to disable generation of gauge-data.txt by the
> skin. As you have found the instructions in rtgd.py (step 6 I think) are
> correct.
>
> The offending staff member has since been fired.
>
> Gary
>
> On Sunday, 13 January 2019 12:07:52 UTC+10, [email protected] wrote:
>
> OK. I see more detailed instructions in the rtgd.py file. I’ll give it a
> go though I may wait until tomorrow morning when I am fresh. The steps
> seem pretty involved for us novices. It does appear as though the
> gauge-data.txt file generated by SS is placed in the public_html/ss
> directory and the RTGD will place it in the public_html do it should not be
> an issue.
>
>
>
> Tom
>
>
>
> *From:* [email protected] <[email protected]> *On Behalf
> Of *[email protected]
> *Sent:* Saturday, January 12, 2019 7:55 PM
> *To:* [email protected]
> *Subject:* [weewx-user] Real Time Gauges (RTGD) for Steel Series
>
>
>
> I am just starting to attempt to set these up. I intend to use the
> post_gauge-data.php to get the files on my off-site server. The
> instructions say:
>
>
>
> *Note:* If the SteelSeries weeWX skin is installed either disable the
> skin or ensure that the *Realtime gauge-data* extension generated
> *gauge-data.txt* file is saved to a different location to that generated
> by the SteelSeries weeWX skin.
>
>
>
> Doesn’t the SS skin generate the index.html file and the graphs. I might
> have read somewhere that the graphs do not work with the RTGD extension but
> I would think you need the index.html? So do go into the weex.conf file
> and but ##skin=ss and that is all other than modifying the rtgd.py file?
>
>
>
> Tom
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout
> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7Cd871e20a73de41c8b8e908d678fcb132%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636829424023498535&sdata=if0Dwc2aa4Bn%2FquPcLTNDCavS5VUMCKpWIWPEerD5M8%3D&reserved=0>
> .
>
> --
> 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 [email protected] <javascript:>.
> For more options, visit https://groups.google.com/d/optout
> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7Cd871e20a73de41c8b8e908d678fcb132%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636829424023498535&sdata=if0Dwc2aa4Bn%2FquPcLTNDCavS5VUMCKpWIWPEerD5M8%3D&reserved=0>
> .
>
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
