Skip to content

Commit

Permalink
Merge pull request #256 from cgiesche/cgiesche-patch-1
Browse files Browse the repository at this point in the history
Update README.md
  • Loading branch information
cgiesche authored Feb 26, 2024
2 parents d651b44 + 2431aff commit 055c9dc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 055c9dc

Please sign in to comment.