-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Power on failed : Device is not connected. But it is ???? #102
Comments
That’s the whole log ouput, it just instantly restarts right after… |
Did you ever get a response about this? I’m having the same issue with my NVIDIA Shield Pro now. I switched to the official Homebridge container though. Maybe it doesn’t work with that one? |
From the log, it’s looks like nodejs spawn error. The
This error was produced when the plugins trying to call adb using spawn. The latest version doesn’t use spawn anymore to call adb. But I don’t know if fix the problem or not.
I’m using homebridge container and it works well. Without any log output I don’t know if you have the same problem or not. |
@dwaan I can now run homebridge with homebridge-adb, but I still have a problem, Also how do I switch to a Static IP ? I saw that somewhere else on reddit so maybe it is it ? I don't know if it already is a Static IP |
Just jumping in here because I completely nuked my Homebridge and started over yesterday. Saving ADB for last though since I was having issues with it. Just to answer your question, whatever box is running Homebridge, you need to reserve an IP for it on your router. How that is done depends on your router. Usually it in the DHCP Server settings somewhere. But avoid using the phrase “static IP,” as that typically means your external IP being a static IP address that you pay extra for. For routers, it usually called reserved IP if you want a device to have the same IP on your network every time it boots. |
Hey 😄
I set up the Homebridge ADB plugin for my Android TV (TPM191E, Philips 55OLED934/12) and it worked for a second until I started to get the same error again and again. Homebridge kept on restarting over and over again so I couldn’t use my other Homebridge connected devices on HomeKit. I think it maybe is because of the path for ADB tools but I quadruple-checked I think even… 5-times-checked or 6 times and I believe it’s the right path for ADB tools !
Log output :
The text was updated successfully, but these errors were encountered: