Stability issues #46
Comments
|
If you have new findings and want to share them here, please make sure to
I'll start extensive testing in my environment soon and try to reproduce the networking issues (delayed messages) first with fix for crashes of Homebridge applied. |
|
Homebridge is crashing for me. If I send a command to fast together it will crash. I tried reinstalling the plugin. |
|
I'm not sure if I'm right in this thread. Since a few days the plugin crashes very often, on average every 30 to 45 minutes, without me using it or any automation triggering it. The error message is: Error: This socket has been ended by the other party. Which socket is meant and why there is a party on my Raspi? I've enabled the API of your plugin. I see that this error is triggered by node-apple-tv-x, so maybe I'm not only in the wrong thread, but I'm asking the wrong developer? :-D |
|
@sschuste You're at the right place! The PR has not been accepted by stickpin yet, I added a new comment, maybe he forgot about it. Anyways, if the PR is not not merged within the next days, I'll reference my fork of node-appletv-x in the plugin. This should solve the issue of writing to the closed connection. I haven't found out why some people have this issue so often and others (including me) haven't seen this once. |
|
All right. I'll wait and see. Normally I would hardly notice a crash of the Homebridge, but I have a small monitoring system running and it generates an hearable acoustic signal when the Homebridge is down. At the moment the alarm is triggered very often. Interesting might be the accumulation of alarms. I grep'd my logs starting at May 10th: Something has changed. Apple TV update? |
|
Great plugin!! But I have the same problem AppleTv 4k 32go v13.3.1 (not the latest), Homebridge 1.1.1 , raspbian buster 4.19.66-v7+ and an error message at the startup of homebridge. (same error socket than sschuste). The normal CPU charge is about 2% without plugin and with plugin on the first hour was 8%, and then I had some crashes of homebridge 40% (no refresh of the accessories and impossible commands). Thanks in advance |
|
Looking forward to get this fix. Knowing it's not all in your hands @lukasroegner |
|
Not sure yet if its relevant but I've been running this plugin for months without issue but last night updated from Jessie to Buster and immediately started seeing the socket issue above. Still poking around. |
|
Further to this, I simply removed the plugin from homebridge and re-added after the buster update and haven't seen the issue since. Raspbian GNU/Linux Buster (10) |
|
New version is now on NPM, which points to my fork of |
|
Hi @lukasroegner, Upgrading the plugin to 0.8.6 gives the following error: |
|
Have you tried with |
|
|
I think the issue is that the dependency "node-appletv-x" is already installed, but now re-installed and updated from a different source. Can you try to uninstall the plugin (which should also uninstall "node-appletv-x" and reinstall it? |
|
I am sorry but that didn't help either ... I uninstalled |
|
This is what I did to check if installation works: |
|
Did exactly what you did ... |
|
If you try to install the previous version of the plugin, does that still work? |
|
Yes that still works: |
|
What about vs. |
|
The first command executes successful, but the second causes the error, apparently the fork doesn't want to get installed ... |
|
That is super strange. The only thing that I changed is a line of code and the version number... |
|
Let me setup a new homebridge container to see if that solves the issue of installing the fork.. [update] in a container where neither node-appletv-x nor lukasroegner/node-appletv-x.git nor homebridge-apple-tv-remote has been installed before:
|
|
In the same container, does |
|
yes it does: |
|
@lukasroegner I tried to update with config-ui-x and run into this error. 2020-06-21T09_42_37_971Z-debug.log |
|
Hi, I don't know what OS is being used by the persons that are reporting problems with this plugin, in my case I downloaded the Raspberry PI Raspbian image (from https://github.com/homebridge/homebridge-raspbian-image) and it's been running with 0 errors now for many months. I really appreciate the work done by lukasroegnser, I was using another software for my apple tv's (https://github.com/lprhodes/homebridge-apple-tv) that at the end gave me nothing but problems. |
|
First time installing this plugin.
But upon clicking the switch my homebridge dies with the following logs. (I've also seen this heartbeat issue mentioned elsewhere in here)
My apply TV is currently on the latest tvOS14. I've also seen this log printed after another failed attempt. |
|
After I noticed that there is a new update, I started the next attempt. I had this stupid load problem all the time and the temperature rise. In the end I had to uninstall your plugin. I am thrilled! Now your plugin runs even with my setup. Load is stable, and so is the temperature of the Raspi. Lukas, thank you very much for the effort you put into this plugin. My apartment has become a little more beautiful again. I only use the plugin to switch the ATV on and off. I can't say anything about all the other functions, but what I need works just fine. |
|
Hey are you still on the part with the delayed messages since tvOS 14 it happens very often? |
|
@try-and-error-and-repeat I haven't had issues with delayed responses from the Apple TV in the past and cannot reproduce this issue on tvOS. It still seems to depend on the host system and/or network configuration. I'm running the plugin on a Raspberry Pi 4, connected via Ethernet, plain Homebridge (no HOOBS), Amplifi router. The switches are updated within milliseconds. |
|
@lukasroegner I had no problem until the update to tvOS 14. It worked fine and was 99% reliable. I use a Raspberry Pi 3, connected via Ethernet (Gigabit on the same network switch as the Apple TV 4K) also plain homebridge, FRITZ!Box 7490 Router and homebridge with Version 1.2.2. Node.js with version 12.18.4 and npm 6.18.4. home hub is also the Apple TV 4K |
|
Plug-in is causing homebridge to give error sigterm command received and causing it to not be able to start, homebridge will not even start up with the plugin installed. |
|
@brj5 Can you please provide debug logs so that the cause of your issue can be investigated? |
|
INFO: Homebridge Version: 2.6 [9/27/2020, 9:41:52 PM] Homebridge v1.2.3 is running on port 52108. |
|
I never had problems with the delay that people are talking about here, it always worked instantly for me. But since the updates from last weekend there is a big delay. Everything is updated to it's latest version. Nothing has changed in the network. |
|
I reinstalled the plugin and now the problem is only related to the play Pauze buttons, I added the application related buttons for Netflix and YouTube as well. But they behave the same way. |
|
Same problem. Running it on a separate RPi 3 with just this plugin and homebridge UI X. So the Problem is not related to other plugins. I can send debug logs if this would help. |
|
I get this error every 7 seconds for 15 to 20 minutes every time I restart HomeBridge, until it finally connects to my Apple TV. I'm on a clean UniFi network. Anything I can do about it? Thanks!
|
|
Greetings to all. Not sure whether it is the right place to post my issue or not. Please help and advise. I have installed homebridge-apple-tv-remote in my RP Hoobs. But stopped the server frequently. Any suggestion? Also, like to know if there is refresh option for the connection. |
I provided the logs in a post above, I retried this again and got the same error, I really want this to work so I can use Alexa with my tv. |
|
Hi, looks like I also have a delay issue, at least it’s related to Play / Pause button. So when I press Play / Pause on AW, remote, AirPods I see that in Home app it changes state only after 30-40 seconds. Problem is that I have some automations in which this switch is involved and those are also being executed with the same delay which is quite annoying =( Besides that, if I press Play / Pause when it’s out of sync (during these 30-40 seconds) playback starts (or stops) and at the time it is synced it might be already in wrong state, meaning if playback is on, switch shows Pause state. Thx for any help in advance @lukasroegner My setup is: |
|
I'm also experiencing the same delay issue as @njuart, same setup as well. Strange thing is that it worked flawlessly for the first hour. |
|
@lukasroegner Thanks so much for this plugin, it's a great plugin! I'm experiencing this same delay/out of sync play/pause button issue as @njuart has mentioned. MacOS |
|
Today I tried to connect my second Apple TV and did not gave him a unique Name for the Play Pause and the On Off Switch and it worked. So I tried the same with my first Apple TV with the "Out-Of-Sync-Problem" and it worked also. I'll take a closer look to that in the next few days but maybe it helps others also. My Config looks like this right now: |
|
has anyone gotten on/off detection to work super reliably? It's not perfect on my end but hoping to figure this out so I can layer automation on top :) |
|
I do also experience a delay with the atv turn on/off switch. Is there a know reason behind? |
Just wanted to give this more visibility. I was having problems, I removed the unique name and it fixed it! |
|
No Apple TVs found on the network. Try again. latest TVOS any work around? TIA |
|
Like many others I have the connection problem since OS15: Will you get your plugin working again? |
and others
There are three main issues with the plugin in its current state:
Delayed messages
For some users, messages from the Apple TV to the plugin are delayed (sometimes for minutes), resulting in switches that are out of sync. As the on/off switch emulates remote input, it also cannot execute the correct action if the plugin state is out of sync with the Apple TV state.
On/off detection
The logic to detect whether an Apple TV is on or off is not correct, yet. Currently, three state variables are considered to check whether the Apple TV is on:
Crashes of homebridge
For some users, connections to the Apple TV are suddenly closed, resulting in an unhandled exception when the plugin tries to send a message through the closed channel. The PR for fixing the request has also been submitted, but not accepted, yet: stickpin/node-appletv-x#3
The text was updated successfully, but these errors were encountered: