this looks like a problem with the python installation, not with the current directory.
you do not have to be in the /Users/Shared/weewx directory to run weewxd. On Sunday, March 4, 2018 at 12:04:24 PM UTC-5, Tom Keffer wrote: > > The problem is that you are in the wrong subdirectory and, as a result, > are using the original weewx.conf that came with the distribution, rather > than the freshly minted copy with your choices. > > Try this > > cd /Users/Shared/weewx > ./bin/weewxd weewx.conf > > > -tk > > > > On Sun, Mar 4, 2018 at 8:53 AM, kdbarto <[email protected] <javascript:>> > wrote: > >> Installed drivers include: >> 0) AcuRite (weewx.drivers.acurite) >> 1) CC3000 (weewx.drivers.cc3000) >> 2) FineOffsetUSB (weewx.drivers.fousb) >> 3) Simulator (weewx.drivers.simulator) >> 4) TE923 (weewx.drivers.te923) >> 5) Ultimeter (weewx.drivers.ultimeter) >> 6) Vantage (weewx.drivers.vantage) >> 7) WMR100 (weewx.drivers.wmr100) >> 8) WMR200 (weewx.drivers.wmr200) >> 9) WMR300 (weewx.drivers.wmr300) >> 10) WMR9x8 (weewx.drivers.wmr9x8) >> 11) WS1 (weewx.drivers.ws1) >> 12) WS23xx (weewx.drivers.ws23xx) >> 13) WS28xx (weewx.drivers.ws28xx) >> choose a driver: *6* >> Specify the hardware interface, either 'serial' or 'ethernet'. >> If the station is connected by serial, USB, or serial-to-USB >> adapter, specify serial. Specify ethernet for stations with >> WeatherLinkIP interface. >> type [serial]: *serial* >> Specify a port for stations with a serial interface, for >> example /dev/ttyUSB0 or /dev/ttyS0. >> port [/dev/ttyUSB0]: */dev/tty.usbserial-A900aaCR* >> >> Then run the thing and it looks like the station or serial driver didn’t >> take. >> >> marvin:weewx-3.8.0$ /Users/Shared/weewx/bin/weewxd weewx.conf >> Traceback (most recent call last): >> File "/Users/Shared/weewx/bin/weewxd", line 64, in <module> >> weewx.engine.main(options, args) >> File "/Users/Shared/weewx/bin/weewx/engine.py", line 865, in main >> engine = engine_class(config_dict) >> File "/Users/Shared/weewx/bin/weewx/engine.py", line 71, in __init__ >> self.setupStation(config_dict) >> File "/Users/Shared/weewx/bin/weewx/engine.py", line 89, in setupStation >> driver = config_dict[stationType]['driver'] >> File "build/bdist.macosx-10.11-intel/egg/configobj.py", line 554, in >> __getitem__ >> KeyError: 'unspecified' >> >> David >> >> On Mar 3, 2018, at 3:42 PM, Thomas Keffer <[email protected] <javascript:>> >> wrote: >> >> Nice to have a Mac expert around! Perhaps in a quiet moment you can tell >> me how to get the system logger to work on High Sierra. >> >> The biggest problem you are going to have is device drivers. In >> particular, if your hardware appears as anything other than a simple serial >> device, you may have problems getting it to work. From your first email, it >> looks like you have a Davis Vantage, which is a good thing, because it uses >> a serial interface. Hopefully, the Mac will recognize it as such. >> >> Get the prerequisites installed, as per the MacOS instructions >> <http://weewx.com/docs/macos.htm>. I know the instructions say to use >> easy_install (we should change that), but pip usually works better. If >> you're already installed everything using easy_install, don't worry about >> it. >> >> If you have a Vantage, you do not need to install pyusb >> >> Judging from your 2nd email, it looks like you tried installing weewx in >> /Users/Shared/weewx/... So try deleting everything in that directory. >> >> Then it's pretty much following the directions in the MacOS instructions, >> making sure to let the installer run to completion. >> >> An easy to overlook step is editing >> the file >> setup.cfg >> to reflect your nonstandard install location (normally, weewx is >> installed into /home/weewx, but /home is reserved on the Mac). >> >> */Users/Shared/weewx/weewx-3.8.0/setup.cfg:* >> >> # Configuration file for weewx installer. The syntax is from module >> # ConfigParser. See http://docs.python.org/library/configparser.html >> >> [install] >> >> # Set the following to the root directory where weewx should be installed >> home = /Users/Shared/weewx >> >> # Given the value of 'home' above, the following are reasonable values >> prefix = >> exec-prefix = >> install_lib = %(home)s/bin >> install_scripts = %(home)s/bin >> >> -tk >> >> >> On Sat, Mar 3, 2018 at 2:12 PM, kdbarto <[email protected] <javascript:>> >> wrote: >> >>> >>> On Mar 3, 2018, at 2:00 PM, Thomas Keffer <[email protected] >>> <javascript:>> wrote: >>> >>> The Mac is an "unsupported platform," but I'm sure we can get it >>> working. >>> >>> First, see if you already have a copy of PIL or Pillow. From the command >>> line: >>> >>> python -c "import PIL” >>> >>> Had no output. I’ll assume that is good. >>> >>> >>> If that gives you an import error, try this >>> >>> python -c "import Image" >>> >>> >>> If either of these work, then you are probably OK, and do not need to >>> install Pillow. I say "probably," because it's possible your previous >>> attempt to install using "install" resulted in a corrupted copy being left >>> behind. We'll see. >>> >>> If neither of these two command lines work, then you will need to >>> install Pillow. Use pip to do so. Your system probably already has pip, but >>> if it doesn't see the pip website >>> <https://pip.pypa.io/en/stable/installing/> for instructions on how to >>> install it. >>> >>> With pip in hand, install Pillow: >>> >>> pip install pillow >>> >>> >>> As for your second error, "KeyError", that looks like it may be caused >>> by an incomplete install. Did you use setup.py to install? Normally, the >>> weewx configuration file comes with a station type of "unspecified". That >>> is then replaced by setup.py with your actual hardware type. This second >>> step somehow did not get completed. >>> >>> Try deleting everything and trying again, this time making sure you let >>> the setup.py install run to completion. >>> >>> >>> Deleting everything. I’m good with that. Where is this everything you >>> refer to? 8^) >>> I’m well versed in all things Unix and programming, so being technical >>> is OK with me. (My name appears in every iPhone shipped, for instance). >>> >>> David >>> >>> >>> Hope this gets you started. >>> >>> -tk >>> >>> On Sat, Mar 3, 2018 at 1:42 PM, David <[email protected] <javascript:>> >>> wrote: >>> >>>> I’m just following the instructions from the weewx website. At this >>>> point it fails to launch. >>>> >>>> What I read on the Wview mailing list was that this was a good >>>> replacement and was actively developed and maintained, unlike wview. >>>> >>>> I guess I just need to know what to do ‘next’. Is there an un-install I >>>> can try to reset, and then try again? >>>> >>>> David >>>> >>>> On Mar 3, 2018, at 11:46 AM, Thomas Keffer <[email protected] >>>> <javascript:>> wrote: >>>> >>>> This seems to be a problem with the Pillow install, and not with WeeWX. >>>> >>>> First, are you sure you need to install Pillow? Most Python >>>> installations come with a version of PIL or Pillow. >>>> >>>> Second, I have generally had better luck installing things with pip, >>>> rather than BSD install or easy_install. >>>> >>>> -tk >>>> >>>> >>>> On Sat, Mar 3, 2018 at 10:38 AM, David Barto <[email protected] >>>> <javascript:>> wrote: >>>> >>>>> wviewd_vpro is consuming 75% of the cpu. So I thought I’d give weewx a >>>>> shot. >>>>> >>>>> Installing from their instructions shows the following problem, and >>>>> since I don’t know Python that well I though I’d ask if this is ‘OK’. >>>>> After doing this, trying it again shows that it is installed according >>>>> to the installer program. >>>>> >>>>> Anyone here have any answers about these problems? >>>>> >>>>> David >>>>> >>>>> >>>>> MacOS 10.11.6 >>>>> >>>>> marvin:Desktop$ python -V >>>>> Python 2.7.10 >>>>> >>>>> sudo install Pillow >>>>> >>>>> Adding Pillow 5.0.0 to easy-install.pth file >>>>> >>>>> Installed >>>>> /Library/Python/2.7/site-packages/Pillow-5.0.0-py2.7-macosx-10.11-intel.egg >>>>> Processing dependencies for Pillow >>>>> Finished processing dependencies for Pillow >>>>> Exception in thread Thread-1: >>>>> Traceback (most recent call last): >>>>> File >>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", >>>>> >>>>> line 810, in __bootstrap_inner >>>>> self.run() >>>>> File >>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", >>>>> >>>>> line 763, in run >>>>> self.__target(*self.__args, **self.__kwargs) >>>>> File >>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py", >>>>> >>>>> line 330, in _handle_workers >>>>> debug('worker handler exiting') >>>>> TypeError: 'NoneType' object is not callable >>>>> >>>>> Exception TypeError: TypeError("'NoneType' object does not support >>>>> item deletion",) in <Finalize object, dead> ignored >>>>> Exception in thread Thread-2: >>>>> Traceback (most recent call last): >>>>> File >>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", >>>>> >>>>> line 810, in __bootstrap_inner >>>>> self.run() >>>>> File >>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", >>>>> >>>>> line 763, in run >>>>> self.__target(*self.__args, **self.__kwargs) >>>>> File >>>>> "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py", >>>>> >>>>> line 366, in _handle_tasks >>>>> debug('task handler got sentinel') >>>>> TypeError: 'NoneType' object is not callable >>>>> >>>>> >>>> >>>> >>> >>> >> >> >
