Error in Log on Startup

[Russ1525]

Thanks very much for the work you put into this! Created a separate Eufy account and invited it to regular account.

Here is my config and log error...thanks in advance:

eufy:
username: username
password: password
mqtt:
url: 'mqtt://192.168.0.120:1883'
username: mqttusername
password: mqttpassword
home_assistant:
off_delay: 5
log_level: info
eval: ''

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...

Add-on: Eufy Home Assistant MQTT Bridge
Publish events as MQTT messages

Add-on version: 1.18.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.13 (amd64 / intel-nuc)
Home Assistant Core: 2021.5.4
Home Assistant Supervisor: 2021.04.3

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:00:24] INFO: Exporting log level for nodejs: info
[11:00:25] INFO: Symlinking data dir
[11:00:25] INFO: Running 'eval' commands
[11:00:25] INFO: Generating config.yml from options.json
[11:00:25] INFO: Image build with version 0.2.18
[11:00:25] INFO: starting original stuff...

[email protected] start /app
NODE_ENV=production node --unhandled-rejections=strict index.js
/run.sh: line 20: 337 Illegal instruction (core dumped) npm run start
[cmd] /run.sh exited 132
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...

---

            Oops! Something went wrong.

We are so sorry, but something went terribly wrong when
starting or running this add-on.

Be sure to check the log above, line by line, for hints.

[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

[Wurmie1978]

I got the same error.

Thanks for all your hard work by the way

[tashda]

I have the same issue and I am pretty sure that I am doing something wrong, but I have been looking at this for the last 4 days and can't seem to get it working.

Tried setting log_level: debug, but no more info was provided.

Anyone able to point in the right direction?
I reckon it's most likely the connection to the MQTT broker

> [email protected] start /app
> NODE_ENV=production node --unhandled-rejections=strict index.js
/run.sh: line 20:   339 Illegal instruction     (core dumped) npm run start
[cmd] /run.sh exited 132

[tashda]

Have tried to solve this for what feels like a infinite amount of time.
I'm usually quick to pick up on these things, but I simply can not get this to start up.

Running Ubuntu Server with Home Assistent Docker.

[matijse]

I think this might have to do with the new Docker setup I use from 0.2.18, which was needed to include a specific image verification library. This includes some complex dependencies which I don't fully understand.

I just deployed release 0.2.19, but I think the addon by @MaxWinterstein does not really use my Dockerfile, but rather the source code. So if you use the addon, some things might be not entirely correct there on some architectures...

I've only tested mine on Ubuntu 64 bit, running my Docker image directly, without the addon. The builds for arm (Raspberry Pi) do succeed now as well.

So for everyone that sees Illegal instruction (core dumped) npm run start errors:

• Do you run the HA Addon or Docker image directly?
• On which architecture? (64 bit Linux, arm v7/v8 (Raspberry Pi))

[tashda]

Hi, thanks so much for your reply.
I run as a HA Addon (from Max) on Ubuntu Server (64 bit).

Sounds like I will have to try your (original) way of doing it instead of cutting corners.

[matijse]

I just released 0.2.19 and this also breaks the build process of the HA Addon, so I think if things are updated in the addon to match the changes I made in the Dockerfile, that might work again...

[tashda]

I just released 0.2.19 and this also breaks the build process of the HA Addon, so I think if things are updated in the addon to match the changes I made in the Dockerfile, that might work again...

Thanks a million for your reply.

[Russ1525]

• Running the HA Addon
• Running HASS OS, Intel NUC install

[matijse]

FYI: I just released version 0.2.21 which should not depend on image libraries anymore, so those issues should hopefully be gone...

[tashda]

Thanks a million!
I ditched the add-on and set it up following your instructions and it has been working flawlessly