Closed ViniciusPine closed 2 years ago
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!
also, could you also try on node14 plz ? (with and without flag above)
thanks!
NODE_OPTIONS=--no-expose-wasm
Sorry for my newbie knowledge but how can I do that?
[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
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/)
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!
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!
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.
@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 :/)
When clicking “settings”, the UI does progress past this screen. I’m on x86_64 docker.
humm... new issue, and the wheel doesn't stop spinning ?
could you please attach the corresponding homebridge logs?
what arch are you on ?
On Sun, 9 Jan 2022 at 20:53, mefbgil @.***> wrote:
When clicking “settings”, the UI does progress past this screen. [image: AC03D7C2-5B7B-4E96-97CB-D6D81F3C1A11] https://user-images.githubusercontent.com/16986758/148700571-4564549c-0c98-44e8-abfc-b7f1e52a3212.jpeg
— Reply to this email directly, view it on GitHub https://github.com/AntonioMeireles/homebridge-vieramatic/issues/88#issuecomment-1008421373, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFVQZ375MQHORB45OP35S3UVHYTPANCNFSM5LRBJQ4A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID: @.***>
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!
Yes - docker is in host mode. Plug-in had been working fine for months, and then noticed today that the bridge was erroring out and restarting itself. So I then plugged out the config and started over. This UI happens on mobile and desktop chrome.
On Jan 9, 2022, at 3:59 PM, António Meireles @.***> wrote:
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...
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.
ok, this is a separate issue, docker specific... use please pre 4.x version until i fix it (at least here i have ways to repro) btw could you plz attach your specific bridge errors ?
On Sun, 9 Jan 2022 at 21:10, mefbgil @.***> wrote:
Yes - docker is in host mode. Plug-in had been working fine for months, and then noticed today that the bridge was erroring out and restarting itself. So I then plugged out the config and started over. This UI happens on mobile and desktop chrome.
On Jan 9, 2022, at 3:59 PM, António Meireles @.***> wrote:
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...
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.
— Reply to this email directly, view it on GitHub https://github.com/AntonioMeireles/homebridge-vieramatic/issues/88#issuecomment-1008424493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFVQZ7LQVO7PX44PWTGJXDUVH2WBANCNFSM5LRBJQ4A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID: @.***>
Yes - let me role back to pre-4, re-add, then re-upgrade, then will attach. Thanks much for the quick responses! On Sunday, January 9, 2022, 04:13:50 PM EST, António Meireles @.***> wrote:
ok, this is a separate issue, docker specific... use please pre 4.x version until i fix it (at least here i have ways to repro) btw could you plz attach your specific bridge errors ?
On Sun, 9 Jan 2022 at 21:10, mefbgil @.***> wrote:
Yes - docker is in host mode. Plug-in had been working fine for months, and then noticed today that the bridge was erroring out and restarting itself. So I then plugged out the config and started over. This UI happens on mobile and desktop chrome.
On Jan 9, 2022, at 3:59 PM, António Meireles @.***> wrote:
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...
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.
— Reply to this email directly, view it on GitHub https://github.com/AntonioMeireles/homebridge-vieramatic/issues/88#issuecomment-1008424493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFVQZ7LQVO7PX44PWTGJXDUVH2WBANCNFSM5LRBJQ4A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID: @.***>
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.Message ID: @.***>
@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!
@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
@mefbgil
didn't updating homebridge tonpm i homebridge@1.4.0-beta.4
fix that specific issue ? or didn't you tried yet ?
@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.
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 ?
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.
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
@Vinixpx
sorry lag (COVID woes here :/) . still looking into this. THANKS for your patience!
@Vinixpx
sorry lag (COVID woes here :/) . still looking into this. THANKS for your patience!
No problem! Stay safe!
@ViniciusPine
is this still an issue with homebridge-vieramatic@4.0.20
and homebridge@1.4.0
both installed ?
Thanks in advance!
@ViniciusPine
is this still an issue with
homebridge-vieramatic@4.0.20
andhomebridge@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!
@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
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.
@ViniciusPine
still digging on this. shouldn't happen anymore as upstream says the issue is fixed.
thanks for your patience!
@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?
@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?
https://github.com/homebridge/HAP-NodeJS/issues/919#issuecomment-1005935273
@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?
Hey, I saw that thing about WASM, but how I can start homebridge with --no-expose-wasm ?
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)
I have a Raspberry Pi, I'm very newbie. Don't know how to edit files through terminal commands.
sudo nano /usr/bin/homebridge
... (google is your friend too ;-) )
sudo nano /usr/bin/homebridge
... (google is your friend too ;-) )
Thanks for your quick reply! I'm studying all about, thanks! I'll try
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 :(
@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 ;-)
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
@ViniciusPine
not yet :/. (&& thanks for your patience!)
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!
@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!
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:
////////// ------ //////////
Details about your specific homebridge setup
Maybe the plugin stopped working with this architecture (32-bit ARMv6Z)?