Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-14 Thread Tom Robertson
Thanks Gary and understand all.  I am actually having fun getting weewx setup 
and customized.  It is a powerful program that can do amazing stuff.

I found out that the timeout variable was causing my system not to upload.  
When I copied it from the py file I left it set at 1.  When I changed it to 2, 
the default, or commented it out, things  work fine.

# timeout in seconds for remote URL posts. Optional, default is 2
timeout = 1

I am an engineer and probably follow things too literally.  For example the 
"instructions" in the py file say

3.  Add the following stanza to weewx.conf:

[RealtimeGaugeData]
.
.

and that is what I did. 


I broke out an old Intel I3 notebook and installed Ubuntu and weewx on it. I 
have to say it works better than the RPI I was using.  I'may have to est the 
RPI and see if it can handle the 2 sec upload along with the other stuff.


Let me see what I can break next.


Tom






From: weewx-user@googlegroups.com  on behalf of 
gjr80 
Sent: Monday, January 14, 2019 5:15 PM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

Good news.

The instructions at the top of the rtgd.py are meant as a fallback if all you 
have are the source files for the extension with no access to instructions or 
the installer. They really just document all of the settings, you can certainly 
copy the [RealtimeGaugeData] stanza to weewx.conf but it will certainly need 
some changes, for example the scroller_source config option indicates all of 
the possible sources (scroller_source = text|file|WU|DS|Zambretti) and you need 
to have just one. If you copy the config stanza from rtgd.py then you really 
need to go through each config option carefully to make sure it is correct for 
your install/setup.

For rtgd I have tried to structure it such that installing rtgd as an extension 
using wee_extension gives a basic functioning install (emphasis on the basic). 
Instructions for this are presented in the github readme that displays at the 
bottom of the page when you land on the rtgd repo. Manual instructions are 
included as well for those that do not want to use wee_extension, again these 
should be on the landing page. Both wee_extension and manual instructions 
should be in the Quickstart 
Guide<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgjr80%2Fweewx-realtime_gauge-data%2Fwiki%2FQuick-Start-Guide=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435%7C1%7C0%7C636831045233612184=xyJPvbQK6giDSp7jo8x8lGJLGehMCS1aMdAcp6TsRsw%3D=0>
 in the rtgd 
wiki<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgjr80%2Fweewx-realtime_gauge-data%2Fwiki=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435%7C1%7C0%7C636831045233612184=%2FCbfh9nm3vie%2BKDDhDo7KDS87u45wD1PmI%2FbbN8VHBo%3D=0>.
 If users want to customise the basic install, say add a forecast source, 
change units or post gauge-data.txt using http post then they should refer to 
the partially written Users 
Guide<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgjr80%2Fweewx-realtime_gauge-data%2Fwiki%2FUser%27s-Guide=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435%7C1%7C0%7C636831045233612184=upPbMNALgAfPjpuiiI0ZXCaqqu3S6ijR4LQyeQaspCU%3D=0>
 again in the rtgd wiki. The instructions on the landing page, the Quickstart 
Gide, the User's Guide and the comments in rtgd.py, whilst all being different 
and serving slightly different purposes should all be consistent. I will have a 
look through each to ensure this is the case.

As a general rule, weeWX users should never need to modify a .py file, all 
config/settings etc should be done through a .conf file, ideally weewx.conf or 
a skin.conf.

Getting back to your install, if you continue to have an issue and cannot find 
the problem in weewx.conf I suggest you post a sanitised copy of the problem 
[RealtimeGaugeData] stanza making sure any sensitive info (eg API key) is 
removed .

Gary

On Monday, 14 January 2019 23:59:10 UTC+10, Tom Robertson wrote:
Whew.  Got it.  The full path did the trick.

I did have the units=US in the wrong place.  I had it in the RTGD file.  I put 
it in the block where the instructions were.   I initially missed the part of 
the instructions that said to copy the block to weewx.conf and thought you 
entered the data into rtgd.py.  For some reason

Initially I did not copy ALL the data under the instructions in the py file to 
the weewx.conf file but obvioulsy it worked because of the defaults that are 
set.  I have since copied all the data to the weex.conf file but need to do 
some more checking since the data file is not being uploaded.  If I go back to 
my original file with just a few entries under the rtgd area things work fine.

I mentioned earlier I started out using the instruction on 
ht

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-14 Thread gjr80
Good news. 

The instructions at the top of the rtgd.py are meant as a fallback if all 
you have are the source files for the extension with no access to 
instructions or the installer. They really just document all of the 
settings, you can certainly copy the [RealtimeGaugeData] stanza to 
weewx.conf but it will certainly need some changes, for example the 
scroller_source config option indicates all of the possible sources 
(scroller_source 
= text|file|WU|DS|Zambretti) and you need to have just one. If you copy the 
config stanza from rtgd.py then you really need to go through each config 
option carefully to make sure it is correct for your install/setup.

For rtgd I have tried to structure it such that installing rtgd as an 
extension using wee_extension gives a basic functioning install (emphasis 
on the basic). Instructions for this are presented in the github readme 
that displays at the bottom of the page when you land on the rtgd repo. 
Manual instructions are included as well for those that do not want to use 
wee_extension, again these should be on the landing page. Both wee_extension 
and manual instructions should be in the Quickstart Guide 
<https://github.com/gjr80/weewx-realtime_gauge-data/wiki/Quick-Start-Guide> 
in the rtgd wiki <https://github.com/gjr80/weewx-realtime_gauge-data/wiki>. 
If users want to customise the basic install, say add a forecast source, 
change units or post gauge-data.txt using http post then they should refer 
to the partially written Users Guide 
<https://github.com/gjr80/weewx-realtime_gauge-data/wiki/User's-Guide> 
again in the rtgd wiki. The instructions on the landing page, the 
Quickstart Gide, the User's Guide and the comments in rtgd.py, whilst all 
being different and serving slightly different purposes should all be 
consistent. I will have a look through each to ensure this is the case.

As a general rule, weeWX users should never need to modify a .py file, all 
config/settings etc should be done through a .conf file, ideally weewx.conf 
or a skin.conf.

Getting back to your install, if you continue to have an issue and cannot 
find the problem in weewx.conf I suggest you post a sanitised copy of the 
problem [RealtimeGaugeData] stanza making sure any sensitive info (eg API 
key) is removed .

Gary

On Monday, 14 January 2019 23:59:10 UTC+10, Tom Robertson wrote:
>
> Whew.  Got it.  The full path did the trick.  
>
> I did have the units=US in the wrong place.  I had it in the RTGD file.  I 
> put it in the block where the instructions were.   I initially missed 
> the part of the instructions that said to copy the block to weewx.conf and 
> thought you entered the data into rtgd.py.  For some reason
>
> Initially I did not copy ALL the data under the instructions in the py 
> file to the weewx.conf file but obvioulsy it worked because of the defaults 
> that are set.  I have since copied all the data to the weex.conf file but 
> need to do some more checking since the data file is not being uploaded.  
> If I go back to my original file with just a few entries under the rtgd 
> area things work fine.
>
> I mentioned earlier I started out using the instruction on 
> https://github.com/gjr80/weewx-realtime_gauge-data before I discovered 
> the instructions in the py file.  I think that led to some confusion on my 
> part.  You might want to think about adding something to the web page to 
> direct folks to the py file.
>
> Bottom line gauges are updating every 2 seconds by including the php name 
> in the path.  I can look at my David console and look at my web page and 
> see the gauges changing to match the console.
>
> I know have to figure out why the config file with all the rtgd setting is 
> not working.  I'm sure I have just missed something.
>
> As always thanks a lot for the help!
>
> Tom
> --
> *From:* weewx...@googlegroups.com   > on behalf of gjr80 >
> *Sent:* Monday, January 14, 2019 1:25 AM
> *To:* weewx-user
> *Subject:* Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series 
>  
> Tom,
>
> Ok, good news on the http post front - it is a simple fix. The 
> remote_server_url config option under [RealtimeGaugeData] needs to 
> include the name of the php file that accepts the http post. So rather than:
>
> remote_server_url = http://www.kq5s.com/weewx/ss 
> <https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C838b2c9138114a1deb2408d679f186a9%7C84df9e7fe9f640afb435%7C1%7C0%7C636830475577369484=EsaLpPCWb0ZlQXC3yYL3QiIFITh7ictlk71uRQfeNDs%3D=0>
>
> <https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C838b2c9138114a1deb2408d679f186a9%7C84df9e7fe9f640afb435%7C1%7C0%7C636830475577369484=EsaLpPCWb0ZlQ

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-14 Thread Tom Robertson
Whew.  Got it.  The full path did the trick.

I did have the units=US in the wrong place.  I had it in the RTGD file.  I put 
it in the block where the instructions were.   I initially missed the part of 
the instructions that said to copy the block to weewx.conf and thought you 
entered the data into rtgd.py.  For some reason

Initially I did not copy ALL the data under the instructions in the py file to 
the weewx.conf file but obvioulsy it worked because of the defaults that are 
set.  I have since copied all the data to the weex.conf file but need to do 
some more checking since the data file is not being uploaded.  If I go back to 
my original file with just a few entries under the rtgd area things work fine.

I mentioned earlier I started out using the instruction on 
https://github.com/gjr80/weewx-realtime_gauge-data before I discovered the 
instructions in the py file.  I think that led to some confusion on my part.  
You might want to think about adding something to the web page to direct folks 
to the py file.

Bottom line gauges are updating every 2 seconds by including the php name in 
the path.  I can look at my David console and look at my web page and see the 
gauges changing to match the console.

I know have to figure out why the config file with all the rtgd setting is not 
working.  I'm sure I have just missed something.

As always thanks a lot for the help!

Tom

From: weewx-user@googlegroups.com  on behalf of 
gjr80 
Sent: Monday, January 14, 2019 1:25 AM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

Tom,

Ok, good news on the http post front - it is a simple fix. The 
remote_server_url config option under [RealtimeGaugeData] needs to include the 
name of the php file that accepts the http post. So rather than:

remote_server_url = 
http://www.kq5s.com/weewx/ss<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C838b2c9138114a1deb2408d679f186a9%7C84df9e7fe9f640afb435%7C1%7C0%7C636830475577369484=EsaLpPCWb0ZlQXC3yYL3QiIFITh7ictlk71uRQfeNDs%3D=0>
<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C838b2c9138114a1deb2408d679f186a9%7C84df9e7fe9f640afb435%7C1%7C0%7C636830475577369484=EsaLpPCWb0ZlQXC3yYL3QiIFITh7ictlk71uRQfeNDs%3D=0>

you need

   remote_sever_url = 
http://www.kq5s.com/weewx/ss<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C838b2c9138114a1deb2408d679f186a9%7C84df9e7fe9f640afb435%7C1%7C0%7C636830475577369484=EsaLpPCWb0ZlQXC3yYL3QiIFITh7ictlk71uRQfeNDs%3D=0>/post_gauge-data.php

You will need to save weewx.conf and do a config reload or restart weeWX for 
the change to take effect.

It seems that if you hit the server without the php file name no error is 
thrown, I will need to see if there is something I can catch to at least log 
the error in the weeWX log.

Not so good on the units. I just ran up a virtual machine installed weeWX 3.8.2 
and rtgd 0.3.5 and setup WU and by default it displays a metric forecast. I set 
units = US under [RealtimeGaugeData] [[WU]] in weewx.conf, saved weewx.conf and 
restarted weeWX and it immediately downloaded a WU forecast and display US 
customary units. Can you confirm your placement of units = US, it should be 
similar to:

# Options for extension 'Rtgd'
[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://your.site.address.com/path/to/post_gauge-data.php
# 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

[[Groups]]
...
[[StringFormats]]
...
[[WU]]
api_key = abcdefghijklmnop
units = US

And of course you did restart weeWX?

Gary


On Monday, 14 January 2019 12:26:16 UTC+10, gjr80 wrote:
No, no idea about the units. Will look at that as well.

Gary

--
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+unsubscr...@googlegroups.com<mailto:weewx-user+unsubscr...@googlegroups.com>.
For more options, visit 
https://groups.google.com/d/optout<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout=02%7C01%7C%7C838b2c9138114a1deb2408d679f186a9%7C84df9e7fe9f640afb435%7C1%7C0%7C636830475577369484=EiffispSxboTX7cN%2BMfIgvgIshBwoeuoyRCMuBvXPAs%3D=0>.

-- 
You received this message because you are subscribed to the Google Groups 

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread gjr80
Tom,

Ok, good news on the http post front - it is a simple fix. The 
remote_server_url config option under [RealtimeGaugeData] needs to include 
the name of the php file that accepts the http post. So rather than:

remote_server_url = http://www.kq5s.com/weewx/ss


you need
 
   remote_sever_url = http://www.kq5s.com/weewx/ss/post_gauge-data.php

You will need to save weewx.conf and do a config reload or restart weeWX 
for the change to take effect.

It seems that if you hit the server without the php file name no error is 
thrown, I will need to see if there is something I can catch to at least 
log the error in the weeWX log.

Not so good on the units. I just ran up a virtual machine installed weeWX 
3.8.2 and rtgd 0.3.5 and setup WU and by default it displays a metric 
forecast. I set units = US under [RealtimeGaugeData] [[WU]] in weewx.conf, 
saved weewx.conf and restarted weeWX and it immediately downloaded a WU 
forecast and display US customary units. Can you confirm your placement of 
units 
= US, it should be similar to:

# Options for extension 'Rtgd'
[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:
//your.site.address.com/path/to/post_gauge-data.php
# 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

[[Groups]]
...
[[StringFormats]]
...
[[WU]]
api_key = abcdefghijklmnop
units = US

And of course you did restart weeWX?

Gary


On Monday, 14 January 2019 12:26:16 UTC+10, gjr80 wrote:
>
> No, no idea about the units. Will look at that as well.
>
> Gary
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread gjr80
No, no idea about the units. Will look at that as well.

Gary

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread Tom Robertson
No hurry  Once a minute works.

Any idea why the units are not changing to US?  This is from the latest 
gauge-data.txt file:
"forecast":Mostly cloudy.  Low 2C"


-

73,

Tom - KQ5S


From: weewx-user@googlegroups.com  on behalf of 
gjr80 
Sent: Sunday, January 13, 2019 7:40 PM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

Ok, that indicates the thread is still alive. Am at a bit of a loss at the 
moment. I will have to put a bit more logging into rtgd.py so we can see what 
is going on around the posting of gauge-data.txt.

Going to be a later today job for me so I guess tomorrow for you :).

Gary

On Monday, 14 January 2019 11:35:11 UTC+10, Tom Robertson wrote:
Yep.  I can go to public_html and see the file time change every 2 seconds.



-

73,

Tom - KQ5S


From: weewx...@googlegroups.com  on behalf of gjr80 

Sent: Sunday, January 13, 2019 7:14 PM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

Ok, nothing unusual in the weewx log. Sounds like the the rtgd thread silently 
dies and hence rtgd never gets a chance to post gauge-data.txt. Can you confirm 
that gauge-data.txt is being generated on your weeWX machine without error 
every 2 odd seconds?

Gary

On Monday, 14 January 2019 10:56:09 UTC+10, Tom Robertson wrote:
Attached is the syslog file with debug=1.  I went to my hosting site and using 
CPanel there is a page that shows:


The function displays up to 300 of the most recent entries in your website’s 
error logs, in reverse chronological order. You can use this information to 
find broken links or problems with missing files. For more information, read 
our 
documentation<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgo.cpanel.net%2FErrors=02%7C01%7C%7Cb4c9251e85734af6efca08d679c139aa%7C84df9e7fe9f640afb435%7C1%7C0%7C636830268129621742=Aq%2FvgX2bbuJWTj6lgFVYTGuoeKGhr9DFoqqRtZUQ0HI%3D=0>.

Last 300 Error Log messages in reverse order:

Nothing is showing.

I was looking at my hosting site and it said the error logs do not include php 
and to add some stuff to the .htaccess and php.ini files.   I did that and 
still no errors are showing.

I also added the units = US and metric is still showing.

[[WU]]
# WU API key to be used when calling the WU API
api_key = 8f246XX
units = US


Tom


From: weewx...@googlegroups.com  on behalf of gjr80 

Sent: Sunday, January 13, 2019 5:38 PM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

When I go to 
www.kq5s.com/weewx/ss/post_gauge-data.php<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss%2Fpost_gauge-data.php=02%7C01%7C%7Cb4c9251e85734af6efca08d679c139aa%7C84df9e7fe9f640afb435%7C1%7C0%7C636830268129621742=6RPjo8jZxWDnu%2BlQ4kxR4rnyPM56Hs6R7SusFcYIU2A%3D=0>
 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<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7Cb4c9251e85734af6efca08d679c139aa%7C84df9e7fe9f640afb435%7C1%7C0%7C636830268129621742=K85otb8%2FwPacXrbxTyewo4h1HAF1F5lnfaFOSl6q9wM%

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread gjr80
Ok, that indicates the thread is still alive. Am at a bit of a loss at the 
moment. I will have to put a bit more logging into rtgd.py so we can see 
what is going on around the posting of gauge-data.txt. 

Going to be a later today job for me so I guess tomorrow for you :).

Gary

On Monday, 14 January 2019 11:35:11 UTC+10, Tom Robertson wrote:
>
> Yep.  I can go to public_html and see the file time change every 2 
> seconds. 
>
>
> -
>
> 73,
>
> Tom - KQ5S
>
> --
> *From:* weewx...@googlegroups.com   > on behalf of gjr80 >
> *Sent:* Sunday, January 13, 2019 7:14 PM
> *To:* weewx-user
> *Subject:* Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series 
>  
> Ok, nothing unusual in the weewx log. Sounds like the the rtgd thread 
> silently dies and hence rtgd never gets a chance to post gauge-data.txt. 
> Can you confirm that gauge-data.txt is being generated on your weeWX 
> machine without error every 2 odd seconds?
>
> Gary
>
> On Monday, 14 January 2019 10:56:09 UTC+10, Tom Robertson wrote: 
>
> Attached is the syslog file with debug=1.  I went to my hosting site and 
> using CPanel there is a page that shows:
>
> The function displays up to 300 of the most recent entries in your 
> website’s error logs, in reverse chronological order. You can use this 
> information to find broken links or problems with missing files. For more 
> information, read our documentation 
> <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgo.cpanel.net%2FErrors=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84df9e7fe9f640afb435%7C1%7C0%7C636830252780134532=B%2BcCSD9Yn3VX9%2BR%2FFXXlwhp4rq1pe7XSnKBQ9wWbr4U%3D=0>
> .
> Last 300 Error Log messages in reverse order: 
>
> Nothing is showing.
>
> I was looking at my hosting site and it said the error logs do not include 
> php and to add some stuff to the .htaccess and php.ini files.   I did that 
> and still no errors are showing. 
>
> I also added the units = US and metric is still showing.
>
> [[WU]]
> # WU API key to be used when calling the WU API
> api_key = 8f246XX
> units = US
>
> Tom
>
> ----------
> *From:* weewx...@googlegroups.com  on behalf 
> of gjr80 
> *Sent:* Sunday, January 13, 2019 5:38 PM
> *To:* weewx-user
> *Subject:* Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series 
>  
> When I go to www.kq5s.com/weewx/ss/post_gauge-data.php 
> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss%2Fpost_gauge-data.php=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84df9e7fe9f640afb435%7C1%7C0%7C636830252780134532=d3Wt03iZtPAmlLze1tSmiyVgdJBRmqMJ3q4JRPkBfSg%3D=0>
>  
> 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 
> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84d

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread Tom Robertson
Yep.  I can go to public_html and see the file time change every 2 seconds.



-

73,

Tom - KQ5S


From: weewx-user@googlegroups.com  on behalf of 
gjr80 
Sent: Sunday, January 13, 2019 7:14 PM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

