mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 07:17:14 +00:00
u-z integrations: apply sentence-style capitalization (#29865)
* u-z integrations: apply sentence-style capitalization * Update source/_integrations/velux.markdown
This commit is contained in:
c0ffeeca7
GitHub
parent
39cc232bb3
commit
d35e999e6b
@ -30,7 +30,7 @@ Set up your API user credentials in your [UpCloud control panel](https://hub.upc
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Binary Sensor
|
||||
## Binary sensor
|
||||
|
||||
A binary sensor entity is set up for all discovered servers.
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ information on the update state:
|
||||
- `release_summary`: A summary of the release notes for the update available.
|
||||
- `release_url`: A link to the full release announcement for the update available.
|
||||
|
||||
## Device Classes
|
||||
## Device classes
|
||||
|
||||
The way these update entities are displayed in the frontend depend on their
|
||||
device classes. The following device classes are supported for switches:
|
||||
|
||||
@ -34,7 +34,7 @@ The **number** platform allows to control supply air temperatures.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Profile Switching
|
||||
## Profile switching
|
||||
|
||||
For convenient switching of ventilation profiles in the GUI, just click on the `Vallox` fan entity to get a drop-down menu to select from. Alternatively, the service `fan/set_preset_mode` can be used.
|
||||
|
||||
@ -45,7 +45,7 @@ The four standard Vallox profiles are supported:
|
||||
- `Boost`
|
||||
- `Fireplace`
|
||||
|
||||
## Fan Services
|
||||
## Fan services
|
||||
|
||||
### Service `vallox.set_profile_fan_speed_home`
|
||||
|
||||
|
||||
@ -50,7 +50,7 @@ The following values are supported for the preset_mode state attribute:
|
||||
|
||||
Note - Please ensure that you update your thermostat to the latest firmware. Initially tested on firmware 5.10 and currently VH6.79.
|
||||
|
||||
### Enabling Local API
|
||||
### Enabling local API
|
||||
Local API mode needs to be enabled on the thermostat itself. It cannot be enabled using the Venstar mobile apps or Skyport cloud service. Exact steps vary across different [series](https://venstar.com/thermostats/) of thermostats:
|
||||
|
||||
- [ColorTouch](https://venstar.com/thermostats/colortouch/)
|
||||
|
||||
@ -112,7 +112,7 @@ Eco mode reduces the target temperature by 3°C, whereas Comfort mode sets the t
|
||||
| `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. To target all entities, use `all` keyword instead of entity_id.
|
||||
| `preset_mode` | no | New value of preset mode.
|
||||
|
||||
## Water Heater
|
||||
## Water heater
|
||||
|
||||
It is not possible to turn on/off water heating via the Water Heater integration since this would conflict with the operation modes of the heating integration. Therefore the operation mode of that integration is just available as an attribute and cannot be modified.
|
||||
|
||||
|
||||
@ -39,7 +39,7 @@ To change the settings, go to {% my integrations title="**Settings** > **Devices
|
||||
|
||||
## Additional info
|
||||
|
||||
### Device Tracker
|
||||
### Device tracker
|
||||
|
||||
**Note**: If you don't want to automatically track newly detected devices, disable the integration system option `Enable new added entities`.
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ The `volvooncall` integration offers integration with the [Volvo Cars App](https
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
### Available Resources
|
||||
### Available resources
|
||||
|
||||
The list of currently available resources:
|
||||
|
||||
|
||||
@ -187,7 +187,7 @@ name:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### Additional Examples
|
||||
### Additional examples
|
||||
|
||||
Full example that produces `switch.amazing_server`, assuming a subscription that has an ID of `123456` and a label of `Web Server`:
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ device:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## Binary Sensor
|
||||
## Binary sensor
|
||||
|
||||
The `w800rf32` platform supports X10 RF binary sensors such as Palm Pad remotes, key chain remotes, Hawkeye motion detectors, and many, many other X10 RF devices. Some that have specifically been used with this are the KR19A keychain, MS16A motion detector and the RSS18 four button wall mount keypad.
|
||||
|
||||
|
||||
@ -265,7 +265,7 @@ value_template:
|
||||
|
||||
If a property works in *optimistic mode* (when the corresponding state topic is not set), Home Assistant will assume that any state changes published to the command topics did work and change the internal state of the entity immediately after publishing to the command topic. If it does not work in optimistic mode, the internal state of the entity is only updated when the requested update is confirmed by the device through the state topic. You can enforce optimistic mode by setting the `optimistic` option to `true`. When set, the internal state will always be updated, even when a state topic is defined.
|
||||
|
||||
## Using Templates
|
||||
## Using templates
|
||||
|
||||
For all `*_state_topic`s, a template can be specified that will be used to render the incoming payloads on these topics. Also, a default template that applies to all state topics can be specified as `value_template`. This can be useful if you received payloads are e.g., in JSON format. Since in JSON, a quoted string (e.g., `"foo"`) is just a string, this can also be used for unquoting.
|
||||
|
||||
|
||||
@ -48,7 +48,7 @@ password:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## Binary Sensor
|
||||
## Binary sensor
|
||||
|
||||
To enable the binary sensor platform for your tags, set up with your [wirelesstag.net](https://wirelesstag.net/) account. Add the following to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ The Soundavo WS66i 6-Zone Amplifier integration allows you to control the [Sound
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Configuration Notes
|
||||
## Configuration notes
|
||||
|
||||
Enter the IP Address of the WS66i amplifier when prompted to connect to the device and hit submit. It will detect the number of connected amplifiers and present each zone as an entity.
|
||||
|
||||
@ -29,6 +29,6 @@ Enter the IP Address of the WS66i amplifier when prompted to connect to the devi
|
||||
|
||||
Once detected, you can add them to an area.
|
||||
|
||||
## Source Management
|
||||
## Source management
|
||||
|
||||
You can configure source names by hitting the **CONFIGURE** button in the integration card.
|
||||
|
||||
@ -32,7 +32,7 @@ The Yamaha MusicCast integration implements the grouping services. There are som
|
||||
- It is not possible to let mediaplayer entities of the same device (e.g., different zones) be in distinct groups.
|
||||
- If a non-main zone is the master of a group, it is not possible to let other mediaplayers of the same device join this group.
|
||||
|
||||
## Play Media functionality
|
||||
## Play media functionality
|
||||
|
||||
The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text-to-speech services.
|
||||
|
||||
@ -66,7 +66,7 @@ data:
|
||||
|
||||
Depending on the features supported by the device, several entities will be added for every MusicCast Device. Some of the entities are related to the MusicCast device and some are related to a zone of the device. All device and main zone related entities will be assigned to the Home Assistant device of the main zone. Entities related to other zones will be assigned to the Home Assistant device of the corresponding zone.
|
||||
|
||||
### Number Entities
|
||||
### Number entities
|
||||
|
||||
The following entities will be added, if they are supported by the MusicCast device:
|
||||
- Equalizer (configuration, zone level)
|
||||
@ -80,7 +80,7 @@ The following entities will be added, if they are supported by the MusicCast dev
|
||||
- DTS Dialogue Control (configuration, zone level)
|
||||
- Control the volume of dialogues for DTS:X content
|
||||
|
||||
### Select Entities
|
||||
### Select entities
|
||||
The following entities will be added, if they are supported by the MusicCast device:
|
||||
- Dimmer (configuration, device level)
|
||||
- Set the display brightness
|
||||
@ -99,7 +99,7 @@ The following entities will be added, if they are supported by the MusicCast dev
|
||||
- Link Audio Quality (configuration, zone level)
|
||||
- Set the audio quality for grouped speakers
|
||||
|
||||
### Switch Entities
|
||||
### Switch entities
|
||||
The following entities will be added, if they are supported by the MusicCast device:
|
||||
- Speaker A (configuration, device level)
|
||||
- A switch to turn on the speaker set A
|
||||
|
||||
@ -112,7 +112,7 @@ zabbix:
|
||||
- sensor.time
|
||||
```
|
||||
|
||||
## Configure Filter
|
||||
## Configure filter
|
||||
|
||||
By default, no entity will be excluded. To limit which entities are being published to Zabbix, you can use the `include` and `exclude` parameters.
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ zpid:
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
### Additional Attributes
|
||||
### Additional attributes
|
||||
|
||||
The following additional attributes are also available via the sensor.
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ get the Zeversolar IP address.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Sensor Types
|
||||
## Sensor types
|
||||
|
||||
When configured, the integration will create two sensors for each configured inverter:
|
||||
|
||||
|
||||
@ -105,7 +105,7 @@ action:
|
||||
name: Home
|
||||
```
|
||||
|
||||
## Binary Sensor
|
||||
## Binary sensor
|
||||
|
||||
The `zoneminder` binary sensor platform lets you monitor the availability of your [ZoneMinder](https://www.zoneminder.com) install.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user