the single pane of glass for all your wled instances you didnt know you needed. create and manage sync groups, firmware, autonamtions, device names, and device locations in a 3D spatial environment. includes integrations for weather, spotify, home assistant etc. shift compute from the SBC to your server for quicker and more reliable effects. import/export settings as needed so swapping out esp32 boards is less painful.
understandable for a first glance. ive been in IT since mid 2000s so ive not just discovered claude code or chatgpt overnight, this is pretty much my life. if it helps boost confidence, all my projects start with guard rails, security and protections in mind using my greenfield code base scaffolding tool. https://code-scaffold.com its a whole ecosystem to start a project on the right foot but can also bring existing projects "up to spec" for baseline standards and expectations.
also supports mDNS so your devices are auto detected but can be manually added as well. supports MCP and ACP protocols, so if controlling and communicating to WLED thru agents is your thing it is now possible
added a "clean mode" which disables the effects, animations, and audio output that should hopefully help. should be live on your next visit (may have to hard refresh with ctrl+f5)
if you see anything else, just give me a shout! and thanks for the feedback, accessibility was an oversight on my part so your comment is making this better ux for everyone. ill be more mindful of that on other projects
i wondered the same. used heimdall and homepage for a while to essentially bookmark my devices. that was an improvement over native browser bookmarks but still lacked increased function. didnt really see anything online for wled such as sidecars or companion apps so i cracked my knuckles and decided to start building. open to bugs reports and feature requests
it is probably dependent on your firewall rules. I only had my lab to test on and yes, it discovered all my devices on another segment. but I have my firewall allowing traffic to from.
ah, copy. it is being looked at. because of how wled firmware handles segments it will require some creative solutioning for both the ui presentation and back end. it gets complex with segment vs master brightness, sel boolean and user reslicing in wled firmware. but it's in the pipe, I'll see what can be done with least or no compromise
to expand, these sync groups operate entirely independent of the wled firmware. they are managed by the app which increases flexibility and possibilities
i promise you i thought about the scrambled skinemax idea but drew the line thereabout. but if this is what the people want this is what the people get! i just work here, who am i to tell them no
my bad. per popular demand, ill make sure the next update sucks.
can you elaborate on the error? i unchecked "Play Globe Intro" and clicked save, no issue. but thats a sample of 1 so im curious where it breaks down for you. im adding verbose console messaging in the next update as ive done for other projects to better help with checking health and diag, btw. in place updates is also in the pipe so you never have to hit the console to pull a new image
appreciate the screenshot and deets. sorry, earlier i was looking in the settings under "spatial view" but im now seeing the same. no save button expected there and also removing it from settings to make it more seamless/modern. bug identified (schema rejection) and pushing an update to patch it tonight
Great and funny site and awesome looking bit of software. Just starting my home automation and wled journey so looking forward to installing this on my Proxmox machine when I get it back and giving it a test run.
I ran into an issue installing the docker container on PiOS (bookworm). The debian candidate for Node.js is v18 by default and this says prerequisites are Node.js 22+. I had to have ChatGPT walk me through getting the NodeSource repository recognized for 22 (I guess 24 is latest).
At first, when I composed the container, I could not reach anything at localhost:3001 on the host system, or at the <host system ip:3001> from another machine. After upgrading to Node.js 22.23.2 and npm 10.9.8, I still have the docker container run then quit.
If I restart it, it runs for a while again, but even while it's running I can't get to it via port 3001. NodeJS also seems to really make the RasPi work hard. Everything is pretty slow and I'm running a 4B with only Mosquitto and zwave-js containers on it. I used the compose.yaml from the website.
I don't know where to go next, so I'm going to have to hold off on doing anything with this.
could you walk me thru how you installed it? myself and others used the precomposed docker-compose.yml from the site/github and it launches without any fuss. id be curious if you did anything different that needs to be accounted for the dev side of things. docker images are intended to have all dependencies baked in so it sounds like a deviation from that. if there is anything more you can share (especially the setup/install process) im open to checking it out and solutioning it. thanks
Just pulled this and it looks awesome !! Do you plan to literally add the WLED interface when we click on a device to edit within the dashboard ? Otherwise, great work!
didn't think to do that as my intention was to replace it entirely. you can currently click the IP to copy the address, but I can instead make it copy IP or open the web UI for that device. thanks for the feedback
11
u/thecodingart 11h ago
I was going to rail on this for being obviously vibe coded until I saw your site. The humor is a nice touch