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
description: Set this, if Home Assistant is reachable under a different IP from the CCU (NAT, Docker etc.).
69
69
required: false
70
70
type: string
71
71
callback_port:
72
72
description: Set this, if Home Assistant is reachable under a different IP from the CCU (NAT, Docker etc.).
73
73
required: false
74
-
type: int
74
+
type: integer
75
75
resolvenames:
76
76
description: Try to fetch device names. Defaults to `false` if not specified.
77
77
required: false
78
-
type: map
78
+
type: string
79
79
default: false
80
-
keys:
81
-
metadata:
82
-
description: Homegear provides device-names through the metadata devices have internally. When using an HM-CFG-LAN interface, you typically use a configuration software ("HomeMatic-Komponenten konfigurieren" is the name of the shortcut on your desktop by default) to pair and configure your devices. If you have paired devices, you'll see them listed in a table. The leftmost column (Name) is prefilled with default names. You can click such a name and enter whatever you like.
83
-
json:
84
-
description: The CCU allows to fetch details of the paired devices via JSON-RPC. For this to work you need to add valid credentials to your component-configuration. Guest-access is sufficient to query for device names.
85
-
xml:
86
-
description: If you use a CCU, there is an add-on called the "XML-API". With it installed, you are able to fetch all kinds of information from you CCU using XML-RPC. We can leverage this and fetch the names of devices set within the CCU. We don't support authentication with this method.
87
80
jsonport:
88
81
description: Port of CCU JSON-RPC Server. The default is 80, but it may be different when running CCU virtually via Docker.
89
82
required: false
90
-
type: int
83
+
type: integer
91
84
username:
92
85
description: When fetching names via JSON-RPC, you need to specify a user with guest-access to the CCU.
93
86
required: false
@@ -157,9 +150,9 @@ homematic:
157
150
158
151
We use three approaches to fetch the names of devices. Each assumes you have properly named your devices in your existing Homematic setup. As a general advice: Use ASCII for your devices names. Home Assistant won't include non-ASCII characters in entity-names.
159
152
160
-
1. `json`
161
-
2. `xml`
162
-
3. `metadata`
153
+
1. `json`: The CCU allows to fetch details of the paired devices via JSON-RPC. For this to work you need to add valid credentials to your component-configuration. Guest-access is sufficient to query for device names.
154
+
2. `xml`: If you use a CCU, there is an add-on called the "XML-API". With it installed, you are able to fetch all kinds of information from you CCU using XML-RPC. We can leverage this and fetch the names of devices set within the CCU. We don't support authentication with this method.
155
+
3. `metadata`: Homegear provides device-names through the metadata devices internally have. When using an HM-CFG-LAN interface, you typically use a configuration software ("HomeMatic-Komponenten konfigurieren" is the name of the shortcut on your desktop by default) to pair and configure your devices. If you have paired devices, you'll see them listed in a table. The leftmost column (Name) is prefilled with default names. You can click such a name and enter whatever you like.
163
156
164
157
Resolving names can take some time. So when you start Home Assistant you won't see you devices at first. For a setup with 20+ devices it can take up to a minute until all devices show up in the UI.
0 commit comments