weewx and the meteostick

[J.L. Blom]

I recently found that you can use the meteostick to receive the Davis
vantage ISS signals. If I understand correctly the output of the
meteostick that received values is in csv-format. As I am seriously
considering to purchase that combination and I wonder if I can use that
with weewx. It looks like a simple solution - although the meteostick is
not cheap - but I don't need the console as I can see my station values
on tablet, smart-phone or workstation..
I Hope somebody has experience already with this.
Thanks in advance,
Joep

[Luc Heijst]

Hi Joep,

The meteostick can't work without a meteobridge, the total investment would be about 300 euro (in Holland).

As far as I know there is no interface yet for weewx for this combination.

Besides a console is showing local weather data, it contains also the nescessary pressure sensor (also inside temp and hummidity sensors)

The alternative for a Davis console is a Davis Envoy. The Envoy also has a pressure sensor.

Together with a Davis USB data logger the price would be about 345 euro.

The advance of a (battery powered) Davis console (Vue or VP2) with a datalogger is that during a power break data will continue be collected and stored for later retrieval.

Luc 

[Luc Heijst]

Maybe I was a bit too fast in my conclusion...

The meteostick also has a high quality pressure sensor on board and can work with third party software.

Attached the meteostick manual with a description how to interface with third party programs.

Maybe our drivers expert Matthew can have a look at the protocol to see the possibilities for a weewx driver.

Luc

[mwall]

On Friday, January 29, 2016 at 12:15:45 PM UTC-5, Luc Heijst wrote:

The meteostick also has a high quality pressure sensor on board and can work with third party software.

Attached the meteostick manual with a description how to interface with third party programs.

Maybe our drivers expert Matthew can have a look at the protocol to see the possibilities for a weewx driver.

writing a driver for that should take less than an hour to achieve basic functionality, perhaps a couple of days for complete testing.

it could take considerably longer to make the driver work with all of the meteostick capabilities.  for example, a single meteostick can listen to multiple vantage stations at once.  there may be some issues with decoding davis-specific data.

another option is to use a software-defined radio (SDR - discussed elsewhere in this forum and at wxforum).  those cost about 25$US and they can decode transmissions from many different types of hardware, including fine offset, acurite, and davis stations.  should be easy to write a weewx driver for those, too, and use existing opensource software for the rf decoding.

here is one example:

http://www.amazon.com/NooElec-NESDR-Mini-Compatible-Packages/dp/B009U7WZCA

the SDRs do not have a pressure sensor or temperature sensor in them.

m

[Luc Heijst]

Thanks Matthew,

Well, it's up to Joep if he wants to buy a meteostick and develop a driver with your guidance. 

I would like to assist because this is a challenge, but I don't own a meteostick unfortuanately..

Luc

[J.L. Blom]

> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+...@googlegroups.com
> <mailto:weewx-user+...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.
Luc & Mathew,
Thanks for your clarifying answers. The meteostick looks like a
promising solution but is rather pricey if it has to be used with a
meteobridge. However, the manual says it can receive the davis ISS
signals and give them through as 1:1 raw data which I would think can be
directly used as input for weewx but I am not yet so familiar with the
driver construction that I can see how to implement it.

However, I did not know the existence of a software defined radio for
this purpose. My HAM-radiotime is from before the use of computers as
receivers (although I had a serial interface linked with my set and
coupled to a computer using standard serial port (modem) protocol for
data transport). I am still licensed but I will look into it as I have
no idea which hardware is necessary and what type of antenna's have to
be used, except maybe the use of a wireless dongle.
I recently read somewhere that somebody had developed a driver for the
meteostick but I have to look in the weewx archives to find it back.
Luc, can you clarify why you think a meteobridge is necessary?
Greetings,
Joep

[mwall]

On Saturday, January 30, 2016 at 8:13:02 AM UTC-5, Joep L. Blom wrote:

Thanks for your clarifying answers. The meteostick looks like a
promising solution but is rather pricey if it has to be used with a
meteobridge. However, the manual says it can receive the davis ISS
signals and give them through as 1:1 raw data which I would think can be
directly used as input for weewx but I am not  yet so familiar with the
driver construction that I can see how to implement it.

the meteostick is a nice implementation, especially since most of the work is already done for you.  fergusd has already started an implementation of a weewx driver:

https://github.com/fergusd/weewx-meteostick

however, there are other alternatives for reading sensor data directly from the rf:

https://github.com/cmatteri/CC1101-Weather-Receiver/

m

[Luc Heijst]

Joep,

This was the information given on a Dutch site who sell the meteobridge. But as I can see now, with a dedicated third-party (weewx) driver a meteobridge isn't nescessary.

Luc

[J.L. Blom]

> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+...@googlegroups.com
> <mailto:weewx-user+...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

Luc,
Thanks for the clarification. But I think I first will explore the road
using SRD as Mathew pointed out.. As Ham-radio amateur is that a very
interesting road and maybe I can find a way to read the data of the TFA
Nexus (=Hideki) as well.
It is all new to me but I'll explore it as soon as I can find the time.
Greetings,
Joep

[Thomas Keffer]

The website wxforum.net is the center of effort for using SDR to pick up RF signals directly. Indeed, a search of the site for "SDR" will return dozens of entries. 

The effort on the Davis Vantage series started with this post, but I'm sure there are more recent threads.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

[fraban]

Hi all

I still have meteostick here, also a Vantage Pro 2 and a Vantage vue.  Vantage Pro2 and Vue are still running with data loggers from Davis one with console, one with the envoy. Now I try to get it run with the meteostick.

I Installed weewx debian style.  So still I have a simple question.  Where to put the   files from https://github.com/fergusd/weewx-meteostick   on a debian installation. I know the paths conversion  /home/weewx/weewx.conf -> /etc/weewx/weewx.conf 

/home/weewx/skins -> /etc/weewx/skins

/home/weewx/bin/user -> /usr/share/weewx/user ...

Should I only copy the file from /bin/user to  /usr/share/weewx/user ?  

I guess I need a little help at this point. 

thanks Frank

[mwall]

On Tuesday, February 9, 2016 at 1:32:52 PM UTC-5, fraban wrote:

Hi all

I still have meteostick here, also a Vantage Pro 2 and a Vantage vue.  Vantage Pro2 and Vue are still running with data loggers from Davis one with console, one with the envoy. Now I try to get it run with the meteostick.

I Installed weewx debian style.  So still I have a simple question.  Where to put the   files from https://github.com/fergusd/weewx-meteostick   on a debian installation.

Should I only copy the file from /bin/user to  /usr/share/weewx/user ?  

I guess I need a little help at this point. 

frank,

the standard way to install an extension goes like this:

1) download the extension.  in this case, choose the 'Download ZIP' button at https://github.com/fergusd/weewx-meteostick, or do it by command line:

wget https://github.com/fergusd/weewx-meteostick/archive/master.zip

2) install the extension:

sudo wee_extension --install weewx-meteostick-master.zip

3) since this is a driver, run wee_config to select the driver you just installed:

sudo wee_config

4) start weewx

sudo /etc/init.d/weewx start

m

[fraban]

Yes this way I tried also before - now again.

And yes the file weewxmeteostick.py will be written to the user directory. 

in the weewx.conf I can see

# Options for extension 'weewxmeteostick'

[WEEWXMETEOSTICK]

    driver = user.weewxmeteostick

    poll_interval = 2.5

I changed

station_type = WEEWXMETEOSTICK 

Now I tried wee_device to check what happened and got back. 

root@raspberrypi:/etc/weewx# wee_device

Using configuration file /etc/weewx/weewx.conf

Cannot load configurator for WEEWXMETEOSTICK

Hm whats missing here ? Any idea ?

Thanks Frank

[fraban]

Ok - here is the problem .  the driver is not listed ....  I try to copy the driver into the main-driver directory - I´ll make a symbolic link ,,, and give this a try.

root@raspberrypi:~# wee_config --list-drivers

Module name              Driver name    Version  Status

  weewx.drivers.acurite    AcuRite        0.24

  weewx.drivers.cc3000     CC3000         0.9

  weewx.drivers.fousb      FineOffsetUSB  1.8

  weewx.drivers.simulator  Simulator      3.0

  weewx.drivers.te923      TE923          0.16

  weewx.drivers.ultimeter  Ultimeter      0.15

  weewx.drivers.vantage    Vantage        3.0

  weewx.drivers.vueiss     ?              ?        No module named MySQLdb

  weewx.drivers.wmr100     WMR100         3.1

  weewx.drivers.wmr200     WMR200         3.1

  weewx.drivers.wmr300     WMR300         0.9

  weewx.drivers.wmr9x8     WMR9x8         3.0

  weewx.drivers.ws1        WS1            0.24

  weewx.drivers.ws23xx     WS23xx         0.24

  weewx.drivers.ws28xx     WS28xx         0.34

[fraban]

Nope - not working -

I cannot see the driver for meteostick at the moment and so no chance to choose it.

There must be a simple error I did not see at the moment. 

Regards Frank

[Luc Heijst]

Frank,

Weewx.conf says:

 

[WEEWXMETEOSTICK]

    driver = user.weewxmeteostick

    poll_interval = 2.5

so file weewxmeteostick.py should go to the user directory. In your case that will be: /usr/share/weewx/user. 

Not sure what the use is of the files meteostickSerial.py, mystick.py, pythread.py and sampledata in the home directory of the driver.

Luc

[fraban]

Luc

yes thats correct - I have the file weewxmeteostick.py  in the right directory.

root@raspberrypi:/usr/share/weewx/user# ls -al

insgesamt 60

drwxr-xr-x  3 root root 4096 Feb  9 21:11 .

drwxr-xr-x 11 root root 4096 Feb  3 12:15 ..

-rw-r--r--  1 root root  541 Dez  7 00:52 extensions.py

-rw-r--r--  1 root root  419 Feb  3 12:15 extensions.pyc

-rw-r--r--  1 root root  306 Jan 18 00:04 __init__.py

-rw-r--r--  1 root root  324 Feb  3 12:15 __init__.pyc

drwxr-xr-x  4 root root 4096 Feb  9 20:34 installer

-rw-r--r--  1 root root 7955 Feb  9 21:11 weewxmeteostick.py

-rw-r--r--  1 root root 7533 Feb  9 21:11 weewxmeteostick.pyc

--

sampledata is as its named a sampl. This I can produce with running meteostick and "minicom" command. I can read the meteostick natively, so I know it is working. 

Still question is why I have the error

"Cannot load configurator for WEEWXMETEOSTICK"

when starting weewx 

thanks Frank

[mwall]

On Tuesday, February 9, 2016 at 3:18:42 PM UTC-5, fraban wrote:

Nope - not working -

I cannot see the driver for meteostick at the moment and so no chance to choose it.

There must be a simple error I did not see at the moment. 

the file weewxmeteostick.py does not include DRIVER_NAME or DRIVER_VERSION - without these wee_config does not know that it is a driver.

you can either manually set station_type in weewx.conf.

or if you want to 'fix' the driver so that wee_config can recognize it, add these two lines just before the CommunicationError class definition:

DRIVER_NAME = 'WEEWXMETEOSTICK'
DRIVER_VERSION = '1.0'

you do not need the symlink in the weewx/drivers directory.

m

[mwall]

On Tuesday, February 9, 2016 at 3:37:27 PM UTC-5, fraban wrote:

Luc

yes thats correct - I have the file weewxmeteostick.py  in the right directory.

frank, try this fork:

https://github.com/matthewwall/weewx-meteostick

i added the DRIVER_ identifiers and change the name from WEEWXMETEOSTICK to simply Meteostick.

if it works, maybe fergus will accept the changes in master.

m

[fraban]

Ok I added the 2 lines to the weewxmeteostick.py  and now  wee_config shows the driver.

..

but at the end there are new errors ...  ok next one ...

Enter a brief description of the station, such as its location.  For example:

Santa's Workshop, North Pole

description [Neufahrn - Mintraching - Envoy]:

Specify altitude, with units 'foot' or 'meter'.  For example:

35, foot

12, meter

altitude [464, meter]:

Specify latitude in decimal degrees, negative for south.

latitude [48.3]:

Specify longitude in decimal degrees, negative for west.

longitude [11.7]:

Indicate the preferred units for display: 'metric' or 'us'

units:

Installed drivers include:

  0) WEEWXMETEOSTICK (user.weewxmeteostick)

  1) AcuRite         (weewx.drivers.acurite)

  2) CC3000          (weewx.drivers.cc3000)

  3) FineOffsetUSB   (weewx.drivers.fousb)

  4) Simulator       (weewx.drivers.simulator)

  5) TE923           (weewx.drivers.te923)

  6) Ultimeter       (weewx.drivers.ultimeter)

  7) Vantage         (weewx.drivers.vantage)

  8) WMR100          (weewx.drivers.wmr100)

  9) WMR200          (weewx.drivers.wmr200)

 10) WMR300          (weewx.drivers.wmr300)

 11) WMR9x8          (weewx.drivers.wmr9x8)

 12) WS1             (weewx.drivers.ws1)

 13) WS23xx          (weewx.drivers.ws23xx)

 14) WS28xx          (weewx.drivers.ws28xx)

choose a driver [0]:

Traceback (most recent call last):

  File "/usr/bin/wee_config", line 115, in <module>

    main()

  File "/usr/bin/wee_config", line 110, in main

    config_mgr.run(args, options)

  File "/usr/share/weewx/weecfg/config.py", line 102, in run

    self.modify_config(config_dict, options)

  File "/usr/share/weewx/weecfg/config.py", line 119, in modify_config

    stn_info = self.get_stn_info(config_dict, options)

  File "/usr/share/weewx/weecfg/config.py", line 150, in get_stn_info

    stn_info.update(weecfg.prompt_for_driver_settings(driver))

  File "/usr/share/weewx/weecfg/__init__.py", line 1061, in prompt_for_driver_settings

    loader_function = getattr(driver_module, 'confeditor_loader')

AttributeError: 'module' object has no attribute 'confeditor_loader'

[mwall]

On Tuesday, February 9, 2016 at 3:49:50 PM UTC-5, fraban wrote:

Ok I added the 2 lines to the weewxmeteostick.py  and now  wee_config shows the driver.

..

but at the end there are new errors ...  ok next one ...

try this one now:

https://github.com/matthewwall/weewx-meteostick

i added the conf editor.

(you should be able to run weewx anyway - all i'm doing is adding the bits that make the meteostick driver work with wee_config, hopefully to make setup easier)

m

[L.J.M. Heijst]

Matthew, Fabian,

It looks like the driver is calculating rain from 0.01 inch buckets. Be aware this has to be altered when using the 0.2 mm rain adapter.

Also the driver lacks an init part that sets up the right communication protocol.

Luc

Verstuurd vanaf mijn iPad

--
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/xQQmRQpDqU8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.

[fraban]

Hm - no not working similiar error I´ve had before, look here. 

I try yours. There must be something other in the original driver from from fergus.

Installed drivers include:

  0) Meteostick      (user.meteostick)

  1) WEEWXMETEOSTICK (user.weewxmeteostick)

  2) AcuRite         (weewx.drivers.acurite)

  3) CC3000          (weewx.drivers.cc3000)

  4) FineOffsetUSB   (weewx.drivers.fousb)

  5) Simulator       (weewx.drivers.simulator)

  6) TE923           (weewx.drivers.te923)

  7) Ultimeter       (weewx.drivers.ultimeter)

  8) Vantage         (weewx.drivers.vantage)

  9) WMR100          (weewx.drivers.wmr100)

 10) WMR200          (weewx.drivers.wmr200)

 11) WMR300          (weewx.drivers.wmr300)

 12) WMR9x8          (weewx.drivers.wmr9x8)

 13) WS1             (weewx.drivers.ws1)

 14) WS23xx          (weewx.drivers.ws23xx)

 15) WS28xx          (weewx.drivers.ws28xx)

choose a driver [0]:

Traceback (most recent call last):

  File "/usr/bin/wee_config", line 115, in <module>

    main()

  File "/usr/bin/wee_config", line 110, in main

    config_mgr.run(args, options)

  File "/usr/share/weewx/weecfg/config.py", line 102, in run

    self.modify_config(config_dict, options)

  File "/usr/share/weewx/weecfg/config.py", line 119, in modify_config

    stn_info = self.get_stn_info(config_dict, options)

  File "/usr/share/weewx/weecfg/config.py", line 150, in get_stn_info

    stn_info.update(weecfg.prompt_for_driver_settings(driver))

  File "/usr/share/weewx/weecfg/__init__.py", line 1062, in prompt_for_driver_settings

    editor = loader_function()

  File "/usr/share/weewx/user/meteostick.py", line 25, in confeditor_loader

    return MeteostickConfEditor()

NameError: global name 'MeteostickConfEditor' is not defined

[fraban]

Just found a 2nd source using a meteostick with weewx

https://github.com/buwx/weewx 

but still there is also no more detailled description. Seems that a mysql is addionally needed. I will look at this tomorrow. May be there are some things which can help the meteostick run with weewx. 

thx frank

[mwall]

On Tuesday, February 9, 2016 at 4:20:03 PM UTC-5, fraban wrote:

Hm - no not working similiar error I´ve had before, look here. 

I try yours. There must be something other in the original driver from from fergus.

no, it is a typo on my part.  in meteostick.py change line 218 from this:

class MeteostickEditor(weewx.drivers.AbstractConfEditor):

to this:

class MeteostickConfEditor(weewx.drivers.AbstractConfEditor):

m

[mwall]

On Tuesday, February 9, 2016 at 4:35:37 PM UTC-5, fraban wrote:

Just found a 2nd source using a meteostick with weewx

https://github.com/buwx/weewx 

but still there is also no more detailled description.

that one is slightly different.  for that one you configure meteostick to send data to a mysql database (perhaps using meteobridge/plug/hub/pro?).  then the driver pulls data from the mysql database.

m

[fraban]

Yes I saw - thanks for the quick check

[fraban]

OK - now I was able to run the things without an conf error. - Thank you for this help.

But still the system tolds me at the end that it cannot load the "Meteostick" ..  

Look here

...

Installed drivers include:

  0) Meteostick      (user.meteostick)

  1) WEEWXMETEOSTICK (user.weewxmeteostick)

  2) AcuRite         (weewx.drivers.acurite)

  3) CC3000          (weewx.drivers.cc3000)

  4) FineOffsetUSB   (weewx.drivers.fousb)

  5) Simulator       (weewx.drivers.simulator)

  6) TE923           (weewx.drivers.te923)

  7) Ultimeter       (weewx.drivers.ultimeter)

  8) Vantage         (weewx.drivers.vantage)

  9) WMR100          (weewx.drivers.wmr100)

 10) WMR200          (weewx.drivers.wmr200)

 11) WMR300          (weewx.drivers.wmr300)

 12) WMR9x8          (weewx.drivers.wmr9x8)

 13) WS1             (weewx.drivers.ws1)

 14) WS23xx          (weewx.drivers.ws23xx)

 15) WS28xx          (weewx.drivers.ws28xx)

choose a driver [0]:

Saved backup to /etc/weewx/weewx.conf.20160209224311

Saved configuration to /etc/weewx/weewx.conf

root@raspberrypi:~# nano /etc/weewx/weewx.conf

-- things look fine here

root@raspberrypi:~# wee_device

Using configuration file /etc/weewx/weewx.conf

Cannot load configurator for Meteostick ... Arghh hm ? 

root@raspberrypi:~#

[fraban]

I guess you are referring to these lines in the code.

    def calculate_rain(self, data_packet):

        rain = data_packet[3]

        if self.last_rain is not None:

            if rain == self.last_rain:

                inches_rain = 0

            else:

                inches_rain = (rain - self.last_rain) % 128 * 0.01

        else:

            inches_rain = 0

        self.last_rain = rain

        return inches_rain

--  this hat to be fixed to european with 0.2mm - you´re right.

Thank you for pointing this. 

[mwall]

On Tuesday, February 9, 2016 at 4:47:46 PM UTC-5, fraban wrote:

OK - now I was able to run the things without an conf error. - Thank you for this help.

But still the system tolds me at the end that it cannot load the "Meteostick" ..

root@raspberrypi:~# wee_device

Using configuration file /etc/weewx/weewx.conf

Cannot load configurator for Meteostick ... Arghh hm ? 

this is ok.  the not every hardware can be configured from software.

try running weewx.  first do it directly:

sudo weewxd /etc/weewx/weewx.conf

and watch the log file from another shell:

sudo tail -f /var/log/syslog

if that works you can run it as a daemon.

m

[fraban]

Before going foreward - here a snapshot from the running meteostick together with a DAVIS Vantage Vue. 

Using - minicom on raspberry to show the raw data .

It´s just Vantage Vue - meteostick and raspberry - without any DAVIS Console.  - So I hope we can get this run with weewx. 

?

mode:m 1

transmitter:t 2

repeater:r 255

verbose:v 0

debug:d 0

ledmode:l 1

bandwidth:b 0

threshold:x 180

output:o 2

probe:p 0

channel:c 255

filter:f 0

Wind id:2 speed:1.89m/s dir:243deg signal:-69db

Rain id:2 ticks:173 signal:-66db

Wind id:2 speed:2.84m/s dir:245deg signal:-66db

Outdoor id:2 temp:6.3C hum:64% signal:-67db

Wind id:2 speed:3.79m/s dir:255deg signal:-67db

Outdoor id:1 temp:6.5C hum:67% signal:-81db

Wind id:1 speed:3.79m/s dir:296deg signal:-81db

Rain id:2 ticks:173 signal:-66db

Wind id:2 speed:2.37m/s dir:117deg signal:-66db

Outdoor id:2 temp:6.3C hum:64% signal:-73db

Wind id:2 speed:1.42m/s dir:268deg signal:-73db

Panel id:2 power:2.4% signal:-67db

Indoor temp:19.2C press:939.15hPa valid packets:48.2%

Rain id:2 ticks:173 signal:-67db

Wind id:2 speed:2.84m/s dir:224deg signal:-67db

Outdoor id:2 temp:6.3C hum:64% signal:-68db

Wind id:2 speed:1.89m/s dir:173deg signal:-68db

Rain id:2 ticks:173 signal:-69db

Wind id:2 speed:0.94m/s dir:252deg signal:-69db

Outdoor id:2 temp:6.3C hum:64% signal:-69db

Wind id:2 speed:0.94m/s dir:185deg signal:-69db

[fraban]

I try setting --  Record generation will be attempted in 'hardware'   to "software "... 

---

this one is the syslog with "hardware" setting

Feb  9 23:03:07 raspberrypi systemd[1]: Starting LSB: weewx weather system...

Feb  9 23:03:08 raspberrypi weewx[26221]: engine: Initializing weewx version 3.4.0

Feb  9 23:03:08 raspberrypi weewx[26221]: engine: Using Python 2.7.9 (default, Mar  8 2015, 00:52:26) #012[GCC 4.9.2]

Feb  9 23:03:08 raspberrypi weewx[26221]: engine: Platform Linux-4.1.13-v7+-armv7l-with-debian-8.0

Feb  9 23:03:08 raspberrypi weewx[26221]: engine: pid file is /var/run/weewx.pid

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Using configuration file /etc/weewx/weewx.conf

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Loading station type Meteostick (user.meteostick)

Feb  9 23:03:08 raspberrypi systemd[1]: Started LSB: weewx weather system.

Feb  9 23:03:08 raspberrypi weewx[26211]: Starting weewx weather system: weewx.

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: StdConvert target unit is 0x1

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Archive will use data binding wx_binding

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Record generation will be attempted in 'hardware'

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Using archive interval of 300 seconds

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Using binding 'wx_binding' to database 'weewx.sdb'

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Starting backfill of daily summaries

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Daily summaries up to date.

Feb  9 23:03:08 raspberrypi weewx[26225]: restx: Weather365: service version is 1.8.1

Feb  9 23:03:08 raspberrypi weewx[26225]: restx: Weather365: Data will be uploaded for station id U55CDPT8SH

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Starting up weewx version 3.4.0

Feb  9 23:03:08 raspberrypi weewx[26225]: engine: Starting main packet loop.

[fraban]

yes thats running now - thanks ...  but problem is now -  NO DATA  N/A

still have this message

root@raspberrypi:~# wee_device --info

Using configuration file /etc/weewx/weewx.conf

Cannot load configurator for Meteostick

Frank

[L.J.M. Heijst]

Frank,

The driver hasn't a configurator section that reacts on -- info (or any other configurator command).

Just start weewx as Matthew has pointed out. The sample data file show the raw data achieved with the o0 command. You use in your example the o2 command.

Luc

Verstuurd vanaf mijn iPad

--

[fraban]

Yes I did as Matthew pointed out. 

Still the result is....

root@raspberrypi:/usr/share/weewx/user# /etc/init.d/weewx stop

[ ok ] Stopping weewx (via systemctl): weewx.service.

root@raspberrypi:/usr/share/weewx/user# weewxd /etc/weewx/weewx.conf

LOOP:   2016-02-09 23:48:27 CET (1455058107) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058107, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-09 23:48:30 CET (1455058110) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058110, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-09 23:48:32 CET (1455058112) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058112, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-09 23:48:35 CET (1455058115) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058115, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-09 23:48:37 CET (1455058117) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058117, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-09 23:48:40 CET (1455058120) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058120, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-09 23:48:42 CET (1455058122) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455058122, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 0.0, rainRate: 0, usUnits: 1, windchill: None

and this is the corresponding syslog

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Initializing weewx version 3.4.0

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Using Python 2.7.9 (default, Mar  8 2015, 00:52:26) #012[GCC 4.9.2]

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Platform Linux-4.1.13-v7+-armv7l-with-debian-8.0

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Using configuration file /etc/weewx/weewx.conf

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Loading station type Meteostick (user.meteostick)

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: StdConvert target unit is 0x1

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Archive will use data binding wx_binding

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Record generation will be attempted in 'hardware'

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Using archive interval of 300 seconds

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Using binding 'wx_binding' to database 'weewx.sdb'

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Starting backfill of daily summaries

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Daily summaries up to date.

Feb  9 23:48:27 raspberrypi weewx[27771]: restx: Weather365: service version is 1.8.1

Feb  9 23:48:27 raspberrypi weewx[27771]: restx: Weather365: Data will be uploaded for station id U55CDPT8SH

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Starting up weewx version 3.4.0

Feb  9 23:48:27 raspberrypi weewx[27771]: engine: Starting main packet loop.

Feb  9 23:48:44 raspberrypi weewx[27771]: engine: Keyboard interrupt.

[L.J.M. Heijst]

Did you change your meteostick output to produce raw data (o0 format). Set with command o0. The driver can't decipher the format when it set to human readable output (o2 format).

Luc

Verstuurd vanaf mijn iPad

[L.J.M. Heijst]

Hi,

I found this info about the vantage raw data format. It is experimental and not complete yet.

https://github.com/dekay/DavisRFM69/wiki/Message-Protocol

Luc

Verstuurd vanaf mijn iPad

[L.J.M. Heijst]

Frank,

When filtering is switched off (f0) you will get some data from your other weather station (Vantage pro) on channel 1 during frequency hopping. You don't want the weewx driver put this data in the weewx (Vantage vue) database, so better set filtering on (f1).

Luc

Verstuurd vanaf mijn iPad

--

[fraban]

Hi Luc,

still I´m not the Python-specialist - I can read and understand the code step by step. At the moment I guess the problem is that weewx - the fresh installed weewx.driver is working with weewx, but still is not reading data from the /dev/ttyUSB0 where the meteostick is connected. I first have to understand how the other python scripts work in the https://github.com/matthewwall/weewx-meteostick  and how to get the work. 

actual situation is: meteostick is connected. I can read the data raw by using minicom. But if I start weewx then data is not seen. So there is a missing step between reading data from the meteostick /dev/ttyUSB0 and the weewx-driver for meteostick.  I hope you understand where my problem is located. 

What is meteostickSerial.py doing and how to get it run with weewx if we need ? 

What is mystick.py doing ?  

Step by step going forward - I want to understand it and also run it :-) 

Frank 

[fraban]

Ok next step to get it work :-) 

In the back I started minicom and now I can the meteostick data in this format: 

Thats same format as Fergus has in his sampledata

# MeteoStick Version 2.3b1 (Apr 24 2015 12:14:04), Free RAM 723, SN: EEE372B3CF926000

# License Information:

#   MeteoStick (c) 2014-2015 by smartbedded.com

?

# Meteostick Version 2.3b1

t1

# listening to transmitter 1

f1

# filter on

o0

# output raw (8 bytes)

m1

# chip authentication ok: 14

# frequency band 868MHz (EU)

B 28627 325073 244 94423 0 0

I 100 A0 3 88 4D 39 0 B7 F0  -83 2560750 -111

I 102 E0 2 6C 75 3 0 BF F0  -80 5125016 223

I 103 50 3 74 E8 62 0 72 1A  -83 2562512 -23

I 104 60 4 8B B 43 0 BD 57  -80 2562516 138

I 100 80 4 98 17 29 0 64 F7  -82 2562500 -106

I 101 E0 5 8D 75 3 0 2A 7A  -82 2562508 55

I 102 50 6 99 E8 63 0 DF 10  -80 2562512 222

I 103 40 4 91 6 C1 0 C4 F8  -85 2562512 -23

I 104 80 3 8C 17 29 0 D2 75  -82 2562504 139

I 100 E0 3 5E 75 3 0 D4 20  -83 2562508 -112

I 101 50 3 5E E8 63 0 1E CE  -82 2562492 56

I 102 90 1 5E B 3 2D E3 F9  -80 2562512 221

I 103 80 1 6B 17 2B 0 25 53  -84 2562520 -26

I 104 E0 1 C9 75 3 0 7 11  -82 2562516 139

I 100 50 1 D0 E8 63 0 25 2F  -80 2562508 -109

I 101 A0 4 DA 4A 3B 0 AB 85  -80 2562500 56

I 102 80 5 C7 17 29 0 6F 73  -80 2562496 224

---

Now I start the weewx by hand - not as a deamon and I will see this.  - IMHO the error after a few lines ... multiprocessing.connection.Client  I guess here I made something wrong or a mistake. 

---

root@raspberrypi:/etc/weewx# weewxd /etc/weewx/weewx.conf

LOOP:   2016-02-10 11:54:07 CET (1455101647) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101647, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 397.983357428, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:09 CET (1455101649) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101649, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.000924214, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:12 CET (1455101652) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101652, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.02725717, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:15 CET (1455101655) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101655, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.053555762, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:17 CET (1455101657) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101657, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.071053847, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:20 CET (1455101660) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101660, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.097283753, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:22 CET (1455101662) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101662, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.114747462, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:25 CET (1455101665) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101665, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.140908683, rainRate: 0, usUnits: 1, windchill: None

Exception in thread Thread-1:

Traceback (most recent call last):

  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner

    self.run()

  File "/usr/share/weewx/user/meteostick.py", line 52, in run

    conn = multiprocessing.connection.Client((self.hostname, self.port))

  File "/usr/lib/python2.7/multiprocessing/connection.py", line 169, in Client

    c = SocketClient(address)

  File "/usr/lib/python2.7/multiprocessing/connection.py", line 304, in SocketClient

    s.connect(address)

  File "/usr/lib/python2.7/socket.py", line 224, in meth

    return getattr(self._sock,name)(*args)

error: [Errno 111] Verbindungsaufbau abgelehnt

Exception in thread Thread-2:

Traceback (most recent call last):

  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner

    self.run()

  File "/usr/share/weewx/user/meteostick.py", line 52, in run

    conn = multiprocessing.connection.Client((self.hostname, self.port))

  File "/usr/lib/python2.7/multiprocessing/connection.py", line 169, in Client

    c = SocketClient(address)

  File "/usr/lib/python2.7/multiprocessing/connection.py", line 304, in SocketClient

    s.connect(address)

  File "/usr/lib/python2.7/socket.py", line 224, in meth

    return getattr(self._sock,name)(*args)

error: [Errno 111] Verbindungsaufbau abgelehnt

LOOP:   2016-02-10 11:54:27 CET (1455101667) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101667, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.158303775, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:30 CET (1455101670) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101670, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.184396313, rainRate: 0, usUnits: 1, windchill: None

LOOP:   2016-02-10 11:54:32 CET (1455101672) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101672, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.201791273, rainRate: 0, usUnits: 1, windchill: None

[L.J.M. Heijst]

Hi Frank,

Hi Luc, still I´m not the Python-specialist

That makes two of us!

- I can read and understand the code step by step. At the moment I guess the problem is that weewx - the fresh installed weewx.driver is working with weewx, but still is not reading data from the /dev/ttyUSB0 where the meteostick is connected.

As I said before, the weewx driver does't initialize the meteostock. What it should do:
send r\n (reset)
wait for answer (question mark)
# MeteoStick Version 2.3b1 (Jul  8 2015 20:40:35), Free RAM 723, SN: EEE372B3CFA44500

# License Information:
#   MeteoStick (c) 2014-2015 by smartbedded.com
?

send t2\r
wait for answer
# listening to transmitter 2
send f1\r
wait for answer
# filter on
send o0\r
wait for answer

# output raw (8 bytes)

send m1\r (set european freqency)
wait for answer
(now the meteostick will send a continuous stream of raw data packages like:
B 27640 341495 277 100309 0 0
I 200 80 0 81 28 5B 0 82 8E  -73 2560750 -85
I 201 E0 0 81 88 3 0 E7 1C  -72 2562440 83
I 202 50 0 81 FF 73 0 49 71  -72 2562448 249
I 203 40 0 81 FF C3 0 4D F8  -77 2562436 1
I 204 80 0 81 28 5B 0 82 8E  -74 2562444 169
I 200 E0 0 81 88 3 0 E7 1C  -74 2562428 -82
I 201 50 0 81 FF 73 0 49 71  -74 2562460 80
I 202 90 0 81 0 3 8 B1 73  -74 2562436 247
I 203 80 0 81 28 5B 0 82 8E  -78 2562440 1
I 204 E0 0 81 88 3 0 E7 1C  -74 2562444 166
I 200 50 0 81 FF 73 0 49 71  -74 2562444 -85
I 201 A0 0 81 CF 2B 0 9A 7E  -74 2562440 82
I 202 80 0 81 28 4B 0 81 FD  -73 2562444 249
I 203 E0 0 81 88 3 0 E7 1C  -76 2562428 1
I 204 50 0 81 FF 73 0 49 71  -74 2562460 169
I 200 A0 0 81 CF 2B 0 9A 7E  -73 2562432 -83
I 201 80 0 81 28 5B 0 82 8E  -73 2562444 81
The meteostick driver doesn't do this init part but expects to get the raw data packets right away.

I first have to understand how the other python scripts work in the https://github.com/matthewwall/weewx-meteostick  and how to get the work.  actual situation is: meteostick is connected. I can read the data raw by using minicom. But if I start weewx then data is not seen.

Two possibilities: 
1. the meteostick is not sendig data at all
2. the meteostick is sending data in the wrong format like:

Wind id:2 speed:1.89m/s dir:243deg signal:-69db
Rain id:2 ticks:173 signal:-66db
Wind id:2 speed:2.84m/s dir:245deg signal:-66db
Outdoor id:2 temp:6.3C hum:64% signal:-67db
Wind id:2 speed:3.79m/s dir:255deg signal:-67db
Outdoor id:1 temp:6.5C hum:67% signal:-81db
Wind id:1 speed:3.79m/s dir:296deg signal:-81db
Rain id:2 ticks:173 signal:-66db

So there is a missing step between reading data from the meteostick /dev/ttyUSB0 and the weewx-driver for meteostick.  I hope you understand where my problem is located.  What is meteostickSerial.py doing

It presets the meteostick (for channel 1), reads the data and writes the output to a standard output channel. The result is seen in file sampledata.

and how to get it run with weewx if we need ?

Here my knowledge is the same as yours!

What is mystick.py doing ?

Is is handling the raw data stream; no init part here either.

The meteostick.py driver needs the following things to do (as I can see now):

• add init part for setting up the meteostick; reading parameters from weewc.conf where needed (frequency, rain bucket size, which channels)
  My vantage pro2 has two channels: 1=iss, 2=wind sensor, so the channel id must be 3 (a combination of upto 8 bits). The driver doens't handle this part in the right way.
• add configuration part to work with wee_device; info, set channel(s), set frequency, (set rain_bucket_size) 
• skip info when a sensor is not present (FF)
• handle battery low data
• send debug output of: time since last packet, signal strenght, inside temp, 
• eventual handle rainRate data: it's in the raw message
• calculate rain on base of the rain_bucket_size

I will try to add some of the above in Matthews version of meteostick.py
More to come.

Luc

Step by step going forward - I want to understand it and also run it :-)  Frank

