fixed typos, spelling mistakes (#3436)
This commit is contained in:
parent
9d94f28131
commit
3f1972b97b
139 changed files with 209 additions and 209 deletions
|
@ -35,7 +35,7 @@ homematic:
|
|||
Configuration variables (global):
|
||||
|
||||
- **hosts** (*Required*): Configuration for each host to integrate into Home Assistant.
|
||||
- **local_ip** (*Optional*): IP of device running Home Assistant. Override autodetected value for exotic network setups.
|
||||
- **local_ip** (*Optional*): IP of device running Home Assistant. Override auto-detected value for exotic network setups.
|
||||
- **local_port** (*Optional*): Port for connection with Home Assistant. By default it is randomly assigned.
|
||||
|
||||
Configuration variables (host):
|
||||
|
@ -87,7 +87,7 @@ Resolving names can take some time. So when you start Home Assistant you won't s
|
|||
|
||||
In order to allow communication with multiple hosts or different protocols in parallel (wireless, wired and ip), multiple connections will be established, each to the configured destination. The name you choose for the host has to be unique and limited to ASCII letters.
|
||||
Using multiple hosts has the drawback, that the services (explained below) may not work as expected. Only one connection can be used for services, which limits the devices/variables a service can use to the scope/protocol of the host.
|
||||
This does *not* affect the entites in Home Assistant. They all use their own connection and work as expected.
|
||||
This does *not* affect the entities in Home Assistant. They all use their own connection and work as expected.
|
||||
|
||||
### {% linkable_title Reading attributes of entities %}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue