[weewx-user] Re: wee_import PWS station not found.

[Jay Jaeger]

FYI, I am in the same boat with a 403 error during wee_import for WU.  Glad 
to hear someone is working on it.  As I am currently testing, and have 
"throw away" data (just running the Simulator at present - my real station 
continues to run) I'd be happy to give it a whirl.  I don't plan on a real 
migration until I test my actual weather station (probably next week) - and 
in any event, not until the new year.

(As an aside, I am really impressed so far with the help I had with a 
question earlier today and with the general activity level on this forum.  
I have been out in the boondocks running the *ancient* meteo software for 
more than a decade.)

JRJ


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3c9a571b-295a-4947-b9cb-03297a272219%40googlegroups.com.

Re: [weewx-user] setup.py: Did not prompt for configuration information

[Jay Jaeger]

Thanks - of course, that worked fine.

(Maybe someone should consider updating the web site then, since there is a 
default .conf file in the tarball.  ;) )

Have it running fine as a Simulator.  Plan on cutting over from my ancient 
meteo software at the turn of the year - and running it briefly on my 
actual weather station as a test - it needs an extension driver installed 
(Davis WeatherMonitor II)

JRJ


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a1fe7e8f-7e8f-4eef-b079-8da3374200d9%40googlegroups.com.

Re: [weewx-user] setup.py: Did not prompt for configuration information

[Thomas Keffer]

Oops. That's

*wee_config --reconfigure /opt/weewx/weewx.conf*

On Wed, Nov 27, 2019 at 3:13 PM Thomas Keffer  wrote:

> If there is an existing weewx.conf configuration file in the installation
> target, setup.py does not prompt. It just uses the values it finds there.
>
> If you want to reconfigure, then after the install use the tool wee_config:
>
> *wee_config --reconfigure /open/weewx/weewx.conf*
>
> -tk
>
> On Wed, Nov 27, 2019 at 2:52 PM Jay Jaeger  wrote:
>
>> So, I am doing a first-time install of weewx (version 3.9.2), on a
>> somewhat older version of Ubuntu, following the instructions at
>> http://www.weewx.com/docs/setup.htm .  I prefer to NOT use a pre-build
>> distribution package.
>>
>> Python is version 2.7.3
>>
>> I made sure all of the pre-reqs are there, a few of which I needed to
>> install.  That all went fine (see below).
>>
>> I plan on using MySQL, and created the appropriate user and grants (but I
>> don't think it is getting that far -- I think that requires manual
>> intervention later).
>>
>> I un-tar'd the distribution into /opt/weewx-3.9.2 and created a symbolic
>> link /opt/weewx to point to it.
>>
>> I "tweaked" setup.cfg, changing home to be /opt/weewx.
>>
>> I ran "./setup.py build" as myself.  It seemed to be OK.
>>
>> I ran "sudo bash" and then "./setup.py install"
>>
>> Per the web page above, I expected to see prompts for station information
>> from this last step - but there were none.  Obviously I could edit the
>> information in the configuration file -- but is this a documentation error
>> on that web page, or is something else going wrong?
>>
>> Thanks in advance
>>
>>
>> ==
>>
>> Ubuntu info:
>>
>> Linux mythtv2 3.8.0-44-generic #66~precise1-Ubuntu SMP Tue Jul 15
>> 04:01:04 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>>
>> Pre-req info:
>>
>>python   2.7
>>python-imaging   1.1.7-4ubuntu0.12.04.3
>>python-configobj 4.7.2+ds-3build1
>>python-cheetah   missing ==> apt-get install python-cheetah ->
>> 2.4.4-2ubuntu3
>>python-serial2.5-2.1build1
>>mysql-client 5.5.54-0ubuntu0.12.04.1
>>python-mysqldb   1.2.3-1ubuntu0.1
>>python-dev   missing ==> apt-get install python-dev ->
>> 2.7.3-0ubuntu2.2
>>   Added automatically: libssl-dev libssl-doc python2.7-dev
>>python-pip   missing ==> apt-get install python-pip -> 1.0-1build1
>>   Added automatically:  python-setuptoolsdpkg
>>
>>pip install pyephem did not do anything.
>>pip install --index-url=https://pypi.python.org/simple/ pyephem worked
>>   It looks like "C" code.
>>
>>useradd wxuser
>>Edit /etc/passwd, change shell for wxuser to /bin/bash
>>password wxuser (set to t-word)
>>Created /etc/udev/rules.d/60-persistent-serial-rules
>>   KERNEL=="ttyS0", MODE="0666"
>>
>> Build output:
>>
>> running build
>> running build_py
>> creating build
>> creating build/lib.linux-x86_64-2.7
>> copying bin/daemon.py -> build/lib.linux-x86_64-2.7
>> creating build/lib.linux-x86_64-2.7/schemas
>> copying bin/schemas/__init__.py -> build/lib.linux-x86_64-2.7/schemas
>> copying bin/schemas/wview.py -> build/lib.linux-x86_64-2.7/schemas
>> creating build/lib.linux-x86_64-2.7/user
>> copying bin/user/__init__.py -> build/lib.linux-x86_64-2.7/user
>> copying bin/user/extensions.py -> build/lib.linux-x86_64-2.7/user
>> creating build/lib.linux-x86_64-2.7/weecfg
>> copying bin/weecfg/extension.py -> build/lib.linux-x86_64-2.7/weecfg
>> copying bin/weecfg/__init__.py -> build/lib.linux-x86_64-2.7/weecfg
>> copying bin/weecfg/config.py -> build/lib.linux-x86_64-2.7/weecfg
>> copying bin/weecfg/database.py -> build/lib.linux-x86_64-2.7/weecfg
>> creating build/lib.linux-x86_64-2.7/weedb
>> copying bin/weedb/__init__.py -> build/lib.linux-x86_64-2.7/weedb
>> copying bin/weedb/mysql.py -> build/lib.linux-x86_64-2.7/weedb
>> copying bin/weedb/sqlite.py -> build/lib.linux-x86_64-2.7/weedb
>> creating build/lib.linux-x86_64-2.7/weeimport
>> copying bin/weeimport/__init__.py -> build/lib.linux-x86_64-2.7/weeimport
>> copying bin/weeimport/csvimport.py -> build/lib.linux-x86_64-2.7/weeimport
>> copying bin/weeimport/weeimport.py -> build/lib.linux-x86_64-2.7/weeimport
>> copying bin/weeimport/cumulusimport.py ->
>> build/lib.linux-x86_64-2.7/weeimport
>> copying bin/weeimport/wuimport.py -> build/lib.linux-x86_64-2.7/weeimport
>> creating build/lib.linux-x86_64-2.7/weeplot
>> copying bin/weeplot/utilities.py -> build/lib.linux-x86_64-2.7/weeplot
>> copying bin/weeplot/genplot.py -> build/lib.linux-x86_64-2.7/weeplot
>> copying bin/weeplot/__init__.py -> build/lib.linux-x86_64-2.7/weeplot
>> creating build/lib.linux-x86_64-2.7/weeutil
>> copying bin/weeutil/weeutil.py -> build/lib.linux-x86_64-2.7/weeutil
>> copying bin/weeutil/rsyncupload.py -> build/lib.linux-x86_64-2.7/weeutil
>> copying bin/weeutil/Sun.py -> build/lib.linux-x86_64-2.7/weeutil
>> copying bin/weeu

Re: [weewx-user] setup.py: Did not prompt for configuration information

[Thomas Keffer]

If there is an existing weewx.conf configuration file in the installation
target, setup.py does not prompt. It just uses the values it finds there.

If you want to reconfigure, then after the install use the tool wee_config:

*wee_config --reconfigure /open/weewx/weewx.conf*

-tk

On Wed, Nov 27, 2019 at 2:52 PM Jay Jaeger  wrote:

> So, I am doing a first-time install of weewx (version 3.9.2), on a
> somewhat older version of Ubuntu, following the instructions at
> http://www.weewx.com/docs/setup.htm .  I prefer to NOT use a pre-build
> distribution package.
>
> Python is version 2.7.3
>
> I made sure all of the pre-reqs are there, a few of which I needed to
> install.  That all went fine (see below).
>
> I plan on using MySQL, and created the appropriate user and grants (but I
> don't think it is getting that far -- I think that requires manual
> intervention later).
>
> I un-tar'd the distribution into /opt/weewx-3.9.2 and created a symbolic
> link /opt/weewx to point to it.
>
> I "tweaked" setup.cfg, changing home to be /opt/weewx.
>
> I ran "./setup.py build" as myself.  It seemed to be OK.
>
> I ran "sudo bash" and then "./setup.py install"
>
> Per the web page above, I expected to see prompts for station information
> from this last step - but there were none.  Obviously I could edit the
> information in the configuration file -- but is this a documentation error
> on that web page, or is something else going wrong?
>
> Thanks in advance
>
>
> ==
>
> Ubuntu info:
>
> Linux mythtv2 3.8.0-44-generic #66~precise1-Ubuntu SMP Tue Jul 15 04:01:04
> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> Pre-req info:
>
>python   2.7
>python-imaging   1.1.7-4ubuntu0.12.04.3
>python-configobj 4.7.2+ds-3build1
>python-cheetah   missing ==> apt-get install python-cheetah ->
> 2.4.4-2ubuntu3
>python-serial2.5-2.1build1
>mysql-client 5.5.54-0ubuntu0.12.04.1
>python-mysqldb   1.2.3-1ubuntu0.1
>python-dev   missing ==> apt-get install python-dev ->
> 2.7.3-0ubuntu2.2
>   Added automatically: libssl-dev libssl-doc python2.7-dev
>python-pip   missing ==> apt-get install python-pip -> 1.0-1build1
>   Added automatically:  python-setuptoolsdpkg
>
>pip install pyephem did not do anything.
>pip install --index-url=https://pypi.python.org/simple/ pyephem worked
>   It looks like "C" code.
>
>useradd wxuser
>Edit /etc/passwd, change shell for wxuser to /bin/bash
>password wxuser (set to t-word)
>Created /etc/udev/rules.d/60-persistent-serial-rules
>   KERNEL=="ttyS0", MODE="0666"
>
> Build output:
>
> running build
> running build_py
> creating build
> creating build/lib.linux-x86_64-2.7
> copying bin/daemon.py -> build/lib.linux-x86_64-2.7
> creating build/lib.linux-x86_64-2.7/schemas
> copying bin/schemas/__init__.py -> build/lib.linux-x86_64-2.7/schemas
> copying bin/schemas/wview.py -> build/lib.linux-x86_64-2.7/schemas
> creating build/lib.linux-x86_64-2.7/user
> copying bin/user/__init__.py -> build/lib.linux-x86_64-2.7/user
> copying bin/user/extensions.py -> build/lib.linux-x86_64-2.7/user
> creating build/lib.linux-x86_64-2.7/weecfg
> copying bin/weecfg/extension.py -> build/lib.linux-x86_64-2.7/weecfg
> copying bin/weecfg/__init__.py -> build/lib.linux-x86_64-2.7/weecfg
> copying bin/weecfg/config.py -> build/lib.linux-x86_64-2.7/weecfg
> copying bin/weecfg/database.py -> build/lib.linux-x86_64-2.7/weecfg
> creating build/lib.linux-x86_64-2.7/weedb
> copying bin/weedb/__init__.py -> build/lib.linux-x86_64-2.7/weedb
> copying bin/weedb/mysql.py -> build/lib.linux-x86_64-2.7/weedb
> copying bin/weedb/sqlite.py -> build/lib.linux-x86_64-2.7/weedb
> creating build/lib.linux-x86_64-2.7/weeimport
> copying bin/weeimport/__init__.py -> build/lib.linux-x86_64-2.7/weeimport
> copying bin/weeimport/csvimport.py -> build/lib.linux-x86_64-2.7/weeimport
> copying bin/weeimport/weeimport.py -> build/lib.linux-x86_64-2.7/weeimport
> copying bin/weeimport/cumulusimport.py ->
> build/lib.linux-x86_64-2.7/weeimport
> copying bin/weeimport/wuimport.py -> build/lib.linux-x86_64-2.7/weeimport
> creating build/lib.linux-x86_64-2.7/weeplot
> copying bin/weeplot/utilities.py -> build/lib.linux-x86_64-2.7/weeplot
> copying bin/weeplot/genplot.py -> build/lib.linux-x86_64-2.7/weeplot
> copying bin/weeplot/__init__.py -> build/lib.linux-x86_64-2.7/weeplot
> creating build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/weeutil.py -> build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/rsyncupload.py -> build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/Sun.py -> build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/__init__.py -> build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/Moon.py -> build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/config.py -> build/lib.linux-x86_64-2.7/weeutil
> copying bin/weeutil/ftpupload.py -> build/li

[weewx-user] Re: sensor data wind and rain hideki (tfa Sinus-bresser ...)

[Andy]

I am glad it worked. The sdr.py driver as not reading the wind and rain 
sensor. The output from rtl_433 has changed due to a different sensor or 
rtl_433 change. You can see the changes here. 


Old vs new message, yours is on the bottom.

Old

# {"time" : "2017-01-16 04:38:39", "model" : "HIDEKI Wind sensor", "rc" 
: 0, "channel" : 4, "battery" : "OK", "temperature_C" : -4.400, 
"windstrength" : 2.897, "winddirection" : 292.500}

New

# {"time" : "2019-11-24 19:13:41", "model" : "HIDEKI Wind sensor", "rc" 
: 3, "channel" : 4, "battery" : "OK", "temperature_C" : 11.000, 
"wind_speed_mph" : 1.300, "gust_speed_mph" : 0.100, "wind_approach" : 1, 
"wind_direction" : 270.000, "mic" : "CRC"}


Just added some if/else statements to parse the old and new versions:

if 'windstrength' in obj: 
pkt['wind_speed'] = Packet.get_float(obj, 'windstrength')
else:
pkt['wind_speed'] = Packet.get_float(obj, 'wind_speed_mph')
if 'winddirection' in obj:
pkt['wind_dir'] = Packet.get_float(obj, 'winddirection')
else:
pkt['wind_dir'] = Packet.get_float(obj, 'wind_direction')
if 'gust_speed_mph' in obj:
pkt['wind_gust'] = Packet.get_float(obj, 'gust_speed_mph')   

Did the same for the rain.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6b77b7de-8d5e-4573-bd42-1e126e7eb336%40googlegroups.com.

[weewx-user] setup.py: Did not prompt for configuration information

[Jay Jaeger]

So, I am doing a first-time install of weewx (version 3.9.2), on a somewhat 
older version of Ubuntu, following the instructions at 
http://www.weewx.com/docs/setup.htm .  I prefer to NOT use a pre-build 
distribution package.

Python is version 2.7.3

I made sure all of the pre-reqs are there, a few of which I needed to 
install.  That all went fine (see below).

I plan on using MySQL, and created the appropriate user and grants (but I 
don't think it is getting that far -- I think that requires manual 
intervention later).

I un-tar'd the distribution into /opt/weewx-3.9.2 and created a symbolic 
link /opt/weewx to point to it.

I "tweaked" setup.cfg, changing home to be /opt/weewx.

I ran "./setup.py build" as myself.  It seemed to be OK.

I ran "sudo bash" and then "./setup.py install" 

Per the web page above, I expected to see prompts for station information 
from this last step - but there were none.  Obviously I could edit the 
information in the configuration file -- but is this a documentation error 
on that web page, or is something else going wrong?

Thanks in advance

==

Ubuntu info:

Linux mythtv2 3.8.0-44-generic #66~precise1-Ubuntu SMP Tue Jul 15 04:01:04 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Pre-req info:

   python   2.7
   python-imaging   1.1.7-4ubuntu0.12.04.3
   python-configobj 4.7.2+ds-3build1
   python-cheetah   missing ==> apt-get install python-cheetah ->  
2.4.4-2ubuntu3 
   python-serial2.5-2.1build1
   mysql-client 5.5.54-0ubuntu0.12.04.1
   python-mysqldb   1.2.3-1ubuntu0.1
   python-dev   missing ==> apt-get install python-dev ->  
2.7.3-0ubuntu2.2 
  Added automatically: libssl-dev libssl-doc python2.7-dev
   python-pip   missing ==> apt-get install python-pip -> 1.0-1build1 
  Added automatically:  python-setuptoolsdpkg 
   
   pip install pyephem did not do anything.
   pip install --index-url=https://pypi.python.org/simple/ pyephem worked
  It looks like "C" code.

   useradd wxuser
   Edit /etc/passwd, change shell for wxuser to /bin/bash
   password wxuser (set to t-word)
   Created /etc/udev/rules.d/60-persistent-serial-rules
  KERNEL=="ttyS0", MODE="0666"   

Build output:

running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
copying bin/daemon.py -> build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/schemas
copying bin/schemas/__init__.py -> build/lib.linux-x86_64-2.7/schemas
copying bin/schemas/wview.py -> build/lib.linux-x86_64-2.7/schemas
creating build/lib.linux-x86_64-2.7/user
copying bin/user/__init__.py -> build/lib.linux-x86_64-2.7/user
copying bin/user/extensions.py -> build/lib.linux-x86_64-2.7/user
creating build/lib.linux-x86_64-2.7/weecfg
copying bin/weecfg/extension.py -> build/lib.linux-x86_64-2.7/weecfg
copying bin/weecfg/__init__.py -> build/lib.linux-x86_64-2.7/weecfg
copying bin/weecfg/config.py -> build/lib.linux-x86_64-2.7/weecfg
copying bin/weecfg/database.py -> build/lib.linux-x86_64-2.7/weecfg
creating build/lib.linux-x86_64-2.7/weedb
copying bin/weedb/__init__.py -> build/lib.linux-x86_64-2.7/weedb
copying bin/weedb/mysql.py -> build/lib.linux-x86_64-2.7/weedb
copying bin/weedb/sqlite.py -> build/lib.linux-x86_64-2.7/weedb
creating build/lib.linux-x86_64-2.7/weeimport
copying bin/weeimport/__init__.py -> build/lib.linux-x86_64-2.7/weeimport
copying bin/weeimport/csvimport.py -> build/lib.linux-x86_64-2.7/weeimport
copying bin/weeimport/weeimport.py -> build/lib.linux-x86_64-2.7/weeimport
copying bin/weeimport/cumulusimport.py -> 
build/lib.linux-x86_64-2.7/weeimport
copying bin/weeimport/wuimport.py -> build/lib.linux-x86_64-2.7/weeimport
creating build/lib.linux-x86_64-2.7/weeplot
copying bin/weeplot/utilities.py -> build/lib.linux-x86_64-2.7/weeplot
copying bin/weeplot/genplot.py -> build/lib.linux-x86_64-2.7/weeplot
copying bin/weeplot/__init__.py -> build/lib.linux-x86_64-2.7/weeplot
creating build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/weeutil.py -> build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/rsyncupload.py -> build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/Sun.py -> build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/__init__.py -> build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/Moon.py -> build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/config.py -> build/lib.linux-x86_64-2.7/weeutil
copying bin/weeutil/ftpupload.py -> build/lib.linux-x86_64-2.7/weeutil
creating build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/imagegenerator.py -> build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/wxformulas.py -> build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/filegenerator.py -> build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/defaults.py -> build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/units.py -> build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/accum.py -> build/lib.linux-x86_64-2.7/weewx
copying bin/weewx/restx.py 

[weewx-user] Re: Belchertown skin 1.0 released!

[Kike .Asekas]

Ok, I already understand. The fail is in MQTT. The skin only show it send 
by mqtt. If mqtt send m/s the skin shows m/s.
Fortunately the mqtt module have options to change the units show to every 
observation.
I change [MQTT] in weewx.conf with this
[[[inputs]]]
windSpeed
units = km_per_hour
windGust
units = km_per_hour

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b0033ae9-ef25-4720-83aa-750faf15dfd0%40googlegroups.com.

[weewx-user] Re: sensor data wind and rain hideki (tfa Sinus-bresser ...)

[giuseppe saia]

it works perfectly
how did you do?
What can I do to thank you?
Il giorno martedì 26 novembre 2019 16:11:44 UTC+1, Andy ha scritto:
>
>
> Please try the updated sdr driver. Replace your existing sdr.py with the 
> attached. In your weewx install directory the sdr driver is located in 
> bin/user/.
>
> My install dir is /home/weewx so:
> root@weewx-01:~# ls /home/weewx/bin/user/sdr.py
> /home/weewx/bin/user/sdr.py
>
>
> Your install directory may be different. 
>
>
> Andy
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fa9df95e-4c9e-48d9-9b3a-aa221018b18c%40googlegroups.com.

Re: [weewx-user] Re: Belchertown skin 1.0 released!

[Greg Troxel]

"Kike .Asekas"  writes:

> I use MQTT y I have configure it with METRICWX.
> [[MQTT]]
> server_url = mqtt://broker.hivemq.com:1883
> topic = estacion/datos
> unit_system = METRICWX
> binding = loop
> ...
> When I load the page goes well, but at the time of updating the wind speed 
> appears in m / s. If I change the lines I told you multiplying x3.6 it goes 
> well. 

You can tell the mqtt publisher to set the units on each thing to
publish.   Probably you should just do that, even if in the background
you try to investigate the defaults.

For example, I have

[[[inputs]]]
barometer
name = barometer_hPa
units = hPa

I am really not sure why I needed this, as I have group_pressure set to
hPa as a default for all reports, but it was easy to set.

> This is the output of MQTT. By the way, I don't understand how maxSolarRad 
> appears without having a solar sensor

That does not make sense.  Some stations pretend to measure solar
radation from an illuminance sensor, but I don't even see that in your
output.

Also, since solar radiation is more or less always in W/m^2 (even in the
US we do not use hp/ft^2), the value 7 does not really make sense unless
right at dawn.  Even a very dark day will see 50.

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

[weewx-user] Re: Belchertown skin 1.0 released!

[Kike .Asekas]

If I set US in MQTT the temperature and all data, barometer, cloudbase, etc 
it appears in the US units.
{"noise_dB": "-31.005", "barometer_inHg": "29.7715847252", "outHumidity": 
"92.0", "maxSolarRad": "0.19266621551", "rainRate_mm_per_hour": "0.0", 
"dewpoint_F": "52.2228357071", "rain_in": "0.0", "cloudbase_foot": 
"704.545678119", "heatindex_F": "54.5", "altimeter_inHg": "29.7612660083", 
"dayRain_mm": "0.3", "battery": "0.0", "outTemp_F": "54.5", "appTemp_F": 
"52.2075030114", "snr_dB": "30.881", "rain_total": "68.16", "windchill_F": 
"54.5", "hourRain_in": "0.0", "humidex_F": "57.8664956127", "rssi_dB": 
"-0.124", "windGust_mph": "8.36618332697", "pressure_inHg": 
"29.5692623834", "inTemp_F": "63.5", "usUnits": "1.0", "windSpeed_mph": 
"5.32393484443", "rain24_in": "0.0708661417323", "dateTime": 
"1574873496.0", "windDir": "180.0"}
And if I set METRIC the rain is in cm.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8e4094af-5bbc-42bc-83a7-acb164187226%40googlegroups.com.

[weewx-user] Re: MQTT missing information?

[Philippe]

Well if anything the link you provided confirms that when there is no wind 
then no wind direction is broadcasted by default.

On Tuesday, 26 November 2019 21:23:47 UTC, Xant wrote:
>
> Interesting ET and CloudBase are WeeWX calculations (
> http://www.weewx.com/docs/usersguide.htm#[[Calculations]] ). Thought that 
> required trigger command in 'weewx.conf', but apparently not and calculated 
> by software by default.
>
> X
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/40d5bd71-a17f-49ef-bc3b-19e858909944%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Kike .Asekas]

If I set METRIC in MQTT the speed it appears well. But I think now the 
problem is the rain in cm.
This is the output of MQTT
{"noise_dB": "-31.005", "cloudbase_meter": "214.870790215", "outHumidity": 
"92.0", "pressure_mbar": "1001.17", "rain_cm": "0.0", "maxSolarRad": 
"1.45829104758", "barometer_mbar": "1008.01791956", "rainRate_mm_per_hour": 
"0.0", "dewpoint_C": "11.3338998187", "*windGust_kph*": "15.9120395619", 
"heatindex_C": "12.6", "dayRain_mm": "0.3", "battery": "0.0", 
"altimeter_mbar": "1007.67110825", "windchill_C": "12.6", "snr_dB": 
"30.899", "rain_total": "68.16", "appTemp_C": "11.1172772991", "outTemp_C": 
"12.6", "humidex_C": "14.5196613477", "rain24_cm": "0.18", "rssi_dB": 
"-0.106", "hourRain_cm": "0.0", "inTemp_C": "17.5", "*windSpeed_kph*": 
"9.79202434576", "usUnits": "16.0", "dateTime": "1574873016.0", "windDir": 
"135.0"}

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2db6db11-8e28-4156-b1ed-99bba5f29005%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Kike .Asekas]

I use MQTT y I have configure it with METRICWX.
[[MQTT]]
server_url = mqtt://broker.hivemq.com:1883
topic = estacion/datos
unit_system = METRICWX
binding = loop
...
When I load the page goes well, but at the time of updating the wind speed 
appears in m / s. If I change the lines I told you multiplying x3.6 it goes 
well. 
This is the output of MQTT. By the way, I don't understand how maxSolarRad 
appears without having a solar sensor
{"noise_dB": "-32.602", "cloudbase_meter": "214.870790215", "outHumidity": 
"92.0", "pressure_mbar": "1001.03", "maxSolarRad": "7.37293576364", 
"barometer_mbar": "1007.87696197", "rainRate_mm_per_hour": "0.0", 
"dewpoint_C": "11.3338998187", "heatindex_C": "12.6", "dayRain_mm": "0.3", 
"battery": "0.0", "altimeter_mbar": "1007.53033843", "windchill_C": "12.6", 
"snr_dB": "32.481", "rain_total": "68.16", "appTemp_C": "11.1172772991", 
"outTemp_C": "12.6", "humidex_C": "14.5196613477", "hourRain_mm": "0.0", 
*"windGust_mps*": "4.08001014407", "rssi_dB": "-0.12", "inTemp_C": "17.5", 
"usUnits": "17.0", "rain_mm": "0.0", "rain24_mm": "1.8", "dateTime": 
"1574872344.0", "windDir": "180.0", "*windSpeed_mps*": "2.72000676271"}
In this case in the web page it appear WindSpeed 2.7 and gust 4.8 Km/h


El miércoles, 27 de noviembre de 2019, 0:39:35 (UTC+1), Pat escribió:
>
> Kike I don't this this is a bug. Are you using MQTT? If so, then you need 
> to configure your MQTT plugin to use metricwx. 
>
> *There is no need to do math like this in the js*. 
>
> Please see this thread on how to update your MQTT settings. 
>
>
> https://github.com/poblabs/weewx-belchertown/issues/23#issuecomment-440529099
>
>
>
> On Tuesday, November 26, 2019 at 4:38:20 PM UTC-5, Kike .Asekas wrote:
>>
>>
>> Pat, I detect a bug in the js. I use the target_unit=metricwx that store 
>> the speed in m/s but i want see the speed in km/h and for that reason i 
>> have the group_speed=km_per_hour. The skin shows the speed in km/s until 
>> update then m/s. I change the lines 879 and 893  multiply x 3.6. Maybe it 
>> also fails to people with us  target unit and metric visualization.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/24feaa64-54ff-41fb-86a7-d19a62b27b2b%40googlegroups.com.

[weewx-user] Belchertown beta feedback

[vince]

Pat - I'm seeing some garbage on my windspeed direction dial image ala the 
attached image.  System is  a pi4, latest Raspbian, latest weewx 4.0.0 
beta, latest dev Belchertown, all under python3, websockets/mqtt 'enabled', 
but it doesn't affect this bug report if it's on or off.  Same result both 
ways.



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/31b111f5-9dd6-4c69-9620-455a6fa7bd3d%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[vince]

On Wednesday, November 27, 2019 at 5:21:43 AM UTC-8, Günther Wrana wrote:
>
> Womit bearbeite ich die Archivtabelle und welche Datenbankdienstprogramm 
> verwende ich dafür?
>
>
>
https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data

 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/34f27a6b-cfb2-4059-8fb9-5f77dd90c016%40googlegroups.com.

[weewx-user] Re: Datenbank zusammen legen.

[Günther Wrana]

Womit bearbeite ich die Archivtabelle und welche Datenbankdienstprogramm 
verwende ich dafür?

Am Dienstag, 26. November 2019 07:45:39 UTC+1 schrieb Andrew Milner:
>
> I would merge only the archive table and then use the database utility to 
> drop the daily summary and rebuild the summaries for the combined database.
>
>
>
> On Tuesday, 26 November 2019 06:33:06 UTC+2, J D wrote:
>>
>> Hi,
>>
>> Yes you can merge two databases I have done it a number of times. You 
>> need to use SQLite commands. At a high level you attached to the two 
>> databases and then use the update command. If you google merge sqlite 
>> databases you can find a number of ways to do it.
>> Jerry 
>>
>> On Sunday, November 24, 2019 at 2:52:27 AM UTC-7, Günther Wrana wrote:
>>>
>>> Hallo
>>>
>>> ich möchte Versuchen zwei Datenbanken von weewx.sdb zusammen zu fügen.
>>>
>>> Ich habe einen Rechner mit Ubuntu und kann die Datenbank mit DB Browser 
>>> for SQLite öffnen.
>>>
>>> Die beiden Datenbanken beginnen und enden zu folgenden Zeiten.
>>>
>>> 1573144800 07.11.2019 17:40:00
>>> 1573149300 07.11.2019 18:55:00
>>>
>>> 1573249500 08.11.2019 22:45:00
>>> 1574009700 17.11.2019 17:55:00
>>>
>>> Nun habe ich noch nicht herausgefunden wie ich das mit DB Browser for 
>>> SQLite mache.
>>> Ich weis auch nicht ob das das Richtige Programm für mein Vorhaben ist.
>>>
>>> Darum hoffe ich das Ihr mir sagen könnt wie oder mit welchem Programm 
>>> ich das tun soll.
>>> Das ganze ist einmal ein Versuch danach würde ich dann gerne meine alten 
>>> Wetterdaten die ich seit November 2014 aufgezeichnet habe auch noch 
>>> einfügen.
>>>
>>> Für alle Tipps bin ich dankbar also dann
>>>
>>> Grüße Günther
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/23e215b8-0bb2-4f0c-8b71-f99c7183baa8%40googlegroups.com.

[weewx-user] Re: Seasons statistics.inc question for displaying windrun

[Jared]

No, you've got it.  And ah, I see what I was missing.  I was thinking of 
"week" as in the last seven days, and so expected the rain total to be 
higher.  It was a coincidence that I started windrun on Sunday and that was 
also the last day we had rain, otherwise maybe I would have caught it.

And you're correct, 'maxsum' works as you described!

Thanks a lot for your help :)


On Tuesday, November 26, 2019 at 9:35:26 PM UTC-5, gjr80 wrote:
>
> Hi,
>
> I am not sure I am seeing anything unexpected in your data/output. You 
> mention 'max sum' but I don't see 'max' anywhere in the code, only 'sum'. 
> The Seasons skin statistics module gives statistics over various periods. 
> By default it is day, week, month and year. For rainfall this is the total 
> rainfall for the current day, current week, current month and current year. 
> If you have duplicated the statistics.inc rain code substituting windrun 
> for rain then you will have the total windrun for the current day, current 
> week etc. From the data you show and code you are using the output is 
> exactly that. If you are seeking to display the highest daily windrun for 
> the current week, current month and current year then you need to change 
> your windrun code to use the appropriate aggregate. Changing 
> $archive.windrun.sum.format(add_label=False) to (untested) 
> $archive.windrun.maxsum.format(add_label=False) should work.
>
> Or have I missed the issue you are having?
>
> Gary
>
> On Wednesday, 27 November 2019 12:09:05 UTC+10, Jared wrote:
>>
>> Hi,
>>
>> I've enabled windrun, and it seems to be writing to the database and 
>> functioning normally.  For my skin I'm running Seasons but adding a couple 
>> of data points.  I now want to add windrun to my statistics page, and it 
>> seemed like it should function exactly like rain would, since the both 
>> aggregate on a daily basis.
>>
>> Rain  looks like:
>>
>> 
>>   $obs.label.rain
>>   $unit.label.rain
>>   #for $archive in $archive_data
>>   $archive.rain.sum.format(add_label=False)
>>   #end for
>> 
>>
>> My new windrun  looks like:
>>
>> 
>>   $obs.label.windrun
>>   $unit.label.windrun
>>   #for $archive in $archive_data
>>   $archive.windrun.sum.format(add_label=False)
>>   #end for
>> 
>>
>>
>> But for some reason this isn't taking the "max sum" for the day like Rain 
>> does, it's adding it for the whole week.  Here's the HTML output for both 
>> (Today in column 1 and Week in column 2) and the last 10 archive_day 
>> records for both from the database.  There's the 0.76 for rain.  But it's 
>> adding the windrun all together to make 66.7 for the week, rather than 
>> taking 31, the highest value so far for the week.  8.75 + 27.0 + 31.0 = 
>> 66.75.  Why are they behaving differently?
>>
>>
>>
>>
>>
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4a2857c1-7ec3-477b-882a-a41ce45daf7a%40googlegroups.com.

[weewx-user] Re: Sun & Moon

[francisco javier martinez de lizarduy]

First of all, I apologize for the delay in replying. 

This question I made is not very important, as your skin works perfectly. 
Furthermore,

 I congratulate you and thank you for your great work. 

1) I don’t really work with Linux; weewx works on my Windows PC after 
installing weewx-windows. There is difference in relation to a "pure Linix" 
installation; for example in the name of some folders. 

2) Yes, I have pyephem installed:
Package Version
--- ---
Cheetah33.2.4
configobj   5.0.6
Django  1.11.25
ephem   3.7.7.0
image   1.5.27
Markdown3.1.1
paho-mqtt   1.4.0
Pillow  6.2.0
pip 19.3.1
pyephem 3.7.7.0
python-dateutil 2.8.0
pytz2019.3
pyusb   1.0.2
setuptools  41.4.0
six 1.12.0
uptime3.0.1

 



3) I do not know where to find "syslog". Thank you very much for your 
kindness



El lunes, 25 de noviembre de 2019, 20:03:56 (UTC+1), francisco javier 
martinez de lizarduy escribió:
>
> Greetings to all and thank you very much for your great work.
>
>  I have installed the Belchertown skin that I think is magnificent: 
>
>  http://kocher.es/index.html
>
>  In the Sun & Moon box,  the sunrise and sunset data does not appear, the 
> data also appears in the moon with a pale text.
>
>  Despite this, the information on the almanac seems correct. 
>
>  What could be the cause of it? Thank you very much
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/02bb3e01-00fc-4b57-babc-ab65e5e2178a%40googlegroups.com.

[weewx-user] Re: Crazy windSpeed from BloomSky when STORM's battery goes flat

[Rick M0LEP]

On Wed 27 Nov gjr80 wrote:
> Good, thanks. That will give me some time to juggle drivers;

Sounds like fun... ;)

I figure, unless we have some good sunny mornings, the STORM's battery 
will be flat again inside a week. It took a bit over four dull grey days 
to drop from full to shut-down this week.

The STORM's solar panel coped OK during the brighter months, but now 
we've got to the time of the year when, even if the Sun were to shine 
all day, the panel on mine would only get two or three hours of direct 
sunshine, and that mostly at a low angle. There's a forest on the 
hillside to the south of me, so there's not much chance of direct 
sunlight in the afternoon. I may have to try pointing the panel East 
rather than South (the geometry of the mounting doesn't allow for 
anything in between) and setting it so the panel's nearer vertical to 
try to catch any morning sun better.

