Skip to content
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

Open
DonAarya9163 opened this issue Oct 31, 2023 · 5 comments
Open

Power on failed : Device is not connected. But it is ???? #102

DonAarya9163 opened this issue Oct 31, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@DonAarya9163
Copy link

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 :
IMG_2491

  • Name: Philips 55OLED934/12 Android TV - TPM191E
@DonAarya9163 DonAarya9163 added the bug Something isn't working label Oct 31, 2023
@DonAarya9163
Copy link
Author

That’s the whole log ouput, it just instantly restarts right after…

@SawkeeReemo
Copy link

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?

@dwaan
Copy link
Owner

dwaan commented Dec 3, 2023

From the log, it’s looks like nodejs spawn error. The

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 : IMG_2491

  • Name: Philips 55OLED934/12 Android TV - TPM191E

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.

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?

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.

@DonAarya9163
Copy link
Author

DonAarya9163 commented Jan 3, 2024

@dwaan I can now run homebridge with homebridge-adb, but I still have a problem,
image
I can add it to home but even when the TV is on it shows off in Home and Homebridge Accessories
I tried powering it on (it already was on btw) and it said
image
I revoked all permissions on the TV, then I ran adb connect 192.168.1.180:5555, it asked me to approve on the TV so I did and then I ran adb devices to check and it was here and it didn't say unauthorized like before, it said device
So I tried restarting homebridge and it still didn't work

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

@DonAarya9163 DonAarya9163 changed the title Homebridge can’t run anymore because of ADB error Power on failed : Device is not connected. But it is ???? Jan 3, 2024
@SawkeeReemo
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants