RTGD

[Phil Owers]

Im trying to set up the HTTP POST.  The gauge-data.txt is being produced as the web site already uses that which gets updated every 10 mins.

Ive set a gaugedata sub-directory up with post_gauge-data.php in it, but Im not getting a gauge-data.txt file generated.

In weewx.conf the remote_server_url = http://www.sheringhamweathercentre.uk/gaugedata/post_gauge-data.php but its not generating a gauge-data.txt file

In the log I get 

DATA MAY HAVE BEEN POSTED SUCCESFULLY RESPONCE MESSAGE WAS NOT RECEIVED BUT A VALID CODE WAS RECEIVED.

I was wondering if the PHP 7.4 installed on my web hosting may be the problem, it can be changed but im afraid im guessing here

Any help would be appreciated 

Thanks Phil

[Phil Owers]

After changing a couple of things on my web hosting (under supervision) it started producing the gauge-data.txt.

We changed them back one at a time and it still produces the txt file so didn't prove anything but it is now working

[gjr80]

Appreciate this one is solved, albeit for unknown reason. But maybe some pointers for others with any future issues of this type.

rtgd uses a fairly basic http post to post gauge-data.txt. rtgd looks for a pre-agreed response from the php script to indicate successful transfer but I have found that some combinations of python/php did not send/receive the pre-agreed response despite successful transfer of the file (probably needs further investigation/time). Hence the somewhat wishy/washy (WeeWX) log entry. Otherwise the transfer is fire and forget, so there is not much that can be added to the (WeeWX) log to hep trouble shooot. In these case it is often worth looking at the php log on the web server to see what is/is not being received. The most common issue I have encountered is a mismatch of directories; rtgd is posting somewhere in the web server tree but the the php script on the web server is actually located elsewhere in the tree and hence never receives the file.

Gary