Re: [weewx-user] Re: Datenbank zusammen legen.

[Günther Wrana]

Ich habe die weewx.conf aus meiner Datensicherung neu eingespielt nun kommt 
diese Meldung.
Soll ich das ganze neu installieren oder was ist nun defekt?

Feb 27 05:53:21 raspberrypi weewx[19161]: engine: pid file is 
/var/run/weewx.pid
Feb 27 05:53:21 raspberrypi weewx[19173]: engine: Using configuration file 
/home/weewx/weewx.conf
Feb 27 05:53:21 raspberrypi weewx[19173]: engine: Loading station type 
WH23xx (user.wh23xx)
Feb 27 05:53:21 raspberrypi weewx[19150]: Starting weewx weather system: 
weewx.
Feb 27 05:53:21 raspberrypi systemd[1]: Started LSB: weewx weather system.
Feb 27 05:53:21 raspberrypi weewx[19173]: engine: Caught unrecoverable 
exception in engine:
Feb 27 05:53:21 raspberrypi weewx[19173]:   bad marshal data 
(unknown type code)
Feb 27 05:53:21 raspberrypi weewx[19173]:   Traceback (most recent 
call last):
Feb 27 05:53:21 raspberrypi weewx[19173]: File 
"/home/weewx/bin/weewx/engine.py", line 888, in main
Feb 27 05:53:21 raspberrypi weewx[19173]: File 
"/home/weewx/bin/weewx/engine.py", line 72, in __init__
Feb 27 05:53:28 raspberrypi dhcpcd[389]: wlan0: Router Advertisement from 
fe80::9ada:c4ff:feb9:eeda
Feb 27 05:53:28 raspberrypi dhcpcd[389]: wlan0: soliciting a DHCPv6 lease
Feb 27 05:53:28 raspberrypi dhcpcd[389]: wlan0: dropping DHCPv6 due to no 
valid routers
Feb 27 05:53:32 raspberrypi dhcpcd[389]: wlan0: Router Advertisement from 
fe80::9ada:c4ff:feb9:eeda
Feb 27 05:53:32 raspberrypi dhcpcd[389]: wlan0: soliciting a DHCPv6 lease
Feb 27 05:53:32 raspberrypi dhcpcd[389]: wlan0: dropping DHCPv6 due to no 
valid routers
Feb 27 05:53:36 raspberrypi dhcpcd[389]: wlan0: Router Advertisement from 
fe80::9ada:c4ff:feb9:eeda
Feb 27 05:53:37 raspberrypi dhcpcd[389]: wlan0: soliciting a DHCPv6 lease
Feb 27 05:53:37 raspberrypi dhcpcd[389]: wlan0: dropping DHCPv6 due to no 
valid routers

-- 
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/eeefe49e-0bd6-4db3-9283-98a1f17e64c6%40googlegroups.com.

[weewx-user] Re: wxnow.txt does not contain precipitation totals

[Bill Arthur]

Gary,

Almost 24 hours later  cwxn 0.5a is chugging along. It's outputting 
wxnow.txt every five minutes. I'm good with that.
Maybe cwxn binding is actually set for archive but it's just not displaying 
properly in the log. Output at exactly five minutes makes me think it is.

Now we just need some rain.

Bill

On Wednesday, February 26, 2020 at 12:15:44 AM UTC-6, Bill Arthur wrote:
>
>
> Instead of spinning my wheels over binding=archive, I updated cwxn.py.  It 
> seems to be working fine. Syslog reports version 0.5a and "binding is 
> loop"  Wxnow.txt is updating and new data is making it to findu
>
>
>
>
>
>
> On Tuesday, February 25, 2020 at 10:50:30 PM UTC-6, Bill Arthur wrote:
>>
>>
>>
>> One more thing...
>> The original problem was that when I had added binding=archive my output 
>> was static for a day. Now, I have binding=archive in weewx.conf and my 
>> output is updating regularly.. But we seem to have a different problem now, 
>> with binding=archive not showing up in the syslog.
>>
>>
>>
>> On Tuesday, February 25, 2020 at 10:20:13 PM UTC-6, Bill Arthur wrote:
>>>
>>> I've configured it (after stopping) with binding=archive in 
>>> /etc/weewx/weewx.conf.. saved. viewed to confirm. restarted. syslog says 
>>> binding=loop. rebooted. same results. 
>>> stopped weewx. deleted line.saved. viewed to confirm. restarted. read 
>>> syslog. syslog says binding=loop. stopped. set binding=archive. saved. 
>>> viewed to confirm. restarted. syslog says binding=loop.. rebooted. read 
>>> syslog. no change.
>>>
>>>
>>> I don't believe it has any effect, but i should tell you that I am not 
>>> directly connected to the RasPi, I've working through VNC.
>>>
>>> On Tuesday, February 25, 2020 at 10:01:57 PM UTC-6, Bill Arthur wrote:

 Gary,

 I saved and restarted, then I rebooted. I've confirmed correct 
 /etc/weewx/weewx.conf location listed in the /var/log/syslog file. I'm not 
 aware of any other weewx.conf file

 I've set it back and I'm trying it again. Will advise

 On Tuesday, February 25, 2020 at 9:28:41 PM UTC-6, gjr80 wrote:
>
> Some obvious things. You did save weewx.conf? You did restart Weewx? 
> Is there more than one weewx.conf on your system and are you editing the 
> right one(it happens). When you start Weewx look at the log during WeeWX 
> startup and it will tell you the full path to weewx.conf, that is the 
> file 
> you need to edit.
>
> Gary
>


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/66972a74-c387-4e87-9c6f-352270d478c1%40googlegroups.com.

Re: [weewx-user] Re: Datenbank zusammen legen.

[gjr80]

Vielleicht Zeile neun in weewx.conf?

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1f417c31-32d8-4465-bb91-3519444b86de%40googlegroups.com.

Re: [weewx-user] Re: Raspberry/MQTT > VPS Server

[Greg Troxel]

Gert Andersen  writes:

> One more question. Should I just Mosquitto on vps-host(no weewx) and 
> uploading the weewx reports?

on vps-host, you should run the mosquitto daemon.

on the weewx computer, there is no need for a broker*.



* One can run multiple brokers and bridge  them, but I do not recommend
  that to anyone who is having the slightest amount of trouble!
  

-- 
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/rmilfopcdj0.fsf%40s1.lexort.com.

[weewx-user] Re: Raspberry/MQTT > VPS Server

[Gert Andersen]

Hi

One more question. Should I just Mosquitto on vps-host(no weewx) and 
uploading the weewx reports?

Gert

On Wednesday, February 26, 2020 at 9:56:02 AM UTC+1, Gert Andersen wrote:
>
> Hi there
> Is this scenario possible.
>
> Currently I have an Ecowitt GW1000 which sends data to a VPS Server every 
> 16 seconds with Weewx Interceptor, MQTT and Belchertowner installed on the 
> VPS Server. This works fine.
>
> I also have a Davis Vantage Pro2, which is connected to a Meetobridge via 
> Davis USB logger. This also works fine.
>
> Here's my new scenario:
> Davis USB logger connected to rpi/weewx. On rpi/weewx I want to install 
> mqtt with the following content:
>
> [[MQTT]]
> server_url = mqtt: // user: password @ vps_host_name: 1883 /
> topic = weather
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True
>
> On  I have installed Mosquitto which works fine with upload 
> via Interceptor. I want this to be able to upload every 2 seconds.
>
> I have not yet connected Davis to the rpi / weewx. but tried the 
> configuration with Simulator and the above MQTT configuration. Belchertown 
> on  connects fine to MQTT, but is awaiting data. Is it 
> because Simulator does not send data via MQTT or because my configuration 
> is wrong.
>
> Gert
>

-- 
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/fb92f36d-ed50-4842-b039-b4f260c7c492%40googlegroups.com.

[weewx-user] Re: Raspberry/MQTT > VPS Server

[Gert Andersen]

Hi

Thanks, now I have a starting point.

Gert

