# Mui\_text not working

**URL:** <https://discourse.nodered.org/t/mui-text-not-working/26812>\
**Category:** Dashboard\
**Created:** [17 May 2020 17:25 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812 "2020-05-17T17:25:15Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![tatuiot](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tatuiot/32/22200_2.png) [@tatuiot](https://discourse.nodered.org/u/tatuiot)\
**Post date:** [17 May 2020 17:25 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/1 "2020-05-17T17:25:15Z")

</div>

Hi team, I have been fighting with this issue for a couple of days , but no success so far.  
I have this simple mui dashboard (localhost:1880/mui), mui\_text does not display data at all. Running v0.20.5 in ubuntu linux 18.04 with node v13.12.0

the wired thing here is that mui\_button, mui\_slide, mui\_switch work fine... I am lost

```auto
[{"id":"c7830b2e.c14868","type":"tab","label":"UPDATE MQTT DEVICE","disabled":false,"info":""},{"id":"c6d8f038.e3e65","type":"inject","z":"c7830b2e.c14868","name":"Reboot","topic":"WTF","payload":"{\"deviceId\":6742829,\"ip\":\"192.168.100.59\",\"rssi\":-55,\"msgCount\":5903,\"reportInterval\":10,\"ledBlink\":false,\"ledState\":1}","payloadType":"json","repeat":"","crontab":"","once":true,"onceDelay":0.1,"x":398,"y":223,"wires":[["5743c07d.388a4","5862eb0f.df0124"]]},{"id":"5743c07d.388a4","type":"mui_text","z":"c7830b2e.c14868","group":"d17ec657.4f6158","order":3,"width":0,"height":0,"name":"commandResponse","label":"TBD","format":"{{payload.ip}}","layout":"row-spread","x":615,"y":287,"wires":[]},{"id":"5862eb0f.df0124","type":"debug","z":"c7830b2e.c14868","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":578,"y":221,"wires":[]},{"id":"d17ec657.4f6158","type":"mui_group","z":"","name":"Telemetry","tab":"b07cd333.4fc05","order":2,"disp":true,"width":"6","collapse":true},{"id":"b07cd333.4fc05","type":"mui_tab","z":"","name":"Telemetry","icon":"dashboard","order":2,"disabled":false,"hidden":false}]

```

any hint, where could be the error?

I tested with ui\_text in a different dashbord (localhost:1880/ui) and it works fine

Thanks in advance

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [17 May 2020 17:42 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/2 "2020-05-17T17:42:25Z")

</div>

You should only have one dashboard installed at a time to prevent conflicts. So either use node-red-dashboard or node-red-contrib-mdashboard but not both at once.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 May 2020 17:46 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/3 "2020-05-17T17:46:06Z")

</div>

