You are right for the server.
the metadata is only the 4 figures after the F.
But unfortunately, it seems to not be working anymore.
below is what i was using but now plex is only throwing a crash report
{
"entity_id": "media_player.shield",
"command": "am start -a android.intent.action.VIEW -d plex://abcdefghijklmnopqrstuvwxyz0123456789ABCD/movie//library/metadata/3742"
}
Do you think this is a Plex issue or an ADB issue?
Hi could someone please help
I’ve been using the add on for months without issue yet since I rebooted this evening I’m seeing the following error message
2019-06-25 22:37:01 ERROR (SyncWorker_14) [root] ADB device is unavailable; encountered an error when searching for device.
2019-06-25 22:37:01 WARNING (SyncWorker_14) [homeassistant.components.androidtv.media_player] Could not connect to NVidia Shield at 192.168.1.184:5555 using ADB server at 127.0.0.1:5037
2019-06-25 22:37:01 ERROR (SyncWorker_14) [root] ADB device is unavailable; encountered an error when searching for device.
2019-06-25 22:37:01 WARNING (SyncWorker_14) [homeassistant.components.androidtv.media_player] Could not connect to NVidia Shield at 192.168.1.184:5555 using ADB server at 127.0.0.1:5037
2019-06-25 22:37:01 ERROR (SyncWorker_14) [root] ADB device is unavailable; encountered an error when searching for device.
2019-06-25 22:37:01 WARNING (SyncWorker_14) [homeassistant.components.androidtv.media_player] Could not connect to NVidia Shield at 192.168.1.184:5555 using ADB server at 127.0.0.1:5037
I’m running the latest 5.0 update and it states is connected
How do I get all my apps on android TV ?(miobox 3)
Hi i have a issue with this , the addon connect to my tvbox ,and say connected on log but the media player component on HA , say unavailible , after many reboots when TV Is on , and restarting also ha and the addon , i can see the media player component, but as soon reboot the HA the media player back to unavailible
I don’t know why my device looped as image, after restar the hassio addon, but when is looping , i don’t see any error or issue on logs
Which log has no errors, the HA log or the ADB server add-on log?
neither, on adb log only say “already connected to 192.168.1.42:5555” on every timeout reconnect, and on the HA log i don’t show any issue, but when restart the addon, back to normal, for a while , i think happens when mi tv box goes to standby and after a time go to play again
Try this as a custom component and post the HA log. It won’t fix the issue, but it will log a lot of info.
ok, let me do it
Thanks for posting the log. Unfortunately, I don’t know what the cause of the error is. Does it ever go back to a stable connection?
When it’s doing this, try using the androidtv.adb_command service to send the command echo hello and post the HA log results (just the relevant lines).
Random idea: try adding device_class: firetv to your config and let me know if the error still occurs.
hi, just now see the reply , let me do that and i post the log thanks
Release v0.5.1This is a general maintenance release.
Changes
Upgrades add-on base image to v3.1.4Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Release v0.5.2This is a general maintenance release.
Changes Upgrades add-on base image to v3.2.0Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Hi,
After some recent update, I have noticed that my nvidia shield stoped respond to HA. Log for adb addon looks ok:
[a6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: ADB - Android Debug Bridge
The Android Debug Bridge server program
-----------------------------------------------------------
Add-on version: 0.5.2
You are running the latest version of this add-on.
System: Arch Linux ARM (armv7 / odroid-xu)
Home Assistant version: 0.98.5
Supervisor version: 187
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] adb.sh: executing...
[cont-init.d] adb.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:54:42] INFO: Starting the Android Debug Bridge server...
[13:54:43] INFO: Connecting to device: 192.168.0.230...
connected to 192.168.0.230:5555
[13:57:43] INFO: Connecting to device: 192.168.0.230...
already connected to 192.168.0.230:5555
So what can be wrong?
To be honest I can find the point when it stopped to work. My bad.
Never mind start working again.
Release v0.5.3This is a general maintenance release.
Changes Upgrades add-on base image to v4.0.0Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
My nvidia shield keeps cycling between standby and playing despite it being in playing mode logs show no issues.
Exacly the same thing started happening to my configuration abourt a week ago.