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 
/home/pi/Install_files/hp3001_reader_python_script.py
Traceback (most recent call last):
  File "/home/pi/Install_files/hp3001_reader_python_script.py", line 4, in 
<module>
    import usb.core
ImportError: No module named usb.core

More or less as expected the 'import'-section causes first trouble, calling 
modules not present.
Not further tested, expecting 'more of the same'. Seems to demonstrate that 
'stand-alone' in this case is not 100%.

After installation on that machine of *weewx in the 'basic' form according 
to the UserGuide*, the result is as below (for my configuration):

pixx@raspberrypixx:~ $ sudo python 
/home/pi/Install_files/hp3001_reader_python_script.py
{'dateTime': 1581756586, 'extraHumid4': 88, 'extraHumid5': 88, 
'extraHumid2': 54, 'extraHumid3': 88, 'extraHumid1': 56, 'extraTemp4': 
11.4, 'extraTemp5': 11.4, 'extraTemp2': 16.8, 'extraTemp3': 11.3, 
'usUnits': 17, 'extraTemp1': 17.2}

Looks good!
Probably simplest solution with least effort is installation of weewx 
before running of the reader-script:
installation may be, either 'basic', or via setup.py

*Next questions*
- the output of this script on Putty's CLI is recognized as a JSON-file
- reading a program from another programmer is not always easy.
Therefore the quick&easy requests to the programmer (*Olivier?*) for 
support of my views:
1. What is the line of the script with the print-command and the 
JSON-file-name for this output?
2. Output by the JSON-file now dynamically limited to data from valid 
sensors.
=> if a sensor goes down (such as 'battery empty'), then a different 
JSON-file.
For subsequent processing somewhat easier/simpler if 'empty' fields are 
still there.
How/where to change the script to get that?

Op vrijdag 14 februari 2020 08:50:02 UTC+1 schreef Ton vanN:
>
> 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 <ton...@gmail.com> 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
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/1e03f915-8022-454a-813a-fc7afc99e064%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> | 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/26eec3f6-f742-4943-b63b-517490a07650%40googlegroups.com.

Reply via email to