guidone/node-red-contrib-chatbot

Mission Control in Home Assistant

Closed this issue · 16 comments

smcnab1 commented

Got chatbot working in HA Node-RED. However, I can't seem to get mission control working. I have it in my settings.js as

module.exports = {
  enableMissionControl: true,
  // Retry time in milliseconds for MQTT connections
  mqttReconnectTime: 15000,
  // Retry time in milliseconds for Serial port connections
  serialReconnectTime: 15000,

Doesn't give me option to tick box to enable for some reason.

guidone commented

Can you see the logs?

guidone commented

Did you try adding the env variable to the docker image

REDBOT_ENABLE_MISSION_CONTROL=true

smcnab1 commented

Overnight it seems to have uninstalled itself. Attempted to follow #473 instructions again and now being presented with the below logs when trying to install chatbot.


-----------------------------------------------------------
2022-09-24T10:39:53.361Z Install : node-red-contrib-chatbot 1.0.8

2022-09-24T10:39:53.556Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-chatbot@1.0.8
2022-09-24T10:39:56.155Z [err] npm
2022-09-24T10:39:56.160Z [err]  
2022-09-24T10:39:56.162Z [err] WARN
2022-09-24T10:39:56.163Z [err]  
2022-09-24T10:39:56.164Z [err] config
2022-09-24T10:39:56.164Z [err]  production Use `--omit=dev` instead.
2022-09-24T10:42:39.080Z [err] npm
2022-09-24T10:42:39.081Z [err]  WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
2022-09-24T10:42:42.551Z [err] npm 
2022-09-24T10:42:42.553Z [err] WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
2022-09-24T10:42:42.937Z [err] npm 
2022-09-24T10:42:42.938Z [err] WARN deprecated har-validator@5.1.5: this library is no longer supported
2022-09-24T10:42:44.163Z [err] npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
2022-09-24T10:42:46.722Z [err] npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
2022-09-24T10:42:48.282Z [err] npm WARN deprecated
2022-09-24T10:42:48.283Z [err]  source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
2022-09-24T10:42:59.791Z [err] npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
2022-09-24T10:42:59.871Z [err] npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
2022-09-24T10:43:04.164Z [err] npm WARN 
2022-09-24T10:43:04.164Z [err] deprecated formidable@1.0.17: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
2022-09-24T10:43:04.205Z [err] npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2022-09-24T10:43:04.209Z [err] npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2022-09-24T10:43:04.214Z [err] npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2022-09-24T10:43:04.220Z [err] npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
2022-09-24T10:43:09.199Z [err] npm WARN deprecated mkdirp@0.3.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
2022-09-24T10:43:15.547Z [err] npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
2022-09-24T10:43:20.184Z [err] npm WARN deprecated express@2.5.11: express 2.x series is deprecated
2022-09-24T10:43:30.848Z [err] npm 
2022-09-24T10:43:30.851Z [err] WARN deprecated subscriptions-transport-ws@0.9.19: The `subscriptions-transport-ws` package is no longer maintained. We recommend you use `graphql-ws` instead. For help migrating Apollo software to `graphql-ws`, see https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws    For general help using `graphql-ws`, see https://github.com/enisdenjo/graphql-ws/blob/master/README.md
2022-09-24T10:43:41.817Z [err] npm WARN deprecated
2022-09-24T10:43:41.818Z [err]  bson@1.0.9: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details
2022-09-24T10:43:41.890Z [err] npm WARN deprecated connect@1.9.2: connect 1.x series is deprecated
2022-09-24T10:43:49.224Z [err] npm
2022-09-24T10:43:49.225Z [err]  
2022-09-24T10:43:49.226Z [err] WARN
2022-09-24T10:43:49.227Z [err]  
2022-09-24T10:43:49.227Z [err] deprecated
2022-09-24T10:43:49.228Z [err]  graphql-tools@4.0.8: This package has been deprecated and now it only exports makeExecutableSchema.\nAnd it will no longer receive updates.\nWe recommend you to migrate to scoped packages such as @graphql-tools/schema, @graphql-tools/utils and etc.\nCheck out https://www.graphql-tools.com to learn what package you should use instead
2022-09-24T10:43:51.004Z [err] npm WARN deprecated sequelize@5.22.5: Please update to v6 or higher! A migration guide can be found here: https://sequelize.org/v6/manual/upgrade-to-v6.html
2022-09-24T10:44:24.443Z [err] npm
2022-09-24T10:44:24.444Z [err]  WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2022-09-24T10:44:24.454Z [err] npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
2022-09-24T10:44:24.458Z [err] npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
smcnab1 commented

Did you try adding the env variable to the docker image

REDBOT_ENABLE_MISSION_CONTROL=true

I added the above to settings.js but still didn't activate.

guidone commented

Mmm these are just warnings.

I cannot test home assistant right now, I've not with me the raspberry.

Don't know very well HA (honestly I don't like it very much), if I'm not wrong it runs these extensions in a docker image. It would be much easier to run RedBot directly using the Docker image

https://hub.docker.com/r/guidone/redbot

I'll check in the next days

smcnab1 commented

Do you know of a way to run on a seperate RPi on docker and somehow connect to HA on a different Pi? Apart from that may need to work without Mission Control

guidone commented

Not sure I've understood what you need, very little knowledge on HA.

Just checked and enableMissionControl doesn't work on my local installation too, will fix soon

guidone commented

Ok, luckily for me the bug is in the documentation, to enable Mission Control from the settings file

module.exports = {
  // Node-RED config
  RedBot: {
    enableMissionControl: true
  }
}

the updated doc: https://www.notion.so/redbot/Enable-Mission-Control-7327f353a25c40a48a12349d10a5d150

smcnab1 commented

Got mission control available on node-red. When I go to http://homeassistant.local:1880/mc I get the following in the web page.

Same goes for when I try http://IP:1880/mc

Cannot GET /mc

guidone commented
smcnab1 commented

Yeah available at homeassistant.local:1880/mc

guidone commented

I've been trying to install HA locally for more than an hour without success.
I hate HA, I'll try later

guidone commented

Finally installed with node-red and redbot, were you able to set the env variable?

smcnab1 commented

I have installed externally of my HA install with Docker and have been able to. Wasn't able to do through HA locally as HA OS install

guidone commented

Thanks @smcnab1

Ok, after spending hours trying to install HA and running Node-RED on it, then RedBot, then trying to some basic configuration on RedBot + Node-RED with, I hit the wall of HomeAssistant ingress, it's blocking everything.

So long story short:

1 - RedBot is working under HA, Mission Control is working, but you just can't get to it, HA is blocking it
2 - I will never spend an additional minute on HA, I don't like it and I don't see a reason why someone would run Node-RED inside HA
3 - Run RedBot as separate Docker container

  • 😄1
john-trn commented

Has someone made it work with Node Red as HA Addon? It's useful because you can make easy use of all HA entities etc...
I can access MC at http://localhost:1880/mc but admin/admin is not working.