Re: [weewx-user] Re: weewx server?

[Doug Jenkins]

Glad some of you find this useful.

I have been using this method since it came out this summer (July 2022). I
run my infrastructure (Web Server, WeeWX, MQTT, MariaDB) as containers in
one stack in its own network all in Docker. I do this to limit what the
cloudflare tunnel can access on my network (just WeeWx stuff). All of this
works in docker in one stack and one YAML file!

Like Tom Lawerence mentioned in the video I attached, you have to put
Cloudflare in your "circle of trust" as you are depending on them for both
the client and server/edge side of the tunnel. You have to make that
determination on your own if you are comfortable with that.

As other methods mentioned here, they are all great alternatives. I was not
aware adafriut offered a dashboard to present your data. That can be a good
alternative than going through the hassle of hosting a full website for
your station.

If I get a free moment in a few weeks, I can post a step-by-step article on
onboarding your WeeWX weather station as a public website using Cloudflare.
I think it can help a lot of users who struggle with the network & security
setup.

DDJ

On Wed, Jan 4, 2023 at 12:49 PM vince  wrote:

> On Tuesday, January 3, 2023 at 6:41:01 PM UTC-8 do...@dougjenkins.com
> wrote:
>
>> If you are willing to roll up your sleeves and get technical, serving
>> your website at home can be done safely and securely without changing your
>> firewall. There are some steps to do, but at the end it will save you money
>> and it will give you some real-world IT experience.
>>
>>
> Very cool - thanks for the pointer to the video.  I hadn't previously
> figured out the Zero Trust terminology enough to try the tunnel stuff. I'll
> have to try the tunnel thing too 
>
> For the original poster, Doug's steps 1-3 are very easy.  I'd previously
> done that using Google Domains ($12/year).
>
> Note - you probably still want to possibly harden your weewx webserver a
> bit.  There are zillions of bots trying to attack web servers 'especially'
> all things WordPress.  If you go just with a vanilla weewx setup you're
> likely in very good shape straight out of the box.  Cool cheap option for
> sure.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/56afd382-a9ba-49e7-831f-2813872d6db0n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0w%3DqKpv7m9wf--LgrbuHS2tui8JWnigPePzb9hoXuQZ0A%40mail.gmail.com.

Re: [weewx-user] Re: weewx server?

[Doug Jenkins]

If you are willing to roll up your sleeves and get technical, serving your
website at home can be done safely and securely without changing your
firewall. There are some steps to do, but at the end it will save you money
and it will give you some real-world IT experience.

So to self-host your WeeWX website, I would do the following

NOTE: This is a high-level checklist. there are lot of steps for each item.

1. Get a domain name. Porkbun.com is cheap, but Google Domains works too.
2. You need to have a NameServer Service to tell the internet where your
website is. My checklist will use CloudFlare (free). They have a bunch of
services that we are going to use to make this happen.
3. Once you buy your domain name, you will need to point it to Cloudflare's
Servers. Cloudflare's setup will walk you through it. This will take 4 - 24
hours to propagate across the internet (your response may vary).
4. Once it is propagated (Cloudflare sends an email to you), You will setup
your website inside the tool. We are going to setup "Zero Trust" tunnel
that will create a secure tunnel between cloudflare and your server. I have
a video that walks this whole process through (including configuring
cloudflare)

https://youtu.be/eojWaJQvqiw

This tunnel is the KEY. This tunnel will encrypt the traffic coming to your
domain, secure your domain with an SSL Certificate, and essentially expose
it directly on your server. Again this service is free for small domains
(like weather station sites!) and does not expose your network to the
internet directly.

5. Within the tool you will configure your Server name and the port (80)
that your webserver is now hosting your WeeWX site. You will have to
install a package from Cloudflare to act as the broker for the connection.
The video goes over a container-approach, but in Cloudflare's
documentation, they cover a linux server install.

The benefits of doing this approach are:

1. Site gets a free SSL certificate (https:) that is handled by Cloudflare
2. Cloudflare acts as a reverse proxy to broker your connection from the
internet to your server and port.
3. connection between Cloudflare and your server is secure. You do not need
to open a port for this.
4. You get website statistics and other security features for your website
for free from cloudflare.

Check out the video and let me know if this helps. There are other
resources on the internet that can help on this setup.

Doug Jenkins

On Tue, Jan 3, 2023 at 11:46 AM vince  wrote:

> If you're asking that question, you really shouldn't do it for security
> reasons.  There are s many bots and automated scanners out there
> looking for victim sites that you'd be massively attacked within literally
> a minute or two. Please don't.  Really.
>
> But to answer - you'd need to alter your home firewall to permit incoming
> web traffic to 'only' that computer and tcp/ip port.  Ideally you would
> have your webserver also running 'only' https (a bit hard on a LAN to do),
> have lots of logging (syslog), blocking typical attacks (fail2ban) and
> hopefully even alerting that attacks are even happening.  You should also
> segment your network so it's on an isolated VLAN so it can't be used as a
> jumping off point to attack your other home network devices.  That requires
> special network hardware usually, and some additional level of expertise.
> It's a big lift to do correctly.
>
> Simpler answer is to spend a few bucks/month and spin up a AWS Lightsail
> VM and use weewx's RSYNC uploader to update the Internet webserver with the
> weewx-generated data automatically.  Lightsail is free for 3 months trial,
> then $3.50/month.  Small price to pay for peace of mind.
>
> You'd still have to harden your Lightsail VM, but that's far easier to
> learn how to do.  Get a lets-encrypt ssl certificate to use only https.
> Use the Lightsail console to let 'just' https in.  Install fail2ban.   Very
> doable.  Lots of guides out there for how to do so if you google a bit.
>
>
> On Tuesday, January 3, 2023 at 4:23:59 AM UTC-8 kb3...@gmail.com wrote:
>
>> I was able to get the local network page of my weewx station but how do
>> you see this from the public ip?
>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4a1e2ea1-74c3-4f08-ac28-2267cb1148f5n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/4a1e2ea1-74c3-4f08-ac28-2267cb1148f5n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
Yo

Re: [weewx-user] Is there a way to suppress LOOP entries in the stdout from WeeWX?

[Doug Jenkins]

Vince/Tom:

Actually I built my own image. It essentially builds weewx via python
setup.py and I add a few popular extensions (mqtt, forecast, belchertown)
as a "batteries include" release.

My docker image performs all of it's logging to stdout, so you can review
the logs in your favorite orchestration tool (eg. I use portainer). My
docker image also supports MySQL/MariaDB connections if needed.


 I will create a public repo with my weewx docker setup. I will post back
here with a link and I will write a wiki article about it.

My biggest challenge is that my in laws are staying with us and I have kids
camping out in my office, so access to my workstation is limited until this
week is over. So please be patient until I get a chance to post it. :)

Doug Jenkins
Largoweather.com

On Wed, Nov 23, 2022, 7:21 AM t...@tom.org  wrote:

> Re the Docker image, Vince is right that it did not support anything but
> what I was using, which is x86-64 (I run my instances as Kubetnetes pods).
> Now it supports arm, arm64, and x86-64.
>
> Phusion is a weird base image, but it did a nice job of supporting the
> logging requirements of weewx. I would love a collaborator to either
> optimize this one or base it on another base altogether. I think Doug is
> working on something?
>
> On Tuesday, November 22, 2022 at 1:47:01 PM UTC-5 vince wrote:
>
>> Thanks for the explanation.  Doug+I are doing the same thing.
>> Suppressing LOOP via removing StdPrint and redirecting logging using the v4
>> logging to console as you documented for the wiki in the spring.
>> Difference is I'm building up from base debian as a starting point.
>>
>> [...tl;dr...]
>>
>> Doug's stuff has more dominos that have to be lined up to build the
>> image. He builds on top of Tom Mitchell's image, which builds on top of an
>> old pfusion base image, which has some uniquenesses in there for Docker if
>> I remember from poking around a bit.   I think pfusion is released for less
>> architectures too if I remember. I had to rebuild the whole stack starting
>> with pfusion when I was trying 64-bit Ubuntu and 64-bit RaspiOS on a pi
>> earlier this year and tried to build some Docker images on top of those
>> os.  Took a while.
>>
>> Results from a weewx perspective are the same once you get there of
>> course, but I wanted a simpler path to updating the os under the hood and
>> for playing around with switching the Docker host os version
>> (RaspiOS/Ubuntu) and 32/64 bit variants of the host os.  Change one line in
>> the Dockerfile and go for changing the weewx image os too.  Gotta love
>> containers.
>>
>> On Tuesday, November 22, 2022 at 5:07:41 AM UTC-8 Tom Keffer wrote:
>>
>>> StdPrint is sending messages directly to stdout via print() statements
>>> --- the logging facility is not involved at all. So, no, I would not expect
>>> that to work.
>>>
>>> Doug is using a log handler that sends log messages to "console," that
>>> is, stdout. So, what you're looking at is a mixture of print() statements
>>> and logging messages.
>>>
>>> Hope that helps.
>>>
>>>
>>>
>>> On Mon, Nov 21, 2022 at 5:09 PM vince  wrote:
>>>
>>>> Sorry for the late reply.  Rebuilding/consolidating my docker setups
>>>> and had a question...
>>>>
>>>> Removing StdPrint 'does' work for suppressing the LOOP messages in
>>>> Docker, but is there a way to get the same effect via a custom [Logging]
>>>> stanza ?
>>>>
>>>> I got very lost under the hood trying to follow how StdPrint is logging
>>>> at all.
>>>> Would this be expected to work ?
>>>>
>>>> [Logging]
>>>> [[loggers]]
>>>> [[[weewx.engine.StdPrint]]]
>>>> level = ERROR
>>>>
>>>>
>>>> On Sunday, March 27, 2022 at 4:28:52 AM UTC-7 Tom Keffer wrote:
>>>>
>>>>> Just remove "StdPrint" from the list of reporting services to be run.
>>>>> So, this
>>>>>
>>>>> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>>>>>
>>>>> becomes this
>>>>>
>>>>> report_services = weewx.engine.StdReport
>>>>>
>>>>>
>>>>> On Sun, Mar 27, 2022 at 4:24 AM Doug Jenkins 
>>>>> wrote:
>>>>>
>>>>>> Is there a way to suppress the LOOP data?
>>>>>>
>>>>> --
>>>>
>>> You r

Re: [weewx-user] Is there a way to suppress LOOP entries in the stdout from WeeWX?

[Doug Jenkins]

For my docker configuration for my weewx weatherstation, I add this
configuration right after the version = x.x.x line. Give it a couple of
empty lines to separate it out

###
[Logging]
version = 1
disable_existing_loggers = False

# Root logger
[[root]]
  level = {log_level}
  handlers = console,

# Additional loggers would go in the following section. This is useful
for tailoring logging
# for individual modules.
[[loggers]]

# Definitions of possible logging destinations
[[handlers]]

# Log to a set of rotating files
[[[rotate]]]
level = DEBUG
formatter = standard
class = logging.handlers.RotatingFileHandler
filename = /var/log/weewx.log
maxBytes = 1000
backupCount = 4

# Log to console
[[[console]]]
level = INFO
formatter = standard
class = logging.StreamHandler
# Alternate choice is 'ext://sys.stderr'
stream = ext://sys.stdout

# How to format log messages
[[formatters]]
[[[simple]]]
format = "%(levelname)s %(message)s"
[[[standard]]]
format = "%(asctime)s  {process_name}[%(process)d]
%(levelname)s %(name)s: %(message)s"
# Format to use for dates and times:
datefmt = %Y-%m-%d %H:%M:%S
[[[verbose]]]
format = "%(asctime)s  {process_name}[%(process)d]
%(levelname)s %(name)s: %(message)s"
# Format to use for dates and times:
datefmt = %Y-%m-%d %H:%M:%S

##




On Tue, Nov 22, 2022 at 8:07 AM Tom Keffer  wrote:

> StdPrint is sending messages directly to stdout via print() statements ---
> the logging facility is not involved at all. So, no, I would not expect
> that to work.
>
> Doug is using a log handler that sends log messages to "console," that is,
> stdout. So, what you're looking at is a mixture of print() statements and
> logging messages.
>
> Hope that helps.
>
>
>
> On Mon, Nov 21, 2022 at 5:09 PM vince  wrote:
>
>> Sorry for the late reply.  Rebuilding/consolidating my docker setups and
>> had a question...
>>
>> Removing StdPrint 'does' work for suppressing the LOOP messages in
>> Docker, but is there a way to get the same effect via a custom [Logging]
>> stanza ?
>>
>> I got very lost under the hood trying to follow how StdPrint is logging
>> at all.
>> Would this be expected to work ?
>>
>> [Logging]
>> [[loggers]]
>> [[[weewx.engine.StdPrint]]]
>> level = ERROR
>>
>>
>> On Sunday, March 27, 2022 at 4:28:52 AM UTC-7 Tom Keffer wrote:
>>
>>> Just remove "StdPrint" from the list of reporting services to be run.
>>> So, this
>>>
>>> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>>>
>>> becomes this
>>>
>>> report_services = weewx.engine.StdReport
>>>
>>>
>>> On Sun, Mar 27, 2022 at 4:24 AM Doug Jenkins 
>>> wrote:
>>>
>>>> Is there a way to suppress the LOOP data?
>>>>
>>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/d1e72f8a-5a6d-4a90-8df5-4722c38a544dn%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/d1e72f8a-5a6d-4a90-8df5-4722c38a544dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEA29dW4XRmKj4pB2k9xTXNHJ3n%2B8Dypsv4etjzCe%3Dg6ZQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEA29dW4XRmKj4pB2k9xTXNHJ3n%2B8Dypsv4etjzCe%3Dg6ZQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zyMcHY4WXM_Q20tsYJhN0KbDqEo9%3DoobkLP6RB3xH%3DRg%40mail.gmail.com.

Re: [weewx-user] Offload Webpage Generation?

[Doug Jenkins]

Another option that I have tested in the past is to setup your Pi with
MySQL/MariaDB and WeeWX to perform the archive activities only. Then setup
WeeWX on another machine on the network, using the Pi database connection
to just run the stdreport function.

That way you collect and hold the data on your Pi and use another machine
to query and render the html/reports.



On Tue, Oct 11, 2022, 7:24 PM Tom Keffer  wrote:

> You could remove all report generation from the RPi, then on a different
> computer use cron jobs to launch wee_reports
>  on a
> regular basis.
>
> On Tue, Oct 11, 2022 at 3:36 PM mlewi...@gmail.com 
> wrote:
>
>> I have a working WeeWx install on a Pi that is struggling to generate the
>> webpages in a timely fashion due to overall workload on the Pi. I would
>> like to offload the webpage generation to another machine somehow.
>>
>> The sole reason it is on the Pi is because I can put the Pi close to the
>> station for USB connectivity.
>>
>> Stringing a longer cable is not an option.
>> Moving the station is not an option.
>> Reducing overall load on the Pi is not an option.
>>
>> The current instance logs to a MySql/Maria DB on another machine.
>>
>> What are my options here? Some kind of USB over the network? The data is
>> all in a database, so this should be pretty simple to do. Tell WeeWx where
>> the data is and have it generate the reports, but not have it try to update
>> the data.
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/6e2e55eb-c874-4799-a43f-d54712af6a06n%40googlegroups.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAX1L0tFmQOBy3PrReiqFTOZyDpsVUa7-zi9E24FE%3Dknw%40mail.gmail.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yZ2kCkhcoYHxWou7zaBFmaXzeRRda2W5Udi1dzM6NQiA%40mail.gmail.com.

Re: [weewx-user] Re: Using Multiple MySQL databases

[Doug Jenkins]

Seth:

I think you have a couple of options to choose from. One concern I would 
have with MQTT is that it always publishes the latest record, so if your 
farm location is down for 1 hour, your remote will not get the records up 
to the last archive.

thinking about your use case now, It may make sense to setup the station on 
SQLite and rsync the database to your remote location after the archive 
period. that way if your farm location lost connection, you would know 
based on the last archive record at home and once you have a connection 
again, you would get all the data.

here is a wiki article on the github weewx repo that kind of explains this 
: Using the RSYNC skin as a backup solution · weewx/weewx Wiki (github.com) 
<https://github.com/weewx/weewx/wiki/Using-the-RSYNC-skin-as-a-backup-solution>

To answer your question about my other databases, for forecast and AQI, as 
Vince indicated earlier, there are a host of extensions available. The one 
I use for forecast is Weewx-Forecast by Matthew Wall ( 
matthewwall/weewx-forecast: 
forecasting extension for weewx (github.com) 
<https://github.com/matthewwall/weewx-forecast>) and I use a AQI extension 
to pull from my Davis Airlink AQI device ( chaunceygardiner/weewx-airlink: 
WeeWX extension to support Davis AirLink air quality sensor. (github.com) 
<https://github.com/chaunceygardiner/weewx-airlink>) 

hope this helps!

Doug Jenkins

On Wednesday, September 14, 2022 at 9:10:40 PM UTC-4 vince wrote:

> On Wednesday, September 14, 2022 at 4:47:53 PM UTC-7 Seth Ratner wrote:
>
>> But I also run various programs at home that reference the archive, and 
>> they won't work when the WeeWx host has lost internet. 
>>
> So I need two copies of the archive available at all times, one for each 
>> location. 
>>
>
> Still unclear why without knowing what you're running at the non-weewx 
> site.   Can you run that on the weewx host and upload the results to home 
> occasionally ?   Does the non-weewx site need to be totally up to date 
> always ? Is your internet 'slow' in terms of bandwidth or just unstable ?
>
> You're jumping to a solution but not really explaining the problem(s) and 
> why you have a split setup.
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9e98036d-592b-4ff4-8c7c-dc9ecbe3a7ffn%40googlegroups.com.

Re: [weewx-user] Re: Using Multiple MySQL databases

[Doug Jenkins]

I am not understanding the use case. If you are running MySQL both locally
and remotely for the archive, why don't you just replicate the local MySQL
instance to the remote on a schedule?

I run multiple weewx databases (aqi, forecast, archive) on mariadb and just
back it up daily to my NAS. If I needed a remote db, I would just restore
my backup on a separate instance.

On Wed, Sep 14, 2022, 5:51 PM Seth Ratner  wrote:

>
> Looks like I can just add another binding in [DataBingings], but in
> [StdArchive] I'm not sure I can have two archive processes run.
>
> I think these sections are all fine.
>
> [DataBindings]
> [[wx_binding]]
> database = archive_mysql
> table_name = archive
> manager = weewx.manager.DaySummaryManager
> schema = schemas.wview_extended.schema
> [[backup_binding]]
> database = archive_backup
> table_name = archive
> manager = weewx.manager.DaySummaryManager
> schema = schemas.wview_extended.schema
>
> ##
> [Databases]
>
> [[archive_sqlite]]
> database_name = weewx.sdb
> database_type = SQLite
>
> # MySQL
> [[archive_mysql]]
> database_name = weewx
> database_type = MySQL
>
> [[archive_backup]]
> database_name = weewx
> database_type = MySQL2
>
> ##
>
> #   This section defines defaults for the different types of databases.
>
> [DatabaseTypes]
>
> [[SQLite]]
> driver = weedb.sqlite
> # Directory in which the database files are located
> SQLITE_ROOT = /var/lib/weewx
>
> # Defaults for MySQL databases
> [[MySQL]]
> driver = weedb.mysql
> host = localhost
> user = weewx
> password = gt9drSvlB3ImZGS
>
> [[MySQL2]]
> driver = weedb.mysql
> host = 192.168.30.110
> user = weewx
> password = test
>
>
> But the [StdArchive] section only accepts one binding as far as I can tell:
>
>
> [StdArchive]
> archive_interval = 300
> record_generation = software
> loop_hilo = True
> data_binding = wx_binding  *<-- This is where I think I would
> need to be able to list two bindings... right?*
> log_success = True
> log_failure = True
> On Wednesday, September 14, 2022 at 4:38:38 PM UTC-5 Seth Ratner wrote:
>
>> Simple concept, but I'd like to use one local and one network db.
>> Poosible?
>>
>> Seems easy enough to add the second database to the config, but I don't
>> know if [DataBindings] can accept the second database.
>>
>> Anyone tried this?
>>
>> Seth
>>
>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/34a25b20-3d32-485d-a1e8-e627dcb712a0n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xp0UX-MKAoqwsqmrb1EBnTp%2BUx5gri3eXbSeL-8YLz8w%40mail.gmail.com.

Re: [weewx-user] Re: Weewx and Mqtt

[Doug Jenkins]

Troy:

You can dump out the topic from your broker. I found Pat O'Brien's mqtt
broker setup very helpful. I would read this for more insight

https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/

Doug Jenkins

On Mon, Sep 12, 2022, 7:43 PM Troy Roberts  wrote:

> I'm going to go out on a limb and say there is no mqtt topic labeled
> highOutsideTemp and lowOutsideTemp. If there is it might me labeled
> something different. Do you have a list of all the topics /weather?
>
> On Mon, Sep 12, 2022, 4:58 PM vince  wrote:
>
>> In the absence of any description of your setup, any logs or any snippets
>> from your config file(s) - no, no ideas.
>>
>> I've never heard of those two parameters nor where they might come from.
>>
>> On Monday, September 12, 2022 at 2:49:37 AM UTC-7 tsh...@gmail.com wrote:
>>
>>> Hi,
>>> I have weewx linked via mqtt to a homeassistant.
>>> Everything is working fine apart from the parameters highOutsideTemp and
>>> lowOutsideTemp which return incorrect results.
>>>
>>> I can't see any errors in the installation - just wondering if anyone
>>> has any ideas
>>>
>>> Thanks
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/zD-I9CmElsY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/f0b71c74-964a-45ac-9168-2ee9e111e186n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/f0b71c74-964a-45ac-9168-2ee9e111e186n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CABY4LHM4v9KxndqsTAWaUMkdLh0nbDHZY2fe2BYhwpbiO%3DXBaQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CABY4LHM4v9KxndqsTAWaUMkdLh0nbDHZY2fe2BYhwpbiO%3DXBaQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xwP9%2B4eA9QLjv57XComCBrBcm5pD28Hdb05%2B8DvSB%2BTA%40mail.gmail.com.

[weewx-user] Re: Errors connecting to remote MariaDB server

[Doug Jenkins]

Marcus:

I run MariaDB with my WeeWX Setup and yes using a comma is probably giving 
you some trouble. WeeWX maybe building a database connection string with 
your information and the comma is throwing the connection attempt.

I would recommend changing the password to the user account that is 
accessing the weewx account and omit using a comma or a semicolon. There 
are enough character/numeral combinations to keep your password strong.

just for reference, here is my MariaDB setup for my station. the password 
was obviously changed :)

== WEEWX.CONF START ==
#   This section binds a data store to a database.

[DataBindings]

[[wx_binding]]
# The database must match one of the sections in [Databases].
# This is likely to be the only option you would want to change.
database = archive_mariadb

# The name of the table within the database
table_name = archive

# The manager handles aggregation of data for historical summaries
manager = weewx.manager.DaySummaryManager

# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = user.weatherlink_live.schema


##

#   This section defines various databases.

[Databases]

# MySQL
[[archive_mariadb]]
database_name = weewx_davis_vp2
database_type = MariaDB


##

#   This section defines defaults for the different types of databases.

[DatabaseTypes]

# Defaults for MySQL databases
[[MariaDB]]
driver = weedb.mysql
# The host where the database is located
host =  172.16.1.25
# The user name for logging in to the host
user = weewx
# The password for the user name (quotes guard against parsing 
errors)
password = password

== WEEWX.CONF END =

Doug
On Tuesday, August 30, 2022 at 8:01:22 AM UTC-4 marcusz...@gmail.com wrote:

> Hello all,
>
> I am stuck with an error that I do not understand with the configuration 
> of my remote MariaDB server.
>
> *What I checked:*
> - Remote access on my database server is enabled.
> - Remote login from the weewx host is working as well.  (confirmed with 
> mariadb -uweewxdb -hdatabase.homenet.local -p;  entered the password and 
> had access)
>
> *My weewx.conf file:  (shortened)* 
> [DataBindings]
> [[wx_binding]]
> database = archive_mysql
> table_name = archive
> manager = weewx.manager.DaySummaryManager
> schema = schemas.wview_extended.schema
> [Databases]
> # MySQL
> [[archive_mysql]]
> database_name = weewx
> database_type = MySQL
> [DatabaseTypes]
> # Defaults for MySQL databases
> [[MySQL]]
> driver = weedb.mysql
> host = database.homenet.local
> user = weewxdb
> password = ComplexPrefix,weewxdb  # tried also with single and 
> double quotes
>
>
> My assumption is, that the comma in my password might cause trouble.
> But I also tried it with 'ComplexPrefix,weewxdb' or 
> "ComplexPrefix,weewxdb", and neither helps.
>
>
> *I get an error in my Python:*
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
> File "/usr/share/weewx/weedb/mysql.py", line 54, in gua>
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
>   return fn(*args, **kwargs)
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
> File "/usr/share/weewx/weedb/mysql.py", line 136, in __>
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
>   connection = MySQLdb.connect(host=host, port=int(port>
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
> File "/usr/lib/python3/dist-packages/MySQLdb/__init__.p>
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
>   return Connection(*args, **kwargs)
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
> File "/usr/lib/python3/dist-packages/MySQLdb/connection>
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
>   super(Connection, self).__init__(*args, **kwargs2)
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
>   *TypeError: connect() argument 3 must be str, not list*
> Aug 30 11:34:46 weewx python3[2909]: weewx[2909] CRITICAL __main__: 
>   Exiting.
>
>
> What is the next thing that I should try?
>
> Thanks and best regards,
>Marcus
>

-- 
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 view this discussion on the web vis

Re: [weewx-user] Database details - what to do in this instance (2 specific questions)?

[Doug Jenkins]

Kruse:

I would recommend looking right here in the users' guide for all the things
you need to backup:

http://weewx.com/docs/usersguide.htm#backup

A good idea would be to write a quick bash script that copies these files
off to a temp directory, then zip that directory and save the files to an
external device. Schedule this on cron to run daily. 99.9% of the time the
sqlite database is inert, so you can copy the database with no issues with
WeeWX.



On Sun, Aug 28, 2022 at 2:14 PM Kruse Ludington 
wrote:

> I know the answer is probably buried somewhere and apologies but if nobody
> is able to explain exactly the answers to #1 and #2 below, maybe someone
> can point me to a specific spot in the voluminous weewk wiki/help files so
> I don't need to read war and peace before I figure it out (thank you!)?
>
> I have a Raspberry Pi 4b 8gig running on a 1tb ssd (yes overkill) running
> weewx - and since I do a ton of other stuff with it as well, I often back
> up the entire storage (only after disabling weewx and everything else that
> would run on it when it is rebooted, to make the last step of the restore
> process easier - see the below * asterisk). The weewx install on that RPI
> is using the default database that it comes with when installed (no changes
> in that regard).
>
> Long story short, sometimes I do need to do a restore when I try to do
> something fancy that makes the whole thing blow up (the RPI - unrelated
> things on the same hardware) in my face. In that case, I do a restore and I
> am good to go no issues.
>
> Except one thing.
>
> If the restore is from a one week old backup - I've lost one week of data
> in the weewx default database.
>
> So, from that point of view, if I am able to log into the RPI with VNC
> viewer or telnet/whatever on the screwed up RPI, as a first step before the
> whole restore process -
>
> Steps to do right at that point -
>
> 1. What files do I copy from the RPI to later copy back onto the RPI
> restored from the backup so no data is lost? Is the DB all just one file or
> is it a bunch of files (e.g., files for each index, etc.)?
>
> 2. Once the restored RPI is back up and running, BEFORE* weewx is
> launched, in addition to copying the files from #1 above onto the newly
> restored RPI weewx instance - are there any other config files or anything
> like that I need to adjust prior to firing everything back up on the
> restored RPI weewx instance?
>
> Thanks for all your help!
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/4a6a579e-0b32-4bf0-a6ce-1980765603f3n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xk40ri95cSZvEmJibAR3wN%2B6APHZMsD%3D1uDHP81guZJQ%40mail.gmail.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Doug Jenkins]

We need to see the ftp section of the weewx.conf file in order to help

On Tue, Aug 23, 2022, 8:11 AM Eric Gammeter  wrote:

> Okay-  Looking on my web site target directory (/weather/4.8) there are
> not any .css or .js files present, only .png and .html files.  What steps
> will I need to re-populate them?  I guess I am reliant upon WEEWX to ftp
> whatever files it needs to operate.
>
> On Monday, August 22, 2022 at 5:00:21 PM UTC-4 do...@dougjenkins.com
> wrote:
>
>> Can you confirm on the target of the website that seasons.css file is
>> there? Matt responded earlier that if you use the developer tools in your
>> browser, you will see that the seasons.css file is missing on your apache
>> web server directory.
>>
>> Since you are FTP'ing the files, verify that you are grabbing all the
>> files from the source directory. It should include .js, .css, and .png, and
>> .html files.
>>
>> DDJ
>>
>> On Mon, Aug 22, 2022 at 3:34 PM Eric Gammeter  wrote:
>>
>>> I have WEEWX running on the Rpi3; also on that Rpi is Apache web
>>> server.  From there, all I know of is the WEEWX ftp process to upload files
>>> to my web site.  I access my web site file manager and see all (37?) files
>>> there.  So- the only mirroring I know of is WEEWX ftp'ing up to the web
>>> site.   I installed WEEWX using the DEB package.
>>>
>>> On Monday, August 22, 2022 at 11:16:27 AM UTC-4 matthew wall wrote:
>>>
 the seasons.js and seasons.css files are not on your public-facing web
 server.  so whatever mechanism you use to mirror your pi to n8aay.net
 is not copying all of the files.

 use the 'developer tools' option in your web browser to diagnose this
 kind of problem.  that will provide lots of information about which files
 are loaded, which css attributes are applied (or not), javascript errors,
 etc.

 On Monday, August 22, 2022 at 9:58:25 AM UTC-4 n8a...@gmail.com wrote:

> Just to reiterate my situation:  When I view my local Rpi ip address:
> 192.168.1.38/weewx) I see the full graphic-laden screen.  That is
> good!  When I view my internet source (https://www.n8aay.net) I see
> only the text-only version.
>

 [image: no-js-css.png]

>>> --
>>>
>> 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.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/c8a13bf2-af31-486e-8382-1cc0e0b922a3n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/00b4efbf-4d61-426e-96a4-3ef6e48769b8n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yNgPbskuP8T0%3DZNFTr0NJFtf%3DCqy2fToFJVKB6NwbSwQ%40mail.gmail.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Doug Jenkins]

Can you confirm on the target of the website that seasons.css file is
there? Matt responded earlier that if you use the developer tools in your
browser, you will see that the seasons.css file is missing on your apache
web server directory.

Since you are FTP'ing the files, verify that you are grabbing all the files
from the source directory. It should include .js, .css, and .png, and .html
files.

DDJ

On Mon, Aug 22, 2022 at 3:34 PM Eric Gammeter  wrote:

> I have WEEWX running on the Rpi3; also on that Rpi is Apache web server.
> From there, all I know of is the WEEWX ftp process to upload files to my
> web site.  I access my web site file manager and see all (37?) files
> there.  So- the only mirroring I know of is WEEWX ftp'ing up to the web
> site.   I installed WEEWX using the DEB package.
>
> On Monday, August 22, 2022 at 11:16:27 AM UTC-4 matthew wall wrote:
>
>> the seasons.js and seasons.css files are not on your public-facing web
>> server.  so whatever mechanism you use to mirror your pi to n8aay.net is
>> not copying all of the files.
>>
>> use the 'developer tools' option in your web browser to diagnose this
>> kind of problem.  that will provide lots of information about which files
>> are loaded, which css attributes are applied (or not), javascript errors,
>> etc.
>>
>> On Monday, August 22, 2022 at 9:58:25 AM UTC-4 n8a...@gmail.com wrote:
>>
>>> Just to reiterate my situation:  When I view my local Rpi ip address:
>>> 192.168.1.38/weewx) I see the full graphic-laden screen.  That is
>>> good!  When I view my internet source (https://www.n8aay.net) I see
>>> only the text-only version.
>>>
>>
>> [image: no-js-css.png]
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/c8a13bf2-af31-486e-8382-1cc0e0b922a3n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yDf%3DQjn27qRHJ6%3D%2BqEAsjh8wBPRcvGRnosdPe6M3BZLA%40mail.gmail.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Doug Jenkins]

The other thing to check is make sure you have the permissions set
correctly for your web server account to access the subdirectories that are
published. One thing I do is make sure the target public_html directly has
read/write permissions for the weewx account and read permissions that are
inheritable by the webserver account.

Once that is set, I clear the public_html directly completely (all files
and folders) and restart weewx. it will recreate everything (including the
folders) with the correct permissions.



On Sun, Aug 21, 2022 at 12:17 PM Eric Gammeter  wrote:

> Aug 21 12:00:55 raspberrypi3WEEWX weewx[606] DEBUG weeutil.ftpupload: 56
> ./index.html
> 522bce22f22f09c2ee428a8373f9f8d72f490b88a1463d82971d8ff3630fa1d2
> Aug 21 12:00:55 raspberrypi3WEEWX weewx[606] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/index.html to /weather/4.8/index.html
>
>
>
> [[SeasonsReport]]
>
> # The SeasonsReport uses the 'Seasons' skin, which contains the
>
> # images, templates and plots for the report.
>
> skin = Seasons
>
> enable = true
>
>
>
> [[SmartphoneReport]]
>
> # The SmartphoneReport uses the 'Smartphone' skin, and the images
> and
>
> # files are placed in a dedicated subdirectory.
>
> skin = Smartphone
>
> enable = true
>
> HTML_ROOT = /var/www/html/weewx/smartphone
>
>
>
> [[MobileReport]]
>
> # The MobileReport uses the 'Mobile' skin, and the images and
> files
>
> # are placed in a dedicated subdirectory.
>
> skin = Mobile
>
> enable = true
>
> HTML_ROOT = /var/www/html/weewx/mobile
>
>
>
> [[StandardReport]]
>
> # This is the old "Standard" skin. By default, it is not enabled.
>
> skin = Standard
>
> enable = false
>
>
>
>
> Station uses VANTAGE weather station.
>
>
> Version:  4.8.0
>
> On Sunday, August 21, 2022 at 11:51:22 AM UTC-4 Eric Gammeter wrote:
>
>> both of the INDEX.HTML files referred to above are updating every 30
>> minutes.
>>
>> On Sunday, August 21, 2022 at 11:49:11 AM UTC-4 Eric Gammeter wrote:
>>
>>> Seemingly out of the blue I have a problem with the INDEX.HTML.  IE:
>>> When I look at my Rpi (192.168.1.38/weewx) in a browser locally-  the
>>> correct report formatting is there and it looks fine (has all it's graphs);
>>> however when I go to the web address (http://www.n8aay.net) the index
>>> file that I see there is only "formatted for RSS" (that is:  no graphics,
>>> only text).  I did recently upgrade to v 4.8.0
>>> ?   /Thanks, EG
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0c23f1d6-4c73-4dd8-8f01-d1fe1705d1e0n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zV%3D6NOGeArKBfEjNaTdZqRuHnqAvmxdX7P%3D8PLmC%2BvpQ%40mail.gmail.com.

Re: [weewx-user] Re: problem with INDEX.HTML file version

[Doug Jenkins]

Eric:

First clear your  browser cache. you can check this by running in-private
browsing in either edge or chrome.

if that doesn't work, we are going to need a lot more information to help.
Specifically:

1. What is your web server?
2. What port is your webserver serving weewx (assuming 80)
3. How are you routing your n8aay.net domain to your local RPi?
4. Do you have your firewall properly configured to route incoming 80/443
traffic to your RPi?

On Sun, Aug 21, 2022 at 12:17 PM Eric Gammeter  wrote:

> Aug 21 12:00:55 raspberrypi3WEEWX weewx[606] DEBUG weeutil.ftpupload: 56
> ./index.html
> 522bce22f22f09c2ee428a8373f9f8d72f490b88a1463d82971d8ff3630fa1d2
> Aug 21 12:00:55 raspberrypi3WEEWX weewx[606] DEBUG weeutil.ftpupload:
> Uploaded file /var/www/html/weewx/index.html to /weather/4.8/index.html
>
>
>
> [[SeasonsReport]]
>
> # The SeasonsReport uses the 'Seasons' skin, which contains the
>
> # images, templates and plots for the report.
>
> skin = Seasons
>
> enable = true
>
>
>
> [[SmartphoneReport]]
>
> # The SmartphoneReport uses the 'Smartphone' skin, and the images
> and
>
> # files are placed in a dedicated subdirectory.
>
> skin = Smartphone
>
> enable = true
>
> HTML_ROOT = /var/www/html/weewx/smartphone
>
>
>
> [[MobileReport]]
>
> # The MobileReport uses the 'Mobile' skin, and the images and
> files
>
> # are placed in a dedicated subdirectory.
>
> skin = Mobile
>
> enable = true
>
> HTML_ROOT = /var/www/html/weewx/mobile
>
>
>
> [[StandardReport]]
>
> # This is the old "Standard" skin. By default, it is not enabled.
>
> skin = Standard
>
> enable = false
>
>
>
>
> Station uses VANTAGE weather station.
>
>
> Version:  4.8.0
>
> On Sunday, August 21, 2022 at 11:51:22 AM UTC-4 Eric Gammeter wrote:
>
>> both of the INDEX.HTML files referred to above are updating every 30
>> minutes.
>>
>> On Sunday, August 21, 2022 at 11:49:11 AM UTC-4 Eric Gammeter wrote:
>>
>>> Seemingly out of the blue I have a problem with the INDEX.HTML.  IE:
>>> When I look at my Rpi (192.168.1.38/weewx) in a browser locally-  the
>>> correct report formatting is there and it looks fine (has all it's graphs);
>>> however when I go to the web address (http://www.n8aay.net) the index
>>> file that I see there is only "formatted for RSS" (that is:  no graphics,
>>> only text).  I did recently upgrade to v 4.8.0
>>> ?   /Thanks, EG
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0c23f1d6-4c73-4dd8-8f01-d1fe1705d1e0n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0wbeM6xh86%3DeFzJ%2B5aOrKrtVAK1XdGTP6SxhHZj3HJoHA%40mail.gmail.com.

Re: [weewx-user] Belchertown Skin - UV & Solar Radiation Sensors

[Doug Jenkins]

Clay:

I have the same setup and I am able to show both UV and Solar Radiation
sensors. First how are you connecting WeeWX to the station? Are you using a
data logger or WeatherLink Live?

On Sun, Aug 14, 2022 at 12:23 PM ccroom  wrote:

> I just upgrade my station to a Davis Vantage Pro2+ with UV & Solar
> Radiation Sensors.  I am using the basic Belchertown skin and would like it
> now to show the readings from these 2 new sensors.  I have looked at the
> Belchertown instructions and reviewed the weesx.conf file but can't find
> anything to point me in the right direction.  Can someone assist?  Clay
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/fe725267-0a67-4392-8758-27d56be01476n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0z8rKav-701mHJ_eSr0-MH%3DUVoEFpZbpyn1h_Tf2x4C%2Bg%40mail.gmail.com.

Re: [weewx-user] weewx airlink update

[Doug Jenkins]

No problem. I reviewed the airlink proxy code and it is a bit of effort to
get setup and configured. I personally do not use the proxy as I am just
polling the sensor every 5 minutes.

What I would do for now is just setup the weewx airlink driver with your
station and set the archive interval to 60 seconds and see how that goes.

DDJ



On Sat, Aug 13, 2022 at 9:53 AM  wrote:

> Hello Doug.
>
>
>
> Thx for the Help. I've tried to somehow get that with the proxy. But
> unfortunately without success. Since I'm not a professional in such things,
> for me it's mostly stationery what's written there. Is there a more
> detailed guide on how to install this proxy? How can I start it
> afterwards and check whether it is running?
>
> Excuse my "dummy" question ;-)
>
>
>
> Greeting
>
>
>
> *Von:* weewx-user@googlegroups.com  *Im
> Auftrag von *Doug Jenkins
> *Gesendet:* Freitag, 12. August 2022 20:17
> *An:* weewx-user@googlegroups.com
> *Betreff:* Re: [weewx-user] weewx airlink update
>
>
>
> You can by setting your archive interval to 60 seconds in the weewx conf
> file here
>
>
>
> [StdArchive]
>
>
>
> # If the station hardware supports data logging then the archive
> interval
>
> # will be downloaded from the station. Otherwise, specify it (in
> seconds).
>
> archive_interval = 300
>
>
>
> Now with the Airlink driver, you may get a timeout from the API if you
> poll it all the time. John Kline has another repo that creates a proxy
> service for the airlink driver. that repo is here : 
> chaunceygardiner/airlink-proxy:
> Proxy server for Davis AirLink air quality sensor. (github.com)
> <https://github.com/chaunceygardiner/airlink-proxy>
>
>
>
> DDJ
>
>
>
> On Fri, Aug 12, 2022 at 2:10 PM Meteo Oberwallis 
> wrote:
>
> Hello everyone.
>
> I use the interval of 10 minutes at Weewx. Now, of course, the fine dust
> pollution is only measured at ten-minute intervals. Is there any way to set
> this interval to every minute? Then it would also be possible to save the
> particulate matter values ​​in a separate SQLite database? Has that
> possibly already run someone of you?
>
> It`s the original Davis Air Quality Sensor.
>
>
>
> I have this -> https://github.com/chaunceygardiner/weewx-airlink
>
>
>
> Thank for our Help`s
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/L351f8T97jg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CACC0i0wqNWKiiuHy13-0pSf-4O3CRWYXBDLtbhK3HDWZFcuhLw%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CACC0i0wqNWKiiuHy13-0pSf-4O3CRWYXBDLtbhK3HDWZFcuhLw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/000e01d8af1c%241efe0a60%245cfa1f20%24%40bluewin.ch
> <https://groups.google.com/d/msgid/weewx-user/000e01d8af1c%241efe0a60%245cfa1f20%24%40bluewin.ch?utm_medium=email&utm_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xojh2SNj5DGU%3Dg_Xp%2BHcMr2xqjbpY9my24XCGc4op_dg%40mail.gmail.com.

Re: [weewx-user] Weewx connectivity restored - a success/appreciation post

[Doug Jenkins]

Wow! At first I thought it was just a super-imposed image, but it is the 
real deal! 

If I see someone walk in a bar with that shirt, I would tell the bartender 
to pour them a drink as they know about the weather!

:)

On Friday, August 12, 2022 at 4:46:44 PM UTC-4 tke...@gmail.com wrote:

> That's awesome! 
>
> I'll bet you could go into any bar in the world wearing that and get a 
> free drink. :-)
>
> On Fri, Aug 12, 2022 at 9:48 AM vince  wrote:
>
>> ok the back makes it beyond good.
>>
>> On Friday, August 12, 2022 at 8:20:54 AM UTC-7 brentonw...@gmail.com 
>> wrote:
>>
>>> also, here is the back!
>>
>>  
>>
>> -- 
>>
> 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.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/6130c6f7-6ac9-4b4c-84d4-8dd7177434b9n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e2f4d347-808f-4232-9c0b-c106bbf419e1n%40googlegroups.com.

Re: [weewx-user] weewx airlink update

[Doug Jenkins]

You can by setting your archive interval to 60 seconds in the weewx conf
file here


[StdArchive]

# If the station hardware supports data logging then the archive
interval
# will be downloaded from the station. Otherwise, specify it (in
seconds).
archive_interval = 300

Now with the Airlink driver, you may get a timeout from the API if you poll
it all the time. John Kline has another repo that creates a proxy service
for the airlink driver. that repo is here : chaunceygardiner/airlink-proxy:
Proxy server for Davis AirLink air quality sensor. (github.com)


DDJ

On Fri, Aug 12, 2022 at 2:10 PM Meteo Oberwallis 
wrote:

> Hello everyone.
> I use the interval of 10 minutes at Weewx. Now, of course, the fine dust
> pollution is only measured at ten-minute intervals. Is there any way to set
> this interval to every minute? Then it would also be possible to save the
> particulate matter values ​​in a separate SQLite database? Has that
> possibly already run someone of you?
> It`s the original Davis Air Quality Sensor.
>
> I have this -> https://github.com/chaunceygardiner/weewx-airlink
>
> Thank for our Help`s
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9d580716-93d3-41d4-87c5-54d345e583e8n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0wqNWKiiuHy13-0pSf-4O3CRWYXBDLtbhK3HDWZFcuhLw%40mail.gmail.com.

Re: [weewx-user] Re: Solid non-Raspbian platform for WeeWx + MariaDB?

[Doug Jenkins]

Windows 10 has ssh built into its powershell terminal. This is my little
checklist I use for all my ubuntu based distributions.

Create SSH Keys & harden SSH Access
URL : https://kb.iu.edu/d/aews
===

1. First ensure you have a RSA key generated on your windows 10 workstation
2. On the remote server, create the ssh directory and authorized_keys file
mkdir -p ~/.ssh
touch ~/.ssh/authorized_keys
3. Run this command on your PC in powershell replacing SERVER
type $env:USERPROFILE\.ssh\id_rsa.pub | ssh SERVER " cat >>
.ssh/authorized_keys"
4. login to the console of the new server and harden SSH
a. sudo nano /etc/ssh/sshd_config
i. PasswordAuthentication no
ii. PermitEmptyPasswords no
iii. MaxAuthTries 3
iv. ClientAliveInterval 300   #5 minute idle timeout
v. ClientAliveCountMax 3
vi. PermitRootLogin no
vii. AllowUsers %USERNAME%
b. sudo systemctl reload sshd.service

All you need to do in Windows is start powershell and type ssh
USERNAME@server and you are in

DDJ

On Fri, Aug 12, 2022 at 12:47 PM vince  wrote:

> Using keys generated on putty for access to a linux server was always
> painful in my (fortunately ancient) experience.  I always added cygwin to
> my windows systems to get a real shell and ssh client rather than the putty
> kludges.  I'm sure what you're trying is doable, you just need to find the
> magic incantation to generate a key that a modern Linux sshd supports.
>  It's also possible to generate your key on linux and import it into
> putty's setup the other way, but it's been so many years since I had to use
> putty that my memory is hazy on how to do that.
>
> I don't see any difference in users between raspios and ubuntu other than
> the name of the built-in canned default user.  They're both debian(ish)
> under the hood.
>
> Resetting the mariadb root password is something I 'have' done
> occasionally when I mess up the initial setup.  See if (this link)
> 
>  helps
> any.
>
> If it's me, I'd work the problems one by one rather than punting the base
> os by reflex out of frustration.
>
> But consider adding cygwin and ssh to your windows setup if you're going
> to do a lot of ssh'ing into linux hosts.  It'll make your life 'much'
> easier.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9f815966-942d-4a54-b4a1-f9c38e033bfdn%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0wEKdQvjxVyaPrrsoQo%3D4kSTC%2Bwbb_YYS_MoK%3Dz%2BzrM6Q%40mail.gmail.com.

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Doug Jenkins]

Tom, I forgot to mention that I also modernized the logging for this 
driver. that was included in the second commit. I sent a pull request to 
the original author this morning.

On Monday, July 25, 2022 at 9:01:33 AM UTC-4 Doug Jenkins wrote:

> Jan & Tom:
>
> I might be a bit late on this thread, but I modified the driver and 
> created an installer package for it. I was able to test the installer, but 
> I cannot test the driver as I am not running on a Raspberry PI with a 
> BME280 and the other components.
> The Repo for this change is in my ddjlabs org on GitHub here:  
> https://github.com/ddjlabs/BYOWS_RPi
>
> JAN: If you have resolved your issue with Tom's suggestion, then please 
> let me know. I will send this to Jardi Martinez (original author) via pull 
> request so he can incorporate it for future releases.
>
> = Instructions to install it =
> 1. Download the v0.52 package from my github to the root directory of 
> WeeWX (eg /home/weewx)
>
> https://github.com/ddjlabs/BYOWS_RPi/archive/refs/tags/v0.51.zip
>
> 2. In the location of where you installed WeeWX (eg /home/weewx), run this 
> command:
>
> sudo ./bin/wee_extension --install v0.52.zip
>
> This process will make a backup of your weewx.conf and add the necessary 
> configuration items and code to the solution. The driver file will be 
> located in the bin/user folder within the WeeWX root directory. You can 
> modify it there as needed. This process will protect your changes as WeeWX 
> updates do not modify the user directory.
>
> = END INSTRUCTIONS =
>
> DDJ
>
> On Sunday, July 24, 2022 at 6:23:36 PM UTC-4 tke...@gmail.com wrote:
>
>> Ah! The advantages of cutting and pasting over a summarization. You were 
>> having a PYTHONPATH problem.
>>
>> Sounds like you got things working by using the "python -m 
>> user.byows_rpi" method.
>>
>> The other method should also work with an explicit PYTHONPATH. Something 
>> like
>>
>> *PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/byows_rpi.py*
>>
>> No matter. You got it working.
>>
>> As for the TypeError exception: now you're deep into the driver and I 
>> have no experience with it. You'll have to ask the author.
>>
>> -tk
>>
>>
>>
>> On Sun, Jul 24, 2022 at 3:04 PM Jan Bennett  wrote:
>>
>>> Following your above suggestion about a different way to try running the 
>>> file, I get two different responses depending on which one I run:
>>>
>>> /usr/share/weewx $ python user/byows_rpi.py 
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/user/byows_rpi.py", line 34, in 
>>> import weewx.drivers
>>> ModuleNotFoundError: No module named 'weewx'
>>>
>>> and 
>>>
>>> /usr/share/weewx $ python -m user.byows_rpi
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
>>> return _run_code(code, main_globals, None,
>>>   File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
>>> exec(code, run_globals)
>>>   File "/usr/share/weewx/user/byows_rpi.py", line 335, in 
>>> station = ByowsRpiStation()
>>>   File "/usr/share/weewx/user/byows_rpi.py", line 113, in __init__
>>> self.bme280_sensor.load_calibration_params(self.bme280_bus, 
>>> self.bme280_address)
>>>   File "/usr/local/lib/python3.9/dist-packages/bme280/__init__.py", line 
>>> 154, in load_calibration_params
>>> compensation_params.dig_T1 = read.unsigned_short(0x88)
>>>   File "/usr/local/lib/python3.9/dist-packages/bme280/reader.py", line 
>>> 40, in unsigned_short
>>> return self._bus.read_word_data(self._address, register) & 0x
>>>   File "/usr/local/lib/python3.9/dist-packages/smbus2/smbus2.py", line 
>>> 470, in read_word_data
>>> self._set_address(i2c_addr, force=force)
>>>   File "/usr/local/lib/python3.9/dist-packages/smbus2/smbus2.py", line 
>>> 354, in _set_address
>>> ioctl(self.fd, I2C_SLAVE, address)
>>> TypeError: argument must be an int, or have a fileno() method.
>>>
>>>
>>>
>>> On Sunday, July 24, 2022 at 3:42:56 PM UTC-6 Jan Bennett wrote:
>>>
>>>> Thank you. I verified that I was downloading the entire file by:
>>>>
>>>> renaming the /usr/share/ weewx/user/byows_rpi.py file and then I wget 
>>>> the file you linked

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Doug Jenkins]

Tom:

I can give it a look. Right now I am trying to get the install.py file
working to install the driver properly with the correct statements in
weewx.conf. Once I have that working, I can take a look at the logging.

One challenge is that I do not have a BME280, so I am probably going to
have to stub out those function calls to see if the solution will work in
principle.

hopefully Jan will help us out and verify the driver is working.

DDJ

On Sun, Jul 24, 2022 at 10:15 AM Tom Keffer  wrote:

> Your version has been altered --- it's missing an import statement.
>
> Here's the original version
> .
> You can give it a try.
>
> Doug: If you're going to work on the driver, perhaps you can port it to
> WeeWX V4? In particular, it uses the old-style "syslog", instead of the new
> style "logging 
> ".
>
>
> On Sun, Jul 24, 2022 at 6:04 AM Jan Bennett  wrote:
>
>> I have attached the byows_rpi.py file that I am using currently. Some of
>> the values haven't been changed for my equipment just yet. I need to add
>> the ground temp serial number and some additional wind vane values.
>>
>> Many thanks for your time and energy here!
>>
>>
>>
>>
>> On Sat, Jul 23, 2022 at 3:51 PM Tom Keffer  wrote:
>>
>>> Something is off. Could you send me the copy of byows_rpi.py you are
>>> using?
>>>
>>>
>>> On Sat, Jul 23, 2022 at 2:33 PM Jan Bennett 
>>> wrote:
>>>
 Thank you for your time in responding.

 It is correct that byows_rpi extension
  is mostly just a python file
 (byows_rpi.py) saved to /usr/share/weewx/user/

 I have followed the directions at the git repository and have verified
 with Change Driver 
 that I've done the appropriate things to weewx.conf as well.

 When I run either of the commands you listed I receive the same error
 as before:

 class ByowsRpi(weewx.drivers.AbstractDevice)
 NameError: name 'weewx' is not defined



 On Saturday, July 23, 2022 at 9:02:42 AM UTC-6 tke...@gmail.com wrote:

> 1, It looks like the byows_pi extension does not use the extension
> installer, so weewx has no way of knowing of its existence. This is why it
> doesn't show up in the list of available drivers.
>
> 2. As for running byows_pi directly, you have a slight problem with
> your paths. Try either this
>
> cd /usr/share/weewx
> python user/byows_rpi.py
>
>
> or this
>
> cd /usr/share/weewx
> python -m user.byows_rpi
>
>
> -tk
>
> On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett 
> wrote:
>
>> I should also note that when I 'sudo wee_config --reconfigure
>> --driver=user.byows_rpi --no-prompt' I see the following:
>>
>> Using configuration file /home/weewx/weewx.conf
>> Driver user.byows_rpi  failed to load: name 'weewx' is not defined
>>
>> On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:
>>
>>> Hey all -
>>>
>>> I am trying to install the driver for the Build Your Own Weather
>>> Station using Raspberry pi (byows_rpi.py)
>>>
>>> I have updated weewx-config to include BYOWS. I also have the
>>> interceptor driver installed.
>>>
>>> However, I cannot seem to get the driver to show up under the
>>> drivers list when I try 'wee_config --list-drivers'.  I show 
>>> byows_rpi.py
>>> under /usr/share/weewx/user/
>>>
>>> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi
>>> --no-promt' to no avail.
>>>
>>> I feel like I've missed a step somewhere about how to actually get
>>> the system to recognize the driver.
>>>
>>> When I try to run the byows_rpi.py via command line from within the
>>> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the 
>>> following
>>> error:
>>>
>>> class ByowsRpi(weewx.drivers.AbstractDevice)
>>> NameError: name 'weewx' is not defined
>>>
>>> Any guidance would be greatly appreciated!
>>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/074ed02d-872f-4384-82bf-748449e13ef5n%40googlegroups.com
>> 
>> .
>>
> --
 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

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Doug Jenkins]

No worries, I already forked it on my GitHub account and started working on
it. Will send the link once it done and tested

On Sun, Jul 24, 2022, 9:05 AM Jan Bennett  wrote:

> I am not familiar with how to do all of that just yet but I will
> definitely start looking into it!
>
>
>
> On Sat, Jul 23, 2022 at 3:55 PM Doug Jenkins  wrote:
>
>> To add to this thread Jan, could you fork this repo and send a link? I am
>> starting some work on a few enhancements to the wee_extensions and I can
>> create the proper packaging that weewx expects so that future users of the
>> driver can install it properly.
>>
>> I would fork the repo, but I do not have a BME280 sensor to properly test
>> the driver.
>>
>> If it all works, you can send a pull request to the original author and
>> have it merged.
>>
>> DDJ
>>
>> On Sat, Jul 23, 2022 at 5:51 PM Tom Keffer  wrote:
>>
>>> Something is off. Could you send me the copy of byows_rpi.py you are
>>> using?
>>>
>>>
>>> On Sat, Jul 23, 2022 at 2:33 PM Jan Bennett 
>>> wrote:
>>>
>>>> Thank you for your time in responding.
>>>>
>>>> It is correct that byows_rpi extension
>>>> <https://github.com/jardiamj/BYOWS_RPi> is mostly just a python file
>>>> (byows_rpi.py) saved to /usr/share/weewx/user/
>>>>
>>>> I have followed the directions at the git repository and have verified
>>>> with Change Driver <https://github.com/weewx/weewx/wiki/Change-driver>
>>>> that I've done the appropriate things to weewx.conf as well.
>>>>
>>>> When I run either of the commands you listed I receive the same error
>>>> as before:
>>>>
>>>> class ByowsRpi(weewx.drivers.AbstractDevice)
>>>> NameError: name 'weewx' is not defined
>>>>
>>>>
>>>>
>>>> On Saturday, July 23, 2022 at 9:02:42 AM UTC-6 tke...@gmail.com wrote:
>>>>
>>>>> 1, It looks like the byows_pi extension does not use the extension
>>>>> installer, so weewx has no way of knowing of its existence. This is why it
>>>>> doesn't show up in the list of available drivers.
>>>>>
>>>>> 2. As for running byows_pi directly, you have a slight problem with
>>>>> your paths. Try either this
>>>>>
>>>>> cd /usr/share/weewx
>>>>> python user/byows_rpi.py
>>>>>
>>>>>
>>>>> or this
>>>>>
>>>>> cd /usr/share/weewx
>>>>> python -m user.byows_rpi
>>>>>
>>>>>
>>>>> -tk
>>>>>
>>>>> On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett 
>>>>> wrote:
>>>>>
>>>>>> I should also note that when I 'sudo wee_config --reconfigure
>>>>>> --driver=user.byows_rpi --no-prompt' I see the following:
>>>>>>
>>>>>> Using configuration file /home/weewx/weewx.conf
>>>>>> Driver user.byows_rpi  failed to load: name 'weewx' is not defined
>>>>>>
>>>>>> On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:
>>>>>>
>>>>>>> Hey all -
>>>>>>>
>>>>>>> I am trying to install the driver for the Build Your Own Weather
>>>>>>> Station using Raspberry pi (byows_rpi.py)
>>>>>>>
>>>>>>> I have updated weewx-config to include BYOWS. I also have the
>>>>>>> interceptor driver installed.
>>>>>>>
>>>>>>> However, I cannot seem to get the driver to show up under the
>>>>>>> drivers list when I try 'wee_config --list-drivers'.  I show 
>>>>>>> byows_rpi.py
>>>>>>> under /usr/share/weewx/user/
>>>>>>>
>>>>>>> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi
>>>>>>> --no-promt' to no avail.
>>>>>>>
>>>>>>> I feel like I've missed a step somewhere about how to actually get
>>>>>>> the system to recognize the driver.
>>>>>>>
>>>>>>> When I try to run the byows_rpi.py via command line from within the
>>>>>>> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the 
>>>>

Re: [weewx-user] Re: Install user.byows_rpi driver?

[Doug Jenkins]

To add to this thread Jan, could you fork this repo and send a link? I am
starting some work on a few enhancements to the wee_extensions and I can
create the proper packaging that weewx expects so that future users of the
driver can install it properly.

I would fork the repo, but I do not have a BME280 sensor to properly test
the driver.

If it all works, you can send a pull request to the original author and
have it merged.

DDJ

On Sat, Jul 23, 2022 at 5:51 PM Tom Keffer  wrote:

> Something is off. Could you send me the copy of byows_rpi.py you are
> using?
>
>
> On Sat, Jul 23, 2022 at 2:33 PM Jan Bennett  wrote:
>
>> Thank you for your time in responding.
>>
>> It is correct that byows_rpi extension
>>  is mostly just a python file
>> (byows_rpi.py) saved to /usr/share/weewx/user/
>>
>> I have followed the directions at the git repository and have verified
>> with Change Driver 
>> that I've done the appropriate things to weewx.conf as well.
>>
>> When I run either of the commands you listed I receive the same error as
>> before:
>>
>> class ByowsRpi(weewx.drivers.AbstractDevice)
>> NameError: name 'weewx' is not defined
>>
>>
>>
>> On Saturday, July 23, 2022 at 9:02:42 AM UTC-6 tke...@gmail.com wrote:
>>
>>> 1, It looks like the byows_pi extension does not use the extension
>>> installer, so weewx has no way of knowing of its existence. This is why it
>>> doesn't show up in the list of available drivers.
>>>
>>> 2. As for running byows_pi directly, you have a slight problem with your
>>> paths. Try either this
>>>
>>> cd /usr/share/weewx
>>> python user/byows_rpi.py
>>>
>>>
>>> or this
>>>
>>> cd /usr/share/weewx
>>> python -m user.byows_rpi
>>>
>>>
>>> -tk
>>>
>>> On Sat, Jul 23, 2022 at 6:12 AM Jan Bennett  wrote:
>>>
 I should also note that when I 'sudo wee_config --reconfigure
 --driver=user.byows_rpi --no-prompt' I see the following:

 Using configuration file /home/weewx/weewx.conf
 Driver user.byows_rpi  failed to load: name 'weewx' is not defined

 On Saturday, July 23, 2022 at 7:07:55 AM UTC-6 Jan Bennett wrote:

> Hey all -
>
> I am trying to install the driver for the Build Your Own Weather
> Station using Raspberry pi (byows_rpi.py)
>
> I have updated weewx-config to include BYOWS. I also have the
> interceptor driver installed.
>
> However, I cannot seem to get the driver to show up under the drivers
> list when I try 'wee_config --list-drivers'.  I show byows_rpi.py under
> /usr/share/weewx/user/
>
> I have tried 'sudo wee_config --reconfigure --driver=user.byows_rpi
> --no-promt' to no avail.
>
> I feel like I've missed a step somewhere about how to actually get the
> system to recognize the driver.
>
> When I try to run the byows_rpi.py via command line from within the
> /usr/share/weewx/user/ folder: 'python3 byows_rpi.py' I see the following
> error:
>
> class ByowsRpi(weewx.drivers.AbstractDevice)
> NameError: name 'weewx' is not defined
>
> Any guidance would be greatly appreciated!
>
 --
 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.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/074ed02d-872f-4384-82bf-748449e13ef5n%40googlegroups.com
 
 .

>>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/c207e67c-2fb6-4a4c-812d-867387566476n%40googlegroups.com
>> 
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zED6%3DO2-mjrfCdB9N%3DkwNoHdoh429f9aeDtw_4KFSVSFMw%40mail.gmail.com
> 
> .
>

-- 
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 i

Re: [weewx-user] weewx sql database repair tools

[Doug Jenkins]

Andy:

I use dbeaver (dbeaver.io) to manage all my databases. It is a client tool,
but it connects to MariaDB, MySQL, and SQLite databases. You can manage the
database here.

For your power problem, I would suggest NUT (Network UPS Tool). This can
run as a service on your linux server (Including RPi) and you can configure
it to talk directly to your UPS (they have many drivers). Here is a good
video walkthrough in setting up the tool and creating a quick interface for
it.

[image: image.png]



On Mon, Jun 27, 2022 at 5:32 PM VE4PER Andy <
andrew.webb.501.ve4...@gmail.com> wrote:

> I had a major commercial power failure about 10 days ago. In the process
> it ran the UPS down almost completely such that when the last few power
> surge/bumps/fails occured something in the date time pointer system , I
> believe in the SQL databse became disconnected and immediate restart of
> the program on power restoral Had the local /var/www/html page was a
> wrong date and the FTP'd  page sent to my web site also had a corrupt
> date/Time string and neither agreed nor were either  at all real cuurent
> time accurate.
>
> I shut down the PC with the intent of looking for a mySQL dB
> troubleshooting/repair software application and attempting to correct
> the corrupted data when I had time.  About a week later I found time to
> take a look at the problem and when I restated the PC , with the intent
> of halting weewx to troubleshooting the dB. It all came back working
> normally but with no back archived data available but it appears the
> delay from it being down so long allowed it to restart and regenerate
> the consistent web pages and messages.
>
> So although it is back working now, I would like to know if their is a
> recommended dB software /data repair/maintenance package available that
> is open source freeware either standalone program or possibly something
> like a plug option/package to use with a browser similar to phpmyadmin.
>
> My 2nd takeaway is when urgent commercial power fails get to the weewx
> PC and shut it down immediately in an orderly fashion before the 8-10
> min UPS backup support runs out.
>
> Any pointers are welcome, considering so many outside agancies use the
> data (eg AWEKAS, CWOP/NOAA/aprs/ WeatherUnderground in addition to my on
> local and www page.
>
> Thanks 73
>
> Andy
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/31c1e793-4db7-672c-ffc0-01361e7aec82%40gmail.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yma27VUTjTdoW-KedaMBZrrUYWhfBKj6tk4-krtyLtSA%40mail.gmail.com.

[weewx-user] Re: Help with forecast

[Doug Jenkins]

Tim:

The forecast module uses a completely different schema and database. What 
you need to do is configure the module to a separate database and in your 
skin, bring in the data to be presented.

I personally use John Kline's weewx forecast driver ( GitHub - 
chaunceygardiner/weewx-forecast: forecasting extension for weewx 
) as it is being 
maintained and it works with the latest version of WeeWX (v4.8). You will 
need to look at the sample pages that accompany the driver and integrate 
the cheetah template code into your skin. 

Best practice is to copy your existing skin folder (eg seasons) to a 
separate folder (seasons-forecast) and make the modifications there. I 
usually use the wee_reports utility to generate the html when I make 
changes to the skin.

Please let us know if you have any questions.

Doug
www.largoweather.com


On Friday, June 10, 2022 at 10:22:59 AM UTC-4 RobbH wrote:

> This is certainly not what you are looking for, but it is what I use to 
> get NWS forecasts.
>
> Here is a url for a forecast for a randomly selected location:
>
>
> https://forecast.weather.gov/MapClick.php?lat=41.177010&lon=-73.141963&unit=0&lg=english&FcstType=text&TextType=2
>
> Note where latitude and longitude are inserted. "TextType=2" at the end 
> tells the server to include forecast graphics.
>
> Several times a day, a cron job uses PhantomJS  to 
> retrieve that page and create an jpeg of the forecast graphics, which is 
> then displayed on my weewx home page.
>
> It usually works well enough for my purposes, but there are times when the 
> forecast page is down, so I end up with a blank rectangle on the weewx page.
>
>
>
> On Wednesday, June 8, 2022 at 12:16:33 PM UTC-4 Timothy Reaves wrote:
>
>> Hello all.  I'm using the latest version running on a Pi 4, with a Davis 
>> Vantage Pro.  I've had my site configured to use Aeris for forecasting, and 
>> have never really liked it.  It just isn't as accurate as the NWS.  But I 
>> stuck with it.  Then last week, the Aeris forecast for my sight started 
>> diverging significantly not only from the NWS, but also from the actual 
>> Aeris site (which following the forecast link).  I don't know what's going 
>> on, so I thought I'd jut stop using it.
>>
>> So I installed the Forecast user module.  When I start weewx now, it 
>> fails to load with the error below.  In looking at the code, the database 
>> schema isn't matching the extensions in-memory schema.  Don't know why.
>>
>> Has anyone an example of using NWS forecasts instead of Aeris?  Or can 
>> provide any other ideas to troubleshoot?
>>
>> Thanks.
>>
>> Jun  8 10:12:34 pi4home weewx[12748] CRITICAL __main__:  
>>  Exception: NWS: schema mismatch: ['dateTime', 'usUnits', 'interval', 
>> 'altimeter', 'appTemp', 'appTemp1', 'barometer', 'batteryStatus1', 
>> 'batteryStatus2', 'batteryStatus3', 'batteryStatus4', 'batteryStatus5', 
>> 'batteryStatus6', 'batteryStatus7', 'batteryStatus8', 'cloudbase', 'co', 
>> 'co2', 'consBatteryVoltage', 'dewpoint', 'dewpoint1', 'ET', 'extraHumid1', 
>> 'extraHumid2', 'extraHumid3', 'extraHumid4', 'extraHumid5', 'extraHumid6', 
>> 'extraHumid7', 'extraHumid8', 'extraTemp1', 'extraTemp2', 'extraTemp3', 
>> 'extraTemp4', 'extraTemp5', 'extraTemp6', 'extraTemp7', 'extraTemp8', 
>> 'forecast', 'hail', 'hailBatteryStatus', 'hailRate', 'heatindex', 
>> 'heatindex1', 'heatingTemp', 'heatingVoltage', 'humidex', 'humidex1', 
>> 'inDewpoint', 'inHumidity', 'inTemp', 'inTempBatteryStatus', 'leafTemp1', 
>> 'leafTemp2', 'leafWet1', 'leafWet2', 'lightning_distance', 
>> 'lightning_disturber_count', 'lightning_energy', 'lightning_noise_count', 
>> 'lightning_strike_count', 'luminosity', 'maxSolarRad', 'nh3', 'no2', 
>> 'noise', 'o3', 'outHumidity', 'outTemp', 'outTempBatteryStatus', 'pb', 
>> 'pm10_0', 'pm1_0', 'pm2_5', 'pressure', 'radiation', 'rain', 
>> 'rainBatteryStatus', 'rainRate', 'referenceVoltage', 'rxCheckPercent', 
>> 'signal1', 'signal2', 'signal3', 'signal4', 'signal5', 'signal6', 
>> 'signal7', 'signal8', 'snow', 'snowBatteryStatus', 'snowDepth', 
>> 'snowMoisture', 'snowRate', 'so2', 'soilMoist1', 'soilMoist2', 
>> 'soilMoist3', 'soilMoist4', 'soilTemp1', 'soilTemp2', 'soilTemp3', 
>> 'soilTemp4', 'supplyVoltage', 'txBatteryStatus', 'UV', 'uvBatteryStatus', 
>> 'windBatteryStatus', 'windchill', 'windDir', 'windGust', 'windGustDir', 
>> 'windrun', 'windSpeed'] != ['t', 'd']
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fd772c47-c35c-49fb-9d34-7875c4a32b75n%40googlegroups.com.

