Odd status text from e-mail and mqtt nodes

General
1

I have been re-factoring some of my flows to make better use of node status messages and have run into a few quirks and possible bugs. I will try to post about them over the next few days. Here is the first.

19 Aug 19:30:10 - [info] Node-RED version: v0.20.6
19 Aug 19:30:10 - [info] Node.js version: v8.11.2
19 Aug 19:30:10 - [info] Darwin 18.7.0 x64 LE

With this flow,

[{"id":"f6acdf91.d5683","type":"status","z":"d141e924.5365a8","name":"status:mqtt","scope":["8b571501.8e06c","56474d5.75b57b4"],"x":270,"y":100,"wires":[["4aef2ae4.569564"]]},{"id":"4aef2ae4.569564","type":"debug","z":"d141e924.5365a8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"status","targetType":"msg","x":450,"y":100,"wires":[]},{"id":"56474d5.75b57b4","type":"mqtt out","z":"d141e924.5365a8","name":"","topic":"","qos":"","retain":"","broker":"74015cbe.beb164","x":110,"y":60,"wires":[]},{"id":"4f2b7cdb.58c2fc","type":"e-mail in","z":"d141e924.5365a8","name":"","protocol":"IMAP","server":"imap.gmail.com","useSSL":true,"port":"993","box":"INBOX","disposition":"Read","criteria":"UNSEEN","repeat":"300","fetch":"auto","inputs":0,"x":110,"y":220,"wires":[[]]},{"id":"c0636354.a988b","type":"status","z":"d141e924.5365a8","name":"status:email","scope":["4f2b7cdb.58c2fc"],"x":270,"y":220,"wires":[["56c02f7a.076c88"]]},{"id":"56c02f7a.076c88","type":"debug","z":"d141e924.5365a8","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"status","targetType":"msg","x":450,"y":220,"wires":[]},{"id":"8b571501.8e06c","type":"mqtt in","z":"d141e924.5365a8","name":"","topic":"/","qos":"2","datatype":"auto","broker":"74015cbe.beb164","x":110,"y":140,"wires":[[]]},{"id":"74015cbe.beb164","type":"mqtt-broker","z":"","name":"","broker":"test","port":"1883","clientid":"","usetls":false,"compatmode":true,"keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthRetain":"false","birthPayload":"","closeTopic":"","closeQos":"0","closeRetain":"false","closePayload":"","willTopic":"","willQos":"0","willRetain":"false","willPayload":""}]

on startup or restart, the e-mail and mqtt nodes display the correct status in the editor, but the status node connected to the e-mail node receives the status text
"email.status.connecterror", and the one connected to the mqtt nodes receives "node-red:common.status.connecting". I suspect this comes from a problem in retrieving the proper strings from a lookup, and the developers will know exactly where to look.:grinning:

2

You are right to say they are message catalog identifiers but that is not a bug.

If you have a flow that checks the status value, you wouldn't want it to have to check the value in japanese, german or chinese depending on what locale you happened to be running in.

3

I guess that makes sense. Still, it's a bit strange to see the editor display "connecting" but having to translate from "node-red:common.status.connecting" in order to display in the dashboard. Is there a way to do the lookup in a function or change node?