--  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/xQQmRQpDqU8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to

weewx-user+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.

Dit e-mailbericht is verzonden vanaf een virusvrije computer die wordt beschermd door Avast. www.avast.com

[L.J.M. Heijst]

Frank,

Ok next step to get it work :-)  In the back I started minicom and now I can the meteostick data in this format:  Thats same format as Fergus has in his sampledata # MeteoStick Version 2.3b1 (Apr 24 2015 12:14:04), Free RAM 723, SN: EEE372B3CF926000 # License Information: #   MeteoStick (c) 2014-2015 by smartbedded.com ? # Meteostick Version 2.3b1 t1 # listening to transmitter 1 f1

Listening to your vantage pro; not to your vantage vue as you had planned

Not sure what "rejected connection" means in this context.

LOOP:   2016-02-10 11:54:27 CET (1455101667) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101667, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.158303775, rainRate: 0, usUnits: 1, windchill: None LOOP:   2016-02-10 11:54:30 CET (1455101670) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101670, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.184396313, rainRate: 0, usUnits: 1, windchill: None LOOP:   2016-02-10 11:54:32 CET (1455101672) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101672, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.201791273, rainRate: 0, usUnits: 1, windchill: None

--

I don't understand why maxSolarRad is the only item with data (besides dateTime)

Frank, could you please send a longer log of your raw data? Now not all data is present. The minimum is 20 lines, but if you send 200 lines or so I will get an idea how data is changing.
Does your vantage pro has a UV sensor and/or solar sensor?

Could you please start weewx as a daemon with debug =1 set in weewx.conf? The driver writes all kind of debug and error messages I like to see in the debug and system logs.

Luc

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/xQQmRQpDqU8/unsubscribe. To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.

[fraban]

Hi Luc

thank you for your assistance. I still run here a Vantage Pro2 with ID1 and a Vantage Vue sending on ID 2.  I have both running with dataloggers from DAVIS ( one USB, and one IP-based weatherlink). The IP-based is connected with the envoy and the usb based is connected with the Vantage pro 2 console.  Every of them is running weewx 3.4. on raspberry.  But I don´t use the console so the DAVIS Console plus Weatherlink logger is overheaded for us here.  

Thats why we want to give meteostick or other solutions a try reading the Davis directly :-) . 

Meteostick seems to be intresting handling this I think we can get it run :-)  .  At the end of the day I look for a solution running Davis Stations without DAVIS Consoles and Data loggers.  Davis stations are great - but no need for me having a console .... 

I try now to read it again in the oO fromat and will have a closer look to the python code. 

Thanks Frank

[fraban]

Luc

short answer in between 

Am Mittwoch, 10. Februar 2016 12:41:46 UTC+1 schrieb Luc Heijst:

Frank,

Ok next step to get it work :-)  In the back I started minicom and now I can the meteostick data in this format:  Thats same format as Fergus has in his sampledata # MeteoStick Version 2.3b1 (Apr 24 2015 12:14:04), Free RAM 723, SN: EEE372B3CF926000 # License Information: #   MeteoStick (c) 2014-2015 by smartbedded.com ? # Meteostick Version 2.3b1 t1 # listening to transmitter 1 f1

Listening to your vantage pro; not to your vantage vue as you had planned

Yes correct - for the first step that does not matter if it is the Pro or the vue .. 

I guess it says - thats /dev/ttyUSB0 is blocked .... 

 

LOOP:   2016-02-10 11:54:27 CET (1455101667) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101667, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.158303775, rainRate: 0, usUnits: 1, windchill: None LOOP:   2016-02-10 11:54:30 CET (1455101670) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101670, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.184396313, rainRate: 0, usUnits: 1, windchill: None LOOP:   2016-02-10 11:54:32 CET (1455101672) altimeter: None, appTemp: None, barometer: None, cloudbase: None, dateTime: 1455101672, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: 398.201791273, rainRate: 0, usUnits: 1, windchill: None --

I don't understand why maxSolarRad is the only item with data (besides dateTime)

Same to me   

Frank, could you please send a longer log of your raw data? Now not all data is present. The minimum is 20 lines, but if you send 200 lines or so I will get an idea how data is changing.
Does your vantage pro has a UV sensor and/or solar sensor?

Yes the Pro2 has UV and solar. 

 

Could you please start weewx as a daemon with debug =1 set in weewx.conf? The driver writes all kind of debug and error messages I like to see in the debug and system logs.

no problem - I can do that.

-Frank

[fraban]

Luc 

here longer log of raw data - received by meteostick 

-frank

# MeteoStick Version 2.3b1 (Apr 24 2015 12:14:04), Free RAM 723, SN: EEE372B3CF926000

# License Information:

#   MeteoStick (c) 2014-2015 by smartbedded.com

?

# Meteostick Version 2.3b1

t1

# listening to transmitter 1

f1

# filter on

o0

# output raw (8 bytes)

m1

# chip authentication ok: 14

# frequency band 868MHz (EU)

B 28624 325098 244 94425 0 0

I 100 A0 3 D5 F6 29 0 F6 30  -86 2560750 -111

I 101 80 3 D3 18 19 0 5A 4  -81 2562500 53

I 102 E0 2 D0 78 3 0 43 42  -82 2562528 217

I 103 50 2 3D FE 71 0 E2 43  -89 2562504 -30

I 104 60 3 D5 10 3 0 B3 BC  -85 2562492 136

I 100 80 8 C8 18 19 0 B3 43  -87 2562516 -112

I 101 E0 7 DA 78 1 0 6E DC  -84 2562500 56

I 102 50 6 D6 FE 71 0 F1 B0  -82 2562512 220

I 104 80 6 DC 18 1B 0 CB DF  -85 5125008 138

I 100 E0 5 E0 78 1 0 6E 1D  -86 2562504 -107

I 101 50 3 DE FE 71 0 57 24  -81 2562504 55

I 102 90 4 C1 B 3 5F 8C A  -82 2562496 219

I 103 80 5 C7 18 1B 0 20 B5  -87 2562504 -32

I 104 E0 4 C6 78 3 0 B2 F9  -84 2562524 139

I 100 50 4 E4 FE 73 0 12 D0  -84 2562496 -110

I 101 A0 5 C9 F6 29 0 6F 20  -85 2562520 54

I 102 80 5 E7 18 19 0 71 99  -89 2562500 221

I 103 E0 5 DA 78 1 0 2A 5F  -89 2562496 -23

I 104 50 5 E2 FE 73 0 9F 18  -86 2562508 143

I 100 A0 7 E2 F6 29 0 2 F2  -88 2562516 -108

I 102 E0 6 CC 78 3 0 9E D1  -90 5125012 220

B 28662 324928 247 94429 25 61

I 100 80 6 E0 18 1B 0 A8 4  -86 7667036 -108

I 101 E0 6 D8 78 1 0 29 E5  -86 2562508 56

I 103 40 5 D5 9 41 0 FD 6D  -87 5125012 -22

I 104 80 4 D4 18 19 0 6C FD  -86 2562532 137

I 100 E0 4 CA 78 1 0 9B A9  -85 2562472 -108

I 101 50 6 E2 FE 73 0 71 CA  -84 2562512 54

I 102 90 5 E6 B 3 6F 76 6B  -83 2562496 217

I 103 80 5 F5 18 19 0 87 56  -86 2562508 -25

I 104 E0 4 F5 78 3 0 5 CC  -83 2562516 139

I 100 50 4 DF FE 71 0 46 44  -81 2562504 -108

I 101 A0 4 C1 F4 29 0 2E D2  -83 2562496 55

I 102 80 4 E7 18 19 0 DB C8  -82 2562516 223

I 103 E0 6 E9 78 1 0 73 B8  -87 2562508 -22

I 104 50 6 D8 FE 73 0 35 88  -86 2562500 139

I 100 A0 7 BF F4 2B 0 46 4D  -86 2562508 -109

I 101 80 7 CA 18 1B 0 5D B0  -85 2562508 56

I 102 E0 6 E2 78 1 0 6D A7  -84 2562504 223

I 103 50 7 DD FE 73 0 23 9C  -86 2562500 -27

I 104 60 6 E2 14 3 0 31 EF  -82 2562504 141

I 100 80 6 D5 18 19 0 5E CA  -82 2562520 -109

I 101 E0 5 FC 78 3 0 5C EA  -85 2562508 57

B 28692 324777 248 94425 25 32

I 102 50 5 D9 FE 71 0 CB 8C  -82 2544060 225

I 103 40 4 CC 9 C3 0 C2 16  -85 2562508 -24

I 104 80 5 D6 18 1B 0 4D A6  -85 2562512 140

I 101 50 9 AF FE 71 0 25 4B  -86 5125008 57

I 102 90 6 A3 B 1 7F 3E 33  -82 2562508 218

I 103 80 5 B8 18 19 0 D0 4C  -85 2562504 -25

I 104 E0 4 B1 78 3 0 A1 A1  -82 2562508 137

I 100 50 3 BF FE 73 0 1E 20  -84 2562508 -109

I 101 A0 3 D0 F4 2B 0 42 77  -85 2562492 56

I 102 80 3 DA 18 19 0 A9 73  -86 2562504 216

I 101 E0 7 BF 78 1 0 8B 4B  -89 2560750 54

I 102 50 7 A2 FE 73 0 B5 7  -85 2562500 222

I 103 40 5 A1 A 41 0 2C B9  -85 2562508 -18

I 104 80 3 86 18 19 0 93 7A  -82 2562508 143

B 28712 324697 250 94425 18 47

I 100 E0 2 BA 78 3 0 72 3B  -83 2543048 -107

I 102 90 3 EE B 1 8F A5 61  -81 5125012 222

I 104 E0 5 E4 78 1 0 A4 EC  -85 5125004 142

I 100 50 6 DE FE 73 0 12 11  -86 2562508 -108

I 101 A0 5 F6 F4 29 0 F9 47  -82 2562508 53

I 102 80 5 DB 18 1B 0 74 20  -84 2562512 221

I 103 E0 5 D5 78 3 0 98 D3  -90 2562500 -20

I 104 50 4 DD FE 71 0 AB 2C  -85 2562508 139

I 100 A0 4 DD F4 29 0 7A 47  -86 2562520 -107

I 101 80 2 DE 18 1B 0 AF B1  -87 2562492 54

I 102 E0 2 DE 78 3 0 E1 18  -84 2562504 220

I 103 50 1 C5 FE 71 0 16 1F  -86 2562512 -31

I 104 60 1 C2 18 83 0 F 8C  -86 2562496 141

I 100 80 2 0 18 19 0 C3 8A  -87 2562512 -108

[fraban]

Luc 

here is the debug - log.   weewx.conf with debug=1 

