[TV] Polling Erroneously Triggers Automation about homebridge-webos-tv HOT 11 OPEN

Hi, i am not quite sure if i understand your issue correctly, but did you should be able to do what you describe in HomeKit already. You trigger some actions or automations based on the TV status. Is there an issue with that?

from homebridge-webos-tv.

It a problem I have with other plugins on home bridge.

I'm not sure what the technical cause for this problem is. It expressed as repeated triggering of a "device controlled" automation in HomeKit.

If you turn on the tv, HomeKit reflects this instantly.

When the plug in polls the api, it seems like it tells HomeKit again the device is on, trigging the device is on automation again.

from homebridge-webos-tv.

What LG TV do you have?

from homebridge-webos-tv.

Model number 32LQ63BPUA, webOSTV 7.0(2.4.4), TV Firmware 4.40.91.

The TV powers on and off perfectly with HomeKit. It's the repeated automation triggers that makes it difficult to tie automation to its use.

from homebridge-webos-tv.

As far as i can see your TV does not use polling to get the status but rather listens to the TV events as it is a newer one. The TV only sends the events when something happens and as far as i know it only sends the turn on event once. What you could is to enable deepDebugLog start homebridge in debug mode and check the log when the situations which you find is not correct happens, you can then post the log here so i can have a look.

from homebridge-webos-tv.

I see this in the log.

Idk if this causes an update to HomeKit or not.

from homebridge-webos-tv.

That just states that the plugin is trying to connect to the tv, there might be something that causes it to disconnect, hence you need to enable the deepDebugLog so we can see the full log of what is happening.
https://github.com/merdok/homebridge-webos-tv?tab=readme-ov-file#troubleshooting

from homebridge-webos-tv.

okay, I added,

{ "name": "Display", "ip": "10.0.145.9", "mac": "4c:ba:d7:e5:02:ea", "broadcastAdr": "10.0.145.233", "hideTvService": false, "volumeLimit": 100, "volumeControl": "none", "channelControl": false, **"deepDebugLog": true** }

And after rebooting homebridge, I see this in the log:

[4/20/2024, 8:42:45 AM] [homebridge-webos-tv] [Display] Error - Error: connect ETIMEDOUT 10.0.145.9:3000 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16) { errno: -110, code: 'ETIMEDOUT', syscall: 'connect', address: '10.0.145.9', port: 3000 } [4/20/2024, 8:42:50 AM] [homebridge-webos-tv] [Display] Connecting to TV [4/20/2024, 8:43:27 AM] [homebridge-webos-tv] [Display] Connecting to TV [4/20/2024, 8:44:04 AM] [homebridge-webos-tv] [Display] Connecting to TV [4/20/2024, 8:44:41 AM] [homebridge-webos-tv] [Display] Connecting to TV [4/20/2024, 8:45:18 AM] [homebridge-webos-tv] [Display] Connecting to TV [4/20/2024, 8:45:55 AM] [homebridge-webos-tv] [Display] Connecting to TV [4/20/2024, 8:46:31 AM] [homebridge-webos-tv] [Display] Connecting to TV

It's unclear how homebridge updates HomeKit. Automation I have tied to the TV's state repeat.

from homebridge-webos-tv.

But did you start homebridge in debug mode? This log only indicates that the plugin is trying to connect to your TV, based on that the plugin should not even work.

from homebridge-webos-tv.

Yep, I've had it turned on to troubleshoot multiple plugins that can't keep homekit in sync. I added the "deep debug" to this webos plug in and started homebridge. What you see is the result. Without interacting with the TV (which I don't usually do during the day), I just get repeated "Connecting messages."

Running 2.4.4 of the plugin.

from homebridge-webos-tv.

Yeah, well that is certainly not the complete log so i guess that you are missing something. I would need the complete log, as without that it is impossible for me to tell why your TV constantly re-connects.

from homebridge-webos-tv.