docs: updated README with requirements, settings, known issues

Author: zehnm

README.md

@@ -8,10 +8,11 @@ Source list is limited to a predefined list as retrieving a list of installed ap
 
 This integration is included in the Remote Two firmware and no external service must be run to connect with Android TV
 devices. A standalone service can be used for development or connecting multiple devices.
-A single instance of the integration doesn't support multiple Android TV devices yet (planned: [#14](https://github.com/aitatoi/integration-androidtv/issues/14)).
 
-Device profiles allow device specific support and custom key bindings, for example double-click or long-press actions.
-See [command mappings](docs/command_mapping.md) for more information.
+- [Requirements and setting](docs/settings.md).
+- Multiple Android TV devices are supported with version 0.5.0 and newer.
+- Device profiles allow device specific support and custom key bindings, for example double-click or long-press actions.  
+  See [command mappings](docs/command_mapping.md) for more information.
 
 ## Standalone Usage
 ### Setup
@@ -38,8 +39,10 @@ For running a separate integration driver on your network for Remote Two, the co
 UC_CONFIG_HOME=./config python3 intg-androidtv/driver.py
 ```
 
-See available [environment variables](https://github.com/unfoldedcircle/integration-python-library#environment-variables)
-in the Python integration library to control certain runtime features like listening interface and configuration directory.
+- See available [environment variables](https://github.com/unfoldedcircle/integration-python-library#environment-variables)
+  in the Python integration library to control certain runtime features like listening interface and configuration directory.
+- The client name used for the client certificate can be set in ENV variable `UC_CLIENT_NAME`.
+  The hostname is used by default. 
 
 ## Build self-contained binary
 

docs/settings.md

@@ -0,0 +1,45 @@
+# Requirements and Settings
+
+## Requirements
+
+- Only devices running the [Android TV Remote Service](https://play.google.com/store/apps/details?id=com.google.android.tv.remote.service)
+  are supported.
+  - ‼️ This service does not work on Fire TV devices.
+- Only devices in the same network can be discovered.
+- The mDNS protocol must be allowed in your network.
+  - In most consumer networks the mDNS protocol is allowed and when the Remote and the Android TV device(s) are on the
+  same network, the Remote should have no difficulties finding the device(s).
+  - When using mesh networking or professional networking gear, mDNS may be disabled or only specific mDNS services may
+    be allowed.  
+    In such cases, please check the manufacturer's documentation on how to enable mDNS or specific mDNS services.
+
+## Limitations and Known Issues
+
+- During the setup process, you have to enter a PIN code that is shown on your Android TV.
+  - Please make sure that your Android TV is powered on and that no old pairing request is shown.
+  - If pairing continuously fails, reboot your Android TV device and try again.
+  - If sending commands doesn't work after pairing or the integration is repeatedly disconnected, try rebooting the
+    Android TV device.
+- Verify with the Google TV mobile app or the Google Home mobile app to send commands to the Android TV device.
+  - If these don't work, neither will this integration.
+- Not every app will work or supports all keycodes.
+  - For example, some IP-TV apps don't support channel-up & down commands.  
+- Some devices, like TCL, become unavailable after they are turned off, unless you activate the `Screenless service`.  
+  - Activate it under: Settings, System, Power and energy: Screenless service
+
+See also the known issues of [Home Assistant's Android TV Remote Integration](https://www.home-assistant.io/integrations/androidtv_remote/#limitations-and-known-issues),
+since it is using the same communication library.
+
+## Application Settings
+
+### Kodi
+
+If navigation doesn't work within the Kodi app, an additional input controller needs to be configured first with the
+original Android TV remote:
+
+1. Start Kodi
+2. Go to Settings, System, Input: `Configure attached controllers`
+3. Select `Get more...`
+4. Scroll down and select `TV Remote`
+5. Configure buttons: select a button in the list with the original remote, then confirm it with the corresponding
+   Remote Two button.