AntonioMeireles / homebridge-vieramatic

Homebridge plugin for Panasonic™ Viera™ TVs (includes support for 2018 and later models)
Apache License 2.0
43 stars 9 forks source link

This plugin slows down Homebridge #76

Closed peezy45 closed 2 years ago

peezy45 commented 3 years ago

Hey,

I'm receiving this error with the newest version of the plugin and homebridge.

[4/14/2021, 8:55:43 AM] [homebridge-vieramatic] This plugin slows down Homebridge. The read handler for the characteristic 'Active' on the accessory 'Schlafzimmer Fernseher 2BCB' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[4/14/2021, 8:55:43 AM] [homebridge-vieramatic] Error: 
    at Accessory.sendCharacteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1874:14)
    at Timeout._onTimeout (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1431:16)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

Kind regards

AntonioMeireles commented 3 years ago

hi @peezy45

thanks for reporting! AFAIK this may happen if/when you restart homebridge while the TV is off / in standby, and should be innoccuous. If it isn't - i.e. if somehow this implies that things won't work i.e. that TV won't power on / etc via homekit then it is a bug, otherwise just cosmetic cruft 😄

So, which case it is ?

All the best,

António

peezy45 commented 3 years ago

Hey Antonio,

The result is that Homebridge successfully starts but TVs are not responding in the home app. Other Homebridge devices work as expected.

Greetings

AntonioMeireles commented 3 years ago

Hey Antonio,

The result is that Homebridge successfully starts but TVs are not responding in the home app. Other Homebridge devices work as expected.

Greetings

humm, that's sad ...so, we'll need a bit of additional data in order to try to id the root issue and fix it:

Thanks in advance!

António

peezy45 commented 3 years ago

Hey, files are included in the zip file. It's an old install, I just updated my homebridge and plugin version and it happens always, already tried to restart homebridge while tvs are both turned on. Didn't help Already restart the whole docker container multiple times. Updated the container. Nothing helped

Greetings

Pascal

Archiv.zip

AntonioMeireles commented 3 years ago

ok... thanks!!!

2 ,5 quickies, for a start :

Thanks once again for your patience!

AntonioMeireles commented 3 years ago

@peezy45

also of note:

have a great weekend too!

peezy45 commented 3 years ago

So I tried to disable nuki plugin - no change changed the mdns advertiser - no change tv models are TX-49GXN938 and TX-65GZT1506. docker container network is setup as host, yes I even completely removed the plugin and restored it but still no change. I removed your plugin for now cause the "not responding" devices in my home app really annoy me 😅

greetings mate

AntonioMeireles commented 3 years ago

So I tried to disable nuki plugin - no change changed the mdns advertiser - no change tv models are TX-49GXN938 and TX-65GZT1506. docker container network is setup as host, yes I even completely removed the plugin and restored it but still no change. I removed your plugin for now cause the "not responding" devices in my home app really annoy me 😅

greetings mate

😢 could you do an experiment please ? have only a single TV configured in the plugin. restart homebridge and see please if issue persists.

Thanks!

peezy45 commented 3 years ago

Hello again, sorry for the late reply.

So I deleted the plugin including the persistent files and reinstalled it , now I can't even generate encryption keys anymore. It just says the tv uses encrypted communication and cancels viera-pair command. Could it be related to a software update of my tv's or something ?

Greetings

AntonioMeireles commented 3 years ago

@peezy45 is this still happening to you ?

AntonioMeireles commented 2 years ago

closing per lack of reply. afaict this shouldn't be an issue anymore. if it is with recent versions of the plugin just reopen.