Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Andrew Milner]

It looks as though weewx found your wmr300 this time.

The index.html will not be created until the first archive interval - so 
how long it takes to appear depends on what archive interval you set in 
weewx.conf

Just leave it running, and monitor the log using the command
tail -f /var/log/syslog

(you exit the monitoring by typing ctrl/c)



On Tuesday, 21 February 2017 09:14:47 UTC+2, Torbjørn Aasen wrote:

> Sorry I nag so much on you.
> But I am a little distressed over not get it to work.
>
> I ran your commands and this is what came in the log
>
> But I can still do not these files
> file: ///var/www/html/weewx/index.html
>
>
>
> Feb 21 07:38:53 raspberrypi kernel: [   88.499789] usb 1-1.4: reset 
> full-speed USB device number 5 using dwc_otg
> Feb 21 07:38:53 raspberrypi weewx[657]: engine: StdConvert target unit is 
> 0x1
> Feb 21 07:38:53 raspberrypi weewx[657]: wxcalculate: The following values 
> will be calculated: barometer=prefer_hardware, windchill=hardware, 
> dewpoint=hardware, appTemp=prefer_hardware, rainRate=hardware, 
> windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
> Feb 21 07:38:53 raspberrypi weewx[657]: wxcalculate: The following 
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Feb 21 07:38:53 raspberrypi weewx[657]: engine: Archive will use data 
> binding wx_binding
> Feb 21 07:38:53 raspberrypi weewx[657]: engine: Record generation will be 
> attempted in 'hardware'
> Feb 21 07:38:53 raspberrypi weewx[657]: engine: Using archive interval of 
> 300 seconds (specified in weewx configuration)
> Feb 21 07:38:53 raspberrypi weewx[657]: engine: Using binding 'wx_binding' 
> to database 'weewx.sdb'
> Feb 21 07:38:53 raspberrypi weewx[657]: manager: Starting backfill of 
> daily summaries
> Feb 21 07:38:53 raspberrypi weewx[657]: manager: Daily summaries up to date
> Feb 21 07:38:53 raspberrypi weewx[657]: restx: StationRegistry: 
> Registration not requested.
> Feb 21 07:38:53 raspberrypi weewx[657]: restx: Wunderground: Posting not 
> enabled.
> Feb 21 07:38:53 raspberrypi weewx[657]: restx: PWSweather: Posting not 
> enabled.
> Feb 21 07:38:53 raspberrypi weewx[657]: restx: CWOP: Posting not enabled.
> Feb 21 07:38:53 raspberrypi weewx[657]: restx: WOW: Posting not enabled.
> Feb 21 07:38:53 raspberrypi weewx[657]: restx: AWEKAS: Posting not enabled.
> Feb 21 07:38:53 raspberrypi weewx[657]: engine: Starting up weewx version 
> 3.6.2
> Feb 21 07:38:53 raspberrypi weewx[657]: wmr300: reading records since 
> *** N/A *** (N/A   )
> Feb 21 07:38:57 raspberrypi vncserver-x11[601]: Connections: disconnected: 
> t...@olga.no  (via hc-4-gb-slg-1.services.vnc.com) 
> ([AuthFailure] Either the username was not recognised, or the password was 
> incorrect)
> Feb 21 07:39:03 raspberrypi vncserver-x11[601]: HostedRendezvous: 
> Connection to [YG9dPF-b3yCx-sioUik] is from user " >"
> Feb 21 07:39:04 raspberrypi vncserver-x11[601]: Connections: connected: 
> t...@olga.no  (via hc-4-gb-slg-1.services.vnc.com)
> Feb 21 07:39:12 raspberrypi vncserver-x11[601]: Connections: 
> authenticated: t...@olga.no  (via 
> hc-4-gb-slg-1.services.vnc.com), as (anonymous) (d permissions)
> Feb 21 07:39:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Tue Feb 21 07:39:42 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Feb 21 07:39:13 raspberrypi dbus[429]: [system] Activating via systemd: 
> service name='org.freedesktop.ColorManager' unit='colord.service'
> Feb 21 07:39:14 raspberrypi systemd[1]: Starting Manage, Install and 
> Generate Color Profiles...
> Feb 21 07:39:14 raspberrypi colord: Using mapping database file 
> /var/lib/colord/mapping.db
> Feb 21 07:39:14 raspberrypi colord: Using device database file 
> /var/lib/colord/storage.db
> Feb 21 07:39:14 raspberrypi colord: Using profile database file 
> /var/lib/colord/storage.db
> Feb 21 07:39:14 raspberrypi colord: loaded plugin libcd_plugin_scanner.so
> Feb 21 07:39:14 raspberrypi colord: loaded plugin libcd_plugin_sane.so
> Feb 21 07:39:14 raspberrypi colord: loaded plugin libcd_plugin_camera.so
> Feb 21 07:39:14 raspberrypi colord: Daemon ready for requests
> Feb 21 07:39:14 raspberrypi dbus[429]: [system] Successfully activated 
> service 'org.freedesktop.ColorManager'
> Feb 21 07:39:14 raspberrypi systemd[1]: Started Manage, Install and 
> Generate Color Profiles.
> Feb 21 07:39:14 raspberrypi colord: Profile added: 
> TA_Kontor_via_VNC_from_TA-THINK-Gray..
> Feb 21 07:39:14 raspberrypi colord: Profile added: 
> TA_Kontor_via_VNC_from_TA-THINK-CMYK..
> Feb 21 07:39:14 raspberrypi colord[1145]: (colord:1145): Cd-WARNING **: 
> failed to get session [pid 530]: Unknown error -2
> Feb 21 07:39:14 raspberrypi colord: Device added: 
> cups-TA_Kontor_via_VNC_from_TA-THINK
> Feb 21 

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Torbjørn Aasen]

Sorry I nag so much on you.
But I am a little distressed over not get it to work.

I ran your commands and this is what came in the log

But I can still do not these files
file: ///var/www/html/weewx/index.html



Feb 21 07:38:53 raspberrypi kernel: [   88.499789] usb 1-1.4: reset
full-speed USB device number 5 using dwc_otg
Feb 21 07:38:53 raspberrypi weewx[657]: engine: StdConvert target unit is
0x1
Feb 21 07:38:53 raspberrypi weewx[657]: wxcalculate: The following values
will be calculated: barometer=prefer_hardware, windchill=hardware,
dewpoint=hardware, appTemp=prefer_hardware, rainRate=hardware,
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware,
humidex=prefer_hardware, pressure=prefer_hardware,
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
cloudbase=prefer_hardware
Feb 21 07:38:53 raspberrypi weewx[657]: wxcalculate: The following
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 21 07:38:53 raspberrypi weewx[657]: engine: Archive will use data
binding wx_binding
Feb 21 07:38:53 raspberrypi weewx[657]: engine: Record generation will be
attempted in 'hardware'
Feb 21 07:38:53 raspberrypi weewx[657]: engine: Using archive interval of
300 seconds (specified in weewx configuration)
Feb 21 07:38:53 raspberrypi weewx[657]: engine: Using binding 'wx_binding'
to database 'weewx.sdb'
Feb 21 07:38:53 raspberrypi weewx[657]: manager: Starting backfill of daily
summaries
Feb 21 07:38:53 raspberrypi weewx[657]: manager: Daily summaries up to date
Feb 21 07:38:53 raspberrypi weewx[657]: restx: StationRegistry:
Registration not requested.
Feb 21 07:38:53 raspberrypi weewx[657]: restx: Wunderground: Posting not
enabled.
Feb 21 07:38:53 raspberrypi weewx[657]: restx: PWSweather: Posting not
enabled.
Feb 21 07:38:53 raspberrypi weewx[657]: restx: CWOP: Posting not enabled.
Feb 21 07:38:53 raspberrypi weewx[657]: restx: WOW: Posting not enabled.
Feb 21 07:38:53 raspberrypi weewx[657]: restx: AWEKAS: Posting not enabled.
Feb 21 07:38:53 raspberrypi weewx[657]: engine: Starting up weewx version
3.6.2
Feb 21 07:38:53 raspberrypi weewx[657]: wmr300: reading records since
*** N/A *** (N/A   )
Feb 21 07:38:57 raspberrypi vncserver-x11[601]: Connections: disconnected:
t...@olga.no (via hc-4-gb-slg-1.services.vnc.com) ([AuthFailure] Either the
username was not recognised, or the password was incorrect)
Feb 21 07:39:03 raspberrypi vncserver-x11[601]: HostedRendezvous:
Connection to [YG9dPF-b3yCx-sioUik] is from user ""
Feb 21 07:39:04 raspberrypi vncserver-x11[601]: Connections: connected:
t...@olga.no (via hc-4-gb-slg-1.services.vnc.com)
Feb 21 07:39:12 raspberrypi vncserver-x11[601]: Connections: authenticated:
t...@olga.no (via hc-4-gb-slg-1.services.vnc.com), as (anonymous) (d
permissions)
Feb 21 07:39:12 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Tue Feb 21 07:39:42 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 21 07:39:13 raspberrypi dbus[429]: [system] Activating via systemd:
service name='org.freedesktop.ColorManager' unit='colord.service'
Feb 21 07:39:14 raspberrypi systemd[1]: Starting Manage, Install and
Generate Color Profiles...
Feb 21 07:39:14 raspberrypi colord: Using mapping database file
/var/lib/colord/mapping.db
Feb 21 07:39:14 raspberrypi colord: Using device database file
/var/lib/colord/storage.db
Feb 21 07:39:14 raspberrypi colord: Using profile database file
/var/lib/colord/storage.db
Feb 21 07:39:14 raspberrypi colord: loaded plugin libcd_plugin_scanner.so
Feb 21 07:39:14 raspberrypi colord: loaded plugin libcd_plugin_sane.so
Feb 21 07:39:14 raspberrypi colord: loaded plugin libcd_plugin_camera.so
Feb 21 07:39:14 raspberrypi colord: Daemon ready for requests
Feb 21 07:39:14 raspberrypi dbus[429]: [system] Successfully activated
service 'org.freedesktop.ColorManager'
Feb 21 07:39:14 raspberrypi systemd[1]: Started Manage, Install and
Generate Color Profiles.
Feb 21 07:39:14 raspberrypi colord: Profile added:
TA_Kontor_via_VNC_from_TA-THINK-Gray..
Feb 21 07:39:14 raspberrypi colord: Profile added:
TA_Kontor_via_VNC_from_TA-THINK-CMYK..
Feb 21 07:39:14 raspberrypi colord[1145]: (colord:1145): Cd-WARNING **:
failed to get session [pid 530]: Unknown error -2
Feb 21 07:39:14 raspberrypi colord: Device added:
cups-TA_Kontor_via_VNC_from_TA-THINK
Feb 21 07:39:15 raspberrypi kernel: [  110.722384] warning: process
`colord-sane' used the deprecated sysctl system call with 8.1.2.
Feb 21 07:39:15 raspberrypi colord-sane: [bjnp] create_broadcast_socket:
bind socket to local address failed - Cannot assign requested address
Feb 21 07:39:35 raspberrypi dhcpcd[443]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 21 07:39:40 raspberrypi dhcpcd[443]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 21 07:39:40 raspberrypi dhcpcd[443]: wlan0: DHCPv6 REPLY: No Addresses
Available
Feb 21 07:41:40 raspberrypi dhcpcd[443]: wlan0: DHCPv6 REPLY: No Addresses
Available
Feb 21 

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Torbjørn Aasen]

Hello again
1 I we get this to work :-)
I used this guide but weather was not in RPI
I've put it in reach but it helps nothing.

Configure apt
Tell apt where to find the weewx releases. This only has to be done once -
the first time you install.

curl -s http://weewx.com/keys.html | sudo apt-key add -
echo "deb [arch = all] http://weewx.com/apt/ squeeze main" | sudo tee
/etc/apt/sources.list.d/weewx.list
Install
Use apt-get install two weewx. When you are done, weewx will be running in
the background as a daemon.

sudo apt-get update
sudo apt-get install weewx

2017-02-21 7:54 GMT+01:00 Andrew Milner :

> 1.  what were you trying to do with the command which you posted?
> 2.  how did you install weewx?  If you used the deb install then try the
> commands:
> sudo /etc/init.d/weewx start and
> sudo /etc/init.d/weewx stop
>
> to stop and start the weewx daemon - if you were trying to start weewx.
>
>
>
>
> On Tuesday, 21 February 2017 08:47:16 UTC+2, Torbjørn Aasen wrote:
>
>> pi@raspberrypi:~ $ sudo weewxd weewx.conf
>> Unable to open configuration file /home/pi/weewx.confTraceback (most
>> recent call last):
>>   File "/usr/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/usr/share/weewx/weewx/engine.py", line 823, in main
>> config_dict = getConfiguration(config_path)
>>   File "/usr/share/weewx/weewx/engine.py", line 922, in getConfiguration
>> config_dict = configobj.ConfigObj(config_path, file_error=True)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in
>> __init__
>> self._load(infile, configspec)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1240, in
>> _load
>> raise IOError('Config file not found: "%s".' % self.filename)
>> IOError: Config file not found: "/home/pi/weewx.conf".
>> pi@raspberrypi:~ $
>>
>>
>>
>>
>>
>>
>> 2017-02-21 7:46 GMT+01:00 Andrew Milner :
>>
>>> Have you connected the weather station to the Pi??  The log is saying
>>> that weewx cannot find the weather station plugged into the USB.
>>>
>>> If you want to run weewx without a weather station connected to the RPi
>>> you must select 'simulator' as the station type.
>>>
>>> If you select a station type of WMR300 - as you have done - then the
>>> station must be connected to the RPi for weewx to be able to run.
>>>
>>>
>>>
>>>
>>> On Tuesday, 21 February 2017 08:35:56 UTC+2, Torbjørn Aasen wrote:
>>>
 Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
 router available
 Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
 router available
 Feb 20 20:35:21 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
 router available
 Feb 20 20:35:24 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No
 Addresses Available
 Feb 20 20:36:02 raspberrypi vncserver-x11-serviced[524]: executing
 SUDO_LAUNCHCMD: gksudo -D 'VNC Server - sudo password required' --
 '/usr/bin/vncpipehelper' '-hash' 'b339b13545b35610a9bb03a210ce6812e39aaa83'
 '/tmp/.vnc-1000/vncserverui-service.vncpipehelper.173669680'
 '/usr/bin/vncserver-x11-core' '-service' '-configHelper'
 Feb 20 20:36:02 raspberrypi rsyslogd-2007: action 'action 17'
 suspended, next retry is Mon Feb 20 20:36:32 2017 [try
 http://www.rsyslog.com/e/2007 ]
 Feb 20 20:36:40 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
 router available
 Feb 20 20:36:40 raspberrypi rsyslogd-2007: action 'action 17'
 suspended, next retry is Mon Feb 20 20:37:10 2017 [try
 http://www.rsyslog.com/e/2007 ]
 Feb 20 20:36:44 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
 router available
 Feb 20 20:36:49 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
 router available
 Feb 20 20:36:53 raspberrypi vncserver-x11[617]: HostedRendezvous:
 Connection to [YG9tMT-oUaaq-EDofz9] is from user ""
 Feb 20 20:36:53 raspberrypi vncserver-x11[617]: Connections: connected:
 t...@olga.no (from 192.168.50.12::54827)
 Feb 20 20:37:06 raspberrypi vncserver-x11[617]: Connections:
 authenticated: t...@olga.no (from 192.168.50.12::54827), as
 (anonymous) (d permissions)
 Feb 20 20:37:07 raspberrypi dbus[428]: [system] Activating via systemd:
 service name='org.freedesktop.ColorManager' unit='colord.service'
 Feb 20 20:37:07 raspberrypi systemd[1]: Starting Manage, Install and
 Generate Color Profiles...
 Feb 20 20:37:08 raspberrypi colord: Using mapping database file
 /var/lib/colord/mapping.db
 Feb 20 20:37:08 raspberrypi colord: Using device database file
 /var/lib/colord/storage.db
 Feb 20 20:37:08 raspberrypi colord: Using profile database file
 /var/lib/colord/storage.db
 Feb 20 20:37:08 raspberrypi colord: loaded plugin
 libcd_plugin_scanner.so
 Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_sane.so
 Feb 20 20:37:08 

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Andrew Milner]

or to run directly, not as a daemon, try
sudo weewxd /etc/weewx/weewx.conf



On Tuesday, 21 February 2017 08:54:41 UTC+2, Andrew Milner wrote:

> 1.  what were you trying to do with the command which you posted?
> 2.  how did you install weewx?  If you used the deb install then try the 
> commands:
> sudo /etc/init.d/weewx start and
> sudo /etc/init.d/weewx stop
>
> to stop and start the weewx daemon - if you were trying to start weewx.
>
>
>
>
> On Tuesday, 21 February 2017 08:47:16 UTC+2, Torbjørn Aasen wrote:
>
>> pi@raspberrypi:~ $ sudo weewxd weewx.conf
>> Unable to open configuration file /home/pi/weewx.confTraceback (most 
>> recent call last):
>>   File "/usr/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/usr/share/weewx/weewx/engine.py", line 823, in main
>> config_dict = getConfiguration(config_path)
>>   File "/usr/share/weewx/weewx/engine.py", line 922, in getConfiguration
>> config_dict = configobj.ConfigObj(config_path, file_error=True)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
>> __init__
>> self._load(infile, configspec)
>>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1240, in 
>> _load
>> raise IOError('Config file not found: "%s".' % self.filename)
>> IOError: Config file not found: "/home/pi/weewx.conf".
>> pi@raspberrypi:~ $ 
>>
>>
>>
>>
>>
>>
>> 2017-02-21 7:46 GMT+01:00 Andrew Milner :
>>
>>> Have you connected the weather station to the Pi??  The log is saying 
>>> that weewx cannot find the weather station plugged into the USB.
>>>
>>> If you want to run weewx without a weather station connected to the RPi 
>>> you must select 'simulator' as the station type.
>>>
>>> If you select a station type of WMR300 - as you have done - then the 
>>> station must be connected to the RPi for weewx to be able to run.
>>>
>>>
>>>
>>>
>>> On Tuesday, 21 February 2017 08:35:56 UTC+2, Torbjørn Aasen wrote:
>>>
 Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
 router available
 Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
 router available
 Feb 20 20:35:21 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
 router available
 Feb 20 20:35:24 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No 
 Addresses Available
 Feb 20 20:36:02 raspberrypi vncserver-x11-serviced[524]: executing 
 SUDO_LAUNCHCMD: gksudo -D 'VNC Server - sudo password required' -- 
 '/usr/bin/vncpipehelper' '-hash' 
 'b339b13545b35610a9bb03a210ce6812e39aaa83' 
 '/tmp/.vnc-1000/vncserverui-service.vncpipehelper.173669680' 
 '/usr/bin/vncserver-x11-core' '-service' '-configHelper'
 Feb 20 20:36:02 raspberrypi rsyslogd-2007: action 'action 17' 
 suspended, next retry is Mon Feb 20 20:36:32 2017 [try 
 http://www.rsyslog.com/e/2007 ]
 Feb 20 20:36:40 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
 router available
 Feb 20 20:36:40 raspberrypi rsyslogd-2007: action 'action 17' 
 suspended, next retry is Mon Feb 20 20:37:10 2017 [try 
 http://www.rsyslog.com/e/2007 ]
 Feb 20 20:36:44 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
 router available
 Feb 20 20:36:49 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
 router available
 Feb 20 20:36:53 raspberrypi vncserver-x11[617]: HostedRendezvous: 
 Connection to [YG9tMT-oUaaq-EDofz9] is from user ""
 Feb 20 20:36:53 raspberrypi vncserver-x11[617]: Connections: connected: 
 t...@olga.no (from 192.168.50.12::54827)
 Feb 20 20:37:06 raspberrypi vncserver-x11[617]: Connections: 
 authenticated: t...@olga.no (from 192.168.50.12::54827), as 
 (anonymous) (d permissions)
 Feb 20 20:37:07 raspberrypi dbus[428]: [system] Activating via systemd: 
 service name='org.freedesktop.ColorManager' unit='colord.service'
 Feb 20 20:37:07 raspberrypi systemd[1]: Starting Manage, Install and 
 Generate Color Profiles...
 Feb 20 20:37:08 raspberrypi colord: Using mapping database file 
 /var/lib/colord/mapping.db
 Feb 20 20:37:08 raspberrypi colord: Using device database file 
 /var/lib/colord/storage.db
 Feb 20 20:37:08 raspberrypi colord: Using profile database file 
 /var/lib/colord/storage.db
 Feb 20 20:37:08 raspberrypi colord: loaded plugin 
 libcd_plugin_scanner.so
 Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_sane.so
 Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_camera.so
 Feb 20 20:37:08 raspberrypi colord: Daemon ready for requests
 Feb 20 20:37:08 raspberrypi dbus[428]: [system] Successfully activated 
 service 'org.freedesktop.ColorManager'
 Feb 20 20:37:08 raspberrypi systemd[1]: Started Manage, Install and 
 Generate Color Profiles.
 Feb 20 20:37:08 raspberrypi colord: Profile added: 
 ES3451_MFP(PCL)_via_VNC_from_THINK2-Gray..
 Feb 

[weewx-user] KlimaLogg Pro with sensors 30.3180.IT: batteryStatus

[Christian]

I'm evaluating weewx on a Raspberry Pi 3. I've been waiting years for a 
solution to read the KlimaLogg sensor data without Windows software, and 
I'm very happy that it's possible with weewx and the weewx-klimalogg driver.

I own a KlimaLogg Pro device and 8 thermo/hygro sensors.

The installation of weewx worked fine. I do not use any report generator; 
the values are just written to a SQLite database which is read periodically 
by the home automation software FHEM as described on their forum 
.

The database contains temperature and humidity values for all sensors, and 
rxCheckPercent. The batteryStatus values are all NULL.

My questions:
1.) Is it correct that the batteryStatus values are missing? Can maybe 
someone tell me if my hardware does support them at all?
2.) Is logging of alarm events supported by the weewx-klimalogg driver?

My hardware has the following labels:

   - Base station:
  - Raumklima-Detektor RH100
  - Kat Nr.: 30.3039.01.IT
  - 03/2012 V11
   - Transceiver:
  - Kat-Nr.: 30.3175
  - 02/2012 V00
   - Sensors:
  - 30.3180.IT
  - 04/2012 V01C2
  
I didn't create debug logs yet but will be able to provide them if it is 
necessary to answer my questions.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Andrew Milner]

1.  what were you trying to do with the command which you posted?
2.  how did you install weewx?  If you used the deb install then try the 
commands:
sudo /etc/init.d/weewx start and
sudo /etc/init.d/weewx stop

to stop and start the weewx daemon - if you were trying to start weewx.




On Tuesday, 21 February 2017 08:47:16 UTC+2, Torbjørn Aasen wrote:

> pi@raspberrypi:~ $ sudo weewxd weewx.conf
> Unable to open configuration file /home/pi/weewx.confTraceback (most 
> recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 823, in main
> config_dict = getConfiguration(config_path)
>   File "/usr/share/weewx/weewx/engine.py", line 922, in getConfiguration
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1240, in _load
> raise IOError('Config file not found: "%s".' % self.filename)
> IOError: Config file not found: "/home/pi/weewx.conf".
> pi@raspberrypi:~ $ 
>
>
>
>
>
>
> 2017-02-21 7:46 GMT+01:00 Andrew Milner  >:
>
>> Have you connected the weather station to the Pi??  The log is saying 
>> that weewx cannot find the weather station plugged into the USB.
>>
>> If you want to run weewx without a weather station connected to the RPi 
>> you must select 'simulator' as the station type.
>>
>> If you select a station type of WMR300 - as you have done - then the 
>> station must be connected to the RPi for weewx to be able to run.
>>
>>
>>
>>
>> On Tuesday, 21 February 2017 08:35:56 UTC+2, Torbjørn Aasen wrote:
>>
>>> Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
>>> router available
>>> Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
>>> router available
>>> Feb 20 20:35:21 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
>>> router available
>>> Feb 20 20:35:24 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No 
>>> Addresses Available
>>> Feb 20 20:36:02 raspberrypi vncserver-x11-serviced[524]: executing 
>>> SUDO_LAUNCHCMD: gksudo -D 'VNC Server - sudo password required' -- 
>>> '/usr/bin/vncpipehelper' '-hash' 'b339b13545b35610a9bb03a210ce6812e39aaa83' 
>>> '/tmp/.vnc-1000/vncserverui-service.vncpipehelper.173669680' 
>>> '/usr/bin/vncserver-x11-core' '-service' '-configHelper'
>>> Feb 20 20:36:02 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Mon Feb 20 20:36:32 2017 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Feb 20 20:36:40 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
>>> router available
>>> Feb 20 20:36:40 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Mon Feb 20 20:37:10 2017 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Feb 20 20:36:44 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
>>> router available
>>> Feb 20 20:36:49 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
>>> router available
>>> Feb 20 20:36:53 raspberrypi vncserver-x11[617]: HostedRendezvous: 
>>> Connection to [YG9tMT-oUaaq-EDofz9] is from user ""
>>> Feb 20 20:36:53 raspberrypi vncserver-x11[617]: Connections: connected: 
>>> t...@olga.no (from 192.168.50.12::54827)
>>> Feb 20 20:37:06 raspberrypi vncserver-x11[617]: Connections: 
>>> authenticated: t...@olga.no (from 192.168.50.12::54827), as (anonymous) 
>>> (d permissions)
>>> Feb 20 20:37:07 raspberrypi dbus[428]: [system] Activating via systemd: 
>>> service name='org.freedesktop.ColorManager' unit='colord.service'
>>> Feb 20 20:37:07 raspberrypi systemd[1]: Starting Manage, Install and 
>>> Generate Color Profiles...
>>> Feb 20 20:37:08 raspberrypi colord: Using mapping database file 
>>> /var/lib/colord/mapping.db
>>> Feb 20 20:37:08 raspberrypi colord: Using device database file 
>>> /var/lib/colord/storage.db
>>> Feb 20 20:37:08 raspberrypi colord: Using profile database file 
>>> /var/lib/colord/storage.db
>>> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_scanner.so
>>> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_sane.so
>>> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_camera.so
>>> Feb 20 20:37:08 raspberrypi colord: Daemon ready for requests
>>> Feb 20 20:37:08 raspberrypi dbus[428]: [system] Successfully activated 
>>> service 'org.freedesktop.ColorManager'
>>> Feb 20 20:37:08 raspberrypi systemd[1]: Started Manage, Install and 
>>> Generate Color Profiles.
>>> Feb 20 20:37:08 raspberrypi colord: Profile added: 
>>> ES3451_MFP(PCL)_via_VNC_from_THINK2-Gray..
>>> Feb 20 20:37:08 raspberrypi colord: Profile added: 
>>> ES3451_MFP(PCL)_via_VNC_from_THINK2-CMYK..
>>> Feb 20 20:37:08 raspberrypi colord[1894]: (colord:1894): Cd-WARNING **: 
>>> failed to get session [pid 511]: Unknown error -2
>>> Feb 20 20:37:08 raspberrypi colord: 

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Torbjørn Aasen]

I have it connected to now
I had not when I installed into WEEWX program.
Do I delete weewx program to get it or is there something else that can fix
it


2017-02-21 7:46 GMT+01:00 Andrew Milner :

> Have you connected the weather station to the Pi??  The log is saying that
> weewx cannot find the weather station plugged into the USB.
>
> If you want to run weewx without a weather station connected to the RPi
> you must select 'simulator' as the station type.
>
> If you select a station type of WMR300 - as you have done - then the
> station must be connected to the RPi for weewx to be able to run.
>
>
>
>
> On Tuesday, 21 February 2017 08:35:56 UTC+2, Torbjørn Aasen wrote:
>
>> Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:35:21 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:35:24 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No
>> Addresses Available
>> Feb 20 20:36:02 raspberrypi vncserver-x11-serviced[524]: executing
>> SUDO_LAUNCHCMD: gksudo -D 'VNC Server - sudo password required' --
>> '/usr/bin/vncpipehelper' '-hash' 'b339b13545b35610a9bb03a210ce6812e39aaa83'
>> '/tmp/.vnc-1000/vncserverui-service.vncpipehelper.173669680'
>> '/usr/bin/vncserver-x11-core' '-service' '-configHelper'
>> Feb 20 20:36:02 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Mon Feb 20 20:36:32 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Feb 20 20:36:40 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:36:40 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Mon Feb 20 20:37:10 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Feb 20 20:36:44 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:36:49 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:36:53 raspberrypi vncserver-x11[617]: HostedRendezvous:
>> Connection to [YG9tMT-oUaaq-EDofz9] is from user ""
>> Feb 20 20:36:53 raspberrypi vncserver-x11[617]: Connections: connected:
>> t...@olga.no (from 192.168.50.12::54827)
>> Feb 20 20:37:06 raspberrypi vncserver-x11[617]: Connections:
>> authenticated: t...@olga.no (from 192.168.50.12::54827), as (anonymous)
>> (d permissions)
>> Feb 20 20:37:07 raspberrypi dbus[428]: [system] Activating via systemd:
>> service name='org.freedesktop.ColorManager' unit='colord.service'
>> Feb 20 20:37:07 raspberrypi systemd[1]: Starting Manage, Install and
>> Generate Color Profiles...
>> Feb 20 20:37:08 raspberrypi colord: Using mapping database file
>> /var/lib/colord/mapping.db
>> Feb 20 20:37:08 raspberrypi colord: Using device database file
>> /var/lib/colord/storage.db
>> Feb 20 20:37:08 raspberrypi colord: Using profile database file
>> /var/lib/colord/storage.db
>> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_scanner.so
>> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_sane.so
>> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_camera.so
>> Feb 20 20:37:08 raspberrypi colord: Daemon ready for requests
>> Feb 20 20:37:08 raspberrypi dbus[428]: [system] Successfully activated
>> service 'org.freedesktop.ColorManager'
>> Feb 20 20:37:08 raspberrypi systemd[1]: Started Manage, Install and
>> Generate Color Profiles.
>> Feb 20 20:37:08 raspberrypi colord: Profile added:
>> ES3451_MFP(PCL)_via_VNC_from_THINK2-Gray..
>> Feb 20 20:37:08 raspberrypi colord: Profile added:
>> ES3451_MFP(PCL)_via_VNC_from_THINK2-CMYK..
>> Feb 20 20:37:08 raspberrypi colord[1894]: (colord:1894): Cd-WARNING **:
>> failed to get session [pid 511]: Unknown error -2
>> Feb 20 20:37:08 raspberrypi colord: Device added:
>> cups-ES3451_MFP(PCL)_via_VNC_from_THINK2
>> Feb 20 20:37:08 raspberrypi kernel: [  366.331551] warning: process
>> `colord-sane' used the deprecated sysctl system call with 8.1.2.
>> Feb 20 20:37:08 raspberrypi colord-sane: [bjnp] create_broadcast_socket:
>> bind socket to local address failed - Cannot assign requested address
>> Feb 20 20:37:25 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:37:25 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Mon Feb 20 20:37:55 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Feb 20 20:38:26 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Mon Feb 20 20:39:26 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Feb 20 20:39:13 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:39:18 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:39:23 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
>> router available
>> Feb 20 20:39:40 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No
>> Addresses Available
>> Feb 

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Andrew Milner]

Have you connected the weather station to the Pi??  The log is saying that 
weewx cannot find the weather station plugged into the USB.

If you want to run weewx without a weather station connected to the RPi you 
must select 'simulator' as the station type.

If you select a station type of WMR300 - as you have done - then the 
station must be connected to the RPi for weewx to be able to run.




On Tuesday, 21 February 2017 08:35:56 UTC+2, Torbjørn Aasen wrote:

> Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:35:21 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:35:24 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No Addresses 
> Available
> Feb 20 20:36:02 raspberrypi vncserver-x11-serviced[524]: executing 
> SUDO_LAUNCHCMD: gksudo -D 'VNC Server - sudo password required' -- 
> '/usr/bin/vncpipehelper' '-hash' 'b339b13545b35610a9bb03a210ce6812e39aaa83' 
> '/tmp/.vnc-1000/vncserverui-service.vncpipehelper.173669680' 
> '/usr/bin/vncserver-x11-core' '-service' '-configHelper'
> Feb 20 20:36:02 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Mon Feb 20 20:36:32 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Feb 20 20:36:40 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:36:40 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Mon Feb 20 20:37:10 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Feb 20 20:36:44 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:36:49 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:36:53 raspberrypi vncserver-x11[617]: HostedRendezvous: 
> Connection to [YG9tMT-oUaaq-EDofz9] is from user " >"
> Feb 20 20:36:53 raspberrypi vncserver-x11[617]: Connections: connected: 
> t...@olga.no  (from 192.168.50.12::54827)
> Feb 20 20:37:06 raspberrypi vncserver-x11[617]: Connections: 
> authenticated: t...@olga.no  (from 192.168.50.12::54827), as 
> (anonymous) (d permissions)
> Feb 20 20:37:07 raspberrypi dbus[428]: [system] Activating via systemd: 
> service name='org.freedesktop.ColorManager' unit='colord.service'
> Feb 20 20:37:07 raspberrypi systemd[1]: Starting Manage, Install and 
> Generate Color Profiles...
> Feb 20 20:37:08 raspberrypi colord: Using mapping database file 
> /var/lib/colord/mapping.db
> Feb 20 20:37:08 raspberrypi colord: Using device database file 
> /var/lib/colord/storage.db
> Feb 20 20:37:08 raspberrypi colord: Using profile database file 
> /var/lib/colord/storage.db
> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_scanner.so
> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_sane.so
> Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_camera.so
> Feb 20 20:37:08 raspberrypi colord: Daemon ready for requests
> Feb 20 20:37:08 raspberrypi dbus[428]: [system] Successfully activated 
> service 'org.freedesktop.ColorManager'
> Feb 20 20:37:08 raspberrypi systemd[1]: Started Manage, Install and 
> Generate Color Profiles.
> Feb 20 20:37:08 raspberrypi colord: Profile added: 
> ES3451_MFP(PCL)_via_VNC_from_THINK2-Gray..
> Feb 20 20:37:08 raspberrypi colord: Profile added: 
> ES3451_MFP(PCL)_via_VNC_from_THINK2-CMYK..
> Feb 20 20:37:08 raspberrypi colord[1894]: (colord:1894): Cd-WARNING **: 
> failed to get session [pid 511]: Unknown error -2
> Feb 20 20:37:08 raspberrypi colord: Device added: 
> cups-ES3451_MFP(PCL)_via_VNC_from_THINK2
> Feb 20 20:37:08 raspberrypi kernel: [  366.331551] warning: process 
> `colord-sane' used the deprecated sysctl system call with 8.1.2.
> Feb 20 20:37:08 raspberrypi colord-sane: [bjnp] create_broadcast_socket: 
> bind socket to local address failed - Cannot assign requested address
> Feb 20 20:37:25 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:37:25 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Mon Feb 20 20:37:55 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Feb 20 20:38:26 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Mon Feb 20 20:39:26 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Feb 20 20:39:13 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:39:18 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:39:23 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca 
> router available
> Feb 20 20:39:40 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No Addresses 
> Available
> Feb 20 20:39:40 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Mon Feb 20 20:40:40 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Feb 20 20:40:41 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Mon Feb 20 20:41:41 2017 [try 

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Torbjørn Aasen]

Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:35:16 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:35:21 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:35:24 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No Addresses
Available
Feb 20 20:36:02 raspberrypi vncserver-x11-serviced[524]: executing
SUDO_LAUNCHCMD: gksudo -D 'VNC Server - sudo password required' --
'/usr/bin/vncpipehelper' '-hash' 'b339b13545b35610a9bb03a210ce6812e39aaa83'
'/tmp/.vnc-1000/vncserverui-service.vncpipehelper.173669680'
'/usr/bin/vncserver-x11-core' '-service' '-configHelper'
Feb 20 20:36:02 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Mon Feb 20 20:36:32 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 20 20:36:40 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:36:40 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Mon Feb 20 20:37:10 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 20 20:36:44 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:36:49 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:36:53 raspberrypi vncserver-x11[617]: HostedRendezvous:
Connection to [YG9tMT-oUaaq-EDofz9] is from user ""
Feb 20 20:36:53 raspberrypi vncserver-x11[617]: Connections: connected:
t...@olga.no (from 192.168.50.12::54827)
Feb 20 20:37:06 raspberrypi vncserver-x11[617]: Connections: authenticated:
t...@olga.no (from 192.168.50.12::54827), as (anonymous) (d permissions)
Feb 20 20:37:07 raspberrypi dbus[428]: [system] Activating via systemd:
service name='org.freedesktop.ColorManager' unit='colord.service'
Feb 20 20:37:07 raspberrypi systemd[1]: Starting Manage, Install and
Generate Color Profiles...
Feb 20 20:37:08 raspberrypi colord: Using mapping database file
/var/lib/colord/mapping.db
Feb 20 20:37:08 raspberrypi colord: Using device database file
/var/lib/colord/storage.db
Feb 20 20:37:08 raspberrypi colord: Using profile database file
/var/lib/colord/storage.db
Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_scanner.so
Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_sane.so
Feb 20 20:37:08 raspberrypi colord: loaded plugin libcd_plugin_camera.so
Feb 20 20:37:08 raspberrypi colord: Daemon ready for requests
Feb 20 20:37:08 raspberrypi dbus[428]: [system] Successfully activated
service 'org.freedesktop.ColorManager'
Feb 20 20:37:08 raspberrypi systemd[1]: Started Manage, Install and
Generate Color Profiles.
Feb 20 20:37:08 raspberrypi colord: Profile added:
ES3451_MFP(PCL)_via_VNC_from_THINK2-Gray..
Feb 20 20:37:08 raspberrypi colord: Profile added:
ES3451_MFP(PCL)_via_VNC_from_THINK2-CMYK..
Feb 20 20:37:08 raspberrypi colord[1894]: (colord:1894): Cd-WARNING **:
failed to get session [pid 511]: Unknown error -2
Feb 20 20:37:08 raspberrypi colord: Device added:
cups-ES3451_MFP(PCL)_via_VNC_from_THINK2
Feb 20 20:37:08 raspberrypi kernel: [  366.331551] warning: process
`colord-sane' used the deprecated sysctl system call with 8.1.2.
Feb 20 20:37:08 raspberrypi colord-sane: [bjnp] create_broadcast_socket:
bind socket to local address failed - Cannot assign requested address
Feb 20 20:37:25 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:37:25 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Mon Feb 20 20:37:55 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 20 20:38:26 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Mon Feb 20 20:39:26 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 20 20:39:13 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:39:18 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:39:23 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:39:40 raspberrypi dhcpcd[436]: wlan0: DHCPv6 REPLY: No Addresses
Available
Feb 20 20:39:40 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Mon Feb 20 20:40:40 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 20 20:40:41 raspberrypi rsyslogd-2007: action 'action 17' suspended,
next retry is Mon Feb 20 20:41:41 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 20 20:40:51 raspberrypi dbus[428]: [system] Activating via systemd:
service name='org.freedesktop.PackageKit' unit='packagekit.service'
Feb 20 20:40:51 raspberrypi systemd[1]: Starting PackageKit Daemon...
Feb 20 20:40:51 raspberrypi PackageKit: daemon start
Feb 20 20:40:51 raspberrypi dbus[428]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 20 20:40:51 raspberrypi systemd[1]: Started PackageKit Daemon.
Feb 20 20:41:20 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:41:20 raspberrypi dhcpcd[436]: wlan0: fe80::222:7ff:fe4a:ebca
router available
Feb 20 20:41:20 raspberrypi dhcpcd[436]: 

Re: [weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[mwall]

i found it helpful to configure the broker so that it publishes using 
websockets.  then you can use a web browser to see what is happening.  this 
is especially useful when you're trying to decode someone else's topic 
hierarchy, or to figure out why your own topics are not showing up where 
you think they should be.

the hivemq folks wrote one of the first ones, which many people have now 
embedded:

http://www.hivemq.com/blog/full-featured-mqtt-client-browser

http://www.espert.io/mqtt/index.html

but many other browser-based clients are out there:

http://mitsuruog.github.io/what-mqtt/

https://www.cloudmqtt.com/docs-websocket.html

if you're using the mosquitto broker, you'll have to compile it with 
websocket compatibility.  but once you do that, enabling websockets is just 
a matter of making the broker listen on the websocket port.

m

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[Bill Morrow]

That "Socket error" may be an MQTT protocol version mismatch.

Try changing the version which is hardcoded in my driver
import paho.mqtt.client as mqtt

self.client = mqtt.Client(client_id=self.client_id, protocol=mqtt.MQTTv31)

to match what your library and MQTT broke Mosquitto support. You can check 
your MQTT version in this file:
/usr/local/lib/python2.7/dist-packages/paho/mqtt/client.py
or an equivalent depending on what OS you are using. I also believe I have 
to manually build mosquitto-1.4.10 to get the connection to work.

Another possibility is that you have Mosquitto configured to NOT need user 
and password.

On Monday, 20 February 2017 17:34:01 UTC-4, wysiwyg wrote:
>
>
>> 1487626012: New connection from 192.168.1.180 on port 1883.
> 1487626012: Socket error on client , disconnecting.
> 1487626042: New connection from 192.168.1.180 on port 1883.
> 1487626042: Socket error on client , disconnecting.
>
>
> disconnection occurs when I reload weewx configuration (weewx restart)
>
>
>
>
>  
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[Bill Morrow]

OK, so no issues with MQTT.

I originally was not using the username/password facility in Mosquitto. You
could try that, and simply comment out the lines in the driver.

I think this is the setting in mosquitto.conf
allow_anonymous true


Thank you for trying the driver. When we find out why it is not working, I
will document better or improve the code to make it smoother for future
users.


On Mon, Feb 20, 2017 at 5:36 PM, wysiwyg  wrote:

> and I forget to say  I use "mqtt dashboard" android app to send the
> following text with weather topic:
>
> TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT:
> 4.44,IRRA:12,BATV:974,PHOV:673,SYST:33.20,WIND: 0.0,WDIR: 0.0
>
> I publish the text manually by clicking on "publish" button of the app.
> The text is send (and well received as I also subscribe to the topic in
> the same app on an other tablet)
>
> Le lundi 20 février 2017 22:34:01 UTC+1, wysiwyg a écrit :
>>
>> for information: syslog, I have only this every 1s (my poll interval)
>>>
>> Feb 20 21:31:59 localhost weewx[9448]: wxMesh: Sleeping for 1
>> Feb 20 21:32:00 localhost weewx[9448]: wxMesh: Working on payload : Empty
>> Feb 20 21:32:00 localhost weewx[9448]: wxMesh: Sleeping for 1
>> Feb 20 21:32:01 localhost weewx[9448]: wxMesh: Working on payload : Empty
>> Feb 20 21:32:01 localhost weewx[9448]: wxMesh: Sleeping for 1
>>
>>
>> on /var/log/mosquitto/mosquitto.log:
>>
>>
>> 1487626012: New connection from 192.168.1.180 on port 1883.
>> 1487626012: Socket error on client , disconnecting.
>> 1487626042: New connection from 192.168.1.180 on port 1883.
>> 1487626042: Socket error on client , disconnecting.
>>
>>
>> disconnection occurs when I reload weewx configuration (weewx restart)
>>
>>
>>
>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/zhl4I7oRtt8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[Bill Morrow]

Oh, make sure you connect as a different client if you use that monitoring
script. Otherwise it will take all the traffic from weewx!

On Mon, Feb 20, 2017 at 6:44 PM, Bill Morrow  wrote:

> Frederic, these two lines you have highlighted
> self.username = stn_dict.get('username', 'XXX')
> self.password = stn_dict.get('password', 'password')
> should pick up the username and password from the python "dictionary
> " that is populated
> when weewx reads your weewx.conf file on startup.
>
> Do you get any sort of error message, either from weewx or Mosquitto? In
> weewx.conf, you can set
>
>> # Set to 1 for extra debug info, otherwise comment it out or set to zero.
>> debug = 1
>
> and it will log much more information about what it is doing.
>
> Try adding this line right after the two highlighted
> self.username = stn_dict.get('username', 'XXX')
> self.password = stn_dict.get('password', 'password')
> logdbg("Set username to %s and password to %s" % (self.username,
> self.password))
>
> In Mosquitto, you have to explicitly set logging to go to syslog,
> otherwise it is only to stdout. Also, I recall having problems with the
> wrong version of the MQTT protocol when I started. I might have had to
> build a newer version of Mosquitto manually, instead of using the one which
> came with the running version of the OS.
>
> I'm attaching a small python script which should watch everything going
> through your Mosquitto broker.
>
> On Mon, Feb 20, 2017 at 5:24 PM, wysiwyg  wrote:
>
>> Bill,
>>
>> I have some troubles to make the driver work.
>> While look at the code, I have the feeling that the username / password
>> from weewx.conf are not used ?
>>
>> I tried something, but seems not working better.
>>
>> here is my test (it's based on other lines of the driver, I try to do
>> something similar, but as I said, I know nothing about python)
>>
>>
>>  def __init__(self, **stn_dict):
>> # where to find the data file
>> self.host = stn_dict.get('host', 'localhost')
>> self.topic = stn_dict.get('topic', 'weather')
>> self.username = stn_dict.get('username', 'XXX')
>> self.password = stn_dict.get('password', 'password')
>> # how often to poll the weather data file, seconds
>> self.poll_interval = float(stn_dict.get('poll_interval', 5.0))
>> # mapping from variable names to weewx names
>> self.label_map = stn_dict.get('label_map', {})
>>
>>
>> loginf("host is %s" % self.host)
>> loginf("topic is %s" % self.topic)
>> loginf("polling interval is %s" % self.poll_interval)
>> loginf('label map is %s' % self.label_map)
>>
>>
>> self.payload = "Empty"
>> #self.payloadList = [payload]
>> self.client = mqtt.Client(client_id="XXX", protocol=mqtt.MQTTv31)
>>
>>
>> #self.client.on_connect = self.on_connect
>> self.client.on_message = self.on_message
>>
>>
>> self.client.username_pw_set(self.username, self.password)
>> self.client.connect(self.host, 1883, 60)
>> self.client.subscribe(self.topic, qos=1)
>>
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/weewx-user/zhl4I7oRtt8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[Bill Morrow]

Frederic, these two lines you have highlighted
self.username = stn_dict.get('username', 'XXX')
self.password = stn_dict.get('password', 'password')
should pick up the username and password from the python "dictionary
" that is populated when
weewx reads your weewx.conf file on startup.

Do you get any sort of error message, either from weewx or Mosquitto? In
weewx.conf, you can set

> # Set to 1 for extra debug info, otherwise comment it out or set to zero.
> debug = 1

and it will log much more information about what it is doing.

Try adding this line right after the two highlighted
self.username = stn_dict.get('username', 'XXX')
self.password = stn_dict.get('password', 'password')
logdbg("Set username to %s and password to %s" % (self.username,
self.password))

In Mosquitto, you have to explicitly set logging to go to syslog, otherwise
it is only to stdout. Also, I recall having problems with the wrong version
of the MQTT protocol when I started. I might have had to build a newer
version of Mosquitto manually, instead of using the one which came with the
running version of the OS.

I'm attaching a small python script which should watch everything going
through your Mosquitto broker.

On Mon, Feb 20, 2017 at 5:24 PM, wysiwyg  wrote:

> Bill,
>
> I have some troubles to make the driver work.
> While look at the code, I have the feeling that the username / password
> from weewx.conf are not used ?
>
> I tried something, but seems not working better.
>
> here is my test (it's based on other lines of the driver, I try to do
> something similar, but as I said, I know nothing about python)
>
>
>  def __init__(self, **stn_dict):
> # where to find the data file
> self.host = stn_dict.get('host', 'localhost')
> self.topic = stn_dict.get('topic', 'weather')
> self.username = stn_dict.get('username', 'XXX')
> self.password = stn_dict.get('password', 'password')
> # how often to poll the weather data file, seconds
> self.poll_interval = float(stn_dict.get('poll_interval', 5.0))
> # mapping from variable names to weewx names
> self.label_map = stn_dict.get('label_map', {})
>
>
> loginf("host is %s" % self.host)
> loginf("topic is %s" % self.topic)
> loginf("polling interval is %s" % self.poll_interval)
> loginf('label map is %s' % self.label_map)
>
>
> self.payload = "Empty"
> #self.payloadList = [payload]
> self.client = mqtt.Client(client_id="XXX", protocol=mqtt.MQTTv31)
>
>
> #self.client.on_connect = self.on_connect
> self.client.on_message = self.on_message
>
>
> self.client.username_pw_set(self.username, self.password)
> self.client.connect(self.host, 1883, 60)
> self.client.subscribe(self.topic, qos=1)
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/zhl4I7oRtt8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.
import time
import thread
import paho.mqtt.client as mqtt


# The callback for when the client receives a CONNACK response from the server.
def on_connect(client, userdata, rc):
print("Connected with result code "+str(rc))
# Subscribing in on_connect() means that if we lose the connection and
# reconnect then subscriptions will be renewed.
client.subscribe("#")

# The callback for when a PUBLISH message is received from the server.
def on_message(client, userdata, msg):
print(msg.topic+" "+str(msg.payload))
#print("In thread %s" % thread.get_ident())
userdata[0] = str(msg.topic)+"->"+str(msg.payload)

data = "   data  "
list = [data]
print "Initializing list to %s" % list[0]
client = mqtt.Client(client_id="surveyLooper", userdata = list, protocol=mqtt.MQTTv31)

client.on_connect = on_connect
client.on_message = on_message

client.username_pw_set("user", "passwd")
client.connect("localhost", 1883, 60)
client.loop_start()
oldmsg = ''

while(1) :
  time.sleep(1)
  #print("Do some other stuff in this thread %s" % thread.get_ident() )
  if list[0] != oldmsg :
  oldmsg = list[0]
  print "List is now %s " % list[0]

Re: [weewx-user] Re: Steel Series Gauges and RealTime update - 2.5 second interval - how?

[Devonian]

Dropped the new file in place, stop/start weewx and it looks good to me 
Gary.
Online in the usual place if anyone is interested...

http://www.nthead.co.uk/ss/index.html

Nigel.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[Devonian]

Why do I want rapidly changing gauge data?

a) Because I can.
b) So I can sit with my ipad in my lounge and watch the dials move during 
gusty/stormy conditions and not have to stand at my console to see the same.
c) When I am away from home, I can watch them from afar.

Not worried whether anyone else is interested in my site or not - it's a 
personal thing.

@Gary, thanks for your time and effort given so freely, it's refreshing in 
this day and age (along with the other developers).

Nigel.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[tempus]

Sorry, I neglected to provide this link to the development site in the post 
above.

http://www.lablibrary.com/ss/

Bob

On Monday, February 20, 2017 at 2:09:20 PM UTC-8, tempus wrote:
>
> The gauges show both average and gust data, neither of which are 'fake 
> weather.'  Peak gusts are important to aircraft pilots and mariners.  They 
> also are important to analyzing and predicting changing weather 
> conditions.  Wind speeds and directions averaged over various past time 
> intervals, ranging from minutes to months or even years are important to 
> other kinds of analysis.
>
> I have temporarily enabled public access to a software development site 
> where you can see gauges updating at 3-second intervals, although the wind 
> is very light right now and not as interesting as it often is. If website 
> visitors think near-real-time weather information is interesting after the 
> presentation is finished, they will be able to watch it.  If they don't, 
> they will be free to ignore it and get their weather information somewhere 
> else.  Some people will see value in near-real-time information. Others 
> won't.
>
> Bob
>
> On Monday, February 20, 2017 at 11:53:51 AM UTC-8, Andrew Milner wrote:
>>
>> @ tempus:
>>
>> 1.  Windspeeds do indeed change rapidly, which is why there is usually a 
>> 10 minute averaging period to cover reported wind speeds.
>>
>> Measuring gusts and wind intensity
>>
>> Because wind is an element that varies rapidly over very short periods of 
>> time it is sampled at high frequency (*e**v**e**r**y 0.25 sec*) to 
>> capture the intensity of gusts, or short-lived peaks in speed, which 
>> inflict greatest damage in storms. The gust speed and direction are defined 
>> by the maximum three second average wind speed occurring in any period.
>>
>> A better measure of the overall wind intensity is defined by the average 
>> speed and direction over the ten minute period leading up to the reporting 
>> time. Mean wind over other averaging periods may also be calculated. A gale 
>> is defined as a surface wind of mean speed of 34-40 knots, averaged over a 
>> period of ten minutes. Terms such as 'severe gale', 'storm', etc are also 
>> used to describe winds of 41 knots or greater.
>>
>>
>> 2.  What cobblers - rapidly changing gauges could be reporting conditions 
>> now, 5 minutes ago, an hour ago - or even yesterday.  They do not 
>> demonstrate or prove anything apart from maybe the speed of an internet 
>> connection.  If one can have 'fake news', one can have certainly have 'fake 
>> weather' also!!!
>>
>>
>>
>>
>>
>> On Monday, 20 February 2017 20:57:26 UTC+2, tempus wrote:
>>
>>> 1) Wind speed and direction data tends to change radically from 
>>> second-to-second and is interesting to watch, especially in coastal areas 
>>> where high wind speeds often cause significant property damage and even 
>>> loss of life.
>>>
>>> 2) Rapidly changing gauges quickly demonstrate to website visitors that 
>>> they are in fact watching near-real-time data.
>>>
>>> Bob
>>>
>>> On Monday, February 20, 2017 at 10:23:14 AM UTC-8, Andrew Milner wrote:

 I would prefer to ask the questions - why am I providing 3 second 
 updates? What practical value do 3 second updates have for most users??  
 What is the point??



 On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:

> This is merely a suggestion for consideration.
>
> Space characters are commonly used within and between key-value pairs 
> in associative arrays to improve human readability.  Because 
> 'gauge-data.txt' human-readability isn't important, the file could be 
> reduced in size 158 bytes, plus another 15 bytes if spaces after commas 
> in 
> the "WindRoseData" string were removed, which would make the file 10 
> percent smaller.
>
> 173 bytes doesn't seem like much. However, with 3-second updates there 
> will 86400 / 3 = 28,800 file transmissions per day to each concurrent 
> user.  28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user. 
>  
> It is not uncommon for individual pages at active websites to have large 
> numbers of concurrent visitors, so why waste the bandwidth and processing 
> time?
>
> Bob
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[tempus]

The gauges show both average and gust data, neither of which are 'fake 
weather.'  Peak gusts are important to aircraft pilots and mariners.  They 
also are important to analyzing and predicting changing weather 
conditions.  Wind speeds and directions averaged over various past time 
intervals, ranging from minutes to months or even years are important to 
other kinds of analysis.

I have temporarily enabled public access to a software development site 
where you can see gauges updating at 3-second intervals, although the wind 
is very light right now and not as interesting as it often is. If website 
visitors think near-real-time weather information is interesting after the 
presentation is finished, they will be able to watch it.  If they don't, 
they will be free to ignore it and get their weather information somewhere 
else.  Some people will see value in near-real-time information. Others 
won't.

Bob

On Monday, February 20, 2017 at 11:53:51 AM UTC-8, Andrew Milner wrote:
>
> @ tempus:
>
> 1.  Windspeeds do indeed change rapidly, which is why there is usually a 
> 10 minute averaging period to cover reported wind speeds.
>
> Measuring gusts and wind intensity
>
> Because wind is an element that varies rapidly over very short periods of 
> time it is sampled at high frequency (*e**v**e**r**y 0.25 sec*) to 
> capture the intensity of gusts, or short-lived peaks in speed, which 
> inflict greatest damage in storms. The gust speed and direction are defined 
> by the maximum three second average wind speed occurring in any period.
>
> A better measure of the overall wind intensity is defined by the average 
> speed and direction over the ten minute period leading up to the reporting 
> time. Mean wind over other averaging periods may also be calculated. A gale 
> is defined as a surface wind of mean speed of 34-40 knots, averaged over a 
> period of ten minutes. Terms such as 'severe gale', 'storm', etc are also 
> used to describe winds of 41 knots or greater.
>
>
> 2.  What cobblers - rapidly changing gauges could be reporting conditions 
> now, 5 minutes ago, an hour ago - or even yesterday.  They do not 
> demonstrate or prove anything apart from maybe the speed of an internet 
> connection.  If one can have 'fake news', one can have certainly have 'fake 
> weather' also!!!
>
>
>
>
>
> On Monday, 20 February 2017 20:57:26 UTC+2, tempus wrote:
>
>> 1) Wind speed and direction data tends to change radically from 
>> second-to-second and is interesting to watch, especially in coastal areas 
>> where high wind speeds often cause significant property damage and even 
>> loss of life.
>>
>> 2) Rapidly changing gauges quickly demonstrate to website visitors that 
>> they are in fact watching near-real-time data.
>>
>> Bob
>>
>> On Monday, February 20, 2017 at 10:23:14 AM UTC-8, Andrew Milner wrote:
>>>
>>> I would prefer to ask the questions - why am I providing 3 second 
>>> updates? What practical value do 3 second updates have for most users??  
>>> What is the point??
>>>
>>>
>>>
>>> On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:
>>>
 This is merely a suggestion for consideration.

 Space characters are commonly used within and between key-value pairs 
 in associative arrays to improve human readability.  Because 
 'gauge-data.txt' human-readability isn't important, the file could be 
 reduced in size 158 bytes, plus another 15 bytes if spaces after commas in 
 the "WindRoseData" string were removed, which would make the file 10 
 percent smaller.

 173 bytes doesn't seem like much. However, with 3-second updates there 
 will 86400 / 3 = 28,800 file transmissions per day to each concurrent 
 user.  28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user.  
 It is not uncommon for individual pages at active websites to have large 
 numbers of concurrent visitors, so why waste the bandwidth and processing 
 time?

 Bob

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[wysiwyg]

and I forget to say  I use "mqtt dashboard" android app to send the 
following text with weather topic:

TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 
4.44,IRRA:12,BATV:974,PHOV:673,SYST:33.20,WIND: 0.0,WDIR: 0.0

I publish the text manually by clicking on "publish" button of the app.
The text is send (and well received as I also subscribe to the topic in the 
same app on an other tablet)

Le lundi 20 février 2017 22:34:01 UTC+1, wysiwyg a écrit :
>
> for information: syslog, I have only this every 1s (my poll interval)
>>
> Feb 20 21:31:59 localhost weewx[9448]: wxMesh: Sleeping for 1
> Feb 20 21:32:00 localhost weewx[9448]: wxMesh: Working on payload : Empty
> Feb 20 21:32:00 localhost weewx[9448]: wxMesh: Sleeping for 1
> Feb 20 21:32:01 localhost weewx[9448]: wxMesh: Working on payload : Empty
> Feb 20 21:32:01 localhost weewx[9448]: wxMesh: Sleeping for 1
>
>
> on /var/log/mosquitto/mosquitto.log:
>
>
> 1487626012: New connection from 192.168.1.180 on port 1883.
> 1487626012: Socket error on client , disconnecting.
> 1487626042: New connection from 192.168.1.180 on port 1883.
> 1487626042: Socket error on client , disconnecting.
>
>
> disconnection occurs when I reload weewx configuration (weewx restart)
>
>
>
>
>  
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[wysiwyg]

>
> for information: syslog, I have only this every 1s (my poll interval)
>
Feb 20 21:31:59 localhost weewx[9448]: wxMesh: Sleeping for 1
Feb 20 21:32:00 localhost weewx[9448]: wxMesh: Working on payload : Empty
Feb 20 21:32:00 localhost weewx[9448]: wxMesh: Sleeping for 1
Feb 20 21:32:01 localhost weewx[9448]: wxMesh: Working on payload : Empty
Feb 20 21:32:01 localhost weewx[9448]: wxMesh: Sleeping for 1


on /var/log/mosquitto/mosquitto.log:


1487626012: New connection from 192.168.1.180 on port 1883.
1487626012: Socket error on client , disconnecting.
1487626042: New connection from 192.168.1.180 on port 1883.
1487626042: Socket error on client , disconnecting.


disconnection occurs when I reload weewx configuration (weewx restart)




 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[wysiwyg]

Bill,

I have some troubles to make the driver work.
While look at the code, I have the feeling that the username / password 
from weewx.conf are not used ?

I tried something, but seems not working better.

here is my test (it's based on other lines of the driver, I try to do 
something similar, but as I said, I know nothing about python)


 def __init__(self, **stn_dict):
# where to find the data file
self.host = stn_dict.get('host', 'localhost')
self.topic = stn_dict.get('topic', 'weather')
self.username = stn_dict.get('username', 'XXX')
self.password = stn_dict.get('password', 'password')
# how often to poll the weather data file, seconds
self.poll_interval = float(stn_dict.get('poll_interval', 5.0))
# mapping from variable names to weewx names
self.label_map = stn_dict.get('label_map', {})


loginf("host is %s" % self.host)
loginf("topic is %s" % self.topic)
loginf("polling interval is %s" % self.poll_interval)
loginf('label map is %s' % self.label_map)


self.payload = "Empty"
#self.payloadList = [payload]
self.client = mqtt.Client(client_id="XXX", protocol=mqtt.MQTTv31)


#self.client.on_connect = self.on_connect
self.client.on_message = self.on_message


self.client.username_pw_set(self.username, self.password)
self.client.connect(self.host, 1883, 60)
self.client.subscribe(self.topic, qos=1)



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[Andrew Milner]

@ tempus:

1.  Windspeeds do indeed change rapidly, which is why there is usually a 10 
minute averaging period to cover reported wind speeds.

Measuring gusts and wind intensity

Because wind is an element that varies rapidly over very short periods of 
time it is sampled at high frequency (*e**v**e**r**y 0.25 sec*) to capture 
the intensity of gusts, or short-lived peaks in speed, which inflict 
greatest damage in storms. The gust speed and direction are defined by the 
maximum three second average wind speed occurring in any period.

A better measure of the overall wind intensity is defined by the average 
speed and direction over the ten minute period leading up to the reporting 
time. Mean wind over other averaging periods may also be calculated. A gale 
is defined as a surface wind of mean speed of 34-40 knots, averaged over a 
period of ten minutes. Terms such as 'severe gale', 'storm', etc are also 
used to describe winds of 41 knots or greater.


2.  What cobblers - rapidly changing gauges could be reporting conditions 
now, 5 minutes ago, an hour ago - or even yesterday.  They do not 
demonstrate or prove anything apart from maybe the speed of an internet 
connection.  If one can have 'fake news', one can have certainly have 'fake 
weather' also!!!





On Monday, 20 February 2017 20:57:26 UTC+2, tempus wrote:

> 1) Wind speed and direction data tends to change radically from 
> second-to-second and is interesting to watch, especially in coastal areas 
> where high wind speeds often cause significant property damage and even 
> loss of life.
>
> 2) Rapidly changing gauges quickly demonstrate to website visitors that 
> they are in fact watching near-real-time data.
>
> Bob
>
> On Monday, February 20, 2017 at 10:23:14 AM UTC-8, Andrew Milner wrote:
>>
>> I would prefer to ask the questions - why am I providing 3 second 
>> updates? What practical value do 3 second updates have for most users??  
>> What is the point??
>>
>>
>>
>> On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:
>>
>>> This is merely a suggestion for consideration.
>>>
>>> Space characters are commonly used within and between key-value pairs in 
>>> associative arrays to improve human readability.  Because 'gauge-data.txt' 
>>> human-readability isn't important, the file could be reduced in size 158 
>>> bytes, plus another 15 bytes if spaces after commas in the "WindRoseData" 
>>> string were removed, which would make the file 10 percent smaller.
>>>
>>> 173 bytes doesn't seem like much. However, with 3-second updates there 
>>> will 86400 / 3 = 28,800 file transmissions per day to each concurrent 
>>> user.  28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user.  
>>> It is not uncommon for individual pages at active websites to have large 
>>> numbers of concurrent visitors, so why waste the bandwidth and processing 
>>> time?
>>>
>>> Bob
>>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[vince]

On Monday, February 20, 2017 at 9:33:27 AM UTC-8, tempus wrote:
>
> This is merely a suggestion for consideration.
> 173 bytes doesn't seem like much. However, with 3-second updates there 
> will 86400 / 3 = 28,800 file transmissions per day to each concurrent 
> user.  28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user.  
> It is not uncommon for individual pages at active websites to have large 
> numbers of concurrent visitors, so why waste the bandwidth and processing 
> time?
>
>
I'd offer a counter-suggestion mentioning that this is not 1988 with 386SX 
processors and 1200 baud modems.   You'd need an incredibly large number of 
concurrent users to even notice any difference.  I'd suspect that no weewx 
site in the world has enough simultaneous users to make that 
over-optimization necessary.

Every piece of software has a balance in how it's optimized versus 
size/speed/supportability.  A little whitespace isn't killing anybody if it 
makes the product more supportable.

And you can of course modify 'your' system to strip whitespace out in 
'your' templates if you feel the need is so strong.

 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Realtime Gauge-Data Extension 0.2.4 'gauge-data.txt' Issues

[tempus]

'gauge-data.txt' contains *cloudbaseunit": "m"*.

In the U.S. the Cloud Base unit-of-measure should be foot.

Bob

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[tempus]

1) Wind speed and direction data tends to change radically from 
second-to-second and is interesting to watch, especially in coastal areas 
where high wind speeds often cause significant property damage and even 
loss of life.

2) Rapidly changing gauges quickly demonstrate to website visitors that 
they are in fact watching near-real-time data.

Bob

On Monday, February 20, 2017 at 10:23:14 AM UTC-8, Andrew Milner wrote:
>
> I would prefer to ask the questions - why am I providing 3 second updates? 
> What practical value do 3 second updates have for most users??  What is the 
> point??
>
>
>
> On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:
>
>> This is merely a suggestion for consideration.
>>
>> Space characters are commonly used within and between key-value pairs in 
>> associative arrays to improve human readability.  Because 'gauge-data.txt' 
>> human-readability isn't important, the file could be reduced in size 158 
>> bytes, plus another 15 bytes if spaces after commas in the "WindRoseData" 
>> string were removed, which would make the file 10 percent smaller.
>>
>> 173 bytes doesn't seem like much. However, with 3-second updates there 
>> will 86400 / 3 = 28,800 file transmissions per day to each concurrent 
>> user.  28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user.  
>> It is not uncommon for individual pages at active websites to have large 
>> numbers of concurrent visitors, so why waste the bandwidth and processing 
>> time?
>>
>> Bob
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Cant find file:///var/www/html/weewx/index.html

[Torbjørn Aasen]

Hi
I am completely new to this.
I did not find the log file either.
Have restarted the new NOOBS now.
Going to try and install once more before I enter the following description.

2017-02-18 21:10 GMT+01:00 mwall :

>
>
> On Saturday, February 18, 2017 at 2:50:35 PM UTC-5, Torbjørn Aasen wrote:
>>
>> I have loaded the latest Noobs and Weewx twice on my Raspberry PI 3.
>> When I follow the installation guide it all seems to go right for
>> themselves but this file can not I find afterwards.
>> I've never done this before so there are great opportunities that I'm
>> doing something wrong.
>> I have not connected weather station to PI yet.
>>
>> I use this manual: http://www.weewx.com/docs/apt-get.htm
>>
>> But this can not I find afterwards: file: ///var/www/html/weewx/index.ht
>> ml
>>
>
> torbjørn,
>
> what do you see in the log, starting just before the time when you started
> weewx until at least 5 minutes later, possibly 30 minutes later?
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/6-NAVeNuNME/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 









Med vennlig hilsen

Torbjørn Aasen

Mob: 92092037



Carpe Diem

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[Andrew Milner]

I would prefer to ask the questions - why am I providing 3 second updates? 
What practical value do 3 second updates have for most users??  What is the 
point??



On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:

> This is merely a suggestion for consideration.
>
> Space characters are commonly used within and between key-value pairs in 
> associative arrays to improve human readability.  Because 'gauge-data.txt' 
> human-readability isn't important, the file could be reduced in size 158 
> bytes, plus another 15 bytes if spaces after commas in the "WindRoseData" 
> string were removed, which would make the file 10 percent smaller.
>
> 173 bytes doesn't seem like much. However, with 3-second updates there 
> will 86400 / 3 = 28,800 file transmissions per day to each concurrent 
> user.  28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user.  
> It is not uncommon for individual pages at active websites to have large 
> numbers of concurrent visitors, so why waste the bandwidth and processing 
> time?
>
> Bob
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[tempus]

This is merely a suggestion for consideration.

Space characters are commonly used within and between key-value pairs in 
associative arrays to improve human readability.  Because 'gauge-data.txt' 
human-readability isn't important, the file could be reduced in size 158 
bytes, plus another 15 bytes if spaces after commas in the "WindRoseData" 
string were removed, which would make the file 10 percent smaller.

173 bytes doesn't seem like much. However, with 3-second updates there will 
86400 / 3 = 28,800 file transmissions per day to each concurrent user.  
28,800 x 173 bytes = 4,982,400 unnecessary bytes-per-day-per-user.  It is 
not uncommon for individual pages at active websites to have large numbers 
of concurrent visitors, so why waste the bandwidth and processing time?

Bob

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[Bill Morrow]

On Monday, 20 February 2017 13:04:47 UTC-4, wysiwyg wrote:
>
> Many thanks for so quick answer and wiki link. I will read this page 
> carefully !
>
> One more question: 
> Would it make sense to use topic instead of all data in one topic ? 
> I mean
> weather/outside/temperature  = 21
> weather/outside/humiduty  = 77
> weather/inside/temperature  = 21
> 
> This is just an open question, I know mqtt since yesterday so, only have a 
> noob point of view :D...
>

Yes, I believe that would be more in keeping with the design of MQTT. I 
have not done it yet, though. I am new to MQTT also, but I like its 
potential.
 

>
>
> I understand your solution for the timestamp. The only issue I see is that 
> it might slightly delay data...weewx will consider reading time as the 
> measurement time which might be a few seconds earlier.
> but it does not seems critical for most measurement.
>

I agree. I might add a realtime clock to my station someday. Currently I am 
working on getting it powered by PV cell.
 

>
> Regarding raingauge, you may know that there are some raingauge with 
> heating function to melt the snow ;-ppp
> More seriously: from what I have seen: there is this Rainwise "1wire" 
> compatible rain gauge. it uses a DS2423 counter IC.
> As far as I understand, this IC just count the ticks: I mean it starts 
> from 0 and just count, always up, never goes down.
>
> Then, you can read it every minute, hour, day to calculate the minute, 
> hourly or daily total rain (for the rainwise, 1 tick = 0.25mm)
> This calculation should be easy to do in an ESP8266 (or anything arduino, 
> whatever like).
> We just need to know how to feed weewx correctly :-)
>
> If I correctly understand (also after looking the "fileparser" driver). 
> The data we have to feed in the driver match the database schemas.
> there is only 2 rain data here.
> ('rainRate', 'REAL'),
> ('rain', 'REAL'),
>
>
>
I know some others have extended the schema, but I think you are on the 
right approach: do some work in the weather station and provide baseline 
data to weewx. 

>
>
>
>
>
>
>
>
>
>
>
>  
>
>
>
>
> Le lundi 20 février 2017 17:13:36 UTC+1, Bill Morrow a écrit :
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[Bill Morrow]

I've removed my user/password information from the github document. Thank
you for alerting me to the goof, Frederic.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system - using wxMesh driver

[wysiwyg]

Many thanks for so quick answer and wiki link. I will read this page 
carefully !

One more question: 
Would it make sense to use topic instead of all data in one topic ? 
I mean
weather/outside/temperature  = 21
weather/outside/humiduty  = 77
weather/inside/temperature  = 21

This is just an open question, I know mqtt since yesterday so, only have a 
noob point of view :D...


I understand your solution for the timestamp. The only issue I see is that 
it might slightly delay data...weewx will consider reading time as the 
measurement time which might be a few seconds earlier.
but it does not seems critical for most measurement.

Regarding raingauge, you may know that there are some raingauge with 
heating function to melt the snow ;-ppp
More seriously: from what I have seen: there is this Rainwise "1wire" 
compatible rain gauge. it uses a DS2423 counter IC.
As far as I understand, this IC just count the ticks: I mean it starts from 
0 and just count, always up, never goes down.

Then, you can read it every minute, hour, day to calculate the minute, 
hourly or daily total rain (for the rainwise, 1 tick = 0.25mm)
This calculation should be easy to do in an ESP8266 (or anything arduino, 
whatever like).
We just need to know how to feed weewx correctly :-)

If I correctly understand (also after looking the "fileparser" driver). The 
data we have to feed in the driver match the database schemas.
there is only 2 rain data here.
('rainRate', 'REAL'),
('rain', 'REAL'),














 




Le lundi 20 février 2017 17:13:36 UTC+1, Bill Morrow a écrit :


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: attaching a raspberry Pi weather station to the weewx system

[wysiwyg]

Hello Bill,

I'm just discovering your work (and I'm also discovering mqtt, and 
ESP8266)
I feel like a new world of expending weewx is opening to me :-D

I plan to replace little by little my Oregon station by an homemade one.

So yesterday I setup a mosquitto server on an orange pi (an kind of 
raspberry) : it works great. I have tested with android app "MQTT 
dashboard" to build some subscriber and publicher.
I have ordered an ESP8266 and a sensor to start with (but it will take a 
few days or weeks to arrive.

In the mean time I plan to install wxMesh / Weewx on the orange pi and do 
some tests.
I can simulate a publisher either with the android app or on linux to check 
the wxmesh setup.


Unfortunately, I am not confortable with python and I was not able to read 
how the MQTT message shall looks like as input for wxMesh.

If I guessed well, the mqtt topic id should be *weather*.

I have many questions !! 

In a previous message of this thread, it is mentionned:

TIME:0,AMBT: 7.23,BARP:1001.97,RHUM:70.92,HUMT: 4.44,IRRA:12,BATV:974,PHOV:
673,SYST:33.20,WIND:  0.0,WDIR:  0.0

But I dont see the link with weewx labels here,c an you help a bit with 
that ?
Also I wonder how to deal with multiple publisher: I have in mind to have 
at least 2 (1 for outside, 1 for inside and barometric sensor).
last question, what is the expected format for time stamp ? unix epoc 
timestamp? ( like 1487603802 ).

And finally: simple measurements (temp, humidity, pressure...) seems ok, 
but how is working measurements like rain ? ( what is the data to be put 
here: daily total? )

Sorry for this question avalanche !




-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Steel Series Gauges and RealTime update - 2.5 second interval - how?

[gjr80]

Unfortunately the issue will remain whilst the gauge-data.txt values are 
formatted to the likes of 1 decimal place. This issue also exists with 
other PWS software that produce a similarly formatted data file for use by 
the SteelSeries Weather Gauges. Changing the underlying units to the units 
normally used by the user will eliminate the issue for those units, but the 
issue will eventually recur if different units are selected for display 
(for example, your MPH values will now be accurate but someone observing 
your gauges in km/h will eventually see a similar small error, admittedly 
they won't have a console in front of them to highlight the discrepancy :) )

Gary

On Monday, 20 February 2017 04:06:11 UTC+10, tempus wrote:
>
> On Saturday, February 18, 2017 at 5:56:41 PM UTC-8, tempus wrote:
>>
>> On Saturday, February 18, 2017 at 5:43:42 PM UTC-8, gjr80 wrote:
>>>
>>> Yes,  thought it would, my gauges exhibit the same behaviour. The 
>>> SteelSeries gauges do a lot of funky stuff to calculate gauge scales etc, I 
>>> need to sit down and work through the data. 
>>>
>>> Of course,  we could just disable F :) 
>>>
>>> Gary
>>>
>>>
>>> I will have a look at the code myself when I have time. 
>>
>> While you are looking, I noticed another issue. The gauge wind speed is 
>> 0.1 MPH less than shown on the Davis console.
>>
>> 1 MPH shows as 0.9 MPH
>> 2 MPH shows as 1.9 MPH
>> 3 MPH shows as 2.9 MPH
>> etc.
>>
>> Bob
>>
>
> This was found to be due to a loss of precision resulting from Rtgd 
> converting F to C and JavaScript then converting C back to F.  This and 
> other issues were fixed by specifying US units in weewx, like this:
>
> [RealtimeGaugeData]
> ...
>
> [[Groups]]
> group_pressure = inHg
> group_rain = inch
> group_rainrate = inch_per_hour
> group_speed = mile_per_hour
> group_distance = mile
> group_temperature = degree_F
> group_percent = percent
> group_uv = uv_index
> group_direction = degree_compass
>
> And by adding US 'StringFomats', like this:
>
> [[StringFormats]]
> degree_C = %.1f
> degree_F = %.1f
> degree_compass = %.0f
> hPa = %.1f
> inHg = %.3f
> inch = %.2f
> inch_per_hour = %.2f
> km_per_hour = %.0f
> km = %.1f
> knot = %.0f
> mbar = %.1f
> meter = %.0f
> meter_per_second = %.1f
> mile_per_hour = %.0f
> mile = %.1f
> mm = %.1f
> mm_per_hour = %.1f
> percent = %.0f
> uv_index = %.1f
> watt_per_meter_squared = %.0f
>
> Bob
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Steel Series Gauges and RealTime update - 2.5 second interval - how?

[gjr80]

Option 3 was implemented in v0.2.3. No need to do anything with appTemp, 
rtgd taes care of it.

Gary

On Monday, 20 February 2017 06:05:34 UTC+10, tempus wrote:
>
> Your Option 3 below seems best to me.  Where is the best place to set 
> apptempL and apptempH both to the current appTemp value?
>
> Bob
>
> On Saturday, February 18, 2017 at 9:50:54 PM UTC-8, gjr80 wrote:
>>
>> I had a suspicion the issue was with apptemp and gauge autoscaling; since 
>> weeWX (by default) calculates appTemp and adds it to each loop/archive 
>> packet but does not natively archive appTemp, there are no stats 
>> available for appTemp, just the current value. I knew the SteelSeries 
>> gauges do not like null values in its data feed yet I foolishly left the 
>> day high and low apptemp fields in gauge-data.txt go to None (which 
>> results in null in the gauge-data.txt JSON format). This messed up the 
>> autoscaling that is triggerred when switching to F (I suspect that if you 
>> set rtgd to output F it would work fine but when you then change display to 
>> C it would exhibit similar bad behaviour). There are a few options:
>>
>> 1. customise weeWX to archive appTemp, ie follow the instructions at Adding 
>> a new observation type 
>>  in 
>> the Customization Guide. Note that there is no need to add a service as 
>> appTemp is already calaculated, the only real change is that you need to 
>> add appTemp to the db and set its units. Pretty easy stuff.
>>
>> 2. set apptempL and apptempH both to 0. The light red wedge on the 
>> apparent temp gauge that shows the appTemp day range would not show, we 
>> can't make up data so no problems there. The mouseover plot would show the 
>> day low and high to be 0 (or maybe 32 deending on source and display units) 
>> - that will be wrong but at least it is largely hidden from the user. The 
>> autoscaling could have some issues if you were in a very hot location where 
>> all your temps (outTemp, windchill, heatindex, humidex, dewpoint, appTemp) 
>> were relatively high; the apptempL and apptempH values may skew the 
>> autoscaling to the lower end. But the nonsense behaviour currently 
>> happening would not occur.
>>
>> 3. set apptempL and apptempH both to the current appTemp value. Again 
>> the light red wedge on the apparent temp gauge that shows the appTemp 
>> day range would not show. The mouseover plot would show the day low and 
>> high to be whatever the current appTemp value is - again that will be 
>> wrong but at least it is largely hidden from the user. The autoscaling 
>> would not be uspet (ie skewed) under any circumstances.
>>
>> 4. use weeWX-WD to record appTemp in a separate database. This has all 
>> the advantages of 1. without the need to chnage the weeWX database (which 
>> is not really an issue). I don't think this is a practical solution, its a 
>> bit like buying a Mack truck just to take a trip to the corner store for 
>> the paper each day (and finding your truck probably breaks down once a 
>> month!).
>>
>> At the moment I am leaning towards a hybrid; look for a day low/high 
>> appTemp, if they are available use them, otherwise set both to the 
>> current appTemp value. I could probably include a silent option in the 
>> rtgd config to specify a binding from where to get appTemp data which 
>> would default to wx_binding (the weeWX default binding) (I have my 
>> appTemp data in a separate datbase so this ability will almost certainly 
>> be included :) )
>>
>> Gary
>>
>> On Sunday, 19 February 2017 11:43:42 UTC+10, gjr80 wrote:
>>>
>>> Yes,  thought it would, my gauges exhibit the same behaviour. The 
>>> SteelSeries gauges do a lot of funky stuff to calculate gauge scales etc, I 
>>> need to sit down and work through the data. 
>>>
>>> Of course,  we could just disable F :) 
>>>
>>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Digest for weewx-user@googlegroups.com - 5 updates in 4 topics

[Tom Lafleur]

I'm now sending my data to Wunderground and using this program on my iPhone and 
iPad...
Very nice way to display data from weewx...

http://pwsmonitor.blogspot.com/

http://www.wunderground.com/weatherstation/about.asp

~~ _/)  _/)  _/)  _/) ~~

Tom Lafleur

> On Feb 20, 2017, at 3:52 AM, weewx-user@googlegroups.com wrote:
> 
> 
> weewx-user@googlegroups.com   Google Groups  
> Topic digest 
> View all topics
> Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues - 1 Update
> Steel Series Gauges and RealTime update - 2.5 second interval - how? - 2 
> Updates
> New User, New Install, no run - 1 Update
> 10 min average wind - 1 Update
> Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues   
> tempus : Feb 19 11:52PM -0800 
> 
> It is customary in the U.S. to report barometric pressures adjusted to sea 
> level as inches of mercury (inHg) to two and sometimes three decimal digits 
> of precision. The default rtgd-0.2.2 string format for inHg appears to be 
> "%.3f", but that seems to be ignored in the code, because the pressure 
> value in 'gauge-data.txt' has only a single decimal digit of precision.
>  
> For example, right now the pressure is 29.637, 'gauge-data.txt' contains 
> only,
>  
>  
> *"press": "29.6"*
> and the pressure gauge displays
> * 29.60.*
> Another issue that even though "*group_rain = inch*" is specified under 
> [[Groups]] in weewx.conf, 'gauge-data.txt' contains:
>  
> *"rainunit": "mm"*
>  
> Bob
> Back to top
> Steel Series Gauges and RealTime update - 2.5 second interval - how?  
>  
> tempus : Feb 19 04:32PM -0800 
> 
> This is a link to a page at a test-site if you want to see the gauges 
> updating at 3-second intervals.
>  
> http://www.lablibrary.com/ss/
>  
> There are no developer-credits or anything else other than gauges on that 
> page, because access is normally blocked at the firewall. I am just playing 
> around with ideas with the general intention to eventually embed that page 
> within another one at a public website.
>  
> The Wind Rose still needs attention, but otherwise the gauges seem to be 
> working.
>  
> Bob
>  
> On Sunday, February 19, 2017 at 3:26:42 PM UTC-8, tempus wrote:
> tempus : Feb 19 05:45PM -0800 
> 
> Sorry if you aren't able load the test page. I have taken it down to fix an 
> issue.
>  
> Bob
>  
> On Sunday, February 19, 2017 at 4:32:38 PM UTC-8, tempus wrote:
> Back to top
> New User, New Install, no run   
> ge...@embarqmail.com: Feb 19 04:51PM -0800 
> 
> duh... sorry, missed that
> got driver loaded, reconfigured, and started without error :>)
> off to figure out how to get skins running in my apache2
>  
> Thanks for your valuable assistance
>  
> Geary
>  
> On Saturday, February 18, 2017 at 2:39:00 PM UTC-8, gjr80 wrote:
> Back to top
> 10 min average wind   
> gjr80 : Feb 19 03:56PM -0800 
> 
> Hi,
>  
> Wind speed can be a complex topic. The simple answer to your question *I'm 
> wondering if weewx calculates the average windspeed over 10 minutes* is *yes, 
> it can, but...*. Perhaps an explanation of what weeWX archives and reports 
> and a few points on the SteelSeries Weather Gauges might make it clear.
>  
> The WeeWX archive field windSpeed holds the average wind speed over the 
> archive period. This might be calculated from loop wind speed data if using 
> software record generation or received directly from the station if 
> hardware record generation is used. On your install your windSpeed fields 
> would I expect be averaged over 2 minutes, I have a 5 minute archive period 
> so mine is a 5 minute average. Stations that use a 10 minute archive period 
> would indeed have a 10 minute average in their windSpeed fields. The daily 
> summary for windSpeed is just an optimisation holding aggregates and other 
> data on your archive windSpeed data, so they to refer to 2, 5 or 10 (in the 
> examples I cited) average values. That is the data storage aspect of weeWX.
>  
> The other side of the weeWX coin is the reporting. WeeWX has a variety of 
> tags that allow generation of statistics over some period of time eg $day, 
> $week, $span etc. For windSpeed, $day.windSpeed.avg will give you the 
> average of all of the windSpeed values for the day so far. One could argue 
> that the average of an average is dangerous, though in the case where the 
> archive period is homogeneous the calculation is valid (or if your archive 
> period is non-homogeneous and you are using weeWX 3.7.0 or later with the 
> weighted summaries fix applied the calculation is also valid as the values 
> are appropriately weighted). The $span tag allows calculation of aggregates 
> over a user defined period of time, so $span($time_delta=600).windSpeed.avg 
> would allow you use the average windSpeed over the last immediate 10 
> minutes in your reports, irrespective of your archive period (of 

[weewx-user] Re: Realtime Gauge-Data Extension 0.2.2 'gauge-data.txt' Issues

[gjr80]

Typo was the cause of the rain issue, as for the pressure issue, seems I 
changed the structure of config options for formatting but neglected to 
change the code. Should be fixed now in v0.2.4.

Note that the digital display on the pressure gauge will display 2 decimal 
places when using inHg, this is a SteelSeries Weather Gauges limitation not 
rtgd.

Gary

On Monday, 20 February 2017 17:52:11 UTC+10, tempus wrote:
>
> It is customary in the U.S. to report barometric pressures adjusted to sea 
> level as inches of mercury (inHg) to two and sometimes three decimal digits 
> of precision.  The default rtgd-0.2.2 string format for inHg appears to be 
> "%.3f", but that seems to be ignored in the code, because the pressure 
> value in 'gauge-data.txt' has only a single decimal digit of precision.
>
> For example, right now the pressure is 29.637, 'gauge-data.txt' contains 
> only,
>
>
> *"press": "29.6"*
> and the pressure gauge displays
> * 29.60.*
> Another issue that even though "*group_rain = inch*" is specified under 
> [[Groups]] in weewx.conf, 'gauge-data.txt' contains:
>
> *"rainunit": "mm"*
>
> Bob
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Wind direction and wind vector stuck in easterly direction

[Rune Laegreid]

Finally we are back in on-line with with correct wind measurements again. 
It might be interesting for you to know that the issue was hardware related 
describes as "I think 180 degrees is where the potentiometer transitions 
from a high resistance to a low resistance.  It sounds at though there may 
be an issue with the potentiometer."
The anemometer was replaced under warranty by Scaled Instruments 
. Super service and responsiveness from 
Ryan Wilhour!

Rune. 

mandag 7. november 2016 13.08.17 UTC+1 skrev Rune Laegreid følgende:
>
> Hi and thank you for your replies.
> I had no friendly eyes but my own up there. 
> The issue was a defect in the anemometer. A replacement anemometer is in 
> delivery and I will hopefully be "back in business" within a couple of 
> weeks.
>
> Rune.
>
> onsdag 12. oktober 2016 15.11.22 UTC+2 skrev mwall følgende:
>>
>> On Wednesday, October 12, 2016 at 8:32:42 AM UTC-4, Rune Laegreid wrote:
>>>
>>> Are there anyone out there that can come up with a way for me to 
>>> determine if it is the interpretation of the data from Davis Vantage Pro 2 
>>> station or it is the weather station itself that causes the issue?
>>> and if it is a software/parameter issue, where should I start search 
>>> for a solution?
>>>
>>
>> analogous to the first computer support question of "is it plugged in?", 
>> you might want to check the hardware first.  do you have a camera on it or 
>> friendly eyeballs nearby the station that could inspect it for you?
>>
>> a bird once had a rather hard landing on the anemometer arm of one of our 
>> weather stations.  that, combined with a fastener that had become loose, 
>> resulted in a 4 or 5 degree angle from vertical.  so all of the wind 
>> direction readings were biased.
>>
>> m
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Wrong data archived after reboot

[Lloyd Brown]

Jeff:

I know this is a couple years old but did you ever find out how to suppress 
the bad data?  I have a similar setup and resorted to just putting in a UPS 
but that does not help when you do have to stop the process.  Get zero on 
the temperature on boot up which messes 
up the data.  Any information would be appreciated.
Thanks 
Lloyd



On Saturday, September 19, 2015 at 7:10:10 AM UTC-6, Jeff Gschwend wrote:
>
> Thanks Tom. That will help. Thinking I'll move things over to the Mac and 
> test there, to make sure it's reproducible and maybe a little less 
> convoluted than SSHing into the Pi. Unfortunately, weekend chores have 
> expanded to fill the void and I may not have much time now. Will post on 
> what I find, when I get a chance to dig into this. 
>
> jeff
>
>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.