Re: [weewx-user] Problem with weewx-airlink

[Doug Jenkins]

My guess since you do not see the device in weatherlink.com is that it is
not reporting correctly on the network.


1.  First see if you can open your web browser to the api of the airlink
device.

for example: http://xxx.xxx.xxx.xxx/v1/current_conditions
You should see JSON data returned.

2. Also check the APi Documentation from Davis (Introduction | AirLink
Local API (weatherlink.github.io)
 about how the
device works on a network. From their documentation, AirLink devices
advertise their presence on the local network using DNS Service Discovery
 over multicast DNS (mDNS)
. These technologies are also known as
Zeroconf or Bonjour or Avahi.

I have a weewx-airlink device and I followed this guide using the driver
with success. Please let me know if you have any questions.



if not,

On Wed, May 25, 2022 at 11:24 AM anc...@gmail.com  wrote:

> Hi guys,
> I just installed for the first time a Davis Airlink and I want to
> integrate it in WeeWX with which my Davis VP2 already works. I followed the
> instructions on the weewx-airlink page
> , but for some reason
> it is not working . Here is some log:
>
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Could not get concentrations from any source.
> May 25 16:11:01 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:03 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:05 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink:
> last_report_time must be time since boot: 85441 seconds.  Record: {'data':
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85441, 'conditions':
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.0, 'hum': 26.5,
> 'dew_point': 52.7, 'wet_bulb': 60.0, 'heat_index': 89.8, 'pm_1_last': 4,
> 'pm_2p5_last': 5, 'pm_10_last': 5, 'pm_1': None, 'pm_2p5': None,
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None,
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None,
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None,
> 'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time':
> 85441, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None,
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error':
> None}
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Could not get concentrations from any source.
> May 25 16:11:07 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:09 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:11 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink:
> last_report_time must be time since boot: 85446 seconds.  Record: {'data':
> {'did': '001D0A100829', 'name': 'IIS Ceccano', 'ts': 85446, 'conditions':
> [{'lsid': 522424, 'data_structure_type': 6, 'temp': 92.1, 'hum': 26.7,
> 'dew_point': 53.0, 'wet_bulb': 60.3, 'heat_index': 89.9, 'pm_1_last': 4,
> 'pm_2p5_last': 4, 'pm_10_last': 4, 'pm_1': None, 'pm_2p5': None,
> 'pm_2p5_last_1_hour': None, 'pm_2p5_last_3_hours': None,
> 'pm_2p5_last_24_hours': None, 'pm_2p5_nowcast': None, 'pm_10': None,
> 'pm_10_last_1_hour': None, 'pm_10_last_3_hours': None,
> 'pm_10_last_24_hours': None, 'pm_10_nowcast': None, 'last_report_time':
> 85446, 'pct_pm_data_last_1_hour': None, 'pct_pm_data_last_3_hours': None,
> 'pct_pm_data_nowcast': None, 'pct_pm_data_last_24_hours': None}]}, 'error':
> None}
> May 25 16:11:12 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Could not get concentrations from any source.
> May 25 16:11:13 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:15 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager:
> Added record 2022-05-25 16:11:00 CEST (1653487860) to database 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] INFO weewx.manager:
> Added record 2022-05-25 16:11:00 CEST (1653487860) to daily summary in
> 'weewx.sdb'
> May 25 16:11:16 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:17 StazioneMeteoiisCeccano weewx[32034] ERROR user.airlink:
> Found no concentrations to insert.
> May 25 16:11:19 StazioneMeteoiisCeccano weewx[32034] INFO user.airlink:
> collect_data: Attempt to fetch from: 192.168.0.196 failed:
> HTTPConnectionPool(host='192.168.0

Re: [weewx-user] Logging

[Doug Jenkins]

Mark:

It is worth a shot and most likely it would work. If it does, I would
recommend forking the repo and make the same changes for log.error,
log.message, and log.debug using the functions from weeutil.logger.

Then I would commit the changes to your fork and send the maintainer a pull
request to make the changes in the regular driver.

DDJ



On Mon, May 23, 2022 at 9:59 AM Mark Fraser  wrote:

> On 23/05/2022 11:54, Doug Jenkins wrote:
> > Mark:
> >
> > I would add the log_success = False under the BME280 driver in your
> > weewx.conf. If that doesn't work, then check with the driver's author to
> > see if the code can be revised to accommodate WeeWx logging class.
> >
> > On Mon, May 23, 2022 at 4:02 AM Mark Fraser  > <mailto:mfra...@gmail.com>> wrote:
> >
> > I'm running version 4.8 of weewx and although I've got
> > log_success = False
> > In all places in weewx.conf, I still see lines like:
> > May 23 09:00:56 weathercam /weewxd: bme280: BME280 data
> > compensated_reading(id=a4ff8186-9fd7-4cb1-ac00-22716b358662,
> > timestamp=2022-05-23 09:00:56.543049, temp=34.843 °C, pressure=996.53
> > hPa, humidity=17.31 % rH)
> > May 23 09:00:56 weathercam /weewxd: bme280: {'windGust': 3.672,
> > 'outBatteryStatus': 0, 'rain_total': 42.06, 'windSpeed': 2.448,
> > 'windDir': 270.0, 'outHumidity': 70.0, 'outTemp': 16.0, 'dateTime':
> > 1653292852, 'usUnits': 16, 'rain': 0.0, 'pressure':
> 996.5324701184883}
> > In /var/log/syslog.
> >
> > Is there any way of stopping these messages too?
>
> Looks like it has already been asked for:
> https://gitlab.com/wjcarpenter/bme280wx/-/issues/1
>
> and it seems to be using it's own logging functions:
>
> def logmsg(level, msg):
>  syslog.syslog(level, 'bme280: %s' % msg)
>
> def logdbg(msg):
>  logmsg(syslog.LOG_DEBUG, msg)
>
> def loginf(msg):
>  logmsg(syslog.LOG_INFO, msg)
>
> def logerr(msg):
>  logmsg(syslog.LOG_ERR, msg)
>
>
> If I replace these with:
> import weeutil.logger
> and change instances of loginf() with log.info() is it likely to work?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f3d06f4b-511a-671f-d708-c87c0398aa1d%40gmail.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xu2uRO_hX_-%2BtEJAX64mB5GH6jhexD0SAbH456xL3RDA%40mail.gmail.com.

Re: [weewx-user] HTTP and HTTPS have different layouts

[Doug Jenkins]

Susan:

Check your nginx config to ensure your SSL configuration includes the
subdirectories and their files. Based on your message, it appears the css
file is not being read by the web client.

DDJ

On Mon, May 23, 2022 at 6:24 AM Susan Mackay  wrote:

> Weewx v4.1.1
> Nginx V1.14.2
> Any browser but testing with Chrome
>
> (Not sure if this is a Weewx or nginx question - starting here)
>
> When I first set up my station I used HTTP only and using the (pseudo URL)
> HTTP://myserver.org/weather returned the nicely formatted display.
>
> I then tried to create an HTTPS arrangement and have all HTTP traffic
> redirected to HTTPS. That all seems to work OK BUT
>
> When I access the HTTPS URL, the underlying page is sent but the
> formatting seems to be lost - everything is in a single 'line' down the
> left-hand edge of the window. Everything seems to be there - even the
> 'Current', 'Week' 'Month' and 'Year' buttons that show as links, and the
> 'Monthly Summary' pull-down is there but as a list of entries.
>
> Any idea what I'm doing wrongly?
>
> Susan (obviously a beginner with this web stuff)
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f0dceff0-fe32-4c36-b76f-9e600c89acffn%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0we_5cbVbATruDnVQHr8br9bVMJ1o5GZx_NfJZ7vG%3DcHA%40mail.gmail.com.

Re: [weewx-user] Logging

[Doug Jenkins]

Mark:

I would add the log_success = False under the BME280 driver in your
weewx.conf. If that doesn't work, then check with the driver's author to
see if the code can be revised to accommodate WeeWx logging class.

On Mon, May 23, 2022 at 4:02 AM Mark Fraser  wrote:

> I'm running version 4.8 of weewx and although I've got
> log_success = False
> In all places in weewx.conf, I still see lines like:
> May 23 09:00:56 weathercam /weewxd: bme280: BME280 data
> compensated_reading(id=a4ff8186-9fd7-4cb1-ac00-22716b358662,
> timestamp=2022-05-23 09:00:56.543049, temp=34.843 °C, pressure=996.53
> hPa, humidity=17.31 % rH)
> May 23 09:00:56 weathercam /weewxd: bme280: {'windGust': 3.672,
> 'outBatteryStatus': 0, 'rain_total': 42.06, 'windSpeed': 2.448,
> 'windDir': 270.0, 'outHumidity': 70.0, 'outTemp': 16.0, 'dateTime':
> 1653292852, 'usUnits': 16, 'rain': 0.0, 'pressure': 996.5324701184883}
> In /var/log/syslog.
>
> Is there any way of stopping these messages too?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/724506eb-825f-04c3-7c18-3cb39c801b32%40gmail.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zYBx5Y%3DVtDuCNMMh2U3uiMzahh%3D7o%3DONw4mRrGzvEPqw%40mail.gmail.com.

Re: [weewx-user] Re: Excessive Syslog data

[Doug Jenkins]

In the weewx engine section, remove stdprint. That is what is printing the
loop data in your log. Make sure you recycle your weewx service to take
effect

On Fri, Apr 29, 2022, 2:39 PM Andy Peterman  wrote:

> Oops, forgot that info.
>
> VantagePro weather station (Vantage driver)
> MacOS 10.6.8 (yea, it's an older Mac Mini, but it works really well for
> this) along with Python 3.6.15
> Not sure about installation - I assume it was setup.py
>
> I looked at that link, but I'm not sure what it was talking about.  I'm
> not really familiar with what StdPrint is supposed to be doing.  I do see
> logging information at /var/log/weewx.log and there also seems to be a file
> weewx.stderr in the weewx directory, but I don't understand why I'm getting
> all this LOOP info in the system log.  I have all the "successful" logging
> turned off and all the "unsuccessful" logging on.
>
> On Friday, April 29, 2022 at 11:19:04 AM UTC-7 vince wrote:
>
>> Usual FAQ how to report a problem answer applies
>>
>> - what driver are you running ?
>> - what os ?
>> - what kind of installation (docker ?  setup.py ?  dpkg ?  rpm ?)
>>
>> Does https://groups.google.com/g/weewx-user/c/_4OJtLsI7_w/m/yuC9Zry2BQAJ
>> help any ?
>>
>> On Friday, April 29, 2022 at 9:50:14 AM UTC-7 Andy Peterman wrote:
>>
>>> I've recently updated to 4.7.0 and just noticed the system log (syslog)
>>> has been getting dumps of loop data every few seconds.  Here's what I've
>>> been seeing:
>>>
>>> Apr 29 09:46:35 Multipass com.weewx.weewxd[2617]: LOOP:   2022-04-29
>>> 09:46:14 PDT (1651250774) 'altimeter': '30.112925788902526', 'appTemp':
>>> '51.403945964940384', 'barometer': '30.111', 'cloudbase':
>>> '1509.5918641388919', 'consBatteryVoltage': '4.28', 'dateTime':
>>> '1651250774', 'dayET': '0.0', 'dayRain': '0.03', 'dewpoint':
>>> '47.3437957977', 'ET': 'None', 'extraAlarm1': '0', 'extraAlarm2': '0',
>>> 'extraAlarm3': '0', 'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6':
>>> '0', 'extraAlarm7': '0', 'extraAlarm8': '0', 'forecastIcon': '6',
>>> 'forecastRule': '44', 'heatindex': '52.4830004', 'humidex':
>>> '54.82771626032395', 'inDewpoint': '43.399219063882676', 'inHumidity':
>>> '34.0', 'insideAlarm': '0', 'inTemp': '73.5', 'maxSolarRad':
>>> '565.2481829491581', 'monthET': '0.0', 'monthRain': '5.9', 'outHumidity':
>>> '79.0', 'outsideAlarm1': '0', 'outsideAlarm2': '0', 'outTemp': '53.7',
>>> 'pressure': '30.039635406360034', 'rain': 'None', 'rainAlarm': '0',
>>> 'rainRate': '0.0', 'soilLeafAlarm1': '0', 'soilLeafAlarm2': '0',
>>> 'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0', 'stormRain': '0.08',
>>> 'stormStart': '1651129200', 'sunrise': '1651237860', 'sunset':
>>> '1651288620', 'txBatteryStatus': '0', 'usUnits': '1', 'windchill': '53.7',
>>> 'windDir': '246.0', 'windGust': '3.0', 'windGustDir': '246.0', 'windrun':
>>> 'None', 'windSpeed': '3.0', 'windSpeed10': '3.0', 'yearET': '0.02',
>>> 'yearRain': '57.57'
>>>
>>> This results in a syslog file of over 20MB per day!
>>>
>>> I've managed to locate where this is coming from, engine.py in Class
>>> StdPrint at new_loop_packet.
>>>
>>> Any idea why this is happening.  I'm not versed in Python enough to
>>> track this down.
>>>
>>> Thanks!
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1249f468-07fc-4c85-8133-2c0008cdc507n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0z4%3Dxv8_oSWHas4P%3D%3Da9v60VdyKiruo0uqqMr0K7fLOew%40mail.gmail.com.

Re: [weewx-user] Re: Acurite 5-in-1 dead?

[Doug Jenkins]

I have a similar problems with my 5-in-1 recently eating batteries every
month. I hope I can figure it out and not a internal issue with the station
itself.

For SDR, I was able to get data off rtl_433 on channel 40. You will get
temp, humidity, wind speed/direction, and rain. You will not get the
barometer as that sensor is located inside the console unit.

I am experimenting with a BME280 sensor chip with a RPi3 where I was going
to write a data service to poll the sensor and update the LOOP data with
its values (Temp/humidity/pressure). Hopefully that will be merged with the
SDR driver from Matthew Wall to replicate the same data sans the console.

for station replacement, you may want to consider the Davis Vantage vue or
any other all-in-one stations from Davis. Their build quality is better and
have better integration options than Acurite. Just my $0.02.

Let us know if you have any questions.

On Wed, Apr 27, 2022, 12:44 PM ewhain...@gmail.com 
wrote:

> Gotcha *thanks*!
>
> So a bit of an update - I took the sensor unit down and brought it in,
> popped the batteries out, powered down the sensor. I switched both units
> from channel A to C, powered up the display, powered up the sensor and it
> is currently working.
>
> *THEN* i set it on the outside table to see if it was going to remain
> stable - well the wind picked up and blew it off the table and broke the
> directional vane. Let's see how well the Gorilla glue works
>
> Might still need that recommendation for a new system yet...
>
> On Wednesday, April 27, 2022 at 11:43:15 AM UTC-4 an oldman wrote:
>
>> the freq for my 5n1 from a SDR running rtl_433 for about 15 mins
>> "freq" : 433.945
>>  "freq" : 433.946
>>  "freq" : 433.947
>>  "freq" : 433.948
>>  "freq" : 433.949
>>  "freq" : 433.950
>>  "freq" : 433.954
>>  "freq" : 433.955
>>  "freq" : 433.965
>> this one likes to jump channels from A to C for some reason
>>
>> On Wednesday, April 27, 2022 at 9:59:36 AM UTC-5 ewhain...@gmail.com
>> wrote:
>>
>>> So it looks like one of my 5-in-1 units are dead. I have changed the
>>> batteries in the sensor unit with known fresh batteries but the display is
>>> showing nothing found.
>>>
>>> I have seen that some people have used an SDR dongle to get the data,
>>> but can I use a Bearcat scanner to see if it is sending? And what frequency
>>> are they transmitting?
>>>
>>> And if the sensor unit IS dead, what is a good replacement that works
>>> easily with WeeWx, relatively same features and cost?
>>>
>>> Thanks
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/6346c66d-c347-4dfb-938d-f1b68c2c7820n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yT1GrsbQ%2BeYpSJkuRbrvq8XStw1k5QdzHVcCJzNtqE2g%40mail.gmail.com.

Re: [weewx-user] Re: Align Belchertown subtitle

[Doug Jenkins]

I wonder if you try to put html tags within the title/subtitle. can you
give this a go:


title = 'Historical Rain Totals By Month'
subtitle = 'Rain Totals for All
Months for All Time'


On Sat, Apr 16, 2022 at 1:07 PM Geni  wrote:

> i think it is a bug from highchart
> i use Belchertown Skin Version: 1.3b1
> here it is also incorrect
> https://belchertownweather.com/graphs/?graph=raintotals
> [image: belch03.jpg]
>
> do...@dougjenkins.com schrieb am Samstag, 16. April 2022 um 18:36:21
> UTC+2:
>
>> Geni:
>>
>> Here is the sample that displays the chart appropriately (See Below). You
>> can find this information in the Charts wiki
>>
>> Belchertown Charts Documentation · poblabs/weewx-belchertown Wiki
>> (github.com)
>> 
>>
>> If you still need assistance, we are going to need a copy of your
>> graphs.conf file in the /skins/Belchertown folder of your WeeWx
>> installation.
>>
>> [raintotals]
>> title = Rain Totals by Month
>> show_button = true
>> button_text = Rain Totals
>> type = column
>> time_length = all
>> aggregate_type = max
>> aggregate_interval = 86400 # 1 day
>>
>> [[rainmonthtotals]]
>> title = Historical Rain Totals By Month
>> subtitle = Rain Totals for All Months for All Time
>> xAxis_groupby = month
>> xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 
>> 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>> [[[rainTotal]]]
>> name = Rain Total
>>
>>
>> On Sat, Apr 16, 2022 at 12:31 PM vince  wrote:
>>
>>> You have to tell us more.  Which version of Belchertown ?   What page is
>>> that screen image from ?   I don't see any graphs that look like that.  Did
>>> you add a custom graphs.conf ?
>>>
>>> On Saturday, April 16, 2022 at 8:19:31 AM UTC-7 Geni wrote:
>>>
 Hi, where and how to center the subtitle to the title
 is
 [image: belch01.jpg]
 should
 [image: belch02.jpg]
 Geni

>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/b4c2652a-964a-484a-b821-c06b820a21ban%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/e993df1a-23c2-4d68-859d-c7350eb0b389n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zrZJKna5QDRqSST3qcFui8CMe1Z3_LrxtG8G85dMLoYw%40mail.gmail.com.

Re: [weewx-user] Re: Align Belchertown subtitle

[Doug Jenkins]

Geni:

Here is the sample that displays the chart appropriately (See Below). You
can find this information in the Charts wiki

Belchertown Charts Documentation · poblabs/weewx-belchertown Wiki
(github.com)


If you still need assistance, we are going to need a copy of your
graphs.conf file in the /skins/Belchertown folder of your WeeWx
installation.

[raintotals]
title = Rain Totals by Month
show_button = true
button_text = Rain Totals
type = column
time_length = all
aggregate_type = max
aggregate_interval = 86400 # 1 day

[[rainmonthtotals]]
title = Historical Rain Totals By Month
subtitle = Rain Totals for All Months for All Time
xAxis_groupby = month
xAxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun',
'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
[[[rainTotal]]]
name = Rain Total


On Sat, Apr 16, 2022 at 12:31 PM vince  wrote:

> You have to tell us more.  Which version of Belchertown ?   What page is
> that screen image from ?   I don't see any graphs that look like that.  Did
> you add a custom graphs.conf ?
>
> On Saturday, April 16, 2022 at 8:19:31 AM UTC-7 Geni wrote:
>
>> Hi, where and how to center the subtitle to the title
>> is
>> [image: belch01.jpg]
>> should
>> [image: belch02.jpg]
>> Geni
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b4c2652a-964a-484a-b821-c06b820a21ban%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0y-2evtE-kz%3DrredZ%2B3Hy21h4zuCDi1Xr3pCE4mTbNw8g%40mail.gmail.com.

Re: [weewx-user] Reading rain rate more frequently than the archive period

[Doug Jenkins]

have you considered MQTT? You could setup the MQTT WeeWX Extension in which 
it will push both LOOP and ARCHIVE records to a MQTT broker. I have an 
Acurite 5-n-1 weather station and use MQTT to update my website as the LOOP 
data changes. I get updates around every 18 seconds or so.

In your Python program, you use Paho Python library to "subscribe" to your 
MQTT host and invoke an event when you get a LOOP Record. From there 
evaluate the rain values and take action with your car windows at that 
moment based on the data.

MQTT is a small, lightweight protocol that will update in near real time. 
It is used a lot in IOT devices.


On Saturday, April 9, 2022 at 2:31:03 AM UTC-4 Graham Eddy wrote:

> your Acurite driver creates a ‘loop packet’ each time it receives a 
> reading from the station. you can have a ’service’ immediately export 
> selected data from each loop packet, not wait until the end of the archive 
> interval (which is when database is updated). depending how you want the 
> data exported, there could be an existing service extension available 
> off-the-shelf
>
> On 9 Apr 2022, at 3:23 pm, Sylvain Gagnon  wrote:
>
> Hi, I've been using WeeWx for many years now but first time posting here.
>
> I'm writing a program in Python that queries my Acurite 5 in 1 probe 
> through WeeWX for the rain rate and if it's above 0mm, then it will close 
> the car windows if they are opened and the car is parked. It works well but 
> relies on daily.json to fetch the rain rate and that value I believe 
> updates at the archive frequency (ie, 5 minutes) but the stations sends 
> that data every 36 seconds. Is there a way to fetch this value? The only 
> other option that I can think of is to set the "archive_interval" to 60 
> instead of 300 in [StdArchive]. If I do that, will that mess up all the 
> historical data already in the database? Any other side effects?
>
> Thanks for your help at keeping the inside of my car dry :-)
>
>
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/c90fb5b9-f691-4024-a00f-ab55a340fb04n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1edcdb0a-4786-40f7-8506-a653275177a3n%40googlegroups.com.

Re: [weewx-user] Re: belchertown skin question: reporting from multiple weewx instances

[Doug Jenkins]

Thanks Vince once again :)

In my configuration work, I found that if I use the weewx-airlink and 
weewx-weatherlink-live extensions together, I get both the AQI and station 
data on the same loop. The author of the weewx-airlink extension is using a 
data service, which updates the LOOP record when the device is polled. 

So in essence, I am going to run the site on a single instance which 
simplifies my configuration :)

Thanks for the code example, I will probably use it for other sensor 
integration outside of the Davis Hardware.

DDJ

On Wednesday, March 23, 2022 at 12:37:57 PM UTC-4 vince wrote:

> Example from graphs.conf
>
> [day]
> title = "Today"
> show_button = true
> button_text = "Day"
> time_length = today
> tooltip_date_format = "LLL"
> gapsize = 30
>
> # an added chart from multiple db sources
> # note how 'some' elements specify a binding to a secondary db
> [[chartA]]
> title = Temperature Comparison
> connectNulls = true
> [[[outTemp]]]
> name = VP2 Temperature
> [[[extraTemp1]]]
> data_binding = pi_binding
> name = ds18b20_1
> [[[extraTemp2]]]
> data_binding = pi_binding
> name = ds18b20_2
>
> # an added chart with all data from a secondary db
> [[chart0]]
> title = WeeWX Memory Usage
> data_binding = mem_binding
> connectNulls = true
> [[[mem_size]]]
> [[[mem_rss]]]
> [[[mem_share]]]
>
> On Tuesday, March 22, 2022 at 8:10:19 PM UTC-7 do...@dougjenkins.com 
> wrote:
>
>> Thanks Vince, you answered my question. My plan was to run belchertown in 
>> a separate "reporting" instance with database bindings to the aqi and davis 
>> weather station databases (fed with separate weewx instances). I will have 
>> to play with the weewx.conf and skin.conf to see if I can bind certain 
>> values to certain database sources.
>>
>> For MQTT, I want to publish the live values from both stations, so I will 
>> probably setup each weewx station to publish to separate topics and bring 
>> that in on the reporting weewx instance.
>>
>> DDJ
>>
>> On Tue, Mar 22, 2022 at 10:46 PM vince  wrote:
>>
>>> My recollection is that Belchertown only supports one weewxinstance, 
>>> although you 'can' bind to multiple db within 'one' instance of weewx.  I 
>>> do just that to add info from multiple secondary db to my VP2 data in the 
>>> default db.
>>>
>>> You could kludge something together with having one weewx instance 
>>> publish data to MQTT and have the primary one subscribe to that MQTT data 
>>> if you 'really' wanted to add'em all up into one Belchertown dashboard.  I 
>>> actually do that too in order to add stuff from some DS18b20 sensors to my 
>>> Belchertown graphs.
>>>
>>> Weewx supporting MQTT pub/sub is very powerful and is rock solid if your 
>>> network and MQTT broker are stable.
>>>
>>>
>>> On Tuesday, March 22, 2022 at 5:54:17 PM UTC-7 do...@dougjenkins.com 
>>> wrote:
>>>
>>>> Good evening fellow WeeWX users!
>>>>
>>>> I was wondering if anyone was using the belchertown skin with multiple 
>>>> weewx instances. I am going to be setting up my new Davis Vantage Pro 2 
>>>> (just came in today) with a Davis AirLink and I need to bind both the AQI 
>>>> and Weather data together.
>>>>
>>>> From what I saw in the repos for WeatherLink Live, I can get the data 
>>>> via one driver, but the AirLink is not supported at the same time. Since 
>>>> WeeWX supports only 1 station per instance, I am going to setup a separate 
>>>> WeeWX instance to talk to AirLink and a separate WeeWX instance to pull in 
>>>> the Weather Station data from WeatherLink Live.
>>>>
>>>> I desire to publish both instances to MQTT and report them out on the 
>>>> Belchertown skin.
>>>>
>>>> Any help or suggestions with the skin to report both values is 
>>>> appreciated!
>>>>
>>>> Doug Jenkins
>>>> largoweather.com
>>>
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/3e093324-202c-4233-896d-798a06f13d02n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/3e093324-202c-4233-896d-798a06f13d02n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0b6800f5-490b-4fb3-a6b4-ad6eb758446en%40googlegroups.com.

Re: [weewx-user] Re: Belchertown MQTT Issues

[Doug Jenkins]

Geni:

The problem now with your site is that your main website is now https, but 
your websocket is not. Here are the errors I get in my javascript console 
on your website:

=== START LOG ===
paho-mqtt.min.js:37 

   Mixed Content: The page at 'https://wetter.affolter.familyds.net/' 
was loaded over HTTPS, but attempted to connect to the insecure WebSocket 
endpoint 'ws://wetter.affolter.familyds.net:9001/mqtt'. This request has 
been blocked; this endpoint must be available over WSS.
d._doConnect @ paho-mqtt.min.js:37
jquery.min.js:2 

   Uncaught DOMException: Failed to construct 'WebSocket': An insecure 
WebSocket connection may not be initiated from a page loaded over HTTPS.
at d._doConnect 
(https://cdnjs.cloudflare.com/ajax/libs/paho-mqtt/1.1.0/paho-mqtt.min.js:37:221)
at d.connect 
(https://cdnjs.cloudflare.com/ajax/libs/paho-mqtt/1.1.0/paho-mqtt.min.js:31:233)
at Client.connect 
(https://cdnjs.cloudflare.com/ajax/libs/paho-mqtt/1.1.0/paho-mqtt.min.js:70:506)
at connect 
(https://wetter.affolter.familyds.net/js/belchertown.js?1648519234:780:12)
at HTMLDocument. 
(https://wetter.affolter.familyds.net/:157:21)
at l 
(https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js:2:29375)
at c 
(https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js:2:29677)

=== END LOG ===

I would try to set your mqtt_websockets_host = wetter.affolter.familyds.net 
and set the mqtt_websockets_ssl = 1. see below

[[MQTT]]
server_url = mqtt://user:pass...@192.168.56.51:1883/ 

topic = wetter
unit_system = METRIC
binding = archive, loop
aggregation = aggregate
   
   
#--- MQTT Websockets (for Real Time Streaming) Options ---
mqtt_websockets_enabled = 1
mqtt_websockets_host = wetter.affolter.familyds.net 

mqtt_websockets_port = 9001
mqtt_websockets_ssl = 1
mqtt_websockets_topic = wetter/loop
mqtt_websockets_username = user
mqtt_websockets_password = password
disconnect_live_website_visitor = 180


if it does not work, switch the mqtt_websockets_port = 443 and try that. If 
that does not work, then I would recommend setting up a reverse proxy on 
your network (see nginxproxymanager.com ) to allow 443 traffic to be 
properly routed to your weewx webserver and mosquitto.

Let us know if this helps.

DDJ

On Monday, March 28, 2022 at 7:08:47 AM UTC-4 Geni wrote:

> I have now changed the "mqtt_websockets_host = 
> wetter.affolter.familyds.net" and the port 9001 is forwarded to the 
> weewx-server(raspberry).
> The webserver is on a Synology and has a LetsEncrypt certificate.
> With the call of the web page with the IP address (
> http://192.168.56.1/wetter/) of the Synology the live update works.
> If you call the web page with the domain name (
> https://wetter.affolter.familyds.net/) of the web page, the live update 
> does not work.
> Does the Mosquitto also have to have a certificate? If so which one?
> Geni
> do...@dougjenkins.com schrieb am Sonntag, 27. März 2022 um 21:41:37 UTC+2:
>
>> No, port forwarding will not solve the problem. WeeWx is creating the 
>> belchertown JavaScript file every time an archive is executed. Your users 
>> are getting this JavaScript file from the webserver and running it on their 
>> browser. If you have your local ip address configured for mqtt, then it 
>> will not resolve for the client as they have no path back to your server.
>>
>> I would first just try your domain name instead of the ip address. If it 
>> still does not work, check your firewall that port 9001 is being passed to 
>> your web server from the wan side of your Network.
>>
>> On Fri, Mar 25, 2022, 11:06 AM Geni  wrote:
>>
>>> If I only enter the local IP address of the Raspberry (weewx and 
>>> mosquitto) in the mqtt_websockets_host as suggested and call the web server 
>>> (on a Synology) with the local IP address of the Synology it works as 
>>> desired.
>>> For access from the Internet, can I get there with port forwarding to 
>>> the target? 
>>>
>>> Geni
>>>
>>> do...@dougjenkins.com schrieb am Freitag, 25. März 2022 um 13:49:35 
>>> UTC+1:
>>>
 To add what Tom is saying, when I check your site in the Javascript 
 console, I see this error:

 Uncaught DOMException: Failed to construct 'WebSocket': The URL 
 'ws://[mqtt://192.168.56.51]:9001/mqtt' is invalid.

 The reason the site is not showing the real-time weather data is that 
 the local brower of your users needs to connect to the website on port 
 9001 
 to get the MQTT topic data to present. Since you are posting your internal 
 server IP address, the internet user will not receive the information as 
 there is no way to route this correctly.

 What I would do is change mqtt_websockets_host to 

Re: [weewx-user] Belchertown skin - dark theme switchover around sunset

[Doug Jenkins]

Yes, that is the project. submit an issue and I can see what I can do with
a update. It will still be up to the maintainer (Pat O'Brien) to merge it
for distribution.

On Sun, Mar 27, 2022 at 4:12 PM Eric Koester  wrote:

> Thanks for looking at this, Doug.
>
> "Probably what should happen here is the script is fed the server time as
> a constant when the cheetah generator "creates" this script upon execution
> of StdReport. Then the code will evaluate that datevalue to determine if
> the theme should change."
> Until my Eastern time zone friend reported otherwise, I expected that this
> was the default behavior.
>
> I suspect you are talking about this Github project page?
> https://github.com/poblabs/weewx-belchertown
>
> Eric
>
> On Sun, Mar 27, 2022 at 2:29 PM Doug Jenkins  wrote:
>
>> I looked at the code and yes, this is running on the client side. This
>> means the light/dark mode is determined y checking the person's web browser
>> and seeing if it is out of the range of sunrise hours.
>>
>> If it is, then the JavaScript changes the theme to dark, otherwise it
>> remains on light.
>>
>> So what this means if it is midnight where your weather station is on the
>> east coast of the US, a user in Tokyo (+13 hours) is going to see the light
>> theme of he goes to your weather website.
>>
>> Probably what should happen here is the script is fed the server time as
>> a constant when the cheetah generator "creates" this script upon execution
>> of StdReport. Then the code will evaluate that datevalue to determine if
>> the theme should change.
>>
>> If there is any interest on this item, I recommend putting in an issue on
>> the GitHub project and send it to me. I can do an update and submit a PR
>> with the correction.
>>
>> Doug Jenkins
>>
>> On Sun, Mar 27, 2022, 12:54 PM vince  wrote:
>>
>>> Easiest thing to do is figure it out experimentally.Connect into a
>>> Belchertown site on the other side of the ocean and see.
>>>
>>> On Sunday, March 27, 2022 at 9:33:58 AM UTC-7 Eric K wrote:
>>>
>>>> I gave a link to the file so you could look at it:
>>>>
>>>> https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl
>>>>
>>>> There is a definition of a "var d" at line 507.
>>>> var d = new Date();
>>>>
>>>> I still can't tell where it's getting its time from.
>>>>
>>>> On Sat, Mar 26, 2022 at 6:37 PM Doug Jenkins 
>>>> wrote:
>>>>
>>>>> I think it is from the local client. The JavaScript is executed in the
>>>>> browser.
>>>>>
>>>>> We need to see where "D" is initialized to make sure it is not using a
>>>>> web api to obtain the time
>>>>>
>>>>> On Sat, Mar 26, 2022, 4:39 PM Eric K  wrote:
>>>>>
>>>>>> I have the Belchertown skin theme set to "auto" so it switches over
>>>>>> to the dark theme around sunset.
>>>>>> I have noted that the Belchertown skin switches over to the dark
>>>>>> theme at large fractions of an hour before sunset actually occurs.
>>>>>> Then, I got a report from a friend in the Eastern time zone, that the
>>>>>> webpage theme switched to dark around 6:00pm Eastern time - around 2 
>>>>>> hours
>>>>>> early compared to the local sundown time (7:39pm Central) at my weewx
>>>>>> weather station.
>>>>>> He said he had not clicked the manual theme switch at the upper right
>>>>>> corner of the Belchertown page.
>>>>>>
>>>>>> So, I started looking through the code to see how the theme change
>>>>>> gets triggered.
>>>>>>
>>>>>> see:
>>>>>> https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl
>>>>>>
>>>>>> Around line 507 the current hour and minute get assigned to variables
>>>>>> with the expressions
>>>>>> var nowHour = d.getHours();
>>>>>> var nowMinutes = d.getMinutes();
>>>>>> Where is the time being read from?
>>>>>> 1. from the clock of the computer that weewx is running inside?
>>>>>> 2. from the clock of webpage visitor's computer?
>>>>>&

Re: [weewx-user] Re: Belchertown MQTT Issues

[Doug Jenkins]

No, port forwarding will not solve the problem. WeeWx is creating the
belchertown JavaScript file every time an archive is executed. Your users
are getting this JavaScript file from the webserver and running it on their
browser. If you have your local ip address configured for mqtt, then it
will not resolve for the client as they have no path back to your server.

I would first just try your domain name instead of the ip address. If it
still does not work, check your firewall that port 9001 is being passed to
your web server from the wan side of your Network.

On Fri, Mar 25, 2022, 11:06 AM Geni  wrote:

> If I only enter the local IP address of the Raspberry (weewx and
> mosquitto) in the mqtt_websockets_host as suggested and call the web server
> (on a Synology) with the local IP address of the Synology it works as
> desired.
> For access from the Internet, can I get there with port forwarding to the
> target?
>
> Geni
>
> do...@dougjenkins.com schrieb am Freitag, 25. März 2022 um 13:49:35 UTC+1:
>
>> To add what Tom is saying, when I check your site in the Javascript
>> console, I see this error:
>>
>> Uncaught DOMException: Failed to construct 'WebSocket': The URL
>> 'ws://[mqtt://192.168.56.51]:9001/mqtt' is invalid.
>>
>> The reason the site is not showing the real-time weather data is that the
>> local brower of your users needs to connect to the website on port 9001 to
>> get the MQTT topic data to present. Since you are posting your internal
>> server IP address, the internet user will not receive the information as
>> there is no way to route this correctly.
>>
>> What I would do is change mqtt_websockets_host to
>> wetter.affolter.familyds.net and see if that works.
>>
>> If it does not work, then the next best option is to set up Cloudflare to
>> host your domain name and route the websockets and internet traffic to your
>> local IP address at home. Cloudflare can help with the SSL Certificate
>> portion automatically. From there, you would use a reverse proxy (NGINX
>> Proxy Manager) to route the traffic correctly to your MQTT and WeeWX Web
>> Server instances. Please let me know if you have any other questions or if
>> you need instructions on how to do this.
>>
>> Doug
>>
>>
>> On Fri, Mar 25, 2022 at 7:51 AM t...@tom.org  wrote:
>>
>>> My websockets_host is just my hostname without the protocol. So instead
>>> of "mqtt://foo.bar.com" or "ws://foo.bar.com" it is just "foo.bar.com"
>>>
>>> On Friday, March 25, 2022 at 5:43:41 AM UTC-4 Geni wrote:
>>>
 I am having trouble getting the Belchertown skin MQTT websocket
 real-time updates to work correctly on my website
 wetter.affolter.familyds.net.
 I have already spent a lot of time troubleshooting over the last few
 weeks
 I have WeeWx with Mosquitto Broker on a Rasperry 3+ the database
 MariaDB and the webserver on a Synology
 I know that the weewx-mqtt extension is installed correctly enough that
 I can see that the data arrives every 2.5 seconds in the broker on one side
 with "mosquitto_sub -h 192.168.56.51 -t weather/#" and on my desktop
 station with the program MQTT.fx

 But on the web page nothing does only the message Connection (orange)
 but no Connect (green). For testing I didn't want to use SSL certificate.

 Here are my current configs:

 *weewx.conf*
 [[MQTT]]
 server_url = mqtt://user:pass...@192.168.56.51:1883/
 
 topic = wetter
 unit_system = METRIC
 binding = archive, loop
 aggregation = aggregate


 #--- MQTT Websockets (for Real Time Streaming) Options ---
 mqtt_websockets_enabled = 1
 mqtt_websockets_host = mqtt://192.168.56.51
 mqtt_websockets_port = 9001
 mqtt_websockets_ssl = 0
 mqtt_websockets_topic = wetter/loop
 mqtt_websockets_username = user
 mqtt_websockets_password = password
 disconnect_live_website_visitor = 180



 */etc/mosquitto/conf.d/myconfig.conf*
 persistence false
 allow_anonymous true
 password_file /etc/mosquitto/passwd
 acl_file /etc/mosquitto/acl

 # Insecure mqtt to localhost only, and secure mqtt
 listener 1883
 protocol mqtt

 # websockets
 listener 9001
 protocol websockets

 Thanks in advance for anything I may be overlooking, advice or possible
 solutions.

>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/af0fb5e4-cd5b-4890-9cf9-b6e7dfb8683dn%40googlegroups.com
>>> 

Re: [weewx-user] Belchertown skin - dark theme switchover around sunset

[Doug Jenkins]

I looked at the code and yes, this is running on the client side. This
means the light/dark mode is determined y checking the person's web browser
and seeing if it is out of the range of sunrise hours.

If it is, then the JavaScript changes the theme to dark, otherwise it
remains on light.

So what this means if it is midnight where your weather station is on the
east coast of the US, a user in Tokyo (+13 hours) is going to see the light
theme of he goes to your weather website.

Probably what should happen here is the script is fed the server time as a
constant when the cheetah generator "creates" this script upon execution of
StdReport. Then the code will evaluate that datevalue to determine if the
theme should change.

If there is any interest on this item, I recommend putting in an issue on
the GitHub project and send it to me. I can do an update and submit a PR
with the correction.

Doug Jenkins

On Sun, Mar 27, 2022, 12:54 PM vince  wrote:

> Easiest thing to do is figure it out experimentally.Connect into a
> Belchertown site on the other side of the ocean and see.
>
> On Sunday, March 27, 2022 at 9:33:58 AM UTC-7 Eric K wrote:
>
>> I gave a link to the file so you could look at it:
>>
>> https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl
>>
>> There is a definition of a "var d" at line 507.
>> var d = new Date();
>>
>> I still can't tell where it's getting its time from.
>>
>> On Sat, Mar 26, 2022 at 6:37 PM Doug Jenkins 
>> wrote:
>>
>>> I think it is from the local client. The JavaScript is executed in the
>>> browser.
>>>
>>> We need to see where "D" is initialized to make sure it is not using a
>>> web api to obtain the time
>>>
>>> On Sat, Mar 26, 2022, 4:39 PM Eric K  wrote:
>>>
>>>> I have the Belchertown skin theme set to "auto" so it switches over to
>>>> the dark theme around sunset.
>>>> I have noted that the Belchertown skin switches over to the dark theme
>>>> at large fractions of an hour before sunset actually occurs.
>>>> Then, I got a report from a friend in the Eastern time zone, that the
>>>> webpage theme switched to dark around 6:00pm Eastern time - around 2 hours
>>>> early compared to the local sundown time (7:39pm Central) at my weewx
>>>> weather station.
>>>> He said he had not clicked the manual theme switch at the upper right
>>>> corner of the Belchertown page.
>>>>
>>>> So, I started looking through the code to see how the theme change gets
>>>> triggered.
>>>>
>>>> see:
>>>> https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl
>>>>
>>>> Around line 507 the current hour and minute get assigned to variables
>>>> with the expressions
>>>> var nowHour = d.getHours();
>>>> var nowMinutes = d.getMinutes();
>>>> Where is the time being read from?
>>>> 1. from the clock of the computer that weewx is running inside?
>>>> 2. from the clock of webpage visitor's computer?
>>>>
>>>> --
>>>> 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.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/7eb9e891-52a4-4e1f-9e04-e322bb2460bcn%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/7eb9e891-52a4-4e1f-9e04-e322bb2460bcn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>>>
>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/WfhDmYJZZZw/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/CACC0i0xDXGaD0%2BZZ0E-Cu3W6eo_QDOpbxoZ5m0tbe3OxKiCCAg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/weewx-user/CACC0i0xDXGaD0%2BZZ0E-Cu3W6eo_QDOpbxoZ5m0tbe3OxKiCCAg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> You receiv

Re: [weewx-user] Is there a way to suppress LOOP entries in the stdout from WeeWX?

[Doug Jenkins]

Thanks Tom I appreciate it! Worked as expected :)

On Sunday, March 27, 2022 at 7:28:52 AM UTC-4 tke...@gmail.com wrote:

> Just remove "StdPrint" from the list of reporting services to be run. So, 
> this
>
> report_services = weewx.engine.StdPrint, weewx.engine.StdReport
>
> becomes this
>
> report_services = weewx.engine.StdReport
>
>
> On Sun, Mar 27, 2022 at 4:24 AM Doug Jenkins  
> wrote:
>
>> Good Morning:
>>
>> I am preparing a docker image for my new weatherstation. I am configuring 
>> WeeWX the "docker way" where the log data in being written to the stdout 
>> via logging handlers.
>>
>> When I run WeeWX (both in a docker container and on a VM itself), I 
>> always see the LOOP output written to stdout. While this is helpful for 
>> configuration, I want to suppress this via a configuration setting.
>>
>> Is there a way to suppress the LOOP data?
>>
>> Please refer to the LOG SNIPPET and the WeeWX.conf section below for 
>> details.
>>
>> # START LOG SNIPPET =
>> weewx[1] INFO __main__: Initializing weewx version 4.7.0
>> weewx[1] INFO __main__: Using Python 3.10.4 (main, Mar 24 2022, 23:15:59) 
>> [GCC 10.2.1 20210110]
>> weewx[1] INFO __main__: Platform 
>> Linux-4.19.128-microsoft-standard-x86_64-with-glibc2.31
>> weewx[1] INFO __main__: Locale is 'C.UTF-8'
>> weewx[1] INFO __main__: Using configuration file /home/weewx/weewx.conf
>> weewx[1] INFO __main__: Debug is 0
>> weewx[1] INFO weewx.engine: Loading station type Simulator 
>> (weewx.drivers.simulator)
>> weewx[1] INFO weewx.engine: StdConvert target unit is 0x1
>> weewx[1] INFO weewx.wxservices: StdWXCalculate will use data binding 
>> wx_binding
>> weewx[1] INFO weewx.manager: Created and initialized table 'archive' in 
>> database 'weewx.sdb'
>> weewx[1] INFO weewx.manager: Created daily summary tables
>> weewx[1] INFO weewx.engine: Archive will use data binding wx_binding
>> weewx[1] INFO weewx.engine: Record generation will be attempted in 
>> 'hardware'
>> weewx[1] INFO weewx.engine: Using archive interval of 60 seconds 
>> (specified in weewx configuration)
>> weewx[1] INFO weewx.restx: StationRegistry: Registration not requested.
>> weewx[1] INFO weewx.restx: Wunderground: Posting not enabled.
>> weewx[1] INFO weewx.restx: PWSweather: Posting not enabled.
>> weewx[1] INFO weewx.restx: CWOP: Posting not enabled.
>> weewx[1] INFO weewx.restx: WOW: Posting not enabled.
>> weewx[1] INFO weewx.restx: AWEKAS: Posting not enabled.
>> weewx[1] INFO weewx.engine: 'pyephem' detected, extended almanac data is 
>> available
>> weewx[1] INFO __main__: Starting up weewx version 4.7.0
>> weewx[1] INFO weewx.engine: Clock error is -0.05 seconds (positive is 
>> fast)
>> weewx[1] INFO weewx.engine: Using binding 'wx_binding' to database 
>> 'weewx.sdb'
>> weewx[1] INFO weewx.manager: Starting backfill of daily summaries
>> weewx[1] INFO weewx.manager: Empty database
>> weewx[1] INFO weewx.engine: Starting main packet loop.
>> LOOP:   2022-03-27 07:17:24 EDT (1648379844) 'altimeter': 
>> '31.15866069654221', 'appTemp': '28.46010918752483', 'barometer': 
>> '31.09998967093', 'cloudbase': '1294.323176426526', 
>> 'consBatteryVoltage': '12.0', 'dateTime': '1648379844', 'dewpoint': 
>> '27.203560993945757', 'ET': 'None', 'heatindex': '32.67858297022247', 
>> 'heatingVoltage': '10.964725663844588', 'humidex': '32.67858297022247', 
>> 'inDewpoint': '31.079533828013187', 'inHumidity': '29.99958683617', 
>> 'inTemp': '63.0002065819', 'inTempBatteryStatus': '0', 'maxSolarRad': 
>> '1068.3866207089147', 'outHumidity': '79.9996901272', 'outTemp': 
>> '32.67858297022247', 'outTempBatteryStatus': '0', 'pressure': 
>> '31.09998967093', 'radiation': '109.693874983191', 'rain': '0', 
>> 'rainBatteryStatus': '0', 'rainRate': '0.0', 'referenceVoltage': 
>> '10.946701975973381', 'rxCheckPercent': '64.8412332946774', 
>> 'supplyVoltage': '12.774749615929705', '

[weewx-user] Is there a way to suppress LOOP entries in the stdout from WeeWX?

[Doug Jenkins]

Good Morning:

I am preparing a docker image for my new weatherstation. I am configuring 
WeeWX the "docker way" where the log data in being written to the stdout 
via logging handlers.

When I run WeeWX (both in a docker container and on a VM itself), I always 
see the LOOP output written to stdout. While this is helpful for 
configuration, I want to suppress this via a configuration setting.

Is there a way to suppress the LOOP data?

Please refer to the LOG SNIPPET and the WeeWX.conf section below for 
details.

# START LOG SNIPPET =
weewx[1] INFO __main__: Initializing weewx version 4.7.0
weewx[1] INFO __main__: Using Python 3.10.4 (main, Mar 24 2022, 23:15:59) 
[GCC 10.2.1 20210110]
weewx[1] INFO __main__: Platform 
Linux-4.19.128-microsoft-standard-x86_64-with-glibc2.31
weewx[1] INFO __main__: Locale is 'C.UTF-8'
weewx[1] INFO __main__: Using configuration file /home/weewx/weewx.conf
weewx[1] INFO __main__: Debug is 0
weewx[1] INFO weewx.engine: Loading station type Simulator 
(weewx.drivers.simulator)
weewx[1] INFO weewx.engine: StdConvert target unit is 0x1
weewx[1] INFO weewx.wxservices: StdWXCalculate will use data binding 
wx_binding
weewx[1] INFO weewx.manager: Created and initialized table 'archive' in 
database 'weewx.sdb'
weewx[1] INFO weewx.manager: Created daily summary tables
weewx[1] INFO weewx.engine: Archive will use data binding wx_binding
weewx[1] INFO weewx.engine: Record generation will be attempted in 
'hardware'
weewx[1] INFO weewx.engine: Using archive interval of 60 seconds (specified 
in weewx configuration)
weewx[1] INFO weewx.restx: StationRegistry: Registration not requested.
weewx[1] INFO weewx.restx: Wunderground: Posting not enabled.
weewx[1] INFO weewx.restx: PWSweather: Posting not enabled.
weewx[1] INFO weewx.restx: CWOP: Posting not enabled.
weewx[1] INFO weewx.restx: WOW: Posting not enabled.
weewx[1] INFO weewx.restx: AWEKAS: Posting not enabled.
weewx[1] INFO weewx.engine: 'pyephem' detected, extended almanac data is 
available
weewx[1] INFO __main__: Starting up weewx version 4.7.0
weewx[1] INFO weewx.engine: Clock error is -0.05 seconds (positive is fast)
weewx[1] INFO weewx.engine: Using binding 'wx_binding' to database 
'weewx.sdb'
weewx[1] INFO weewx.manager: Starting backfill of daily summaries
weewx[1] INFO weewx.manager: Empty database
weewx[1] INFO weewx.engine: Starting main packet loop.
LOOP:   2022-03-27 07:17:24 EDT (1648379844) 'altimeter': 
'31.15866069654221', 'appTemp': '28.46010918752483', 'barometer': 
'31.09998967093', 'cloudbase': '1294.323176426526', 
'consBatteryVoltage': '12.0', 'dateTime': '1648379844', 'dewpoint': 
'27.203560993945757', 'ET': 'None', 'heatindex': '32.67858297022247', 
'heatingVoltage': '10.964725663844588', 'humidex': '32.67858297022247', 
'inDewpoint': '31.079533828013187', 'inHumidity': '29.99958683617', 
'inTemp': '63.0002065819', 'inTempBatteryStatus': '0', 'maxSolarRad': 
'1068.3866207089147', 'outHumidity': '79.9996901272', 'outTemp': 
'32.67858297022247', 'outTempBatteryStatus': '0', 'pressure': 
'31.09998967093', 'radiation': '109.693874983191', 'rain': '0', 
'rainBatteryStatus': '0', 'rainRate': '0.0', 'referenceVoltage': 
'10.946701975973381', 'rxCheckPercent': '64.8412332946774', 
'supplyVoltage': '12.774749615929705', 'txBatteryStatus': '0', 'usUnits': 
'1', 'UV': '1.5357142497646739', 'windBatteryStatus': '0', 'windchill': 
'32.67858297022247', 'windDir': '359.998140763', 'windGust': 
'6.197456769996279e-09', 'windGustDir': '359.998140763', 'windrun': 
'None', 'windSpeed': '5.164547900449179e-09'

# = END LOG SNIPPET =

#  START WEEWX.CONF LOG CONFIGURATION =
# Do not modify this. It is used when installing and updating weewx.
version = 4.7.0

# LOGGING CONFIGURATION #
[Logging]
version = 1
disable_existing_loggers = False

# Root logger
[[root]]
  level = {log_level}
  handlers = console,

# Additional loggers would go in the following section. This is useful 
for tailoring logging
# for individual modules.
[[loggers]]

# Definitions of possible logging destinations
[[handlers]]

# Log to a set of rotating files
[[[rotate]]]
level = DEBUG
formatter = standard
class = logging.handlers.RotatingFileHandler
filename = /var/log/weewx.log
maxBytes = 1000
backupCount = 4

# Log to console
[[[console]]]
level = INFO
formatter = standard
class = logging.StreamHandler
# Alternate choice is 'ext://sys.stderr'
stream = ext://sys.stdout

# How to format log messages
[[formatters]]
[[[simple]]]
format = "%(levelname)s %(message)s"
[[[standard]]]
format = "{process_name}[%(process)d] %(levelname)s %(name)s: 
%(message)s" 
[[[verbose]]]
format = "%(asctime)s  {process_na

Re: [weewx-user] Belchertown skin - dark theme switchover around sunset

[Doug Jenkins]

I think it is from the local client. The JavaScript is executed in the
browser.

We need to see where "D" is initialized to make sure it is not using a web
api to obtain the time

On Sat, Mar 26, 2022, 4:39 PM Eric K  wrote:

> I have the Belchertown skin theme set to "auto" so it switches over to the
> dark theme around sunset.
> I have noted that the Belchertown skin switches over to the dark theme at
> large fractions of an hour before sunset actually occurs.
> Then, I got a report from a friend in the Eastern time zone, that the
> webpage theme switched to dark around 6:00pm Eastern time - around 2 hours
> early compared to the local sundown time (7:39pm Central) at my weewx
> weather station.
> He said he had not clicked the manual theme switch at the upper right
> corner of the Belchertown page.
>
> So, I started looking through the code to see how the theme change gets
> triggered.
>
> see:
> https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/js/belchertown.js.tmpl
>
> Around line 507 the current hour and minute get assigned to variables with
> the expressions
> var nowHour = d.getHours();
> var nowMinutes = d.getMinutes();
> Where is the time being read from?
> 1. from the clock of the computer that weewx is running inside?
> 2. from the clock of webpage visitor's computer?
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/7eb9e891-52a4-4e1f-9e04-e322bb2460bcn%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xDXGaD0%2BZZ0E-Cu3W6eo_QDOpbxoZ5m0tbe3OxKiCCAg%40mail.gmail.com.

Re: [weewx-user] Re: Belchertown MQTT Issues

[Doug Jenkins]

To add what Tom is saying, when I check your site in the Javascript
console, I see this error:

Uncaught DOMException: Failed to construct 'WebSocket': The URL
'ws://[mqtt://192.168.56.51]:9001/mqtt' is invalid.

The reason the site is not showing the real-time weather data is that the
local brower of your users needs to connect to the website on port 9001 to
get the MQTT topic data to present. Since you are posting your internal
server IP address, the internet user will not receive the information as
there is no way to route this correctly.

What I would do is change mqtt_websockets_host to
wetter.affolter.familyds.net and see if that works.

If it does not work, then the next best option is to set up Cloudflare to
host your domain name and route the websockets and internet traffic to your
local IP address at home. Cloudflare can help with the SSL Certificate
portion automatically. From there, you would use a reverse proxy (NGINX
Proxy Manager) to route the traffic correctly to your MQTT and WeeWX Web
Server instances. Please let me know if you have any other questions or if
you need instructions on how to do this.

Doug


On Fri, Mar 25, 2022 at 7:51 AM t...@tom.org  wrote:

> My websockets_host is just my hostname without the protocol. So instead of
> "mqtt://foo.bar.com" or "ws://foo.bar.com" it is just "foo.bar.com"
>
> On Friday, March 25, 2022 at 5:43:41 AM UTC-4 Geni wrote:
>
>> I am having trouble getting the Belchertown skin MQTT websocket real-time
>> updates to work correctly on my website wetter.affolter.familyds.net.
>> I have already spent a lot of time troubleshooting over the last few weeks
>> I have WeeWx with Mosquitto Broker on a Rasperry 3+ the database MariaDB
>> and the webserver on a Synology
>> I know that the weewx-mqtt extension is installed correctly enough that I
>> can see that the data arrives every 2.5 seconds in the broker on one side
>> with "mosquitto_sub -h 192.168.56.51 -t weather/#" and on my desktop
>> station with the program MQTT.fx
>>
>> But on the web page nothing does only the message Connection (orange) but
>> no Connect (green). For testing I didn't want to use SSL certificate.
>>
>> Here are my current configs:
>>
>> *weewx.conf*
>> [[MQTT]]
>> server_url = mqtt://user:pass...@192.168.56.51:1883/
>> 
>> topic = wetter
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>>
>>
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = mqtt://192.168.56.51
>> mqtt_websockets_port = 9001
>> mqtt_websockets_ssl = 0
>> mqtt_websockets_topic = wetter/loop
>> mqtt_websockets_username = user
>> mqtt_websockets_password = password
>> disconnect_live_website_visitor = 180
>>
>>
>>
>> */etc/mosquitto/conf.d/myconfig.conf*
>> persistence false
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>>
>> # Insecure mqtt to localhost only, and secure mqtt
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> Thanks in advance for anything I may be overlooking, advice or possible
>> solutions.
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/af0fb5e4-cd5b-4890-9cf9-b6e7dfb8683dn%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yKd%2BgS_RwyD%2Ba9g01OWPPjN8s4TXUGT4hKqL_NnQjVxw%40mail.gmail.com.

Re: [weewx-user] Re: belchertown skin question: reporting from multiple weewx instances

[Doug Jenkins]

Thanks Vince, you answered my question. My plan was to run belchertown in a
separate "reporting" instance with database bindings to the aqi and davis
weather station databases (fed with separate weewx instances). I will have
to play with the weewx.conf and skin.conf to see if I can bind certain
values to certain database sources.

For MQTT, I want to publish the live values from both stations, so I will
probably setup each weewx station to publish to separate topics and bring
that in on the reporting weewx instance.

DDJ

On Tue, Mar 22, 2022 at 10:46 PM vince  wrote:

> My recollection is that Belchertown only supports one weewxinstance,
> although you 'can' bind to multiple db within 'one' instance of weewx.  I
> do just that to add info from multiple secondary db to my VP2 data in the
> default db.
>
> You could kludge something together with having one weewx instance publish
> data to MQTT and have the primary one subscribe to that MQTT data if you
> 'really' wanted to add'em all up into one Belchertown dashboard.  I
> actually do that too in order to add stuff from some DS18b20 sensors to my
> Belchertown graphs.
>
> Weewx supporting MQTT pub/sub is very powerful and is rock solid if your
> network and MQTT broker are stable.
>
>
> On Tuesday, March 22, 2022 at 5:54:17 PM UTC-7 do...@dougjenkins.com
> wrote:
>
>> Good evening fellow WeeWX users!
>>
>> I was wondering if anyone was using the belchertown skin with multiple
>> weewx instances. I am going to be setting up my new Davis Vantage Pro 2
>> (just came in today) with a Davis AirLink and I need to bind both the AQI
>> and Weather data together.
>>
>> From what I saw in the repos for WeatherLink Live, I can get the data via
>> one driver, but the AirLink is not supported at the same time. Since WeeWX
>> supports only 1 station per instance, I am going to setup a separate WeeWX
>> instance to talk to AirLink and a separate WeeWX instance to pull in the
>> Weather Station data from WeatherLink Live.
>>
>> I desire to publish both instances to MQTT and report them out on the
>> Belchertown skin.
>>
>> Any help or suggestions with the skin to report both values is
>> appreciated!
>>
>> Doug Jenkins
>> largoweather.com
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/3e093324-202c-4233-896d-798a06f13d02n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/3e093324-202c-4233-896d-798a06f13d02n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xqN-mMtm%3D61NWd%2BSTCHR%2B1t11C_NRFXJHErWXV9HFaLw%40mail.gmail.com.

[weewx-user] belchertown skin question: reporting from multiple weewx instances

[Doug Jenkins]

Good evening fellow WeeWX users!

I was wondering if anyone was using the belchertown skin with multiple 
weewx instances. I am going to be setting up my new Davis Vantage Pro 2 
(just came in today) with a Davis AirLink and I need to bind both the AQI 
and Weather data together.

>From what I saw in the repos for WeatherLink Live, I can get the data via 
one driver, but the AirLink is not supported at the same time. Since WeeWX 
supports only 1 station per instance, I am going to setup a separate WeeWX 
instance to talk to AirLink and a separate WeeWX instance to pull in the 
Weather Station data from WeatherLink Live.

I desire to publish both instances to MQTT and report them out on the 
Belchertown skin.

Any help or suggestions with the skin to report both values is appreciated!

Doug Jenkins
largoweather.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8b7cdb9c-fd67-4696-a7ad-357ed1b9fb96n%40googlegroups.com.

Re: [weewx-user] Weewx-Multi not quite working

[Doug Jenkins]

Tom:

I had trouble with this configuration back 2 years ago when I ran both a
SDR and a Acurite instance of WeeWX using a reporting instance to report
the results for both.

What I did was I created a shell script for each instance (eg wx-sdr,
wx-acurite, wx-rpt) and used cron to execute each at reboot. Here is a
snippet of my script that I used:

#WX_SDR Instance execution
HOME=/home/weewx
CONF_FILE=/home/weewx/conf/wx_sdr.conf LOG_FILE=/home/weewx/logs/wx_sdr.log
echo "using $CONF_FILE"

cd $HOME

./bin/weewxd $CONF_FILE >> $LOG_FILE

WeeWX will start an instance and I just had it report its results in a log.
You can modify this to use logrotate as prescribed in the wiki

logging · weewx/weewx Wiki (github.com)
<https://github.com/weewx/weewx/wiki/logging#save-weewx-log-messages-to-a-separate-file>

hope this helps!

Doug Jenkins
largoweather.com


On Tue, Mar 22, 2022 at 6:26 PM Tom Hogland  wrote:

> I haven't been able to find any record of this behavior. Adjusted my
> working weewx with VP2 to use weewx-multi, added the second config, etc.
> all per the docs, naming/databases/configs etc. Running "/etc/init.d/weewx
> start" fires up both instances, both are working correctly (updating
> webroot files etc.). Problem is, "weewx status" shows neither is running,
> and "weewx stop" says the same, however "weewx restart" closes and restarts
> them both without issue. Specifying either instance name does the same -
> status or stop says not running, restart works fine. Looking at the ps
> listing - both are there and working fine... pid files in /run are also
> correct. I don't see any issues in the script itself.
>
> I imagine there's something simple to this but I can't find it - anyone
> know what's causing the failure to see the correct status?  Or is there a
> simple solution that I just failed to dig out of the docs/forum?
>
> -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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/7a1420e8-3bc2-4b79-9696-581174e3c2aen%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/7a1420e8-3bc2-4b79-9696-581174e3c2aen%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zfSP48yjNJrYfFb3LBkSoFvXC3B6Gu8r3uO_JsmBOrXw%40mail.gmail.com.

Re: [weewx-user] Re: Station upgrade advice (Acurite -> Davis)

[Doug Jenkins]

Ok I pulled the trigger and ordered the Davis 6163 (with console), Airlink, 
and Weatherlink Live today. My first attempt with WeeWX will be using the 
weatherlink weewx driver and the airlink driver to collect the data.

I will report back with my setup, configuration, and experience for others 
that are interested.

On Wednesday, March 16, 2022 at 9:17:21 PM UTC-4 Doug Jenkins wrote:

> Tom:
>
> the reason I am considering the 6163 with the 24 hour aspiration fan is 
> because where I am going to mount the ISS.
>
> On my property, I really have 2 locations to mount the ISS (minus the 
> anemometer), on my TV Tower that is mounted to the side of my house, or on 
> a post in the front yard. The front yard would be ideal, but I was worried 
> someone would steal/damage the unit as it would be sticking out from the 
> street. The location would be perfect on a meterological prespective, but a 
> $1000+ station unprotected is asking for trouble where I live. Plus 
> mounting this device out there would require me to get a solar wireless 
> transmitter device ($149) for the anemometer that is going up the TV tower.
>
> So if I go with mounting the station on my tv tower, I will be putting it 
> up 4 feet above the roof line. With the florida sun, I expect the temp 
> readings to be considerably off, so I figured a aspirating fan would tamper 
> that effect. Again i could be wrong on this approach, so if anyone has run 
> into this as an issue, please let me know.
>
> for the rest of the sensors, I want the UV/Radiation sensors so I can know 
> the UV index at my location.
>
> Again thanks for the great information, it is helping me plan and design 
> this setup out. :)
>
> On Wed, Mar 16, 2022, 10:30 AM Tom Hogland  wrote:
>
>> Only other thing might be, why the 6163? If you need 24-hour fans and the 
>> solar/UV then that's what you need, but it's a hefty price increase to get 
>> those. I think the 6162 loses the fan, and the 6152 (that I have) loses the 
>> solar/UV. Otherwise, the wireless is all the same, as are the basic weather 
>> sensors (the "ISS" to Davis). Note that the 6152C/6162C/etc are the cabled 
>> versions - all the ones without the C in the model are wireless, and all of 
>> the anemometers are wired to the ISS regardless of model (although Davis 
>> has a wireless anemometer adapter, either AC powered or solar).
>>
>> If the WL Live will integrate both devices then that's probably the way 
>> to go - the Envoy pre-dates the Airlink by quite a few years and I can't 
>> see any docs that say it will see the Airlink. (In fact none of the Envoy 
>> docs mention the Airlink...) The Envoy + Weatherlink datalogger mostly 
>> duplicates the WL Live functionality, so you don't need both. The Envoy 
>> *may* be more reliable, depending on a LOT of variables, just because it's 
>> a dedicated ISS receiver that's hard-wired to your weather PC, while the WL 
>> Live depends on your weewx sniffing network packets for data.
>>
>> I have a *real* Dell/Ubuntu server in the basement, so weewx happily runs 
>> on it. If I was to duplicate it today I'd probably go get a Dell/HP/Lenovo 
>> micro-form factor PC instead. Models with 6-8th gen i5 CPUs, 16GB memory 
>> and decent drives are under $300 and that lets them run generic Linux on 
>> them - very easy to support, troubleshoot etc. A "spinny" drive would be my 
>> choice - I'm too old-school to trust any form of SSD for the constant 
>> writes that these systems do, and a 250GB-500GB drive is cheap. I've still 
>> got 20+ year old drives in the basement that function perfectly, although 
>> they're worthless when it comes to capacity - too easy to fill up a 4GB 
>> drive these days :-)
>>
>> On Wednesday, March 16, 2022 at 5:19:37 AM UTC-8 do...@dougjenkins.com 
>> wrote:
>>
>>> Thank you Greg and Tom for the advice and insight! I do appreciate it!
>>>
>>> The reason I am considering the 6163 (VP2+ Wireless) model is that it 
>>> would be a very long cable run through my attic (which has poor access) to 
>>> get to my utility closet where I keep my telco equipment and my dedicated 
>>> machine for the weather station. Plus I might get a soil/leaf module in the 
>>> future to monitor my garden once I recover from the sticker shock of buying 
>>> the initial Davis hardware :)
>>>
>>> For the weatherlink data logger, I will need to consider that in the 
>>> future. Right now I was thinking of just getting the WeatherLink Live 6100 
>>> as according to the user guides, it will allow me to pull the raw data 

Re: [weewx-user] Re: Station upgrade advice (Acurite -> Davis)

[Doug Jenkins]

Tom:

the reason I am considering the 6163 with the 24 hour aspiration fan is
because where I am going to mount the ISS.

On my property, I really have 2 locations to mount the ISS (minus the
anemometer), on my TV Tower that is mounted to the side of my house, or on
a post in the front yard. The front yard would be ideal, but I was worried
someone would steal/damage the unit as it would be sticking out from the
street. The location would be perfect on a meterological prespective, but a
$1000+ station unprotected is asking for trouble where I live. Plus
mounting this device out there would require me to get a solar wireless
transmitter device ($149) for the anemometer that is going up the TV tower.

So if I go with mounting the station on my tv tower, I will be putting it
up 4 feet above the roof line. With the florida sun, I expect the temp
readings to be considerably off, so I figured a aspirating fan would tamper
that effect. Again i could be wrong on this approach, so if anyone has run
into this as an issue, please let me know.

for the rest of the sensors, I want the UV/Radiation sensors so I can know
the UV index at my location.

Again thanks for the great information, it is helping me plan and design
this setup out. :)

On Wed, Mar 16, 2022, 10:30 AM Tom Hogland  wrote:

> Only other thing might be, why the 6163? If you need 24-hour fans and the
> solar/UV then that's what you need, but it's a hefty price increase to get
> those. I think the 6162 loses the fan, and the 6152 (that I have) loses the
> solar/UV. Otherwise, the wireless is all the same, as are the basic weather
> sensors (the "ISS" to Davis). Note that the 6152C/6162C/etc are the cabled
> versions - all the ones without the C in the model are wireless, and all of
> the anemometers are wired to the ISS regardless of model (although Davis
> has a wireless anemometer adapter, either AC powered or solar).
>
> If the WL Live will integrate both devices then that's probably the way to
> go - the Envoy pre-dates the Airlink by quite a few years and I can't see
> any docs that say it will see the Airlink. (In fact none of the Envoy docs
> mention the Airlink...) The Envoy + Weatherlink datalogger mostly
> duplicates the WL Live functionality, so you don't need both. The Envoy
> *may* be more reliable, depending on a LOT of variables, just because it's
> a dedicated ISS receiver that's hard-wired to your weather PC, while the WL
> Live depends on your weewx sniffing network packets for data.
>
> I have a *real* Dell/Ubuntu server in the basement, so weewx happily runs
> on it. If I was to duplicate it today I'd probably go get a Dell/HP/Lenovo
> micro-form factor PC instead. Models with 6-8th gen i5 CPUs, 16GB memory
> and decent drives are under $300 and that lets them run generic Linux on
> them - very easy to support, troubleshoot etc. A "spinny" drive would be my
> choice - I'm too old-school to trust any form of SSD for the constant
> writes that these systems do, and a 250GB-500GB drive is cheap. I've still
> got 20+ year old drives in the basement that function perfectly, although
> they're worthless when it comes to capacity - too easy to fill up a 4GB
> drive these days :-)
>
> On Wednesday, March 16, 2022 at 5:19:37 AM UTC-8 do...@dougjenkins.com
> wrote:
>
>> Thank you Greg and Tom for the advice and insight! I do appreciate it!
>>
>> The reason I am considering the 6163 (VP2+ Wireless) model is that it
>> would be a very long cable run through my attic (which has poor access) to
>> get to my utility closet where I keep my telco equipment and my dedicated
>> machine for the weather station. Plus I might get a soil/leaf module in the
>> future to monitor my garden once I recover from the sticker shock of buying
>> the initial Davis hardware :)
>>
>> For the weatherlink data logger, I will need to consider that in the
>> future. Right now I was thinking of just getting the WeatherLink Live 6100
>> as according to the user guides, it will allow me to pull the raw data for
>> both the airlink and the VP2+ via its API directly from the local device. I
>> see that there are a number of weatherlink weewx drivers on the wiki page
>> from others who are pulling this data today. The weatherlink 6100 will be
>> on a battery backup and directly connected to my home network in a closet
>> that is close to the weather station. I will see if that is enough to go
>> through some of our regular thunderstorms here in West Florida (we lose
>> power on a regular basis).
>>
>> Based on Toms' feedback, I am not going to go with the sonic anemometer.
>> It is very expensive ($540 today) and what I read is that it is good for up
>> to 90mph. I will use the included anemometer with the VP2+ and see how that
>> goes. I read those cups can go through a cat5 hurricane, just hope I do not
>> have to experience that to test that theory out at home!
>>
>> I am going to use a dedicated NUC PC for this station as they are
>> currently cheaper than a RPI4 (8GB) and wil

