RE: [weewx-user] Re: Weewx + Acurite Atlas + Access + SDR

Yes lots of b\'\', b\'\', b\'\', b\'\', b\'\', b\'\', b\'\', b\'\', b\'\', b\'\', b\'\ From: weewx-user@googlegroups.com On Behalf Of gjr80 Sent: Tuesday, September 8, 2020 07:36 PM To: weewx-user Subject: [weewx-user] Re: Weewx + Acurite Atlas + Access + SDR OK, so WeeWX is finding rt

[weewx-user] Re: Weewx + Acurite Atlas + Access + SDR

OK, so WeeWX is finding rtl_433 OK. The error in the log is just the windrose generator complaining about no wind, it will be fine once it gets some data (though it should not fail like that - I need to fix it). Next step is to run WeeWX directly with: $ sudo /home/weewx/bin/weewxwd /home/weewx

[weewx-user] Re: Weewx + Acurite Atlas + Access + SDR

Here is the syslog Sep 8 18:51:22 na7kr systemd[1]: weewx.service: Succeeded. Sep 8 18:51:22 na7kr systemd[1]: Stopped LSB: weewx weather system. Sep 8 18:51:34 na7kr dhcpd: DHCPREQUEST for 10.70.1.119 from 38:f7:3d:1f:c8:b6 (amazon-78f205e8f) via enp0s25 Sep 8 18:51:34 na7kr dhcpd: DHCPACK on

Re: [weewx-user] Re: Proper/Best Way to Add Additional Ecowitt Sensors

Rob, Took a bit longer than I hoped but have put together some instructions on how to add a new field to the Seasons skin. If you are still interested you will find the instructions in the GW1000 driver wiki here

Re: [weewx-user] weewx-Weather34 installation questions

Appologies TK. Here is the log capturing the weewx start as well. *Sep 8 19:00:10 raspberrypi dbus-daemon[14817]: [session uid=0 pid=14814] Activating service name='ca.desrt.dconf' requested by ':1.0' (uid=0 pid=14807 comm="mousepad ")* *Sep 8 19:00:10 raspberrypi dbus-daemon[14817]: [session

Re: [weewx-user] weewx-Weather34 installation questions

You missed the early parts of the startup, when it would tell us what version of Python is being used. It's OK to use tail -f, but you've got to use it *before* starting up weewxd, not afterwards. -tk On Tue, Sep 8, 2020 at 5:11 PM ExprmntAl <72604.3...@compuserve.com> wrote: > Ok TK, here is t

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

Strange. I would delete the html files, restart weewx and let it re-generate them. They should be in sync with whatever you've set in weewx.conf for rounding values. On Tuesday, September 8, 2020 at 1:32:14 PM UTC-4 tcich...@gmail.com wrote: > I also just noticed that my PUBLIC server is NOT r

[weewx-user] Re: Belchertown skin - working great, except Darksky Forecasts

Need a little more information than this. A link to your website? Debug logs? Skin version 1.2 will be released tomorrow if all goes to plan, and I advise you to switch to Aeris weather since DarkSky will be stopping their API usage at some point. On Sunday, September 6, 2020 at 12:14:48 PM

[weewx-user] Re: Weewx + Acurite Atlas + Access + SDR

Kevin, It looks like WeeWX may still not be finding rtl_433. When you start WeeWX and it does nothing what do you see in the log? Can you post the log from startup? If WeeWX cannot start rtl_433 there should be errors in the log when WeeWX tries to load the sdr driver. Gary On Wednesday, 9 Se

Re: [weewx-user] weewx-Weather34 installation questions

Ok TK, here is the Syslog with Debug = 1 from startup through the first reporting cycle. *pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop* *[ ok ] Stopping weewx (via systemctl): weewx.service.* *pi@raspberrypi:~ $ sudo /etc/init.d/weewx start* *[ ok ] Starting weewx (via systemctl): weewx.service

Re: [weewx-user] weewx-Weather34 installation questions

Maybe. Mr AI's response shows that configobj was installed for python 3, but not necessarily python 2. And... we don't know what version of python is being used, because we have not seen a log. Stop weewxd, set debug=1, restart weewxd. Post the log from startup through the first reporting cycle.

[weewx-user] Weewx + Acurite Atlas + Access + SDR

I see data on SDR With this config: ## [SDR] # This section is for the software-defined radio driver. # The driver to use driver = user.sdr cmd = rtl_433 -M utc -F json" path = /usr/local/bin ld_

Re: [weewx-user] weewx-Weather34 installation questions

On Tuesday, September 8, 2020 at 12:50:16 PM UTC-7, ExprmntAl wrote: > > OK Vince, thanks for helping me. Here is what I got. > > *pi@raspberrypi:~ $ dpkg -l | grep -i configobj* > *ii python3-configobj 5.0.6-3 > all simple but powerf

Re: [weewx-user] weewx-Weather34 installation questions

OK Vince, thanks for helping me. Here is what I got. *pi@raspberrypi:~ $ dpkg -l | grep -i configobj* *ii python3-configobj 5.0.6-3 all simple but powerful config file reader and writer for Python 3* *pi@raspberrypi:~ $ pip list |

Re: [weewx-user] WS23xx error when trying to set interval

Hi Tom, Very close now (good enough for me) as I'm preparing to upgrade from 3.9.2 to 4.x and just testing on a test rig before committing ;-) ./wee_device --set-interval=5 (works, but did take maybe 20+ seconds before it gave me the chance to hit 'y' to confirm on first attempt) - 2nd time of ru

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

I also just noticed that my PUBLIC server is NOT rounding the values ... but local server is? [image: Rounding_weewx_webpage.PNG] On Tuesday, September 8, 2020 at 1:24:16 PM UTC-4 Tom Cichowicz wrote: > wow... OK that fixed! ((Link to page) >

[weewx-user] Re: Images

This worked. Thanks for the help. I was also able to rearrange some if the images the way I like them. On Friday, September 4, 2020 at 1:27:19 PM UTC-5 J Jones wrote: > Thank you. I was in the directory but only saw the skins.conf file. Giving > it a shot now. > > On Thursday, September 3, 2020

Re: [weewx-user] weewx-Weather34 installation questions

On Tuesday, September 8, 2020 at 3:50:22 AM UTC-7, ExprmntAl wrote: > How can I determine that "configobj" is installed normally? > > It could have been installed via dpkg or pip or pip3, and you might have python2 'and' python3 installed on your system, so you need to check 3 ways. dpkg -l |

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

On Tuesday, September 8, 2020 at 9:43:22 AM UTC-7, Tom Cichowicz wrote: > mqtt_websockets_host = "localhost" > > The websockets host needs to be the fully qualified hostname (or ip) of the computer. You can't use 'localhost'. That would cause your browser to try to connect to the host

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

These are my conf - file settings.. skin.conf # MQTT Websockets defaults mqtt_websockets_enabled = 1 mqtt_websockets_host = "localhost" mqtt_websockets_port = 9001 mqtt_websockets_ssl = 0 mqtt_websockets_topic = "weather/loop" disconnect_live_website_visitor = 180 w

Re: [weewx-user] Enabling historical data collection on new install

wow, this is an exercise in troubleshooting! It seems that copy and paste is not friendly when doing this sort of thing. Typing out all the values, units, etc appears to have worked. The other issue I encountered is that it doesn't handle the change from BST to GMT as there are duplicate reco

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

Are you using Firefox? That does not connect for me while Edge does. -- 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. To vi

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

Your configuration of MQTT in the Belchertwon skin.conf is complete? And are you using the right topics in MQTT? It would be best if you posted the MQTT sections of your weex.conf and Belchertown skin.conf here. Otherwise it is very hard for someone to figure out what might be wrong. Op dinsdag

Re: [weewx-user] weewx upgrade from python2 to python3

Thanks, Tom, that seems to have fixed it. Sorry to have added to the confused thread. Bob On Monday, September 7, 2020 at 6:47:54 PM UTC-4 tke...@gmail.com wrote: > In the file emoncms.py, try changing lines 290-293 from > > def check_response(self, response): > txt = response.read(

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

Vince; thanks for the reply ... I'll keep searching. (I've already followed those posts) I have a running MQTT broker - that is returning published messages, my local webserver for weewx that has Belchertown skins enabled displaying the data. On Monday, September 7, 2020 at 6:20:57 PM U

Re: [weewx-user] Enabling historical data collection on new install

I've obtained the historical data directly from the weather station and am trying to import using wee_import. I have configured the required info but am facing the following problem and don't know what it means and how to fix it. Can anyone help please? pi@rasptest:/home/weewx/bin $ sudo ./we

Re: [weewx-user] weewx-Weather34 installation questions

I installed weewx using the "DEB (packaged)" installation in late July and it has been running since then and populating the seasons skin from my Tempest weather station. I have also installed the WeatherFlow extension to work with the Tempest. Below is the version from the weewx.conf file. *

Re: [weewx-user] WS23xx error when trying to set interval

Hi Tom, Sorry, still erroring... root@raspberrypi:/home/weewx/bin# ./wee_device --set-interval=5 Using configuration file /home/weewx/weewx.conf Using WS23xx driver version 0.41 (weewx.drivers.ws23xx) Changing the interval will clear the station memory. Interval is 60 Set interval to 5 minutes (y