# Unable to install Chatbot from Hassio add-on

**URL:** https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581
**Category:** General
**Created:** [29 March 2019 16:56 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581 "2019-03-29T16:56:53Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![jbautomaion](https://avatars.discourse-cdn.com/v4/letter/j/919ad9/32.png) [@jbautomaion](https://discourse.nodered.org/u/jbautomaion)
#### Post date: [29 March 2019 16:56 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/1 "2019-03-29T16:56:54Z")

</div>

I started to install the chatbot module about a month ago and ran into issues. I posted this log over on the Home Assistance forums thinking that it might be something wrong or missing with the HomeAssistant add-on, but I didn't get any responses other than a couple of other users having the same issue. To my understanding, the npm install should install all of the pre-requisites but from looking at the logs that may not be the case. Below is the log (Edit: I updated with the log from the attempt today). Please let me know if you have any ideas I'm willing to try anything. Thanks in advance.

> 29 Mar 13:01:09 - [info] Installing module: node-red-contrib-chatbot, version: 0.16.6  
> 29 Mar 13:03:41 - [warn] Installation of module node-red-contrib-chatbot failed:  
> 29 Mar 13:03:41 - [warn] ------------------------------------------  
> 29 Mar 13:03:41 - [warn] npm WARN deprecated @types/p-cancelable@1.0.1: This is a stub types definition. p-cancelable provides its own type definitions, so you do not need this installed.  
> npm WARN deprecated @types/p-retry@3.0.1: This is a stub types definition. p-retry provides its own type definitions, so you do not need this installed.  
> npm WARN deprecated snekfetch@3.6.4: use node-fetch instead  
> npm WARN deprecated socks@1.1.10: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0  
> node-pre-gyp WARN Using request for node-pre-gyp https download  
> node-pre-gyp WARN Tried to download(404): [https://node-precompiled-binaries.grpc.io/grpc/v1.19.0/node-v64-linux-arm-musl.tar.gz](https://node-precompiled-binaries.grpc.io/grpc/v1.19.0/node-v64-linux-arm-musl.tar.gz)  
> node-pre-gyp WARN Pre-built binaries not found for grpc@1.19.0 and node@10.14.2 (node-v64 ABI, musl) (falling back to source compile with node-gyp)  
> gyp ERR! build error  
> gyp ERR! stack Error: not found: make  
> gyp ERR! stack at getNotFoundError (/usr/lib/node\_modules/npm/node\_modules/which/which.js:13:12)  
> gyp ERR! stack at F (/usr/lib/node\_modules/npm/node\_modules/which/which.js:68:19)  
> gyp ERR! stack at E (/usr/lib/node\_modules/npm/node\_modules/which/which.js:80:29)  
> gyp ERR! stack at /usr/lib/node\_modules/npm/node\_modules/which/which.js:89:16  
> gyp ERR! stack at /usr/lib/node\_modules/npm/node\_modules/isexe/index.js:42:5  
> gyp ERR! stack at /usr/lib/node\_modules/npm/node\_modules/isexe/mode.js:8:5  
> gyp ERR! stack at FSReqWrap.oncomplete (fs.js:154:21)  
> gyp ERR! System Linux 4.4.50  
> gyp ERR! command "/usr/bin/node" "/usr/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--library=static\_library" "--module=/config/node-red/node\_modules/grpc/src/node/extension\_binary/node-v64-linux-arm-musl/grpc\_node.node" "--module\_name=grpc\_node" "--module\_path=/config/node-red/node\_modules/grpc/src/node/extension\_binary/node-v64-linux-arm-musl" "--napi\_version=3" "--node\_abi\_napi=napi" "--napi\_build\_version=0" "--node\_napi\_label=node-v64"  
> gyp ERR! cwd /config/node-red/node\_modules/grpc  
> gyp ERR! node -v v10.14.2  
> gyp ERR! node-gyp -v v3.8.0  
> gyp ERR! not ok  
> node-pre-gyp ERR! build error  
> node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node\_modules/npm/node\_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --library=static\_library --module=/config/node-red/node\_modules/grpc/src/node/extension\_binary/node-v64-linux-arm-musl/grpc\_node.node --module\_name=grpc\_node --module\_path=/config/node-red/node\_modules/grpc/src/node/extension\_binary/node-v64-linux-arm-musl --napi\_version=3 --node\_abi\_napi=napi --napi\_build\_version=0 --node\_napi\_label=node-v64' (1)  
> node-pre-gyp ERR! stack at ChildProcess. (/config/node-red/node\_modules/grpc/node\_modules/node-pre-gyp/lib/util/compile.js:83:29)  
> node-pre-gyp ERR! stack at ChildProcess.emit (events.js:182:13)  
> node-pre-gyp ERR! stack at maybeClose (internal/child\_process.js:962:16)  
> node-pre-gyp ERR! stack at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:251:5)  
> node-pre-gyp ERR! System Linux 4.4.50  
> node-pre-gyp ERR! command "/usr/bin/node" "/config/node-red/node\_modules/grpc/node\_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" "--library=static\_library"  
> node-pre-gyp ERR! cwd /config/node-red/node\_modules/grpc  
> node-pre-gyp ERR! node -v v10.14.2  
> node-pre-gyp ERR! node-pre-gyp -v v0.12.0  
> node-pre-gyp ERR! not ok  
> npm WARN discord.js@11.4.2 requires a peer of bufferutil@^3.0.3 but none is installed. You must install peer dependencies yourself.  
> npm WARN discord.js@11.4.2 requires a peer of erlpack@discordapp/erlpack but none is installed. You must install peer dependencies yourself.  
> npm WARN discord.js@11.4.2 requires a peer of node-opus@^0.2.7 but none is installed. You must install peer dependencies yourself.  
> npm WARN discord.js@11.4.2 requires a peer of opusscript@^0.0.6 but none is installed. You must install peer dependencies yourself.  
> npm WARN discord.js@11.4.2 requires a peer of sodium@^2.0.3 but none is installed. You must install peer dependencies yourself.  
> npm WARN discord.js@11.4.2 requires a peer of libsodium-wrappers@^0.7.3 but none is installed. You must install peer dependencies yourself.  
> npm WARN discord.js@11.4.2 requires a peer of uws@^9.14.0 but none is installed. You must install peer dependencies yourself.  
> npm ERR! code ELIFECYCLE  
> npm ERR! errno 1  
> npm ERR! grpc@1.19.0 install: `node-pre-gyp install --fallback-to-build --library=static_library`  
> npm ERR! Exit status 1  
> npm ERR!  
> npm ERR! Failed at the grpc@1.19.0 install script.  
> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.  
> npm ERR! A complete log of this run can be found in:  
> npm ERR! /root/.npm/\_logs/2019-03-29T17\_03\_41\_438Z-debug.log  
> 29 Mar 13:03:41 - [warn] ------------------------------------------

---

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [29 March 2019 17:24 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/2 "2019-03-29T17:24:34Z")

</div>

Its trying to build the software but hasn't got the tools to do so.

What operating system are you running this on?

---

<div class="post-metadata">

### Author: ![jbautomaion](https://avatars.discourse-cdn.com/v4/letter/j/919ad9/32.png) [@jbautomaion](https://discourse.nodered.org/u/jbautomaion)
#### Post date: [29 March 2019 17:29 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/3 "2019-03-29T17:29:27Z")

</div>

Running under HassIO on a raspberry pi 3. Node red is running and has been up and running for a while now on the install. I also have several other modules loaded in the Node-red environment. If you need any other info just let me know.

---

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [29 March 2019 17:40 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/4 "2019-03-29T17:40:35Z")

</div>

Not all nodes need to be built, but if they do they need the tools to build them.  
Not sure how you get them on HassIO, its probably a question for their forum.

How to do it on Raspbian is listed [https://nodered.org/docs/hardware/raspberrypi](https://nodered.org/docs/hardware/raspberrypi)

---

<div class="post-metadata">

### Author: ![jbautomaion](https://avatars.discourse-cdn.com/v4/letter/j/919ad9/32.png) [@jbautomaion](https://discourse.nodered.org/u/jbautomaion)
#### Post date: [29 March 2019 17:46 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/5 "2019-03-29T17:46:48Z")

</div>

Awesome! Thank you for the response. I will add these notes to the post over in the HassIO forums and see if I get any bites there. I am wondering if there is an add-on that they have to include these tools, since it does not have access to the command line. I will definitely check that out thanks for the info. What tools specifically am I looking for?

---

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [29 March 2019 18:10 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/6 "2019-03-29T18:10:31Z")

</div>

Well your error post says it can't find `make` , the post I linked to includes the following:

> On really minimal Debian installs you may need to run sudo apt-get install build-essential before running the script so that the serialport builds and installs OK. This is optional.

---

<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: [30 March 2019 06:59 UTC](https://discourse.nodered.org/t/unable-to-install-chatbot-from-hassio-add-on/9581/7 "2019-03-30T06:59:09Z")

</div>

Sometimes you also need the python2.7-dev package, but generally build-essential should be enough.