Re: [weewx-user] Re: Station upgrade advice (Acurite -> Davis)

[Doug Jenkins]

Greg:

In my research, I found that you can locally access the raw data directly
from the weather link device via their web api. In the api calls, you
reference the local ip of the weather link device and port to get the data.

I think most of the weather link drivers perform the same function. I was
looking at some of the repos of these drivers and they are essentially
pulling the UDP data. This is also the same for the airline, just a
different URI.

I am thinking of taking the risk and getting one of these devices and
giving it a shot. I noticed there isn't a guide on how to setup one of
these devices from start to finish. I will probably do a guide on my
experience.

DDJ

On Wed, Mar 16, 2022, 3:13 PM Greg Troxel  wrote:

>
> Tom Hogland  writes:
>
> > If the WL Live will integrate both devices then that's probably the way
> to
> > go - the Envoy pre-dates the Airlink by quite a few years and I can't
> see
> > any docs that say it will see the Airlink. (In fact none of the Envoy
> docs
> > mention the Airlink...) The Envoy + Weatherlink datalogger mostly
> > duplicates the WL Live functionality, so you don't need both. The Envoy
> > *may* be more reliable, depending on a LOT of variables, just because
> it's
> > a dedicated ISS receiver that's hard-wired to your weather PC, while the
> WL
> > Live depends on your weewx sniffing network packets for data.
>
> This is the part I don't understand.   With envoy or console and
> e.g. "Weatherlink serial":
>
>   You can set it up without any proprietary apps, and without any cloud
>   accounts, and without any working internet.
>
>   The logger, at least in the console, keeps logging data while power to
>   the computer is out, and weewx gets this data and puts it in the db
>   when the computer is back.
>
> So with weatherlink live:
>
>   Is it just like a console, data logger, and then a wifi interface that
>   gets an ip address and you can then connect to some port and it's just
>   like serial?
>
>   Do you need a proprietary app to set it up?
>
>   Can you get data locally without WLL sending to the cloud?
>
>   Can you set it up without letting it talk to the internet?
>
>   Can you get data locally if the internet connection is down or
>   firewalled, as long as the wifi works from the weewx machine.
>
>   When you get data locally, is that straightforward and non-kludgy, vs
>   some kind of "interceptor" driver?
>
>
> I looked at the hardware guide
>
>   https://www.weewx.com/docs/hardware.htm#vantage_notes
>
> and the user's guide
>
>   https://www.weewx.com/docs/usersguide.htm#[Vantage]
>
> and it looks like IP connection to weatherlink, but I didn't understand
> the degree of non-consensual cloudiness (regardless of whether on is
> concerned with reliability or privacy :-).
>
> Greg
>
>
>
>
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/rmipmmlognc.fsf%40s1.lexort.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0ygNCT-KC1ephjThgmCH-V1stfYE6FMrGUoDCONjiDZOg%40mail.gmail.com.

[weewx-user] Re: Station upgrade advice (Acurite -> Davis)

[Doug Jenkins]

Thank you Greg and Tom for the advice and insight! I do appreciate it!

The reason I am considering the 6163 (VP2+ Wireless) model is that it would 
be a very long cable run through my attic (which has poor access) to get to 
my utility closet where I keep my telco equipment and my dedicated machine 
for the weather station. Plus I might get a soil/leaf module in the future 
to monitor my garden once I recover from the sticker shock of buying the 
initial Davis hardware :)

For the weatherlink data logger, I will need to consider that in the 
future. Right now I was thinking of just getting the WeatherLink Live 6100 
as according to the user guides, it will allow me to pull the raw data for 
both the airlink and the VP2+ via its API directly from the local device. I 
see that there are a number of weatherlink weewx drivers on the wiki page 
from others who are pulling this data today. The weatherlink 6100 will be 
on a battery backup and directly connected to my home network in a closet 
that is close to the weather station. I will see if that is enough to go 
through some of our regular thunderstorms here in West Florida (we lose 
power on a regular basis).

Based on Toms' feedback, I am not going to go with the sonic anemometer. It 
is very expensive ($540 today) and what I read is that it is good for up to 
90mph. I will use the included anemometer with the VP2+ and see how that 
goes. I read those cups can go through a cat5 hurricane, just hope I do not 
have to experience that to test that theory out at home!

I am going to use a dedicated NUC PC for this station as they are currently 
cheaper than a RPI4 (8GB) and will have a M.2 SSD. That should be more than 
enough hardware to run the website and weewx with no issues.

anything else I am missing?

On Tuesday, March 15, 2022 at 10:37:13 AM UTC-4 tom.h...@gmail.com wrote:

> I'm using a VP2 - about 12 years worth now. My connection is via a serial 
> Weatherlink in a Weather Envoy, as my weewx install is in the basement and 
> my console is upstairs in the living room. Since the WL Live came out the 
> Envoy is more affordable than it used to be, and works great. If you can 
> put your console next to (or close to) the weewx PC then you can just use 
> the serial/USB module, otherwise you'll need the Envoy. 
>
> I use the standard anemometer on my roof; I also have a Tempest with sonic 
> anemometer, and it doesn't seem to be quite as accurate or sensitive as the 
> old-school version. (It's also $500 extra, and I'm cheap...) My anemometer 
> has needed absolutely no maintenance in that 12 years. I'm also thinking 
> about using the AirLink if I can get it's data pulled into weewx and 
> integrated, but haven't seen any discussion about it in here. 
>
> Next plan is to start using the Tempest to report into a weewx instance 
> and see how it compares to the VP2, If it's accurate and reliable it'll go 
> up on the roof pole with the VP2 anemometer and do it's thing.
>
>
> On Monday, March 14, 2022 at 4:33:20 AM UTC-8 do...@dougjenkins.com wrote:
>
>>
>> 1. Should I use the WeatherLink or a direct connection module? Pros/Cons?
>> 2. Has anyone used the Air Quality module from Davis on their weather 
>> station and reported the data using WeeWX?
>> 3. Has anyone used the Davis Sonic Anemometer? I am thinking of putting 
>> the anemometer high up on the tower (33ft/10m), but maintaining that will 
>> be a big chore. I am surrounded by large oaks, so the higher the 
>> anemometer, the better wind reading.
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/396cb8fe-992f-4d4f-8b04-f9085cd41bc0n%40googlegroups.com.

[weewx-user] Station upgrade advice (Acurite -> Davis)

[Doug Jenkins]

Good morning fellow WeeWx users!

I have started to plan my next side project for the spring. Currently I am 
using a Acurite 5-n-1 weather station that is attached on our 40ft TV 
antenna tower since 2018, using weewx since 2019 self-hosting my weewx 
instance on largoweather.com. I have many neighbors using the site to track 
the local weather in our neighborhood for their gardens and our kids school 
is now asking me to do a talk on weather stations for STEM days. 

I now get some decent traffic for the site (all things considering), but 
the station is not really accurate and I am having connection issues 
between the station and the console. I have decided to take the weather 
station project to the next level by buying a Davis 6163 sensor suite, 
including the Air Quality Monitor module.

I have a number of questions and advice interfacing with the Davis station 
and WeeWX:

1. Should I use the WeatherLink or a direct connection module? Pros/Cons?
2. Has anyone used the Air Quality module from Davis on their weather 
station and reported the data using WeeWX?
3. Has anyone used the Davis Sonic Anemometer? I am thinking of putting the 
anemometer high up on the tower (33ft/10m), but maintaining that will be a 
big chore. I am surrounded by large oaks, so the higher the anemometer, the 
better wind reading.

Thanks in advance!

Doug


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b9eb2551-64a8-48aa-a1d4-544ef3bf48c0n%40googlegroups.com.

Re: [weewx-user] Re: want to have /home/weewx/public_html in a ramdisk

[Doug Jenkins]

I am sorry, I didn't read the entire post.

On Sat, Mar 12, 2022, 5:33 PM Eric K  wrote:

> Its' a Raspberry Pi 3B+
>
> On Saturday, March 12, 2022 at 4:25:00 PM UTC-6 do...@dougjenkins.com
> wrote:
>
>> Eric, if you have pi4 with firmware older than 09/2021, you can boot from
>> a usb3 drive. This is what I have been doing with my RPI as I have lost 2
>> good sdcards due to write failures.
>>
>> On Sat, Mar 12, 2022, 4:46 PM Eric K  wrote:
>>
>>> Hi Peter.
>>>
>>> Correct, extending the life of the SD card is my goal.
>>>
>>> I am currently rebuilding my weewx Raspberry Pi system because of a
>>> suspected SD card failure.
>>> I had 2 local Linux users tell me that the symptoms are consistent with
>>> an SD card corruption.
>>> The card is only 9 months old, and it's not bottom-of-the barrel quality!
>>> I reached out for help 2 weeks ago and got zero responses.
>>> see:
>>>
>>> https://forums.raspberrypi.com/viewtopic.php?p=1979221&hilit=kernel+panic#p1979221
>>>
>>>
>>>
>>> On Saturday, March 12, 2022 at 3:35:06 PM UTC-6 peterq...@gmail.com
>>> wrote:
>>>
 If you're wanting a ramdisk because SD cards are unreliable, I wouldn't
 bother. There is plenty of history of people running Weewx on Raspberry Pis
 for many years without a problem with corrupted SD cards.

 On Sat, Mar 12, 2022 at 12:55 PM vince  wrote:

> I would try 'mkdir /home/weewx/public_html/forecast' so the parent
> directory exists when weewx tries to write it.
>
> I'd also add that doing it your way means your NOAA files will be
> recreated every time it boots, which could take ages if you have many 
> years
> of info like many of us do.
>
> One way would be to put something in your rc.local which runs after
> things mount ala:
>
> if [ -d /home/weewx/public_html ]
> then
># prepopulate things here
>mkdir /home/weewx/public_html/forecast
> else
>logger "error - rc.local could not mkdir for weewx"
> fi
>
> You might run into timing issues if you do too much this way since
> rc.local tends to run toward the end of the startup sequence, but a quick
> mkdir should work.
>
> On Saturday, March 12, 2022 at 12:40:49 PM UTC-8 Eric K wrote:
>
>> Currently running weewx 4.5.1 in a Raspberry Pi 3B+ with the Bullseye
>> version of Raspberry Pi OS.
>> For a Raspberry Pi (using a microSD card as the OS system drive) I
>> want to create a ramdisk for the /home/weewx/public_html directory.
>> I followed examples from various webpages on the ramdisk topic.
>> What I've tried thus far doesn't fully work.
>> How are others implementing this?
>>
>> I started by renaming my /home/weewx/public_html directory to
>> /home/weewx/public_html_backup, so there would be no conflict when the
>> ramdisk was created at bootup.
>> Then, I put this line in the /etc/fstab file and rebooted.
>> tmpfs   /home/weewx/public_html   tmpfs   defaults,noatime,size=100M
>>  0 0
>> I tested it with sudo mount -a and the new partition was visible by
>> using the df command.
>>
>> After a reboot, a /home/weewx/public_html directory was created as a
>> tmpfs volume.
>> To test the functionality, I manually ran wee_reports to force the
>> webpage to be created.
>> When wee_reports ran, the process crashed with errors, because some
>> of the files don't exist from previous runs of wee_reports.
>>
>> pi@rpi3b:/home/weewx $ sudo bin/wee_reports
>> Using configuration file /home/weewx/weewx.conf
>> Generating for all time
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/user/belchertown.py", line 1390, in
>> get_extension_list
>> with open(forecast_file, "wb+") as file:
>> FileNotFoundError: [Errno 2] No such file or directory:
>> '/home/weewx/public_html/json/forecast.json'
>>
>> During handling of the above exception, another exception occurred:
>>
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/weewx/reportengine.py", line 196, in run
>> obj.start()
>>   File "/home/weewx/bin/weewx/reportengine.py", line 281, in start
>> self.run()
>>   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 152, in run
>> ngen = self.generate(gen_dict[section_name], self.gen_ts)
>>   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 222, in
>> generate
>> ngen += self.generate(section[subsection], gen_ts)
>>   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 222, in
>> generate
>> ngen += self.generate(section[subsection], gen_ts)
>>   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 310, in
>> generate
>> searchList = self._getSearchList(encoding, timespan,
>>   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 387, in
>> _getSearchList
>> s

Re: [weewx-user] Re: want to have /home/weewx/public_html in a ramdisk

[Doug Jenkins]

Eric, if you have pi4 with firmware older than 09/2021, you can boot from a
usb3 drive. This is what I have been doing with my RPI as I have lost 2
good sdcards due to write failures.

On Sat, Mar 12, 2022, 4:46 PM Eric K  wrote:

> Hi Peter.
>
> Correct, extending the life of the SD card is my goal.
>
> I am currently rebuilding my weewx Raspberry Pi system because of a
> suspected SD card failure.
> I had 2 local Linux users tell me that the symptoms are consistent with an
> SD card corruption.
> The card is only 9 months old, and it's not bottom-of-the barrel quality!
> I reached out for help 2 weeks ago and got zero responses.
> see:
>
> https://forums.raspberrypi.com/viewtopic.php?p=1979221&hilit=kernel+panic#p1979221
>
>
>
> On Saturday, March 12, 2022 at 3:35:06 PM UTC-6 peterq...@gmail.com wrote:
>
>> If you're wanting a ramdisk because SD cards are unreliable, I wouldn't
>> bother. There is plenty of history of people running Weewx on Raspberry Pis
>> for many years without a problem with corrupted SD cards.
>>
>> On Sat, Mar 12, 2022 at 12:55 PM vince  wrote:
>>
>>> I would try 'mkdir /home/weewx/public_html/forecast' so the parent
>>> directory exists when weewx tries to write it.
>>>
>>> I'd also add that doing it your way means your NOAA files will be
>>> recreated every time it boots, which could take ages if you have many years
>>> of info like many of us do.
>>>
>>> One way would be to put something in your rc.local which runs after
>>> things mount ala:
>>>
>>> if [ -d /home/weewx/public_html ]
>>> then
>>># prepopulate things here
>>>mkdir /home/weewx/public_html/forecast
>>> else
>>>logger "error - rc.local could not mkdir for weewx"
>>> fi
>>>
>>> You might run into timing issues if you do too much this way since
>>> rc.local tends to run toward the end of the startup sequence, but a quick
>>> mkdir should work.
>>>
>>> On Saturday, March 12, 2022 at 12:40:49 PM UTC-8 Eric K wrote:
>>>
 Currently running weewx 4.5.1 in a Raspberry Pi 3B+ with the Bullseye
 version of Raspberry Pi OS.
 For a Raspberry Pi (using a microSD card as the OS system drive) I want
 to create a ramdisk for the /home/weewx/public_html directory.
 I followed examples from various webpages on the ramdisk topic.
 What I've tried thus far doesn't fully work.
 How are others implementing this?

 I started by renaming my /home/weewx/public_html directory to
 /home/weewx/public_html_backup, so there would be no conflict when the
 ramdisk was created at bootup.
 Then, I put this line in the /etc/fstab file and rebooted.
 tmpfs   /home/weewx/public_html   tmpfs   defaults,noatime,size=100M
  0 0
 I tested it with sudo mount -a and the new partition was visible by
 using the df command.

 After a reboot, a /home/weewx/public_html directory was created as a
 tmpfs volume.
 To test the functionality, I manually ran wee_reports to force the
 webpage to be created.
 When wee_reports ran, the process crashed with errors, because some of
 the files don't exist from previous runs of wee_reports.

 pi@rpi3b:/home/weewx $ sudo bin/wee_reports
 Using configuration file /home/weewx/weewx.conf
 Generating for all time
 Traceback (most recent call last):
   File "/home/weewx/bin/user/belchertown.py", line 1390, in
 get_extension_list
 with open(forecast_file, "wb+") as file:
 FileNotFoundError: [Errno 2] No such file or directory:
 '/home/weewx/public_html/json/forecast.json'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/home/weewx/bin/weewx/reportengine.py", line 196, in run
 obj.start()
   File "/home/weewx/bin/weewx/reportengine.py", line 281, in start
 self.run()
   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 152, in run
 ngen = self.generate(gen_dict[section_name], self.gen_ts)
   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 222, in
 generate
 ngen += self.generate(section[subsection], gen_ts)
   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 222, in
 generate
 ngen += self.generate(section[subsection], gen_ts)
   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 310, in
 generate
 searchList = self._getSearchList(encoding, timespan,
   File "/home/weewx/bin/weewx/cheetahgenerator.py", line 387, in
 _getSearchList
 searchList += obj.get_extension_list(timespan, db_lookup)
   File "/home/weewx/bin/user/belchertown.py", line 1399, in
 get_extension_list
 raise Warning(
 Warning: Error writing forecast info to
 /home/weewx/public_html/json/forecast.json. Reason: [Errno 2] No such file
 or directory: '/home/weewx/public_html/json/forecast.json'

 I found that if I copy the contents of my
 /home/weewx/public

Re: [weewx-user] Re: VatnagePro driver: what is the best way to get archiveRecords every minute?

[Doug Jenkins]

Saverio:

Reading your post, have you considered using mqtt for each station node
publishing it's archive data to a single broker?

I wonder if you could do the following to achieve the same goal:

1. Set each station node archive interval to 1 minute.
2. Install weewx mqtt extension on each node
3. Configure each node to publish to a different topic, for example
weather-n1, n2,etc.
4. Configure the mqtt driver to just publish archive data.
5. Setup a mosquito mqtt broker on the same network to collect all the
data. It can be setup in a container.

This assumes all of your nodes are on the same network, although you could
setup the mqtt broker in a cloud instance if the nodes are not on the same
network.

That way you will get the full archive record published from each station.
You would just need to focus on consuming the published data from the
broker. At least all the data will be in a single place.

Just a thought.

On Sat, Mar 12, 2022, 6:50 AM Saverio Guzzo  wrote:

> PS. One detail that I forgot to mention: Balena uses docker images, for
> running the program I'm using
> balenalib/raspberrypi4-64-python:3.8-stretch-run
> 
>
> On Saturday, 12 March 2022 at 11:17:13 UTC+1 Saverio Guzzo wrote:
>
>> Hey community,
>>
>> I have a fleet of Davis weather stations connected to as many
>> RaspberryPis, on which I am running the vantage drivers as a standalone
>> program on docker container, deployed using Balena
>> .
>> I'd like my program to send data every minute to a REST API and I've been
>> looking into some way to get archive data from a in loop, but I'm not sure
>> I'm doing it the right way.
>>
>> What I did was defining in the driver's main method something like:
>>
>> *while True:*
>> * since_ts = datetime.datetime.timestamp(datetime.datetime.now() -
>> datetime.timedelta(minutes=1))*
>> * for packet in vantage.genDavisArchiveRecords(since_ts):*
>> * try:*
>> * new_packet = weewx.units.to_METRICWX(packet)*
>> * davispusher.send_message(payload=new_packet)*
>> * log.debug(davispusher.payload)*
>> * except Exception as e:*
>> * log.debug("Found an exception: %s" % e)*
>> * time.sleep(1.2)*
>> * continue*
>> * time.sleep(60)*
>>
>> Where davispusher is an instance of a simple class that is needed to add
>> some values to the archive record and send the message and is defined as:
>> *class DavisPusher:*
>> * def __init__(self, host='https://mywebsite.somewhere
>> , port=8080, endpoint='davis'):*
>> * self._endpoint = "{host}:{port}/{endpoint}".format(host=host, *
>> * endpoint=endpoint,*
>> * port=port)*
>> * self.payload = {}*
>>
>> * def format_message(self,*
>> * payload: dict,*
>> * sensor_id: str = environ['SENSOR_ID'],*
>> * latitude: str = environ['LATITUDE'],*
>> * longitude: str = environ['LONGITUDE'],*
>> * altitude: str = environ['ALTITUDE'],*
>> * ) -> dict:*
>> * """Formats message for backend."""*
>>
>> * payload_copy = payload.copy()*
>> * try:*
>> * self.payload = payload_copy*
>> * self.payload['sensor_id'] = sensor_id*
>> * self.payload['altitude'] = float(altitude)*
>> * self.payload['longitude'] = float(longitude)*
>> * self.payload['latitude'] = float(latitude)*
>>
>> * except Exception:*
>> * self.payload = {}*
>> * def send_message(self, payload):*
>> * '''formats and sends message to backend'''*
>> * self.format_message(payload)*
>> * resp = requests.post (self._endpoint, data =
>> json.dumps(self.payload), allow_redirects = True)*
>> * log.debug("got HTTP statuscode %s", resp.status_code)*
>>
>> However, my logs are full of logging errors ("Bad file descriptor", "File
>> "/usr/local/lib/python3.8/logging/handlers.py" No such file or directory")
>> I guess those are errors due to logging configuration, but I'm not sure
>> how to address them. I created a GitHub Gist
>>  in
>> order not to pollute this post!
>>
>> Also, what I would like to achieve is the possibility to configure the
>> various consoles (set time, set coordinates) at startup using environment
>> variables. How could I do this using the VantageConfigurator class?
>>
>> Thanks a lot in advance for your help, I'm kind of alone in my work and
>> I'd really appreciate your help.
>>
>> Friendly greetings,
>> Saverio
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/55d40e74-aa67-40c0-bcb6-8b8a03c9a665n%40googlegroups.com
> 

[weewx-user] Re: Hi All, I am running weewx-sdr/MQTT loop packets with Belchertown skin. I have an Acurite 0645M lightning detector, and I've been having major trouble getting it to display the "delta

[Doug Jenkins]

I have tried my hand in this device last year with SDR and MQTT. What I 
found is that the device's counter counts up to 127 (or 255 depending on 
the SDR release) then essentially resets back to zero. I did not see any 
code that would compare the incoming value (eg strike count is now 100) to 
the loop value (eg 99) and update the strike count by 1. 

My best guess is that Acurite's base station is doing this math difference 
and showing you the total strikes for the day with the distance of the last 
strike.

What needs to be done here is have a driver/service that will take the raw 
SDR value for lightning strike count and distance, compare it to the last 
reported value, then create a record recording the strike count and 
distance as a separate row in a table (eg lighting_raw_data). Once the 
archive generation starts, you take the sum of the strikes between archive 
periods and average the strike distance. I believe that is what the 
accumulator will do for you.

This is where I gave up on the device. I have it in my "nice to have" notes 
to write this component one day.

An alternative is to look at the AS3925 lightning sensor. You can attach 
that to a Raspberry PI and use Matthew Wall's driver (matthewwall/weewx-as3935: 
weewx service that collects data from as3935 lightning detector (github.com) 
<https://github.com/matthewwall/weewx-as3935>) in a separate weewx instance 
reporting to a separate db. From there you can bind both databases in your 
main weewx install and report the lightning data in your skin. Look up 
multiple database bindings in the docs side of the the weewx documentation.

Hope that helps!

Doug Jenkins
www.largoweather.com



On Monday, March 7, 2022 at 8:42:46 AM UTC-5 Kingsclear Studios wrote:

> Thanks Troy, can confirm it's in place, makes no difference:
>
> [Accumulator]
> [[lightning_strike_count]]
> extractor = sum
> [[lightning_distance]]
> extractor = min
> merger = minmax
>
> Lightning Distance is working perfectly, after each artificial strike test 
> (power drill + brushless motor = fake lightning) I get the distance updated 
> properly, with units, my total_strikes count goes up, and I see odd entries 
> like: strike_count: 0.0 - but no delta value(s), I've been trying for ages, 
> it seems to elude me :)
>
> Sample MQTT data flowing to the station as of now:
>
> { "inHumidity": "31.0", "inTemp_C": "23.775", "strikes_total": 
> "244.0", "lightning_distance_km": "6.437376", "dateTime": "1646660541.0", 
> "inDewpoint_C": "5.625713349750434", "maxSolarRad_Wpm2": 
> "362.7045034071919", "rainRate_cm_per_hour": "0.0", "strikes_count": "0.0", 
> "rain_total": "1.59", "windSpeed_kph": "4.310998666280064", "outTemp_C": 
> "5.889", "outHumidity": "86.0", "appTemp_C": 
> "3.6810358576208713", "cloudbase_meter": "326.41695917564834", 
> "dewpoint_C": "3.7282050766260766", "heatindex_C": "4.7788891", 
> "humidex_C": "5.889", "windchill_C": "5.889", 
> "extraTemp1_C": "5.3995", "extraHumid1": "53.0", "windDir": 
> "225.0", "hourRain_cm": "0.025423", "rain24_cm": 
> "1.98120007", "dayRain_cm": "0.7112", "usUnits": "16.0" }
> On Monday, March 7, 2022 at 9:02:11 AM UTC-4 tarob...@gmail.com wrote:
>
>> The only thing I see missing from your weewx.conf would be the 
>> Accumulator section:
>>
>> [Accumulator]
>> [[lightning_strike_count]]
>> extractor = sum
>> [[lightning_distance]]
>> extractor = min
>>
>> See if adding the Accumulator section in your weewx.conf fixes your issue.
>>
>> -Troy
>>
>> On Sunday, March 6, 2022 at 7:40:30 AM UTC-5 Kingsclear Studios wrote:
>>
>>> Weewx Conf:
>>>
>>> [SDR]
>>> # This section is for the software-defined radio driver.
>>>
>>> # The driver to use
>>> driver = user.sdr
>>> path = /usr/local/bin
>>> log_unknown_sensors = True
>>> log_unmapped_sensors = True
>>> [[sensor_map]]
>>> extraTemp1 = temperature.1720.AcuriteTowerPacketV2# basement
>>> extraHumid1 = humidity.1720.AcuriteTowerPacketV2

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Yes. I would run docker-compose up and check to see if the docker
containers are running. If you are using portainer, check the stack there.

You will know if weewx is working by reviewing the log from the docker
container. Again I like using portainer for this as the GUI allows an easy
interface to see the results.

Common issues that you will run into are permissions to the host
directories that weewx/MQTT/NGINX need to access. then the next possible
issue would be access to your weather station hardware (assumed you plugged
the console to the RPI). You will need to debug this a bit to get it to
work properly.

if you need to debug the solution, just edit the weewx.conf located in your
config folder on the host and restart the containers. Weewx.conf is the
main file that governs weewx.

DDJ

On Sun, Feb 20, 2022 at 4:37 PM Adam Morgan 
wrote:

> Sorry, did a private response by mistake a minute ago.  I do understand
> the basics of docker.   This particular approach is a bit new to me so I
> thought I would ask what to do next.  The config files are in place - is it
> a matter of just issuing a docker run with the image?
>
> On Sunday, February 20, 2022 at 2:53:33 PM UTC-5 vince wrote:
>
>> On Sunday, February 20, 2022 at 11:15:42 AM UTC-8 muchgoo...@gmail.com
>> wrote:
>>
>>> I then ran all of your commands by hand.  The first was running "docker
>>> build ." to initiate the build.  I then did each command one by one.  That
>>> seemed to go well - I see the image and the folders populated as expected.
>>> Now what?  Should I see a container?
>>>
>>
>> You guys might want to consider taking this one offline to email at this
>> point, but...
>>
>> Tom - I'd suggest you do might some more reading up on Docker
>> (do https://www.docker.com/101-tutorial - it's pretty good)
>>
>>- An "image" is a built configured reusable thing.
>>- A "container" is a running instance of that image.
>>- Building an image ala 'docker build' or 'docker-compose build' does
>>not create a running instance (container) of that image.
>>- You have to do "docker run' or 'docker-compose up' to start a
>>container running.
>>- Changes made while building an image persist.
>>- Changes made within a running container go 'poof' when the
>>container stops
>>
>> What his scripts are doing is populating an external mounted directory
>> under /srv on persistent storage.
>>
>> But blindly running somebody else's script without spinning yourself up a
>> bit more on how Docker works is just going to be confusing and frustrating.
>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/63f503fd-c774-45c9-9690-31c9fc7f3b7bn%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yGMaCoT0U6F6ijA%2BVdxiOiW4A4OWi%3DDJLQhRm9UBjb7Q%40mail.gmail.com.

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Essentially yes. I would login with the user account that has docker access
and clone my repo in the current directory (~). Then I would configure the
docker-compose.yml and the weewx.conf files inside my config folder and use
the shell script to build it out.

You probably have to tinker with the setup as I got this to work on Ubuntu
and not on Debian.

Also, you do not have to use MariaDB with weewx. I like using MariaDB
because I like to query the live db to run checks and to build a new
interface in the future.

Let me know where you end up. I am checking my email daily now so I can be
more available to help.

On Fri, Feb 18, 2022, 10:03 AM Adam Morgan  wrote:

> Thank you again Doug!  I can't tell you how much I appreciate it.
>
> Ok, I think I got most of what you are saying.  So for your example I
> would be copying all of the files in your repo to the /weewx folder on my
> host, modify the yml file, and then execute the config.sh file?
>
>
>
> On Friday, February 18, 2022 at 8:41:09 AM UTC-5 do...@dougjenkins.com
> wrote:
>
>> Adam:
>>
>> Sorry for the late reply. I am still adjusting my gmail filters to get
>> all the weewx-users and weewx-developer messages through.
>>
>> I ran into the same problem when I started using the docker image for my
>> custom install. I wanted to bring in a few of the popular weewx extensions
>> (MQTT, Belchertown, Windy) yet if I recreate the container, I would have to
>> manually re-add these extensions and then post my weewx.conf back into the
>> solution. This can be a problem when you have to reboot the server for
>> maintenance.
>>
>> So going back to my notes and repo internally, what I did was to create
>> my own docker image using Tom Mitchell's image, then loading the extensions
>> and then copying my weewx.conf file back AFTER the extensions were
>> installed. I also updated his executing script (/bin/run) to point the
>> weewx.conf file to a specific folder (/home/weewx/config/weewx.conf). This
>> way I can make changes to the weewx.conf, redeploy the solution, rebuild
>> the image, etc.
>>
>> To help understand all of this (as this took some time to set up as I was
>> learning docker), I created a public github repo that has all of these
>> files and configurations set so you can see how I set up my station. All of
>> the sensitive items have been removed, so you will need to go through the
>> config files and update them for your station.
>>
>> here is that link : WeeWX Docker Stack Example (NGINX | MQTT | WEEWX |
>> MARIADB) 
>>
>> Please let me know if this helps and let me know the next issue that you
>> run into.
>>
>> DDJ
>>
>>
>> On Thu, Feb 17, 2022 at 8:25 PM Adam Morgan  wrote:
>>
>>> @DougJenkins I am hoping that you might be able to see what I am doing
>>> wrong.  I can see that the config files are being written inside the docker
>>> container and not the path in /AppData.  The weird thing is that it does
>>> create the WeeWx folder in AppData but it is empty.
>>>
>>> https://hub.docker.com/r/mitct02/weewx
>>>
>>> The documentation is for docker run and thus it isn't the same thing:
>>>
>>> docker run -d --volume /Users/tom/weewx.conf:/home/weewx/weewx.conf
>>> --volume
>>>
>>> I did try this - I ended up with a subfolder of "weex.conf" that was
>>> again empty.
>>>
>>>
>>>
>>> On Wednesday, February 16, 2022 at 9:27:07 AM UTC-5 Adam Morgan wrote:
>>>
 Do you see anything wrong in the config that I posted yesterday?

 Here is the view from putty:



 On Tuesday, February 15, 2022 at 9:24:51 PM UTC-5 vince wrote:

> Wild guess is that you either tried to map to directories that don't
> exist, or your volume mounts aren't working.
>
>
> --
>>> 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.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/7f7a2556-0ba4-4a86-80bb-7c3a120dd335n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/fy3nqJ34Ho0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b6283982-ca35-4220-80cd-fa4f770b11e7n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscri

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Adam:

Sorry for the late reply. I am still adjusting my gmail filters to get all
the weewx-users and weewx-developer messages through.

I ran into the same problem when I started using the docker image for my
custom install. I wanted to bring in a few of the popular weewx extensions
(MQTT, Belchertown, Windy) yet if I recreate the container, I would have to
manually re-add these extensions and then post my weewx.conf back into the
solution. This can be a problem when you have to reboot the server for
maintenance.

So going back to my notes and repo internally, what I did was to create my
own docker image using Tom Mitchell's image, then loading the extensions
and then copying my weewx.conf file back AFTER the extensions were
installed. I also updated his executing script (/bin/run) to point the
weewx.conf file to a specific folder (/home/weewx/config/weewx.conf). This
way I can make changes to the weewx.conf, redeploy the solution, rebuild
the image, etc.

To help understand all of this (as this took some time to set up as I was
learning docker), I created a public github repo that has all of these
files and configurations set so you can see how I set up my station. All of
the sensitive items have been removed, so you will need to go through the
config files and update them for your station.

here is that link : WeeWX Docker Stack Example (NGINX | MQTT | WEEWX |
MARIADB) 

Please let me know if this helps and let me know the next issue that you
run into.

DDJ


On Thu, Feb 17, 2022 at 8:25 PM Adam Morgan 
wrote:

> @DougJenkins I am hoping that you might be able to see what I am doing
> wrong.  I can see that the config files are being written inside the docker
> container and not the path in /AppData.  The weird thing is that it does
> create the WeeWx folder in AppData but it is empty.
>
> https://hub.docker.com/r/mitct02/weewx
>
> The documentation is for docker run and thus it isn't the same thing:
>
> docker run -d --volume /Users/tom/weewx.conf:/home/weewx/weewx.conf
> --volume
>
> I did try this - I ended up with a subfolder of "weex.conf" that was again
> empty.
>
>
>
> On Wednesday, February 16, 2022 at 9:27:07 AM UTC-5 Adam Morgan wrote:
>
>> Do you see anything wrong in the config that I posted yesterday?
>>
>> Here is the view from putty:
>>
>>
>>
>> On Tuesday, February 15, 2022 at 9:24:51 PM UTC-5 vince wrote:
>>
>>> Wild guess is that you either tried to map to directories that don't
>>> exist, or your volume mounts aren't working.
>>>
>>>
>>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/7f7a2556-0ba4-4a86-80bb-7c3a120dd335n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zSvRmGg9hVpQPbzn9yaOaM-Ri4AOBW3s3Arsz4uLn1Wg%40mail.gmail.com.

[weewx-user] Re: Upgrade Raspberry Pi 2 to Raspberry Pi 4

[Doug Jenkins]

Well that depends:

1. What version of Raspbian is the RPi2 using?
2. Do you have any device-specific items on i2c or via GPIO?

If it is a RPI4 and the RAM is over 4GB (eg 8gb version), then you should 
consider setting up the new Raspberry Pi OS 64bit release. 

Another consideration is to update the micro-sd card to another newer card 
or use a USB drive. The new RPI4s (newer than Sept 2020) support boot from 
USB Device.

Just my $0.02

DDJ

On Monday, February 14, 2022 at 4:34:31 PM UTC-5 bchap...@gmail.com wrote:

> Can I just swap out the card?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/14ce56e6-7597-46e6-867d-85873ad36d3dn%40googlegroups.com.

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Adam:

By Default, each stack in Docker will have its own internal network. These 
will show up as 172.16.x.x. That is ok as docker will route traffic from 
the host to the container as long as you have the ports mapped correctly.

The next thing we need to check is to see if you have a http server inside 
the container that you are running with WeeWx. Looking at felddy's 
weewx-docker Dockerfile (weewx-docker/Dockerfile at develop · 
felddy/weewx-docker · GitHub 
) I did not 
see a http server serving the pages. So the html will not be viewable 
without a http server.

The best course of action here is to spin up a http server as a container. 
I actually do this for my setup (www.largoweather.com) using a nginx 
container. What i do is configure weewx to write to a directory that is 
shared with the container. Then I add both containers to the same yaml file 
and have them share the same network. 

Here is a copy of my yaml file. In it I am running Tom Mitchell's weewx 
container (GitHub - tomdotorg/docker-weewx: Docker image for weewx weather 
software ) with Belchertown skin 
using a MQTT broker with a ngnix web server. You can modify this to your 
liking. If you have any questions on the configs, just let me know.

# == WEEWX STACK START ==
version: "2.1"
services:
  web:
image: nginx
container_name: weewx_web
networks:
  - wxnet
ports:
  - 91:80
depends_on:
  - mqtt-broker
  - weewx-engine
environment:
  - TZ=America/New_York
  - NGINX_HOST=<>.com
  - NGINX_PORT=80
volumes:
  - /media/docker/volumes/weewx/html:/usr/share/nginx/html:ro
  - /media/docker/volumes/ngnix/templates:/etc/nginx/templates
restart: unless-stopped 
  
  mqtt-broker:
image: eclipse-mosquitto:latest
container_name: weewx_mqtt
networks:
  - wxnet
environment:
  - TZ=America/New_York
volumes:
  - /media/docker/volumes/weewx/mosquitto/config:/mosquitto/config
  - /media/docker/volumes/weewx/mosquitto/data:/mosquitto/data
  - /media/docker/volumes/weewx/mosquitto/log:/mosquitto/log
ports:
  - 1883:1883
  - 9001:9001
depends_on:
  - weewx-engine
restart: unless-stopped
  
  weewx-engine:
image:  mitct02/weewx:4.5.1
container_name: weewx_engine
environment:
  - TZ=America/New_York
networks:
  - wxnet
privileged: true
volumes:
  - /media/docker/volumes/weewx/config/:/home/weewx/conf/
  - 
/media/docker/volumes/weewx/skins/Belchertown/:/home/weewx/skins/Belchertown/
  - /media/docker/volumes/weewx/html/:/home/weewx/public_html/
restart: unless-stopped
 
networks:
  wxnet:
driver: bridge


# == WEEWX STACK STOP ===[



On Sunday, February 13, 2022 at 6:36:49 PM UTC-5 muchgoo...@gmail.com wrote:

> Sorry, still struggling with this one.  I don't want a new network 
> created.  Instead, I just want to bind to the host.  Any help would be 
> greatly appreciated.  Thank you again!
>
> On Sunday, February 13, 2022 at 1:54:28 PM UTC-5 Adam Morgan wrote:
>
>> Thank you, that's a good thought.  I did verify that nothing else is 
>> using that port (I only have 10ish containers).
>>
>> I did notice that this created a new network.  Could that be the issue?  
>> In my limited experience I have only ever used "host".  This is a device 
>> running on my network and not local host - would that mean that I can't use 
>> the IP of the host to access it through the browser?  
>>
>> On Sunday, February 13, 2022 at 1:05:29 PM UTC-5 vince wrote:
>>
>>> I'd run "docker ps -a" and look at which containers are forwarding 
>>> which ports.
>>>

>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1d94b41b-62f8-43c6-9799-8a53289415e9n%40googlegroups.com.

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

yes, you can map any port from the internal container to the external
machine. For example, if you want to map the container's http port (80) to
an external port 91, this is what you would do:

version: "3.8"


services:
  weewx:
image: felddy/weewx
init: true
restart: "yes"
privileged: true
ports:
   - 91:80
volumes:
  - /srv/dev-disk-by-label-Docker/AppData/WeeWx/:/home/weewx/conf/
environment:
  - TZ=TZ=America/New_York
  - WEEWX_UID=1000
  - WEEWX_GID=1000

One thing if you are going to publish your weewx website to the public
internet, you want to run a Proxy Manager in front of it. I recommend Nginx
Proxy Manager. It will accept traffic for multiple websites domains and
route it to specific ports on your server (or other servers in
your network). Furthermore it will handle SSL for you.

I would strongly suggest reviewing these YouTube video below in setting up
Nginx proxy manager with portainer using CloudFlare. This will keep your
network and your server secure and will ensure SSL on your site with no
cost.

https://youtu.be/Ha8NIAOsNvo


DDJ

On Sat, Feb 12, 2022 at 1:06 PM Adam Morgan 
wrote:

> Thank you so much Doug!  That is fantastic information.  I have one more
> question that I meant to ask earlier.  Is there a way to change the port to
> something other than 8080 in the creation step?  I have another container
> using that port.  Or can that be done later?
>
> On Saturday, February 12, 2022 at 9:20:14 AM UTC-5 do...@dougjenkins.com
> wrote:
>
>> Adam:
>>
>> I am also using Portainer with Docker. I am using Ubuntu, but the
>> commands and approach are the same.
>>
>> The issue that you have is that you need to bind the container's volume
>> to a local volume. While the volume tag works, I always found this to work.
>>
>> Also I see a few issues with your yaml definition:
>>
>> 1. Your Environment Variable for timezone should be TZ=America/New_York.
>> 2. your WeeWX user id and group id look off. run uid on the terminal and
>> see what your group id and user ids are and update the file. most likely
>> they are 1000 each.
>> 3. While device mapping is allowed, I could not get it to properly work
>> in portainer. The only way I got it to work is by adding the line
>> "privileged: true". This has the container run with sudo privileges and
>> exposes the /dev directory to the container. That way WeeWX can communicate
>> directly with your USB device.
>>   (PS: If someone has a way to run this with standard privileges, I am
>> all ears!)
>> 4. I use mitcht02/weewx:4:5:1 docker image from Tom Mitchell. His image
>> has been up to date and runs WeeWx nicely in a dockerized way.
>>
>> so I modified your yaml file below with those changes. Give it a go and
>> let me know if you have any questions.
>>
>>
>> version: "3.8"
>>
>>
>> services:
>>   weewx:
>> image: felddy/weewx
>> init: true
>> restart: "yes"
>> privileged: true
>> volumes:
>>   - /srv/dev-disk-by-label-Docker/AppData/WeeWx/:/home/weewx/conf/
>> environment:
>>   - TZ=TZ=America/New_York
>>   - WEEWX_UID=1000
>>   - WEEWX_GID=1000
>>
>> DDJ
>>
>> On Sat, Feb 12, 2022 at 8:58 AM Adam Morgan  wrote:
>>
>>> Hello, I have a working knowledge of docker and linux but not much
>>> beyond that.  I have used both for years and can generally follow a guide
>>> to create a container.
>>>
>>> I found a sample yml file in the docs so I decided to try that as my
>>> installation method.  I am running Open Media Vault, which is debian.  I am
>>> trying to perform this installation using portainer and portainer will
>>> perform  a docker-compose on the yml file.
>>>
>>> So here is my yml file.  I am getting an error on the volume - it is
>>> telling me that volume must be a mapping and not a string.  I'd appreciate
>>> any advice as I am not sure that my other configs are correct either (I am
>>> going on what I've done for other containers).
>>>
>>> ---
>>> version: "3.8"
>>>
>>> volumes:
>>>   data:/srv/dev-disk-by-label-Docker/AppData/WeeWx
>>>
>>> services:
>>>   weewx:
>>> image: felddy/weewx
>>> init: true
>>> restart: "yes"
>>> volumes:
>>>   - type: bind
>>> source: ./data
>>> target: /data
>>> environment:
>>>   - TIMEZONE=US/Eastern
>>>   - WEEWX_UID=1000
>>>   - WEEWX_GID=100
>>> devices:
>>>   - "/dev/ttyUSB0:/dev/ttyUSB0"
>>>
>>> --
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/a502db19-07dd-4616-8938-6d23aba3b116n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
> You received this message bec

Re: [weewx-user] Trying to install docker and need yml assistance

[Doug Jenkins]

Adam:

I am also using Portainer with Docker. I am using Ubuntu, but the commands
and approach are the same.

The issue that you have is that you need to bind the container's volume to
a local volume. While the volume tag works, I always found this to work.

Also I see a few issues with your yaml definition:

1. Your Environment Variable for timezone should be TZ=America/New_York.
2. your WeeWX user id and group id look off. run uid on the terminal and
see what your group id and user ids are and update the file. most likely
they are 1000 each.
3. While device mapping is allowed, I could not get it to properly work in
portainer. The only way I got it to work is by adding the line "privileged:
true". This has the container run with sudo privileges and exposes the /dev
directory to the container. That way WeeWX can communicate directly with
your USB device.
  (PS: If someone has a way to run this with standard privileges, I am all
ears!)
4. I use mitcht02/weewx:4:5:1 docker image from Tom Mitchell. His image has
been up to date and runs WeeWx nicely in a dockerized way.

so I modified your yaml file below with those changes. Give it a go and let
me know if you have any questions.


version: "3.8"

services:
  weewx:
image: felddy/weewx
init: true
restart: "yes"
privileged: true
volumes:
  - /srv/dev-disk-by-label-Docker/AppData/WeeWx/:/home/weewx/conf/
environment:
  - TZ=TZ=America/New_York
  - WEEWX_UID=1000
  - WEEWX_GID=1000

DDJ

On Sat, Feb 12, 2022 at 8:58 AM Adam Morgan 
wrote:

> Hello, I have a working knowledge of docker and linux but not much beyond
> that.  I have used both for years and can generally follow a guide to
> create a container.
>
> I found a sample yml file in the docs so I decided to try that as my
> installation method.  I am running Open Media Vault, which is debian.  I am
> trying to perform this installation using portainer and portainer will
> perform  a docker-compose on the yml file.
>
> So here is my yml file.  I am getting an error on the volume - it is
> telling me that volume must be a mapping and not a string.  I'd appreciate
> any advice as I am not sure that my other configs are correct either (I am
> going on what I've done for other containers).
>
> ---
> version: "3.8"
>
> volumes:
>   data:/srv/dev-disk-by-label-Docker/AppData/WeeWx
>
> services:
>   weewx:
> image: felddy/weewx
> init: true
> restart: "yes"
> volumes:
>   - type: bind
> source: ./data
> target: /data
> environment:
>   - TIMEZONE=US/Eastern
>   - WEEWX_UID=1000
>   - WEEWX_GID=100
> devices:
>   - "/dev/ttyUSB0:/dev/ttyUSB0"
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a502db19-07dd-4616-8938-6d23aba3b116n%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0zcsXuNyObc0zEVMy0PWgsD_WtbuJfYpy-%2B-AC2UxHOJA%40mail.gmail.com.

Re: [weewx-user] Anyone else seeing Wunderground Rapid Fire down?

[Doug Jenkins]

Specifically looking at my log, it started to fail at 9:15AM EST and
continues to fail. I will restart my docker image and see if it will clear
up. Sounds like this is all related to an api endpoint issue.

On Tue, Feb 8, 2022 at 11:10 AM Tom Hogland  wrote:

> Mine's been fine until this morning - dropped offline and logs show I'm
> unable to connect to upload. Apparently the issues persist...
>
> On Monday, February 7, 2022 at 7:40:52 AM UTC-9 Jeremy A wrote:
>
>> Yes, seems to be working again. using RF as well
>>
>> On Monday, February 7, 2022 at 10:39:12 AM UTC-6 n0...@n0nb.us wrote:
>>
>>> * On 2022 07 Feb 06:44 -0600, Jeremy A wrote:
>>> > Not working with or without rapid fire for me... Looks like it came
>>> back
>>> > online during the night but it's down again.
>>>
>>> It seems to be working, at least no errors in my log since 8:40 AM
>>> CST/1440z this morning.
>>>
>>> - Nate
>>>
>>> --
>>> "The optimist proclaims that we live in the best of all
>>> possible worlds. The pessimist fears this is true."
>>> Web: https://www.n0nb.us
>>> Projects: https://github.com/N0NB
>>> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>>>
>>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/3a47dc03-ed92-4efc-996f-d42208e31e82n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/3a47dc03-ed92-4efc-996f-d42208e31e82n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yY%2B_7XF4XNfPeb_qJPuV8HOf6UzuZHY1Dggac1GHm3pA%40mail.gmail.com.

Re: [weewx-user] Re: Updated to 4.6.0 Wunderground service upload fails

[Doug Jenkins]

orks ok and I am running the default Skin.
>>>>
>>>> I am uploading to PWSWeather and that is fine, but uploading to
>>>> Wunderground fails.
>>>> Log message:-
>>>> Feb  8 15:42:44 Pi3-Weewx weewx[964] ERROR weewx.restx:
>>>> Wunderground-PWS: Failed to publish record 2022-02-08 15:40:00 GMT
>>>> (1644334800): Failed upload after 3 tries
>>>>
>>>> I haven't changed to password in the weewx.conf file.
>>>> It's not an issue for me so I have just set the service to 'false' in
>>>> the configuration.
>>>> The uploading was working fine with 4.5.1 just prior to upgrading.
>>>> Regards
>>>> Phil
>>>>
>>>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1039805b-50ed-45aa-8fc6-420026f557b2n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/1039805b-50ed-45aa-8fc6-420026f557b2n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xnd-qepeKp-7-JoPu3QohOtZDkM5AvDZLY8zxwX8pVOw%40mail.gmail.com.

Re: [weewx-user] Announcement: AerisWeather Acquired by Vaisala

[Doug Jenkins]

It will be interesting if they will keep the free API access for stations
using PWSWeather.com. Hopefully they do not go the same route as darksky
and wunderground.

On Thu, Jan 27, 2022 at 2:11 PM Colin Larsen  wrote:

> For all those using Aeris Weather
>
>
> We are writing the next chapter of our company history – together with
> Vaisala ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> We are writing the next chapter of our company history – together with
> Vaisala.
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ 
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>
>
> Announcement: AerisWeather acquired by Vaisala
>
> January 27th, 2022
>
> To our valued clients, partners & associates:
>
> We’re excited to share the news with you that AerisWeather has been
> acquired by Vaisala, in a transaction that was settled earlier today.
> Vaisala, a global leader in weather, environmental & industrial
> measurements will integrate AerisWeather into their surging data solutions
> business - elevating its market position as a leading global provider of
> environmental data & imagery solutions.
>
> You can read more about the acquisition in Vaisala’s official stock
> exchange release which can be found here
> <https://email.aerisweather.com/t/j-l-zilgz-ilsfllc-y/>.
>
> In Vaisala we have found a partner with a matching vision and high
> standard for success. While the entire AerisWeather team is proud of our
> accomplishments to date, we’re already looking ahead to accelerating our
> shared product roadmap to create the industry’s most compelling
> data-as-a-service solutions, including:
>
>- Proprietary global weather models, including Europe’s most accurate
>weather forecasts
>- Road & runway surface conditions
>- Renewable energy historical data and forecasts
>- Port, coastal and offshore maritime weather observations
>- Proprietary global lightning network
>
> Additionally, our customers will now have access to world-class
> environmental monitoring solutions.  From weather stations and lightning
> detection to air quality monitoring and wind lidar, we will have site-level
> solutions that are designed to perform in the most severe environments,
> protecting life and property.
>
> Finally, we’d like to thank our clients and partners who have supported us
> over the last five and a half years, both for their loyalty as well as
> their invaluable feedback on our technology platform. We can assure our
> clients that API & Mapping services will continue to function normally and
> there will be no disruption to our existing services.  If you have any
> questions, please reach out to your Account Executive directly or, visit
> www.aerisweather.com/vaisala-aerisweather-faqs
> <https://email.aerisweather.com/t/j-l-zilgz-ilsfllc-j/> to review our
> FAQ’s regarding today’s news.
>
> We look forward to working with you all as we strive to accurately &
> seamlessly measure, monitor and deliver environmental conditions across our
> every-changing planet.
>
> Thanks!
> The AerisWeather Team
> <https://email.aerisweather.com/t/j-l-zilgz-ilsfllc-t/>
> <https://email.aerisweather.com/t/j-l-zilgz-ilsfllc-i/>
> <https://email.aerisweather.com/t/j-l-zilgz-ilsfllc-d/>
>
> AerisWeather, a Vaisala Company
> <https://email.aerisweather.com/t/j-l-zilgz-ilsfllc-p/>
> 6569 City West Parkway
> Eden Prairie, MN 55344
>
>
>
> Unsubscribe <https://email.aerisweather.com/t/j-u-zilgz-ilsfllc-x/>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CACjxfUv4TUM%2BqGYF6jVSuWCdhn22_tmj4q97bCVq5siwx%3D8EoQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CACjxfUv4TUM%2BqGYF6jVSuWCdhn22_tmj4q97bCVq5siwx%3D8E

Re: [weewx-user] Re: windspeed extreme values

[Doug Jenkins]

Joachim:

Cleaning up bad data in your MySQL database can be done using a SQL editor.
I used DBeaver (dbeaver.io) which is a universal database manager. It will
connect to MySQL, SQLite, and MariaDB (which is what I use for WeeWX) and a
lot of other databases.

This is what i would do:

1. Download dbeaver from dbeaver.io and set it up on your workstation
2. in DBeaver, under Database, select new connection. Provide the host name
and port (I believe it is 3306) of the mySQL Server instance and login with
the same login that you are using with WeeWX.
3. Open a new SQL Script window by clicking on SQL Editor->New SQL Script.
Ensure you select the connection and database above.
4. Now using the Bad Data wiki, find the errant record by querying the
archive table in the database. The SQLite commands should work as both
databases are SQL99 compliant.
5. Before you delete any rows, dump the database to a file. you can do that
with DBeaver by clicking on the connection, navigate to the database, right
click on the database and select dump database. See screenshot for details.
6. delete the row by finding the dateTime value you want to remove and use
that in your WHERE Clause. You can use the keyword FROM_UNIXTIME to convert
the dateTime value to a real date. here is an example:
 select FROM_UNIXTIME(dateTime) , windGust from archive;

Let me know if that helps



On Thu, Jan 13, 2022 at 5:44 PM vince  wrote:

>
> When you picked mysql you essentially signed up for learning more on your
> own.
>
> See if https://www.mysqltutorial.org/mysql-update-data.aspx helps you any
> in figuring out the mysql command to do something similar to what the wiki
> sqlite3 example is doing.
>
> On Thursday, January 13, 2022 at 2:25:46 PM UTC-8 jputt...@gmail.com
> wrote:
>
>> I have tried the instruction "old 'bad' data" . But I use the
>> mysql-database. To convert the DB ( 1 million records) to a sqlite-DB was
>> not succesfull.
>> Furthermore run here 2 instances, so no weewx.conf or weewx db but with
>> other names ( ecowitt.conf with weewx_eco db etc).
>>
>> Joachim
>>
>> gjr80 schrieb am Donnerstag, 13. Januar 2022 um 11:31:40 UTC+1:
>>
>>> Hi,
>>>
>>> Have you worked through the Cleaning up old 'bad' data wiki page
>>> <https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data> with
>>> an emphasis on the field windSpeed? You most likely do not see the
>>> spikes on the Seasons year plots as the Seasons year plots plot a day
>>> average value, perhaps you are seeing the spikes on the Belchertown plots
>>> because they plot a different aggregate (or perhaps no aggregate at all).
>>>
>>> Gary
>>>
>>> On Thursday, 13 January 2022 at 19:44:56 UTC+10 jputt...@gmail.com
>>> wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> how can i delete the two peaks in the berlchertown year chart?
>>>> These peaks do not appear in the season year diagram.
>>>> [image: wind-belchertown.png][image: wind-season.png]
>>>> Joachim
>>>>
>>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/dd279948-9e2f-43d3-88ca-be017b753eecn%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/dd279948-9e2f-43d3-88ca-be017b753eecn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xuYk%2BdGbE%2B2wxidRgDbqCt987Sb4eXHs9hPso%3DSWooMA%40mail.gmail.com.

Re: [weewx-user] Reduce logging in the MQTT publisher

[Doug Jenkins]

FYI, I confirmed this setting to work with my station. I am running MQTT
logging every 18 seconds with Acurite.

On Fri, Dec 24, 2021 at 5:10 PM Tom Keffer  wrote:

> If the mqtt extension obeys the rules like other RESTful extensions, a
> simple
>
> [[MQTT]]
>   log_success = False
>
> should do it.
>
>
>
> On Fri, Dec 24, 2021 at 2:04 PM RonV42  wrote:
>
>> Hi,
>>
>> I just install MQTT publishing of my loop events on my Raspberry Pi.
>> Every time a MQTT write is done there are log entries every couple of
>> seconds which is bad for my SD card.
>>
>> Dec 24 15:23:43 pi1 weewx[9988] INFO weewx.restx: MQTT: Published record
>> 2021-12-24 15:23:41 CST (1640381021)
>> Dec 24 15:23:46 pi1 weewx[9988] INFO weewx.restx: MQTT: Published record
>> 2021-12-24 15:23:44 CST (1640381024)
>>
>> I have been looking in the documentation and I can't seem to find where I
>> can control the logging of the messages.   It looks like the native logging
>> of weewx and not part of the  extension of MQTT. I am using MQTT from this
>> project:
>>
>> https://github.com/weewx/weewx/wiki/mqtt
>>
>> Any thoughts?
>>
>> --
>> 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 view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/56b63004-9c7d-461d-bc02-cdcc85dfa315n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/56b63004-9c7d-461d-bc02-cdcc85dfa315n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEAjtWX6cD0vn6Jm9JmFXOreE9Av4m%2BEmYju_iMYihu_xg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEAjtWX6cD0vn6Jm9JmFXOreE9Av4m%2BEmYju_iMYihu_xg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0wRo%3DM-KpWAUAoFPkHGoL52zNP-%3Dv6QMXwvQhiBCe7ZeQ%40mail.gmail.com.

Re: [weewx-user] Re: AERIS Forecast (authentication change)

[Doug Jenkins]

Vince:

Thanks for the heads up! I figured I will be regenerating keys or dumping
this service all together! :)

I did figure this out. AERIS changed their login process, so you need to
create a AERISWeather account. I simply followed Pat O'Briens' link and
recreated my account.

Here are the steps:

1. Setup your weather station on PWSWeather.com. Make sure you obtain a API
key from the station page as that will be your new password in weewx.conf
for your station id.
2. go to https://www.aerisweather.com/signup/pws and login with your
PWSWeather.com email and password. They will send you a verification code
in your email.
3. Once verified, you will be prompted to create an AERISWeather.com
account. They login id is now your email address. I just created a new
account with my email and moved on.
4. Once you are in the dashboard, you create a "app". I used my base domain
as the namespace. It created a ID and secret. I added these into the
forecast api key and secret in the Belchertown skin settings in weewx.conf.

I just performed all of these steps and just pulled the forecast a minute
ago in my weewx weatherstation.



On Mon, Dec 20, 2021 at 2:49 PM vince  wrote:

> You might to generate a new key since you posted your keys here.
>
> If you have a link regarding them asking folks to reset their account
> (whatever that means), it would be nice to pass along.
>
> On Monday, December 20, 2021 at 11:29:00 AM UTC-8 do...@dougjenkins.com
> wrote:
>
>> I was wondering if anyone else is experiencing this issue with
>> Belchertown and AERIS forecast. I was receiving forecasts from AERIS up to
>> 12/15/2021 1:00PMEST. After that, I am getting this error in my weewx.log:
>>
>>  Error downloading forecast data. Check the URL in your configuration
>> and try again. You are trying to use URL:
>> https://api.aerisapi.com/forecasts/27.872488,-82.821730?&format=json&filter=day&limit=7&client_id=4bsPze5DiJpq7sEIRk60G&client_secret=cYZ4xZ2Uyj4WWRMbkrZbRiEsuWMn2co9hwyBHTTh,
>> and the error is: HTTP Error 401: Unauthorized
>>
>>  FULL SNIPPET OF LOG IS ATTACHED TO THIS MESSAGE  AERIS was
>> providing forecast data to accounts that were publishing data to
>> PWSWeather.com. I went to the AERIS website and they stated they have
>> changed their authentication recently and need everyone to reset their
>> account. I submitted a reset account request multiple times, but no
>> response. Anyone else experiencing this?
>>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f0c8ba71-5ca2-44f2-8e8c-22159b09a75en%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/f0c8ba71-5ca2-44f2-8e8c-22159b09a75en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0xTRz4kqZYjmBkQv1Y0XCtK-LgLp6mNbgzYfY3mSiZ9pQ%40mail.gmail.com.

[weewx-user] AERIS Forecast (authentication change)

[Doug Jenkins]

I was wondering if anyone else is experiencing this issue with Belchertown 
and AERIS forecast. I was receiving forecasts from AERIS up to 12/15/2021 
1:00PMEST. After that, I am getting this error in my weewx.log:

 Error downloading forecast data. Check the URL in your configuration 
and try again. You are trying to use URL: 
https://api.aerisapi.com/forecasts/27.872488,-82.821730?&format=json&filter=day&limit=7&client_id=4bsPze5DiJpq7sEIRk60G&client_secret=cYZ4xZ2Uyj4WWRMbkrZbRiEsuWMn2co9hwyBHTTh,
 
and the error is: HTTP Error 401: Unauthorized

 FULL SNIPPET OF LOG IS ATTACHED TO THIS MESSAGE  AERIS was 
providing forecast data to accounts that were publishing data to 
PWSWeather.com. I went to the AERIS website and they stated they have 
changed their authentication recently and need everyone to reset their 
account. I submitted a reset account request multiple times, but no 
response. Anyone else experiencing this?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1bcfe644-9112-43a9-9e54-206521e5d8c4n%40googlegroups.com.
Dec 20 14:05:23 7a8921452451 weewx[28] INFO weewx.restx: PWSWeather: Published 
record 2021-12-20 14:05:00 EST (1640027100)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 'weewx.cheetahgenerator.CheetahGenerator'
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
Error downloading forecast data. Check the URL in your configuration and try 
again. You are trying to use URL: 
https://api.aerisapi.com/forecasts/27.872488,-82.821730?&format=json&filter=day&limit=7&client_id=4bsPze5DiJpq7sEIRk60G&client_secret=cYZ4xZ2Uyj4WWRMbkrZbRiEsuWMn2co9hwyBHTTh,
 and the error is: HTTP Error 401: Unauthorized
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
Traceback (most recent call last):
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/home/weewx/bin/user/belchertown.py", line 1260, in get_extension_list
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   response = urlopen(req)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/usr/lib/python3.6/urllib/request.py", line 223, in urlopen
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   return opener.open(url, data, timeout)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/usr/lib/python3.6/urllib/request.py", line 532, in open
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   response = meth(req, response)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/usr/lib/python3.6/urllib/request.py", line 642, in http_response
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   'http', request, response, code, msg, hdrs)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/usr/lib/python3.6/urllib/request.py", line 570, in error
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   return self._call_chain(*args)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/usr/lib/python3.6/urllib/request.py", line 504, in _call_chain
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   result = func(*args)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/usr/lib/python3.6/urllib/request.py", line 650, in http_error_default
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   raise HTTPError(req.full_url, code, msg, hdrs, fp)
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
urllib.error.HTTPError: HTTP Error 401: Unauthorized
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
During handling of the above exception, another exception occurred:
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:   
Traceback (most recent call last):
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/home/weewx/bin/weewx/reportengine.py", line 196, in run
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
   obj.start()
Dec 20 14:05:23 7a8921452451 weewx[28] ERROR weewx.reportengine:    
 File "/home/weewx/bin/weewx/reportengine.py", line 281, in start
Dec 20 14:05:23 7a8921452451 weewx[28

Re: [weewx-user] Re: Belchertown Error - Any idea what is wrong?

[Doug Jenkins]

Rpi2 with the latest O/S version is probably not enough to run both
belchertown and weewx together. Especially if you have a lot of archive
records to generate the NOAA reports on the first go.

The RPI 4 is readily available and will be a good investment for a nominal
fee. It has at least 2GB (vs 512mb) of RAM and a 4 core processor instead
of the single core Broadcom chip that came on that pi.

The bus is a lot better for I/O and you will have a lot less of an issue
with SD card corruption with RPi4 than with RPi2.

Trust me, I started my weewx 3.x site 3 years ago in on a RPi 2 and
struggled with stability with the pi itself. Now I run on a RPi4 with a
portable SSD drive to store my data with no issues.

Just my $0.02



On Mon, Nov 8, 2021, 8:02 PM vince  wrote:

> I bet if you turn Belchertown off (temporarily) and enable just the
> Standard or Seasons skin that it'll work just fine.
>
> Sometimes you need to throw more compute at the problem.
>
> On Monday, November 8, 2021 at 4:40:00 PM UTC-8 bchap...@gmail.com wrote:
>
>> Raspberry Pi 2 with raspbian buster
>>
>> This runs in a cycle of approximately every 6 minutes.  Nothing else
>> running on this machine.
>>
>> On Monday, November 8, 2021 at 7:35:14 PM UTC-5 tke...@gmail.com wrote:
>>
>>> Yes, tell us what computer you are using. Also, the operating system and
>>> version.
>>>
>>> On Mon, Nov 8, 2021 at 4:32 PM vince  wrote:
>>>
 Your database is locked :-)

 Typically this is when you're trying to do too much too fast on a very
 slow box like a pi-zero or the like.

 On Monday, November 8, 2021 at 4:06:48 PM UTC-8 bchap...@gmail.com
 wrote:

> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Main loop
> exiting. Shutting engine down.
> Nov  8 18:53:35 raspberrypi weewx[5618] INFO weewx.engine: Shutting
> down StdReport thread
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR weewx.reportengine:
> Caught unrecoverable exception in generator
> 'user.belchertown.HighchartsJsonGenerator'
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   database is locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weedb/sqlite.py", line 30, in guarded_fn
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   return fn(*args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weedb/sqlite.py", line 219, in execute
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   return sqlite3.Cursor.execute(self,
> *args, **kwargs)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   sqlite3.OperationalError: database is
> locked
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: 
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   During handling of the above exception,
> another exception occurred:
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: 
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   Traceback (most recent call last):
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   obj.start()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   self.run()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/user/belchertown.py", line 1550, in run
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   start_ts = archive.firstGoodStamp()
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/manager.py", line 247, in firstGoodStamp
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   _row = self.getSql("SELECT
> MIN(dateTime) FROM %s" % self.table_name)
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine: File
> "/usr/share/weewx/weewx/manager.py", line 449, in getSql
> Nov  8 18:53:44 raspberrypi weewx[5618] ERROR
> weewx.reportengine:   _cursor.execute(sql, sqlargs)
> Nov  8 18:53

Re: [weewx-user] Re: No AQI on Belchertown Skin

[Doug Jenkins]

No problem Chris! The site looks great and operates well on my side of the
world :)

Pat did mention that to get the webcam working, there is a specific comment
and commit you need to get from his GitHub. I would just go to his github
and search for it. He has it working on his site now and probably will have
the code for his release general release.

Good luck and good reporting!

Doug

On Wed, Oct 27, 2021 at 12:18 PM 'super zee' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Thanks Doug!  Your code worked like a charm.  Here is the current site.  I
> will keep adding the code from Pat to incorporate the web cam.
>
> Tempe AZ Weather Conditions <https://qso.com/kj7gcm/wx/>
>
> Chris Z
> WG7B
>
>
> On Saturday, October 23, 2021 at 10:13:13 PM UTC-7 super zee wrote:
>
>> Thanks Clifford.  Let me try cp -r
>>
>> Chris
>>
>>
>> On Thursday, October 21, 2021 at 7:52:28 AM UTC-7 Clifford Snow wrote:
>>
>>> On Thu, Oct 21, 2021 at 7:08 AM 'super zee' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
>>>> Okay thanks Doug.  Let me try it.
>>>> If I want to backup copy my whole Belchertown folder, can I use cp
>>>> /etc/weewx/skins/Belchertown /etc/weewx/skins/Belchertown-old  ?
>>>>
>>>> Will the cp command copy a whole folder to back it up?  Or is it just
>>>> for files?
>>>>
>>>> I believe the copy command you want is cp -R
>>> /etc/weewx/skins/Belchertown /etc/weewx/skins/Belchertown-old
>>>
>>> The -R recursively copies all folders to the new location. See man cp
>>>
>>> Best,
>>> Clifford
>>> --
>>> @osm_washington
>>> www.snowandsnow.us
>>> OpenStreetMap: Maps with a human touch
>>>
>> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/85ffb56e-0d86-4a66-83e0-75c067ecf952n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/85ffb56e-0d86-4a66-83e0-75c067ecf952n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,

Doug Jenkins
Phone: 813.391.5686 | d...@dougjenkins.com | www.dougjenkins.com

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0y3GZsTSnxQRN%2BtfQqRTpJDi9DAV8QjGB_MXLRQdjP2aw%40mail.gmail.com.

Re: [weewx-user] Re: No AQI on Belchertown Skin

[Doug Jenkins]

Chris:

Yes.  Make sure you used the link from Pat's documentation 
(https://github.com/poblabs/weewx-belchertown/archive/master.zip) to 
download the latest commit from github.

Then backup your weewx.conf file and any files that you changed in the 
skins/Belchertown/* directory as these will be overwritten with this 
master.zip file.

Finally, you would run sudo wee_extension --install master.zip in the 
directory where you downloaded the file. This will replace your belchertown 
skin with the latest.

If this helps, here are the commands (on ubuntu)

# CODE START
cd ~
wget https://github.com/poblabs/weewx-belchertown/archive/master.zip
sudo wee_extension --install master.zip
sudo service weewx restart
# CODE END

Let me know if this helps!

On Wednesday, October 20, 2021 at 10:10:52 AM UTC-4 zman_...@yahoo.com 
wrote:

> Doug
> When it downloads the zip file, it downloads 
> weewx-belchertown.master.zip.  Is this the right file?   Do I just change 
> the command to sudo wee_extension -- install weewx-belchertown.master.zip?
>
> Chris 
>
>
> On Monday, October 18, 2021, 12:01:57 PM MST, 'C Z' via weewx-user <
> weewx...@googlegroups.com> wrote: 
>
>
> Thanks Doug.  Let me take a look at the new skin and try it out.  I saw it 
> on Pat O'Brien's web site but didn't know where to download it.  Looks like 
> he also added a web cam feature.  Very cool!
>
>
> Chris 
> On Sunday, October 17, 2021, 07:09:17 PM MST, Doug Jenkins <
> do...@dougjenkins.com> wrote: 
>
>
> Chris:
>
> 1. You need to be on the Belchertown 1.3b1 release of the skin in order to 
> get the latest AQI fixes that were applied this year. here is the 
> instructions how to do that:
>
>
> https://github.com/poblabs/weewx-belchertown#how-to-install-the-development-version
>
> 2. You can not chart the AQI data inside of Belchertown skin. the AQI data 
> is pulled when the skin queries AERIS during its forecast cycle. The data 
> is not stored in the weewx database, so the graphs will not work. I checked 
> my setup and I am not recording the AQI data in the archive table.
>
> 3. For ease, here is my AQI setup for belchertown. it is currently working:
>
> [[[Extras]]]
> 
> # For help refer to the docs at 
> https://github.com/poblabs/weewx-belchertown
> 
> #--- General Options ---
> # belchertown_debug = 0
> belchertown_locale = auto
> theme = light
> theme_toggle_enabled = 1
> logo_image = "
> https://www.largoweather.com/images/largoweather_logo_light.png";
> logo_image_dark = "
> https://www.largoweather.com/images/largoweather_logo_dark.png";
> site_title = Largo Weather
> station_observations = barometer, dewpoint, outHumidity, 
> rainWithRainRate, cloudbase, visibility, cloud_cover
> beaufort_categoty = 1
> manifest_name = largoweather.com
> manifest_short_name = LW
> aeris_map = 0
> # radar_html = ''   #  (default seems to center on your 
> lat/lon)
> # radar_html_dark = None
> radar_zoom = 10
> radar_marker = 1
> almanac_extras = 1
> highcharts_enabled = 1
> graph_page_show_all_button = 1
> graph_page_default_graphgroup = day
> highcharts_homepage_graphgroup = day
> highcharts_decimal = auto
> highcharts_thousands = auto
> #googleAnalyticsId = ""
> # pi_kiosk_bold = "false"
> # pi_theme = "auto"
> webpage_autorefresh = 30
> reload_hook_images = 1
> reload_images_radar = 300
> # reload_images_hook_asi = -1
> # reload_images_hook_af = -1
> # reload_images_hook_as = -1
> # reload_images_hook_ac = -1
> # show_last_updated_alert = 1
> # last_updated_alert_threshold = 1800
> 
> #--- Common Titles under Labels Section to Change ---
> home_page_header = "Current Station Weather Conditions"
> graphs_page_header = Weather Observation Graphs
> reports_page_header = NOAA Climate Reports
> records_page_header = Station Records
> about_page_header = About LargoWeather.com
> powered_by = Observations are powered by a  target="_blank">Acurite 6037 5n1 Weather Station
> footer_copyright_text = 2021 Largo Weather
> footer_disclaimer_text = Never make important decisions 

[weewx-user] Re: No AQI on Belchertown Skin

[Doug Jenkins]

Chris:

1. You need to be on the Belchertown 1.3b1 release of the skin in order to 
get the latest AQI fixes that were applied this year. here is the 
instructions how to do that:

https://github.com/poblabs/weewx-belchertown#how-to-install-the-development-version

2. You can not chart the AQI data inside of Belchertown skin. the AQI data 
is pulled when the skin queries AERIS during its forecast cycle. The data 
is not stored in the weewx database, so the graphs will not work. I checked 
my setup and I am not recording the AQI data in the archive table.

3. For ease, here is my AQI setup for belchertown. it is currently working:

[[[Extras]]]

# For help refer to the docs at 
https://github.com/poblabs/weewx-belchertown

#--- General Options ---
# belchertown_debug = 0
belchertown_locale = auto
theme = light
theme_toggle_enabled = 1
logo_image = 
"https://www.largoweather.com/images/largoweather_logo_light.png";
logo_image_dark = 
"https://www.largoweather.com/images/largoweather_logo_dark.png";
site_title = Largo Weather
station_observations = barometer, dewpoint, outHumidity, 
rainWithRainRate, cloudbase, visibility, cloud_cover
beaufort_categoty = 1
manifest_name = largoweather.com
manifest_short_name = LW
aeris_map = 0
# radar_html = ''   #  (default seems to center on your lat/lon)
# radar_html_dark = None
radar_zoom = 10
radar_marker = 1
almanac_extras = 1
highcharts_enabled = 1
graph_page_show_all_button = 1
graph_page_default_graphgroup = day
highcharts_homepage_graphgroup = day
highcharts_decimal = auto
highcharts_thousands = auto
#googleAnalyticsId = ""
# pi_kiosk_bold = "false"
# pi_theme = "auto"
webpage_autorefresh = 30
reload_hook_images = 1
reload_images_radar = 300
# reload_images_hook_asi = -1
# reload_images_hook_af = -1
# reload_images_hook_as = -1
# reload_images_hook_ac = -1
# show_last_updated_alert = 1
# last_updated_alert_threshold = 1800

#--- Common Titles under Labels Section to Change ---
home_page_header = "Current Station Weather Conditions"
graphs_page_header = Weather Observation Graphs
reports_page_header = NOAA Climate Reports
records_page_header = Station Records
about_page_header = About LargoWeather.com
powered_by = Observations are powered by a Acurite 6037 5n1 Weather Station
footer_copyright_text = 2021 Largo Weather
footer_disclaimer_text = Never make important decisions based 
on info from this website.

#--- MQTT Websockets (for Real Time Streaming) Options ---
mqtt_websockets_enabled = 1
mqtt_websockets_host = wxsocket.largoweather.com
mqtt_websockets_port = 443
mqtt_websockets_ssl = 1
mqtt_websockets_topic = weather/loop
disconnect_live_website_visitor = 180

#--- Forecast Options ---
forecast_enabled = 1
forecast_provider = aeris
forecast_api_id = xx
forecast_api_secret = 
forecast_units = us
forecast_lang = en
forecast_stale = 7200
forecast_aeris_use_metar = 1
forecast_interval_hours = 24
forecast_alert_enabled = 3
forecast_alert_limit = 5
forecast_show_daily_forecast_link = 1
forecast_daily_forecast_link = 
https://wx.aerisweather.com/local/us/fl/largo/forecast//MM/DD
aqi_enabled = 1
aqi_location_enabled = 1

On Sunday, October 17, 2021 at 1:02:42 AM UTC-4 zman_...@yahoo.com wrote:

> Can someone help me understand why the current AQI won't show up in the 
> Belchertown skin?  Here is what I have in my weewx.conf:
>
>
> forecast_enabled = 1
>   forecast_provider="aeris"
> forecast_api_id = "2XPqhckudySx8ukdCjsHz"
> forecast_api_secret = "zMGHGb4SlobEOm9QmTy73Zmd0g7xnhl2681vTd7x
>
> And here is what is in the graph.conf:
>
> [[Chart5]]
>   title = Air Quality Index
>   [[[aqiChart]]]
>
> Can someone enlighten me as to what I'm doing wrong?
>
> Thanks, 
>
> Chris 
>

-- 
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 view this discussion on the web visit 
https://groups.google.co

[weewx-user] Re: Belchertown skin issues displaying aqi and cloud cover

[Doug Jenkins]

Evan:

Try stopping the site and clearing the existing html files (especially the 
JSON files) and restart it. I remember running into the same problem and 
that did the trick.



On Thursday, October 14, 2021 at 9:51:24 AM UTC-4 Evan Kimberly wrote:

> Hi all,
>
> I just installed and set up the current version of the Belchertown skin 
> and am trying to display AQI and Cloud Cover. I have "aqi", "visibility", 
> and "cloud_cover" in my line for station observations. visibility displays 
> correctly and updates, showing a current value with proper units (eg, 
> "Visibility 10 miles". However, both aqi and cloud_cover output as
>
> "aqi Invalid Observation" and "cloud_cover Invalid Observation".
>
> I have Aeris set up and am seeing live forecasts on my page. I also have 
> use metar enabled.
>
> Additionally, I have aqi_enabled = 1 and aqi_location_enabled =1 and am 
> seeing neither of those displaying on the left side of the screen.
>
> I assume I could be having issues with AQI due to lack of observations, 
> but I'm surprised that I can't seem to get cloud cover to show.
>
> Any issues with this? Something I'm missing? Any help/insight would be 
> appreciated!
>
> Evan
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/113bc551-c4d2-409c-a392-c8e402f65eb7n%40googlegroups.com.

Re: [weewx-user] Weewx MySQL help

[Doug Jenkins]

Dave & Vince:

I believe WeeWX My SQL Client uses a TCP connection over port 3306 to 
connect to database. To understand the problem, here is what we know:

1. You are running WeeWX on a Raspberry pi. For this illustration, lets 
call it CLIENT
2. You are running MySQL on a Ubuntu 20.04 server. we will call that SERVER
3. you are able to ping SERVER from CLIENT.
4. You are able to login to SERVER via mysql command line from CLIENT.

if anyone of the statements above are incorrect, please update accordingly.

Here is what I would do:

1. in your weewx.conf, change mysql to the IP address of the server.
2. on the CLIENT, ensure you can login using a TCP network connection
mysql -u  -p --port=3306 --host= --protocol=TCP
3. if that does not work, try sudo on the line above.

One culprit is that your MySQL server is not setup to listen for clients 
outside of its server. this is the reason for my questions.

Please let us know if this helps.

On Friday, October 1, 2021 at 6:33:23 PM UTC-4 dave.sp...@gmail.com wrote:

> I have attached a copy of the syslog file and weewx.conf file. Hopefully 
> that will help decipher the issue that I am having with connecting to 
> MySQL. I have redacted the password in the mysql section. 
>
>  
>
> Litte bit more information: I am trying to make a MySQL connection. MySQL 
> is running on Ubuntu Server 20.04 LTS. This is also a brand new server as 
> my old server died during an upgrade
>
> No LSB modules are available.
>
> Distributor ID: Ubuntu
>
> Description:Ubuntu 20.04.3 LTS
>
> Release:20.04
>
> Codename:   focal
>
>  
>
> I am able to cli into the mysql using cli, mysql -u weewx -p. I have check 
> iptables -L and there are no rules for the firewall. I did check both the 
> MySQL server and the RPi and both have no firewall rules.
>
>  
>
> I have run weewx with MySQL connection in the past with no issues, but 
> that was on a much older system.
>
>  
>
> Thanks for any information that may help get a connection to MySQL server
>
>  
>
> Thanks
>
> Dave
>
>  
>
>  
>
> *From:* weewx...@googlegroups.com  *On Behalf 
> Of *vince
> *Sent:* Friday, October 1, 2021 3:27 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Weewx MySQL help
>
>  
>
> On Friday, October 1, 2021 at 2:23:56 PM UTC-7 dave.sp...@gmail.com wrote:
>
> Any other ideas?
>
>  
>
>  
>
> Not without seeing your weewx.conf file - see 
> https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem and 
> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>
>  
>
>  
>
> -- 
>
> 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.
>
> To view this discussion on the web vis  
> https://groups.google.com/d/msgid/weewx-user/ae72c99b-a72d-41bd-8b54-6933a96cd4b8n%40googlegroups.com
>  
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32827c5f-826e-44e2-b111-c9dc896d5873n%40googlegroups.com.

[weewx-user] Re: Belchertown new install

[Doug Jenkins]

what you want to do is disable seasons and leave just belchertown enabled. 
I would also clear out the target public_html directory and point your 
belchertown skin there.

In this example, I am disabling the seasons skin and writing the generated 
html to /home/weewx/public_html. Adjust your target html directory in both 
HTML_ROOT and in HTML_ROOT under [Belchertown]

# = START EXAMPLE =

# Options for 'StdReport'
[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /home/weewx/public_html

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Whether to log a successful operation
log_success = True

# Whether to log an unsuccessful operation
log_failure = True

# Each of the following subsections defines a report that will be run.
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

[[SeasonsReport]]
# The SeasonsReport uses the 'Seasons' skin, which contains the
# images, templates and plots for the report.
skin = Seasons
enable = False   

[[Belchertown]]
skin = Belchertown
HTML_ROOT = /home/weewx/public_html
enable = true

# = END EXAMPLE =

On Monday, September 27, 2021 at 4:44:39 AM UTC-4 kk44...@gmail.com wrote:

> May be, you want to add 'belchertown' at the end of the URL you enter into 
> the browser.
>
> zman_...@yahoo.com schrieb am Montag, 27. September 2021 um 07:58:31 
> UTC+2:
>
>> I am doing a brand new install of the Belchertown skin so here is a noob 
>> question for the group.  How do I actually get weewx to start using the 
>> Belchertown skin and start uploading it to my webhost?  Do I need to set 
>> enable = true in the weewx.conf file?
>>
>> It seems to still constantly upload the Seasons skin to my web host.  
>> Where is the switch to start using the new Belchertown skin?  
>>
>> Here is the weewx.conf file.
>>
>> [[Belchertown]]
>> skin = Belchertown
>> enable=true
>> HTML_ROOT = /var/www/html/weewx/belchertown
>>
>> Is this the old Seasons skin?  This is what it constantly uploads.  I'm 
>> not seeing Belchertown at all and I'm pulling my hair out trying to 
>> understand what is wrong.  
>>
>> Thanks for the help.
>> Chris 
>> [image: Capture.JPG]
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/73bedb22-061b-4d29-b869-4d8e10c06ff5n%40googlegroups.com.

[weewx-user] Re: Help with TrueNAS install, 'env: python: no such file or directory'

[Doug Jenkins]

Matt:

So I stand corrected :) 

I tried your suggestion in another TrueNAS FreeBSD 12.2 jail and it worked. 
I checked the final weewxd and wee_reports files in /home/weewx/bin and 
their shebangs were set to #!/usr/local/bin/python3 as you indicated. 

*Evan:  You may want to revise your install process to skip the symbolic 
link.*

for this procedure Matt, should there be an update to the setup 
documentation ( http://weewx.com/docs/setup.htm ) for those users that use 
FreeBSD? If there is a github repository for the setup documentation, I am 
willing to make the changes and send in a PR for you all to review. If 
there is another place where this procedure should go, please advise.

Just let me know if you need my assistance.

DDJ



On Thursday, September 23, 2021 at 9:39:37 AM UTC-4 matthew wall wrote:

> instead of doing the symlink, you should be able to do this:
>
> /usr/local/bin/python3 setup.py build
> /usr/local/bin/python3 setup.py install
>
> when you use setup.py to build and install, it modifies the shebang line 
> of each entry point to refer to whatever python you used to invoke it.  so 
> whatever ends up in /home/weewx (or wherever you installed weewx) has a 
> shebang bespoke to your system.
>
> the reason we have the 'env python' shebang is to make the weewx entry 
> points as generic as possible (in particular, not specific to how things 
> happen to be done on the latest linux release).  that lets you run weewx 
> directly from the source tree without modifying any python code just to use 
> a specific python interpreter.
>
> m
>
>
> On Wednesday, September 22, 2021 at 5:27:13 PM UTC-4 do...@dougjenkins.com 
> wrote:
>
>> 3. Grab weewx and decompress it in your home folder. In this example 
>> below, we are going to get WeeWX 4.5.1
>>
>> fetch https://weewx.com/downloads/weewx-4.5.1.tar.gz
>> tar xvfz weewx-4.5.1.tar.gz
>> cd weewx-4.5.1
>> ./setup.py build
>> ./setup.py install
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a3789c30-2061-4981-beae-336c2892ee5bn%40googlegroups.com.

[weewx-user] Re: Help with TrueNAS install, 'env: python: no such file or directory'

[Doug Jenkins]

Evan:

I got WeeWX to work in a TrueNAS jail today. I was able to set it up with 
the simulator driver and ran it from the command line (./bin/weewxd + 
./bin/wee_reports) with no issues. This setup assumes you are going to use 
the sqlite database as your datasource.  I will list the instructions below 
this note.

One thing I noticed on your original thread is that you need to do a 
symbolic link for python3 to python. so I ran this statement below after my 
package installation to ease my install:

ln -s /usr/local/bin/python3 /usr/local/bin/python.

Here is the steps I did to get this to work.

= WEEWX FREEBSD INSTALL INSTRUCTIONS =
1. Install these packages:

pkg install python3
pkg install py38-pip
pkg install py38-configobj
pkg install py38-pillow
pkg install py38-pyserial
pkg install py38-pyusb
pkg install py38-cheetah3
pkg install py38-sqlite3
pkg install py38-mysqlclient
pkg install py38-ephem

2. create symbolic link for python3 to python
ln -s /usr/local/bin/python3 /usr/local/bin/python

3. Grab weewx and decompress it in your home folder. In this example below, 
we are going to get WeeWX 4.5.1

fetch https://weewx.com/downloads/weewx-4.5.1.tar.gz
tar xvfz weewx-4.5.1.tar.gz
cd weewx-4.5.1
./setup.py build
./setup.py install

4. Follow the installation prompts to configure your weewx.conf file.

5. Test out your installation by running these commands in the /home/weewx 
directory:

./bin/weewxd
./bin/wee_reports

6. Validate you have a /home/weewx/archive/weewx.sdb file and html files 
located in /home/weewx/public_html directories.

= END FREEBSD WEEWX INSTALL INSTRUCTIONS =

let us know how you make out with this setup and if you need any more help.

DDJ
 

On Wednesday, September 22, 2021 at 10:48:33 AM UTC-4 Doug Jenkins wrote:

> Ok, that helps a bit. 
>
> I have created a jail on my TrueNAS (v12.0.U05) and I will try to get 
> WeeWX to work with a simulator first. My Jail will be based on FreeBSD 12.2
>
> The challenge is getting dependencies installed in Python. I was able to 
> get Python3 installed and configured by running the following statement in 
> my new jail:
>
> pkg install python3.
>
> I will take a look at this in the afternoon and see if I am successful. If 
> so, I will share the details.
>
> DDJ
>
> On Wednesday, September 22, 2021 at 10:26:40 AM UTC-4 Evan Kimberly wrote:
>
>> I tried writing a line in make.conf to point to python 3.8
>>
>> PYTHON_DEFAULT_VERSION='python3.8'
>>
>> No luck still getting it to run.
>>
>> As for hardware access, i plan on using interceptor. From what I've read 
>> on here, it sounds doable to run weewx in a jail on freebsd. I just need to 
>> get the thing installed first!
>>
>> On Wednesday, September 22, 2021 at 10:16:42 AM UTC-4 
>> do...@dougjenkins.com wrote:
>>
>>> Evan:
>>>
>>> In your jail you will need to install python3 and the packaging through 
>>> pkg first. You will need to find the FreeBSD equivalents of the required 
>>> packages as listed in the setup doc (  WeeWX: Installation using 
>>> setup.py <http://weewx.com/docs/setup.htm>) . 
>>>
>>> Keep in mind that jails usually do not have access to the direct 
>>> hardware, so USB/serial passthrough maybe tough.
>>>
>>> It may make sense to setup a VM of Debian Buster on TrueNAS than trying 
>>> to run this through a jail. WeeWx does not need a lot of resources, so a 
>>> small VM (2GB, 2 cores) could be sufficient.
>>>
>>> DDJ
>>>
>>>
>>>
>>> On Wednesday, September 22, 2021 at 9:50:04 AM UTC-4 Evan Kimberly wrote:
>>>
>>>> I just tried that and it is telling me python3 command not found.
>>>>
>>>> On Wednesday, September 22, 2021 at 12:40:37 AM UTC-4 vince wrote:
>>>>
>>>>> Try "python3 setup.py build" and see if that works any better.
>>>>>
>>>>> Basically your system does not have a default "python", which we see 
>>>>> in some operating systems.
>>>>>
>>>>> On Tuesday, September 21, 2021 at 9:17:37 PM UTC-7 Evan Kimberly wrote:
>>>>>
>>>>>> I am still learning my way around bsd and command line in general and 
>>>>>> am having difficulty getting this up and running. I was reading a 
>>>>>> separate 
>>>>>> thread in this group 'FreeBSD / TrueNAS Jail Install Help' and am 
>>>>>> now stuck.
>>>>>>
>>>>>> My current steps as follow:
>>>>>> Set up jail (In TrueNAS, 12.2-RELEASE-p9)
>>>>>> 

Re: [weewx-user] Re: 4.x logging format

[Doug Jenkins]

Tom:

Thanks for the hotfix! I do appreciate it such a quick turnaround on a 
small item like this! :)

I switched the logging.py file at /usr/share/weewx/weeutil/ directory and 
tested it with both wee_reports and the standard weewx service. In both 
cases, Weewx formatted the log using my formatter expression. I made some 
changes to the formatter in my weewx.conf to ensure it was responding to 
the changes. The log reported the changes as expected.

I did not test wee_database, wee_import, or wee_device, but they probably 
will utilize this logging.py change and passthrough the formatter as 
expected.

Please let me know if you need any additional testing for this file or a 
issue/PR logged for the item. 

Again thanks for the great solution and continuous development of weewx! 

DDJ

On Wednesday, September 22, 2021 at 12:16:41 PM UTC-4 tke...@gmail.com 
wrote:

> Hi, Doug
>
> I was able to replicate this. The problem is that ConfigObj, the utility 
> that we use to read the configuration files, is trying to interpolate your 
> 'format', rather than simply pass it on to the logging facility.
>
> Replace your version of logger.py with the attached. You should find it 
> in /usr/share/weewx/weeutil/logger.py
>
> Let me know if that helps.
>
> -tk
>
>
>
> On Wed, Sep 22, 2021 at 3:50 AM Doug Jenkins  
> wrote:
>
>> Good morning Tom:
>>
>> sorry about the late reply on this thread. I did try this on my setup. 
>> and I got the following error when it tried to report:
>>
>> #  FOR REFERENCE : weewx.conf logging setup =
>> # Do not modify this. It is used when installing and updating weewx.
>> version = 4.5.1
>>
>> [Logging]
>>   [[formatters]]
>>   [[[ddj]]]
>> format = '%(asctime)s [%(levelname)s] [%(threadName)s] [%(name)s 
>> : %(funcName)s] %(message)s'
>>   [[root]]
>> handlers = rotate,
>>   [[loggers]]
>> [[handlers]]
>>   [[[rotate]]]
>> level = INFO
>> formatter = ddj
>> class = logging.handlers.RotatingFileHandler
>> filename = /var/log/weewx/weewx.log
>> maxBytes = 100
>> backupCount = 10
>> # = END : weewx.conf logging setup =
>>
>>
>> # = ERROR message when I execute wee_reports. =
>> Using configuration file /etc/weewx/weewx.conf
>> Traceback (most recent call last):
>>
>>   File "/usr/share/weewx/wee_reports", line 103, in 
>> main()
>>   File "/usr/share/weewx/wee_reports", line 63, in main
>> weeutil.logger.setup('wee_reports', config_dict)
>>   File "/usr/share/weewx/weeutil/logger.py", line 178, in setup
>> log_config['Logging'].walk(_fix)
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 919, in walk
>> out[entry] = self[entry].walk(
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 919, in walk
>> out[entry] = self[entry].walk(
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 894, in walk
>> val = function(self, entry, **keywargs)
>>   File "/usr/share/weewx/weeutil/logger.py", line 164, in _fix
>> if isinstance(section[key], (list, tuple)):
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 557, in 
>> __getitem__
>> return self._interpolate(key, val)
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 549, in 
>> _interpolate
>> return engine.interpolate(key, value)
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 352, in 
>> interpolate
>> value = recursive_interpolate(key, value, self.section, {})
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 330, in 
>> recursive_interpolate
>> k, v, s = self._parse_match(match)
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 417, in 
>> _parse_match
>> value, section = self._fetch(key)
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 386, in _fetch
>> raise MissingInterpolationOption(key)
>> configobj.MissingInterpolationOption: missing option "asctime" in 
>> interpolation.
>>
>> #  END ERROR MESSAGE =
>>
>> any help is always appreciated!
>>
>> DDJ
>>
>> On Monday, September 6, 2021 at 8:43:21 AM UTC-4 tke...@gmail.com wrote:
>>
>>> It should be possible. Did you try it? What happened?
>>>
>>> On Sat, Sep 4, 2021 at 8:50 AM Doug Jenkins  
>>> wrote:
>>>
&g

[weewx-user] Re: Help with TrueNAS install, 'env: python: no such file or directory'

[Doug Jenkins]

Ok, that helps a bit. 

I have created a jail on my TrueNAS (v12.0.U05) and I will try to get WeeWX 
to work with a simulator first. My Jail will be based on FreeBSD 12.2

The challenge is getting dependencies installed in Python. I was able to 
get Python3 installed and configured by running the following statement in 
my new jail:

pkg install python3.

I will take a look at this in the afternoon and see if I am successful. If 
so, I will share the details.

DDJ

On Wednesday, September 22, 2021 at 10:26:40 AM UTC-4 Evan Kimberly wrote:

> I tried writing a line in make.conf to point to python 3.8
>
> PYTHON_DEFAULT_VERSION='python3.8'
>
> No luck still getting it to run.
>
> As for hardware access, i plan on using interceptor. From what I've read 
> on here, it sounds doable to run weewx in a jail on freebsd. I just need to 
> get the thing installed first!
>
> On Wednesday, September 22, 2021 at 10:16:42 AM UTC-4 
> do...@dougjenkins.com wrote:
>
>> Evan:
>>
>> In your jail you will need to install python3 and the packaging through 
>> pkg first. You will need to find the FreeBSD equivalents of the required 
>> packages as listed in the setup doc (  WeeWX: Installation using setup.py 
>> ) . 
>>
>> Keep in mind that jails usually do not have access to the direct 
>> hardware, so USB/serial passthrough maybe tough.
>>
>> It may make sense to setup a VM of Debian Buster on TrueNAS than trying 
>> to run this through a jail. WeeWx does not need a lot of resources, so a 
>> small VM (2GB, 2 cores) could be sufficient.
>>
>> DDJ
>>
>>
>>
>> On Wednesday, September 22, 2021 at 9:50:04 AM UTC-4 Evan Kimberly wrote:
>>
>>> I just tried that and it is telling me python3 command not found.
>>>
>>> On Wednesday, September 22, 2021 at 12:40:37 AM UTC-4 vince wrote:
>>>
 Try "python3 setup.py build" and see if that works any better.

 Basically your system does not have a default "python", which we see in 
 some operating systems.

 On Tuesday, September 21, 2021 at 9:17:37 PM UTC-7 Evan Kimberly wrote:

> I am still learning my way around bsd and command line in general and 
> am having difficulty getting this up and running. I was reading a 
> separate 
> thread in this group 'FreeBSD / TrueNAS Jail Install Help' and am now 
> stuck.
>
> My current steps as follow:
> Set up jail (In TrueNAS, 12.2-RELEASE-p9)
> pkg install python38
> pkg install py38-cheetah3
> pkg install py38-configobj
> pkg install py38-pillow
> pkg install py38-sqlite3
> pkg install py38-ephem
> fetch https://weewx.com/downloads/weewx-4.5.1.tar.gz
> tar xvfz weewx-4.5.1.tar.gz
> cd weewx-4.5.1
> ./setup.py build
>
> I get the title error at the last step. I am currently in the 
> directory that setup.py exists in. The thread I was following suggested 
> using python37, but I wasn't able to install those packages. When I run 
> pkg 
> search py37-(whatever) I don't get any results, so i changed up to 38.
>
> Any suggestions?
>


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e593b200-3834-4713-89e2-71ed350c7fd7n%40googlegroups.com.

[weewx-user] Re: Help with TrueNAS install, 'env: python: no such file or directory'

[Doug Jenkins]

Evan:

In your jail you will need to install python3 and the packaging through pkg 
first. You will need to find the FreeBSD equivalents of the required 
packages as listed in the setup doc (  WeeWX: Installation using setup.py 
) . 

Keep in mind that jails usually do not have access to the direct hardware, 
so USB/serial passthrough maybe tough.

It may make sense to setup a VM of Debian Buster on TrueNAS than trying to 
run this through a jail. WeeWx does not need a lot of resources, so a small 
VM (2GB, 2 cores) could be sufficient.

DDJ



On Wednesday, September 22, 2021 at 9:50:04 AM UTC-4 Evan Kimberly wrote:

> I just tried that and it is telling me python3 command not found.
>
> On Wednesday, September 22, 2021 at 12:40:37 AM UTC-4 vince wrote:
>
>> Try "python3 setup.py build" and see if that works any better.
>>
>> Basically your system does not have a default "python", which we see in 
>> some operating systems.
>>
>> On Tuesday, September 21, 2021 at 9:17:37 PM UTC-7 Evan Kimberly wrote:
>>
>>> I am still learning my way around bsd and command line in general and am 
>>> having difficulty getting this up and running. I was reading a separate 
>>> thread in this group 'FreeBSD / TrueNAS Jail Install Help' and am now 
>>> stuck.
>>>
>>> My current steps as follow:
>>> Set up jail (In TrueNAS, 12.2-RELEASE-p9)
>>> pkg install python38
>>> pkg install py38-cheetah3
>>> pkg install py38-configobj
>>> pkg install py38-pillow
>>> pkg install py38-sqlite3
>>> pkg install py38-ephem
>>> fetch https://weewx.com/downloads/weewx-4.5.1.tar.gz
>>> tar xvfz weewx-4.5.1.tar.gz
>>> cd weewx-4.5.1
>>> ./setup.py build
>>>
>>> I get the title error at the last step. I am currently in the directory 
>>> that setup.py exists in. The thread I was following suggested using 
>>> python37, but I wasn't able to install those packages. When I run pkg 
>>> search py37-(whatever) I don't get any results, so i changed up to 38.
>>>
>>> Any suggestions?
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/85a2da78-58cd-4c82-a978-affe6eb0b514n%40googlegroups.com.

[weewx-user] Re: Weewx inside of a Proxmox Linux Container (USB Passthru)

[Doug Jenkins]

I do not believe you can do a device passthrough in a proxmox container. 
Proxmox uses LXC containers which do not have the ability to pass a device 
through. 

By default, USB will not passthrough to VMs in proxmox, you need to assign 
the USB device or port in your VM configuration in order for the VM to use 
it.

I recommend the following steps which I was able to do with Proxmox v7 and 
a Acurite 6037 console (Chaney instruments):

1. Create a VM in Proxmox. For my setup, I used ubuntu 20.04.03
2. I went on the shell of the proxmox host and ran lsusb. I looked for my 
weather station (eg Acurite) and recorded the usb address.
3. Started the VM and installed the O/S.
4. Stopped the VM and went under options and added new USB hardware. In 
Proxmox I selected the same weather station address and set it to 
passthrough.
5. started the VM and entered in the VM shell lsusb. I verified that my 
station was available.


On Wednesday, September 15, 2021 at 5:19:34 AM UTC-4 
1.spee...@googlemail.com wrote:

> Hello,
>
> I would like to install weewx in an Ubuntu Linux container under Proxmox. 
> The installation worked. Now I would like to set up the driver for the 
> TE923 station.
> If I connect the station to a normal Linux PC, weewx can read out the 
> station. This is not yet possible with the Linux container. To do this, I 
> have to forward the USB device from the server to the container.
>
> But I have not yet understood how the driver can find the station via USB. 
> Which device do I have to forward to the container?
>
> Can someone explain to me how the driver finds the station under Linux?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b9867df7-2258-4528-a986-ecb9fd2002b2n%40googlegroups.com.

Re: [weewx-user] Re: 4.x logging format

[Doug Jenkins]

Not to bring up old issues but, I am trying to format my logs. I read the 
wiki attached to this thread and I have this configuration working in my 
weewx.conf:

# = LOGGING SETUP (Configured 09/04/2021) =
[Logging]]
  [[root]]
handlers = rotate,
  [[loggers]]
[[handlers]]
  [[[rotate]]]
level = INFO
formatter = standard
class = logging.handlers.RotatingFileHandler
filename = /mnt/sandisk_512_ssd/weewx/logs/weewx.log
maxBytes = 100
backupCount = 10
# = END LOGGING SETUP =

But I want to format the logging out using a custom formatter as such:
#  PROPOSED CHANGE TO MY WEEWX.CONF =
[Logging]
  [[formatters]]
[[[ddj]]]
  format = 
'%(asctime)s [%(levelname)s] [%(threadName)s] [%(name)s : %(funcName)s] 
%(message)s'
  [[root]]
handlers = rotate,
  [[loggers]]
[[handlers]]
  [[[rotate]]]
level = INFO
formatter = ddj
class = logging.handlers.RotatingFileHandler
filename = /mnt/sandisk_512_ssd/weewx/logs/weewx.log
maxBytes = 100
backupCount = 10
# = END LOGGING SETUP =


I am running Weewx 4.5.1 on a Raspberry Pi using Raspbian O/S (32bit) which 
is essentially Debian buster.

Is there a way to express a formatter in the weewx.conf file so the logging 
object will format the results for me?

On Friday, August 21, 2020 at 3:27:49 PM UTC-4 chri...@gmail.com wrote:

> Just like to say I updated to 4.x and just added
>  
> [Logging]
>   [[handlers]]
> [[[rotate]]]
>   filename = /tmp/weewx.log
>
> To the top section of my weewx.conf file (after version) and it is 
> WONDERFUL to finally have real log output from weewx.  It's beautiful! I 
> might cry for not having to stare at Console.app and hope for something.  :)
> Thank you all for your continued efforts. 
> On Sunday, May 3, 2020 at 4:54:13 AM UTC-7 tke...@gmail.com wrote:
>
>> I like your fix better. Added in commit 6348741 
>> 
>> . 
>>
>> I also made the rotating log handler the default for MacOS.
>>
>> One problem I've discovered: if you 'declare' a handler, then the logging 
>> facility goes ahead and instantiates it, whether or not you actually use 
>> it. That means the program crashes when it tries to create 
>> /var/log/weewx.log unless its run with sudo privileges.
>>
>> So, for non-Mac systems, I took the handler back out, and put 
>> instructions on how to declare it in the wiki documentation 
>> .
>>
>> -tk
>>
>>
>> On Sun, May 3, 2020 at 12:11 AM Graham Eddy  wrote:
>>
>>> woops! i missed your reference to replacement weeutil/logger.py…
>>> putting that in place, it works fine on macos.
>>> it achieves the two things i was after: logs entries in a file (a basic 
>>> function missing from weewx on macos for such a long time!), and allows 
>>> customising message formats
>>>
>>> i have two critiques about this fix:
>>>
>>>   (1) linux would want [syslog] handlers only but macos would want 
>>> [rotate] for default. easiest is to default correctly for one in the code 
>>> and override it in weewx.conf for the other (applied either by user or 
>>> installation script). if both enabled, harmless (if not duplicating entries 
>>> in one logfile on linux) but wasteful
>>>
>>>   (2) shim approach is per- logging handler class only. would be pretty 
>>> easy for python user to add another shim in user/extensions.py but… 
>>> alternatively, do the string->int conversions e.g. add after line 130 in 
>>> weeutil/logger.py “log_config['Logging'].walk(_fix)” something like:
>>>
>>> def _intify_string_leaf(section, key):
>>>
>>> if isinstance(section[key], str):
>>> # The value is a string...
>>> try:
>>> value = int(section[key])
>>> except ValueError:
>>> pass
>>> else:
>>> # ... looks like an int, so make it one
>>> section[key] = value
>>> log_config['Logging'].walk(_intify_string_leaf)
>>>
>>> (this works.) conversely, intifying all leaves could have unintended 
>>> consequences...
>>>
>>> thanks for all that! cheers
>>>
>>> On 3 May 2020, at 5:07 am, Tom Keffer  wrote:
>>>
>>> Try this version of weeutil/logger.py. It includes a shim that does the 
>>> proper type conversion before passing on arguments to 
>>> logging.handlers.RotatingFileHandler.
>>>
>>> To use should be as simple as adding this to weewx.conf (alas, NOT 
>>> TESTED):
>>>
>>> [Logging]
>>>   [[loggers]]
>>> [[[root]]]
>>>   handlers = syslog, rotate
>>>   [[handlers]]
>>> [[[rotate]]]
>>>   filename = /tmp/weewx.log
>>>
>>> By default, it logs to /var/log/weewx.log. Hence, the need to override 
>>> that option if you want to log to /tmp/weewx.log.
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsu

Re: [weewx-user] Fog detection?

[Doug Jenkins]

I wonder if you take cloud base and the humidity values to determine if you
have fog. If the cloud base is low and you have high humidity, then one
could speculate that fog is imminent.

Any meteorologists can weigh in?



On Tue, Aug 31, 2021, 4:19 PM Greg Troxel  wrote:

>
> František Slimařík  writes:
>
> > I got question for hardcore meteorologists here. Is it possible to
> detect
> > fog based on classic meassured values like temperature, humidity,
> preasure,
> > etc?
> > Logically I would say fog appears when dew point equals current
> > temeperature but I guess it will not be so easy. Fogs didn't appear here
> > this year in my locality so I am waiting for autumn to start with
> > observations.
>
> Good question, but my impression is that it is really difficult to
> measure humidity above 95%.   I more or less have the impression that
> fog happens when temp/dewpoint are about the same and the temperature
> falls.
>
> I think you need a fog sensor that actually measures impaired light
> transmission.  Surely there is a norm for measuring that already.   I
> need one too, right after I build a seismograph.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/rmilf4h2wq5.fsf%40s1.lexort.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0wLzFDsK5i6iaNZ_DNgpuh__TpTZbXAF4a4G6NDyobHog%40mail.gmail.com.

Re: [weewx-user] Skin with webcam?

[Doug Jenkins]

Don:

Sorry for the late reply. I checked your site and it appears to be up and
running with SSL on both the Belchertown skin as well as your MQTT broker.
I also see your live streams are working well too.

You have an interesting setup setting up a VPN to your synology NAS then
NGINX as your proxy to the Pi. I understand why you have the setup given
the Starlink dependency and using the Synology as the main ingress for your
setup.

anyways I hope my approach helped. Just reach out on the user group again
if you have any questions. There is a lot of great technical folks here
that can assist.

Doug Jenkins

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACC0i0yj3gLt%3DfOZaz5YUAqAeMc8XQWv-su%3DzjX_DzcnOCk_DQ%40mail.gmail.com.

[weewx-user] Re: problem with alarm.py on gmail

[Doug Jenkins]

So I made the adjustments to my alarm.py and gave it a go with my weather 
station reporting when the temperature is over 70f (which is everyday here 
in Sunny Florida!) In both cases using port 587 and 465 with my Google 
Workspace account (aka paid gmail for a domain), I received alerts from my 
machine. So it is most likely not a port problem.

So what I recommend is going on the terminal and checking to see if you can 
connect directly to smtp.gmail.com at ports 465 and 587 on the machine that 
is hosting your weewx instance:

telnet smtp.gmail.com 587

If it responds back with a 200, then type in HELO  and see if 
it responds back. 

If you get a connection refused, then you are having problems connecting to 
that server. I would diagnosis and research the problem on your end further 
(eg firewalls, gmail security setup, etc.)

Doug

On Friday, July 30, 2021 at 10:17:03 AM UTC-4 Doug Jenkins wrote:

> Matthias:
>
> I will give this a go on my weewx instance and see what the issue is. I 
> have a gmail account and have utilized this smtp library in the past with 
> other Python 3 solutions. I will let you know.
>
> Doug
>
> On Friday, July 30, 2021 at 10:08:05 AM UTC-4 rogu...@gmail.com wrote:
>
>> Thank you very much for your suggestions.
>> I tried port 587 in weewx.conf which did not work (both with username + @
>> gmail.com and without).
>>
>> Then I tried adding the port in the alarm.py with the following result 
>> (botth with/without @gmail.com in weewx.conf)
>> Jul 30 16:00:24 loxberry /weewxd: alarm: Alarm expression "outTemp > 
>> 24.0" evaluated True at 2021-07-30 16:00:00 CEST (1627653600)
>> Jul 30 16:00:24 loxberry /weewxd: alarm: unable to use SMTP_SSL 
>> connection.
>> Jul 30 16:00:24 loxberry /weewxd: alarm: unable to sound alarm. Reason: 
>> [Errno 111] Connection refused
>>
>>
>> code in alarm.py:
>> try:
>> # First try end-to-end encryption
>> s = smtplib.SMTP_SSL(self.smtp_host, timeout=self.timeout, 
>> port=587)
>> syslog.syslog(syslog.LOG_DEBUG, "alarm: using SMTP_SSL on 
>> port 587")
>>
>> do...@dougjenkins.com schrieb am Freitag, 30. Juli 2021 um 15:47:49 
>> UTC+2:
>>
>>> Matthias:
>>>
>>> Gmail requires a SSL Authenticated connection using TLS. It is 
>>> configured to look for traffic from port 587. 
>>>
>>> I looked at the alarm.py code on the master branch in github 
>>> (weewx/alarm.py 
>>> at master · weewx/weewx (github.com) 
>>> <https://github.com/weewx/weewx/blob/master/examples/alarm.py> and it 
>>> is already set appropriately for the smtplib package for SSL, but the port 
>>> is not expressively set, so it is defaulting to port 465 per the smtplib 
>>> package spec ( smtplib — SMTP protocol client — Python 3.9.6 
>>> documentation <https://docs.python.org/3/library/smtplib.html>)
>>>
>>> So I would do the following:
>>> 1. I would try Gary's suggestion in putting the port after the smtp_host 
>>> line. 
>>> 2. If that does not work, then I would modify the alarm.py code to 
>>> supply the port in this manner
>>>
>>>
>>> # Starting at line 168
>>> try:
>>>
>>> # First try end-to-end encryption
>>> s = smtplib.SMTP_SSL(self.smtp_host, timeout=self.timeout, port=587)
>>> syslog.syslog(syslog.LOG_DEBUG, "alarm: using SMTP_SSL on port 587")
>>>
>>> Please let me know if that helps.
>>>
>>> Doug
>>> On Friday, July 30, 2021 at 8:22:30 AM UTC-4 gjr80 wrote:
>>>
>>>> What about smtp_host = smtp.gmail.com:587 ? If you search the forums 
>>>> for ‘smtp.gmail’ you will find a few threads where folks have had gmail 
>>>> smtp issues plus a few suggestions for troubleshooting.
>>>>
>>>> Gary
>>>>
>>>> On Friday, 30 July 2021 at 22:14:19 UTC+10 rogu...@gmail.com wrote:
>>>>
>>>>> Hello all together,
>>>>>
>>>>> it seems I can't get the alarm.py running.
>>>>> I always get an error during authentication to google server:
>>>>> alarm: SMTP mailer refused message with error (535, b'5.7.8 Username 
>>>>> and Password not accepted. Learn more at\n5.7.8  
>>>>> https://support.google.com/mail/?p=BadCredentials j13sm1499223wms.24 
>>>>> - gsmtp')
>>>>>
>>>>> I am using the following config:
>>>>>
>>>>> [Alarm]
>>>>> expres

[weewx-user] Re: problem with alarm.py on gmail

[Doug Jenkins]

Matthias:

I will give this a go on my weewx instance and see what the issue is. I 
have a gmail account and have utilized this smtp library in the past with 
other Python 3 solutions. I will let you know.

Doug

On Friday, July 30, 2021 at 10:08:05 AM UTC-4 rogu...@gmail.com wrote:

> Thank you very much for your suggestions.
> I tried port 587 in weewx.conf which did not work (both with username + @
> gmail.com and without).
>
> Then I tried adding the port in the alarm.py with the following result 
> (botth with/without @gmail.com in weewx.conf)
> Jul 30 16:00:24 loxberry /weewxd: alarm: Alarm expression "outTemp > 24.0" 
> evaluated True at 2021-07-30 16:00:00 CEST (1627653600)
> Jul 30 16:00:24 loxberry /weewxd: alarm: unable to use SMTP_SSL connection.
> Jul 30 16:00:24 loxberry /weewxd: alarm: unable to sound alarm. Reason: 
> [Errno 111] Connection refused
>
>
> code in alarm.py:
> try:
> # First try end-to-end encryption
> s = smtplib.SMTP_SSL(self.smtp_host, timeout=self.timeout, 
> port=587)
> syslog.syslog(syslog.LOG_DEBUG, "alarm: using SMTP_SSL on port 
> 587")
>
> do...@dougjenkins.com schrieb am Freitag, 30. Juli 2021 um 15:47:49 UTC+2:
>
>> Matthias:
>>
>> Gmail requires a SSL Authenticated connection using TLS. It is configured 
>> to look for traffic from port 587. 
>>
>> I looked at the alarm.py code on the master branch in github (weewx/alarm.py 
>> at master · weewx/weewx (github.com) 
>>  and it is 
>> already set appropriately for the smtplib package for SSL, but the port is 
>> not expressively set, so it is defaulting to port 465 per the smtplib 
>> package spec ( smtplib — SMTP protocol client — Python 3.9.6 
>> documentation )
>>
>> So I would do the following:
>> 1. I would try Gary's suggestion in putting the port after the smtp_host 
>> line. 
>> 2. If that does not work, then I would modify the alarm.py code to supply 
>> the port in this manner
>>
>>
>> # Starting at line 168
>> try:
>>
>> # First try end-to-end encryption
>> s = smtplib.SMTP_SSL(self.smtp_host, timeout=self.timeout, port=587)
>> syslog.syslog(syslog.LOG_DEBUG, "alarm: using SMTP_SSL on port 587")
>>
>> Please let me know if that helps.
>>
>> Doug
>> On Friday, July 30, 2021 at 8:22:30 AM UTC-4 gjr80 wrote:
>>
>>> What about smtp_host = smtp.gmail.com:587 ? If you search the forums 
>>> for ‘smtp.gmail’ you will find a few threads where folks have had gmail 
>>> smtp issues plus a few suggestions for troubleshooting.
>>>
>>> Gary
>>>
>>> On Friday, 30 July 2021 at 22:14:19 UTC+10 rogu...@gmail.com wrote:
>>>
 Hello all together,

 it seems I can't get the alarm.py running.
 I always get an error during authentication to google server:
 alarm: SMTP mailer refused message with error (535, b'5.7.8 Username 
 and Password not accepted. Learn more at\n5.7.8  
 https://support.google.com/mail/?p=BadCredentials j13sm1499223wms.24 - 
 gsmtp')

 I am using the following config:

 [Alarm]
 expression = outTemp > 24.0
 time_wait = 1800
 smtp_host = smtp.gmail.com
 smtp_user = relaymtx
 smtp_password = mypassword
 from = weewx
 mailto = mymail
 subject = Alarm from weewx!
 count_treshold = 10

 I did several attempts in changing the smtp_user by adding @gmail.com 
 which results in the same error.
 Also tried adding port 465 to smtp.gmail.com:465 without success.
 IMAP access is activated in the gmail-account.
 So any help would be appreciated.

 Best regards,
 Matthias

>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b0da817b-6f76-461c-974d-e48e16d30333n%40googlegroups.com.

[weewx-user] Re: problem with alarm.py on gmail

[Doug Jenkins]

Matthias:

Gmail requires a SSL Authenticated connection using TLS. It is configured 
to look for traffic from port 587. 

I looked at the alarm.py code on the master branch in github (weewx/alarm.py 
at master · weewx/weewx (github.com) 
 and it is 
already set appropriately for the smtplib package for SSL, but the port is 
not expressively set, so it is defaulting to port 465 per the smtplib 
package spec ( smtplib — SMTP protocol client — Python 3.9.6 documentation 
)

So I would do the following:
1. I would try Gary's suggestion in putting the port after the smtp_host 
line. 
2. If that does not work, then I would modify the alarm.py code to supply 
the port in this manner


# Starting at line 168
try:

# First try end-to-end encryption
s = smtplib.SMTP_SSL(self.smtp_host, timeout=self.timeout, port=587)
syslog.syslog(syslog.LOG_DEBUG, "alarm: using SMTP_SSL on port 587")

Please let me know if that helps.

Doug
On Friday, July 30, 2021 at 8:22:30 AM UTC-4 gjr80 wrote:

> What about smtp_host = smtp.gmail.com:587 ? If you search the forums for 
> ‘smtp.gmail’ you will find a few threads where folks have had gmail smtp 
> issues plus a few suggestions for troubleshooting.
>
> Gary
>
> On Friday, 30 July 2021 at 22:14:19 UTC+10 rogu...@gmail.com wrote:
>
>> Hello all together,
>>
>> it seems I can't get the alarm.py running.
>> I always get an error during authentication to google server:
>> alarm: SMTP mailer refused message with error (535, b'5.7.8 Username and 
>> Password not accepted. Learn more at\n5.7.8  
>> https://support.google.com/mail/?p=BadCredentials j13sm1499223wms.24 - 
>> gsmtp')
>>
>> I am using the following config:
>>
>> [Alarm]
>> expression = outTemp > 24.0
>> time_wait = 1800
>> smtp_host = smtp.gmail.com
>> smtp_user = relaymtx
>> smtp_password = mypassword
>> from = weewx
>> mailto = mymail
>> subject = Alarm from weewx!
>> count_treshold = 10
>>
>> I did several attempts in changing the smtp_user by adding @gmail.com 
>> which results in the same error.
>> Also tried adding port 465 to smtp.gmail.com:465 without success.
>> IMAP access is activated in the gmail-account.
>> So any help would be appreciated.
>>
>> Best regards,
>> Matthias
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8adfd746-55bf-462b-a04d-808325d81c68n%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT Issues

[Doug Jenkins]

Matt:

for some reason I did not get the updates for this thread. I am glad the 
setup is now working for you! I checked your site and you do not have any 
javascript errors now :)


Vince : I agree, I will be more than happy to do a write up on how to 
configure this setup (with screenshots and all). I attached a word document 
to this thread a while back that listed what was needed in Cloudflare to 
offload SSL. I can do a formal write up with some commands and 
configuration from Pat O'Briens MQTT documentation. 

I can also post a message on Pat O'Briens discus chat on his weather site 
to see if he wants to add that as a post to his labs site (obrienlabs.net). 
That may help the majority of the skin users in setting this up on the 
first go.

Doug

On Monday, July 26, 2021 at 2:10:15 PM UTC-4 mattjo...@gmail.com wrote:

> Vince,
>
> I'd be happy to pull it all into one doc with some supporting notes so it 
> makes sense. This was a frustrating (at times) yet rewarding experience to 
> figure this all out and I know many others will want to achieve a similar 
> website and control of their data.
>
> Matt
>
> On Monday, July 26, 2021 at 12:27:51 PM UTC-4 vince wrote:
>
>> Given the long back+forth on this one, it would be really helpful if you 
>> could capture your entire setup someplace for the next person/victim who 
>> tries to do the same thing.  You have quite a lot of moving parts and it 
>> would be great to capture everything you did to set it up so it works both 
>> LAN and WAN.
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d6747cf7-bc8d-4bf9-a5a3-ed88e0c599aen%40googlegroups.com.

[weewx-user] Re: Trying to gee AS3935 to work with weewx 4.5.1

[Doug Jenkins]

Phil:

In looking at your weewx.conf, you may want to switch the process service 
to be before the comma. I think the error is because you are passing [None] 
as the first object in the process_services dictionary.

[Engine]
[[Services]]
process_services =  user.as3935.AS3935, 

After that, it maybe prudent to go through and covert the AS3935 code to 
python3 syntax.

Doug

On Tuesday, July 27, 2021 at 6:48:37 AM UTC-4 gjr80 wrote:

> > Think I will try weewx 3.9.2, as I think that was the last python2 
> version
>
> All WeeWX releases to date have been python 2 compatible, including any 
> 4.x releases. Python 4.0.0 and later are also python 3 compatible. It all 
> comes down to what dependencies you have installed and what version of 
> python WeeWX is run under.
>
> Gary
>
> On Tuesday, 27 July 2021 at 19:51:04 UTC+10 philip@gmail.com wrote:
>
>> Thanks Vince
>> Changed Line 233 to except Exception as e:
>> It then moved to Line 73 === no such module but sudo pip3 install 
>> RPi_AS3935 seems to have cured that (Installed ver 0.2.0 OK)
>> Now it stuck on Line 153 'object not callable. (address=addr, bus=bus)  
>> In weewx.conf I have
>> [AS3935]
>> address = 3
>> bus = 1
>> Pin 17
>> calibration = 6
>>
>> Think I will try weewx 3.9.2, as I think that was the last python2 
>> version , just to see if my lighnting sensor does work.
>> Phil
>>
>> On Monday, July 26, 2021 at 9:42:19 PM UTC+1 vince wrote:
>>
>>> See https://github.com/weewx/weewx/wiki/faq-python-error
>>>
>>> You have a variety of options:
>>>
>>>- find a later version of the driver/extension that supports python3
>>>- patch your copy to be python3 compliant using 2to3
>>>- use python2 for your installation
>>>
>>> In your particular case it looks like the second option is pretty 
>>> trivial.
>>>
>>> Change the offending line to be
>>>  except Exception as e:
>>>
>>> And see if that works ok...
>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/74dfb19b-4ba6-44a2-9bd0-c28672e73f56n%40googlegroups.com.

Re: [weewx-user] Belchertown MQTT Issues

[Doug Jenkins]

Matt:

I am looking into the issue now. I think you need to offload the SSL to 
Cloudflare with NGNIX Proxy. I am capturing screenshots of my setup to see 
if that will help you.

Doug Jenkins

On Saturday, July 24, 2021 at 12:33:22 PM UTC-4 mattjo...@gmail.com wrote:

> Doing more trouble shooting. I have narrowed it down to a SSL issue. 
>
> To confirm this I disabled SSL at cloudflare and disabled force SSL for 
> shakerweather.com with my NGINX reverse proxy server and ran with this 
> setup:
>
> *weewx.config*
> [[MQTT]]
> server_url = mqtt://usr:p...@mqtt.shakerweather.com:1883/
>
> topic = weather
> unit_system = US
> binding = archive, loop 
> aggregation = aggregate
>
> *skin.conf*
># MQTT Websockets defaults
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = "mqtt.shakerweather.com"
> mqtt_websockets_port = 9001
> mqtt_websockets_ssl = 0
> mqtt_websockets_topic = "weather/loop"
> disconnect_live_website_visitor = 180
>
> *mosquitto.conf*
> persistence false
>
> # mqtt
> listener 1883
> protocol mqtt
>
> # websockets
> listener 9001
> protocol websockets
>
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
>
>
> I am able to see the real time websocket updates internally and externally 
> at http://shakerweather.com (I'll leave it up for a short time so if it 
> doesn't work if you click on it that could be why)
>
> So at least I have narrowed down the issue. Still not sure how to resolve 
> to ensure all is secured with SSL
> On Saturday, July 24, 2021 at 10:23:03 AM UTC-4 Matt Johnson wrote:
>
>> Your setup seems similar to mine so I went for it. Still not working. 
>>
>> I went ahead and added a mqtt CNAME record to the shakerweather.com 
>> cloudflare setup. I also added mqtt.shakerweather.com to my NGINX Proxy 
>> Server to forward to port 9001 using the same SSL certificate I have for 
>> shakerweather.com that is forwarding to port 80 to serve the page.
>>
>> Cloudflare:
>> TYPE  NAME CONTENT
>> CNAME  mqttshakerweather.com
>> A shakerweather.com static wan IP
>>
>> *weewx.conf*
>> [[MQTT]]
>> server_url = mqtt://user:p...@10.0.0.30:1883/ 
>> <http://user:pw@10.0.0.30:1883/>
>>
>> topic = weather
>> unit_system = US
>> binding = archive, loop 
>> aggregation = aggregate
>>
>> *skin.conf*
>>  # MQTT Websockets defaults
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = "mqtt.shakerweather.com"
>> mqtt_websockets_port = 443
>>
>> mqtt_websockets_ssl = 1
>> mqtt_websockets_topic = "weather/loop"
>> disconnect_live_website_visitor = 180
>>
>> *mosquitto.conf*
>> persistence false
>>
>> # mqtt
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>>
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>>
>> acl_file /etc/mosquitto/acl
>> On Saturday, July 24, 2021 at 8:33:43 AM UTC-4 do...@dougjenkins.com 
>> wrote:
>>
>>> I had a number of struggles with this when I setup the Belchertown skin 
>>> on my Raspberry Pi hosting my weather site, www.largoweather.com. I 
>>> think the issue is that you need your mqtt_websockets_port to be set to 443 
>>> as the websocket traffic is getting filtered out by your firewall 
>>> (9001->8083)
>>>
>>> Here is what I did to get this to work on largoweather.com:
>>>
>>> 1. Setup Cloudflare to manage the DNS proxy on 2 domains: 
>>>- largoweather.com (A Record)
>>>- wx.largoweather.com (aka your mqtt.beldenserver.com) - CNAME 
>>> Record pointing the content to largoweather.com
>>>- Setup my SSL/TLS to Strict. I am using Cloudflare to offload my SSL 
>>> processing so essentially all traffic is coming in through 443.
>>>
>>>These are pointed to my public IP address which is dynamic. I use a 
>>> shell script to update cloudflare' content to keep my public IP current for 
>>> their system
>>>
>>> 2. NGNIX Proxy Manager : I use this program to manage my NGINX instance 
>>> that acts as a reverse proxy manager for my domains:
>>>  2.1 : Setup:
>>> - largoweather.com : Setup to point 

Re: [weewx-user] Belchertown MQTT Issues

[Doug Jenkins]

I had a number of struggles with this when I setup the Belchertown skin on 
my Raspberry Pi hosting my weather site, www.largoweather.com. I think the 
issue is that you need your mqtt_websockets_port to be set to 443 as the 
websocket traffic is getting filtered out by your firewall (9001->8083)

Here is what I did to get this to work on largoweather.com:

1. Setup Cloudflare to manage the DNS proxy on 2 domains: 
   - largoweather.com (A Record)
   - wx.largoweather.com (aka your mqtt.beldenserver.com) - CNAME Record 
pointing the content to largoweather.com
   - Setup my SSL/TLS to Strict. I am using Cloudflare to offload my SSL 
processing so essentially all traffic is coming in through 443.
   
   These are pointed to my public IP address which is dynamic. I use a 
shell script to update cloudflare' content to keep my public IP current for 
their system

2. NGNIX Proxy Manager : I use this program to manage my NGINX instance 
that acts as a reverse proxy manager for my domains:
 2.1 : Setup:
- largoweather.com : Setup to point to my local server ip 
address. The scheme is http. I use the program's lets encrypt function to 
get a SSL certificate and force SSL traffic to my final weewx website.
 - wx.largoweather.com : This handles my sockets setup. I 
forward all traffic to port 9001 and use the same ssl certificate issued 
for largoweather. I force SSL on this setup as well.

3. mosquitto configuration : I setup mosquitto on the same server as my 
weewx install since everything is running on the pi. here is my 
mosquitto.conf:
   pid_file /var/run/mosquitto.pid
   persistence true
   persistence_location /var/lib/mosquitto/
   log_type error
   websockets_log_level 1023
   connection_messages true
   log_dest file /mnt/*/weewx/logs/mosquitto.log
   
   allow_anonymous true
   password_file /etc/mosquitto/passwd
   acl_file /etc/mosquitto/acl

   listener 9001
   protocol websockets

   listener 1883
   protocol mqtt
   log_type error


4. weewx/Belchertown configuration: Here I setup my MQTT to talk to my 
local IP address on port 1883. Remember the traffic is all coming in on 
port 443, so that is the port I need Belchertown skin to essentially 
connect to resolve the web sockets requests.
   
[[MQTT]]
server_url = mqtt://joeuser:xxx@:1883/
topic = weather
unit_system = US
binding = archive, loop
aggregation = aggregate
[[Belchertown]]
 skin = Belchertown
 enable = True

 [[[Extras]]]
 site_title = Largo Weather 
 mqtt_websockets_enabled = 1
 mqtt_websockets_host = wxsocket.largoweather.com
 mqtt_websockets_port = 443
 mqtt_websockets_topic = weather/loop
 mqtt_websockets_ssl = 1
 disconnect_live_website_visitor = 180

I hope this helps!

Doug Jenkins


On Saturday, July 24, 2021 at 8:07:23 AM UTC-4 mattjo...@gmail.com wrote:

> Thanks Les. I think you have helped clear some things up. For the sake of 
> clarity and getting to the end state I desire and your suggestion let's 
> focus on locally hosting (my first setup) over the cloud broker. I have a 
> robust homelab and really like to keep things in house.
>
> *think the first configuration, with the local mqtt broker  isn’t going to 
> work because mqtt_websockets_host is set to localhost, which will only 
> resolve to the weewx/mqtt server when the web browser is running on that 
> server.  You need to set something here that will resolve to the weewx/mqtt 
> server from any client that you want to get realtime updates.  *
>
> This makes sense. I initially was on this path and changed the 
> mqtt_websockets host to the ip address of the weewx/mqtt server. This did 
> not work for other clients on the LAN which seemed strange given how I have 
> lots of locally running services on a few different servers in my home lab 
> and I access them all via device IP and port, with a few that are 
> accessible externally via reverse proxy. 
>
>
> *You need a DNS name that will resolve to your firewall and get 
> port-forwarded (for port 8083) to the weewx/mqtt server, 
> for mqtt_websockets_host. That should enable external access.  *
>
> I can use my mqtt.beldenserver.com DNS name I have setup at cloudflare 
> for this. I am running OPNSense for my firewall so I should be able to do 
> anything. Right now I have a firewall rule setup to send port 80/443 
> traffic to my NGINX Reverse Proxy where I have several DNS addresses 
> pointing to different services on different servers. One of these takes 
> shakerweather.com through 80/443 and through the reverse proxy and points 
> to the weewx/mqtt ser

[weewx-user] Re: Settings to change after IP address of Vantage changes

[Doug Jenkins]

Have you tried to put the the new IP address in the [MQTT] section of the 
weewx.conf file? I see this error which leads me to believe your DNS is 
still pointed to the old IP address of your former network

Jul  7 11:04:16 raspberrypi weewxd: restx: MQTT: Failed upload attempt 1: 
[Errno -3] Temporary failure in name resolution

On Wednesday, July 7, 2021 at 8:06:52 AM UTC-4 david_h wrote:

> Hi - I recently changed my home network set up, which meant the IP address 
> of my Davis Vantage Pro 2 changed.  I am using an IPlogger. I changed the 
> setting of "host" in weewx.conf to the new IP address, but my system 
> doesn't seem to be working.  Have I missed some other setting that I need 
> to change.  I use the Belchertown skin (with a MQTT broker on a remote 
> server), but can't see anything in the skin configuration file that 
> references the IP address. Am I missing something.  The log file is shown 
> below.  Any help in solving this would be much appreciated.
>
> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: 
> Driver 
> vers  
>   
> 
>  ion is 3.2.2
>
> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: 
> Option 
> loop  
>   
> 
>  _request=1
>
> Jul  7 11:03:26 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: 
> Opened up 
> e 
>
>   
>thernet 
> host 192.168.0.28 on port 2. timeout=4.0, tcp_send_delay=0.5
>
> Jul  7 11:03:26 raspberrypi kernel: [ 1818.633379] [UFW BLOCK] IN=eth0 
> OUT= 
> MAC=  
>   
>   
>01:00:5e:00:00:fb:90:21:06:46:88:f9:08:00:46:c0:00:20:00:00:40:00 
> SRC=10.0.1.200
>   
>
>  
> DST=224.0.0.251 
> LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2
>
> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: 
> ip-read err   
>   
>   
>   or: 
> timed out
>
> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: LOOP 
> try 
> #4
>   
>   
>  ; error: timed out
>
> Jul  7 11:03:26 raspberrypi weewx[1128] ERROR weewx.drivers.vantage: LOOP 
> max 
> tr
> 
>   
>ies 
> (4) exceeded.
>
> Jul  7 11:03:26 raspberrypi weewx[1128] INFO weewx.engine: Main loop 
> exiting. Sh 
>   
>   
> utting 
> engine down.
>
> Jul  7 11:03:27 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: Rude 
> wake 
> u 
>   
>   
>
>  p of console successful
>
> Jul  7 11:03:28 raspberrypi weewx[1716] DEBUG weewx.drivers.vantage: 
> Hardware 
> ty
>
>   
> pe 
> is 16
>
> Jul  7 11:03:29 raspberrypi weewx[1509]

Re: [weewx-user] wee_reports picks up extensions.py delay

[Doug Jenkins]

One thing you can do with the Raspberry Pi is to add a RealTimeClock (RTC) 
board. I use the RasClock 4.0 RTC for my Raspberry Pi to retain the system 
clock. This solves any time variances on my WeeWx data verses the system 
clock

On Wednesday, June 30, 2021 at 10:55:55 AM UTC-4 WindnFog wrote:

> That did the trick:
>
>
> Right after reboot:
>
>
> Weewx uptime: 0 days, 0 hours, 1 minute
>
> Server uptime: 0 days, 0 hours, 0 minutes
>
>
> After the script ran (I wrote it exactly as you suggested):
>
>
> Weewx uptime: 0 days, 0 hours, 4 minutes
>
> Server uptime: 0 days, 0 hours, 10 minutes
>
>
> - Paul VE1DX
>
>
> On 2021-06-29 6:35 p.m., vince wrote:
>
> On Tuesday, June 29, 2021 at 12:48:09 PM UTC-7 WindnFog wrote:
>
>> It's nitpicking, but if I reboot my Pi, the server uptime is always 
>> shorter than the weewx uptime.  I get things like:
>>
>> Weewx uptime:10 days, 1 hour, 38 minutes
>> Server uptime: 10 days, 1 hour, 36 minutes
>>
>
> It does seem like nitpicking perhaps.
> Is it really 'that' important to spend all this time worrying it ?
>
> I did a trial on my pi4 with the simulator and see the same thing.  The 
> weewx uptime is a minute more than the server uptime.  I'm guessing it has 
> something to do with the order the threads get their brains straight but I 
> didn't do much digging around.   If you want to look at the code, check out 
> bin/weewx/station.py
>
> If it bothers you that much, you could add a cron job that resets weewx a 
> few minutes after reboot.
> ref: https://www.tomshardware.com/how-to/run-script-at-boot-raspberry-pi
>
> Perhaps a simple bash script ala "sleep 300 && systemctl restart weewx" or 
> the like (untested).
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/kMMYGq5gC6E/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/b8bc0592-65ac-4e9c-a7dc-2dedce87882cn%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3342f952-1860-460e-a7b8-bbebb7fbn%40googlegroups.com.