On Wednesday, February 26, 2020 at 9:56:02 AM UTC+1, Gert Andersen wrote:
>
> Hi there
> Is this scenario possible.
>
> Currently I have an Ecowitt GW1000 which sends data to a VPS Server every 
> 16 seconds with Weewx Interceptor, MQTT and Belchertowner installed on the 
> VPS Server. This works fine.
>
> I also have a Davis Vantage Pro2, which is connected to a Meetobridge via 
> Davis USB logger. This also works fine.
>
> Here's my new scenario:
> Davis USB logger connected to rpi/weewx. On rpi/weewx I want to install 
> mqtt with the following content:
>
> [[MQTT]]
> server_url = mqtt: // user: password @ vps_host_name: 1883 /
> topic = weather
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True
>
> On  I have installed Mosquitto which works fine with upload 
> via Interceptor. I want this to be able to upload every 2 seconds.
>
> I have not yet connected Davis to the rpi / weewx. but tried the 
> configuration with Simulator and the above MQTT configuration. Belchertown 
> on  connects fine to MQTT, but is awaiting data. Is it 
> because Simulator does not send data via MQTT or because my configuration 
> is wrong.
>
> Gert
>

-- 
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/8da259f5-c933-475a-be67-7b6e01b2f7ff%40googlegroups.com.

Re: [weewx-user] Raspberry/MQTT > VPS Server

[Greg Troxel]

Gert Andersen  writes:

> @Pat, i don't know there are spaces, The mqtt configuration is working fine 
> with Ecowitt GW1000 uploading data to the VPS server using Interceptor.I'll 
> ty the configuration you mention with uploading via ftp. Will I not miss 
> the real-time data every 2 seconds?

The spaces look bizarre in the url.  try dropping them.

> @Greg, seems you're running the system I'm looking after. Is it possible to 
> provide .conf for the weewx and the mqtt broker. Is far as I can see, the 
> only difference is you're running the system on your lan and I'm running 
> the weewx/Davis on the lan and the mqtt broker on cloud.

I can't send the exact mosquitto config since it has a bunch of acls
etc, and it ends up being huge and too hard to sanitize.

In weewx, I have the following, which is pretty much like what you have
except:

 - it lacks the spurious spaces [this could be a huge issue]
 - I am not sending loop
 - I use TLS
 - I fix the pressure units from FF to SI
 - I round dewpoints to 1 decimal (don't remember why clearly but surely they
   are being computed and not rounded from temp/%humidity)


[[MQTT]]
server_url = 
mqtt://user:passw...@fully.qualified.domain.example.com:8883/
topic = weather/someplace
aggregation = aggregate
retain = True
[[[tls]]]
ca_certs = /etc/openssl/certs/ca-certificates.crt
[[[inputs]]]
barometer
name = barometer_hPa
units = hPa
altimeter
name = altimeter_hPa
units = hPa
pressure
name = pressure_hPa
units = hPa
dewpoint
format = %.1f
inDewpoint
format = %.1f


You should be aware that with mosquitto, if a write to a topic is not
permitted by acls, it just doesn't happen, and it's hard to debug.

To debug this, you should break it into pieces.

On your VPS, use mosquitto_pub and mosquitto_sub to publish and receive
someting (junk text is fine) to the topic you want to use, using hte
credentials you will use to publish and subscribe.  Get that working;
it's all about mosquitto and not about weewx at all.  Read the docs
about acls.  Crank up debug levels if it doesn't work.

>From the RPI, use telnet to the server and port 1883 (using the same
name you put int he config).  Use both the -4 and -6 options if you have
an  record for vps_host_name.  If vps_host_name isn't a valid DNS
name and is in some host file, check extra carefully from the RPI about
this.

Then, install mosquitto on your RPI, even if you don't need it
otherwise.  Repeat with mosquitto_pub on the RPI, with mosquitto_sub
running on the VPS.  Then, if you want to subscribe from elsewhere, try
that.

Finally, start up weewx.  Run tcpdump on port 1883 and see if you see
things.  Enable debugging on your broker and watch the logs.

-- 
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/rmitv3dcf4z.fsf%40s1.lexort.com.

Re: [weewx-user] Re: Datenbank zusammen legen.

[Günther Wrana]

Was habe ich nun kaputt gemacht?


pi@raspberrypi:~/Desktop $ tail -f /var/log/syslog
Feb 26 20:33:39 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Feb 26 20:33:39 raspberrypi weewx[8560]: engine: Initializing weewx version 
3.9.2
Feb 26 20:33:39 raspberrypi weewx[8560]: engine: Using Python 2.7.16 
(default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
Feb 26 20:33:39 raspberrypi weewx[8560]: engine: Platform 
Linux-4.19.75-v7+-armv7l-with-debian-10.1
Feb 26 20:33:39 raspberrypi weewx[8560]: engine: Locale is 'de_AT.UTF-8'
Feb 26 20:33:39 raspberrypi weewx[8560]: engine: pid file is 
/var/run/weewx.pid
Feb 26 20:33:39 raspberrypi weewx[8549]: Starting weewx weather system: 
weewx.
Feb 26 20:33:39 raspberrypi systemd[1]: Started LSB: weewx weather system.
Feb 26 20:33:39 raspberrypi weewx[8564]: engine: Error while parsing 
configuration file /home/weewx/weewx.conf
Feb 26 20:33:39 raspberrypi weewx[8564]: Reason: 'Parsing failed 
with several errors.#012First error at line 9.'
Feb 26 20:33:42 raspberrypi dhcpcd[389]: wlan0: Router Advertisement from 
fe80::9ada:c4ff:feb9:eeda
Feb 26 20:33:42 raspberrypi dhcpcd[389]: wlan0: soliciting a DHCPv6 lease
Feb 26 20:33:42 raspberrypi dhcpcd[389]: wlan0: dropping DHCPv6 due to no 
valid routers
Feb 26 20:33:52 raspberrypi dhcpcd[389]: wlan0: Router Advertisement from 
fe80::9ada:c4ff:feb9:eeda
Feb 26 20:33:52 raspberrypi dhcpcd[389]: wlan0: soliciting a DHCPv6 lease
Feb 26 20:33:52 raspberrypi dhcpcd[389]: wlan0: dropping DHCPv6 due to no 
valid routers


Am Montag, 24. Februar 2020 03:11:53 UTC+1 schrieb Thomas Keffer:
>
> The best solution is to replace with your backup.
>
> If you do not have a backup, well, ... you can try dumping it to a file, 
> then restoring. The steps are (NOT TESTED):
>
> *sqlite3 db3.sdb*
> sqlite> *.output db3.sql*
> sqlite> *.dump archive*
> sqlite> *.quit*
>
> Check the file db3.sql, then use it to restore to a new database:
>
> *sqlite3 db3_restored.sdb < db3.sql*
>
> Hopefully the new file, db3_restored.sdb, will be OK.
>
> -tk
>
>
> On Sun, Feb 23, 2020 at 9:34 AM Günther Wrana  > wrote:
>
>> sqlite> pragma integrity_check;
>> *** in database main ***
>> On tree page 554 cell 75: invalid page number 1879769860
>> Multiple uses for byte 1072 of page 554
>> On tree page 957 cell 28: Rowid 18740937184 out of order
>> On tree page 957 cell 25: Rowid 18749066592 out of order
>> On tree page 957 cell 23: Rowid 1561684576 out of order
>> On tree page 957 cell 19: Rowid 1568679008 out of order
>> On tree page 957 cell 17: Rowid 1560117600 out of order
>> On tree page 957 cell 16: Rowid 1593585632 out of order
>> row 9507 missing from index sqlite_autoindex_archive_1
>> row 9508 missing from index sqlite_autoindex_archive_1
>> row 9509 missing from index sqlite_autoindex_archive_1
>> row 9510 missing from index sqlite_autoindex_archive_1
>> row 9511 missing from index sqlite_autoindex_archive_1
>> row 9512 missing from index sqlite_autoindex_archive_1
>> row 9513 missing from index sqlite_autoindex_archive_1
>> row 9514 missing from index sqlite_autoindex_archive_1
>> row 9515 missing from index sqlite_autoindex_archive_1
>> row 9516 missing from index sqlite_autoindex_archive_1
>> row 9517 missing from index sqlite_autoindex_archive_1
>> row 9518 missing from index sqlite_autoindex_archive_1
>> row 9519 missing from index sqlite_autoindex_archive_1
>> row 9520 missing from index sqlite_autoindex_archive_1
>> row 9521 missing from index sqlite_autoindex_archive_1
>> row 9522 missing from index sqlite_autoindex_archive_1
>> row 9523 missing from index sqlite_autoindex_archive_1
>> row 9524 missing from index sqlite_autoindex_archive_1
>> row 9525 missing from index sqlite_autoindex_archive_1
>> row 9526 missing from index sqlite_autoindex_archive_1
>> row 9527 missing from index sqlite_autoindex_archive_1
>> row 9528 missing from index sqlite_autoindex_archive_1
>> row 9529 missing from index sqlite_autoindex_archive_1
>> row 9530 missing from index sqlite_autoindex_archive_1
>> row 9531 missing from index sqlite_autoindex_archive_1
>> row 9532 missing from index sqlite_autoindex_archive_1
>> row 9533 missing from index sqlite_autoindex_archive_1
>> row 9534 missing from index sqlite_autoindex_archive_1
>> row 9535 missing from index sqlite_autoindex_archive_1
>> row 9536 missing from index sqlite_autoindex_archive_1
>> row 9537 missing from index sqlite_autoindex_archive_1
>> row 9538 missing from index sqlite_autoindex_archive_1
>> row 9539 missing from index sqlite_autoindex_archive_1
>> row 9540 missing from index sqlite_autoindex_archive_1
>> row 9541 missing from index sqlite_autoindex_archive_1
>> row 9542 missing from index sqlite_autoindex_archive_1
>> row 9543 missing from index sqlite_autoindex_archive_1
>> row 9544 missing from index sqlite_autoindex_archive_1
>> row 9545 missing from index sqlite_autoindex_archive_1
>> row 9546 missing from index sqlite_autoindex_archive_1
>> row 9547 missing from index sqlite

Re: [weewx-user] Raspberry/MQTT > VPS Server

[Gert Andersen]

Hi

Thanks a lot for your answers.

@Pat, i don't know there are spaces, The mqtt configuration is working fine 
with Ecowitt GW1000 uploading data to the VPS server using Interceptor.I'll 
ty the configuration you mention with uploading via ftp. Will I not miss 
the real-time data every 2 seconds?

@Greg, seems you're running the system I'm looking after. Is it possible to 
provide .conf for the weewx and the mqtt broker. Is far as I can see, the 
only difference is you're running the system on your lan and I'm running 
the weewx/Davis on the lan and the mqtt broker on cloud.

Thanks
Gert

On Wednesday, February 26, 2020 at 4:19:59 PM UTC+1, Greg Troxel wrote:
>
> Gert Andersen > writes: 
>
> > [[MQTT]] 
> > server_url = mqtt: // user: password @ vps_host_name: 1883 / 
> > topic = weather 
> > binding = archive, loop 
> > aggregation = aggregate 
> > log_success = False 
> > log_failure = True 
>
> For what it's worth, I have 
>
>   Davis VP2 
>   raspberry pi (running NetBSD) 
>   weewx (current stable, ish, not v4) 
>   MQTT add on 
>
>   another computer (on the lan) 
>   mosquitto 
>   home assistant (HA) 
>
> and I am getting weather data (via aggregate) into HA just fine.  I am 
> using archive only, not loop. 
>
> So there is no reason your davis/pi/weewx/mqtt should not be able to 
> send mqtt to a broker on a VPS (assuming TCP works with NAT/firewall 
> etc.) 
>

-- 
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/60240a65-dbb6-4048-b5d2-c8a9eb1e3986%40googlegroups.com.

Re: [weewx-user] Re: error with datas of rain

[salinois]

ok thanks Gary

I go to wait 24 hours for the aggregation period; I deleted the records 
in database.


Patrick

Le 26/02/2020 à 00:36, gjr80 a écrit :
That looks suspiciously like a plot generated by the WeeWX image 
generator, if that is the case the data is solely obtained from the 
archive and not the daily summaries. So whilst it is necessary to do 
some rebuilding of the daily summaries after correcting bad data in 
the archive, it will have no effect on WeeWX image generator generated 
plots.


What could possibly be the issue is that the WeeWX generated plots are 
re-generated at different intervals depending on the aggregation 
period of the underlying data used in the plot. For day plots this is 
every archive period, week plots every hour, month plots every 3 hours 
and year plots every 24 hours. rain plots are a little different in 
that day plots use a 1 hour aggregation period whereas week, month and 
year use a 24 hour aggregation period. So rain day plots are updated 
every 1 hour and week, month and year every 24 hours. If this is the 
issue it will come good in time once the offending plot is 
regenerated. Often the easiest thing to do is just delete all plots to 
force regeneration of all plots during the next report cycle.


Gary

On Wednesday, 26 February 2020 07:36:13 UTC+10, Pat wrote:

You'll need to correct the data in archive_day_rain table for the
day by setting to zero or whatever value is correct.

On Tuesday, February 25, 2020 at 2:14:47 PM UTC-5, Patrick
Tranchant wrote:

Hello
the other day when there was a storm in France, the wind made
the rain gauge vibrate, so rain data was recorded; I tried to
delete these records in the base (by finding the time in the
base); but monthly data still appears; should this method make
them disappear?


thanks

Patrick

--
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/19a35acb-1f41-43f9-ab20-b9b8e27e9905%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/e0cf9b49-02c7-b4dd-ac3b-d47dca04beed%40gmail.com.

Re: [weewx-user] Raspberry/MQTT > VPS Server

[Greg Troxel]

Gert Andersen  writes:

> [[MQTT]]
> server_url = mqtt: // user: password @ vps_host_name: 1883 /
> topic = weather
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True

For what it's worth, I have

  Davis VP2
  raspberry pi (running NetBSD)
  weewx (current stable, ish, not v4)
  MQTT add on

  another computer (on the lan)
  mosquitto
  home assistant (HA)

and I am getting weather data (via aggregate) into HA just fine.  I am
using archive only, not loop.

So there is no reason your davis/pi/weewx/mqtt should not be able to
send mqtt to a broker on a VPS (assuming TCP works with NAT/firewall
etc.)

-- 
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/rmimu95fk9z.fsf%40s1.lexort.com.

[weewx-user] Re: Raspberry/MQTT > VPS Server

[Pat]

Are the spaces you're adding for the html_root, belchertown root url, and 
mqtt topic intentional for this forum post? If not, remove those extra 
spaces they as they will cause a problem. 

Do you need to run weewx on the vps host? I don't think you need to. weewx 
on your Pi will generate the webpages needed, then it can FTP or SCP those 
files to the VPS host automatically. Then MQTT on vps host will help broker 
the data. So the config you have will go on the weewx.conf on your Pi as 
that information will get processed into the webpage that weewx will build. 

Port 1883 is MQTT's port; not weewx. Read through this post on how to setup 
MQTT  and testing it for valid data 
and see if it helps you understand the difference between the two systems. 

Also read through this post on how weewx transfers 
the
 
generated webpages to the remote web server (your vps)

On Wednesday, February 26, 2020 at 9:40:22 AM UTC-5, Gert Andersen wrote:
>
> Hi
>
> Thanks for your answer, I'll try that.
>
> I'm a little bit unsure about  the configuration and whether it's right.
>
> On the rpi / weewx I have installed the weewx / mqtt extension to send 
> data on port 1883.
>
> On vps_host I have installed weewx as well as Belchertown. I'm not 
> expecting to install weewx / mqtt here. This is what my weewx.conf looks 
> like on the vps_host:
>
> [[Belchertown]]
>  HTML_ROOT = / var / www / html
>  skin = Belchertown
>  [[[Extras]]]
>  belchertown_root_url = http: // My Server
>  earthquake_enabled = 1
>  forecast_enabled =
>  mqtt_websockets_enabled = 1
>  mqtt_websockets_host = xxx-xxx-xxx-xxx.vpsCloudServer
>  mqtt_websockets_port = 9001
>  mqtt_websockets_ssl = 0
>  mqtt_websockets_topic = weather / loop
>  disconnect_live_website_visitor = 180
>
> My question is also which weewx driver to install on the vps_host. In 
> principle, weewx should only receive data via port 1883 and not use any 
> driver (Vantage, etc) or am I wrong on it
>
> Gert
>
> On Wednesday, February 26, 2020 at 2:11:10 PM UTC+1, Pat wrote:
>>
>> Belchertown should get data as soon as there is a dateTime in the MQTT 
>> payload. Simulator should send this. What you have looks correct, but more 
>> validating needs to take place. Use another client to connect to the MQTT 
>> broker to validate you're seeing any data at all therethere. 
>>
>> Or run Belchertown in debug mode and check the Chrome logs to see what it 
>> says. To run debug, add /?debug=true to the end of your site, like 
>> https://belchertownweather.com/?debug=true - then open the Chrome 
>> console by going to Settings > More Tools > Developer Tools and open the 
>> Console tab. Almost everything the skin is doing is viewable in this debug 
>> mode, from chart generation to any and all MQTT payload data it's seeing.
>>
>>
>>
>> On Wednesday, February 26, 2020 at 3:56:02 AM UTC-5, Gert Andersen wrote:
>>>
>>> Hi there
>>> Is this scenario possible.
>>>
>>> Currently I have an Ecowitt GW1000 which sends data to a VPS Server 
>>> every 16 seconds with Weewx Interceptor, MQTT and Belchertowner installed 
>>> on the VPS Server. This works fine.
>>>
>>> I also have a Davis Vantage Pro2, which is connected to a Meetobridge 
>>> via Davis USB logger. This also works fine.
>>>
>>> Here's my new scenario:
>>> Davis USB logger connected to rpi/weewx. On rpi/weewx I want to install 
>>> mqtt with the following content:
>>>
>>> [[MQTT]]
>>> server_url = mqtt: // user: password @ vps_host_name: 1883 /
>>> topic = weather
>>> binding = archive, loop
>>> aggregation = aggregate
>>> log_success = False
>>> log_failure = True
>>>
>>> On  I have installed Mosquitto which works fine with 
>>> upload via Interceptor. I want this to be able to upload every 2 seconds.
>>>
>>> I have not yet connected Davis to the rpi / weewx. but tried the 
>>> configuration with Simulator and the above MQTT configuration. Belchertown 
>>> on  connects fine to MQTT, but is awaiting data. Is it 
>>> because Simulator does not send data via MQTT or because my configuration 
>>> is wrong.
>>>
>>> Gert
>>>
>>

-- 
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/0a6aee91-aad4-45a6-b692-ca17e268e1a1%40googlegroups.com.

[weewx-user] Re: Raspberry/MQTT > VPS Server

[Gert Andersen]

Hi

Thanks for your answer, I'll try that.

I'm a little bit unsure about  the configuration and whether it's right.

On the rpi / weewx I have installed the weewx / mqtt extension to send data 
on port 1883.

On vps_host I have installed weewx as well as Belchertown. I'm not 
expecting to install weewx / mqtt here. This is what my weewx.conf looks 
like on the vps_host:

[[Belchertown]]
 HTML_ROOT = / var / www / html
 skin = Belchertown
 [[[Extras]]]
 belchertown_root_url = http: // My Server
 earthquake_enabled = 1
 forecast_enabled =
 mqtt_websockets_enabled = 1
 mqtt_websockets_host = xxx-xxx-xxx-xxx.vpsCloudServer
 mqtt_websockets_port = 9001
 mqtt_websockets_ssl = 0
 mqtt_websockets_topic = weather / loop
 disconnect_live_website_visitor = 180

My question is also which weewx driver to install on the vps_host. In 
principle, weewx should only receive data via port 1883 and not use any 
driver (Vantage, etc) or am I wrong on it

Gert

On Wednesday, February 26, 2020 at 2:11:10 PM UTC+1, Pat wrote:
>
> Belchertown should get data as soon as there is a dateTime in the MQTT 
> payload. Simulator should send this. What you have looks correct, but more 
> validating needs to take place. Use another client to connect to the MQTT 
> broker to validate you're seeing any data at all therethere. 
>
> Or run Belchertown in debug mode and check the Chrome logs to see what it 
> says. To run debug, add /?debug=true to the end of your site, like 
> https://belchertownweather.com/?debug=true - then open the Chrome console 
> by going to Settings > More Tools > Developer Tools and open the Console 
> tab. Almost everything the skin is doing is viewable in this debug mode, 
> from chart generation to any and all MQTT payload data it's seeing.
>
>
>
> On Wednesday, February 26, 2020 at 3:56:02 AM UTC-5, Gert Andersen wrote:
>>
>> Hi there
>> Is this scenario possible.
>>
>> Currently I have an Ecowitt GW1000 which sends data to a VPS Server every 
>> 16 seconds with Weewx Interceptor, MQTT and Belchertowner installed on the 
>> VPS Server. This works fine.
>>
>> I also have a Davis Vantage Pro2, which is connected to a Meetobridge via 
>> Davis USB logger. This also works fine.
>>
>> Here's my new scenario:
>> Davis USB logger connected to rpi/weewx. On rpi/weewx I want to install 
>> mqtt with the following content:
>>
>> [[MQTT]]
>> server_url = mqtt: // user: password @ vps_host_name: 1883 /
>> topic = weather
>> binding = archive, loop
>> aggregation = aggregate
>> log_success = False
>> log_failure = True
>>
>> On  I have installed Mosquitto which works fine with 
>> upload via Interceptor. I want this to be able to upload every 2 seconds.
>>
>> I have not yet connected Davis to the rpi / weewx. but tried the 
>> configuration with Simulator and the above MQTT configuration. Belchertown 
>> on  connects fine to MQTT, but is awaiting data. Is it 
>> because Simulator does not send data via MQTT or because my configuration 
>> is wrong.
>>
>> Gert
>>
>

-- 
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/88d7e7e7-e4f9-41d6-8dd0-6a6dc05ab112%40googlegroups.com.

[weewx-user] Re: Raspberry/MQTT > VPS Server

[Pat]

Belchertown should get data as soon as there is a dateTime in the MQTT 
payload. Simulator should send this. What you have looks correct, but more 
validating needs to take place. Use another client to connect to the MQTT 
broker to validate you're seeing any data at all therethere. 

Or run Belchertown in debug mode and check the Chrome logs to see what it 
says. To run debug, add /?debug=true to the end of your site, like 
https://belchertownweather.com/?debug=true - then open the Chrome console 
by going to Settings > More Tools > Developer Tools and open the Console 
tab. Almost everything the skin is doing is viewable in this debug mode, 
from chart generation to any and all MQTT payload data it's seeing.



On Wednesday, February 26, 2020 at 3:56:02 AM UTC-5, Gert Andersen wrote:
>
> Hi there
> Is this scenario possible.
>
> Currently I have an Ecowitt GW1000 which sends data to a VPS Server every 
> 16 seconds with Weewx Interceptor, MQTT and Belchertowner installed on the 
> VPS Server. This works fine.
>
> I also have a Davis Vantage Pro2, which is connected to a Meetobridge via 
> Davis USB logger. This also works fine.
>
> Here's my new scenario:
> Davis USB logger connected to rpi/weewx. On rpi/weewx I want to install 
> mqtt with the following content:
>
> [[MQTT]]
> server_url = mqtt: // user: password @ vps_host_name: 1883 /
> topic = weather
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True
>
> On  I have installed Mosquitto which works fine with upload 
> via Interceptor. I want this to be able to upload every 2 seconds.
>
> I have not yet connected Davis to the rpi / weewx. but tried the 
> configuration with Simulator and the above MQTT configuration. Belchertown 
> on  connects fine to MQTT, but is awaiting data. Is it 
> because Simulator does not send data via MQTT or because my configuration 
> is wrong.
>
> Gert
>

-- 
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/1ae4cc59-a13d-42c8-a31e-c2c0a066af42%40googlegroups.com.

[weewx-user] Raspberry/MQTT > VPS Server

[Gert Andersen]

Hi there
Is this scenario possible.

Currently I have an Ecowitt GW1000 which sends data to a VPS Server every 
16 seconds with Weewx Interceptor, MQTT and Belchertowner installed on the 
VPS Server. This works fine.

I also have a Davis Vantage Pro2, which is connected to a Meetobridge via 
Davis USB logger. This also works fine.

Here's my new scenario:
Davis USB logger connected to rpi/weewx. On rpi/weewx I want to install 
mqtt with the following content:

[[MQTT]]
server_url = mqtt: // user: password @ vps_host_name: 1883 /
topic = weather
binding = archive, loop
aggregation = aggregate
log_success = False
log_failure = True

On  I have installed Mosquitto which works fine with upload 
via Interceptor. I want this to be able to upload every 2 seconds.

I have not yet connected Davis to the rpi / weewx. but tried the 
configuration with Simulator and the above MQTT configuration. Belchertown 
on  connects fine to MQTT, but is awaiting data. Is it 
because Simulator does not send data via MQTT or because my configuration 
is wrong.

Gert

-- 
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/bc74319c-ad7c-404d-acec-149fe55d6d94%40googlegroups.com.

[weewx-user] Re: fousb strange behaviour

[Macha]

Thanks for responding.

Yes, I get spiders (and birds perching on it and ...).

However, these rain results occur even when the rain meter isn’t connected. For 
example, overnight recorded 30mm of rain when the meter was disconnected - 
furthermore, it wasn’t even raining.

I was wondering about some kind interference. Or the station just being, well, 
buggered.

I’m almost at the point of splashing out on a new station, but wouldn’t want 
the new one to act just like the current one.

-- 
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/d2a91952-7e81-4845-907b-24b4b60c8510%40googlegroups.com.