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

Hi all, I have a Misol Hp-3001 too and after some logilc work on Oliver files I was able to convert them in python3 format (I don't know python language). Now last version of weewx get date from my Station. I'm writing you, specially to Vladi, can you share skin/template or all is needed to

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

Don't forget to add 2 linse at the start of the script! import json import dicttoxml Op zondag 23 februari 2020 09:16:12 UTC+1 schreef Ton vanN: > > Olivier, > > 1. Use of JSON/XML > Why not a database or MQTT? Reason = 'history of System-concept' > Within my configuration I have a structure in

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

Olivier, Related to reading the WS3000/HP300x, have split the effort in 2 segments: a) export of data from the WS3000-reader in a layout and to a location which can be accessed by the "User". In my case either JSON-format, or XML-format. This function seems best located at side of the Reader.

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

Olivier, 1. Use of JSON/XML Why not a database or MQTT? Reason = 'history of System-concept' Within my configuration I have a structure in which from various sources a set of JSON/XML-files is uploaded to a 'Central server', and all users can pick as they like: *some* of these files are

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

ok, in fact I am getting very confused by what you are trying to do. Why do you want to mis-use weewx? And why use XML or JSON files, rather than a database? And if the goal is to integrate the WS-3000 with Domoticz, can't this be done directly (by writing a plugin or add-on to Domoticz)? --

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

> > ImportError: No module named usb.core usb.core is not a weewx module, this is a basic python one. What you need to do is not to install weewx, but rather to install the correct python dependencies. Considering what you are trying to do, weewx doesn't seem to be the appropriate tool.

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

Is really a side-step and an indirect way, but 'mis-using' weewx to create a weatherstation based on 'other data' (for example) can be realised via User's Guide · gjr80/weewx-xmlparse Wiki · GitHub Main

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

*Question 3,* to have 'loose' coupling between this reader-script and any follow-on function. Is it possible to add one or more lines for export/save of the JSON-file to a designated folder? Op zondag 16 februari 2020 08:38:02 UTC+1 schreef Ton vanN: > > Fitted the stand-alone reader *on an

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

Fitted the stand-alone reader *on an 'empty' Raspberry without weewx* (just Raspian_Buster + latest Domoticz_beta). In new folder /home/pi/Install-files Slight name-change to match my system-configuration. First result from Putty's CLI shown below. pixx@raspberrypixx:~ $ sudo python

Re: [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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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'

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

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

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

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

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,

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

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]:

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

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

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

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

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:

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

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

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

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

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

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

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

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

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

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,

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

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

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

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

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

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,

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[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-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[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

[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

[weewx-user] Re: WS-3000

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

[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

[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

[weewx-user] Re: WS-3000

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] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[weewx-user] Re: WS-3000

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

[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

[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

[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

[weewx-user] Re: WS-3000

Hi again, I did some more troubleshooting, and I now have the feeling that the driver isn't doing exactly what it should. First of all, a disclaimer: I am no developer and I know next to nothing about the USB protocol, so please don't be too harsh on me if what I am saying is complete BS.

[weewx-user] Re: WS-3000

And by the way, the console's firmware version is 1.1.6 -- 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,

[weewx-user] Re: WS-3000

When I connect the station to a Windows VM, I can successfully read the data using EasyTemp. So I tried to compare what EasyTemp and weewx are sending on the USB bus, using wireshark. Unfortunately, although there are obvious differences, I can't tell what's causing the error. The two files are

[weewx-user] Re: WS-3000

Thanks a lot for your help. I am now one step further: the station is now correctly detected. But I run into the error below almost immediately. NOTE: the error shown below occurs when I try to run weewx in a docker container (using pyusb 1.0.2). To rule out problems related to docker, I also

[weewx-user] Re: WS-3000

On Thursday, January 11, 2018 at 4:50:43 PM UTC-5, olivier.guyotot wrote: > > Hello, > > I am trying to get data from an Ambient Weather WS-3000 station, which > should apparently be supported according to http://weewx.com/hardware.html > (Fine Offset, HP3000 - the name is slightly different,