Updating node to v16 - armv6 error

[athal7]

# Fatal error in , line 0
# Liftoff bailout should not happen. Cause: Armv6 not supported

Originally posted in #3002 (comment)

[Jdemuren]

Same issue here. (raspberry pi Zero W)

[athal7]

@pietje63

[pietje63]

To add to this discussion
Same issue here, also Pi zero

• no issue on update of node (via hb-config or hb-service)
• no issue on update of npm (8.1.3)
• no issue on rebuilding
  issue arises on restart of Homebridge after node update

Getting back to old node is possible (sudo hb-service update-node 14.18.1) to run it again, though support drops (also by plugins)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[EnhancedMind]

using --no-expose-wasm as node argument did the trick for me. The command instead of node . is node --no-expose-wasm .

[elumspe]

using --no-expose-wasm as node argument did the trick for me. The command instead of node . is node --no-expose-wasm .

Where should we put this parameter?

[napdan]

Same question here ¯_(ツ)_/¯

[EnhancedMind]

using --no-expose-wasm as node argument did the trick for me. The command instead of node . is node --no-expose-wasm .

Where should we put this parameter?

I guess you start your code by typing node . or node index.js or something like that into your command line
so instead type node --no-expose-wasm . or node --no-expose-wasm index.js

However I should note that not everything was working. For example, I uset it for discord bot and the bot couldn't play audio in voice channels. However, if I used the --no-expose-wasm on windows it worked fine, so this might be the architecture problem. And no errors returned during that.

[Haxim]

using --no-expose-wasm as node argument did the trick for me. The command instead of node . is node --no-expose-wasm .

Where should we put this parameter?

I edited /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js and changed the first line
#!/usr/bin/env node
to
#!/usr/bin/env -S node --no-expose-wasm

Depending on how you start homebridge, you may need to make the same edit to /usr/local/bin/homebridge as well

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions]

This issue has been closed as no further activity has occurred.

[superevr]

I edited /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js and changed the first line
#!/usr/bin/env node
to
#!/usr/bin/env -S node --no-expose-wasm

This worked for me, but was overwritten in the next update. Wouldn't mind seeing this issue re-opened.

[dlewanda]

My guess here is that we're boned on using official builds of Node.js with the Pi Zero per this link. I'm dropping back to 14.9.0 for now to see if that will get me where I need to be and decide whether to shell out for a Pi with a different version of ARM by the time Node.js v14 is dropped in April 2023.