Merge branch 'main' into min-chrome-ver

README.md

@@ -1,5 +1,7 @@
 # Appium LG WebOS Driver
 
+[![npm version](https://img.shields.io/npm/v/appium-lg-webos-driver.svg)](https://npmjs.org/package/appium-lg-webos-driver)
+
 An Appium 2.x driver for LG WebOS apps
 
 ⚠️  UNDER ACTIVE DEVELOPMENT ⚠️
@@ -22,6 +24,7 @@ package in your `package.json`)
 - You must have an LG webOS TV device on the same network as your Appium host, with all ports accessible to the network
 - The TV must be in [Developer Mode](https://webostv.developer.lge.com/develop/getting-started/developer-mode-app) (must have the Dev Mode app and be signed in, with Dev Mode actually turned "On" in the app)
 - You must have your TV device set up and showing as available using the [`ares-setup-device`](https://www.webosose.org/docs/tools/sdk/cli/cli-user-guide/#ares-setup-device) CLI tool
+    - Please use v`1.12.4` which is available from https://webostv.developer.lge.com/develop/tools/webos-tv-cli-installation for now. (or [this comment for Linux](https://github.com/headspinio/appium-lg-webos-driver/pull/57#issuecomment-2153496885))
 - You should be able to run `ares-device-info --device <name>` and have it show the correct details for your connected device
 - The first time you run an Appium session, the driver will attempt to pair itself with the TV as a remote. A permission popup will appear that you need to interact with. You should only need to do this once. If the driver is reinstalled, its permission token cache is removed, or the TV is updated (and potentially even some other circumstances) re-pairing might be necessary.
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "appium-lg-webos-driver",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "LG WebOS support for Appium",
   "keywords": [
     "appium",