- frank

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Initializing engine

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdTimeSynch

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdTimeSynch

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdConvert

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdConvert

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdCalibrate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdCalibrate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdQC

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdQC

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.wxservices.StdWXCalculate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.wxservices.StdWXCalculate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdArchive

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Use LOOP data in hi/low calculations: 1

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdArchive

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdStationRegistry

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: StationRegistry: Data will not be posted. Missing option 'station_url'

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdStationRegistry

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdWunderground

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: Wunderground: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdWunderground

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdPWSweather

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: PWSweather: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdPWSweather

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdCWOP

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: CWOP: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdCWOP

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdWOW

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: WOW: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdWOW

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdAWEKAS

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: AWEKAS: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdAWEKAS

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdPrint

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdPrint

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdReport

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdReport

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Station does not support reading the time

Feb 10 13:01:53 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105714}

Feb 10 13:01:56 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105716}

Feb 10 13:01:58 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105719}

Feb 10 13:02:01 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105721}

Feb 10 13:02:03 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105724}

Feb 10 13:02:06 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105726}

Feb 10 13:02:08 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105729}

Feb 10 13:02:11 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105731}

Feb 10 13:02:13 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105734}

Feb 10 13:02:16 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105736}

Feb 10 13:02:18 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105739}

Feb 10 13:02:21 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105741}

Feb 10 13:02:23 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105744}

Feb 10 13:02:26 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105746}

Feb 10 13:02:28 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105749}

Feb 10 13:02:31 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105751}

Feb 10 13:02:33 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105754}

Feb 10 13:02:36 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105756}

Feb 10 13:02:38 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105759}

Feb 10 13:02:41 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105761}

Feb 10 13:02:43 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105764}

Feb 10 13:02:46 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105766}

Feb 10 13:02:48 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105769}

Feb 10 13:02:51 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105771}

Feb 10 13:02:53 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105774}

Feb 10 13:02:56 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105776}

Feb 10 13:02:58 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105779}

Feb 10 13:03:01 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105781}

Feb 10 13:03:03 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105784}

Feb 10 13:03:06 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105786}

Feb 10 13:03:08 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105789}

Feb 10 13:03:11 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105791}

Feb 10 13:03:13 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105794}

Feb 10 13:03:16 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105796}

Feb 10 13:03:18 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105799}

Feb 10 13:03:21 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105801}

[gjr80]

Luc/Frank,

I think you will find that maxSolarRad is being calculated and added to the packets by StdWXCalculate. StdWXCalculate is trying to add all derived obs that it can, but all of the other obs it knows about require some sort of measured weather observation eg outTemp, some sort of pressure etc. Since these (measured) obs are None it returns None for all except maxSolarRad. maxSolarRad only requires lat, long, altitude and time so it is calculated and added to the packet. So really just a red herring....

Gary

 

[fraban]

Luc -- the syslog for this session

- frank 

----

Feb 10 13:01:52 raspberrypi systemd[1]: Starting LSB: weewx weather system...

Feb 10 13:01:53 raspberrypi weewx[2926]: engine: Initializing weewx version 3.4.0

Feb 10 13:01:53 raspberrypi weewx[2926]: engine: Using Python 2.7.9 (default, Mar  8 2015, 00:52:26) #012[GCC 4.9.2]

Feb 10 13:01:53 raspberrypi weewx[2926]: engine: Platform Linux-4.1.13-v7+-armv7l-with-debian-8.0

Feb 10 13:01:53 raspberrypi weewx[2926]: engine: pid file is /var/run/weewx.pid

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Using configuration file /etc/weewx/weewx.conf

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Initializing engine

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading station type Meteostick (user.meteostick)

Feb 10 13:01:53 raspberrypi systemd[1]: Started LSB: weewx weather system.

Feb 10 13:01:53 raspberrypi weewx[2916]: Starting weewx weather system: weewx.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdTimeSynch

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdTimeSynch

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdConvert

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: StdConvert target unit is 0x1

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdConvert

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdCalibrate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdCalibrate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdQC

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdQC

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.wxservices.StdWXCalculate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.wxservices.StdWXCalculate

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdArchive

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Archive will use data binding wx_binding

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Record generation will be attempted in 'hardware'

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Using archive interval of 300 seconds

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Use LOOP data in hi/low calculations: 1

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Using binding 'wx_binding' to database 'weewx.sdb'

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Starting backfill of daily summaries

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Daily summaries up to date.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdArchive

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdStationRegistry

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: StationRegistry: Data will not be posted. Missing option 'station_url'

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdStationRegistry

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdWunderground

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: Wunderground: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdWunderground

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdPWSweather

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: PWSweather: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdPWSweather

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdCWOP

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: CWOP: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdCWOP

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdWOW

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: WOW: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdWOW

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.restx.StdAWEKAS

Feb 10 13:01:53 raspberrypi weewx[2930]: restx: AWEKAS: Posting not enabled.

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.restx.StdAWEKAS

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdPrint

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdPrint

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Loading service weewx.engine.StdReport

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Finished loading service weewx.engine.StdReport

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Starting up weewx version 3.4.0

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Station does not support reading the time

Feb 10 13:01:53 raspberrypi weewx[2930]: engine: Starting main packet loop.

Feb 10 13:03:24 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105804}

Feb 10 13:03:26 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105807}

Feb 10 13:03:29 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105809}

Feb 10 13:03:31 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105812}

Feb 10 13:03:34 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105814}

Feb 10 13:03:36 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105817}

Feb 10 13:03:39 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105819}

Feb 10 13:03:41 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105822}

Feb 10 13:03:44 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105824}

Feb 10 13:03:46 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105827}

Feb 10 13:03:47 raspberrypi dhcpcd[381]: eth0: Router Advertisement from fe80::3681:c4ff:fed7:e2ae

Feb 10 13:03:49 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105829}

Feb 10 13:03:51 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105832}

Feb 10 13:03:54 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105834}

Feb 10 13:03:56 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105837}

Feb 10 13:03:59 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105839}

Feb 10 13:04:01 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105842}

Feb 10 13:04:04 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105844}

Feb 10 13:04:06 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105847}

Feb 10 13:04:09 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105849}

Feb 10 13:04:11 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105852}

Feb 10 13:04:14 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105854}

Feb 10 13:04:16 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105857}

Feb 10 13:04:19 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105859}

Feb 10 13:04:21 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105862}

Feb 10 13:04:24 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105864}

Feb 10 13:04:26 raspberrypi weewx[2930]: meteostick: Loop packet: {'usUnits': 1, 'dateTime': 1455105867}

Feb 10 13:04:28 raspberrypi systemd[1]: Stopping LSB: weewx weather system...

Feb 10 13:04:29 raspberrypi weewx[2930]: engine: Received signal TERM.

Feb 10 13:04:29 raspberrypi weewx[2930]: engine: Main loop exiting. Shutting engine down.

Feb 10 13:04:29 raspberrypi weewx[2930]: engine: Terminating weewx version 3.4.0

Feb 10 13:04:34 raspberrypi weewx[3250]: Stopping weewx weather system: weewx..

Feb 10 13:04:34 raspberrypi systemd[1]: Stopped LSB: weewx weather system.

[L.J.M. Heijst]

Frank,

For some reason the packages are not recognized. Otherwise we would have seen "ISS message received" together with the message itself (see code).
if mesg is not None:
    if weewx.debug:
        logdbg('ISS message received: ' + mesg)

I think it's a bug that the driver writes an empty loop packet in such a case.

Luc

--

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/xQQmRQpDqU8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to

weewx-user+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.

[L.J.M. Heijst]

Thanks Gary for your explanation!
Luc

--

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/xQQmRQpDqU8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to

weewx-user+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.

[L.J.M. Heijst]

Frank,

I see the problem now. The current meteostick driver isn't reading the USB port data but reading a "CC1101 weather receiver" device which is read from localhost at port 5772.
So the logic of meteostickSerial.py must be part of the meteostick.py driver.

I'm a slow programmer, so it will take some time...

Luc

--

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/xQQmRQpDqU8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to

weewx-user+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.

[Frank Bandle]

Hi luc - still having launch - i'll check later. 

Thx frank

--
Sent from Ipad ...

[mwall]

On Wednesday, February 10, 2016 at 7:43:43 AM UTC-5, Luc Heijst wrote:

Frank,

I see the problem now. The current meteostick driver isn't reading the USB port data but reading a "CC1101 weather receiver" device which is read from localhost at port 5772.
So the logic of meteostickSerial.py must be part of the meteostick.py driver.

luc,

i renamed the 'matthewwall/weewx-meteostick' repository to weewx-ccwxrxvp2.

the new weewx-meteostick repository reads from serial port:

https://github.com/matthewwall/weewx-meteostick

i'm sure it has bugs, but you and frank should be able to sort it...

m

[Frank Bandle]

Luc

indeed you´re right. Its looking for localhost (127.0.0.1) port 5772 . This cannot work in our case here. 

-frank

-- 
Frank Bandle
Sent with Airmail

[Frank Bandle]

Matthew

thanks for help, I will install it and share the results here. 

-frank

[L.J.M. Heijst]

Frank,

Matthews driver decodes the machine readable messages (o1) from the meteostick.
So you have to set output to o1 first. 

Luc

.

[Luc Heijst]

To all,

Matthew, Frank and I are working on a serial USB meteostick driver for weewx.

We keep you informed about our progress.

Luc

[Luc Heijst]

To all,

Status update.

Version 0.2 of our meteostick driver for weewx produced usefull data in the weewx database which can be seen on the graphs too.

We are now testing the driver for a few hours to see what the system is doing.

Next step are:

• more usefull log messages
• better data handling for some message types
  
• debugging dynamic sensor mapping
• testing start up commands for setting the meteostick device

Luc

[Luc Heijst]

Status update

The meteostick driver (current version 0.12) is now for several weeks in test on three meteosticks of which two are listening to the same weather station.

The received data is compared with the received values from a vantage driver connected to an IP-data-logger listening to the same weather station.

The results are promising!

Recently we discovered big 'jumps' in the registered rain values of 25,6 mm each. The cause was a fault in the meteostick documentation where was stated that the rain counter would go from 0-255 where in our situations the counter wrapped around at a value of 127.

Our most recent changes are:

• Added support for the Australian frequency band
• Added a RF sensitivy parameter.
  Explanation: when the radio signal reception is bad you want to increase the sensitivity of the meteostick antenna (the drawback is an increase of noise and false readings).
  When the signal is very strong, you might want to lower the RF reception. We don't have much experience in this right now.

Luc

[Luc Heijst]

Status update.

The meteostick has three ways of sending data to the computer:

• Human readable data
• Machine readable data
• Raw data (this is the format Davis uses to send the sensor data to it's console / envoy / repeater
  

We first wrote our driver and parsed the machine readable format. The advantage: quick results; the disadvantage: no check on valid data (no CRC-check).

It appeared the wind samples, which should come each 2.5 - 3 s (depending on the channel of the anemometer), were received with an average of more than 9 seconds.:-(

With the other messages from the sensors we didn't discover any probloems.

So now we were 'forced' to use the Davis raw format. The througput is now 94% of the theoretical maximum. Not bad!

The drawback is that not all messages could be handled because a lack of documentation.

Some advantages of the meteostick in respect to Davis Vantage console or Davis Envoy with (any) data-logger:

• No need for a Davis console nor (any) data-logger, but it's nice to have anyhow!
• The temperatures of soil moisture (and leaf wetness I suppose) have a resolution of 0.1 degrees C instead of 1 degree Celsius.
• On the Anemometer Transport Kit you now can connect a Solar and/or UV sensor which will be read by the weewx meteostick driver (Warning: just theory: not tested yet!). 

The disadvantages of the meteostick:

• When the weewx meteostick driver isn't running no data will be stored to the weex database! No backup either, sorry!
• The reach of the smal antenna of the meteostick is less than that of the Davis Envoy which (on it's turn) is less than the reach of the Vantage Pro2 / Vantage Vue console antennas..
  So in cases you have a big distance between your sensors and your computer, the Davis console with data logger connected might be the better choice.

More to come!

Luc

[kobuki]

Great! I'm genuinely interested in making my MS work with WeeWx, too. I migt be able to help, though Python is not really my forte. I've worked a lot with my homebrew Davis receiver based on an Arduino clone called Moteino - the hardware is almost the same as the one the MS uses. There's a lot of discussion on these on wxforum.net (search for DeKay's or my posts, same nickname there).

On topic: I've read almost the whole thread, but I've stumbled on the previous statement about wind data. The wind data should be present in _every_ raw packet the stick spits out. It's on (0-based) offsets 1 and 2, wind speed and direction, respectively. I can see them in fraban's earlier post with the serial log, too. I haven't noticed any missed data with my stick, either, I'm wondering what you saw. Could you show a log of the data with the missing wind packets?

[L.J.M. Heijst]

Hi kobuki,

I came across your name very often when surfing on the net for additional info of the Davis data protocol. But that subject another time. Welcome to the weewx forum!

There is (obviously) no wind data in the packets coming from my leaf-soil station. The data coming from my ISS (without an anemometer connected) has empty wind data. Only the packets received from my Anemometer Transport Kit contain real wind data. In raw format (o0 format) I receive about 107 packets per 5 minutes from ISS and ATK each and 100 packets from the leaf-soil station. As my wind meter is on channel 2, I should get a theoretical maximum of 300 / 2.625 = 117 packets with wind data each 5 minutes. Then a received number of 107 'wind' packets in 300 seconds is not bad!

With 'missing' wind data I mean (we are talking about the o1 protocol here with machine readable data): I only got about 40 packets ('W' lines) with wind data each 5 minutes, so 'missing' 117 - 40 = 77 wind packets of the theoretical maximum. That is an average of 1 wind packet each 9.6 seconds where it should be about 2.6 seconds! The other data (temp, humidity, rain, solar etc.) with theoretical intervals of 10, 50 or 60 seconds, are received in about the same intervals as expected in both the o0 and o1 protocols.

Kobuki, I have a lot data to share with you and a lot questions to ask too! Can we have private mail contact? Please send a note to ljm.heijst at gmail dot com.

Cheers, 

Luc

Verstuurd vanaf mijn iPad

--

[kobuki]

Sorry, I posted late night and I somehow mixed up "machine readable data" (which is actually human readable to my eyes) and raw data in your earlier post. So please disregard my question about wind packets. From your write-up it appears there's something amiss with the stick's output, indeed. I'll drop you a direct mail.

[Michael Buchfink]

Hi Luc,

I just saw your project and it looks really good. I am also feeding weewx with raw data from a Vue iss.

The disadvantages of the meteostick:

• When the weewx meteostick driver isn't running no data will be stored to the weex database! No backup either, sorry!
• The reach of the smal antenna of the meteostick is less than that of the Davis Envoy which (on it's turn) is less than the reach of the Vantage Pro2 / Vantage Vue console antennas..
  So in cases you have a big distance between your sensors and your computer, the Davis console with data logger connected might be the better choice.

I don't want to loose data either. For this reason I'am storing all sensor data with timestamps in a database. Weewx is running on a different server and gets only a copy of the data. In this way I can refill the weewx database if something changes in the interpretation of the raw data. This format is still unoffical as far as I know.

I am using a meteostick only as a backup logger. With my homebrew logger,  a RFM69CW tranceiver and BMP180 pressure sensor directly connected to a Raspberry Pi, I have more control in receiving the iss data and I receive more valid packages from the iss. Also it is much cheaper than a meteostick.

My code is on github: https://github.com/buwx

Cheers,
Michael

BTW: Without the information from wxforum.net it would have been impossible to do this.

 

[Frank Bandle]

Hi Michael

Luc, Matthew and me, we are working on the meteostick-driver. Can you send me/ us a little bit more information what you did with "my homebrew logger,  a RFM69CW tranceiver and BMP180 pressure sensor directly connected to a Raspberry Pi” and how this looks like. I´m intrested in this personally to have a 2nd way receiving ISS Data from Vue or VP Pro2 stations.

Thanks

-frank

-- 
Frank Bandle
Sent with Airmail

[Michael Buchfink]

Hi Frank,

I put some fotos on my weather page: https://buwx.de/index.php/technik/43-logger

The logger is really not a beauty but you can put can cover it...

Maybe more interesting is the python code for receiving the data: https://github.com/buwx/logger/blob/master/davisreceiver.py

[Luc Heijst]

Hi Michael,

Your used hardware is relative cheap (7,5 Euro total for the two used modules), so it would be nice to combine it with a dedicated weewx driver.

I will look at your driver code to see how it's done.

I made progress today with the parsing of the raw data packets received from the meteostick.  

It helps that I can compare the output of the parsed meteostick data with the "official"' data received from a Davis USB datalogger

Currently I test the weewx driver with the following hardware:

• Vantage Vue
• Vantage Pro2
• Anemometer Transport Kit with anomometer (soon: a solar sensor connected to the ATK)
• Leaf-Soil station with Leaf Wetness, Soil Temp and Soil Moisture sensors.

Cheers,

Luc

[Michael Buchfink]

Hi Lux,

please let me know, if I can help you in any way. I have some knowledge about the Vue iss and collected 14 millions data records over the last 13 months :)

My data logger is running fine but maybe someone else with more experience in electronics can design a proper pcb for the community.

Cheers

Michael

[Luc Heijst]

Status update

• Help is offered by several users. Thanks! Together we will develop a good driver!
• My tests now include a solar sensor
• Improved determination of Signal Quality
  Current average value of Signal Quality (% good signals): meteostick machine readable data: 65 %; meteostick raw data: 95%. 

Luc

[L.J.M. Heijst]

Hi,

I started a topic about the meteostick driver for weewx in the weewx development forum

See: https://groups.google.com/forum/#!topic/weewx-development/3XwRG8wB9OQ  

Feel free to add or react.

Cheers,
Luc

Cheers, Luc

-- 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/xQQmRQpDqU8/unsubscribe.

To unsubscribe from this group and all its topics, send an email to

weewx-user+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.

Virusvrij. www.avast.com

[Luc Heijst]

Today I mounted my Davis solar sensor in the mast of my wind meter and connected the sensor on the "sun" marked entry of the Anemometer Transport Kit.

With the Meteostick the data of the solar sensor can be read which is not possible with the official Davis equipment where you can have only one iss per console / datalogger.

See also my topic "Meteostick driver for weewx" in the weewx development forum for some extra info. https://groups.google.com/forum/#!topic/weewx-development/3XwRG8wB9OQ

Luc

[Frank Bandle]

Luc,

thats great - So we can use Solar Sensor seperate with the Anemometer Transport Kit ..

- I will install latest testdriver of meteostick tomorrow. Actually both sticks one connected with the VUE, one with the VP Pro2 are working ok. Parallel I have the data from ENVOY (connected to VP Pro) and IP datalogger . 

-frank

-- 
Frank Bandle
Sent with Airmail

[kobuki]

I wasn't sure where to post this, here or the dev thread but here it goes. I wanted to try the new driver and it was the first time I plugged the MS into my Linux server where other weather stuff is connected among others, and it works, sort of. I connect to it via Minicom and I'm welcomed with the usual banner text, but then it won't accept any commands. In your experience, do I need to use any special settings or commands to make it work? It works without a hitch on Windows 7. So the stick is probably not at fault. I also have several other FTDI USB-serial converters plugged into the same server, never a single problem. I might need to report to the MS devs, but I thought I ask here first. Oh, and just to mage sure, I haven't tried to load the driver yet, since it doesn't seem to work anyway yet.

[Luc Heijst]

Hi Kobuki,

Check the setttings in the Meteostick section of weewx.conf. It should look like:

##############################################################################

[Meteostick]

    # This section is for the Meteostick USB receiver.

    # A serial port must be specified:

    port = /dev/mstk    # Note: I have two drivers which both want to claim /dev/ttyusb0 and /dev/ttyusb1

                        # So I assigned two udev devices: /dev/vpro (console vantage pro) and /dev/mstk (meteostick).

                        # See the weewx user guide.

    # Radio frequency to use between USB transceiver and console: US or EU

    # US uses 915 MHz, EU uses 868.3 MHz.  Default is EU.

    transceiver_frequency = EU

    format = raw  # raw, machine, human (human is not supported by thye driver)

    rf_sensitivity = 90

    # Used channels: 0=not present, 1-8)

    # The channel of the Vantage Vue ISS or Vantage Pro or Pro2 ISS

    iss_channel = 1

    # The values below only apply for Vantage Pro or Pro2

    anemometer_channel = 0

    leaf_soil_channel = 0

    temp_hum_1_channel = 0

    temp_hum_2_channel = 0

    # rain bucket type (0: 0.01 inch, 1: 0.2 mm)

    rain_bucket_type = 1

    # Print debug messages

    #  0=no logging; 1=minimum logging; 2=normal logging; 3=detailed logging

    debug_parse = 2

    debug_serial = 2

    debug_rain = 2

    debug_rf_sensitivity = 2

    # The driver to use:

    driver = user.meteostick

##############################################################################

 Also set debug = 1 and look in syslog.

Luc

[mwall]

On Monday, May 9, 2016 at 11:25:24 AM UTC-4, kobuki wrote:

I wasn't sure where to post this, here or the dev thread but here it goes. I wanted to try the new driver and it was the first time I plugged the MS into my Linux server where other weather stuff is connected among others, and it works, sort of. I connect to it via Minicom and I'm welcomed with the usual banner text, but then it won't accept any commands. In your experience, do I need to use any special settings or commands to make it work? It works without a hitch on Windows 7. So the stick is probably not at fault. I also have several other FTDI USB-serial converters plugged into the same server, never a single problem. I might need to report to the MS devs, but I thought I ask here first. Oh, and just to mage sure, I haven't tried to load the driver yet, since it doesn't seem to work anyway yet.

did you install weewx and the meteostick driver?

when you install the meteostick driver, it should prompt you for the port and a few things about your station.

you can add/modify the other parameters if you like (as luc noted), but everything should work as long as you go the port right.

m

[kobuki]

Luc, thanks for the answer, but as I've said I haven't tried the driver yet. There's no point until the stick refuses to acknowledge the basic commands via a serial console... It does accept them on Win7, but not on the server running Linux (Proxmox PVE, 2.6.32 OpenVZ kernel). So I though something might be amiss with my serial settings but apparently it's indeed a stick issue.

[Frank Bandle]

Hi Kobiku

i´m able to connect the Meteostick with “minicom” on /dev/ttyUSB0.  baudrate 19200 

-frank

-- 

--

[Frank Bandle]

Kobiku ..  sorry wrong baudrate …  not 19200!   try   baudrate = 115200

-frank

[kobuki]

Yeah, using 115200, which is the default.

(Please pay attention to the o and i in my nickname ;)

[Frank Bandle]

Test if the stick is recognized by linux.

dmesg | grep tty

You should see something like: 

…..   usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

and with  lsusb

something like

Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

-frank

[Frank Bandle]

Sorry “Kobuki” for mixing the characters - quick typos ...

-frank

[kobuki]

Thanks, as I've mentioned the stick dumps the usual welcome text/banner - so apparently the stick is recognised as a tty adapter, and yes, it shows up in the lsusb list and as /dev/ttyUSB3 -, then it refuses to do anything else. It doesn't accept commands, if I try to enter one there is no answer at all. I type in all the commands required to start capturing the VP2 packets, but it just sits there doing nothing. It's really a weird issue, as I have 3 more FTDI converters plugged into the same server and all work flawlessly.

[Luc Heijst]

Meteostick driver testers wanted!

Hello all,

We tested our new meteostick weewx driver with:

• Vantage Vue with IP datalogger
  
• Vantage Pro2 with USB datalogger
• Anemometer Transport Kit with wind meter
• Anemometer Transport Kit with solar power sensor
• Leaf & Soil station with Soil Moisture Sensor, Soil Temperature Sensor, Leaf Wetness Sensor

If you have other equipment and like to test the meteostick driver for us, just drop a message at:

ljm.heijst at gmail dot com

Thanks in advance!

Luc Heijst

Paramaribo, Suriname

[kobuki]

OK, sorry for the noise, I have succesfully set up the driver for my MS. It behaves strangely using standard tools like minicom or socat which I routinely use to test serial equipment. That deterred me from using the driver for a while. Ah well.

It's working fine with the driver now, so I'll have some experience to refer to in 1-2 days.

[Luc Heijst]

Status update

We are now testing the meteostick driver with the three of us:

Frank is testing the 'standard' driver on github with Vantage Vue and Vantage Pro2 stations.

Kobuki is testing the wind and gust values with a modified version of the driver to achieve a bigger accuracy.

He has also achieved a higher rf reception on his site.

Luc is testing the soil moisture and leaf wetness values with another modified version of the driver. 

If anybody else wants to participate, just drop a line here.

More to come.

Cheers

Luc

[Jesus C.]

Hi,

I'm running weewx with a meteostick and I have a problem during the launch of the program, having it to run twice. Once active, weewx continues running.
Issue does not occurs always but i don't have a clue what's going on.
Any advice is welcome. Thanks in advance.

Hardware: QNAP TS-253A. OS version 4.2.1 (2016/04/19)

Log:

May 20 16:04:27 hostname weewx[17995]: engine: Initializing weewx version 3.5.0
May 20 16:04:27 hostname weewx[17995]: engine: Using Python 2.7.11 (default, Mar 27 2016, 22:06:47)
May 20 16:04:27 hostname [GCC 5.3.0]
May 20 16:04:27 hostname weewx[17995]: engine: Platform Linux-3.19.8-x86_64-with-glibc2.2.5
May 20 16:04:27 hostname weewx[17995]: engine: Using configuration file /share/homes/weewx/weewx.conf
May 20 16:04:27 hostname weewx[17995]: engine: Initializing engine
May 20 16:04:27 hostname weewx[17995]: engine: Loading station type Meteostick (user.meteostick)
May 20 16:04:27 hostname weewx[17995]: meteostick: driver version is 0.36
May 20 16:04:27 hostname weewx[17995]: meteostick: using rain_bucket_type 1
May 20 16:04:27 hostname weewx[17995]: meteostick: sensor map is: {'solar_radiation': 'radiation', 'in_temp': 'inTemp', 'bat_th_1': 'outTempBatteryStatus', 'rain_rate': 'rainRate', 'rain_count': 'rain', 'leaf_temp_1': 'leafTemp1', 'bat_th_2': 'inTempBatteryStatus', 'pressure': 'pressure', 'soil_moisture_1': 'soilMoist1', 'bat_iss': 'txBatteryStatus', 'bat_anemometer': 'windBatteryStatus', 'temp_1': 'extraTemp1', 'soil_temp_2': 'soilTemp2', 'wind_dir': 'windDir', 'temp_2': 'extraTemp2', 'wind_speed': 'windSpeed', 'humid_2': 'extraHumid2', 'humid_1': 'extraHumid1', 'soil_moisture_3': 'soilMoist3', 'temperature': 'outTemp', 'soil_moisture_4': 'soilMoist4', 'uv': 'UV', 'humidity': 'outHumidity', 'leaf_wetness_2': 'leafWet2', 'leaf_wetness_1': 'leafWet1', 'bat_leaf_soil': 'rainBatteryStatus', 'pct_good': 'rxCheckPercent', 'leaf_temp_2': 'leafTemp2', 'soil_temp_1': 'soilTemp1', 'solar_power': 'extraTemp3', 'soil_temp_3': 'soilTemp3', 'soil_temp_4': 'soilTemp4', 'soil_moisture_2': 'soilMoist2'}
May 20 16:04:27 hostname weewx[17995]: meteostick: using serial port /dev/ttyUSB0
May 20 16:04:27 hostname weewx[17995]: meteostick: using baudrate 115200
May 20 16:04:27 hostname weewx[17995]: meteostick: using frequency EU
May 20 16:04:27 hostname weewx[17995]: meteostick: using rf sensitivity 90 (-90 dB)
May 20 16:04:27 hostname weewx[17995]: meteostick: using output_format raw
May 20 16:04:27 hostname weewx[17995]: meteostick: using iss_channel 1
May 20 16:04:27 hostname weewx[17995]: meteostick: using anemometer_channel 0
May 20 16:04:27 hostname weewx[17995]: meteostick: using leaf_soil_channel 0
May 20 16:04:27 hostname weewx[17995]: meteostick: using temp_hum_1_channel 0
May 20 16:04:27 hostname weewx[17995]: meteostick: using temp_hum_2_channel 0
May 20 16:04:27 hostname weewx[17995]: meteostick: using transmitters 01
May 20 16:04:27 hostname weewx[17995]: meteostick: configure meteostick to logger mode
May 20 16:04:29 hostname weewx[17995]: engine: Unable to load driver: [priority,] message string
May 20 16:04:29 hostname weewx[17995]:     ****  Exiting...
.
- relaunch weewx -
.
May 20 16:05:05 hostname weewx[18038]: engine: Initializing weewx version 3.5.0
May 20 16:05:05 hostname weewx[18038]: engine: Using Python 2.7.11 (default, Mar 27 2016, 22:06:47)
May 20 16:05:05 hostname [GCC 5.3.0]
May 20 16:05:05 hostname weewx[18038]: engine: Platform Linux-3.19.8-x86_64-with-glibc2.2.5
May 20 16:05:05 hostname weewx[18038]: engine: Using configuration file /share/homes/weewx/weewx.conf
May 20 16:05:05 hostname weewx[18038]: engine: Initializing engine
May 20 16:05:05 hostname weewx[18038]: engine: Loading station type Meteostick (user.meteostick)
May 20 16:05:05 hostname weewx[18038]: meteostick: driver version is 0.36
May 20 16:05:05 hostname weewx[18038]: meteostick: using rain_bucket_type 1
May 20 16:05:05 hostname weewx[18038]: meteostick: sensor map is: {'solar_radiation': 'radiation', 'in_temp': 'inTemp', 'bat_th_1': 'outTempBatteryStatus', 'rain_rate': 'rainRate', 'rain_count': 'rain', 'leaf_temp_1': 'leafTemp1', 'bat_th_2': 'inTempBatteryStatus', 'pressure': 'pressure', 'soil_moisture_1': 'soilMoist1', 'bat_iss': 'txBatteryStatus', 'bat_anemometer': 'windBatteryStatus', 'temp_1': 'extraTemp1', 'soil_temp_2': 'soilTemp2', 'wind_dir': 'windDir', 'temp_2': 'extraTemp2', 'wind_speed': 'windSpeed', 'humid_2': 'extraHumid2', 'humid_1': 'extraHumid1', 'soil_moisture_3': 'soilMoist3', 'temperature': 'outTemp', 'soil_moisture_4': 'soilMoist4', 'uv': 'UV', 'humidity': 'outHumidity', 'leaf_wetness_2': 'leafWet2', 'leaf_wetness_1': 'leafWet1', 'bat_leaf_soil': 'rainBatteryStatus', 'pct_good': 'rxCheckPercent', 'leaf_temp_2': 'leafTemp2', 'soil_temp_1': 'soilTemp1', 'solar_power': 'extraTemp3', 'soil_temp_3': 'soilTemp3', 'soil_temp_4': 'soilTemp4', 'soil_moisture_2': 'soilMoist2'}
May 20 16:05:05 hostname weewx[18038]: meteostick: using serial port /dev/ttyUSB0
May 20 16:05:05 hostname weewx[18038]: meteostick: using baudrate 115200
May 20 16:05:05 hostname weewx[18038]: meteostick: using frequency EU
May 20 16:05:05 hostname weewx[18038]: meteostick: using rf sensitivity 90 (-90 dB)
May 20 16:05:05 hostname weewx[18038]: meteostick: using output_format raw
May 20 16:05:05 hostname weewx[18038]: meteostick: using iss_channel 1
May 20 16:05:05 hostname weewx[18038]: meteostick: using anemometer_channel 0
May 20 16:05:05 hostname weewx[18038]: meteostick: using leaf_soil_channel 0
May 20 16:05:05 hostname weewx[18038]: meteostick: using temp_hum_1_channel 0
May 20 16:05:05 hostname weewx[18038]: meteostick: using temp_hum_2_channel 0
May 20 16:05:05 hostname weewx[18038]: meteostick: using transmitters 01
May 20 16:05:05 hostname weewx[18038]: meteostick: configure meteostick to logger mode
May 20 16:05:07 hostname weewx[18038]: meteostick: reset: # MeteoStick Version 2.2 (Apr  5 2015 10:37:04), Free RAM 725, SN: EEE2685807136100
May 20 16:05:08 hostname weewx[18038]: engine: Loading service weewx.engine.StdTimeSynch
May 20 16:05:08 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdTimeSynch
May 20 16:05:08 hostname weewx[18038]: engine: Loading service weewx.engine.StdConvert
May 20 16:05:08 hostname weewx[18038]: engine: StdConvert target unit is 0x11
May 20 16:05:08 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdConvert
May 20 16:05:08 hostname weewx[18038]: engine: Loading service weewx.engine.StdCalibrate
May 20 16:05:08 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdCalibrate
May 20 16:05:08 hostname weewx[18038]: engine: Loading service weewx.engine.StdQC
May 20 16:05:08 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdQC
May 20 16:05:08 hostname weewx[18038]: engine: Loading service weewx.wxservices.StdWXCalculate
May 20 16:05:08 hostname weewx[18038]: wxcalculate: The following values will be calculated: barometer=prefer_hardware,windchill=prefer_hardware,dewpoint=prefer_hardware,appTemp=prefer_hardware,rainRate=prefer_hardware,windrun=prefer_hardware,heatindex=prefer_hardware,maxSolarRad=prefer_hardware,humidex=prefer_hardware,pressure=prefer_hardware,inDewpoint=prefer_hardware,ET=prefer_hardware,altimeter=prefer_hardware,cloudbase=prefer_hardware
May 20 16:05:08 hostname weewx[18038]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA,maxSolarRad=RS
May 20 16:05:08 hostname weewx[18038]: engine: Finished loading service weewx.wxservices.StdWXCalculate
May 20 16:05:08 hostname weewx[18038]: engine: Loading service user.crt.CumulusRealTime
May 20 16:05:08 hostname weewx[18038]: crt: service version is 0.18
May 20 16:05:08 hostname weewx[18038]: crt: output goes to /share/CACHEDEV1_DATA/homes/weewx/public_html/realtime.txt
May 20 16:05:08 hostname weewx[18038]: crt: 'None' values will be displayed as NULL
May 20 16:05:08 hostname weewx[18038]: crt: zambretti forecast: False
May 20 16:05:08 hostname weewx[18038]: crt: binding is loop
May 20 16:05:08 hostname weewx[18038]: engine: Finished loading service user.crt.CumulusRealTime
May 20 16:05:08 hostname weewx[18038]: engine: Loading service weewx.engine.StdArchive
May 20 16:05:08 hostname weewx[18038]: engine: Archive will use data binding wx_binding
May 20 16:05:08 hostname weewx[18038]: engine: Record generation will be attempted in 'software'
May 20 16:05:08 hostname weewx[18038]: engine: Using archive interval of 300 seconds
May 20 16:05:08 hostname weewx[18038]: engine: Use LOOP data in hi/low calculations: 1
May 20 16:05:09 hostname weewx[18038]: engine: Using binding 'wx_binding' to database 'weewx'
May 20 16:05:09 hostname weewx[18038]: manager: Starting backfill of daily summaries
May 20 16:05:09 hostname weewx[18038]: manager: Daily summaries up to date
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdArchive
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.restx.StdStationRegistry
May 20 16:05:09 hostname weewx[18038]: restx: StationRegistry: Data will not be posted. Missing option 'station_url'
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.restx.StdStationRegistry
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.restx.StdWunderground
May 20 16:05:09 hostname weewx[18038]: restx: Wunderground: Posting not enabled.
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.restx.StdWunderground
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.restx.StdPWSweather
May 20 16:05:09 hostname weewx[18038]: restx: PWSweather: Posting not enabled.
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.restx.StdPWSweather
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.restx.StdCWOP
May 20 16:05:09 hostname weewx[18038]: restx: CWOP: Posting not enabled.
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.restx.StdCWOP
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.restx.StdWOW
May 20 16:05:09 hostname weewx[18038]: restx: WOW: Posting not enabled.
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.restx.StdWOW
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.restx.StdAWEKAS
May 20 16:05:09 hostname weewx[18038]: restx: AWEKAS: Posting not enabled.
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.restx.StdAWEKAS
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.engine.StdPrint
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdPrint
May 20 16:05:09 hostname weewx[18038]: engine: Loading service weewx.engine.StdReport
May 20 16:05:09 hostname weewx[18038]: engine: Finished loading service weewx.engine.StdReport
May 20 16:05:09 hostname weewx[18038]: engine: Starting up weewx version 3.5.0
May 20 16:05:09 hostname weewx[18038]: engine: Station does not support reading the time
May 20 16:05:09 hostname weewx[18038]: engine: Starting main packet loop.
May 20 16:05:09 hostname weewx[18038]: meteostick: # chip authentication ok: 14
May 20 16:05:09 hostname weewx[18038]: meteostick: # frequency band 868MHz (EU)
.
.
.

[mwall]

On Tuesday, May 24, 2016 at 6:38:20 PM UTC-4, Jesus C. wrote:

May 20 16:04:27 hostname weewx[17995]: meteostick: configure meteostick to logger mode
May 20 16:04:29 hostname weewx[17995]: engine: Unable to load driver: [priority,] message string
May 20 16:04:29 hostname weewx[17995]:     ****  Exiting...

you're getting an exception during the initial configuration of the meteostick.  unfortunately, the exception type and details are being swallowed.

run weewx directly so that you can see the actual stack trace from the exception, for example:

weewxd /etc/weewx/weewx.conf

then control-c to kill the process.  you'll have to do this multiple times until the exception happens again.

m

[Luc Heijst]

Matthew,
I have the same behaviar here as Jesus describes. It doesn't matter if I have replaced meteostick.py with a newer version or not.
Each second time I got the error (I use the raw format).
When I start weewx via ./weewxwd /home/weewx/weewx_mstk.conf the program starts running right away. I tried about 15 successive starts.
Should I still keep trying to catch an error you think? I don't mind starting it 100 times, when it's needed.
Luc
Currently I'm testing the machine readable output format and I've got the idea the errors are less ore gone. Will investigate this a bit more.

[nls]

Luc,

Do you get the error if you unplug/replug your MS before each start? I suspect something with improper port closing. There is a strange issue, too, which might be connected to this. When I use a serial terminal emulator to access the stick, such as Minicom, the stick doesn't react to any input. That's only on Linux though - the problem never occurs on Windows 7 with KiTTY (PuTTY), for example. There might be going on in its firmware, too, perhaps a timing issue of some kind.

[Luc Heijst]

OK I found a solution for the problem. Apparantly an unknow exception occurred during the reset call.

I have changed the following code:

        """Configure the device to send data continuously."""

        loginf("configure meteostick to logger mode")

        # Put device into state that we can talk to it reliably

        self.reset()

into this:

        """Configure the device to send data continuously."""

        loginf("configure meteostick to logger mode")

        try:

            # Put device into state that we can talk to it reliably

            self.reset()

        except KeyboardInterrupt, e:

            logerr("KeyboardInterrupt: %s" % e)

            raise

        except:

            logerr("Unexpected error during reset, continue")

            pass

Now weewx continues after the unexpected error.

Luc

PS1. I tried a few things to avoid the error, like writing a character before flushing the input buffer and/or increasing the sleep times, but the error remained. Also enabling debug_serial reduced the number of errors, but now and then the error still occurred.

PS2. How can I print the unknown error in Python? Don't know the syntax how to do this.

[nls]

If you don't "pass" but "raise" or dont catch with "except" at all, you should see the trace in the debug log. Otherwise sys.exc_info() contains detailed info in an array (Python pros will correct me if i wrote something wrong) that you can process or print.

--

[Luc Heijst]

Kobuki,

Unfortunately both suggested options didn't revail the error, see below.

Luc

Option a: raise instead of pass

May 27 09:51:23 pi2 mstk[9931]: meteostick: configure meteostick to logger mode

May 27 09:51:25 pi2 mstk[9931]: meteostick: Unexpected error during reset, continue

May 27 09:51:25 pi2 mstk[9931]: engine: Unable to load driver: [priority,] message string

May 27 09:51:25 pi2 mstk[9931]:     ****  Waiting 60 seconds then retrying...

Option b: don't use an except:

May 27 09:52:54 pi2 mstk[9995]: meteostick: configure meteostick to logger mode

May 27 09:52:56 pi2 mstk[9995]: engine: Unable to load driver: [priority,] message string

May 27 09:52:56 pi2 mstk[9995]:     ****  Waiting 60 seconds then retrying...

[nls]

Post your code. Also see: https://wiki.python.org/moin/HandlingExceptions (General Error Catching)

However, it is not a Python programming forum. Let's continue privately.

[Luc Heijst]

Hi Kobuki,

I changed the code into (and had to import sys as well):

        except:

            e = sys.exc_info()[0]

            logerr("Unexpected error %s during reset, continue" % e)

            pass

This reveiled the following error:

May 27 10:09:02 pi2 mstk[10543]: meteostick: Unexpected error <type 'exceptions.TypeError'> during reset, continue

Then changed the code as follows to detect the type of TypeError:

def configure(self):

    """Configure the device to send data continuously."""
    loginf("configure meteostick to logger mode")
    try:
        # Put device into state that we can talk to it reliably
        self.reset()

    except TypeError, e:
        logerr("TypeError: %s, continue" % e)
        pass

The result was...

May 27 10:18:06 pi2 mstk[11107]: meteostick: TypeError: [priority,] message string, continue

Hey, the same message engine came up with each time!

May 27 07:27:05 pi2 mstk[1601]: engine: Unable to load driver: [priority,] message string

So the 'real' error is still unknown, but we now continue via the pass command.

Luc

[mwall]

On Friday, May 27, 2016 at 9:30:02 AM UTC-4, Luc Heijst wrote:

Then changed the code as follows to detect the type of TypeError:

def configure(self):
    """Configure the device to send data continuously."""
    loginf("configure meteostick to logger mode")
    try:
        # Put device into state that we can talk to it reliably
        self.reset()
    except TypeError, e:
        logerr("TypeError: %s, continue" % e)
        pass

The result was...

May 27 10:18:06 pi2 mstk[11107]: meteostick: TypeError: [priority,] message string, continue

luc,

that is just hiding the problem.  we need the stack trace that is causing the TypeError.

run weewx directly (not as a daemon) so that you can see the trace.

m

[Luc Heijst]

Matthew,

Just found the problem. I remembered logging will crash when the message contain a NULL character, so I changed the reset code to the following:

    def reset(self):

        """Reset the device, leaving it in a state that we can talk to it."""

        # flush any previous data in the input buffer

        self.serial_port.flushInput()

        # Send a reset command

        self.serial_port.write('r\n')

        # Wait until we see the ? character

        ready = False

        response = ''

        while not ready:

            time.sleep(0.1)

            while self.serial_port.inWaiting() > 0:

                c = self.serial_port.read(1)

                if c == '?':

                    ready = True

                # don't place null characters in the responce

                elif ord(c) != 0:

                    response += c

                else:

                    loginf("skip null character")

                    

        loginf("reset: %s" % response.split('\n')[0])

        dbg_serial(2, "full response to reset: %s" % response)

This happened when checked for null characters:

        

May 27 13:41:11 pi2 mstk[12765]: meteostick: configure meteostick to logger mode

May 27 13:41:13 pi2 mstk[12765]: meteostick: skip null character

May 27 13:41:13 pi2 mstk[12765]: meteostick: skip null character

... 1684 more lines with "skip null character" messages

May 27 13:41:15 pi2 mstk[12765]: meteostick: skip null character

May 27 13:41:15 pi2 mstk[12765]: meteostick: skip null character

But NO crash anymore!

Of course we will remove the following two lines after our test.

:

                else:

                    loginf("skip null character")

                    

Luc

[nls]

Nice catch! ;)

--

[Jesus C.]

Hi,

Updated driver to 0.37 and weewx don't run:

May 31 13:11:15 myNAS weewx[28698]: engine: Initializing weewx version 3.5.0
May 31 13:11:15 myNAS weewx[28698]: engine: Using Python 2.7.11 (default, May 12 2016, 12:24:40)
May 31 13:11:15 myNAS [GCC 5.3.0]
May 31 13:11:15 myNAS weewx[28698]: engine: Platform Linux-3.19.8-x86_64-with-glibc2.2.5
May 31 13:11:15 myNAS weewx[28698]: engine: Using configuration file /share/homes/admin/weewx/weewx.conf
May 31 13:11:15 myNAS weewx[28698]: engine: Initializing engine
May 31 13:11:15 myNAS weewx[28698]: engine: Loading station type Meteostick (user.meteostick)
May 31 13:11:16 myNAS weewx[28698]: meteostick: driver version is 0.37
May 31 13:11:16 myNAS weewx[28698]: meteostick: using rain_bucket_type 1
May 31 13:11:16 myNAS weewx[28698]: meteostick: sensor map is: {'solar_radiation': 'radiation', 'in_temp': 'inTemp', 'bat_th_1': 'outTempBatteryStatus', 'rain_rate': 'rainRate', 'rain_count': 'rain', 'leaf_temp_1': 'leafTemp1', 'bat_th_2': 'inTempBatteryStatus', 'pressure': 'pressure', 'supercap_volt': 'supplyVoltage', 'soil_moisture_1': 'soilMoist1', 'bat_iss': 'txBatteryStatus', 'bat_anemometer': 'windBatteryStatus', 'temp_1': 'extraTemp1', 'soil_moisture_2': 'soilMoist2', 'wind_dir': 'windDir', 'temp_2': 'extraTemp2', 'wind_speed': 'windSpeed', 'humid_2': 'extraHumid2', 'humid_1': 'extraHumid1', 'soil_moisture_3': 'soilMoist3', 'temperature': 'outTemp', 'soil_moisture_4': 'soilMoist4', 'uv': 'UV', 'humidity': 'outHumidity', 'leaf_wetness_2': 'leafWet2', 'leaf_wetness_1': 'leafWet1', 'solar_power': 'referenceVoltage', 'pct_good': 'rxCheckPercent', 'leaf_temp_2': 'leafTemp2', 'soil_temp_1': 'soilTemp1', 'soil_temp_2': 'soilTemp2', 'soil_temp_3': 'soilTemp3', 'soil_temp_4': 'soilTemp4', 'bat_leaf_soil': 'rainBatteryStatus'}
May 31 13:11:16 myNAS weewx[28698]: meteostick: using serial port /dev/ttyUSB0
May 31 13:11:16 myNAS weewx[28698]: meteostick: using baudrate 115200
May 31 13:11:16 myNAS weewx[28698]: meteostick: using frequency EU
May 31 13:11:16 myNAS weewx[28698]: meteostick: using rf sensitivity 90 (-90 dB)
May 31 13:11:16 myNAS weewx[28698]: meteostick: using output_format raw
May 31 13:11:16 myNAS weewx[28698]: meteostick: using iss_channel 1
May 31 13:11:16 myNAS weewx[28698]: meteostick: using anemometer_channel 0
May 31 13:11:16 myNAS weewx[28698]: meteostick: using leaf_soil_channel 0
May 31 13:11:16 myNAS weewx[28698]: meteostick: using temp_hum_1_channel 0
May 31 13:11:16 myNAS weewx[28698]: meteostick: using temp_hum_2_channel 0
May 31 13:11:16 myNAS weewx[28698]: meteostick: using transmitters 01
May 31 13:11:16 myNAS weewx[28698]: meteostick: configure meteostick to logger mode

weewx freezes at this point and i have to CTRL+C to end.

I made the mistake of not keeping driver zip file of earlier versions to rollback changes. Is Is it possible to download it from somewhere else?

[nls]

- go to https://github.com/matthewwall/weewx-meteostick/commits/master

- click on the [ <> ] button for the version you think is appropriate

- Clone or download button -> Download ZIP

--