search

merdok / homebridge-webos-tv

Homebridge plugin for LG webOS TVs
MIT License
664 stars 89 forks source link

update to 2.4.4 fails with fatal error: assert.h: No such file or directory #529

Closed czbird77 closed 7 months ago

czbird77 commented 7 months ago

Hi, I'm unable to up the plugin to v2.4.4. Any clues what went wrong? Thanks!

USER: homebridge DIR: /usr CMD: sudo -E -n npm install -g homebridge-webos-tv@2.4.4

(##################) ⠦ reify:es5-ext: timing reifyNode:node_modules/homebridge-webos-t

bufferutil@4.0.8 install node-gyp-build

(##################) ⠹ reify:es5-ext: timing reifyNode:node_modules/homebridge-webos-t make: Entering directory '/usr/lib/node_modules/homebridge-webos-tv/node_modules/bufferutil/build' CC(target) Release/obj.target/bufferutil/src/bufferutil.o ../src/bufferutil.c:2:10: fatal error: assert.h: No such file or directory 2 | #include | ^~~~~~ compilation terminated. make: *** [bufferutil.target.mk:106: Release/obj.target/bufferutil/src/bufferutil.o] Error 1 make: Leaving directory '/usr/lib/node_modules/homebridge-webos-tv/node_modules/bufferutil/build' gyp ERR! build error ⠹ reify:es5-ext: timing reifyNode:node_modules/homebridge-webos-t gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23) gyp ERR! System Linux 5.10.103-v7l+ gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /usr/lib/node_modules/homebridge-webos-tv/node_modules/bufferutil gyp ERR! node -v v20.12.0 gyp ERR! node-gyp -v v10.0.1 gyp ERR! not ok npm ERR! code 1 npm ERR! path /usr/lib/node_modules/homebridge-webos-tv/node_modules/bufferutil npm ERR! command failed npm ERR! command sh -c node-gyp-build

npm ERR! A complete log of this run can be found in: /home/homebridge/.npm/_logs/2024-04-24T20_16_16_153Z-debug-0.log

Operation failed with code 1. You can download this log file for future reference. See https://github.com/homebridge/homebridge-config-ui-x/wiki/Troubleshooting for help.

czbird77 commented 7 months ago

Also current v2.4.3 just have started misbehaving for no reason - despite of no errors in HB log, the TV is displayed as being OFF in the Homekit. No idea what's going on here.

[4/24/2024, 10:22:20 PM] [homebridge-webos-tv] Launched child bridge with PID 28700 [4/24/2024, 10:22:20 PM] Registering platform 'homebridge-webos-tv.webostv' [4/24/2024, 10:22:20 PM] [homebridge-webos-tv] Loaded homebridge-webos-tv v2.4.3 child bridge successfully [4/24/2024, 10:22:20 PM] Loaded 0 cached accessories from cachedAccessories.0E9E797603AE. [4/24/2024, 10:22:20 PM] [homebridge-webos-tv] Init - initializing devices [4/24/2024, 10:22:20 PM] [homebridge-webos-tv] [My LG TV] Init - got TV configuration, initializing device with name: My LG TV [4/24/2024, 10:22:21 PM] Homebridge v1.8.0 (HAP v0.12.0) (homebridge-webos-tv) is running on port 34022. [4/24/2024, 10:22:21 PM] My LG TV 19F0 is running on port 34253. [4/24/2024, 10:22:21 PM] Please add [My LG TV 19F0] manually in Home app. Setup Code: 747-97-534 [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Connected to TV [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Got TV information [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] TV webOS version: 6.0 [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] App launched, current appId: com.disney.disneyplus-prod [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Screen saver started! [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Sound output changed. Current sound output: external_arc [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Subscribed to TV services [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Connected to remote pointer input socket [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] Setup finished [4/24/2024, 10:22:21 PM] [homebridge-webos-tv] [My LG TV] TV setup finished, ready to control tv

czbird77 commented 7 months ago

Ah - looks like the OFF-issue is caused by the screen saver being active; is there an option to keep reporting power state as ON despite the screen saver? Thanks!

merdok commented 7 months ago

Hi, the issue during update seems like a node issue. You would need to try to clear all the cache and try again, also you can check for solution on the internet, I think some references will pop up.

The screen saver should not affect the power state of the tv. Are you sure that you checking at the correct place?

czbird77 commented 7 months ago

Thanks for pointing that it could be node issue -- fixed by checking following packages (and adding what was missing):

Screensaver issue did not re-occur since the update, so let's close this one. Thanks.