We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Hi everyone,
I’m Joe. I work in maintenance and process optimization in an industrial plant and I’m currently getting into LoRaWAN and condition monitoring.
I wanted to try Beaver IoT on my Proxmox home lab and noticed there wasn’t really anything here about running it on Proxmox. So I built a small one-command installer for it: github.com/dzeykop/proxmox-beaver-iot
You run one line on your Proxmox host. The script shows your host resources and the recommended values for Beaver IoT. It lets you choose CPU, RAM, disk, storage and network bridge. It creates a Debian 12 VM, installs Docker and starts Beaver IoT with the web UI and MQTT on port 1883. It also checks once a day for a new Beaver IoT version and shows a notice at SSH login. It never updates by itself: you decide with “sudo beaver-update”, including backup and rollback.
I’ve tested it on my own Proxmox setup and the installation runs through without problems. It’s a personal learning project and not an official Milesight tool.
I’d really appreciate any feedback. Does it work on your setup? Are the recommended resources sensible? Is there anything you’d like to see added, for example static IP or SSH key support?
If you try it, let me know how it went. Thanks!
Joe
0 Votes
1 Comments
Aslan Lu posted 2 days ago Admin
Hi Joe,
Thanks so much for putting this together and sharing it!
Having a streamlined Debian 12 + Docker VM installer for Proxmox makes spinning up Beaver IoT for testing much easier.
Giving users interactive resource selection and manual update control (
beaver-updatewith backup/rollback) is a very smart design choice—especially coming from an industrial maintenance background where predictable uptime matters.To answer your question on features: static IP configuration and SSH key support would definitely be the top two additions we'd love to see, since pointing LoRaWAN gateways/nodes to a fixed MQTT broker IP (port 1883) is usually step one.
If you want to get more eyes and hands-on feedback on the script, come share it in our Discord community! Our developers and many self-hosting/home lab users are active there—they’d love to try this out on their Proxmox nodes and chat about condition monitoring use cases with you:
Beaver IoT / Milesight Discord:https://discord.gg/ZKRFQvz8f
Thanks again for the great work, and hope to catch you in the server!
0 Votes
Login or Sign up to post a comment