I don't know anything about that dashboard, but you are using a fairly old version of node-red and a too-new version of nodejs. Nodejs should be 8, 10 or 12 (the LTS versions). Many nodes will not be compatible with v 13 I imagine.  
The easiest way to get a consistent set of tools is to remove nodejs then run the [recommended install script](https://nodered.org/docs/getting-started/raspberrypi) (it is promoted as for the Pi but works well with other Debian based systems, including Ubuntu).  
When posting a flow please see [How to share code or flow json](https://discourse.nodered.org/t/how-to-share-code-or-flow-json/506/4) for how to do it, otherwise your flow will not be importable.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [17 May 2020 17:51 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/4 "2020-05-17T17:51:57Z")

</div>

@colin, for simple things like Dashboard nodejs 13 should be ok... It's not recommended for nodes that have a binary component as sometimes they don't compile correctly.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 May 2020 18:08 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/5 "2020-05-17T18:08:18Z")

</div>

> [@dceejay](#):
>
> for simple things like Dashboard nodejs 13 should be ok

No doubt that is true, but is it not always a good idea to point out to people when they are using non-recommended versions of the infrastructure?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [17 May 2020 18:38 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/6 "2020-05-17T18:38:22Z")

</div>

Yes. But uninstalling nodejs , reinstalling , and rebuilding is more fraught than just uninstalling a node, especially when it is unlikely to be the root cause.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 May 2020 20:57 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/7 "2020-05-17T20:57:18Z")

</div>

I had missed the significance of the comment about the usual dashboard, that it likely means that both are installed at the same time. That is not explicitly stated but I suspect that in fact both are installed. @zenofmud's post clashed with mine so I had not seen it when I posted.

---

<div class="post-metadata">

**Author:** ![tatuiot](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tatuiot/32/22200_2.png) [@tatuiot](https://discourse.nodered.org/u/tatuiot)\
**Post date:** [17 May 2020 22:08 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/8 "2020-05-17T22:08:59Z")

</div>

Hi, thanks everyone for replying with comments and suggestions, so far, I've updated node-red version to 1.0.6, and nodejs back to 12.16.3 running the RPi script , need to modfy the path from /usr/bin to /usr/local/bin in /etc/systemd/system/node-red.service script.  
Unistalled both dashboard & mdashboard, installed mdashboard, restarted everything, but nothing new, still facing the same issue. I'll keep on trying to see if I can make it work, but your comments helped a lot... thanks

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [18 May 2020 07:55 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/9 "2020-05-18T07:55:35Z")

</div>

> [@tatuiot](#):
>
> /usr/bin to /usr/local/bin in /etc/systemd/system/node-red.service

That is the wrong file, it is nodered.service, not node-red.service.

Can you post the startup log when you run  
`node-red-stop`  
`node-red-start`  
in case there is anything there that might prove helpful for the dashboard problem.

---

<div class="post-metadata">

**Author:** ![tatuiot](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tatuiot/32/22200_2.png) [@tatuiot](https://discourse.nodered.org/u/tatuiot)\
**Post date:** [18 May 2020 12:40 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/10 "2020-05-18T12:40:36Z")

</div>

Hi, thanks, about nodered.service (it was my original implementation , that is why the name is not the original )  
Here is the output from node-red-logs  
18 May 09:34:44 - [info] Dashboard up and running  
Mon, 18 May 2020 12:34:45 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.  
In the future, you will have to enable it yourself.  
See [https://github.com/yagop/node-telegram-bot-api/issues/319](https://github.com/yagop/node-telegram-bot-api/issues/319). at internal/modules/cjs/loader.js:1133:30  
Missing ENV var CONFIG\_PATH  
Stopping Node-RED graphical event wiring tool...  
18 May 09:34:49 - [info] mDashboard version 2.19.4-beta started at /mui  
18 May 09:34:50 - [warn] ------------------------------------------------------  
18 May 09:34:50 - [warn] [node-red-contrib-socketio-client/socketio-client] Type already registered  
18 May 09:34:50 - [warn] [node-red-contrib-googlechart/googlechart] Error: Cannot find module '/usr/local/lib/node\_modules/node-red/red/red'  
Require stack:

- /home/tatu/.node-red/node\_modules/node-red-contrib-googlechart/googlechart.js
- /usr/local/lib/node\_modules/node-red/node\_modules/@node-red/registry/lib/loader.js
- /usr/local/lib/node\_modules/node-red/node\_modules/@node-red/registry/lib/index.js
- /usr/local/lib/node\_modules/node-red/node\_modules/@node-red/runtime/lib/nodes/index.js
- /usr/local/lib/node\_modules/node-red/node\_modules/@node-red/runtime/lib/index.js
- /usr/local/lib/node\_modules/node-red/lib/red.js
- /usr/local/lib/node\_modules/node-red/red.js  
18 May 09:34:50 - [warn] ------------------------------------------------------  
18 May 09:34:50 - [info] Settings file : /home/tatu/.node-red/settings.js  
18 May 09:34:50 - [info] Context store : 'default' [module=memory]  
18 May 09:34:50 - [info] User directory : /home/tatu/.node-red  
18 May 09:34:50 - [warn] Projects disabled : editorTheme.projects.enabled=false  
18 May 09:34:50 - [info] Flows file : /home/tatu/.node-red/flows\_tatuiot.com.json  
Stopped Node-RED graphical event wiring tool.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [18 May 2020 13:06 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/11 "2020-05-18T13:06:50Z")

</div>

Could you use the node-red-start/stop command please. I can only assume that is why some of the startup messages are missing.

My approach is always to fix the obvious problems before trying to fix the more tricky ones. So I suggest sorting out the socketio and google charts problems first.  
You seem to have installed two nodes providing socketio, so remove one of them. Also remove googlechart. If you need it then try re-installing.

---

<div class="post-metadata">

**Author:** ![tatuiot](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tatuiot/32/22200_2.png) [@tatuiot](https://discourse.nodered.org/u/tatuiot)\
**Post date:** [24 May 2020 17:08 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/12 "2020-05-24T17:08:29Z")

</div>

Hi, after some time searching for optimal solution, I decided to move to "uibuilder" node , which provide much more flexibility and extendebility (I might have invented a whole new word) so, for now mui-dashboard is on hold. Thanks for your support and help. If I ever get back to mui-dashboard I'll try again ... and let you know how it went.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [23 June 2020 17:08 UTC](https://discourse.nodered.org/t/mui-text-not-working/26812/13 "2020-06-23T17:08:35Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.