Now that I have tinkered with Node Red and more recently UIBuilder over the past few weeks, I thought I would share my progress to date, mostly to get feedback and critique while possibly giving others some ideas based on my own designs.
First a bit of history on how I got to being here, in the Node Red community that is.
Having started out many years ago tinkering with all things electronics, both analogue and digital together with learning the various programming languages, from assembler through to C/C++ and more recently in the past years Python and common web language tools, I now find myself quite enchanted with using Node Red.
So, end of 2025 I made the effort to learn more about Node Red, first as an add-on to a Home-Assistant setup I got going and then seeing HA was not going to meet my needs, swapping over to Node Red as my core base.
I should say at this point, my use case is my own off grid energy system I have here in the cabin on the sunny side of a mountain on the little island I call home. A real system that is important for my state of sanity. A solar system based on Victron equipment and 20kWh of LiFePO4 cells.
I could speak about this in another topic.
Okay, so now visualisation, how best to do this I wondered. After a light bit of reading it was Dashboard 2 initially. After more reading and many errors I made quite a nice and workable dashboard using Dashboard 2.
But then I could see I was going to hit impassable walls fairly quickly once again, what to do ?
Enter UIBUILDER, yes, I thought. More reading on UIBUILDER from TotallyInformation, which was really starting to get me excited with the possibilities, so I dived in and pulled apart the example flows. I was mostly interested in the full client side logic single page application SPA) concept.
UIBUILDER was presented as a way to allow you to code and created your own visual component in the way you wish, with the help of a good selection of uibuilder helper nodes, could things get any better ?
Okay, so my Node Red lives on a little industrial RPi based machine, a compute module 4 (CM4), and the hardware is made by SeedStudio: reComputer R1125
This box of tricks is quite the beast, rugged and reliable. As an aside, I use these in my industrial projects working in the hot and dusty environments of north western Australia in mining projects.
Anyhow, this is what I have mounted on DIN rail near my off grid solar system playing Node Red server.
Back to visualisation: After some more tinkering I thought to myself, could I slip in my existing front end code base I had developed over the years. Answer, absolutely yes.
My existing front code makes use of only a couple of small helper libraries, namely one to bind data between my objects held by the main Javascript and the HTML being displayed. The other is a small front end router. These two libraries are tinybind.js and routie,js.
I looked at how I do things and how best I could wrangle my code to fit in with UIBUILDER eco-system and found it was best to continue to use both these libraries.
Tinybind offers nice features and is easy to implement the bound data to HTML.
Routie, the front end router, while probably quite similar to the router in uibuilder, allows me to do a few other things. Importantly, when I load up HTML to be placed into the router content section, I also need to load up a corresponding js file. For me, this is important, to have loaded content comprising both HTML and a Javascript module.
The js module holds the code needed explicitly for that HTML visual component. It gets cleanly destroyed on route change to avoid a runaway heap and reduce loading on browser garbage collection processes.
@TotallyInformation, can the router in UIBULDER handle loading of js modules together with the HTML like this ?
Next post - a few screen captures from a live system.
Please, if people have suggestions or questions, do write.









