Custom UI node not visible in dashboard-sidebar


Hi folks,

Got an issue on Github for my node-red-contrib-ui-heatmap node. After some discussions and digging into the code, it seems there are a few things incorrect in my node. ut I'm running out of ideas ...

This is the first problem:

The node needs to be added to some group (which in turn is located on some tab):

But when you do that, my node doesn't become visible in the dashboard sidebar:

P.S. In the dashboard itself, my node is nicely visible in the specified group (and tab)...

Thanks !!



Try this...
Custom UI Node Not Appearing In Group In Dashboard SideTab

I had the same issue and the fix is not apparent.

1 Like


Thanks a lot !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Will try it this evening. Have lost quite some hours already on this issue, but nothing found ...



And if it works ... a Top Tip we need to make clear in the docs !!!



Indeed @dceejay.

I already had that nugget of information in my little node.

Check out the first couple of sections.

1 Like


:slight_smile: - yes - Thanks - I have added to the other examples as well.

1 Like


@seth350, @dceejay,
Some delay due to lack of time ...

Originally I had this:

RED.nodes.registerType('heat-map' ...);

Indeed when I change it to this:

RED.nodes.registerType('ui_heat_map' ...);

Then the UI node nicely appears in the dashboard tree:

Cool... Thanks again !

The disadvantage is that users who have already used the heatmap node in their flow, now will run into troubles:

And seems that 824 users have downloaded this node last month. Damn ...

1 Like


Well you can bump the version to a major release... as it's a breaking change... but yeah... we're all moving slowly forward on the ui widgets so not found all the "obvious" pitfalls, that we ought to know... many apologies...



Apologies not accepted :wink: The widget API is a huuuuuge step forward for contributors like me...

Had also been thinking about a major release, but not sure if the majority of users are aware what all the numbers in the version mean ... But that is the only thing I can do, and put a warning on the readme page (and info panel) so I can guide them around it.



Well if they used the palette manager to install things it will write the package.json so that major version changes won't install with npm update so they should stay working... until they force and update.

1 Like


I have analysed in my mind how users react on feature updates. What I found is that silently giving goodies works but mentioning reliability fails. Not always but somehow dominance can be noticed.

We need for sure more clearly explained starting point for custom ui-widget development but to do it, takes first to experiences of failures on the route. I happily gave some , so do you.

Main thing is not to keep them for ourselves but understanding them, collect and publish for community.