iHost - NodeRed instalation failure

Hi, i’m new at home automattion.

I have an iHost running the 2.0.0 version, and when I try to install the nodered it simply donst install.
It starts the download and a few seconds later stops. It just happen with this addon.

See some imagens above.
1-

2-
image

Can someone help me with his please?

What kind of memory card do you have?

SanDisk Ultra 64GB

image

Adding more information.

Docker Logs:

e[32m[2024-06-20T18:58:16.850Z] [INFO] default -e[39m publish ==========> docker/addon/card/discover {“id”:24,“name”:“nodered/node-red”,“description”:“Low-code programming for event-driven applications”,“state”:0,“addSource”:“user”,“createAt”:1718909896834,“installAt”:null}
e[32m[2024-06-20T18:58:16.856Z] [INFO] default -e[39m [access] ihost.local - e350264b-edb8-4045-b25e-c1b3ec0b4599 - GET /api/v1/rest/docker/addons
e[32m[2024-06-20T18:58:16.858Z] [INFO] default -e[39m [access] ihost.local - e350264b-edb8-4045-b25e-c1b3ec0b4599 - 200:0 “2ms” “GET /api/v1/rest/docker/addons http/1.1” 2440 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:16.876Z] [INFO] default -e[39m [access] ihost.local - 0b4f0c00-4271-4e3f-b226-46f0d6f1b24f - GET /api/v1/rest/docker/addons
e[32m[2024-06-20T18:58:16.878Z] [INFO] default -e[39m [access] ihost.local - 0b4f0c00-4271-4e3f-b226-46f0d6f1b24f - 200:0 “1ms” “GET /api/v1/rest/docker/addons http/1.1” 2440 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:21.816Z] [INFO] default -e[39m [access] ihost.local - 3fc337a4-999d-4d50-90b9-4a4b20b8f447 - POST /api/v1/rest/docker/addons/24/install
e[32m[2024-06-20T18:58:21.817Z] [INFO] default -e[39m [receive] addon install =======> nodered/node-red
e[32m[2024-06-20T18:58:21.847Z] [INFO] default -e[39m [access] ihost.local - 3fc337a4-999d-4d50-90b9-4a4b20b8f447 - 200:0 “30ms” “POST /api/v1/rest/docker/addons/24/install http/1.1” 39 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:21.850Z] [INFO] default -e[39m [publish] =================> { state: 1, installAt: null, layerCount: null, pulledLayerCount: null } 0 1
e[32m[2024-06-20T18:58:21.851Z] [INFO] default -e[39m publish ==========> docker/addon/card/24/updated/install-state {“state”:1,“installAt”:null,“layerCount”:null,“pulledLayerCount”:null}
e[32m[2024-06-20T18:58:21.855Z] [INFO] default -e[39m [access] ihost.local - 084d308a-8419-4e1e-89d4-3364618bd40b - GET /api/v1/rest/docker/containers
e[32m[2024-06-20T18:58:21.860Z] [INFO] default -e[39m [access] ihost.local - 084d308a-8419-4e1e-89d4-3364618bd40b - 200:0 “4ms” “GET /api/v1/rest/docker/containers http/1.1” 4199 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:21.870Z] [INFO] default -e[39m [access] ihost.local - 9f6c951c-5da3-4893-9e11-0d1215171c69 - GET /api/v1/rest/docker/addons
e[32m[2024-06-20T18:58:21.872Z] [INFO] default -e[39m [access] ihost.local - 9f6c951c-5da3-4893-9e11-0d1215171c69 - 200:0 “2ms” “GET /api/v1/rest/docker/addons http/1.1” 2485 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:21.880Z] [INFO] default -e[39m [access] ihost.local - fdf48d32-342b-4449-b8e9-9c236dec6069 - GET /api/v1/rest/docker/addons
e[32m[2024-06-20T18:58:21.882Z] [INFO] default -e[39m [access] ihost.local - fdf48d32-342b-4449-b8e9-9c236dec6069 - 200:0 “1ms” “GET /api/v1/rest/docker/addons http/1.1” 2485 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:21.888Z] [INFO] default -e[39m [access] ihost.local - 3c1f42f8-6ce5-406f-be76-e3925f5acb31 - GET /api/v1/rest/docker/storage
e[32m[2024-06-20T18:58:21.916Z] [INFO] default -e[39m [access] ihost.local - 3c1f42f8-6ce5-406f-be76-e3925f5acb31 - 200:0 “28ms” “GET /api/v1/rest/docker/storage http/1.1” 118 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:21.928Z] [INFO] default -e[39m [access] ihost.local - 0fc22be5-8814-47ee-b4b7-158c541c16df - GET /api/v1/rest/docker/containers
e[32m[2024-06-20T18:58:21.932Z] [INFO] default -e[39m [access] ihost.local - 0fc22be5-8814-47ee-b4b7-158c541c16df - 200:0 “4ms” “GET /api/v1/rest/docker/containers http/1.1” 4199 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[91m[2024-06-20T18:58:24.098Z] [ERROR] default -e[39m [addon] download downloadStatus:4 - errorMsg: {“errorDetail”:{“message”:“no matching manifest for linux/arm/v7 in the manifest list entries”},“error”:“no matching manifest for linux/arm/v7 in the manifest list entries”}

e[32m[2024-06-20T18:58:24.100Z] [INFO] default -e[39m [publish] =================> { state: 0, installAt: null } 1 0
e[32m[2024-06-20T18:58:24.101Z] [INFO] default -e[39m publish ==========> docker/addon/card/24/updated/install-state {“state”:0,“installAt”:null}
e[32m[2024-06-20T18:58:24.103Z] [INFO] default -e[39m publish ==========> docker/addon/card/24/updated/install-result {“success”:false,“reason”:“architectureNotSupport”}
e[32m[2024-06-20T18:58:24.112Z] [INFO] default -e[39m [access] ihost.local - 84129b58-f5fa-4f51-8801-65d5ededec54 - GET /api/v1/rest/docker/addons
e[32m[2024-06-20T18:58:24.114Z] [INFO] default -e[39m [access] ihost.local - 84129b58-f5fa-4f51-8801-65d5ededec54 - 200:0 “1ms” “GET /api/v1/rest/docker/addons http/1.1” 2440 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:24.122Z] [INFO] default -e[39m [access] ihost.local - ab1fb1b1-a5c7-454a-b674-05c5ca1e90a2 - GET /api/v1/rest/docker/addons
e[32m[2024-06-20T18:58:24.123Z] [INFO] default -e[39m [access] ihost.local - ab1fb1b1-a5c7-454a-b674-05c5ca1e90a2 - 200:0 “2ms” “GET /api/v1/rest/docker/addons http/1.1” 2440 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:24.130Z] [INFO] default -e[39m [access] ihost.local - ce9f77e9-11f8-4479-bf5a-326707875614 - GET /api/v1/rest/docker/storage
e[32m[2024-06-20T18:58:24.159Z] [INFO] default -e[39m [access] ihost.local - ce9f77e9-11f8-4479-bf5a-326707875614 - 200:0 “28ms” “GET /api/v1/rest/docker/storage http/1.1” 118 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:24.167Z] [INFO] default -e[39m [access] ihost.local - a6b193d5-aad3-4c2e-b7e6-d3bb07bf1181 - GET /api/v1/rest/docker/storage
e[32m[2024-06-20T18:58:24.186Z] [INFO] default -e[39m [access] ihost.local - 992fa094-6a56-4fed-89f0-d6e1647a1b4d - GET /api/v1/rest/docker/containers
e[32m[2024-06-20T18:58:24.191Z] [INFO] default -e[39m [access] ihost.local - 992fa094-6a56-4fed-89f0-d6e1647a1b4d - 200:0 “4ms” “GET /api/v1/rest/docker/containers http/1.1” 4199 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
e[32m[2024-06-20T18:58:24.197Z] [INFO] default -e[39m [access] ihost.local - a6b193d5-aad3-4c2e-b7e6-d3bb07bf1181 - 200:0 “30ms” “GET /api/v1/rest/docker/storage http/1.1” 118 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36

But apart from this, iHost sees and handles the card without any problems?

Hi.

Yes, i can add or delete the card without any problem.

1 Like

Then I don’t know. They probably broke something again in 2.0
I read somewhere that cards can be quite loose in a slot that is too loose and this may cause problems, but it doesn’t seem to be the case with you.

Download with other add-on is fine, and only failed with node-red?
Please send us the system log via feedback and send me the ticket.
We’ll look into it ASAP.

Hi,
I have the same problem, I think it is software failure. After upgrade to 2.0 I can`t install nodered

Please send us the system log via feedback and send me the ticket.
We’ll look into it ASAP.

We’ve checked the log that one of our user sended.
Download failure of node-red is not due to v2.0.0 update.

It’s because the latest image(updated 4 days ago) of node-red didn’t support linux/arm/v7 architecture.
Therefore we can’t pull it from docker hub due to architecture mismatch.

We’ll start an issue in github to urge node-red fix the problem.

1 Like

So we should avoid updating to Node-RED 4, right?
Actually on the iHost Docker screen, checking for updates in Node-red doesn’t suggest upgrading, but worth pointing out to everyone.
Obviously that’s a problem for a new user.

Before we confirm with node-red developers.
Updating node-red add-on is not recommanded.

2 Likes

I am also seeing the same thing. This is a massive blocker as we have this hardware in use and cannot setup new users with Node-RED. I’m looking at other repos available to see if they have updated for armv7 or not and switching. I’ll let people know on here which one, or if I create one temporarily from an older image. Likewise if anyone comes across a better solution then please post here.

Yes.
Build a new image base on a older version of node-red image is possible.
For me, v3.1 of node-red image is working without any problem.

A self-build image won’t have features like WebUI and default setting.
But you can solve it with opening node-red in a new tab.

Thanks SuiKa, I was going to go with last stable 3.1.1, is that the version you are using? WebUI is not important for our purposes so a tew tab is OK. There is also a previous docker container build, can we specify this repo in the iHost UI command line or environment variables?

I’m using this tag: nodered/node-red:3.1.

I’m not sure. Switching version by using environment variables seems impossible.

I would like to ask for help with the installation. Is it possible to install a previous version of Node-RED on the Ihost device? Unfortunately, I couldn’t find any solution.

Do you have a working image built in 3.1? If so could you upload your container to public docker please? I’m looking into uploading this but I’ve mostly consumed and configured containers and not submitted any so this may take a little while.

OK, I’ve got an image from Node-RED 3.1.1 working on iHost. This is a build based on the public github image GitHub - node-red/node-red-docker at v3.1.11 so as with any public image please use within the licensing constraints of the github release and at your own risk. You can find it at:
https://hub.docker.com/r/damionhelix/node-red-build
Or simply follow the build instructions provided in the repository and on the docker website to build and release your own.