Mission Control is an experimental feature and it’s not enabled by default, in order to enable it, launch node-red
with the environment variable
REDBOT_ENABLE_MISSION_CONTROL=true node-red -u /my-node-red-project
or with Docker
docker run -d -p 1880:1880 -e REDBOT_ENABLE_MISSION_CONTROL=true guidone/redbot
or editing the Node-RED’s configuration file settings.js (generally located at ~/.node-red/settings.js
module.exports = {
// ...
// Node-RED configuration
// ...
RedBot: {
enableMissionControl: true
}
};
Then open the bot configuration in Node-RED (the image below is showing a Facebook Messenger configuration panel) and enable “Use Mission Control”, you can also specify a bot id (or a random one will be assigned)
The Mission Control panel is running - in the development box - at http://localhost:1880/mc
(default username and password: admin / admin) and it’s not connected to the bot “my-bot-id”.
<aside> 💡 The bot id is the unique identifier for a bot application, across different platforms, for example a Telegram bot and Facebook Messenger bot with the same bot id are using the same Mission Control’s panel.
</aside>