BTW, I missed Thomas Carlin's last reply before posting. My apologies for
getting his thread a little sidetracked.
--
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
Hi Thomas,
I use it mainly for the NOAA Climatological monthly and yearly summaries,
and also compile yearly and all time highs and lows from the database, and
appreciate having the database available for any other kind of record
manipulation or graphing. As i mentioned, I don't keep a full
Thank you for your replies.
A couple points of clarification: The main datasource for my station is a
Vantage Pro2, and it is using weewx as designed, LOOP packets, etc. I have
added a second data source as described here
http://www.weewx.com/docs/customizing.htm#Adding_2nd_source, which
Sounds like something for the station manufacturer or the software author, does
not seem to have anything to do with WeeWX unless I missed the release of the
GUI version :) . You may have some luck at wxforum.net
Gary
--
You received this message because you are subscribed to the Google
Proven,
If you haven't restarted WeeWX then you are still using the old highcharts.py
which will of course cause the error. Please restart WeeWX and see how the new
code goes. The point of the instrumented version I said I would send was to
troubleshoot the new code, I won't be doing that
If you restart weewx you may not need the special version. The restart may
fix things anyway.
You should always stop weewx and restart it when modules are changed. You
can usually edit skins without needing to restart however.
On Thursday, 6 September 2018 05:42:24 UTC+3, Praveen
Found it.
After reconfiguring the [Interceptor] defaulted back to device_type =
acurite-bridge while it was originally configured as device_type = observer
Put it back as observer and all is good now.
Regards,
Frits.
On Thursday, 6 September 2018 14:19:09 UTC+12, frits.s...@gmail.com wrote:
>
Hi Gary,
No, I did not restart. I will do once you provide the special version.
Regards,
Praveen
On Thu, 6 Sep 2018, 04:32 gjr80, wrote:
> Did you restart WeeWX?
>
> If you did I will get a special version of highcharts.py to you that will
> log a bit more info to help with debugging.
>
>
Adding to my last. The error started right on 12:00. One might call this a
coincidence but data was recording correctly for about half a hour before
that.
On Thursday, 6 September 2018 14:19:09 UTC+12, frits.s...@gmail.com wrote:
>
> Hello all,
> for a few years now I've used weewx with
Hello all,
for a few years now I've used weewx with interceptor to collect and store
data from my Aercus Weathersleuth and with no problems till this morning.
I enabled PWSweather and added the station name and password. Saved the
config file and restarted weewx.
And now I have quite a few
Thanks for your comments, Jeff, but you've got me curious. If you don't use
WeeWX for its ability to accumulate LOOP packets and make records out of
them, and you don't publish to the web, what do you use it for? Internal
LAN publishing? Something else?
-tk
On Wed, Sep 5, 2018 at 9:08 AM Jeff A.
Hi All,
I realized that that there is blank firmware on my weather station and
would like to reload it.
When I tried to connect the controller to my windows pc and used
WxConfig.exe from http://www.argentdata.com/files/WxConfig.exe
The firmware was downloaded
from
Did you restart WeeWX?
If you did I will get a special version of highcharts.py to you that will
log a bit more info to help with debugging.
Gary
On Thursday, 6 September 2018 00:31:55 UTC+10, Praveen Chandrasekaran wrote:
>
> Hi Gary,
>
> The highcharts.py was below for me:
>
>
You need to do the following:
1. edit weewx.conf (the location of weewx.conf will depend on how you
installed WeeWX, for a setup.py install it will be in /home/weewx,
otherwise it will be in /etc/weewx)
2. set debug = 2 (circa line 11)
3. locate the [WS1] stanza and enter a line read_debug = 2
Yes indeed, thanks, good to know in case I go that way.
On Thu, Sep 6, 2018 at 7:46 AM G Hammer wrote:
> Did you see the cause? http (for you) vs https (for me)
>
> On Wed, Sep 5, 2018 at 3:44 PM Colin Larsen
> wrote:
>
>> Excellent, glad progress is being made
>>
>> On Thu, Sep 6, 2018 at
Did you see the cause? http (for you) vs https (for me)
On Wed, Sep 5, 2018 at 3:44 PM Colin Larsen wrote:
> Excellent, glad progress is being made
>
> On Thu, Sep 6, 2018 at 7:42 AM G Hammer wrote:
>
>> Actually, it is the need to have a cert for the server the Mosquitto is
>> on.
>> For now,
Excellent, glad progress is being made
On Thu, Sep 6, 2018 at 7:42 AM G Hammer wrote:
> Actually, it is the need to have a cert for the server the Mosquitto is
> on.
> For now, using test.mosquitto.org is working fine.
> Thanks to Dave.
>
> On Wed, Sep 5, 2018 at 3:38 PM Colin Larsen
> wrote:
Actually, it is the need to have a cert for the server the Mosquitto is on.
For now, using test.mosquitto.org is working fine.
Thanks to Dave.
On Wed, Sep 5, 2018 at 3:38 PM Colin Larsen wrote:
> Its my understanding that if mosquitto didn't support websockets then the
> skin updates wouldn't
Its my understanding that if mosquitto didn't support websockets then the
skin updates wouldn't work at all, or did I read what you wrote wrong?
This is my in-house mosquitto server config file (untested)
persistence false
allow_anonymous true
# Non-SSL MQTT
listener 1883
protocol mqtt
#
Ended up being a syntax error. Thanks again, Vince
On Wed, Sep 5, 2018, 12:56 PM vince wrote:
> On Wednesday, September 5, 2018 at 9:51:02 AM UTC-7, Steve2Q wrote:
>>
>> Thanks, Vince. I am going to do the manual install as I could not get the
>> extension installer to work. Maybe syntax error
So I just installed on a test Pi running Simulator and am getting the
following when I try to restart Weewx.
Sep 5 18:56:49 raspberrypi systemd[1]: Starting LSB: weewx weather
system...
Sep 5 18:56:49 raspberrypi weewx[5488]: Starting weewx weather system:
weewxTraceback (most recent call
On Wednesday, September 5, 2018 at 9:51:02 AM UTC-7, Steve2Q wrote:
>
> Thanks, Vince. I am going to do the manual install as I could not get the
> extension installer to work. Maybe syntax error or my just not
> understanding how it works in this case..I have used the installer
> successfully
Thanks, Vince. I am going to do the manual install as I could not get the
extension installer to work. Maybe syntax error or my just not
understanding how it works in this case..I have used the installer
successfully in the past.
On Wed, Sep 5, 2018, 12:46 PM vince wrote:
> On Wednesday,
On Wednesday, September 5, 2018 at 8:31:30 AM UTC-7, Steve2Q wrote:
>
> 1. I am running Weewx 3.8.0. In /examples/pmon the changelog says the
> included version is 0.4 date 24 April 2016. Is this the most up to date
> version?
>
>
The git repo says the last change was in May this year. So yes.
If I may chime in on the subject, but there are various reasons I don't
have a full time connection to my wx station (Davis VP), and therefore rely
on the archive records to download from the data logger periodically. Even
using a fairly long archive interval of 30 minutes, the archive records
Hello. I have back from vacation, and I want to try and track down this
problem. From this discussion, I think I would like to initiate pmon to see
what is happening with regards to any memory issues. I have some questions
about installing pmon.
1. I am running Weewx 3.8.0. In /examples/pmon
Hardware setup is: USB-to-Serial (exactly the one in below link), USB end
connected to Raspberry Pi (Model 3 B+) running latest Raspbian OS.
The logs were repeating themselves. Weewx engine starts fine and attempts
to read the data from WS1 for 5 times, the cycle repeats every 60 seconds.
" turn
Hi Gary,
The highcharts.py was below for me:
/usr/share/weewx/user
I downloaded the updated file, diffed with old file to ensure it has
changes. Deleted the year.json. However the next report cycle year.json
still has the same issue.
Regards,
Praveen
On Tue, 4 Sep 2018 at 19:12, gjr80 wrote:
Well, there are some errors.
Connecting to MQTT weather:416:13
jQuery.Deferred exception: An invalid or illegal string was specified
Paho.MQTThttps://cdnjs.cloudflare.com/ajax/libs/
paho-mqtt/1.0.1/mqttws31.min.js:36:453
Paho.MQTThttps://cdnjs.cloudflare.com/ajax/libs/paho-
Here is what is in the dev console when I load the site:
Connecting to MQTT weather:416:13
jQuery.Deferred exception: An invalid or illegal string was specified Paho.
MQTThttps://cdnjs.cloudflare.com/ajax/libs/paho-
mqtt/1.0.1/mqttws31.min.js:36:453
Andrew pretty much has the right idea.
The whole value of weewx is in its archiving abilities. If your driver(s)
don't emit LOOP packets, then your missing out on half the reason to use
the program!
-tk
On Tue, Sep 4, 2018 at 9:46 PM Andrew Milner
wrote:
> If you bind your service to loop
You are a genius! This worked a treat!
The security was the issue.
Thank you ever so much, I would have poked at everything but that.
--
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
Just to confirm I have highlighted in Red what you need to change to make
an https site work with test.mosquitto.org I couldn't get the colouring to
work properly above...
mqtt_port = 8081 instead of 8080
mqtt_ssl = 1 (instead of 0)
Let me know how you get on - if necessary I can spin up
Not a netatmo user but I suspect that the client thread in the netatmo
driver encounters an error and silently dies thus leaving WeeWX running but
with no data coming in so no activity happens. Suggest you make the
following changes to /usr/share/weewx/user/netatmo.py (circa line 310):
def
what gary said. turn up the debug, and capture output from the time you start
weewx until after a few archive intervals or restart cycles.
you *should* be able to do this with this config:
debug = 2
[WS1]
...
debug_read = 1
but you might have to set DEBUG_READ = 1 in the ws1.py file
Well even though I've changed to MySQL as the database, it still stops all
of a sudden.
Here is the log:
Sep 5 04:24:08 bnj-desktop-haven weewx[19143]: netatmo: netatmo-client:
cloud units: {'windunit': 2, 'unit': 0, 'pressureunit': 0}
Sep 5 04:24:08 bnj-desktop-haven weewx[19143]: netatmo:
36 matches
Mail list logo