Ok, nothing unusual in the weewx log. Sounds like the the rtgd thread silently 
dies and hence rtgd never gets a chance to post gauge-data.txt. Can you confirm 
that gauge-data.txt is being generated on your weeWX machine without error 
every 2 odd seconds?

Gary

On Monday, 14 January 2019 10:56:09 UTC+10, Tom Robertson wrote:
Attached is the syslog file with debug=1.  I went to my hosting site and using 
CPanel there is a page that shows:


The function displays up to 300 of the most recent entries in your website’s 
error logs, in reverse chronological order. You can use this information to 
find broken links or problems with missing files. For more information, read 
our 
documentation<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgo.cpanel.net%2FErrors=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84df9e7fe9f640afb435%7C1%7C0%7C636830252780134532=B%2BcCSD9Yn3VX9%2BR%2FFXXlwhp4rq1pe7XSnKBQ9wWbr4U%3D=0>.

Last 300 Error Log messages in reverse order:

Nothing is showing.

I was looking at my hosting site and it said the error logs do not include php 
and to add some stuff to the .htaccess and php.ini files.   I did that and 
still no errors are showing.

I also added the units = US and metric is still showing.

[[WU]]
# WU API key to be used when calling the WU API
api_key = 8f246XX
units = US


Tom


From: weewx...@googlegroups.com  on behalf of gjr80 

Sent: Sunday, January 13, 2019 5:38 PM
To: weewx-user
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

When I go to 
www.kq5s.com/weewx/ss/post_gauge-data.php<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss%2Fpost_gauge-data.php=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84df9e7fe9f640afb435%7C1%7C0%7C636830252780134532=d3Wt03iZtPAmlLze1tSmiyVgdJBRmqMJ3q4JRPkBfSg%3D=0>
 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<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84df9e7fe9f640afb435%7C1%7C0%7C636830252780134532=30QMDKnk%2FxispOJO02V9OnpUeeBYTwdiEiKZiIbudfc%3D=0>.
  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<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7Cda1e4d87df3f4bc0eb4208d679bda6b2%7C84df9e7fe9f640afb435%7C1%7C0%7C636830252780134532=30QMDKnk%2FxispOJO02V9OnpUeeBYTwdiEiKZiIbudfc%3D=0>
# timeout in seconds for remote URL posts. Optional, default is 2
timeout = 1
# text returned from remote URL indicating success. Optional, default i

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread gjr80
Ok, nothing unusual in the weewx log. Sounds like the the rtgd thread 
silently dies and hence rtgd never gets a chance to post gauge-data.txt. 
Can you confirm that gauge-data.txt is being generated on your weeWX 
machine without error every 2 odd seconds?

Gary

On Monday, 14 January 2019 10:56:09 UTC+10, Tom Robertson wrote:
>
> Attached is the syslog file with debug=1.  I went to my hosting site and 
> using CPanel there is a page that shows:
>
> The function displays up to 300 of the most recent entries in your 
> website’s error logs, in reverse chronological order. You can use this 
> information to find broken links or problems with missing files. For more 
> information, read our documentation <https://go.cpanel.net/Errors>.
> Last 300 Error Log messages in reverse order: 
>
> Nothing is showing.
>
> I was looking at my hosting site and it said the error logs do not include 
> php and to add some stuff to the .htaccess and php.ini files.   I did that 
> and still no errors are showing. 
>
> I also added the units = US and metric is still showing.
>
> [[WU]]
> # WU API key to be used when calling the WU API
> api_key = 8f246XX
> units = US
>
> Tom
>
> --
> *From:* weewx...@googlegroups.com   > on behalf of gjr80 >
> *Sent:* Sunday, January 13, 2019 5:38 PM
> *To:* weewx-user
> *Subject:* Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series 
>  
> 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 
> <https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C343c7bf187aa439efdea08d679b02acc%7C84df9e7fe9f640afb435%7C1%7C0%7C636830194864604891=CwXbSeU7%2Fk0ofZeGM8S5bsb4ShJr4CkBSMqfWP4c7z0%3D=0>.
>   
> 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 
> <https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7C343c7bf187aa439efdea08d679b02acc%7C84df9e7fe9f640afb435%7C1%7C0%7C636830194864604891=CwXbSeU7%2Fk0ofZeGM8S5bsb4ShJr4CkBSMqfWP4c7z0%3D=0>
> # 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. Opti

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread gjr80
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:* weewx...@googlegroups.com   > on behalf of gjr80 >
> *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, nine...@gmail.com 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:* weewx...@googlegroups.com  *On Behalf 
> Of *nine...@gmail.com
> *Sent:* Saturday, January 12, 2019 7:55 PM
> *To:* weewx...@googlegroups.com
> *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 exten

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread Tom Robertson
One more thing.  The WU forecast is showing in C not F.  I changed the group 
settings to indicate US measures but the LED is still showing the values in 
metric.


Tom


From: weewx-user@googlegroups.com  on behalf of 
Tom Robertson 
Sent: Sunday, January 13, 2019 10:00 AM
To: weewx-user@googlegroups.com
Subject: Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

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<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7Cd1926a779f3747f7bbce08d67970421b%7C84df9e7fe9f640afb435%7C1%7C0%7C636829920380157699=5wbcJNDfCeLClAb5Ceuz1PQKI8ThxAkuo01Py%2FmPX1Q%3D=0>.
  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<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss=02%7C01%7C%7Cd1926a779f3747f7bbce08d67970421b%7C84df9e7fe9f640afb435%7C1%7C0%7C636829920380157699=5wbcJNDfCeLClAb5Ceuz1PQKI8ThxAkuo01Py%2FmPX1Q%3D=0>

Any help please?

Tom


From: weewx-user@googlegroups.com  on behalf of 
gjr80 
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, nine...@gmail.com 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: weewx...@googlegroups.com  On Behalf Of 
nine...@gmail.com
Sent: Saturday, January 12, 2019 7:55 PM
To: weewx...@googlegroups.com
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 weewx-user+...@googlegroups.com.
For more options, visit 
https://groups.google.com/d/optout<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout=02%7C01%7C%7Cd1926a779f3747f7bbce08d67970421b%7C84df9e7fe9f640afb435%7C1%7C0%7C636829920380157699=FhN7vByMgRPlWGNRe0oMCeZfvYRXEmPOOK7n3EIPAUs%3D=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 
weewx-user+unsubscr...@googlegroups.com<mailto:weewx-

Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-13 Thread Tom Robertson
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<http://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: weewx-user@googlegroups.com  on behalf of 
gjr80 
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, nine...@gmail.com 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: weewx...@googlegroups.com  On Behalf Of 
nine...@gmail.com
Sent: Saturday, January 12, 2019 7:55 PM
To: weewx...@googlegroups.com
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 weewx-user+...@googlegroups.com.
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=02%7C01%7C%7Cd871e20a73de41c8b8e908d678fcb132%7C84df9e7fe9f640afb435%7C1%7C0%7C636829424023498535=if0Dwc2aa4Bn%2FquPcLTNDCavS5VUMCKpWIWPEerD5M8%3D=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 
weewx-user+unsubscr...@googlegroups.com<mailto:weewx-user+unsubscr...@googlegroups.com>.
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=02%7C01%7C%7Cd871e20a73de41c8b8e908d678fcb132%7C84df9e7fe9f640afb435%7C1%7C0%7C636829424023498535=if0Dwc2aa4Bn%2FquPcLTNDCavS5VUMCKpWIWPEerD5M8%3D=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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-12 Thread gjr80
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, nine...@gmail.com 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:* weewx...@googlegroups.com   > *On Behalf Of *nine...@gmail.com 
> *Sent:* Saturday, January 12, 2019 7:55 PM
> *To:* weewx...@googlegroups.com 
> *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 weewx-user+...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout 
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: [weewx-user] Real Time Gauges (RTGD) for Steel Series

2019-01-12 Thread nineback
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: weewx-user@googlegroups.com  On Behalf Of 
nineb...@gmail.com
Sent: Saturday, January 12, 2019 7:55 PM
To: weewx-user@googlegroups.com
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 weewx-user+unsubscr...@googlegroups.com 
 .
For more options, visit https://groups.google.com/d/optout 

 .

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.