dwaan / homebridge-adb

Homebridge script to control remote ADB enabled Android device
MIT License
74 stars 14 forks source link

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

Open DonAarya9163 opened 8 months ago

DonAarya9163 commented 8 months ago

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

DonAarya9163 commented 8 months ago

Thatā€™s the whole log ouput, it just instantly restarts right afterā€¦

SawkeeReemo commented 7 months ago

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 commented 7 months ago

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 commented 6 months ago

@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

SawkeeReemo commented 6 months ago

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.