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: [email protected] <[email protected]> on behalf of
gjr80 <[email protected]>
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&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=xyJPvbQK6giDSp7jo8x8lGJLGehMCS1aMdAcp6TsRsw%3D&reserved=0>
in the rtgd
wiki<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgjr80%2Fweewx-realtime_gauge-data%2Fwiki&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=%2FCbfh9nm3vie%2BKDDhDo7KDS87u45wD1PmI%2FbbN8VHBo%3D&reserved=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&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=upPbMNALgAfPjpuiiI0ZXCaqqu3S6ijR4LQyeQaspCU%3D&reserved=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
https://github.com/gjr80/weewx-realtime_gauge-data<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgjr80%2Fweewx-realtime_gauge-data&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=g1aHcdde%2FJPSNJVCp37Jq3XyjhpQMYc32tmi720NSU0%3D&reserved=0>
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: [email protected] <[email protected]> on behalf of gjr80
<[email protected]>
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://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=R%2BLXIKeAzPr1JJ8343SP0lx9WgwRKfQSevKm%2F2GiPWg%3D&reserved=0>
<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=R%2BLXIKeAzPr1JJ8343SP0lx9WgwRKfQSevKm%2F2GiPWg%3D&reserved=0>
you need
remote_sever_url =
http://www.kq5s.com/weewx/ss<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.kq5s.com%2Fweewx%2Fss&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=R%2BLXIKeAzPr1JJ8343SP0lx9WgwRKfQSevKm%2F2GiPWg%3D&reserved=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<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fyour.site.address.com%2Fpath%2Fto%2Fpost_gauge-data.php&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=tNtdc%2Fm4G0z4dND3ysv%2BSn%2BPgZ2x%2BrOFKbbzoP4dKO0%3D&reserved=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
[[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 [email protected].
For more options, visit
https://groups.google.com/d/optout<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=zHFP9fEGOHPPABop6XXqgH4jlAYDnNpTKQC408Olhns%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]<mailto:[email protected]>.
For more options, visit
https://groups.google.com/d/optout<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7C%7C5664c872e1034f0e199908d67a7628ca%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636831045233612184&sdata=zHFP9fEGOHPPABop6XXqgH4jlAYDnNpTKQC408Olhns%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.
