klionanywhere.blogg.se - Zdf mediathek chromecast problem

Zdf mediathek chromecast problem how to#
Zdf mediathek chromecast problem install#
Zdf mediathek chromecast problem tv#

Zdf mediathek chromecast problem how to#

Follow the directions from the addOn how to get this up and running.

Zdf mediathek chromecast problem install#

If not already done, install the addOn Samba from the addOn-store in Supervisor. When you feel you are good to go, then move over to Supervisor and uninstall the ADB server addOn. This is not time relevant, you can leave it for a few days to see if everything is ok.

After checking that everything is working, you can uninstall the ADB server addOn in Supervisor.

Check also the HA log, if any warnings or errors come up.

Check if everything is working, send some commands, try to turn it on and off, these things.

After the restart you shuld be up and running with the new PythonADB.

Disable both “Start at boot” and “Watchdog”.

Go to Supervisor and open the ADB server page.

Should look like this in the above example:.

Add the following line at the place, where you deleted the previous lines, like so (adjust to the folder address you wrote down earlier):.

Remove both lines adb_server_ip and adb_server_port completely.

# Based on adding my NVidia Shield, which has IP 192.168.1.34. Locate and open the file, where you configured your ADB server, normally it is configuration.yaml. Write down the file path starting with the config folder, should be something like /config/.androidkeys/adbkey.

If you have found the folder, look in it for a file that is called adbkey with no file extension.

If you can’t find it, look downwards for a more detailed explanation. Notice the dot in front of the folder name! The dot means it is hidden from normal view.

Look in your config folder (the one where your configuration.yaml resides) for a hidden folder named something like.

Good it’s working! You could have taken the stored adbkeys, but a new one should do without problems, too.įor everyone who is running into the same problems, here is the way to disable the addOn and change back to the built-in PythonADB:

Zdf mediathek chromecast problem tv#

But the TV “Fernseher” is on standby and replies to ping. The second TV “Glotze” is powered off, so that error is ok. Integration: androidtv (documentation, issues)Ĭould not connect to Glotze at 192.168.2.53:5555 using ADB server at 127.0.0.1:5037Ĭould not connect to Fernseher at 192.168.2.50:5555 using Python ADB implementation with adbkey='/config/.storage/androidtv_adbkey' Source: components/androidtv/media_player.py:227 TcpTimeoutException: Reading from 192.168.2.50:5555 timed out (10.0 seconds)Īnd Logger: _player Retrying in 60 seconds.Īnd Logger: androidtv.adb_manager.adb_manager_async Integration: Mediaplayer (documentation, issues)

When I remove the adb_server_ip the log says this: Logger: _player

So this is my config with the adb_server_ip configured for the addon: platform: androidtvĬom.: "Prime Video"Ĭom.: "ZDF Mediathek"