You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the /api/discovery_info endpoint has been deprecated, we lost a
way to retrieve a unique identifier from the remote instance. This
change introduces /api/remote_homeassistant/discovery containing the
information we are missing. The downside is that the component now must
be installed on the remote instance as well. The upside however is that
we now can add any new endpoint we need for additional features in the
future, which is good.
Fixes#133
Copy file name to clipboardExpand all lines: README.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,12 +15,12 @@ Platform | Description
15
15
-- | --
16
16
`remote_homeassistant` | Link multiple Home-Assistant instances together .
17
17
18
-
The master instance connects to the Websocket APIs of the secondary instances (already enabled out of box), the connection options are specified via the `host`, `port`, and `secure` configuration parameters. If the secondary instance requires an access token to connect (created on the Profile page), it can be set via the `access_token` parameter. To ignore SSL warnings in secure mode, set the `verify_ssl` parameter to false.
18
+
The main instance connects to the Websocket APIs of the remote instances (already enabled out of box), the connection options are specified via the `host`, `port`, and `secure` configuration parameters. If the remote instance requires an access token to connect (created on the Profile page), it can be set via the `access_token` parameter. To ignore SSL warnings in secure mode, set the `verify_ssl` parameter to false.
19
19
20
20
After the connection is completed, the remote states get populated into the master instance.
21
21
The entity ids can optionally be prefixed via the `entity_prefix` parameter.
22
22
23
-
The component keeps track which objects originate from which instance. Whenever a service is called on an object, the call gets forwarded to the particular secondary instance.
23
+
The component keeps track which objects originate from which instance. Whenever a service is called on an object, the call gets forwarded to the particular remote instance.
24
24
25
25
When the connection to the remote instance is lost, all previously published states are removed again from the local state registry.
26
26
@@ -29,7 +29,7 @@ A possible use case for this is to be able to use different Z-Wave networks, on
29
29
30
30
## Installation
31
31
32
-
This component should be installed on the main instance of Home Assistant
32
+
This component *must* be installed on both the main and remote instance of Home Assistant
33
33
34
34
If you use HACS:
35
35
@@ -38,7 +38,18 @@ If you use HACS:
38
38
Otherwise:
39
39
40
40
1. To use this plugin, copy the `remote_homeassistant` folder into your [custom_components folder](https://developers.home-assistant.io/docs/creating_integration_file_structure/#where-home-assistant-looks-for-integrations).
41
-
2. Add `remote_homeassistant:` to your HA configuration.
41
+
42
+
43
+
**Remote instance**
44
+
45
+
On the remote instance you also need to add this to `configuration.yaml`:
46
+
47
+
```yaml
48
+
remote_homeassistant:
49
+
instances:
50
+
```
51
+
52
+
This is not needed on the main instance.
42
53
43
54
## Configuration
44
55
@@ -229,7 +240,7 @@ services:
229
240
230
241
### Missing Components
231
242
232
-
If you have remote domains (e.g. `switch`), that are not loaded on the master instance you need to list them under `load_components`, otherwise you'll get a `Call service failed` error.
243
+
If you have remote domains (e.g. `switch`), that are not loaded on the main instance you need to list them under `load_components`, otherwise you'll get a `Call service failed` error.
0 commit comments