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 <http://weewx.com/docs/usersguide.htm#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 <module> >>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5fa2135e-cdd1-4fb3-b5ae-912f720cbf60%40googlegroups.com.
