January 4, 20188 yr Has anybody thought of trying a Docker or Plugin for Weewx? http://www.weewx.com/
February 20, 20197 yr Anyone? or how to get those containers into Unraid? seems like QNAP has those options Thanks
February 20, 20197 yr 6 minutes ago, killeriq said: Anyone? or how to get those containers into Unraid? seems like QNAP has those options Thanks
January 1, 20215 yr @killeriq Were you able to install weewx in unraid? Of course one could create a small vm on e. g. dietpi base and install weewx there, but the solution we'd prefer would be the docker container.
January 5, 20215 yr I would also be very interested in this, currently running weewx from a VM since I haven't figured out how to set it up as a docker.
January 5, 20215 yr @Zilched I think it should be possible to run weewx under unraid by allowing "additional search results from Docker hub". Go to Apps, Settings (left) and set " Enable additional search results from dockerHub:" to yes. When you search then for "weewx" in the apps tab, it shows "No matching applications found", but above that, you have the option "Click Here To Get More Results From DockerHub". If you click on that, you should see a lot of different weewx images. Unfortunately, the guy, who made the most popular weewx docker container, jgoerzen, wrote in his documentation, that his docker container allows only rsync and ssh for the upload. Since I'm restricted to FTP(S) upload from my hosting provider, I can not use rsync unfortunately. So I have to look for other containers, but maybe this helps you.
February 17, 20215 yr On 1/2/2021 at 12:26 AM, Maginos said: @killeriq Were you able to install weewx in unraid? Of course one could create a small vm on e. g. dietpi base and install weewx there, but the solution we'd prefer would be the docker container. nope , in the end i sort it our without Weewx
February 5, 20224 yr anybody got it running ? can somebody tell me the config which is needed for weewx ?
February 6, 20224 yr 17 hours ago, Curtis777 said: anybody got it running ? can somebody tell me the config which is needed for weewx ? @Curtis777 I personally like the solution with the dedicated dietpi vm. It's actually very lightweight and you're more flexible for example in terms of extensions. So to be honest, I'm quite happy with it and I won't switch to the docker container.
August 3, 20223 yr A weewx container showed up in the CA store today. I went to install it and got an error… I’m guessing for USB pass through? I haven’t used any containers that needed usb access so it sure how that works on unraid. My error: Error response from daemon: error gathering device information while adding custom device "/dev/ttyUSB0": no such file or directory.
August 3, 20223 yr 2 hours ago, BirdHeezy said: A weewx container showed up in the CA store today. I went to install it and got an error… I’m guessing for USB pass through? I haven’t used any containers that needed usb access so it sure how that works on unraid. My error: Error response from daemon: error gathering device information while adding custom device "/dev/ttyUSB0": no such file or directory. Seems like a error from the missing USB device indeed. Try to edit your docker, go down the page to "Add another Path, Port, Variable, Label or Device" and select "Config Type: device". For "Name" you can write "weather station" and for "Value" you can use "/dev/ttyUSB0". I hope with this you get rid of the error.
August 4, 20223 yr 21 hours ago, Maginos said: Seems like a error from the missing USB device indeed. Try to edit your docker, go down the page to "Add another Path, Port, Variable, Label or Device" and select "Config Type: device". For "Name" you can write "weather station" and for "Value" you can use "/dev/ttyUSB0". I hope with this you get rid of the error. Thanks for the reply! that variable has already been setup. This may be a silly question, but do I have to have my usb device plugged in? I don’t know how to define/point the container to a specific USB port… or if that’s something I even need to do. Guess it’s time I did some googling on usb devices and unraid containers!
August 4, 20223 yr 3 hours ago, BirdHeezy said: Thanks for the reply! that variable has already been setup. This may be a silly question, but do I have to have my usb device plugged in? I don’t know how to define/point the container to a specific USB port… or if that’s something I even need to do. Guess it’s time I did some googling on usb devices and unraid containers! So I played around with my USB weather station a bit and unfortunately I was not able to get the weewx container running. Under "Tools", "System Devices", "USB Devices", I identified my weather station to be located at Bus 001 Device 006, so the corresponding device path should be /dev/bus/usb/001/006. I tried different paths for the MQTT device, but nothing worked. I also tried to passthrough the USB device via the extra parameter setting, but without luck. Maybe the problem is within the correct device path... I also tried to bypass the need for an USB device by changing the /mnt/user/appdata/weewx/weewx.conf in the following way: I set "station_type = simulator", but without luck. As mentioned above, I like the dietpi vm better for weewx, as it is comparably lightweight to a docker container but with the options for extensions for example.
August 16, 2025Aug 16 Spent all day today getting the weewx container to work. I am putting down some of the pitfalls I encountered here hoping it will be useful to anyone in the future.Remove MQTT usb device mapping: if not passing through any device remove the mappingFix the appdata folder permission: after hitting install in the community app, it will try to create the "weewx" folder in appdata. However, the folder need manual permission fix. I just gave it 777.Running the container for the first time: after fixing the folder permission, start the container. This time it will generate weewx.conf file and many other stuff, and the container will exit out. Leave the weewx.conf file unmodified for now. it will default to simulator driver. Start the container again, and it should run normal now.Install paho-mqtt module: MQTT extension requires a specific paho-mqtt module (see here). Open the container console, cd to /data folder, and run the pip commandpip install paho-mqtt==1.6.1 Install extension: the container description said it comes bundle with Interceptor and mqtt, however, I found it not being the case. Extensions need manual install by using weectl command. Since the weewx.conf is not in the default location. --config=/path/to/weewx.conf option is needed. Open the container console and run the weectl command like the example below.weectl extension install <extension url> --config=/data/weewx.confMQTT: https://github.com/matthewwall/weewx-mqtt/archive/master.zipInterceptor: https://github.com/matthewwall/weewx-interceptor/archive/master.zipPay attention to the owner/permission of weewx.conf: the container should still be running without any error up to this point. Now we can stop the container and start modifying the weewx.conf. Before editing the file, note down the owner and permission of the file. I noticed this changing depending on how you edit the file. Don't forget to do Step 3 for MQTT extension.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.