-
Notifications
You must be signed in to change notification settings - Fork 9
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
TV does not respond sometimes #65
Comments
hi @jeatrexs, thanks for reporting! i would need way more detailed data about your exact setup to give you a more precise answer. At sight, it just seems that your wifi infrastructure is running with aggressive power saving modes which is messing with your HomeKit setup. Could you try to disable all energy saving features from your wifi and see if issue persists ? Thanks in advance! |
still having issues ? |
sorry for the late response.
Any ideas? Thanks! |
well, this is getting interesting. could you just turn physically OFF the TV (from power), wait a bit, turn it ON and see if the issue persists ? also, could you paste the full TV config (in homebridge's On your TV in
thanks again for your patience. |
OK. on a deeper look i may had found the root cause...
do you happen to have any sort of automation that may induce the number of commands sent to homebridge to the TV be rather large ? it seems that you may be hitting some sort of upper bound ... [mess will be to find the real value to get around it ... if this is indeed the issue] |
The only automation I have is the one on my iPhone in the Shortcut-App which is triggered on weekdays every morning at 6.45 am. This automation does the following:
Thats it... You still want me to un/replug my TV and post my configs? |
- tentative fix for #65 Signed-off-by: António Meireles <[email protected]>
Just post your configs for now, together with the data about your environment - arch, node and homebridge versions. Meanwhile i've just pushed a beta version with a tentative fix which may or not be what we want ...
thanks for your patience |
Sure. By the way: This morning my automation worked and the TV responded and got turned on, without changing anything (so i did not find anything suspicious in my homebridge logs from this morning)... I could install the beta package, but i won't find the time to do this today, so let's wait and see if the problem persists tomorrow. Should i install it anyway tomorrow if the problem won't persist tomorrow? Nevertheless here the information you requested: Environment: Here's the TV-part of my homebridge's config.json: {
"tvs": [
{
"friendlyName": "Fernseher",
"ipAddress": "192.168.178.45",
"encKey": "zbu9ktGhYfc3Kz4p0QmmlQ==",
"appId": "ASA6ebgn646QXQ==",
"hdmiInputs": [
{
"id": "3",
"name": "FireTV"
}
],
"customVolumeSlider": true
}
],
"platform": "PanasonicVieraTV"
}, And here's the content of the vieramatic.json: {
"4D454930-0200-1000-8001-B46C4743042F":{
"data":{
"inputs":{
"hdmi":[
{
"id":"3",
"name":"FireTV",
"hidden":0
}
],
"applications":{
"0":{
"name":"Apps Market",
"id":"0387878700000102",
"hidden":1
},
"1":{
"name":"Netflix",
"id":"0010000200000001",
"hidden":1
},
"2":{
"name":"YouTube",
"id":"0070000200200001",
"hidden":0
},
"3":{
"name":"Cinema",
"id":"0020002400180001",
"hidden":1
},
"4":{
"name":"ARD Mediathek",
"id":"0076010807000001",
"hidden":1
},
"5":{
"name":"ZDFmediathek",
"id":"0076011807000001",
"hidden":1
},
"6":{
"name":"Browser",
"id":"0077777700200002",
"hidden":1
},
"7":{
"name":"Amazon Prime Video",
"id":"0010000100200001",
"hidden":1
},
"8":{
"name":"HD+",
"id":"0020011600000001",
"hidden":1
},
"9":{
"name":"Zattoo TV Streaming",
"id":"0020014500000001",
"hidden":1
},
"10":{
"name":"DAZN",
"id":"0020010800000001",
"hidden":1
},
"11":{
"name":"Joyn | deine Streaming App",
"id":"0020003F00000001",
"hidden":1
},
"12":{
"name":"ProSieben",
"id":"0020013500000001",
"hidden":1
},
"13":{
"name":"XUMO: FREE MOVIES&TV",
"id":"0310006000000002",
"hidden":1
},
"14":{
"name":"SAT.1",
"id":"0020013600000001",
"hidden":1
},
"15":{
"name":"Digital Concert Hall",
"id":"0076002307170001",
"hidden":1
},
"16":{
"name":"TuneIn",
"id":"0010001800000001",
"hidden":1
},
"17":{
"name":"ARTE",
"id":"0020000600000001",
"hidden":1
},
"18":{
"name":"Plex",
"id":"0076010507000001",
"hidden":1
},
"19":{
"name":"CHILI",
"id":"0020004700000002",
"hidden":1
},
"20":{
"name":"Netzkino",
"id":"0076011607000001",
"hidden":1
},
"21":{
"name":"Meteonews TV",
"id":"0020007100000001",
"hidden":1
},
"22":{
"name":"Audio Link",
"id":"0387878700000141",
"hidden":1
},
"23":{
"name":"VIERA Link",
"id":"0387878700000016",
"hidden":1
},
"24":{
"name":"TV Guide",
"id":"0387878700000003",
"hidden":1
},
"25":{
"name":"TV-Aufnahmen",
"id":"0387878700000013",
"hidden":1
},
"26":{
"name":"Multi Window",
"id":"0387878700000050",
"hidden":1
},
"27":{
"name":"Smart Speaker Settings",
"id":"0387878700000146",
"hidden":1
},
"28":{
"name":"Kalender",
"id":"0387878700150020",
"hidden":1
},
"29":{
"name":"Mitteilungszentrale",
"id":"0387878700000140",
"hidden":1
},
"30":{
"name":"List Application",
"id":"0387878700000153",
"hidden":1
}
},
"TUNER":{
"hidden":0
}
},
"ipAddress":"192.168.178.45",
"specs":{
"friendlyName":"Fernseher",
"manufacturer":"Panasonic",
"modelName":"Panasonic VIErA",
"modelNumber":"TX-65HX940WA",
"requiresEncryption":true,
"serialNumber":"4D454930-0200-1000-8001-B46C4743042F"
}
}
}
} |
if i'm seeing things right your issue will only come back after a somewhat long while. tentative fix would/should make it go away. so, ideally it would be great to install beta as soon as possible on your side as if the issue does not ever come back then i fixed it otherwise there's something else going on. [and i need to know about eventual fix side effects :-) ] thanks again for your patience! have a great weekend too! [hopefully with better weather than here] |
Hi @AntonioMeireles, i found some time to install your beta package. After installing it via Homebridge Terminal it displayed the following output. There appeared some warnings, is this okay? I restarted the Homebridge as usual after updating homebridge configuration, everything seems to be running - no errors or warnings in homebridge output after the restart. The Homebridge Plugin page keeps showing me the old (latest release) version of this plugin, this could be normal since i updated the package not via Homebridge store, just want to make sure, I did everything right? Thanks again for the help! Let's see how it will work the next days / week. I will report any further issues or abnormalities here, as soon i will find them ;) |
[sorry lag] i'm not sure about your exact homebridge setup but probably what you want in your specific case to install beta is All the best, António |
Hi @AntonioMeireles, thanks for your respond. I did not retried it with the latest command to install the beta package like you posted in your last comment. How can I be sure, that i have the beta version in my current state? In my current installation state i just again experienced problems. I just sat on the couch and wanted to turn on the TV via Siri. Siri told it's on now, but nothing happened. So i went to the Home App and tried it manually to turn the TV on their. Again nothing happened. The On-button in the Home-App of the TV changed like the TV got turned on, so it was in 'ON'-state, some seconds later it changed to off state automatically. I tried it many times. The TV seems not to be responsive again now. Here the messages i got in the homebridge log when this happened: Should i first try to install your beta package again with Thanks for your further instructions. |
per the output you posted yesterday's install of beta ended in wrong place not being seen by homebridge. so, yes, you' d need to properly install the beta (which the `-g` should do)
regarding the errors you posted if i' m right they are resulting from the issue beta is attempting to fix
António
…On Fri, 12 Feb 2021 at 18:55, jeatrexs ***@***.***> wrote:
Hi @AntonioMeireles <https://github.com/AntonioMeireles>,
thanks for your respond. I did not retried it with the latest command to
install the beta package like you posted in your last comment. How can I be
sure, that i have the beta version in my current state?
In my current installation state i just again experienced problems.
I just sat on the couch and wanted to turn on the TV via Siri. Siri told
it's on now, but nothing happened. So i went to the Home App and tried it
manually to turn the TV on their. Again nothing happened. The On-button in
the Home-App of the TV changed like the TV got turned on, so it was in
'ON'-state, some seconds later it changed to off state automatically. I
tried it many times. The TV seems not to be responsive again now.
Here the messages i got in the homebridge log when this happened:
[image: grafik]
<https://user-images.githubusercontent.com/76820975/107809761-e6709c00-6d6b-11eb-908c-d435cb9e0ee6.png>
Should i first try to install your beta package again with
sudo npm i ***@***.*** -g
or should i already be using the beta since i updated it yesterday with
npm i ***@***.***
Thanks for your further instructions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFVQZ2O44UQA34RGZ2CRS3S6V2RBANCNFSM4XH25T5Q>
.
|
thanks. Installed it that way now, and now homebridge is showing me the installed beta version. |
Hi again, since installing the beta package I experienced a problem again last night, when i went to bed and tried to turn off the TV in the living room via Siri. It did not work. I also tried it via Home-App which did not worked neither. I just looked into the Homebridge log and found this: :( |
Hi again, this morning the automation did not work again. This time i got this errors in homebridge log:
|
Signed-off-by: António Meireles <[email protected]>
Signed-off-by: António Meireles <[email protected]>
ok. we're actually making (some) progress: OTOH you previously shown a trace where the TV was actually replying / alive / reachable but doing it in an unexpected way, so we may have more than a single issue here (as the later is a priori in my realm to fix, but the first (the please install thanks again for your patience |
I see. I will contemplate to open a support ticket for my WiFi Router to ask for any possibilities that could cause this problem. I just updated the plugin via homebridge to 2.0.23 as you recommended.
Is this a problem? Apart from that I will report any further occuring issues and problems. Thank you so much for your efforts! |
this is just weird (or so simple that i'm missing it). can you please mail me (address is in git commit logs) so that we establish a process to properly debug / track / fix this with less latency ? Thanks! |
this is a pre Requirement of the #67 (and #65 actually) ultimate fix Signed-off-by: António Meireles <[email protected]>
During the course of issue #67 there appeared similar problems to this one. Many new patches and minor version of the plugin were released which probably fixed this issues. Thanks for the great support @AntonioMeireles ! |
It happens sporadically that the TV does not respond when I either ask Siri to turn on / off the TV, or when my iPhone wants to turn on the TV via scheduled shortcut automation in the morning.
It also happened that I was sitting on the sofa and wanted to start the TV via iPhone Home app, even then it did not work sometimes. Or i wanted to turn it off and it just did not respond. Ironically i was able to change the volume, but not to turn it off...
I think my TV is configured correctly, because usually everything works. Is it possible that the TV disconnects from the Wi-Fi in standby mode, or there are even WiFi connection drops while the TV is running?
The last entry in the Homebridge log I could find about this is the following (if it happens the next time i will try to find anything immediately and let you know):
[7.2.2021, 01:12:05] [PanasonicVieraTV] (setPowerStatus)/-> into STANDBY - unable to power cycle TV - probably unpowered
Has anyone had this or similar problem before as well? Or could it be a misconfiguration on my part, or maybe a bug?
I am using a Panasonic TX-65HXN978.
Thanks in advance.
The text was updated successfully, but these errors were encountered: