search

merdok / homebridge-webos-tv

Homebridge plugin for LG webOS TVs
MIT License
656 stars 88 forks source link

What can be done for more stable response? #176

Closed Olepir closed 4 years ago

Olepir commented 5 years ago

Turning TV On in Home.app not always working or not displaying correctly – TV can be on, but in Home.app it Off and vice versa. Also volume control latency is long. What can be done for more stable response (except LAN connection)?

merdok commented 5 years ago

Might be that some other plugins are slowing down you Home app.

Olepir commented 5 years ago

Might be that some other plugins are slowing down you Home app.

For example? Thanks

merdok commented 5 years ago

I have no idea what plugins you have installed :p You need to investigate this by yourself by removing plugins and seeing what is causing the slow down...

rooi commented 5 years ago

From my experience, you can get a significant decrease in latency when running multiple instances of homebridge. You can get a guide on hoe to do this here: https://github.com/jvmahon/homebridge-homeseer/wiki/Running-Multiple-Instances-of-HomeBridge I’ve configured my setup such that there’s one instance for each plugin. This makes trouble shooting a whole lot easier as well

Olepir commented 4 years ago

I have no idea what plugins you have installed :p You need to investigate this by yourself by removing plugins and seeing what is causing the slow down...

Everything was fine with same plugins, I don’t have much – webos, deconz, cmd2, cameras and config ui x. Apparently a house owner replaced a router recently and after that issues appeared. Any advices for troubleshooting wifi connections?

Olepir commented 4 years ago

Also noticed "[LG TV] webOS - Error: connect EHOSTUNREACH 192.168.1.76:3000” in ui x console, but IP is correct

merdok commented 4 years ago

This error is fine and should not affect your setup.

Olepir commented 4 years ago

This error is fine and should not affect your setup.

How about this? [LG TV] webOS - Error: Sec-WebSocket-Accept header from server didn't match expected value of kTLtbQAPV+A8cyTK6qmoaTah5Ds=

merdok commented 4 years ago

This is also ok, just sometimes the data gets corrupted for some reason.

Olepir commented 4 years ago

Did everything I could to troubleshoot it (except replacing a router), but with no luck. Will use it PS4-Waker in automations for now.