Re: [weewx-user] Re: Failed MQTT Server Install
Yeah. That hasn't worked. It's still trying to call on it from the script. Might have to go in to the Belchertown script and comment out any mqtt stuff. On Sat, Dec 16, 2023, 11:24 AM vince wrote: > Just turn it off in your skin configuration in weewx.conf > > [[Belchertown]] > [[[Extras]]] > mqtt_websockets_enabled = 0 > > > On Saturday, December 16, 2023 at 10:40:46 AM UTC-8 Mark Sanchez wrote: > >> Hello all, >> >> I attempted to install MQTT for real time data of my weather station >> using this guide. However, it doesn't want to connect to the server and I >> wanted to disable it for the time being. I commented out all the lines >> associated with it but when I run wee_reports I get the following error. >> I'm wondering what I need to do to restore my weather station's status as >> now I just see that it can't connect to it on the webpage. >> >> Traceback (most recent call last): >> File "/usr/share/weewx/weewx/reportengine.py", line 197, in run >> obj.start() >> File "/usr/share/weewx/weewx/reportengine.py", line 385, in start >> self.run() >> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run >> ngen = self.generate(gen_dict[section_name], section_name, >> self.gen_ts) >> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate >> ngen += self.generate(section[subsection], subsection, gen_ts) >> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate >> ngen += self.generate(section[subsection], subsection, gen_ts) >> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 321, in generate >> searchList = self._getSearchList(encoding, timespan, >> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in >> _getSearchList >> search_list += obj.get_extension_list(timespan, db_lookup) >> File "/usr/share/weewx/user/belchertown.py", line 2015, in >> get_extension_list >> if self.generator.skin_dict["Extras"]["mqtt_websockets_host_kiosk"] >> != "": >> File "/usr/lib/python3/dist-packages/configobj.py", line 554, in >> __getitem__ >> val = dict.__getitem__(self, key) >> KeyError: 'mqtt_websockets_host_kiosk' >> >> How can I get rid of the mqtt_websockers_host_kiosk? >> 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 weewx-user+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/b06246d3-62d9-4423-ab74-c2c8700f66ffn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/b06246d3-62d9-4423-ab74-c2c8700f66ffn%40googlegroups.com?utm_medium=email_source=footer> > . > -- 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/CA%2BCc0BEcf3S9LjuvyJAndMJocV52TeLLBipP5jHBSKQmZoypwA%40mail.gmail.com.
[weewx-user] Failed MQTT Server Install
Hello all, I attempted to install MQTT for real time data of my weather station using this guide. However, it doesn't want to connect to the server and I wanted to disable it for the time being. I commented out all the lines associated with it but when I run wee_reports I get the following error. I'm wondering what I need to do to restore my weather station's status as now I just see that it can't connect to it on the webpage. Traceback (most recent call last): File "/usr/share/weewx/weewx/reportengine.py", line 197, in run obj.start() File "/usr/share/weewx/weewx/reportengine.py", line 385, in start self.run() File "/usr/share/weewx/weewx/cheetahgenerator.py", line 169, in run ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts) File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate ngen += self.generate(section[subsection], subsection, gen_ts) File "/usr/share/weewx/weewx/cheetahgenerator.py", line 229, in generate ngen += self.generate(section[subsection], subsection, gen_ts) File "/usr/share/weewx/weewx/cheetahgenerator.py", line 321, in generate searchList = self._getSearchList(encoding, timespan, File "/usr/share/weewx/weewx/cheetahgenerator.py", line 415, in _getSearchList search_list += obj.get_extension_list(timespan, db_lookup) File "/usr/share/weewx/user/belchertown.py", line 2015, in get_extension_list if self.generator.skin_dict["Extras"]["mqtt_websockets_host_kiosk"] != "": File "/usr/lib/python3/dist-packages/configobj.py", line 554, in __getitem__ val = dict.__getitem__(self, key) KeyError: 'mqtt_websockets_host_kiosk' How can I get rid of the mqtt_websockers_host_kiosk? 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/35daa585-c236-44a6-ae5c-746f65e8faa3n%40googlegroups.com.
[weewx-user] Re: Ambientweatherapi not finding ambient_api
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 >> >> 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/efffb8a5--40db-929f-4f4fe68cf89fn%40googlegroups.com.
Re: [weewx-user] Re: Docker image with interceptor driver and neowx skin
No worries. I'm going in another direction with the ambientweatherapi
instead. Cheers.
On Monday, December 4, 2023 at 8:16:57 PM UTC-8 Bruno BORDAS wrote:
> I'm not in a position to test right now.
> I would try to merge the compose file from network with the main one. Try
> to define the MacVLan in the main compose.
>
> If I remember correctly, I separated both because I needed this second
> network with other containers too.
>
> Sorry, I'm moving home at the moment and not setup yet
> Le 4 déc. 2023, à 20:22, Mark Sanchez a écrit:
>>
>> Okay. I'll start with the network connection. I have it in the network
>> folder and have edited the addresses. Do I need to have NGINX installed
>> already? When I run docker compose up -d it just says "No Service
>> Selected". I am assuming it doesn't realize it's supposed to run a MACVLAN
>> network option?
>>
>> When I run docker network ls I see:
>> sudo docker network ls
>> NETWORK ID NAMEDRIVERSCOPE
>> 57223ea2cf02 bridge bridgelocal
>> 49360022eadb hosthost local
>> dab0c8fc1570 nonenull local
>> 00f80f463ca4 weewx_default bridgelocal
>>
>> On Monday, December 4, 2023 at 10:01:49 AM UTC-8 Bruno BORDAS wrote:
>>
>>> Woo this was a long time ago
>>> Let me try to remember.
>>>
>>> No ${PWD} (Print Working Directory) is not for a password , but it is
>>> the location of your source code AKA where is you docker-compose file.
>>>
>>> Without knowing much your errors, difficult to help.
>>>
>>> Le lun. 4 déc. 2023, 18:17, Mark Sanchez >> <http://href>> a écrit :
>>>
>>>> This is super cool as I have now purchased the same weather station.
>>>> However, I'm terrible with Docker. I can't seem to get this running. It
>>>> seems to keep tripping at steps. Right now I'm stuck because something
>>>> needs to happen with the ${PWD} variable. Do I need to change that to just
>>>> my password in the docker-compose.yaml file? I appreciate you setting all
>>>> of this up though!
>>>>
>>>> On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:
>>>>
>>> Dear weewx users.
>>>>>
>>>>> After dozens hours of researches and tries, I'm proud to provide my
>>>>> own docker image of weewx.
>>>>>
>>>>> It runs on Debian stretch, build from sources, with the interceptor
>>>>> driver and neowx skin.
>>>>>
>>>>> I use it with Pihole to grab the data.
>>>>> Everything (I hope) is written in the repo you can find here:
>>>>> https://github.com/MrNonoss/WeewX-Docker
>>>>>
>>>>> Feel free to review and comment it.
>>>>>
>>>>> --
>>>>
>>> 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/Rr_XyWLONZ4/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> weewx-user+...@googlegroups.com <http://href>.
>>>>
>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
--
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/1a52d258-2552-47df-b796-9a6fa4582c48n%40googlegroups.com.
[weewx-user] Re: Ambientweatherapi not finding ambient_api
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
>
> 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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/02cfce69-6012-40c0-8161-cdb94aa862c7n%40googlegroups.com.
[weewx-user] Ambientweatherapi not finding ambient_api
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 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ad4fe8fb-20ae-4d50-bde1-68f651113af9n%40googlegroups.com.
[weewx-user] AmbientWeather API Not Getting Data
Hi all, I have finally had success with getting my Ambient Weather WS-2902 somewhat communicating with Weewx. I used the Ambient Weather API driver and it seems to be running. However, it isn't receiving any data back. There seems to be something about it not getting any device information. Would anybody know what this means: ● weewx.service - LSB: weewx weather system Loaded: loaded (/etc/init.d/weewx; generated) Active: active (running) since Sun 2023-12-10 12:32:12 PST; 6s ago Docs: man:systemd-sysv-generator(8) Process: 10672 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 1595) CPU: 1.393s CGroup: /system.slice/weewx.service └─10687 python3 /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf Dec 10 12:32:16 raspberrypi weewxd[10687]: ambientweatherapi driver encountered an error. Dec 10 12:32:16 raspberrypi python3[10687]: weewx[10687] ERROR root: ambientweatherapi driver encountered an error. Dec 10 12:32:16 raspberrypi weewxd[10687]: Error caught was: AmbientAPI get_devices() returned empty dict Dec 10 12:32:16 raspberrypi python3[10687]: weewx[10687] ERROR root: Error caught was: AmbientAPI get_devices() returned empty dict Dec 10 12:32:16 raspberrypi python3[10687]: weewx[10687] DEBUG root: Starting Packet Build Dec 10 12:32:16 raspberrypi weewxd[10687]: ambientweatherapi driver had an error sending data to weewx. Dec 10 12:32:16 raspberrypi python3[10687]: weewx[10687] ERROR root: ambientweatherapi driver had an error sending data to weewx. Dec 10 12:32:16 raspberrypi weewxd[10687]: Error caught was: Previous error occured, skipping packet build. Dec 10 12:32:16 raspberrypi python3[10687]: weewx[10687] ERROR root: Error caught was: Previous error occured, skipping packet build. Dec 10 12:32:16 raspberrypi python3[10687]: weewx[10687] DEBUG root: Going to sleep It seems to be returning nothing and skipping packet builds. In the API driver I just have the API Key filled in because I couldn't find anywhere to get an Ambient Weather API App Key. Would anyone know where to obtain this? (if it's even necessary) This is how I have the driver set up in weewx.conf: ## [ambientweatherapi] # This section for the AmbientWeatherAPI driver for weewx # The time (in seconds) between LOOP packets and getting API data # The ObserverIP only pushes data every 60 seconds. loop_interval = 60 #API Log level log_level = ERROR #Log file location log_file = /etc/weewx/LOG #URL to the Ambient Weather API api_url = 'https://api.ambientweather.net/v1' #Ambient Weather API App Key api_app_key = '54eae45991714a89a9d6879d9c740cb1fc3eb6a6a40a49afb06466150752c2d7' #Ambient Weather API Key api_key = '54eae45991714a89a9d6879d9c740cb1fc3eb6a6a40a49afb06466150752c2d7' #Ambient Weather Use Meteobridge (default if False) #use_meteobridge = '' # Name of Hardware device. hardware = 'Ambient Weather WS-2902D' # The driver to use: driver = user.ambientweatherapi ## -- 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/4a3eeca2-12bd-4928-b14d-8a284d656bc1n%40googlegroups.com.
[weewx-user] Ambient API with WS-2902D
Hello. So, I abandoned the Interceptor for use with my WS-2902D as it went
nowhere. I decided to try the Ambient Weather API Driver and registered for
an API key with Ambient Weather. However, when I run through the process
detailed here, everything installs just fine but I get these errors when
attempting to start Weewx.
Dec 10 12:06:53 raspberrypi weewx[1500]: Starting weewx weather system:
weewx
Dec 10 12:06:53 raspberrypi weewx[1511]: Error parsing config file: Invalid
line ('ambientweatherapi# WEEWX CONFIGURATION FILE') (matched as neither
section nor keyword) at line 1. File /etc/weewx/weewx.conf
Dec 10 12:06:53 raspberrypi weewx[1511]: Traceback (most recent
call last):
Dec 10 12:06:53 raspberrypi weewx[1511]: File
"/usr/share/weewx/weewxd", line 88, in main
Dec 10 12:06:53 raspberrypi weewx[1511]: config_path,
config_dict = weecfg.read_config(options.config_path, list(args))
Dec 10 12:06:53 raspberrypi weewx[1511]: File
"/usr/share/weewx/weecfg/__init__.py", line 150, in read_config
Dec 10 12:06:53 raspberrypi weewx[1511]: config_dict =
configobj.ConfigObj(config_path,
Dec 10 12:06:53 raspberrypi weewx[1511]: File
"/usr/lib/python3/dist-packages/configobj.py", line 1229, in __init__
Dec 10 12:06:53 raspberrypi weewx[1511]: self._load(infile,
configspec)
Dec 10 12:06:53 raspberrypi weewx[1511]: File
"/usr/lib/python3/dist-packages/configobj.py", line 1318, in _load
Dec 10 12:06:53 raspberrypi weewx[1511]: raise error
Dec 10 12:06:53 raspberrypi weewx[1511]: configobj.ParseError:
Invalid line ('ambientweatherapi# WEEWX CONFIGURATION FILE') (matched as
neither section nor keyword) at line 1. File /etc/weewx/weewx.conf
Dec 10 12:06:53 raspberrypi weewx[1512]: failed!
Dec 10 12:06:53 raspberrypi systemd[1]: weewx.service: Control process
exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit weewx.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Dec 10 12:06:53 raspberrypi systemd[1]: weewx.service: Failed with result
'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit weewx.service has entered the 'failed' state with result
'exit-code'.
Dec 10 12:06:53 raspberrypi systemd[1]: Failed to start LSB: weewx weather
system.
░░ Subject: A start job for unit weewx.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit weewx.service has finished with a failure.
░░
░░ The job identifier is 1427 and the job result is failed.
Dec 10 12:06:53 raspberrypi sudo[1492]: pam_unix(sudo:session): session
closed for user root
The configuration file seems fine but it's not liking how it's in the file?
# Set to type of station hardware. There must be a corresponding stanza
# in this file, which includes a value for the 'driver' option.
station_type = Ambientweatherapi
# If you have a website, you may specify an URL. This is required if you
# intend to register your station.
#station_url = http://www.example.com
# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1
# Start of week (0=Monday, 6=Sunday)
week_start = 6
##
[Ambientweatherapi]
# This section for the AmbientWeatherAPI driver for weewx
# The time (in seconds) between LOOP packets and getting API data
# The ObserverIP only pushes data every 60 seconds.
loop_interval = 60
#API Log level
log_level = ERROR
#Log file location
log_file = /etc/weewx/LOG
#URL to the Ambient Weather API
api_url = 'https://api.ambientweather.net/v1'
#Ambient Weather API App Key
api_app_key = ''
#Ambient Weather API Key
api_key =
'54eae45991714a89a9d6879d9c740cb1fc3eb6a6a40a49afb06466150752c2d7'
#Ambient Weather Use Meteobridge (default if False)
#use_meteobridge = ''
# Name of Hardware device.
hardware = 'Ambient Weather WS-2902D'
# The driver to use:
driver = user.ambientweatherapi
##
Does anyone have any insight as to why this won't work? I did this with a
fresh install of Raspbian, Weewx and all of the dependencies for Python3.
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[weewx-user] Re: Weewx running but interceptor not capturing data?
Yeah. I think that's the problem is this is way over my head. I'm not understanding exactly what files to edit in which manner. Oh well. It was fun while it lasted (not really). I guess I'll just get my data from Ambient Weather and consider this one a failed experiment like all other Linux experiments for the most part. On Friday, December 8, 2023 at 9:51:47 AM UTC-8 vince wrote: > I would follow the github instructions to run the listener interactively > and get 'that' working before trying to go A-Z and doing so under weewx > > On Friday, December 8, 2023 at 8:55:18 AM UTC-8 Mark Sanchez wrote: > >> I actually restarted and am getting something where the interceptor is >> finally being pinged but it's showing this in the syslog: >> thechez@raspberrypi:~ $ sudo tail -f /var/log/syslog >> Dec 8 08:51:10 raspberrypi weewx[1041] INFO weewx.manager: Daily >> summaries up to date >> Dec 8 08:51:10 raspberrypi weewx[1041] INFO weewx.engine: Starting main >> packet loop. >> Dec 8 08:51:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> Dec 8 08:51:30 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> Dec 8 08:51:40 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> Dec 8 08:51:50 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> Dec 8 08:52:00 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> Dec 8 08:52:10 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> Dec 8 08:52:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty >> queue >> >> So it's acknowledging the interceptor driver but nothing is going in? >> >> On Friday, December 8, 2023 at 8:20:08 AM UTC-8 Mark Sanchez wrote: >> >>> I have turned off the firewall in ufw to see if it was any port closures >>> that were causing issues. I also opened port 80 on the weather station in >>> my router. >>> >>> Here's how my conf file is set up: >>> >>> # Set to 1 for extra debug info, otherwise comment it out or set to zero >>> debug = 0 >>> >>> # Root directory of the weewx data file hierarchy for this station >>> WEEWX_ROOT = / >>> >>> # Whether to log successful operations. May get overridden below. >>> log_success = True >>> >>> # Whether to log unsuccessful operations. May get overridden below. >>> log_failure = True >>> >>> # Do not modify this. It is used when installing and updating weewx. >>> version = 4.10.2 >>> >>> >>> ## >>> >>> # This section is for information about the station. >>> >>> [Station] >>> >>> # Description of the station location >>> location = "Spokane, WA" >>> >>> # Latitude in decimal degrees. Negative for southern hemisphere >>> latitude = 47.6884 >>> # Longitude in decimal degrees. Negative for western hemisphere. >>> longitude = -117.4528 >>> >>> # Altitude of the station, with the unit it is in. This is used only >>> # if the hardware cannot supply a value. >>> altitude = 1900, foot >>> >>> # Set to type of station hardware. There must be a corresponding >>> stanza >>> # in this file, which includes a value for the 'driver' option. >>> station_type = Interceptor >>> >>> # If you have a website, you may specify an URL. This is required if >>> you >>> # intend to register your station. >>> #station_url = http://www.example.com >>> >>> # The start of the rain year (1=January; 10=October, etc.). This is >>> # downloaded from the station if the hardware supports it. >>> rain_year_start = 1 >>> >>> # Start of week (0=Monday, 6=Sunday) >>> week_start = 6 >>> >>> >>> ## >>> >>> [Interceptor] >>> # This section is for the network traffic interceptor driver. >>> >>> # The driver to use: >>> driver = user.interceptor >>> >>> # Specify the hardware device to capture. Options include: >>> # acurite-bridge - acurite internet bridge, smarthub, or access >>> # observer - fine offset WH2600/HP1000/HP1003, ambient WS2902 >>> # lw30x - oregon s
[weewx-user] Re: Weewx running but interceptor not capturing data?
I actually restarted and am getting something where the interceptor is finally being pinged but it's showing this in the syslog: thechez@raspberrypi:~ $ sudo tail -f /var/log/syslog Dec 8 08:51:10 raspberrypi weewx[1041] INFO weewx.manager: Daily summaries up to date Dec 8 08:51:10 raspberrypi weewx[1041] INFO weewx.engine: Starting main packet loop. Dec 8 08:51:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue Dec 8 08:51:30 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue Dec 8 08:51:40 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue Dec 8 08:51:50 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue Dec 8 08:52:00 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue Dec 8 08:52:10 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue Dec 8 08:52:20 raspberrypi weewx[1041] DEBUG user.interceptor: empty queue So it's acknowledging the interceptor driver but nothing is going in? On Friday, December 8, 2023 at 8:20:08 AM UTC-8 Mark Sanchez wrote: > I have turned off the firewall in ufw to see if it was any port closures > that were causing issues. I also opened port 80 on the weather station in > my router. > > Here's how my conf file is set up: > > # Set to 1 for extra debug info, otherwise comment it out or set to zero > debug = 0 > > # Root directory of the weewx data file hierarchy for this station > WEEWX_ROOT = / > > # Whether to log successful operations. May get overridden below. > log_success = True > > # Whether to log unsuccessful operations. May get overridden below. > log_failure = True > > # Do not modify this. It is used when installing and updating weewx. > version = 4.10.2 > > > ## > > # This section is for information about the station. > > [Station] > > # Description of the station location > location = "Spokane, WA" > > # Latitude in decimal degrees. Negative for southern hemisphere > latitude = 47.6884 > # Longitude in decimal degrees. Negative for western hemisphere. > longitude = -117.4528 > > # Altitude of the station, with the unit it is in. This is used only > # if the hardware cannot supply a value. > altitude = 1900, foot > > # Set to type of station hardware. There must be a corresponding stanza > # in this file, which includes a value for the 'driver' option. > station_type = Interceptor > > # If you have a website, you may specify an URL. This is required if > you > # intend to register your station. > #station_url = http://www.example.com > > # The start of the rain year (1=January; 10=October, etc.). This is > # downloaded from the station if the hardware supports it. > rain_year_start = 1 > > # Start of week (0=Monday, 6=Sunday) > week_start = 6 > > > ## > > [Interceptor] > # This section is for the network traffic interceptor driver. > > # The driver to use: > driver = user.interceptor > > # Specify the hardware device to capture. Options include: > # acurite-bridge - acurite internet bridge, smarthub, or access > # observer - fine offset WH2600/HP1000/HP1003, ambient WS2902 > # lw30x - oregon scientific LW301/LW302 > # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge > # ecowitt-client - any hardware that uses the ecowitt protocol > # wu-client - any hardware that uses the weather underground protocol > > device_type = observer > mode = sniff > iface = wlan0 > pcap_filter = src 192.168.4.214 and dst port 80 > > > ## > > [WS2902] > # transceiver_frequency = 915 > # model = "Ambient Weather WS2902" > > > ### > > [Simulator] > # This section is for the weewx weather station simulator > > # The time (in seconds) between LOOP packets. > ##loop_interval = 2.5 > > # The simulator mode can be either 'simulator' or 'generator'. > # Real-time simulator. Sleep between each LOOP packet. > ##mode = simulator > # Generator. Emit LOOP packets as fast as possible (useful for > testing). > #mode = generator > > # The start time. Format is -mm-ddTHH:MM. If not specified, the > default > # is to use the present time. > #start = 2011-01-01T00:00 > > # The driver to use: > ##driver = weewx.drivers.simulator > > > ##
[weewx-user] Re: Weewx running but interceptor not capturing data?
I have turned off the firewall in ufw to see if it was any port closures that were causing issues. I also opened port 80 on the weather station in my router. Here's how my conf file is set up: # Set to 1 for extra debug info, otherwise comment it out or set to zero debug = 0 # Root directory of the weewx data file hierarchy for this station WEEWX_ROOT = / # Whether to log successful operations. May get overridden below. log_success = True # Whether to log unsuccessful operations. May get overridden below. log_failure = True # Do not modify this. It is used when installing and updating weewx. version = 4.10.2 ## # This section is for information about the station. [Station] # Description of the station location location = "Spokane, WA" # Latitude in decimal degrees. Negative for southern hemisphere latitude = 47.6884 # Longitude in decimal degrees. Negative for western hemisphere. longitude = -117.4528 # Altitude of the station, with the unit it is in. This is used only # if the hardware cannot supply a value. altitude = 1900, foot # Set to type of station hardware. There must be a corresponding stanza # in this file, which includes a value for the 'driver' option. station_type = Interceptor # If you have a website, you may specify an URL. This is required if you # intend to register your station. #station_url = http://www.example.com # The start of the rain year (1=January; 10=October, etc.). This is # downloaded from the station if the hardware supports it. rain_year_start = 1 # Start of week (0=Monday, 6=Sunday) week_start = 6 ## [Interceptor] # This section is for the network traffic interceptor driver. # The driver to use: driver = user.interceptor # Specify the hardware device to capture. Options include: # acurite-bridge - acurite internet bridge, smarthub, or access # observer - fine offset WH2600/HP1000/HP1003, ambient WS2902 # lw30x - oregon scientific LW301/LW302 # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge # ecowitt-client - any hardware that uses the ecowitt protocol # wu-client - any hardware that uses the weather underground protocol device_type = observer mode = sniff iface = wlan0 pcap_filter = src 192.168.4.214 and dst port 80 ## [WS2902] # transceiver_frequency = 915 # model = "Ambient Weather WS2902" ### [Simulator] # This section is for the weewx weather station simulator # The time (in seconds) between LOOP packets. ##loop_interval = 2.5 # The simulator mode can be either 'simulator' or 'generator'. # Real-time simulator. Sleep between each LOOP packet. ##mode = simulator # Generator. Emit LOOP packets as fast as possible (useful for testing). #mode = generator # The start time. Format is -mm-ddTHH:MM. If not specified, the default # is to use the present time. #start = 2011-01-01T00:00 # The driver to use: ##driver = weewx.drivers.simulator ## # This section is for uploading data to Internet sites [StdRESTful] # Uncomment and change to override logging for uploading services. # log_success = True # log_failure = True [[StationRegistry]] # To register this weather station with weewx, set this to true, # then fill out option 'station_url', located in the [Station] section above. register_this_station = false [[AWEKAS]] # This section is for configuring posts to AWEKAS. # If you wish to post to AWEKAS, set the option 'enable' to true, then specify a username # and password. To guard against parsing errors, put the password in quotes. enable = false username = replace_me password = replace_me [[CWOP]] # This section is for configuring posts to CWOP. # If you wish to post to CWOP, set the option 'enable' to true, # then specify the station ID (e.g., CW1234). enable = false station = replace_me # If this is an APRS (radio amateur) station, specify the On Thursday, December 7, 2023 at 8:18:27 PM UTC-8 vince wrote: > In the absence of you providing any config file(s) nor debug=1 logs nope > no ideas other than trying dropping shields and running with no firewall if > you can do that safely on your network. > > On Thursday, December 7, 2023 at 6:16:59 PM UTC-8 Mark Sanchez wrote: > >> Hello, >> I have now wasted four days so far trying to
[weewx-user] Weewx running but interceptor not capturing data?
Hello, I have now wasted four days so far trying to get weewx setup with my Ambient WS-2902 using interceptor to sniff the packets as it's headed to Ambient Weather's site. I believe I have it running at this point and Apache is set up but nothing is going into the specified folder. How can I tell if it's sniffing the data or not? thechez@raspberrypi:~ $ service weewx status ● weewx.service - LSB: weewx weather system Loaded: loaded (/etc/init.d/weewx; generated) Active: active (running) since Thu 2023-12-07 18:12:50 PST; 55s ago Docs: man:systemd-sysv-generator(8) Process: 433 ExecStart=/etc/init.d/weewx start (code=exited, status=0/SUCCESS) Tasks: 2 (limit: 1595) CPU: 1.314s CGroup: /system.slice/weewx.service └─657 python3 /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO weewx.restx: PWSweather: Posting not enabled. Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO weewx.restx: CWOP: Posting not enabled. Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO weewx.restx: WOW: Posting not enabled. Dec 07 18:12:50 raspberrypi python3[657]: weewx[657] INFO weewx.restx: AWEKAS: Posting not enabled. Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO weewx.engine: 'pyephem' detected, extended almanac data is available Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO __main__: Starting up weewx version 4.10.2 Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb' Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO weewx.manager: Starting backfill of daily summaries Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO weewx.manager: Daily summaries up to date Dec 07 18:12:51 raspberrypi python3[657]: weewx[657] INFO weewx.engine: Starting main packet loop. I have changed my iptables to capture the local IP and port but it doesn't seem to be doing anything. Any ideas or any more information I could add? 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/96fbb80b-35fb-4ecf-8536-2f49ac026c8cn%40googlegroups.com.
Re: [weewx-user] Re: Docker image with interceptor driver and neowx skin
Okay. I'll start with the network connection. I have it in the network
folder and have edited the addresses. Do I need to have NGINX installed
already? When I run docker compose up -d it just says "No Service
Selected". I am assuming it doesn't realize it's supposed to run a MACVLAN
network option?
When I run docker network ls I see:
sudo docker network ls
NETWORK ID NAMEDRIVERSCOPE
57223ea2cf02 bridge bridgelocal
49360022eadb hosthost local
dab0c8fc1570 nonenull local
00f80f463ca4 weewx_default bridgelocal
On Monday, December 4, 2023 at 10:01:49 AM UTC-8 Bruno BORDAS wrote:
> Woo this was a long time ago
> Let me try to remember.
>
> No ${PWD} (Print Working Directory) is not for a password , but it is the
> location of your source code AKA where is you docker-compose file.
>
> Without knowing much your errors, difficult to help.
>
> Le lun. 4 déc. 2023, 18:17, Mark Sanchez a écrit :
>
>> This is super cool as I have now purchased the same weather station.
>> However, I'm terrible with Docker. I can't seem to get this running. It
>> seems to keep tripping at steps. Right now I'm stuck because something
>> needs to happen with the ${PWD} variable. Do I need to change that to just
>> my password in the docker-compose.yaml file? I appreciate you setting all
>> of this up though!
>>
>> On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:
>>
> Dear weewx users.
>>>
>>> After dozens hours of researches and tries, I'm proud to provide my own
>>> docker image of weewx.
>>>
>>> It runs on Debian stretch, build from sources, with the interceptor
>>> driver and neowx skin.
>>>
>>> I use it with Pihole to grab the data.
>>> Everything (I hope) is written in the repo you can find here:
>>> https://github.com/MrNonoss/WeewX-Docker
>>>
>>> Feel free to review and comment it.
>>>
>>> --
>>
> 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/Rr_XyWLONZ4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/weewx-user/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
--
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/290cfa7d-28e3-45a4-b07a-a46dcd52b488n%40googlegroups.com.
[weewx-user] Re: Docker image with interceptor driver and neowx skin
This is great! Thanks for making this. I am still stumbling when trying to get the docker image up and running. I'm not Docker savvy though so it's been a struggle. Right now, the docker compose command can't seem to get past weewx-core being an undefined volume. Is this a directory I need to create? Thanks. On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote: > Dear weewx users. > > After dozens hours of researches and tries, I'm proud to provide my own > docker image of weewx. > > It runs on Debian stretch, build from sources, with the interceptor driver > and neowx skin. > > I use it with Pihole to grab the data. > Everything (I hope) is written in the repo you can find here: > https://github.com/MrNonoss/WeewX-Docker > > Feel free to review and comment it. > -- 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/7c850ba3-620a-435f-a5e5-9e17b776943dn%40googlegroups.com.
[weewx-user] Re: Docker image with interceptor driver and neowx skin
This is super cool as I have now purchased the same weather station.
However, I'm terrible with Docker. I can't seem to get this running. It
seems to keep tripping at steps. Right now I'm stuck because something
needs to happen with the ${PWD} variable. Do I need to change that to just
my password in the docker-compose.yaml file? I appreciate you setting all
of this up though!
On Sunday, November 10, 2019 at 10:09:15 AM UTC-8 Bruno BORDAS wrote:
> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my own
> docker image of weewx.
>
> It runs on Debian stretch, build from sources, with the interceptor driver
> and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here:
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it.
>
--
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/e6e3adaf-6b53-4ab7-b7a8-3d4d618471f1n%40googlegroups.com.
