Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue to setup de plugin after v4.0.0 [issues with 32-bit ARMv6Z] #88

Closed
ViniciusPine opened this issue Jan 8, 2022 · 43 comments
Closed

Issue to setup de plugin after v4.0.0 [issues with 32-bit ARMv6Z] #88

ViniciusPine opened this issue Jan 8, 2022 · 43 comments
Assignees
@AntonioMeireles
Labels
bug Something isn't working

Comments

@ViniciusPine
Copy link

ViniciusPine commented Jan 8, 2022 •
edited by AntonioMeireles

Hi, first of all congratulation for your project, awesome!

I'm using your plugin about a year, but after the last month stopped working. When I try to open the config page from the plugin keeps loading and never ends.

Homebridge Log Error:

[08/01/2022, 18:02:44] [Homebridge UI] [homebridge-vieramatic] 
 Fatal error in , line 0
 Liftoff bailout should not happen. Cause: Armv6 not supported




FailureMessage Object: 0xb61fdf50
[08/01/2022, 18:02:44] [Homebridge UI] [homebridge-vieramatic] Child process ended

////////// ------ //////////

Details about your specific homebridge setup
- Raspberry Pi Zero W
- Raspbian GNU/Linux Bullseye (11)
- v16.13.1
- Homebridge Version v1.3.9
- Vieramatic v4.0.6
- Panasonic TV 55" FX800B (tried Wired and Wireless)

Maybe the plugin stopped working with this architecture (32-bit ARMv6Z)?
@AntonioMeireles AntonioMeireles self-assigned this Jan 8, 2022
@AntonioMeireles AntonioMeireles added the bug Something isn't working label Jan 8, 2022
@AntonioMeireles
Copy link
Owner

thanks for reporting!

can you check if launching homebridge with NODE_OPTIONS=--no-expose-wasm set changes anything ?

thanks again for reporting!

have a great weekend!

@AntonioMeireles
Copy link
Owner

also, could you also try on node14 plz ? (with and without flag above)

thanks!

@AntonioMeireles AntonioMeireles changed the title Issue to setup de plugin after v4.0.0 Issue to setup de plugin after v4.0.0 [issues with 32-bit ARMv6Z] Jan 8, 2022
@ViniciusPine
Copy link
Author

NODE_OPTIONS=--no-expose-wasm

Sorry for my newbie knowledge but how can I do that?

@ViniciusPine
Copy link
Author

ViniciusPine commented Jan 8, 2022 •
edited 

[08/01/2022, 19:35:30] [Homebridge UI] [homebridge-vieramatic] internal/modules/run_main.js:54
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:666:11)
    at Loader.resolve (internal/modules/esm/loader.js:97:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:42:40)
    at link (internal/modules/esm/module_job.js:41:36) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[08/01/2022, 19:35:30] [Homebridge UI] [homebridge-vieramatic] Child process ended

After installing Node v14.0.0

@AntonioMeireles
Copy link
Owner