-- 
73, Rick, M0LEP

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/73bc.5dde6446.dc7d7.m0lep%40hewett.org.

[weewx-user] Re: Crazy windSpeed from BloomSky when STORM's battery goes flat

[gjr80]

Good, thanks. That will give me some time to juggle drivers; I have three 
versions at various states of completeness, the current release, a multi-id 
version and a WeeWX 4.0/python2/3 version. Need some time to massage them 
together and get a WeeWX 3 version and a WeeWX 4 version.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/656ec2a3-f44f-4b31-901d-1c5a7007327c%40googlegroups.com.

[weewx-user] Re: Crazy windSpeed from BloomSky when STORM's battery goes flat

[Rick M0LEP]

On Wed 27 Nov gjr80 wrote:
> Whoops, the development version of the BloomSky driver picks up the 
> api key from weewx.conf, the current release version does not. Try 
> adding --api-key=YOUR_API_KEY to the command line you are using.

I'd just figured that out from burrowing into the code. Of course, with 
the sun up (and my having given the STORM a 100% charge overnight via 
USB) the STORM is now reporting nicely, so this is roughly what it 
looks like when it's working:

[
  {
"ALT": 129.0, 
"BoundedPoint": "", 
"CityName": "***", 
"DST": 0, 
"Data": {
  "DeviceType": "SKY2", 
  "Humidity": 99, 
  "ImageTS": 1574847464, 
  "ImageURL": 
"http://s3-us-west-1.amazonaws.com/bskyimgs/vmZionpk=.jpg";, 
  "Luminance": , 
  "Night": false, 
  "Pressure": 967, 
  "Rain": false, 
  "TS": 1574847464, 
  "Temperature": 7.8, 
  "UVIndex": , 
  "Voltage": 2610
}, 
"DeviceID": "***", 
"DeviceName": "Hillside", 
"FullAddress": "***, ***, England, GB", 
"LAT": 51.***, 
"LON": -2.***, 
"NumOfFollowers": 0, 
"Point": {}, 
"PreviewImageList": [
  "http://s3-us-west-1.amazonaws.com/bskyimgs/rmJakoJU=.jpg";, 
  "http://s3-us-west-1.amazonaws.com/bskyimgs/sl5KnoJ4=.jpg";, 
  "http://s3-us-west-1.amazonaws.com/bskyimgs/tlZiooJo=.jpg";, 
  "http://s3-us-west-1.amazonaws.com/bskyimgs/tnpWnmpU=.jpg";, 
  "http://s3-us-west-1.amazonaws.com/bskyimgs/unZGsnp4=.jpg";
], 
"RegisterTime": 1557998230, 
"Searchable": true, 
"Storm": {
  "24hRain": 1.6, 
  "RainDaily": 0.0, 
  "RainRate": 0.0, 
  "SustainedWindSpeed": 0.62, 
  "UVIndex": "1", 
  "WindDirection": "SE", 
  "WindGust": 1.31
}, 
"StreetName": "***", 
"UTC": 0, 
"VideoList": [
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-22.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-23.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-24.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-25.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-26.mp4";
], 
"VideoList_C": [
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-22_C.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-23_C.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-24_C.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-25_C.mp4";, 
  "http://s3.amazonaws.com/bskytimelapses/***2_0_2019-11-26_C.mp4";
]
  }
]

I'll try to grab the data next time the STORM's battery goes flat.

-- 
73, Rick, M0LEP

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/62e4.5dde48a1.120af.m0lep%40hewett.org.

[weewx-user] Re: Crazy windSpeed from BloomSky when STORM's battery goes flat

[gjr80]

Whoops, the development version of the BloomSky driver picks up the api key 
from weewx.conf, the current release version does not. Try adding 
—api-key=YOUR_API_KEY to the command line you are using.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/745eba52-f508-4e85-b1c8-b6023759ecfc%40googlegroups.com.

[weewx-user] Re: Crazy windSpeed from BloomSky when STORM's battery goes flat

[Rick M0LEP]

On Wed 27 Nov gjr80 wrote:
> Is that how you obtained the data above? If not the output from the 
> --get-json-data when the STORM is misbehaving would help.

   No, I was using a script that uses BloomSkyAPIClient, and I've a 
feeling that may be somewhat older than the present BloomSky driver in 
weewx.

> $ PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/bloomsky.py
>   --get-json-data

When I try this I get an error thus:

Traceback (most recent call last):
  File "/usr/share/weewx/user/bloomsky.py", line 827, in 
main()
  File "/usr/share/weewx/user/bloomsky.py", line 798, in main
get_json_data(opts.api_key)
  File "/usr/share/weewx/user/bloomsky.py", line 823, in get_json_data
raw_data = api_client.sd.get_data()
  File "/usr/share/weewx/user/bloomsky.py", line 708, in get_data
params, headers)
  File "/usr/share/weewx/user/bloomsky.py", line 720, in get_request
obfuscated['Authorization'] = ''.join(("", 
obfuscated['Authorization'][-4:]))
TypeError: 'NoneType' object has no attribute '__getitem__'

The python command is ponting at python2.7

I tried using python3 but that didn't like the weewx modules.

-- 
73, Rick, M0LEP

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5f3b.5dde3d16.d1ee9.m0lep%40hewett.org.