subject:"\[weewx\-user\] Re\: WS\-3000"

Risto,

This script sure helps:
after stripping out the comments, it ran without errors at first try!
Seems quite a good starting point for my planned further effort in 
direction of Domoticz and for graphing with RRDTool.
Like you did, tested while weewx still around & active: therefore next to 
test that it runs without weewx
If not, to be checked whether it runs with weewx installed by the 'simple' 
method (spreading the files from /root).

Last week ;-) quickly learned a lot about weewx by try& error:
Olivier_G thanks for the continuous support for this NOOB!

My conclusion for first use of weewx:
the first installation of weewx makes the difference, but :-(  that is 
unknown for a first time user of weewx.
Perhaps a suggestion that in a description for an addition/modification for 
aspects such as the driver/interface for HP300x or WS3000 in one of the 
first comment lines it is clearly stated that an installation through 
setup.py is assumed, putting files in /home/weewx (*or* by the 'simple' 
method).
After I changed to use of setup.py, the scripts from both Matthewwall and 
Olivier_G started running.

Op vrijdag 14 februari 2020 07:02:38 UTC+1 schreef Risto H. Kurppa:
>
> Not sure if it helps anyone, but with Oliver's help about a year or so 
> ago, I stripped the ws3000 weewx driver code to work as standalone, without 
> needing weewx. That way I was able to just read the values to MQTT for 
> further use, without weewx dependency. The code is not cleaned in any way 
> and it's actually possible that it still uses some weewx things here or 
> there- I still have also weewx installed and haven't tested it without 
> weewx.
>
> https://pastebin.com/37WkUz7N
>
> Feel free to use & edit & expand. Or Olivier, maybe you want to add an 
> standalone script to your github?
>
> Risto
>
>
>
> On Fri, Feb 14, 2020 at 12:26 AM Ton vanN > 
> wrote:
>
>> Perhaps not 100% done according to Olivier's latest message, but got the 
>> same result in weewx.conf
>> Now (in the next days) an update for display & database .
>>
>> Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>>>
>>> Here, I put the code on github, with some basic installation 
>>> instructions.
>>> https://github.com/hublol/WS-3000_WeeWx
>>>
>>> I haven't tested those instructions recently, they might be incomplete 
>>> right now, but it's a start and I'll work to improve them if needed.
>>>
>> -- 
>> 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/qDe-El03C2k/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> | risto h. kurppa
> | risto at kurppa dot fi
> | http://risto.kurppa.fi
>

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

Re: [weewx-user] Re: WS-3000



Op vrijdag 14 februari 2020 07:02:38 UTC+1 schreef Risto H. Kurppa:
>
> Not sure if it helps anyone, but with Oliver's help about a year or so 
> ago, I stripped the ws3000 weewx driver code to work as standalone, without 
> needing weewx. That way I was able to just read the values to MQTT for 
> further use, without weewx dependency. The code is not cleaned in any way 
> and it's actually possible that it still uses some weewx things here or 
> there- I still have also weewx installed and haven't tested it without 
> weewx.
>
> https://pastebin.com/37WkUz7N
>
> Feel free to use & edit & expand. Or Olivier, maybe you want to add an 
> standalone script to your github?
>
> Risto
>
>
>
> On Fri, Feb 14, 2020 at 12:26 AM Ton vanN > 
> wrote:
>
>> Perhaps not 100% done according to Olivier's latest message, but got the 
>> same result in weewx.conf
>> Now (in the next days) an update for display & database .
>>
>> Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>>>
>>> Here, I put the code on github, with some basic installation 
>>> instructions.
>>> https://github.com/hublol/WS-3000_WeeWx
>>>
>>> I haven't tested those instructions recently, they might be incomplete 
>>> right now, but it's a start and I'll work to improve them if needed.
>>>
>> -- 
>> 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/qDe-El03C2k/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> | risto h. kurppa
> | risto at kurppa dot fi
> | http://risto.kurppa.fi
>

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

Re: [weewx-user] Re: WS-3000

2020-02-13 Thread Risto H. Kurppa

Not sure if it helps anyone, but with Oliver's help about a year or so ago,
I stripped the ws3000 weewx driver code to work as standalone, without
needing weewx. That way I was able to just read the values to MQTT for
further use, without weewx dependency. The code is not cleaned in any way
and it's actually possible that it still uses some weewx things here or
there- I still have also weewx installed and haven't tested it without
weewx.

https://pastebin.com/37WkUz7N

Feel free to use & edit & expand. Or Olivier, maybe you want to add an
standalone script to your github?

Risto



On Fri, Feb 14, 2020 at 12:26 AM Ton vanN  wrote:

> Perhaps not 100% done according to Olivier's latest message, but got the
> same result in weewx.conf
> Now (in the next days) an update for display & database .
>
> Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>>
>> Here, I put the code on github, with some basic installation instructions.
>> https://github.com/hublol/WS-3000_WeeWx
>>
>> I haven't tested those instructions recently, they might be incomplete
>> right now, but it's a start and I'll work to improve them if needed.
>>
> --
> 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/qDe-El03C2k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com
> 
> .
>


-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

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

Re: [weewx-user] Re: WS-3000

Perhaps not 100% done according to Olivier's latest message, but got the 
same result in weewx.conf
Now (in the next days) an update for display & database .

Op donderdag 13 februari 2020 22:26:08 UTC+1 schreef Olivier Guyotot:
>
> Here, I put the code on github, with some basic installation instructions.
> https://github.com/hublol/WS-3000_WeeWx
>
> I haven't tested those instructions recently, they might be incomplete 
> right now, but it's a start and I'll work to improve them if needed.
>

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

Re: [weewx-user] Re: WS-3000

2020-02-13 Thread Olivier Guyotot

Here, I put the code on github, with some basic installation instructions.
https://github.com/hublol/WS-3000_WeeWx

I haven't tested those instructions recently, they might be incomplete 
right now, but it's a start and I'll work to improve them if needed.

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

Re: [weewx-user] Re: WS-3000

Olivier has made the read-out of WS3000 an extension to 'another' 
weatherstation.
For just reading & processing the output of WS3000 a number of adaptation 
have to be made.

In my setup I have WeeWX operating with the Simulator which generates 
fake-weather.
On the other hand I have plenty of data from real weather-sensors.
That data is good enough to 'inject' into the Simulator, resulting in one 
merged data-set with all actual data.
Have looked around, but not seen in this Google-group, nor in WeeWX-wiki 
such a possibility.
Did I miss the info, or not yet developed?


Op donderdag 13 februari 2020 11:23:59 UTC+1 schreef Ton vanN:
>
> Forgot to hint that RistoK's HowTo-Instructions for fitting the 
> ws3000-driver on a Raspberry would have been very useful for my efforts 
> (probably significantly reducing my questions and experiments), but 
> unfortunately those instructions no longer accessible, because the hosting 
> server has gone ...
> Now smells a bit like 'reinventing the wheel', unless somebody can 
> reproduce those instructions.
>
> Op donderdag 13 februari 2020 11:05:46 UTC+1 schreef Ton vanN:
>>
>> @Olivier,
>> Changed the WeeWX-setup to the 'normal' configuration resulting after 
>> installation with the tar-file and setup.py.
>> At least the script ws3000.py now starts running, but not without errors: 
>> error report has been sent by Email.
>> Looking at the errorreports, *apparently* the version Python2.7 as part 
>> of Raspian_Buster is conflicting with functions in script ws3000.py
>>
>> Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>>>
>>> If your installation was done using the Debian package manager, then you 
>>> need to deploy the ws3000.py file in /usr/share/weewx/user.
>>>
>>> And the command to run would presumably be:
>>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>>>
>>> Unfortunately I have no experience with this type of installation, and 
>>> no way to test it. I won't be of much help here.
>>>
>>> NOTE: I just noticed that in your configuration, you specified driver = 
> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
> Where did you see this info?
> Or otherwise formulated: where shal I put such line?

 I saw that in the StdConvert issue thread, where you posted part of 
>>> your weex.conf, didn't you?
>>>
>>> What you need is a section such as:
>>> [WS3000]
>>> # This section is for the Ambient Weather WS3000
>>>
>>> # The driver to use
>>> driver = user.ws3000
>>>
>>> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
>>> same...)
>>> model = WS3000
>>>
>>> # [Optional] USB read/write timeout (helps on Raspberry Pi)
>>> # Default is 1000
>>> timeout =  1000
>>>
>>> The rest should be optional.
>>>
>>>
>>>
>>>

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

Re: [weewx-user] Re: WS-3000

Forgot to hint that RistoK's HowTo-Instructions for fitting the 
ws3000-driver on a Raspberry would have been very useful for my efforts 
(probably significantly reducing my questions and experiments), but 
unfortunately those instructions no longer accessible, because the hosting 
server has gone ...
Now smells a bit like 'reinventing the wheel', unless somebody can 
reproduce those instructions.

Op donderdag 13 februari 2020 11:05:46 UTC+1 schreef Ton vanN:
>
> @Olivier,
> Changed the WeeWX-setup to the 'normal' configuration resulting after 
> installation with the tar-file and setup.py.
> At least the script ws3000.py now starts running, but not without errors: 
> error report has been sent by Email.
> Looking at the errorreports, *apparently* the version Python2.7 as part 
> of Raspian_Buster is conflicting with functions in script ws3000.py
>
> Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>>
>> If your installation was done using the Debian package manager, then you 
>> need to deploy the ws3000.py file in /usr/share/weewx/user.
>>
>> And the command to run would presumably be:
>> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>>
>> Unfortunately I have no experience with this type of installation, and no 
>> way to test it. I won't be of much help here.
>>
>> NOTE: I just noticed that in your configuration, you specified driver = 
 user.hp3000. Unless you made a change, it should be driver = user.ws3000.
 Where did you see this info?
 Or otherwise formulated: where shal I put such line?
>>>
>>> I saw that in the StdConvert issue thread, where you posted part of your 
>> weex.conf, didn't you?
>>
>> What you need is a section such as:
>> [WS3000]
>> # This section is for the Ambient Weather WS3000
>>
>> # The driver to use
>> driver = user.ws3000
>>
>> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
>> same...)
>> model = WS3000
>>
>> # [Optional] USB read/write timeout (helps on Raspberry Pi)
>> # Default is 1000
>> timeout =  1000
>>
>> The rest should be optional.
>>
>>
>>
>>

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

Re: [weewx-user] Re: WS-3000

2020-02-13 Thread Olivier Guyotot

In the file that you sent, the error is:
usb.core.USBError: [Errno 13] Access denied (insufficient permissions)

It looks like your user doesn't have access to the USB device. For testing, 
I would suggest to try as root instead. When it will work as root, you can 
then make it work with your normal user.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c50cffd9-1f6e-458c-9d3d-5f3189268e00%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

@Olivier,
Changed the WeeWX-setup to the 'normal' configuration resulting after 
installation with the tar-file and setup.py.
At least the script ws3000.py now starts running, but not without errors: 
error report has been sent by Email.
Looking at the errorreports, *apparently* the version Python2.7 as part of 
Raspian_Buster is conflicting with functions in script ws3000.py

Op woensdag 12 februari 2020 19:39:15 UTC+1 schreef Olivier Guyotot:
>
> If your installation was done using the Debian package manager, then you 
> need to deploy the ws3000.py file in /usr/share/weewx/user.
>
> And the command to run would presumably be:
> PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py
>
> Unfortunately I have no experience with this type of installation, and no 
> way to test it. I won't be of much help here.
>
> NOTE: I just noticed that in your configuration, you specified driver = 
>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>> Where did you see this info?
>>> Or otherwise formulated: where shal I put such line?
>>
>> I saw that in the StdConvert issue thread, where you posted part of your 
> weex.conf, didn't you?
>
> What you need is a section such as:
> [WS3000]
> # This section is for the Ambient Weather WS3000
>
> # The driver to use
> driver = user.ws3000
>
> # The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
> same...)
> model = WS3000
>
> # [Optional] USB read/write timeout (helps on Raspberry Pi)
> # Default is 1000
> timeout =  1000
>
> The rest should be optional.
>
>
>
>

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

Re: [weewx-user] Re: WS-3000

2020-02-12 Thread Olivier Guyotot

If your installation was done using the Debian package manager, then you 
need to deploy the ws3000.py file in /usr/share/weewx/user.

And the command to run would presumably be:
PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/ws3000.py

Unfortunately I have no experience with this type of installation, and no 
way to test it. I won't be of much help here.

NOTE: I just noticed that in your configuration, you specified driver = 
>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>> Where did you see this info?
>> Or otherwise formulated: where shal I put such line?
>
> I saw that in the StdConvert issue thread, where you posted part of your 
weex.conf, didn't you?

What you need is a section such as:
[WS3000]
# This section is for the Ambient Weather WS3000

# The driver to use
driver = user.ws3000

# The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
same...)
model = WS3000

# [Optional] USB read/write timeout (helps on Raspberry Pi)
# Default is 1000
timeout =  1000

The rest should be optional.



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

Re: [weewx-user] Re: WS-3000

Gary,

Completely agree.
After the experiments, this evening checked the location of weewx-files, 
and that is 100% in accordance with http://www.weewx.com/docs/debian.htm
as could be expected, because the installation was also in accordance with 
that document.
Also at my Raspberry weewx_root is /

Probably it means that for&in ws3000.py some adaptations are required for 
alignment with those different locations, to enable installation of 
ws3000.py
In hindsight taking care of differences dependent on installation procedure:
a) as described in User Guide
b) via setup.py

Anton

Anton

Op woensdag 12 februari 2020 00:00:04 UTC+1 schreef gjr80:
>
> Your issue (to do with file locations) is due to the way in which WeeWX 
> was installed. Installation via setup.py  results in WeeWX files being 
> located in /home/weewx by default. Installation via a package results in 
> the WeeWX files being spread over a number of different locations. Refer to 
> Where 
> to find things  
> in the User's Guide.
>
> Gary
>
> On Wednesday, 12 February 2020 08:36:05 UTC+10, Ton vanN wrote:
>>
>> Olivier,
>>
>> Perhaps the underlaying Linux_version makes a difference.
>> In my configuration it is Raspian_Buster_Lite.
>>
>> Anton
>>
>> Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>>>
>>> Olivier,
>>>
>>> Puzzled, because apparently weewx has been installed in my configuration 
>>> in a different way than you expect.
>>> See the inserted text.
>>>
>>> ;-( Some more thinking to be done ...
>>> Waiting for your next suggestions.
>>>
>>> Anton
>>>
>>> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:

 Alright, so the good news is that the vendor_id and product_id are 
 still the same.

 NOTE: I just noticed that in your configuration, you specified driver = 
 user.hp3000. Unless you made a change, it should be driver = user.ws3000.

>>> Where did you see this info? 
>>> Or otherwise formulated: where shal I put such line?
>>>
>>>
 Assuming that you installed the driver correctly in the bin/user 
 directory, 

>>> In my configuration no folder /bin/user; therefore created and put 
>>> ws3000.py in that folder with x-attribute set, to enable execution
>>> Most weewx-files found in folder /etc/weewx
>>>
>>> to check if the current code is working with your station you could try 
 the following:
 1. first, stop weewx.
 2. from the weewx folder, run the command:
 PYTHONPATH=bin python bin/user/ws3000.py

 To get this running from Putty's CLI, I had to change into 
>>> PYTHONPATH=bin python /bin/user/ws3000.py
>>>
>>> Result is that the execution stops at the first comment-line.
>>> At least positive is that ws3000.py has been found and is executed.
>>> Have taken out all comment lines from ws3000.py between """ and """
>>> Then running
>>> PYTHONPATH=bin python /bin/user/ws3000.py
>>> => result is an error report telling 
>>>   File "/bin/user/ws3000.py", line 17, in 
>>> import weewx.drivers
>>> ImportError: No module named weewx.drivers
>>>
>>> Then stopped, to write this response .
>>>
>>> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
 624 and 626, if you don't see the data (check in the logs first).

 Something else that you could try is to enable debug in the weewx 
 configuration file (debug = 1), start weewx, and send me the log.

>>>

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

Re: [weewx-user] Re: WS-3000

2020-02-11 Thread gjr80

Your issue (to do with file locations) is due to the way in which WeeWX was 
installed. Installation via setup.py  results in WeeWX files being located 
in /home/weewx by default. Installation via a package results in the WeeWX 
files being spread over a number of different locations. Refer to Where to 
find things  in 
the User's Guide.

Gary

On Wednesday, 12 February 2020 08:36:05 UTC+10, Ton vanN wrote:
>
> Olivier,
>
> Perhaps the underlaying Linux_version makes a difference.
> In my configuration it is Raspian_Buster_Lite.
>
> Anton
>
> Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>>
>> Olivier,
>>
>> Puzzled, because apparently weewx has been installed in my configuration 
>> in a different way than you expect.
>> See the inserted text.
>>
>> ;-( Some more thinking to be done ...
>> Waiting for your next suggestions.
>>
>> Anton
>>
>> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>>>
>>> Alright, so the good news is that the vendor_id and product_id are still 
>>> the same.
>>>
>>> NOTE: I just noticed that in your configuration, you specified driver = 
>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>
>> Where did you see this info? 
>> Or otherwise formulated: where shal I put such line?
>>
>>
>>> Assuming that you installed the driver correctly in the bin/user 
>>> directory, 
>>>
>> In my configuration no folder /bin/user; therefore created and put 
>> ws3000.py in that folder with x-attribute set, to enable execution
>> Most weewx-files found in folder /etc/weewx
>>
>> to check if the current code is working with your station you could try 
>>> the following:
>>> 1. first, stop weewx.
>>> 2. from the weewx folder, run the command:
>>> PYTHONPATH=bin python bin/user/ws3000.py
>>>
>>> To get this running from Putty's CLI, I had to change into 
>> PYTHONPATH=bin python /bin/user/ws3000.py
>>
>> Result is that the execution stops at the first comment-line.
>> At least positive is that ws3000.py has been found and is executed.
>> Have taken out all comment lines from ws3000.py between """ and """
>> Then running
>> PYTHONPATH=bin python /bin/user/ws3000.py
>> => result is an error report telling 
>>   File "/bin/user/ws3000.py", line 17, in 
>> import weewx.drivers
>> ImportError: No module named weewx.drivers
>>
>> Then stopped, to write this response .
>>
>> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
>>> 624 and 626, if you don't see the data (check in the logs first).
>>>
>>> Something else that you could try is to enable debug in the weewx 
>>> configuration file (debug = 1), start weewx, and send me the log.
>>>
>>

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

Re: [weewx-user] Re: WS-3000

Have checked the other Raspberries within my reach whether they have a 
folder /bin/user/
Result:
Raspian_Stretch => no folder /bin/user/
Raspian_Buster_Desktop => no folder /bin/user/

Op dinsdag 11 februari 2020 23:36:05 UTC+1 schreef Ton vanN:
>
> Olivier,
>
> Perhaps the underlaying Linux_version makes a difference.
> In my configuration it is Raspian_Buster_Lite.
>
> Anton
>
> Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>>
>> Olivier,
>>
>> Puzzled, because apparently weewx has been installed in my configuration 
>> in a different way than you expect.
>> See the inserted text.
>>
>> ;-( Some more thinking to be done ...
>> Waiting for your next suggestions.
>>
>> Anton
>>
>> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>>>
>>> Alright, so the good news is that the vendor_id and product_id are still 
>>> the same.
>>>
>>> NOTE: I just noticed that in your configuration, you specified driver = 
>>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>>
>> Where did you see this info? 
>> Or otherwise formulated: where shal I put such line?
>>
>>
>>> Assuming that you installed the driver correctly in the bin/user 
>>> directory, 
>>>
>> In my configuration no folder /bin/user; therefore created and put 
>> ws3000.py in that folder with x-attribute set, to enable execution
>> Most weewx-files found in folder /etc/weewx
>>
>> to check if the current code is working with your station you could try 
>>> the following:
>>> 1. first, stop weewx.
>>> 2. from the weewx folder, run the command:
>>> PYTHONPATH=bin python bin/user/ws3000.py
>>>
>>> To get this running from Putty's CLI, I had to change into 
>> PYTHONPATH=bin python /bin/user/ws3000.py
>>
>> Result is that the execution stops at the first comment-line.
>> At least positive is that ws3000.py has been found and is executed.
>> Have taken out all comment lines from ws3000.py between """ and """
>> Then running
>> PYTHONPATH=bin python /bin/user/ws3000.py
>> => result is an error report telling 
>>   File "/bin/user/ws3000.py", line 17, in 
>> import weewx.drivers
>> ImportError: No module named weewx.drivers
>>
>> Then stopped, to write this response .
>>
>> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
>>> 624 and 626, if you don't see the data (check in the logs first).
>>>
>>> Something else that you could try is to enable debug in the weewx 
>>> configuration file (debug = 1), start weewx, and send me the log.
>>>
>>

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

Re: [weewx-user] Re: WS-3000

Olivier,

Perhaps the underlaying Linux_version makes a difference.
In my configuration it is Raspian_Buster_Lite.

Anton

Op dinsdag 11 februari 2020 22:29:08 UTC+1 schreef Ton vanN:
>
> Olivier,
>
> Puzzled, because apparently weewx has been installed in my configuration 
> in a different way than you expect.
> See the inserted text.
>
> ;-( Some more thinking to be done ...
> Waiting for your next suggestions.
>
> Anton
>
> Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>>
>> Alright, so the good news is that the vendor_id and product_id are still 
>> the same.
>>
>> NOTE: I just noticed that in your configuration, you specified driver = 
>> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>>
> Where did you see this info? 
> Or otherwise formulated: where shal I put such line?
>
>
>> Assuming that you installed the driver correctly in the bin/user 
>> directory, 
>>
> In my configuration no folder /bin/user; therefore created and put 
> ws3000.py in that folder with x-attribute set, to enable execution
> Most weewx-files found in folder /etc/weewx
>
> to check if the current code is working with your station you could try 
>> the following:
>> 1. first, stop weewx.
>> 2. from the weewx folder, run the command:
>> PYTHONPATH=bin python bin/user/ws3000.py
>>
>> To get this running from Putty's CLI, I had to change into 
> PYTHONPATH=bin python /bin/user/ws3000.py
>
> Result is that the execution stops at the first comment-line.
> At least positive is that ws3000.py has been found and is executed.
> Have taken out all comment lines from ws3000.py between """ and """
> Then running
> PYTHONPATH=bin python /bin/user/ws3000.py
> => result is an error report telling 
>   File "/bin/user/ws3000.py", line 17, in 
> import weewx.drivers
> ImportError: No module named weewx.drivers
>
> Then stopped, to write this response .
>
> NOTE: you may have to replace the 'logdbg' statements by 'print', lines 
>> 624 and 626, if you don't see the data (check in the logs first).
>>
>> Something else that you could try is to enable debug in the weewx 
>> configuration file (debug = 1), start weewx, and send me the log.
>>
>

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

Re: [weewx-user] Re: WS-3000

Olivier,

Puzzled, because apparently weewx has been installed in my configuration in 
a different way than you expect.
See the inserted text.

;-( Some more thinking to be done ...
Waiting for your next suggestions.

Anton

Op dinsdag 11 februari 2020 20:17:29 UTC+1 schreef Olivier Guyotot:
>
> Alright, so the good news is that the vendor_id and product_id are still 
> the same.
>
> NOTE: I just noticed that in your configuration, you specified driver = 
> user.hp3000. Unless you made a change, it should be driver = user.ws3000.
>
Where did you see this info? 
Or otherwise formulated: where shal I put such line?


> Assuming that you installed the driver correctly in the bin/user 
> directory, 
>
In my configuration no folder /bin/user; therefore created and put 
ws3000.py in that folder with x-attribute set, to enable execution
Most weewx-files found in folder /etc/weewx

to check if the current code is working with your station you could try the 
> following:
> 1. first, stop weewx.
> 2. from the weewx folder, run the command:
> PYTHONPATH=bin python bin/user/ws3000.py
>
> To get this running from Putty's CLI, I had to change into 
PYTHONPATH=bin python /bin/user/ws3000.py

Result is that the execution stops at the first comment-line.
At least positive is that ws3000.py has been found and is executed.
Have taken out all comment lines from ws3000.py between """ and """
Then running
PYTHONPATH=bin python /bin/user/ws3000.py
=> result is an error report telling 
  File "/bin/user/ws3000.py", line 17, in 
import weewx.drivers
ImportError: No module named weewx.drivers

Then stopped, to write this response .

NOTE: you may have to replace the 'logdbg' statements by 'print', lines 624 
> and 626, if you don't see the data (check in the logs first).
>
> Something else that you could try is to enable debug in the weewx 
> configuration file (debug = 1), start weewx, and send me the log.
>

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

Re: [weewx-user] Re: WS-3000

2020-02-11 Thread Olivier Guyotot

Alright, so the good news is that the vendor_id and product_id are still 
the same.

NOTE: I just noticed that in your configuration, you specified driver = 
user.hp3000. Unless you made a change, it should be driver = user.ws3000.

Assuming that you installed the driver correctly in the bin/user directory, 
to check if the current code is working with your station you could try the 
following:
1. first, stop weewx.
2. from the weewx folder, run the command:
PYTHONPATH=bin python bin/user/ws3000.py

NOTE: you may have to replace the 'logdbg' statements by 'print', lines 624 
and 626, if you don't see the data (check in the logs first).

Something else that you could try is to enable debug in the weewx 
configuration file (debug = 1), start weewx, and send me the log.

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

Re: [weewx-user] Re: WS-3000

On command *lsusb* the following response

Bus 001 Device 002: ID 0483:5750 STMicroelectronics
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub






Op maandag 10 februari 2020 19:30:49 UTC+1 schreef Olivier Guyotot:
>
> I haven't touched this in a while (it's just running on its own), my 
> memory is a bit fuzzy... It will take time for me to properly remember 
> everything.
>
> That being said, there are 2 major things to check:
> 1. that your station is indeed working like a WS3000.
> 2. what is the correct configuration to use.
>
> Let's start with 2.
>
> In your case, the first thing to check is if you can use the default or if 
> you need to update the vendor_id and product_id.
>
> Just run 
> lsusb
> on your raspberry and please post the output here.
>
>
>

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

Re: [weewx-user] Re: WS-3000

2020-02-10 Thread Olivier Guyotot

I haven't touched this in a while (it's just running on its own), my memory 
is a bit fuzzy... It will take time for me to properly remember everything.

That being said, there are 2 major things to check:
1. that your station is indeed working like a WS3000.
2. what is the correct configuration to use.

Let's start with 2.

In your case, the first thing to check is if you can use the default or if 
you need to update the vendor_id and product_id.

Just run 
lsusb
on your raspberry and please post the output here.


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

Re: [weewx-user] Re: WS-3000

2020-02-10 Thread Ton vanN

This thread makes interesting reading.

Have a Misol console type HP3001 (which probably is a next version/clone of 
HP3000), and assume therefore that the discussed HP3000/WS3000-driver will 
be applicable.
5 Sensors attached.
At processor-side have a configuration with Raspbian Buster on 
Raspberry_Zero_W
Installed ss described by Jack Stromberg at 
https://jackstromberg.com/2018/06/setting-up-weewx-with-a-raspberry-pi/
Lacking a better choice set WeeWX for 'Simulator'
Seems to work.

Next step is installation of the WS3000-driver, reconfig with that driver 
and then restart incl. de USB-interface to the Console of WS3000/HP300x
Have read the attachment to previous message, but NOOB needing simple 
instructions.

*Any hints for the next steps?*

Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>
> Here is an updated version of the driver, including:
> - the fix for sub-zero temperatures
> - improved error handling/retry (something that wasn't working properly 
> before)
> - the usb timeout is now a configuration setting
> - additional comments
>
> It probably won't fix the root cause of the 'crash' issue, but at least it 
> should now properly retry so the problem might be more transparent. And the 
> error reporting will be more useful to figure out what's wrong should an 
> exception occur.
>

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

Re: [weewx-user] Re: WS-3000

2020-02-09 Thread Ton vanN

Sorry, small typing-mistake: my console is Misol HP3001

Op zondag 9 februari 2020 14:02:30 UTC+1 schreef Ton vanN:
>
> This thread makes interesting reading.
>
> Have a Misol console type HP3010 (which probably is a next version/clone 
> of HP3000), and assume therefore that the discussed HP3000-driver will be 
> applicable.
> 5 Sensors attached.
> At processor-side have a configuration with Raspbian Buster on 
> Raspberry_Zero_W
> Lacking a better choice set WeeWX for 'Simulator' [or should that better 
> be FineOffset WS3000?]
> The 5 Sensors not yet included in weewx.conf
>
> For my configuration the manuals on github etc. needed some tweaking, 
> because during installation  the files arrived at other places.
> Now got the pieces operational, but the overall result is negative: 
> no read-out visible from the console, and the web-interface is fixed/fake.
>
> *Any hints for next steps?*
>
> Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>>
>> Here is an updated version of the driver, including:
>> - the fix for sub-zero temperatures
>> - improved error handling/retry (something that wasn't working properly 
>> before)
>> - the usb timeout is now a configuration setting
>> - additional comments
>>
>> It probably won't fix the root cause of the 'crash' issue, but at least 
>> it should now properly retry so the problem might be more transparent. And 
>> the error reporting will be more useful to figure out what's wrong should 
>> an exception occur.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e948c3b8-761a-4bc8-8d8d-136d22184a2d%40googlegroups.com.

Re: [weewx-user] Re: WS-3000

2020-02-09 Thread Ton vanN

This thread makes interesting reading.

Have a Misol console type HP3010 (which probably is a next version/clone of 
HP3000), and assume therefore that the discussed HP3000-driver will be 
applicable.
5 Sensors attached.
At processor-side have a configuration with Raspbian Buster on 
Raspberry_Zero_W
Lacking a better choice set WeeWX for 'Simulator' [or should that better be 
FineOffset WS3000?]
The 5 Sensors not yet included in weewx.conf

For my configuration the manuals on github etc. needed some tweaking, 
because during installation  the files arrived at other places.
Now got the pieces operational, but the overall result is negative: 
no read-out visible from the console, and the web-interface is fixed/fake.

*Any hints for next steps?*

Op dinsdag 30 oktober 2018 17:49:35 UTC+1 schreef olivier...@gmail.com:
>
> Here is an updated version of the driver, including:
> - the fix for sub-zero temperatures
> - improved error handling/retry (something that wasn't working properly 
> before)
> - the usb timeout is now a configuration setting
> - additional comments
>
> It probably won't fix the root cause of the 'crash' issue, but at least it 
> should now properly retry so the problem might be more transparent. And the 
> error reporting will be more useful to figure out what's wrong should an 
> exception occur.
>

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

Re: [weewx-user] Re: WS-3000

2018-10-31 Thread Risto H. Kurppa

Great, I now deployed the updated drivers & restarted on screen with
/usr/bin/weewxd /etc/weewx/weewx.conf

On Tue, Oct 30, 2018 at 6:49 PM  wrote:

> Here is an updated version of the driver, including:
> - the fix for sub-zero temperatures
> - improved error handling/retry (something that wasn't working properly
> before)
> - the usb timeout is now a configuration setting
> - additional comments
>
> It probably won't fix the root cause of the 'crash' issue, but at least it
> should now properly retry so the problem might be more transparent. And the
> error reporting will be more useful to figure out what's wrong should an
> exception occur.
>
> --
> 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/qDe-El03C2k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

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

Here is an updated version of the driver, including:
- the fix for sub-zero temperatures
- improved error handling/retry (something that wasn't working properly
before)
- the usb timeout is now a configuration setting
- additional comments

It probably won't fix the root cause of the 'crash' issue, but at least it
should now properly retry so the problem might be more transparent. And the
error reporting will be more useful to figure out what's wrong should an
exception occur.

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
#
#
"""Classes and functions for interfacing with an Ambient Weather WS-3000
station.

The following references were useful for developing this driver. More than simply useful,
in fact, since a lot of material has been directly reused:

>From Matthew Wall:
https://github.com/matthewwall/weewx-hp3000

>From Tom Keffer, the WMR100 driver for weewx
http://www.weewx.com

Many thanks to the following contributers:
- RistoK for helping with troubleshooting and testing on RPi

NOTE: the HP3000 driver developed by Matthew Wall should also be working
for the WS-3000 station. But various issues led me to rewrite a new driver
on the model of the one for the WMR100. One benefit is that this driver will
work with the "default" version of weewx and doesn't require the usb branch.

NOTE: since the station doesn't distinguish between loop and archive packets,
only genLoopPackets is implemented. It doesn't make sense to implement the other
AbstractDevice methods such as genArchiveRecords.
As a result, weewx should be configured with record_generation = software

NOTE: it seems that when packets are generated (data is fetch from the console) too quickly, errors can
occur, causing the station to 'hang' and potentially crashing weewx (error handling in this
driver is not the best!). Make sure that the loop interval is large enough to avoid any
potential issue.

NOTE for Raspberry Pi: if the usb read/write timeout is too small (100ms), errors
might occur when sending/fetching data from the console. It has been increased to 1000 by default,
but if this is still not sufficient futher increase the timeout in the weewx configuration file.

The comments below are taken directly from Matthew Wall's driver. They are included here for reference:

The HP-3000 supports up to 8 remote temperature/humidity sensors. The console
has a 3"x4" TFT color display, with graph and room for 5 sensor displays. The
sensor display regions can cycle through different sensors when more than 5
sensors are connected.
Every configuration option in the console can be modified via software. These
options includes:
- archive interval
- date/time
- date/time format
- timezone
- which sensors should be displayed in the 5 display regions
- horizontal graph axis scaling
- vertical graph axis
- calibration for temperature/humidity from each sensor
- alarms
- historical data
Historical data are saved to the (optional) microSD card. If no card is
installed, no data are retained.
Each sensor has its own display of temperature and humidity.
Each sensor is identified by channel number. The channel number is set using
DIP switches on each sensor. The DIP switches also determine which units will
be displayed in each sensor.
There are 4 two-position DIP switches. DIP 4 determines units: 0=F 1=C
DIP 1-3 determine which of 8 channels is selected.
Each sensor uses 2 AA batteries. Nominal battery life is 1 year.
The console uses 5V DC from an AC/DC transformer.
Data from sensors are received every 60 seconds.
Dewpoint and heatindex are calculated within the console.
Temperature sensors measure to +/- 2 degree F
Humidity sensors measure to +/- 5 %
Calibrations are applied in the console, so the values received from the
console are calibrated. Calculations in the console are performed in degree C.
The console has a radio controlled clock. During RCC reception, no data will
be transmitted. If no RCC is received, attempt will be made every two hours
until successful.
This driver was developed without any assistance from Ambient Weather (the
vendor) or Fine Offset (the manufacturer).
===
Messages from console
The console sends data in 64-byte chunks. It looks like the console reuses a
buffer, because each message shorter than the previous contains bytes from the
previous message. The byte sequence 0x40 0x7d indicates end of data within a
buffer.
Many of the console messages correspond with the control messages sent from
the host.

<...>

current data (27 bytes)
00 7b
01 00 ch1 temp MSB
02 eb ch1 temp LSBt1 = (signed short(MSB,LSB)) / 10.0 - NB: modified to handle negative values
03 25 ch1 hum h1 = hum
04 7f

Re: [weewx-user] Re: WS-3000

I have Raspberry 2, 1GB but I normally use it as a multimedia player, not 
for the station. So I just installed it with Raspbian (Stretch), following 
your guide :) I also made a few adjustments to my code, to try to improve 
the error reporting, but the syslog module in Python is really crap and 
limited... we'll see if what I did is enough.

So far, no error. I don't know if this is because of the hardware though. 
On average, what is the frequency of your crashes?

Note: could you try to start weewx manually instead of using the service?
/usr/bin/weewxd /etc/weewx/weewx.conf

There might be more information logged in the console than in the logs when 
an exception occurs.

You can use 'screen' to run the command if you don't have a permanent 
connection to the Raspberry. This way the command will continue to run even 
if you disconnect from ssh.

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

Re: [weewx-user] Re: WS-3000

2018-10-29 Thread Risto H. Kurppa

Sub-zero seems to work, ws3000 driver values match to what the original
display shows. Great :) Winter, I'm ready!

I now changed
record_generation = software
archive_interval=120
loop_interval=60
USB read & write timeouts = 1

Oct 29 22:00:03 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:01:03 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:01:05 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:02:05 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:03:06 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:03:08 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:04:08 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:05:08 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:05:10 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:06:10 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:07:11 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:07:12 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:08:13 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:09:13 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:09:15 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:10:16 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:10:18 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:11:18 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:12:18 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:12:21 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 22:13:21 ripapi weewx[25186]: ws3000: write: 7b 03 40 7d (len=4)

As every 2nd value is a 'closely timed pair', it really looks like that
both, the archive run (120s interval) and loop run (60s interval) read new
values from the main unit.



And I agree, that best would be to share the 'final files' - but as this
still is strongly a 'work in progress', I use the etherpad to collect the
'current best solution'. I wouldn't have the energy to now upload all files
publicly available somewhere after every change :)
-> Let's try to make this stable and release the files somewhere


What RasPi do you have? I have the old RasPi model B rev2 (512MB), if that
makes any difference.



On Mon, Oct 29, 2018 at 7:11 PM  wrote:

> OK, I couldn't let you do all the work alone, so I retrieved my ws3000 and
> did some test. Switching to record_generation = software does not prevent
> the duplicate loop packets. But I would still change the configuration,
> because hardware just doesn't make any sense (if I understand what this
> means correctly). I also saw a comment in the documentation mentioning that
> 'hardware' could cause issues with one station.
>
> So far I haven't gotten any crash, so I'll let weewx run for a while, see
> if I also get a crash. If not, I'll try to setup my RPi to do the tests.
>
> --
> 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/qDe-El03C2k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

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

Re: [weewx-user] Re: WS-3000

OK, I couldn't let you do all the work alone, so I retrieved my ws3000 and 
did some test. Switching to record_generation = software does not prevent 
the duplicate loop packets. But I would still change the configuration, 
because hardware just doesn't make any sense (if I understand what this 
means correctly). I also saw a comment in the documentation mentioning that 
'hardware' could cause issues with one station.

So far I haven't gotten any crash, so I'll let weewx run for a while, see 
if I also get a crash. If not, I'll try to setup my RPi to do the tests.

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

Re: [weewx-user] Re: WS-3000

For the sub-zero fix, did you confirm if this is now working as expected?
Also, rather than documenting how to fix the code, it might be better to 
upload the latest version of the code once we'll have fixed all the issues 
(although I'll try to document what we did in the code).

For the crash, the output from grep is interesting:
- first, it confirms that when weewx is generating an archive record, it is 
pulling data from the station (hence the duplicate every 2 minutes).
- since the loop packet and the archive record are generated within a very 
short time, it is likely that this is what's causing the issue (as I 
mentioned, that's something I ran into when I initially tested the driver). 
I wonder if it makes sense to modify the driver to return the latest 
'cached' packet when several attempts are made to fetch the data within a 
short period of time (less than 10 seconds maybe?).

But let's first try to fix this with the configuration: can you try setting 
record_generation 
= software to see if it helps to avoid this issue (after the change, leave 
weewx running for some time then redo the grep)?

Using hardware doesn't really make sense anyway for this station: as far as 
I can tell the WS-3000 has no concept of loop vs archive packets, all you 
can do it fetch the current values from the station. So if this works as I 
expect when using 'software', you could generate loop packets every 30 or 
60 seconds, and let weewx generate the archive record every 2 to 5 minutes. 
weewx will aggregate the data from all the previous loop packets to produce 
the min/max during this 2 to 5 minutes interval but won't fetch the data 
again, thus avoid the issue.

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

Re: [weewx-user] Re: WS-3000

2018-10-29 Thread RistoK

Applied the sub-zero fix and updated it to 
https://etherpad.net/p/weewx_raspi

Yes, I only have 1 station currenlty but might at some point add a DHT22 or 
some DIY air quality sensors.

Oct 29 11:58:58 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 11:59:01 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:00:01 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:01:01 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:01:04 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:02:04 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:03:04 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:03:07 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:04:08 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:05:08 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:05:10 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:05:36 ripapi weewx[22384]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:07:06 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:08:07 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:09:07 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:09:09 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:10:09 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:11:09 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:11:11 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:12:12 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:13:12 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:13:14 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:14:14 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:14:17 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:15:17 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:16:18 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:16:20 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:17:20 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:18:20 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:18:23 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:19:23 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:20:23 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:20:26 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:21:26 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:22:26 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:22:29 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:23:30 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:24:30 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:24:33 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:25:33 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:26:33 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:26:36 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)
Oct 29 12:27:36 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4)


looks like that it's a bit irregular. I changed the loop interval from 30-> 
60 earlier today, but to me it looks like that some 'duplicates' are there.


My weewx.conf visible at https://pastebin.com/gZvFUm5q 
-> Please propose changes, if needed.

Archive interval now 2min for test purposes, can change that to 5min if 
useful. Also if record_generation needs to be changed to software, that's 
also OK. I haven't yet read very much what do these configs do..


And thanks for your help Olivier :)


r

maanantai 29. lokakuuta 2018 11.30.10 UTC+2 olivier...@gmail.com kirjoitti:
>
> ok, this is weird. If the interval was already 30 seconds, I don't 
> understand why the driver was trying to fetch the data several times in a 
> short interval (as seen in your log).
>
> What's the output of:
> grep "ws3000: write" 
> I would like to see how often the driver is fetching data.
>
> I have to admit that I can't remember how this is all supposed to work. My 
> setup is very different: I am using the ws3000DataService to fetch the 
> values from the WS-3000 only when I am writing a record to the database 
> (every 60 seconds). The data is then combined with what I get from my other 
> station. You could say that in my case, the WS-3000 is only a secondary 
> station, and therefore the loop_interval is not taken into account.
>
> In your case (I am assuming that you only have 1 station), it doesn't make 
> sense to use the ws3000DataService. But we need to figure out how weewx and 
> the driver are interacting with the station...
> As far as I can tell, the driver is generating loop packets (using the 
> loop_interval). Then, I assume that when weewx is generating an archive 
> record something el

Re: [weewx-user] Re: WS-3000

ok, this is weird. If the interval was already 30 seconds, I don't 
understand why the driver was trying to fetch the data several times in a 
short interval (as seen in your log).

What's the output of:
grep "ws3000: write" 
I would like to see how often the driver is fetching data.

I have to admit that I can't remember how this is all supposed to work. My 
setup is very different: I am using the ws3000DataService to fetch the 
values from the WS-3000 only when I am writing a record to the database 
(every 60 seconds). The data is then combined with what I get from my other 
station. You could say that in my case, the WS-3000 is only a secondary 
station, and therefore the loop_interval is not taken into account.

In your case (I am assuming that you only have 1 station), it doesn't make 
sense to use the ws3000DataService. But we need to figure out how weewx and 
the driver are interacting with the station...
As far as I can tell, the driver is generating loop packets (using the 
loop_interval). Then, I assume that when weewx is generating an archive 
record something else must be happening, depending on the values of the 
archive_interval and maybe record_generation (software or hardware). But I 
don't know exactly how this is working, and what function weewx is calling 
to fetch the data (is it calling genLoopPackets again?). I have the feeling 
that the record generation might trigger an additional query to the 
station, and if it turns out to be too close to a loop packet generation, 
then we run into the current issue.

Ideally, you would want to disable the loop packets completely if possible, 
and just let weewx fetch the data when it needs to generate an archive 
record. I don't know if this is possible though. But after quickly looking 
at the documentation, I think that you may have to consider switching 
record_generation to *software*. This might help to prevent the problem, if 
weewx builds the record from previous loop packets rather than be querying 
the station again.

What is your archive_interval?

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

Re: [weewx-user] Re: WS-3000

Here is the suggested code change for the negative temperature:

First, add the following import near the top of the file (next to the other 
imports):

import struct

Then, use the following code to compute the temperature

record['t_%s' % (ch + 1)] = struct.unpack('>h', buf[idx:idx+2])[0] / 10.0


I think that this should work properly for all temperatures.
 

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

Re: [weewx-user] Re: WS-3000

2018-10-29 Thread RistoK

Negative values - great!!

I didn't change the loop interval:
# [Optional] The interval at which loop packets should be generated by 
the driver
# Default is 10
loop_interval = 30

Now I changed it to 1min, let's see if crashes still occur.. 

r

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

Re: [weewx-user] Re: WS-3000

For the negative values:
=> I figured it out, it is in fact quite simple. We have to treat the raw 
data as a signed short. I'll see how to change the code to take this into 
account. Shouldn't be difficult.

For the crash:
=> 
- I noticed that at 00:12:31, the driver is sending a command (ws3000: 
reading results), and it reads the data at 00:12:32.
- Then, at 00:12:35, another command is sent, and this one fails.

That's only a few seconds later. If I remember correctly, I ran into 
something similar: I was trying to read the data as fast as for my other 
station (Vantage, for which I get data every second or so). Then I simply 
fetched the data from the WS-3000 when storing records into the weewx 
database, so every minute only. I think that this was what solved the 
problem for me.

How did you configure the loop_interval? Can you try to increase it? Try 30 
or 60 seconds at least. For temperature, it doesn't really make sense to 
fetch the data too often anyway.

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

Re: [weewx-user] Re: WS-3000

2018-10-28 Thread RistoK

Two of us - I feel sorry for everyone else. Think of all the fun they're 
missing :D



*INCORRECT HANDLING OF NEGATIVE TEMPERATURES*
Changed the code as you suggested and made a quick test comparing 
ws3000driver vs. display. Results below:

*Display: -0.2 vs log -0.1 (outside temp.)*
Oct 29 00:01:02 ripapi weewx[18267]: ws3000: reading 64 bytes
Oct 29 00:01:02 ripapi weewx[18267]: ws3000: read: 7b ff fd 32 00 dc 1e 00 
cd 23 00 d2 23 00 d9 21 00 b0 20 00 df 1d 7f ff ff 40 7d 00 40 7d 2c 00 64 
40 7d 00 4e 14 2f 2c d1 d7 e7 70 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 1a 
0e 52 33 f6 80 ce (len=64)
Oct 29 00:01:02 ripapi weewx[18267]: ws3000: extracting values for 
sensor_values
Oct 29 00:01:02 ripapi weewx[18267]: ws3000: raw: array('B', [123, 255, 
253, 50, 0, 220, 30, 0, 205, 35, 0, 210, 35, 0, 217, 33, 0, 176, 32, 0, 
223, 29, 127, 255, 255, 64, 125])
Oct 29 00:01:02 ripapi weewx[18267]: ws3000: data: {'h_6': 32, 'h_7': 29, 
'h_4': 35, 'h_5': 33, 'h_2': 30, 'h_3': 35, 'h_1': 50, 't_6': 17.6, 't_2': 
22.0, 't_3': 20.5, 't_1': -0.2, 'type': 'sensor_values', 't_7': 22.3, 
't_4': 21.0, 't_5': 21.7}
Oct 29 00:01:02 ripapi weewx[18267]: ws3000: packet: {'dateTime': 
1540764063, 'extraHumid6': 32, 'extraHumid7': 29, 'extraHumid4': 35, 
'extraHumid5': 33, 'extraHumid2': 30, 'extraHumid3': 35, 'extraHumid1': 50, 
'extraTemp6': 17.6, 'extraTemp7': 22.3, 'extraTemp4': 21.0, 'extraTemp5': 
21.7, 'extraTemp2': 22.0, 'extraTemp3': 20.5, 'usUnits': 17, *'extraTemp1': 
-0.2*}



*DIsplay -5.4 vs log -5.3 (some minutes in the freezer)*
Oct 29 00:05:13 ripapi weewx[18267]: ws3000: read: 7b ff ca 27 00 dc 1e 00 
cc 22 00 d2 23 00 da 21 00 af 20 00 e0 1d 7f ff ff 40 7d 00 40 7d 2c 00 64 
40 7d 00 4e 14 2f 2c d1 d7 e7 7
0 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 1a 0e 52 33 f6 80 ce (len=64)
Oct 29 00:05:13 ripapi weewx[18267]: ws3000: extracting values for 
sensor_values
Oct 29 00:05:13 ripapi weewx[18267]: ws3000: raw: array('B', [123, 255, 
202, 39, 0, 220, 30, 0, 204, 34, 0, 210, 35, 0, 218, 33, 0, 175, 32, 0, 
224, 29, 127, 255, 255, 64, 125])
Oct 29 00:05:13 ripapi weewx[18267]: ws3000: data: {'h_6': 32, 'h_7': 29, 
'h_4': 35, 'h_5': 33, 'h_2': 30, 'h_3': 34, 'h_1': 39, 't_6': 17.5, 't_2': 
22.0, 't_3': 20.4, 't_1': -5.3,
'type': 'sensor_values', 't_7': 22.4, 't_4': 21.0, 't_5': 21.8}
Oct 29 00:05:13 ripapi weewx[18267]: ws3000: packet: {'dateTime': 
1540764313, 'extraHumid6': 32, 'extraHumid7': 29, 'extraHumid4': 35, 
'extraHumid5': 33, 'extraHumid2': 30, 'extraHu
mid3': 34, 'extraHumid1': 39, 'extraTemp6': 17.5, 'extraTemp7': 22.4, 
'extraTemp4': 21.0, 'extraTemp5': 21.8, 'extraTemp2': 22.0, 'extraTemp3': 
20.4, 'usUnits': 17, 

*'extraTemp1': -5.3}*
*DIsplay -11.2 vs log -11.1 (a bit longer in the freezer)*
Oct 29 00:12:32 ripapi weewx[18267]: ws3000: read: 7b ff 90 28 00 dc 1e 00 
cd 22 00 d2 23 00 d9 21 00 b0 20 00 df 1d 7f ff ff 40 7d 00 40 7d 2c 00 64 
40 7d 00 4e 14 2f 2c d1 d7 e7 70 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 1a 
0e 52 33 f6 80 ce (len=64)
Oct 29 00:12:32 ripapi weewx[18267]: ws3000: extracting values for 
sensor_values
Oct 29 00:12:32 ripapi weewx[18267]: ws3000: raw: array('B', [123, 255, 
144, 40, 0, 220, 30, 0, 205, 34, 0, 210, 35, 0, 217, 33, 0, 176, 32, 0, 
223, 29, 127, 255, 255, 64, 125])
Oct 29 00:12:32 ripapi weewx[18267]: ws3000: data: {'h_6': 32, 'h_7': 29, 
'h_4': 35, 'h_5': 33, 'h_2': 30, 'h_3': 34, 'h_1': 40, 't_6': 17.6, 't_2': 
22.0, 't_3': 20.5, 't_1': -11.1, 'type': 'sensor_values', 't_7': 22.3, 
't_4': 21.0, 't_5': 21.7}
Oct 29 00:12:32 ripapi weewx[18267]: ws3000: packet: {'dateTime': 
1540764752, 'extraHumid6': 32, 'extraHumid7': 29, 'extraHumid4': 35, 
'extraHumid5': 33, 'extraHumid2': 30, 'extraHumid3': 34, 'extraHumid1': 40, 
'extraTemp6': 17.6, 'extraTemp7': 22.3, 'extraTemp4': 21.0, 'extraTemp5': 
21.7, 'extraTemp2': 22.0, 'extraTemp3': 20.5, 'usUnits': 17, 'extraTemp1': 
-11.1}

*DIsplay -16.8 vs log -16.7 (even longer in the freezer)*
Oct 29 00:24:04 ripapi weewx[19860]: ws3000: read: 7b ff 58 2a 00 dd 1f 00 
cc 22 00 d2 23 00 d9 21 00 b0 20 00 e0 1d 7f ff ff 40 7d 00 40 7d 2c 00 64 
40 7d 00 4e 14 2f 2c d1 d7 e7 7
0 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 1a 0e 52 33 f6 80 ce (len=64)
Oct 29 00:24:04 ripapi weewx[19860]: ws3000: extracting values for 
sensor_values
Oct 29 00:24:04 ripapi weewx[19860]: ws3000: raw: array('B', [123, 255, 88, 
42, 0, 221, 31, 0, 204, 34, 0, 210, 35, 0, 217, 33, 0, 176, 32, 0, 224, 29, 
127, 255, 255, 64, 125])
Oct 29 00:24:04 ripapi weewx[19860]: ws3000: data: {'h_6': 32, 'h_7': 29, 
'h_4': 35, 'h_5': 33, 'h_2': 31, 'h_3': 34, 'h_1': 42, 't_6': 17.6, 't_2': 
22.1, 't_3': 20.4, 't_1': -16.7,
 'type': 'sensor_values', 't_7': 22.4, 't_4': 21.0, 't_5': 21.7}
Oct 29 00:24:04 ripapi weewx[19860]: ws3000: packet: {'dateTime': 
1540765444, 'extraHumid6': 32, 'extraHumid7': 29, 'extraHumid4': 35, 
'extraHumid5': 33, 'extraHumid2': 31, 'extraHu
mid3': 34, 'extraHumid1': 42, 'extraTemp6': 17.6, 'extraTemp7': 22.4, 
'extraTemp4': 21.0, 'extraTemp5': 21.

Re: [weewx-user] Re: WS-3000

2018-10-28 Thread olivier . guyotot

For reference, the code converting the raw values to a temperature is 
coming from:
https://github.com/matthewwall/weewx-hp3000

You can see how the values are interpreted in the comments I honestly don't 
know where the MSB * 256 is coming from.

current data (27 bytes)
00 7b
01 00 ch1 temp MSB
02 eb ch1 temp LSBt1 = (MSB * 256 + LSB) / 10.0
03 25 ch1 hum h1 = hum
04 7f ch2 temp MSB
05 ff ch2 temp LSB
06 ff ch2 hum


In my driver, I simply copied the code as is, in the function _raw_to_data

Now, to answer your questions:

1. Changing the formula to handle negative values would be very simple. The 
only problem is to figure out which formula should be used. Your suggestion 
is a possible one, but I would prefer to do (LSB - MSB) / 10. As far as I 
can tell, this should produce the same results, both for positive and 
negative numbers, without an if condition.
For example, based on your logs:
* (1 - 0) / 10 = 0.1
* (230 - 255) / 10 = -2.5
In any case we would need to compare the raw data with the temperature 
displayed by your sensor, for a range of values to confirm that the formula 
is correct or to come up with a better one. Would you be able to collect 
this? It would mean leaving the debug=1 mode on for a while, and when you 
get negative temperatures just compare what the sensor displays with what 
you get in the logs at the same time.

PS: The line that you would have to edit to change the formula (if you want 
to do it yourself) is:

if buf[idx] != 0x7f and buf[idx + 1] != 0xff:
record['t_%s' % (ch + 1)] = (buf[idx] * 256 + buf[idx + 1]) / 10.0

You would have to replace it with:

record['t_%s' % (ch + 1)] = (buf[idx + 1] - buf[idx]) / 10.0


NB: as I said, I never tested the driver with negative values (mine are all 
indoor sensors). And I wouldn't be surprised if we were the only two 
persons in the world using weewx with a WS-3000 :) So no, I don't think 
that anybody ever confirmed anything before (either with my driver or with 
Matthew's).

NB2: yes, putting the code on github would be nice. I thought about it, but 
as with the documentation, I never found the time/motivation to do so.

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

Re: [weewx-user] Re: WS-3000

2018-10-28 Thread RistoK

Yes I changed delay to 1000 on both read & write. Didn't increase it now, 
let's see if I get a debig log if it crashes again.


Regarding values of 6500C from WS3000 driver. Please check these two reads 
from below. I took my outside unit inside for a while - worked OK - and 
then put it to freezer for a while and this is what happened when values 
changed from 0.1C to sub-zero (below 0C). Main unit works without issues.


Oct 28 22:20:55 ripapi weewx[17385]: ws3000: sending request for 
sensor_values
Oct 28 22:20:55 ripapi weewx[17385]: ws3000: write: 7b 03 40 7d (len=4)
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: reading results...
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: reading 64 bytes
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: read: 7b *00 01* 10 00 dc 1f 
00 ce 23 00 d1 23 00 d9 22 00 b0 20 00 dd 1e 7f ff ff 40 7d 00 40 7d 2c 00 
64 40 7d 00 4e 14 2f 2c d1 d7 e7 70 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 
1a 0e 52 33 f6 80 ce (len=64)
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: extracting values for 
sensor_values
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: raw: array('B', [123, *0, 1*, 
16, 0, 220, 31, 0, 206, 35, 0, 209, 35, 0, 217, 34, 0, 176, 32, 0, 221, 30, 
127, 255, 255, 64, 125])
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: data: {'h_6': 32, 'h_7': 30, 
'h_4': 35, 'h_5': 34, 'h_2': 31, 'h_3': 35, 'h_1': 16, 't_6': 17.6, 't_2': 
22.0, 't_3': 20.6, '*t_1': 0.1*, 'type': 'sensor_values', 't_7': 22.1, 
't_4': 20.9, 't_5': 21.7}
Oct 28 22:20:56 ripapi weewx[17385]: ws3000: packet: {'dateTime': 
1540758056, 'extraHumid6': 32, 'extraHumid7': 30, 'extraHumid4': 35, 
'extraHumid5': 34, 'extraHumid2': 31, 'extraHumid3': 35, 'extraHumid1': 16, 
'extraTemp6': 17.6, 'extraTemp7': 22.1, 'extraTemp4': 20.9, 'extraTemp5': 
21.7, 'extraTemp2': 22.0, 'extraTemp3': 20.6, 'usUnits': 17,* 'extraTemp1': 
0.1*}
Oct 28 22:21:26 ripapi weewx[17385]: ws3000: sending request for 
sensor_values
Oct 28 22:21:26 ripapi weewx[17385]: ws3000: write: 7b 03 40 7d (len=4)
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: reading results...
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: reading 64 bytes
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: read: 7b *ff e6* 10 00 dc 1f 
00 cc 23 00 d1 23 00 d9 22 00 b0 20 00 dd 1e 7f ff ff 40 7d 00 40 7d 2c 00 
64 40 7d 00 4e 14 2f 2c d1 d7 e7 70 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 
1a 0e 52 33 f6 80 ce (len=64)
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: extracting values for 
sensor_values
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: raw: array('B', [123, *255, 
230*, 16, 0, 220, 31, 0, 204, 35, 0, 209, 35, 0, 217, 34, 0, 176, 32, 0, 
221, 30, 127, 255, 255, 64, 125])
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: data: {'h_6': 32, 'h_7': 30, 
'h_4': 35, 'h_5': 34, 'h_2': 31, 'h_3': 35, 'h_1': 16, 't_6': 17.6, 't_2': 
22.0, 't_3': 20.4,* 't_1': 6551.0,* 'type': 'sensor_values', 't_7': 22.1, 
't_4': 20.9, 't_5': 21.7}
Oct 28 22:21:27 ripapi weewx[17385]: ws3000: packet: {'dateTime': 
1540758087, 'extraHumid6': 32, 'extraHumid7': 30, 'extraHumid4': 35, 
'extraHumid5': 34, 'extraHumid2': 31, 'extraHumid3': 35, 'extraHumid1': 16, 
'extraTemp6': 17.6, 'extraTemp7': 22.1, 'extraTemp4': 20.9, 'extraTemp5': 
21.7, 'extraTemp2': 22.0, 'extraTemp3': 20.4, 'usUnits': 17, *'extraTemp1': 
6551.0*}
Oct 28 22:21:27 ripapi weewx[17385]: engine: 2018-10-28 22:21:27 EET 
(1540758087) LOOP value 'extraTemp1' 6551.0 outside limits (-40.0, 40.0)


Spending a while trying to understand the read HEX values raw array, to me 
it looks like that as soon as temperature (in C) goes below 0, the variable 
flips back to max, being propably 6553(.).5 - being FF FF in HEX as can be 
seen above.


*Has WS3000 unit's exported values and/or WS3000 driver been earlier 
confirmed to work on sub-zero temperatures?*By a quick look I didn't find 
and indicator telling this is a sub-zero temperature except the fact that 
6500C is a bit hot for these sensors :D

*Would it be possible in to implement a 'sanity check' in the driver to 
convert values of let's say over 6000C back to negative range, something 
like*
IF
Temperature over 6000C 
THEN
Temperature = Temperature-6553,5



*Olivier, do you see this as a doable & reasonable solution? Do you already 
know where would be the good place in the driver to implement it? (and have 
you thought of putting the code to github or similar service ;)*

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

Re: [weewx-user] Re: WS-3000

2018-10-28 Thread olivier . guyotot

About the data transmission between the station and the sensors: I also 
have sensors that are quite far or behind thick walls, with rather poor 
signal reception. But this has never been a problem for me: the station 
simply stops displaying any value for the specific sensor, and I don't get 
any value in weewx, that's all.

So, if the values on your station are always correct but you get 6400 C in 
weewx, then the problem is most likely coming from the driver. I never 
tested the algorithm used to convert raw data to meaningful values with 
temperature around 0°C (or negative values), it could be incorrect.

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

Re: [weewx-user] Re: WS-3000

2018-10-28 Thread olivier . guyotot

For a), we'll hopefully find out more with debug=1. Haven't seen this with 
my own station so far.

For b) ... I am not sure yet. I am a noob at Python, there are still many 
things I don't fully understand properly, including error handling :(
All I can say for now is that:
- in _get_raw_data, the driver first tries to send a command to the station 
(_write_usb),  then it tries to read the results (_read_usb).
- one of those operation fails for some reason. Here again, we will 
hopefully know more with debug=1
- in the worst case scenario, (ie. we cannot figure out what's wrong and 
how to fix this), we could simply modify the driver to ignore the failure 
and hopefully prevent a complete crash.

But first question: did you increase the timeout *both* for read and write? 
What value are you using? I honestly don't know what would be reasonable 
value, 1000 might still not be enough on Raspberry. Back when I first 
investigated the issue for Raspberry, I came across a lot of links 
mentioning issues with USB devices on Raspberry. In one of those, you can 
see that somebody solved the issue by increasing the timeout to 1...

https://github.com/jim-easterbrook/pywws/issues/38

https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=53832

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

Re: [weewx-user] Re: WS-3000

2018-10-28 Thread RistoK

Everything's kind of working now, but 

a) Any clues why do I get temperature values of 6400 C (from outside 
sensor, temperature near 0C / 32F). Then later - it works again. Also this 
sensor seems to loose connection, it's the one with largest distance from 
base station. Is it possible that base station receives the signal 
incorrectly or does this have something to do with base station - weewx / 
ws3000 adapter connection?
After getting these values I added some MinMax values to StdQC..

[StdQC]

[[MinMax]]
extraTemp1 = -40,40,degree_C
extraTemp2 = 0,40,degree_C
extraTemp3 = 0,40,degree_C
extraTemp4 = 0,40,degree_C
extraTemp5 = 0,40,degree_C
extraTemp6 = 0,40,degree_C
extraTemp7 = 0,40,degree_C
extraTemp8 = 0,40,degree_C
extraHumid1 = 0,100
extraHumid2 = 0,100
extraHumid3 = 0,100
extraHumid4 = 0,100
extraHumid5 = 0,100
extraHumid6 = 0,100
extraHumid7 = 0,100
extraHumid8 = 0,100



b) Why does weewx crash every now and then: 
Oct 28 07:32:36 ripapi weewx[7963]: manager: Added record 2018-10-28 
07:32:00 EET (1540704720) to database 'weewx.sdb'
Oct 28 07:32:37 ripapi weewx[7963]: manager: Added record 2018-10-28 
07:32:00 EET (1540704720) to daily summary in 'weewx.sdb'
Oct 28 07:32:40 ripapi weewx[7963]: engine: Shutting down StdReport thread
Oct 28 07:32:47 ripapi weewx[7963]: cheetahgenerator: Generated 14 files 
for report StandardReport in 7.14 seconds
Oct 28 07:32:54 ripapi weewx[7963]: imagegenerator: Generated 20 images for 
StandardReport in 7.16 seconds
Oct 28 07:32:54 ripapi weewx[7963]: copygenerator: copied 0 files to 
/var/www/html/weewx
Oct 28 07:32:54 ripapi weewx[7963]: engine: Caught unrecoverable exception 
in engine:
Oct 28 07:32:54 ripapi weewx[7963]:   'int' object is not callable
Oct 28 07:32:54 ripapi weewx[7963]:   Traceback (most recent call 
last):
Oct 28 07:32:54 ripapi weewx[7963]: File 
"/usr/share/weewx/weewx/engine.py", line 877, in main
Oct 28 07:32:54 ripapi weewx[7963]:   engine.run()
Oct 28 07:32:54 ripapi weewx[7963]: File 
"/usr/share/weewx/weewx/engine.py", line 188, in run
Oct 28 07:32:54 ripapi weewx[7963]:   for packet in 
self.console.genLoopPackets():
Oct 28 07:32:54 ripapi weewx[7963]: File 
"/usr/share/weewx/user/ws3000.py", line 292, in genLoopPackets
Oct 28 07:32:54 ripapi weewx[7963]:   loop_packet = 
self.getCurrentValues()
Oct 28 07:32:54 ripapi weewx[7963]: File 
"/usr/share/weewx/user/ws3000.py", line 267, in getCurrentValues
Oct 28 07:32:54 ripapi weewx[7963]:   raw_data = 
self._get_raw_data(read_sensors_command)
Oct 28 07:32:54 ripapi weewx[7963]: File 
"/usr/share/weewx/user/ws3000.py", line 359, in _get_raw_data
Oct 28 07:32:54 ripapi weewx[7963]:   raise 
weewx.IO_ERROR("Error while fetching " + self._get_cmd_name(hex_command))
Oct 28 07:32:54 ripapi weewx[7963]:   TypeError: 'int' object is 
not callable
Oct 28 07:32:54 ripapi weewx[7963]:   Exiting.

Added now debug=1 to learn more..

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

Re: [weewx-user] Re: WS-3000

2018-10-26 Thread olivier . guyotot

Glad to hear that you got it working! And thanks for howto, much 
appreciated. That's really something that I should have done long ago, but 
I never found the time/motivation to do it. 

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

Re: [weewx-user] Re: WS-3000

2018-10-26 Thread Risto H. Kurppa

Hi,

No, I didn't try that, didn't realize that would also apply.
So now I have a fresh Stretch install and will next try to set everything
up.
I'll try to collect the required steps here..
https://etherpad.net/p/weewx_raspi  (feel free to help to turn it to a
step-by-step tutorial..)

r


On Fri, Oct 26, 2018 at 4:29 PM  wrote:

> Just to clarify, I was referring to the following post:
>
> - edit the file ws3000.py
> - on lines 316 (return self.device.write(self.OUT_ep, data=buf, timeout=
> 100)) and 320 (buf = self.device.read(self.IN_ep, self.packet_size, 100))
> increase the last parameter of the device.write and device.read function
> to 1000 instead of 100.
> - restart weewx
>
> --
> 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/qDe-El03C2k/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi

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

[weewx-user] Re: WS-3000

2018-10-26 Thread olivier . guyotot

Just to clarify, I was referring to the following post:

- edit the file ws3000.py
- on lines 316 (return self.device.write(self.OUT_ep, data=buf, timeout=100)) 
and 320 (buf = self.device.read(self.IN_ep, self.packet_size, 100)) 
increase the last parameter of the device.write and device.read function to 
1000 instead of 100.
- restart weewx

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

[weewx-user] Re: WS-3000

2018-10-26 Thread olivier . guyotot

Did you do the change suggested in my post from Aug 29th?

On RPi, you need to increase the usb timeout. I actually updated my code, 
but I never uploaded the modified files... so unless you manually made the 
change, you probably still have a 100 ms timeout, which isn't enough on RPi.

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

[weewx-user] Re: WS-3000

2018-10-26 Thread RistoK

Thanks for your input!!

I updated my Raspbian to Jessie (took about 24 hours or so :D) and log 
below tells where I'm at now. 
It's still possible that there are issues with Python packages. Still using 
the weewx.deb that requires python-usb from package management. It's 
possible that compiling weewx from source is the next option.. 

And now that I checked Debian releaseses I see that I'm so behind.. I 
thought Jessie was the latest stable but I see it's Stretch already.. -> 
upgrading/fresh install to that next..

Oct 26 15:07:23 ripapi weewx[17576]: engine: Starting up weewx version 3.8.2
Oct 26 15:07:23 ripapi weewx[17576]: engine: Station does not support 
reading the time
Oct 26 15:07:23 ripapi weewx[17576]: engine: Starting main packet loop.
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: sending request for 
sensor_values
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: write: 7b 03 40 7d (len=4)
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: reading results...
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: reading 64 bytes
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: read: 7b 00 25 56 00 da 23 00 
cc 28 00 cd 27 00 dc 26 00 b4 28 00 db 27 7f ff ff 40 7d 00 f1 25 c4 05 80 
fc c5 8a 4e 14 2f 2c d1 d7 e7 70 9c 7b e5 e1 3e 17 5f 4e 19 72 97 5e 02 1a 
0e 52 33 f6 80 ce (len=64)
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: extracting values for 
sensor_values
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: raw: array('B', [123, 0, 37, 
86, 0, 218, 35, 0, 204, 40, 0, 205, 39, 0, 220, 38, 0, 180, 40, 0, 219, 39, 
127, 255, 255, 64, 125])
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: data: {'h_6': 40, 'h_7': 39, 
'h_4': 39, 'h_5': 38, 'h_2': 35, 'h_3': 40, 'h_1': 86, 't_6': 18.0, 't_2': 
21.8, 't_3': 20.4, 't_1': 3.7, 'type': 'sensor_values', 't_7': 21.9, 't_4': 
20.5, 't_5': 22.0}
Oct 26 15:07:23 ripapi weewx[17576]: ws3000: packet: {'dateTime': 
1540555644, 'extraHumid6': 40, 'extraHumid7': 39, 'extraHumid4': 39, 
'extraHumid5': 38, 'extraHumid2': 35, 'extraHumid3': 40, 'extraHumid1': 86, 
'extraTemp6': 18.0, 'extraTemp7': 21.9, 'extraTemp4': 20.5, 'extraTemp5': 
22.0, 'extraTemp2': 21.8, 'extraTemp3': 20.4, 'usUnits': 17, 'extraTemp1': 
3.7}
Oct 26 15:07:53 ripapi weewx[17576]: ws3000: sending request for 
sensor_values
Oct 26 15:07:53 ripapi weewx[17576]: ws3000: write: 7b 03 40 7d (len=4)
Oct 26 15:07:53 ripapi weewx[17576]: engine: Main loop exiting. Shutting 
engine down.
Oct 26 15:07:53 ripapi weewx[17576]: engine: Caught unrecoverable exception 
in engine:
Oct 26 15:07:53 ripapi weewx[17576]:   'int' object is not callable
Oct 26 15:07:53 ripapi weewx[17576]:   Traceback (most recent call 
last):
Oct 26 15:07:53 ripapi weewx[17576]: File 
"/usr/share/weewx/weewx/engine.py", line 877, in main
Oct 26 15:07:53 ripapi weewx[17576]:   engine.run()
Oct 26 15:07:53 ripapi weewx[17576]: File 
"/usr/share/weewx/weewx/engine.py", line 188, in run
Oct 26 15:07:53 ripapi weewx[17576]:   for packet in 
self.console.genLoopPackets():
Oct 26 15:07:53 ripapi weewx[17576]: File 
"/usr/share/weewx/user/ws3000.py", line 292, in genLoopPackets
Oct 26 15:07:53 ripapi weewx[17576]:   loop_packet = 
self.getCurrentValues()
Oct 26 15:07:53 ripapi weewx[17576]: File 
"/usr/share/weewx/user/ws3000.py", line 267, in getCurrentValues
Oct 26 15:07:53 ripapi weewx[17576]:   raw_data = 
self._get_raw_data(read_sensors_command)
Oct 26 15:07:53 ripapi weewx[17576]: File 
"/usr/share/weewx/user/ws3000.py", line 359, in _get_raw_data
Oct 26 15:07:53 ripapi weewx[17576]:   raise 
weewx.IO_ERROR("Error while fetching " + self._get_cmd_name(hex_command))
Oct 26 15:07:53 ripapi weewx[17576]:   TypeError: 'int' object is 
not callable
Oct 26 15:07:53 ripapi weewx[17576]:   Exiting.

-> Can you point out what's possibly wrong?

usbtest.py:

rhk@ripapi ~ $ sudo python usbtest.py
Starting tests...
ws3000_write: entry
Detecting device...
Device found
Sending control packet
Sending command:  [123, 65, 64, 125, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
An error occurred: (, USBError(110, u'Operation 
timed out'), )
Traceback (most recent call last):
  File "usbtest.py", line 54, in ws3000_write
data = device.read(0x82, 64, 100)
  File "/usr/local/lib/python2.7/dist-packages/usb/core.py", line 988, in 
read
self.__get_timeout(timeout))
  File "/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py", 
line 851, in intr_read
timeout)
  File "/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py", 
line 936, in __read
_check(retval)
  File "/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py", 
line 595, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
USBError: [Errno 110] Operation timed out
Tests completed
r

[weewx-user] Re: WS-3000

2018-10-25 Thread olivier . guyotot

I completely forgot some notes I took when I tested the install on a RPi 
last time, just found them now:

1. install Raspbian
> 2. install requirements: apt-get install libjpeg-dev libtiff5-dev 
> zlib1g-dev libfreetype6-dev liblcms2-dev libwebp-dev libharfbuzz-dev 
> libfribidi-dev tcl8.6-dev tk8.6-dev python-tk
> 3. copy requirements.txt, weewx.tar.gz and ws3000*.py to the RPi
> wget https://bootstrap.pypa.io/get-pip.py
> python get-pip.py
> pip install -r requirements.txt


So to update pip on your system, you can use:
wget https://bootstrap.pypa.io/get-pip.py
python get-pip.py


Then try again to install the missing python requirements, and most 
importantly, update pyusb.

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

[weewx-user] Re: WS-3000

2018-10-25 Thread olivier . guyotot


Hello,

First regarding pyephem: you can probably safely ignore this. Here is a 
quote from the weewx documentation:

# optional for extended almanac information:sudo pip install pyephem

So unless you need extended almanac information, skip it.

Then, regarding the usb.core issue. This is because the packages installed 
by apt are prehistoric ones, so you are probably  still using pyusb 0.4. 
You can check with
pip list --outdated

to check just how far behind you are... And by the way, the errors that you 
are getting when using pip to install packages are probably caused by the 
fact that your version of pip must also be outdated. Try to upgrade it 
first (but given your issues, not sure that you can do it simply with pip 
install --upgrade pip).

The solution is NOT to edit the driver, but simply to upgrade pyusb:
pip install --upgrade pyusb

Let's see if you still get some errors after this.

NOTE: in general, I always find that it is best to install the python 
packages using pip rather than to rely on the distribution packages. I 
would remove python-configobj python-cheetah python-serial python-usb and 
reinstall all the modules using pip: I don't think that mixing the two 
installation methods is really safe: there is always the risk that one 
might break what the other did.
Of course, this will break the dependencies for the weewx package. Which is 
why it is also better to install it using the setup tool instead of using 
the deb package. Or, if you want to stick with deb, try to use a much more 
recent distribution.

NOTE2: if you are working with a new database, you don't need to upgrade 
the database schema. So my suggestion is that once you have confirmed that 
the driver is working properly, delete the existing database to let weewx 
create a new one from scratch with the appropriate schema.

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

[weewx-user] Re: WS-3000

2018-10-25 Thread olivier . guyotot

Hello,

First regarding pyephem: you can probably safely ignore this. Here is a 
quote from the weewx documentation:

# optional for extended almanac information:sudo pip install pyephem

So unless you need extended almanac information, skip it.

Then, regarding the usb.core issue. This is because the packages installed 
by apt are prehistoric ones, so you are probably  still using pyusb 0.4. 
You can check with
pip list --outdated

to check just how far behind you are... And by the way, the errors that you 
are getting when using pip to install packages are probably caused by the 
fact that your version of pip must also be outdated. Try to upgrade it 
first (but given your issues, not sure that you can do it simply with pip 
install --upgrade pip).

The solution is NOT to edit the driver, but simply to upgrade pyusb:
pip install --upgrade pyusb

Let's see if you still get some errors after this.

NOTE: in general, I always find that it is best to install the python 
packages using pip rather than to rely on the distribution packages. I 
would remove python-configobj python-cheetah python-serial python-usb and 
reinstall all the modules using pip: I don't think that mixing the two 
installation methods is really safe: there is always the risk that one 
might break what the other did.

NOTE2: if you are working with a new database, you don't need to upgrade 
the database schema. So my suggestion is that once you have confirmed that 
the driver is working properly, delete the existing database to let weewx 
create a new one from scratch with the appropriate schema.

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

[weewx-user] Re: WS-3000

2018-10-24 Thread RistoK

Hi there,

As this is pretty much the only WS3000 thread on this list, I dare to reply 
to the same thread.
So I bought MISOL WS-HP3001-8MZ 5 channel wireless station  + 2 extra 
sensors = 7 in total.

First of all, Thanks Olivier for all your work regarding the WS3000 driver 
& instructions!!! While buying the station I was unsure if it would be 
possible to connect to RasPi - but looks now very promising due to this 
thread. I hope also others will find this thread and allow them to 
configure RasPi for WS3000 data collection :) (keywords for anyone looking 
for info: linux ubuntu raspberry raspbian debian ws3000 ws3001 hp3000 
hp3001 misol weather station) 
That's why I wrote this here in some kind of fuzzy tutorial format:

So as said, 'looks promising', but not 100% there..
I have linux background, but this is the first time I'm using weewx, so 
something to learn there, for sure.

I have 1st gen RasPi with Raspbian:
rhk@ripapi ~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 7.11 (wheezy)
Release:7.11
Codename:   wheezy
rhk@ripapi ~ $

dmesg shows the connected weather monitor:
[ 1907.168919] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[ 1907.273512] usb 1-1.3: New USB device found, idVendor=0483, 
idProduct=5750
[ 1907.273553] usb 1-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 1907.273574] usb 1-1.3: Product: By viewtool
[ 1907.273591] usb 1-1.3: Manufacturer: MyUSB_HID
[ 1907.273608] usb 1-1.3: SerialNumber: 8B6997A71132
[ 1907.291671] hid-generic 0003:0483:5750.0001: hiddev0,hidraw0: USB HID 
v1.10 Device [MyUSB_HID By viewtool] on usb-2098.usb-1.3/input0

- Downloaded weewx_3.8.2-1_all.deb from weewx website. 
- Install with sudo dpkg -i weewx_3.8.2-1_all.deb
- As that didn't work, installed required dependencies: sudo apt-get 
install apache python-configobj python-cheetah python-serial python-usb
- reinstall with sudo dpkg -i weewx_3.8.2-1_all.deb - initially configured 
it to use 'simulator' driver

The weewx web interface seemed to work OK and I got some simulated values 
there, at http://192.168.1.6/html/weewx (note, change localhost to your 
RasPi IP, first check with ifconfig)

- Then off to configure the WS3000 driver:
- I downloaded the ws3000DataService.py  ws3000Extensions.py  ws3000.py 
files from this thread and placed them to /usr/share/weewx/user (NOTE! 
Installation dir with .deb seems different from what is described above in 
Olivier's instructions).
- run this, as instructed above:
rhk@ripapi ~ $ echo "configobj
> pyephem
> pyserial
> pyusb
> willow
> pillow
> cheetah
> Image
> Django==1.11" > requirements.txt
rhk@ripapi ~ $ pip install -r requirements.txt
Requirement already satisfied (use --upgrade to upgrade): configobj in 
/usr/lib/python2.7/dist-packages (from -r requirements.txt (line 1))
Downloading/unpacking pyephem (from -r requirements.txt (line 2))
  Cannot fetch index base URL http://pypi.python.org/simple/
  Could not find any downloads that satisfy the requirement pyephem (from 
-r requirements.txt (line 2))
No distributions at all found for pyephem (from -r requirements.txt (line 
2))
Storing complete log in /home/rhk/.pip/pip.log
rhk@ripapi ~ $
So removed pyephem from the list (-> possible issue here, how does the 
missing ephem impact??) and successful rerun.

Then 
rhk@ripapi ~ $ sudo pip install pyephem
[sudo] password for rhk:
Downloading/unpacking pyephem
  Cannot fetch index base URL http://pypi.python.org/simple/
  Could not find any downloads that satisfy the requirement pyephem
No distributions at all found for pyephem
Storing complete log in /root/.pip/pip.log
rhk@ripapi ~ $
 (I can see it listed in the mentioned url, but doesn't install :(


Then I tried to list drivers but ws3000 line was somehow corrupted 
reporting about missing core or something. So in the ws3000.py file I 
removed these lines: 
import usb.core
import usb.util
as (not with very competent with Python..) I saw that import usb was 
already there. That seemed to help weewx to identify the drivers:

rhk@ripapi /usr/share/weewx $ ./wee_config --list-drivers
Module name  Driver nameVersion  Status
  user.ws3000  WS3000 0.1
  weewx.drivers.acuriteAcuRite0.24
  weewx.drivers.cc3000 CC3000 0.19
  weewx.drivers.fousb  FineOffsetUSB  1.9
  weewx.drivers.simulator  Simulator  3.0
  weewx.drivers.te923  TE923  0.24
  weewx.drivers.ultimeter  Ultimeter  0.18
  weewx.drivers.vantageVantage3.0.11
  weewx.drivers.wmr100 WMR100 3.3.3
  weewx.drivers.wmr200 WMR200 3.3.5
  weewx.drivers.wmr300 WMR300 0.19rc6
  weewx.drivers.wmr9x8 WMR9x8 3.2.2
  weewx.drivers.ws1WS10.25
  weewx.drivers.ws23xx WS23xx 0.27
  weewx.drivers.ws28xx WS28xx 0.35


Then reconfiguring weewx to use WS3000:
rhk@ripapi /usr/share/weewx $ .

[weewx-user] Re: WS-3000

2018-08-29 Thread olivier . guyotot

It would also be helpful to have the complete log, from the moment weewx 
started until you run into the error.

But in the meantime, I did some tests on Raspbian and I indeed ran into an 
error, caused by a timeout. So here is a possible solution for you:
- edit the file ws3000.py
- on lines 316 (return self.device.write(self.OUT_ep, data=buf, timeout=100)) 
and 320 (buf = self.device.read(self.IN_ep, self.packet_size, 100)) 
increase the last parameter of the device.write and device.read function to 
1000 instead of 100.
- restart weewx

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

[weewx-user] Re: WS-3000

2018-08-29 Thread olivier . guyotot

Also, which raspberry distribution are you using and how did you setup 
python are the requirements? I'll try to test here with a similar setup.

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

[weewx-user] Re: WS-3000

Can you please provide the output of:
lsusb

Also, before starting weewx, make sure to delete the existing database:
rm archive/weewx.sdb

And although it probably doesn't make a lot of difference, try to start 
weewx with the following command for now, instead of using the service:
./bin/weewxd weewx.conf



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

[weewx-user] Re: WS-3000

2018-08-28 Thread vince

On Tuesday, August 28, 2018 at 1:56:44 PM UTC-7, Peter Grefges wrote:
>
> Another log i got was the following:
>
> raspberrypi weewx[461]: manager: Replace failed for database weewx.sdb: 
> attempt to write a readonly database
>


Difficult to help with you not telling us what command you ran, and what 
user you tried to run it as

Since you're a new pi user, it is likely you want to preface whatever 
command you ran with "sudo" so it runs with privileges...

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

[weewx-user] Re: WS-3000

2018-08-28 Thread Peter Grefges

Another log i got was the following:

raspberrypi weewx[461]: manager: Replace failed for database weewx.sdb: attempt 
to write a readonly database

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

[weewx-user] Re: WS-3000

2018-08-28 Thread Peter Grefges

Thank you very much for your help, this is really awesome!

I just made the installation with you manual. 



At the moment i get the following status: 


root@raspberrypi:~# sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
root@raspberrypi:~# sudo tail -f /var/log/syslog
Aug 28 22:19:57 raspberrypi weewx[461]: File 
"/home/weewx/bin/weewx/engine.py", line 188, in run
Aug 28 22:19:57 raspberrypi weewx[461]:   for packet in 
self.console.genLoopPackets():
Aug 28 22:19:57 raspberrypi weewx[461]: File 
"/home/weewx/bin/user/ws3000.py", line 292, in genLoopPackets
Aug 28 22:19:57 raspberrypi weewx[461]:   loop_packet = 
self.getCurrentValues()
Aug 28 22:19:57 raspberrypi weewx[461]: File 
"/home/weewx/bin/user/ws3000.py", line 267, in getCurrentValues
Aug 28 22:19:57 raspberrypi weewx[461]:   raw_data = 
self._get_raw_data(read_sensors_command)
Aug 28 22:19:57 raspberrypi weewx[461]: File 
"/home/weewx/bin/user/ws3000.py", line 359, in _get_raw_data
Aug 28 22:19:57 raspberrypi weewx[461]:   raise 
weewx.IO_ERROR("Error while fetching " + self._get_cmd_name(hex_command))
Aug 28 22:19:57 raspberrypi weewx[461]:   TypeError: 'int' object 
is not callable
Aug 28 22:19:57 raspberrypi weewx[461]:   Exiting.



it seems that there is still a small problem. The index.html file is still 
the one from the simulator.




The sensor map in the config file i made like this: 
[[sensor_map]]
inTemp = t_1
outTemp = t_5
extraTemp1 = 
extraTemp2 = t_2
extraTemp3 = t_3
extraTemp4 = t_4
extraTemp5 = 
extraTemp6 = 
extraTemp7 = 
extraTemp8 = 
inHumidity = h_1
outHumidity = h_5
extraHumid1 = 
extraHumid2 = h_2
extraHumid3 = h_3
extraHumid4 = h_4
extraHumid5 = 
extraHumid6 = 
extraHumid7 = 
extraHumid8 = 

My sensor number 1 is the main indoor sensor and my outdoor sensor is 
sensor number 5.


Peter

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

[weewx-user] Re: WS-3000

2018-08-28 Thread gjr80

My apologies, you are correct. I only looked on the driver file ws300.py which 
mentions the need to modify the schema. wee_config picks up the modified schema 
from ws3000Extensions.py and when WeeWX starts up provided there is no database 
one will be created with the modified schema. Key point being there needs to be 
no existing database.

My previous post should be ignored.

Gary

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

[weewx-user] Re: WS-3000

Considering the above, it may be a good idea to run
rm archive/weewx.sdb
before starting weewxd for the first time after deploying the driver and 
doing the configuration... (that's assuming that you don't need or want to 
keep any of the previous data, if any).

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

[weewx-user] Re: WS-3000

True, but when I tested the steps that I outlined above I ran into a rather 
nice surprise: the newly created DB did contain all the extra columns. I 
assume that weex_config (or weewxd when it create the db) automatically 
applied the schema specified in ws3000Extensions.py.
For my own setup I had to manually customize the database schema, but I had 
an already existing database. It looks like this will be done automatically 
for Peter if he starts with a new database, so all he really has to 
customize to use the data from his 5 sensors are the reports.

Note that the suggested sensor_map configuration I provided above is just 
to quickly and simply make use of 2 sensors. In the long run, you may want 
to consider using a different sensor map (currently, sensors 3 to 5 will be 
stored in the columns extraTemp3-5 and extraHumid3-5 while extraTemp1-2 and 
extraHumid1-2 should be empty).

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

[weewx-user] Re: WS-3000

2018-08-28 Thread gjr80

Hi,

Keep in mind that only extraTemp1, extraTemp2, extraTemp3, extraHumid1 and 
extraHumid2 are included in the default WeeWX database schema (refer to the 
Archive 
Types appendix  in the 
Customization 
Guide ); in other words these are 
the only extraTempx and extraHumidx obs that will be saved to database. You 
can certainly still use the others, but you will only be able to use them 
with the $current tag in a WeeWX report. If you want to use these 
additional obs in some form of aggregate eg minimums, maximums, averages 
etc in a WeeWX report you will need to save them to database. This is 
easily done using a custom schema, refer to the section Adding a new type 
to the archive database 
 in the 
Customization Guide.

Gary

On Tuesday, 28 August 2018 18:39:18 UTC+10, olivier...@gmail.com wrote:
>
> There is a small mistake in the sensor_map above. It should be:
> inHumidity = h_1
> outHumidity = h_2
>
>
> instead of:
> inHumidity = h_1
> outHumidity = h_1
>
>
>

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

[weewx-user] Re: WS-3000

There is a small mistake in the sensor_map above. It should be:
inHumidity = h_1
outHumidity = h_2


instead of:
inHumidity = h_1
outHumidity = h_1


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

[weewx-user] Re: WS-3000

Here is a step by step instruction of the complete installation and setup:

# Install weewx
tar xvfz weewx-3.8.2.tar.gz
cd weewx-3.8.2
./setup.py build
sudo ./setup.py install
For this last step, use the simulator driver since ws3000 is not yet 
available.

=> weewx is installed by default in /home/weewx. Update the path in the 
following instructions is this is not the case.
cp ws3000.py /home/weewx/bin/user/
cp ws3000Extensions.py /home/weewx/bin/user/

Make sure that the ws3000 is correctly detected:
cd /home/weewx
./bin/wee_config --list-drivers
Module name  Driver nameVersion  Status   
  user.ws3000  WS3000 0.1   
  weewx.drivers.acuriteAcuRite0.24  
  weewx.drivers.cc3000 CC3000 0.19 
  <...>

Then run the following command to reconfigure weewx with the correct driver:
./bin/wee_config --reconfigure

Finally edit weewx.conf, and change the sensor_map in the WS3000 section 
like this:
[WS3000]
<...>
[[sensor_map]]
inTemp = t_1
outTemp = t_2
extraTemp1 =
extraTemp2 =
extraTemp3 = t_3
extraTemp4 = t_4
extraTemp5 = t_5
extraTemp6 = t_6
extraTemp7 = t_7
extraTemp8 = t_8
inHumidity = h_1
outHumidity = h_1
extraHumid1 =
extraHumid2 =
extraHumid3 = h_3
extraHumid4 = h_4
extraHumid5 = h_5
extraHumid6 = h_6
extraHumid7 = h_7
extraHumid8 = h_8

=> this basically tells weewx to store the temperature and humidity from 
the first 2 sensors (t_1, t_2, h_1 and h_2) into the inTemp, ouTemp, 
inHumidity and outHumidity columns of the database. Everything else will go 
to the extraTempx and extraHumidx columns (you must read the map from right 
to left).
The existing reports will pick up the values from inTemp and ouTemp by 
default. If you want to include the other columns in your reports, you will 
have to customize them.

NB: If you want to use metric units in the database, you can also change 
the following section:
[StdConvert]
<...>
target_unit = METRICWX

Hope this helps.

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

[weewx-user] Re: WS-3000

2018-08-25 Thread Peter Grefges

I have 5 sensors, but for a first start 2 would be fine (1x outdoor, 1x indoor).

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

[weewx-user] Re: WS-3000

2018-08-22 Thread olivier . guyotot

OK. How many sensors do you have?
If you are OK with using just 2 for now, the setup can still be pretty 
simple (I'll explain how). What will become more complex is to store and 
display the values for any additional sensor.


On Wednesday, 22 August 2018 20:02:31 UTC+2, Peter Grefges wrote:
>
> Thanks for your fast reply and help.
> I will try it, but it fear that it is too difficult for me. I just bought 
> the raspberry Pi for the WS3000 weather station and i am a absolute 
> beginner. I thought that everything would have been easier.
>
> So installation of weewx is no problem for me, and the simulator of weewx 
> is working, but changing databases or other things will get difficult 
> because I just do not have the overview what I am actually doing there...
>

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

[weewx-user] Re: WS-3000

2018-08-22 Thread Peter Grefges

Thanks for your fast reply and help.
I will try it, but it fear that it is too difficult for me. I just bought the 
raspberry Pi for the WS3000 weather station and i am a absolute beginner. I 
thought that everything would have been easier.

So installation of weewx is no problem for me, and the simulator of weewx is 
working, but changing databases or other things will get difficult because I 
just do not have the overview what I am actually doing there...

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

[weewx-user] Re: WS-3000

2018-08-19 Thread olivier . guyotot

Hello Peter,

It has been some time since I worked on this, I am not 100% sure to 
remember everything correctly and some instructions might be out-dated. All 
I can say for sure is that I can currently get the data from the WS3000 
without any problem. So here is what I think I did...

First of all, forget the 'usb' version of weewx. I am downloading the 
tar.gz from http://www.weewx.com/downloads/ and doing the install using 
setup.py as per the instructions here (except for installing the 
requirements):
http://www.weewx.com/docs/setup.htm

For the prerequisites, I simply do (just to create a requirement file that 
I can reuse later):
echo "configobj
pyephem
pyserial
pyusb
willow
pillow
cheetah
Image
Django==1.11" > requirements.txt

And then:
pip install -r requirements.txt

Download weewx and run (customize home in setup.cfg if you want to change 
the default location):
tar xvfz weewx-X.Y.Z.tar.gz
cd weewx-X.Y.Z
./setup.py build
sudo ./setup.py install

=> at this point, weewx should be installed and working (standard install, 
you can test the simulator). Now you need to configure it for the HP3000. 
For this, I am using my own driver. It might not be very well written, but 
it seems to be doing the trick correctly.

But first some IMPORTANT notes:

1. I am using the WS3000 as a secondary station, and I am merging the data 
with my primary station using a custom data service. This is optional of 
course, and my data service is probably not going to work for anybody but 
me: consider it as a poor example and if you would like to do the same make 
sure to do all the required changes to ws3000DataService.py.

2. Even if you use the WS3000 on its own, you will probably need to make a 
few changes and think carefully about how you want to store the data in the 
database: you have up to 8 sensors, and by default weewx has only 3 columns 
for temperature and 2 for humidity. So you will probably have to modify the 
database schema anyway. Read 
http://www.weewx.com/docs/customizing.htm#archive_database carefully.
What my driver is doing by default is storing all the data from the WS3000 
in the extraTemp* and extraHumid* columns, you may want to change this 
(this can be done in the configuration file). At first you could try to use 
the default and existing database columns and only try to get the data from 
1 sensor, just to confirm that your installation is working properly.

To install my WS3000 driver:

- copy ws3000.py, ws3000Extensions.py, ws3000DataService.py (optional) to 
/bin/user
- update the database schema to add the extra columns (as defined in 
ws3000Extensions.py)
- add the following section to your configuration file (doing the 
configuration using wee_config should also work I think. Check if 
user.ws3000 is listed by./bin/wee_config --list-drivers)

[WS3000]
# This section is for the Ambient Weather WS3000

# The driver to use
driver = user.ws3000

# The station model, e.g., WS3000, WS3000-X3, WS3000-X5 (all the 
same...)
model = WS3000

# [Optional] The interval at which loop packets should be generated by the 
driver
# Default is 10
#loop_interval = 15

# [Optional] USB vendor ID and product ID, as returned by lsusb. Only 
required if the device
# cannot be found with the default values
# Defaults are 0x0483 and 0x5750
#vendor_id = 0x0483
#product_id = 0x5750

# [Optional] By default, all the sensor values are stored in the extraTemp 
or extraHumid columns. The assumption here is
# that the WS3000 is used as a secondary station to enhance another 
existing station with additional
# temperature sensors, and that the usual inTemp, outTemp, etc. are already 
used by the primary station.
# NOTE: of course, the database schema must be modified to include the 
missing columns.
#[[sensor_map]]
#extraTemp1 = t_1
#extraTemp2 = t_2
#extraTemp3 = t_3
#extraTemp4 = t_4
#extraTemp5 = t_5
#extraTemp6 = t_6
#extraTemp7 = t_7
#extraTemp8 = t_8
#extraHumid1 = h_1
#extraHumid2 = h_2
#extraHumid3 = h_3
#extraHumid4 = h_4
#extraHumid5 = h_5
#extraHumid6 = h_6
#extraHumid7 = h_7
#extraHumid8 = h_8

And add the following line to the DataBinings section:
[DataBindings]
[[wx_binding]]
...
schema = user.ws3000Extensions.ws3000Schema

I hope that this help. It's far from a step by step install guide, but it 
is the best I can do on a short notice... And because of the number of 
temp/humidity sensors, some level of customization will be required in any 
case, both to store the data and to generate the reports.

On Sunday, 19 August 2018 13:31:57 UTC+2, Peter Grefges wrote:
>
> Hi, 
>
> I also have the HP3000 weather station and I spent serveral hours to get 
> it to run with weewx, but without sucess :(
>
> I first found the manuals on github for the HP3000, but it actually does 
> not work.
> Now after another 5 hours of try n error i found this topic. 
>
> @olivier: you posted serveral files here in this topic

[weewx-user] Re: WS-3000

2018-08-19 Thread Peter Grefges

Hi, 

I also have the HP3000 weather station and I spent serveral hours to get it 
to run with weewx, but without sucess :(

I first found the manuals on github for the HP3000, but it actually does 
not work.
Now after another 5 hours of try n error i found this topic. 

@olivier: you posted serveral files here in this topic with drivers and so 
on. Actually i am a Raspberry beginner and I now do not know what to do 
with these drivers and files. Where do I have to put them, which commands 
do I have to execute?
Which installation method for weewx I have to use? 

At the moment I have installed it like on the github homepage written:
git clone https://github.com/weewx/weewx
cd weewx
git checkout usb
./setup.py install

I have now folders from weewx at /home/weewx and there also the html site 
is created, at /home/weewx/public_html
But I also have a weewx folder at /root/weewx


For me as a raspberry beginner it is just overwhelming, there are too much 
ways to realise one and the same thing...

Maybe somebody can help me? That would be really nice!

best regards

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

[weewx-user] Re: WS-3000

One last comment. I modified the hp3000 driver to get weewx to work with my 
WS-3000. Somebody more competent than I am will have to do a complete 
review, but here is what I did (more or less):
- changed the write function. The driver was using the one provided 
in usbhid_pyusb1.py, which is always using self.dev.ctrl_transfer (control 
transfer instead of an interrupt transfer).
- changed the read function (order of the parameters seemed incorrect).
- modified the genLoopPackets a bit, to avoid trying to read data when no 
command has been sent.
- modified the send_sequence, to just send 0x03 commands and nothing else.

With those modifications, weewx is now working fine with my WS-3000. But 
what I did is only dirty patching to get things working: it helps to show 
what was wrong, but this cannot be simply reused as is...

The modified driver is attached.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
#!/usr/bin/env python
# Copyright 2016 Matthew Wall
# Distributed under the terms of the GNU Public License (GPLv3)

"""
Collect data from the HP-3000 console via USB.

  Ambient Weather WS-3000-X5
  Ambient Weather WS-3000-X3

The HP-3000 supports up to 8 remote temperature/humidity sensors.  The console
has a 3"x4" TFT color display, with graph and room for 5 sensor displays.  The
sensor display regions can cycle through different sensors when more than 5
sensors are connected.

Every configuration option in the console can be modified via software.  These
options includes:

 - archive interval
 - date/time
 - date/time format
 - timezone
 - which sensors should be displayed in the 5 display regions
 - horizontal graph axis scaling
 - vertical graph axis
 - calibration for temperature/humidity from each sensor
 - alarms
 - historical data

Historical data are saved to the (optional) microSD card.  If no card is
installed, no data are retained.

Each sensor has its own display of temperature and humidity.

Each sensor is identified by channel number.  The channel number is set using
DIP switches on each sensor.  The DIP switches also determine which units will
be displayed in each sensor.

There are 4 two-position DIP switches.  DIP 4 determines units: 0=F 1=C
DIP 1-3 determine which of 8 channels is selected.

Each sensor uses 2 AA batteries.  Nominal battery life is 1 year.

The console uses 5V DC from an AC/DC transformer.

Data from sensors are received every 60 seconds.

Dewpoint and heatindex are calculated within the console.

Temperature sensors measure to +/- 2 degree F

Humidity sensors measure to +/- 5 %

Calibrations are applied in the console, so the values received from the
console are calibrated.  Calculations in the console are performed in degree C.

The console has a radio controlled clock.  During RCC reception, no data will
be transmitted.  If no RCC is received, attempt will be made every two hours
until successful.

This driver was developed without any assistance from Ambient Weather (the
vendor) or Fine Offset (the manufacturer).

===
Messages from console

The console sends data in 64-byte chunks.  It looks like the console reuses a
buffer, because each message shorter than the previous contains bytes from the
previous message.  The byte sequence 0x40 0x7d indicates end of data within a
buffer.

Many of the console messages correspond with the control messages sent from
the host.

configuration state (30 bytes)
00 7b
01 00 graph type
02 48 graph hours
03 01 time format
04 00 date format
05 00 dst
06 fb timezone
07 01 units
08 00
09 00
0a 00
0b 07 area1
0c 00
0d 00
0e 00
0f 00 area2
10 00
11 00
12 00
13 00 area3
14 00
15 00
16 00
17 00 area4
18 00
19 00
1a 00
1b 00 area5
1c 40
1d 7d

interval (4 bytes)
00 7b
01 05 interval in minutes
02 40
03 7d

unknown (9 bytes)
00 7b
01 01
02 01
03 00
04 00
05 00
06 00
07 40
08 7d

current data (27 bytes)
00 7b
01 00 ch1 temp MSB
02 eb ch1 temp LSBt1 = (MSB * 256 + LSB) / 10.0
03 25 ch1 hum h1 = hum
04 7f ch2 temp MSB
05 ff ch2 temp LSB
06 ff ch2 hum
07 7f ch3 temp MSB
08 ff ch3 temp LSB
09 ff ch3 hum
0a 7f ch4 temp MSB
0b ff ch4 temp LSB
0c ff ch4 hum
0d 7f ch5 temp MSB
0e ff ch5 temp LSB
0f ff ch5 hum
10 7f ch6 temp MSB
11 ff ch6 temp LSB
12 ff ch6 hum
13 7f ch7 temp MSB
14 ff ch7 temp LSB
15 ff ch7 hum
16 7f ch8 temp MSB
17 ff ch8 temp LSB
18 ff ch8 hum
19 40
1a 7d

calibration (27 bytes)
00 7b
01 00 ch1 temp MSB
02 00 ch1 temp LSBtcal1 = (MSB * 256 + LSB) / 10.0
03 00 ch1 hum hcal1 = hum
04 00 ch2 temp MSB
05 00 ch2 temp LSB
06 00 ch2 hum
07 00 ch3 temp MSB
08 00 ch3 temp LSB
09 00 ch3 hum
0a 00 ch4 temp MSB
0b 00 ch4 temp LSB
0c 00 ch4 hum
0d 00 ch5 temp MSB
0e 00 ch5 temp LSB
0f 00 ch5 hum
10 00 ch6 temp MSB

[weewx-user] Re: WS-3000

I quickly checked how calibration is working. The current data sent back by 
the station already takes the calibration into account. Therefore, the only 
useful command that the driver should be sending is the command 0x03.
Also, the results are in °C regardless of the configuration of the console 
or of the sensors, so there is no need to check the configuration first 
either.

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

[weewx-user] Re: WS-3000

Forgot to attach my script...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
##!/opt/bin/python2.7
#!/usr/bin/env python2

import sys, traceback
import usb.core, usb.util
from time import sleep

def trimbuffer(buf):
i = 0
while i < len(buf):
if (i > 0 and buf[i] == 0x7d and buf[i-1] == 0x40):
break
i += 1
return buf[0:i+1]

def ws3000_write(command):
print "ws3000_write: entry"
VENDOR = 0x0483
PRODUCT = 0x5750
CONFIGURATION = 0

try:

print "Detecting device..."
device = usb.core.find(idVendor=VENDOR, idProduct=PRODUCT)
if device is None:
print("Is the WS-3000 connected?")
sys.exit(1)
print("Device found")

# Device busy if managed by the kernel
if device.is_kernel_driver_active(CONFIGURATION):
print("Detaching kernel driver")
device.detach_kernel_driver(CONFIGURATION)

# WS-3000 has only one configuration
device.set_configuration()

# control
print "Sending control packet"
#device.ctrl_transfer(0x21, 10, 0, 0, None)
device.ctrl_transfer(0, 9, 1, 0, None)

commands = [0x41, 0x06, 0x08, 0x09, 0x05, 0x03, 0x04]
#commands = [0x03, 0x03, 0x03, 0x03, 0x03, 0x03, 0x03]
for command in commands:
request = [0x7b, command, 0x40, 0x7d]
padding = [0x0] * 60
request.extend(padding)
print "Sending command: ", request
device.write(0x01, request, 100)
data = device.read(0x82, 64, 100)
data = trimbuffer(data)
print data
print len(data)
#for value in data:
#print hex(value)
sleep(10)

except:
print "An error occurred:", sys.exc_info()
traceback.print_exc(file=sys.stdout)

usb.util.dispose_resources(device)

print("Starting tests...")
ws3000_write("")
print("Tests completed")

[weewx-user] Re: WS-3000