late here... will be more detailed tomorrow. meanwhile you need a more recent node14 (later than 14.13.1 actually) latest is 14.18.2 (per https://nodejs.org/en/about/releases/)

@ViniciusPine
Copy link
Author

late here... will be more detailed tomorrow. meanwhile you need a more recent node14 (later than 14.13.1 actually) latest is 14.18.2 (per https://nodejs.org/en/about/releases/)

I see. Tried with 14.13.1 started to load the Panasonic logo, trying now with 14.18.2 but didn't work at all. I'll try until you bring something! Thanks a lot!

@AntonioMeireles
Copy link
Owner

Tried with 14.13.1 started to load the Panasonic logo

could you please attach the full homebridge debug logs ?
how are you starting homebridge ? pm2, initscript or something else ?

thanks in advance!

@AntonioMeireles
Copy link
Owner

for context

@mefbgil
Copy link

mefbgil commented Jan 9, 2022

I'm getting the same thing using Node.js v16.13.1 inside oznu/homebridge docker container. Completely removed old Viera TV configs, trying to add brand new TV to config.

@AntonioMeireles
Copy link
Owner

AntonioMeireles commented Jan 9, 2022 •
edited

@mefbgil

by same thing you mean the Liftoff bailout should not happen. Cause: Armv6 not supported error ?
If so, cvould you and @vinixpx try latest homebridge beta ? (npm i homebridge@1.4.0-beta.4). AFAICT and from here that should come with the fix for this.

(sadly and per here it doesn't seem that they publish docker images of the beta iterations :/)

@mefbgil
Copy link

mefbgil commented Jan 9, 2022 •
edited

When clicking “settings”, the UI does progress past this screen. I’m on x86_64 docker.
AC03D7C2-5B7B-4E96-97CB-D6D81F3C1A11

@AntonioMeireles
Copy link
Owner

AntonioMeireles commented Jan 9, 2022 via email

@AntonioMeireles
Copy link
Owner

AntonioMeireles commented Jan 9, 2022 •
edited

wait, on the mobile... saw now the docker part...

per the docs please do make sure that docker container networking is in host mode for the homebridge container... that may make issue go away... please confirm

and thanks for your patience!

@mefbgil
Copy link

mefbgil commented Jan 9, 2022 via email

@AntonioMeireles
Copy link
Owner

AntonioMeireles commented Jan 9, 2022 via email

@mefbgil
Copy link

mefbgil commented Jan 9, 2022 via email

@AntonioMeireles
Copy link
Owner

AntonioMeireles commented Jan 10, 2022 •
edited

@mefbgil

disabled the SSDP / upnp / multicast bits for now which is what was messing with docker afaict. so, no automated TV discovery for now :|.

can you try latest version (homebridge-vieramatic@4.0.8) and check that for a change everything else behaves now ?

Thanks in advance!

@ViniciusPine
Copy link
Author

@mefbgil

disabled the SSDP / upnp / multicast bits for now which is what was messing with docker afaict. so, no automated TV discovery for now :|.

can you try latest version (homebridge@4.0.8) and check that for a change everything else behaves now ?

Thanks in advance!

I updated to the last version of plugin and my instance keeps restarting.

I'm gonna try now the beta version

[10/01/2022, 10:48:20] [HB Supervisor] Starting Homebridge with extra flags: -I
[10/01/2022, 10:48:20] [HB Supervisor] Started Homebridge v1.3.9 with PID: 27700
[10/01/2022, 10:48:31] Loaded config.json with 0 accessories and 3 platforms.
[10/01/2022, 10:48:32] Loaded 11 cached accessories from cachedAccessories.
[10/01/2022, 10:48:32] Loaded 11 cached accessories from cachedAccessories.
[10/01/2022, 10:48:33] ---
[10/01/2022, 10:48:45] Loaded plugin: homebridge-config-ui-x@4.41.5
[10/01/2022, 10:48:45] Registering platform 'homebridge-config-ui-x.config'
[10/01/2022, 10:48:45] ---
[10/01/2022, 10:48:46] Loaded plugin: homebridge-ewelink@8.10.0
[10/01/2022, 10:48:46] Registering platform 'homebridge-ewelink.eWeLink'
[10/01/2022, 10:48:46] ---
[10/01/2022, 10:48:49] Loaded plugin: homebridge-tuya-platform@1.5.0
[10/01/2022, 10:48:49] Registering platform 'homebridge-tuya-platform.TuyaPlatform'
[10/01/2022, 10:48:49] ---


#
# Fatal error in , line 0
# 

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

#
#
#
#FailureMessage Object: 0xb49faf50


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

#
#
#
#FailureMessage Object: 0xb59fcf50
[10/01/2022, 10:48:50] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGTRAP

@AntonioMeireles
Copy link
Owner

@mefbgil

didn't updating homebridge tonpm i homebridge@1.4.0-beta.4 fix that specific issue ? or didn't you tried yet ?

@ViniciusPine
Copy link
Author

@mefbgil

by same thing you mean the Liftoff bailout should not happen. Cause: Armv6 not supported error ? If so, cvould you and @vinixpx try latest homebridge beta ? (npm i homebridge@1.4.0-beta.4). AFAICT and from here that should come with the fix for this.

(sadly and per here it doesn't seem that they publish docker images of the beta iterations :/)

Same log error that I posted minutes ago. Didn't work.

@AntonioMeireles
Copy link
Owner

and still doesn't work with latest node 14 ? also (with latest version of plugin) too ? what timezone are you on ?
would you be available for some sort of live debug sprint ?

@ViniciusPine
Copy link
Author

ViniciusPine commented Jan 10, 2022 •
edited

and still doesn't work with latest node 14 ? also (with latest version of plugin) too ? what timezone are you on ?

would you be available for some sort of live debug sprint ?

Didn't tested with 14.8.2. I'll try that. I'm on GMT-3.

What do you mean about debug sprint? My knowledge is limited. I use macOS to access Homebridge via ssh or web browsing.

@ViniciusPine
Copy link
Author

and still doesn't work with latest node 14 ? also (with latest version of plugin) too ? what timezone are you on ?
would you be available for some sort of live debug sprint ?

New scenario:
Node v14.18.2
npm v6.14.15

New log error:

[10/01/2022, 16:32:10] [Homebridge UI] [homebridge-vieramatic] Child process ended
[10/01/2022, 17:05:55] [Homebridge UI] [homebridge-vieramatic] Terminating child process...
[10/01/2022, 17:05:59] [Homebridge UI] [homebridge-vieramatic] events.js:377
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at new NodeError (internal/errors.js:322:7)
    at process.target.send (internal/child_process.js:714:16)
    at pe.ready (/usr/local/lib/node_modules/homebridge-vieramatic/node_modules/@homebridge/plugin-ui-utils/dist/server.js:105:17)
    at new pe (file:///usr/local/lib/node_modules/homebridge-vieramatic/dist/homebridge-ui/server.js:10:901)
    at file:///usr/local/lib/node_modules/homebridge-vieramatic/dist/homebridge-ui/server.js:10:2004
    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)
    at async Loader.import (internal/modules/esm/loader.js:178:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)
Emitted 'error' event on process instance at:
    at internal/child_process.js:718:35
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  code: 'ERR_IPC_CHANNEL_CLOSED'
}
[10/01/2022, 17:05:59] [Homebridge UI] [homebridge-vieramatic] Child process ended

@AntonioMeireles
Copy link
Owner

@vinixpx

sorry lag (COVID woes here :/) . still looking into this. THANKS for your patience!

@ViniciusPine
Copy link
Author

@vinixpx

sorry lag (COVID woes here :/) . still looking into this. THANKS for your patience!

No problem! Stay safe!

AntonioMeireles added a commit that referenced this issue Jan 21, 2022
@AntonioMeireles
update dependencies
3eda2a7 
- of note:
  - hap-nodejs 0.9.8 -> 0.10.0
  - homebridge 1.3.9 -> 1.4.0

 as they fix homebridge/homebridge#3005 /
 homebridge/HAP-NodeJS#919
 which hit us in #88

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
@AntonioMeireles
Copy link
Owner

@ViniciusPine

is this still an issue with homebridge-vieramatic@4.0.20 and homebridge@1.4.0 both installed ?

Thanks in advance!

@ViniciusPine
Copy link
Author

@ViniciusPine

is this still an issue with homebridge-vieramatic@4.0.20 and homebridge@1.4.0 both installed ?

Thanks in advance!

Yep! I've been testing since our last talk and never works. I'm on my iPhone now, but here a screenshot from my log!

image

@AntonioMeireles
Copy link
Owner

@ViniciusPine

thanks for your fast reply

is this also with homebridge@1.4.0 (released yesterday) ? (as it should have the fix for this :|)

@ViniciusPine
Copy link
Author

@ViniciusPine

thanks for your fast reply

is this also with homebridge@1.4.0 (released yesterday) ? (as it should have the fix for this :|)

Yep! I updated yesterday. I don't know anymore. I'm thinking about restoring my SD card and starting all over again.

@AntonioMeireles
Copy link
Owner

@ViniciusPine

still digging on this. shouldn't happen anymore as upstream says the issue is fixed.

thanks for your patience!

@ViniciusPine
Copy link
Author

@ViniciusPine

still digging on this. shouldn't happen anymore as upstream says the issue is fixed.

thanks for your patience!

Have you the change log where they say that was fixed?

@AntonioMeireles
Copy link
Owner

@ViniciusPine
still digging on this. shouldn't happen anymore as upstream says the issue is fixed.
thanks for your patience!

Have you the change log where they say that was fixed?

homebridge/HAP-NodeJS#919 (comment)

@ViniciusPine
Copy link
Author

@ViniciusPine
still digging on this. shouldn't happen anymore as upstream says the issue is fixed.
thanks for your patience!

Have you the change log where they say that was fixed?

homebridge/HAP-NodeJS#919 (comment)

Hey, I saw that thing about WASM, but how I can start homebridge with --no-expose-wasm ?

@AntonioMeireles
Copy link
Owner

AntonioMeireles commented Jan 23, 2022 •
edited

Hi again!

dunno about your specific setup ... but can you try to edit /usr/bin/homebridge and
change first line from #!/usr/bin/env node to #!/usr/bin/env node --no-expose-wasm. may or may not work (as i haven't so far a way to reproduce)

@ViniciusPine
Copy link
Author

I have a Raspberry Pi, I'm very newbie. Don't know how to edit files through terminal commands.

@AntonioMeireles
Copy link
Owner

sudo nano /usr/bin/homebridge ... (google is your friend too ;-) )

@ViniciusPine
Copy link
Author

sudo nano /usr/bin/homebridge ... (google is your friend too ;-) )

Thanks for your quick reply! I'm studying all about, thanks! I'll try

@ViniciusPine
Copy link
Author

Hello, I'm here again! I learned how to edit the files that you pointed earlier but no success running the plugin. I saw some possible fixes for the error but again, no success. Do you know anybody else with this problem or just me?

Something changed in the past updates to stop working on Pi Zero? I was so happy with this :(

@AntonioMeireles
Copy link
Owner

@ViniciusPine

you were the only one reporting it afaick. and so far i haven't got access to similar hardware to try to debug/reproduce it. [it's on my plate, if i find anything you'll be the first to know ;-)

@ViniciusPine
Copy link
Author

Hey, something new? I tried all the updates but always the same error.


[28/01/2022, 21:21:26] [Homebridge UI] [homebridge-vieramatic] #
# Fatal error in , line 0
# Liftoff bailout should not happen. Cause: Armv6 not supported

#
#
#
#FailureMessage Object: 0xb61fdf50
[28/01/2022, 21:21:26] [Homebridge UI] [homebridge-vieramatic] #
# Fatal error in , line 0
# Liftoff bailout should not happen. Cause: Armv6 not supported

#
#
#
#FailureMessage Object: 0xb49faf50
[28/01/2022, 21:21:26] [Homebridge UI] [homebridge-vieramatic] Child process ended

@AntonioMeireles
Copy link
Owner

@ViniciusPine

not yet :/. (&& thanks for your patience!)

@ViniciusPine
Copy link
Author

ViniciusPine commented Feb 15, 2022 •
edited

Hey @AntonioMeireles great news! Last version is working!!! Flawlessly and quicker than ever! Thank you a lot for your hard work!

One thing that I tried now is to install the plugin through terminal

sudo npm install -g homebridge-vieramatic@latest

Using:

Node Version: 16.14.0
NPM Version: 8.5.0

I will close this topic!

@AntonioMeireles
Copy link
Owner

@ViniciusPine

Woot! Great to hear ;-)

Thanks once again for your patience!

All the Best,

António

P.S. feel free to bug me again if issues arise again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AntonioMeireles AntonioMeireles

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AntonioMeireles @mefbgil @ViniciusPine