-
-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
Plugin stopped responding after some times, reported TV is OFF while it is ON #170
Comments
Hi, I'am having a very similar issue (although not 100% sure it is the same). When it has stopped working, I can see occasionally a socket related error (but not systematically at each button press) : And while the TV is ON, no error is displayed although TV state seem stuck : [02/11/2023 11:48:34] [LgWebOsTv] Device: 192.168.1.128 LG webOS TV Homebridge, Power: OFF If I restart Homebridge, everything works as expected : [02/11/2023 11:59:18] [LgWebOsTv] Device: 192.168.1.128 LG webOS TV Homebridge, Connected. I have a bunch of other plugins (no particular network issue) but I haven't found what could be the issue with my TV. Thanks for your help ! |
This is correct, if You try send command to TV and socket is not connected then the error appear in log. Regarding plugin stop responding this can be local specific issue, I have in my environment 65G6V, 48CX, 48C3, 49SK8500, 32LM6300 and not observe described issue. Plugin stop responding issue in most cases is HB problem and local environment. If you can record this issue with debug mode enabled then will be very helpful to find what is wrong. |
Thanks for your suggestion ! Right after HB restart it took some time for the accessories to work (I use "Mute" for my tests) so maybe this is only a "glitch" / transient effect. I will check for other unexpected messages in the coming days. |
Hi, Here is a few extracts from the log. .... Then, the only plugin related messages are the following that were repeated regularly during the night (no more heartbeat) : ^[[37m[03/11/2023 09:43:51] ^[[39m^[[36m[LgWebOsTv]^[[39m Device: 192.168.1.128 LG webOS TV Homebridge, Power: OFF But nothing when I switched the TV ON (and in particular, no more "log cluster" as shown above). While going to accessory tab in HB (forcing some kind of update I guesss), I can only see a new log cluster, with exactly the same content as shown above (telling the TV is OFF, mute ON and so on). I searched for socket related messages but strictly none can be found... Until I forced an action (mute) from HB accessory tab : [03/11/2023 10:28:03] [LgWebOsTv] Device: 192.168.1.128 LG webOS TV Homebridge, set Mute error: Socket not connected. I'm not clear on the precise moment thing started to go wrong since there were no error messages until I forced the use of an accessory. Any idea ? Many thanks |
Yeah i believe you have same issues as mine. However i have move on to another plugin and my tv never got disconnected anymore. Sorry its has been 6 month with no reply. Got to try something right.. |
Send and receive heart beat is only if plugin is connected to tv. After TV switch to of the socket is closed in log is reported socket closed and next start Connect to tv again. If connection is not possible then reported error in the log and this is correct. As long as the TV i not available in the network plugin try to Connect every some seconds and this need to be visible during whole time when TV is Off. In your log this action is stopped, so here is the problem in your case. This problem doesn’t exist in my environment is very difficult check what is wrong. Check please installed node- min v18 and Homebridge min v1.6. I will put today later new version with experimental changes to fix this issue. |
I recently (last week) upgraded to node v20.9.0 and HB is up to date with v1.6.1. |
please try latest 2.14.0-beta and let me know |
Hi ! With the beta I experience an error that makes HB crashing. If I roll back to previous stable version it works again (no crash). I'm pretty sure that at the first restart after update I hadn't this error but I think I only toggle an accessory visibility and since then I couldn't get rid of this error (tried to unistall & reinstall the plugin, restart my RPi, ...). Here is the error I met : [03/11/2023 19:27:08] Error: Accessory LG webOS TV HB experienced an address collision. Any advice ? |
remove and again plugin child bridge |
Removed plugin and reinstalled as child bridge, but still crashes : [04/11/2023 11:14:00] [homebridge-lgwebos-tv] Process Ended. Code: 1, Signal: null Need deeper "cleaning" ? |
@bollee23 |
Indeed, no more crash :-). Maybe I do something wrong (not very familiar with child bridges). If you have any advice for that. I can nevertheless verify that the plugin don't die after TV being switched Off (from HB GUI) Many thanks ! |
You need add the accessory itself to the HomeKit not the bridge. |
Wow ! Works great ! Thank you @grzegorz914 Now I can wait and test to see if it passes the night ;-) Thanks again for your patience ;-) |
Hi again, |
Thanks for testing I will publish it. |
i am having weird issue with this plugin, after some time the plugin seems to be unresponsive where turning on/off from homebridge/homekit doesnt do anything..
homebridge reported the tv is off evethough the tv is currently on.
restarting the child bridge and the issue gone.
TV model : 50UP7750PTB
WebOS Version : 6.32-425
not sure how to produce log my homebridge already set to debug mode
this is the only log appears
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, set Power: ON
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Power: OFF
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Power: OFF
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Input, Name: Kodi, Reference: com.webos.app.hdmi2
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Accessory Name: TV.
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Discovery Mode: Always discoverable
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Closed Captions: 0
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Media: STOP
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Target Media: STOP
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Picture Mode: 3
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Mute: ON
[03/05/2023, 19:15:35] [homebridge-lgwebos-tv]Device: 192.168.0.35 TV, Volume: 6
Under working condition, i can regularly see :
[03/05/2023, 20:03:24] [homebridge-lgwebos-tv] Device: 192.168.0.35 TV, debug: Specialized socket send heartbeat.
[03/05/2023, 20:03:24] [homebridge-lgwebos-tv] Device: 192.168.0.35 TV, debug: Specialized socket received heartbeat.
but none of this message appears when it become unresponsive.
Thanks.
The text was updated successfully, but these errors were encountered: