From 2431aff1202064bc6cbecfbb8e154372d9dffbe5 Mon Sep 17 00:00:00 2001 From: Christoph Giesche Date: Mon, 26 Feb 2024 23:26:19 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4ae9599..cad8a70 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ There are two sections on the plugin's configuration panel: ## Home Assistant Settings * Server URL: `ws://your-homeassistant-ip-or-hostname:your-homeassistant-port/api/websocket`, for example (local network) `ws://192.126.0.5:8123/api/websocket` or (public, with ssl enabled on default port 443) `wss://my-secure-homeassistant.com/api/websocket`. - * Access Token: An long-lived access-token obtained from your Home Assistant. + * Access Token: An long-lived access-token (with admin right) obtained from your Home Assistant. The plugin requires the admin rights, because it uses "execute-script" command that is restricted to admin users. _Long-lived access tokens can be created using the "Long-Lived Access Tokens" section at the bottom of a user's Home Assistant profile page._ (Quote from https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token) After you save your Home Assistant Settings, the plugin will automatically try to connect to your Home Assistant installation. If the connection was successful, the Entity Settings section should allow you to see and configure your entities.