Okay. I wiped the SD card and started over. Turns out I was installing the API driver using wee_extension and that was causing issues. However, it doesn't seem to be logging data for more than an hour now. This is the issue I had before and why I started over again. Is there anyone knowledgeable enough with this driver? Do I need to switch on logging somehow from the API calls? It just doesn't seem to update unless I run wee_reports manually. Thanks.
On Wednesday, December 13, 2023 at 9:49:25 AM UTC-8 Mark Sanchez wrote: > Ugh. I hadn't run the sudo -H pip3 install -r requirements.txt portion. > However, when I do run that and restart the service it is now starting but > throwing a different set of errors. > > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** __init__() takes 1 positional argument but 3 were given > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** Traceback (most recent call last): > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** File "/usr/share/weewx/weewxd", line 148, in main > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** engine = weewx.engine.StdEngine(config_dict) > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** File "/usr/share/weewx/weewx/engine.py", line 93, in __init__ > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** self.loadServices(config_dict) > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** File "/usr/share/weewx/weewx/engine.py", line 161, in > loadServices > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** obj = weeutil.weeutil.get_object(svc)(self, config_dict) > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** TypeError: __init__() takes 1 positional argument but 3 were given > Dec 13 09:46:52 raspberrypi python3[1822]: weewx[1822] CRITICAL __main__: > **** Exiting. > > Will this work itself out or is this just stuck in a loop? > > > On Wednesday, December 13, 2023 at 9:39:23 AM UTC-8 Mark Sanchez wrote: > >> Hello all, >> I had this somewhat working last week but then it just stopped collecting >> data so I had to start over. Now, when I'm following all the steps to >> install WeeWX with the AmbientWeatherAPI it is not working. I am getting >> the following errors: >> >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** File "/usr/share/weewx/weewx/engine.py", line 81, in __init__ >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** self.setupStation(config_dict) >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** File "/usr/share/weewx/weewx/engine.py", line 108, in setupStation >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** __import__(driver) >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** File "/usr/share/weewx/user/ambientweatherapi.py", line 9, in >> <module> >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** from ambient_api.ambientapi import AmbientAPI >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** ModuleNotFoundError: No module named 'ambient_api' >> Dec 13 09:27:20 raspberrypi python3[657]: weewx[657] CRITICAL __main__: >> **** Exiting. >> >> I have the ambient_api module installed via pip install ambient_api. Is >> there a way to manually enter my keys in the api module? The other two >> errors with the engine.py file I'm not understanding at all. >> >> Thanks. >> > -- 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/efffb8a5-6666-40db-929f-4f4fe68cf89fn%40googlegroups.com.
