Discussions are open, come help shape NetPulse #478
Replies: 3 comments 2 replies
|
Hello, looks really nice. Something I was looking for, since a long time. Can you tell, if Fritzbox 4040 and Google Wifi devices are supported also? thanks |
|
Really like this project. Go single static binary, read-only by design, PWA frontend — solid stack, and my one gap is no Home Assistant, ESPHome, MQTT, RouterOS, OPNsense, or Proxmox support yet. @fsolak47 I think NetPulse should target devices like FritzBox or Google WiFi too, just not as a priority. Once the core is solid, it could reach them via a headless browser client that logs in and reads data the way a human would through the web UI, not overly complex. Since it's vibe-coded, I'm guessing it's still early with plenty of room to grow. Down the line, a native iOS/Android app for management and notifications would be great, and AI integration, like a dedicated agent that monitors 24/7 via NetPulse, would be a nice bonus. Big potential here. I'd like to help push it forward with my own resources, since I'm also interested in running NetPulse in production myself. On auto firmware upgrades, my view has shifted over the years. As a junior I loved it; as a senior I'm wary of breaking things without a real reason like a security fix or fatal bug. Firmware behavior varies a lot by device, and on routers that's risky when they're handling production traffic for a business. I'd support having firmware upgrades available through NetPulse, but handled carefully and made very clear to users. |
|
thank you. |
|
All OpenWRT devices should be supported. If not, drop an issue, please. |
|
Thank you @samex and @fsolak47 for your comments. As this idea (and original code) come from long time but now I have the time and resources to boost the development, I wanna try to focus in make it work with openwrt, stable for all users and then let's see. There's always room for other integrations if make sense, but closed source solutions won't be any priority. Of course if there are some people helping and using that will make things faster. :) |
Uh oh!
There was an error while loading. Please reload this page.
Discussions are enabled as of today. The idea came from #473, and it was a good one: the OpenWrt forum thread works, but it wanders, and a feature request can end up buried thirty replies deep under an unrelated argument about Wi-Fi drivers. Issues are the right tool for bugs with logs and reproduction steps. They are a poor fit for "wouldn't it be nice if" conversations, which deserve better than getting closed as not-a-bug.
So this is the place for those conversations now.
What belongs here:
Post ideas under Ideas and questions under Q&A; general chatter fits fine in General.
If you are new to the project: NetPulse is a read-only dashboard for OpenWrt and GL.iNet home networks. A small Go agent runs on each router and pushes to a Go server with a React frontend, so you get fleet status, per-router health, devices and leases, WireGuard peers, AdGuard Home stats and alerts streamed over SSE. The agent and the LuCI app ship as APK v3 and ipk packages, and the server runs on whatever spare box or LXC you have. Landing page and live demo: https://netpulse.cloudless.club
The reason I am glad this exists: the last few releases came almost entirely from user feedback. Password change, clipboard in insecure contexts, real APK v3 packages, release assets that actually attach. That feedback arrived scattered across a forum thread and a handful of issues, and every piece of it shipped. Bring more of it here and NetPulse gets better for everyone running it.
All reactions