diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 3833fbd041e..8cd2284fd57 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -18,7 +18,9 @@ Supported by MQTT discovery: - [HVACs](/integrations/climate.mqtt/) - [Lights](/integrations/light.mqtt/) - [Locks](/integrations/lock.mqtt/) +- [Numbers](/integrations/number.mqtt/) - [Scenes](/integrations/scene.mqtt/) +- [Selects](/integrations/select.mqtt/) - [Sensors](/integrations/sensor.mqtt/) - [Switches](/integrations/switch.mqtt/) - [Tag Scanners](/integrations/tag.mqtt/) diff --git a/source/_integrations/select.mqtt.markdown b/source/_integrations/select.mqtt.markdown new file mode 100644 index 00000000000..c69f3cbb746 --- /dev/null +++ b/source/_integrations/select.mqtt.markdown @@ -0,0 +1,148 @@ +--- +title: "MQTT Select" +description: "Instructions on how to interact with a device exposing a Select through MQTT from within Home Assistant." +ha_category: + - Select +ha_release: 2021.7 +ha_iot_class: Configurable +ha_domain: mqtt +--- + +The `mqtt` Select platform allows you to integrate devices that might expose configuration options through MQTT into Home Assistant as a Select. Every time a message under the `topic` in the configuration is received, the select entity will be updated in Home Assistant and vice-versa, keeping the device and Home Assistant in sync. + +## Configuration + +To enable MQTT Select in your installation, add the following to your `configuration.yaml` file: + +```yaml +# Example configuration.yaml entry +select: + - platform: mqtt + command_topic: topic + name: "Test Select" + options: + - "Option 1" + - "Option 2" +``` + +{% configuration %} +availability: + description: A list of MQTT topics subscribed to receive availability (online/offline) updates. Must not be used together with `availability_topic`. + required: false + type: list + keys: + payload_available: + description: The payload that represents the available state. + required: false + type: string + default: online + payload_not_available: + description: The payload that represents the unavailable state. + required: false + type: string + default: offline + topic: + description: An MQTT topic subscribed to receive availability (online/offline) updates. + required: true + type: string +availability_topic: + description: The MQTT topic subscribed to receive availability (online/offline) updates. Must not be used together with `availability`. + required: false + type: string +availability_mode: + description: When `availability` is configured, this controls the conditions needed to set the entity to `available`. Valid entries are `all`, `any`, and `latest`. If set to `all`, `payload_available` must be received on all configured availability topics before the entity is marked as online. If set to `any`, `payload_available` must be received on at least one configured availability topic before the entity is marked as online. If set to `latest`, the last `payload_available` or `payload_not_available` received on any configured availability topic controls the availability. + required: false + type: string + default: latest +command_topic: + description: The MQTT topic to publish commands to change the selected option. + required: true + type: string +device: + description: "Information about the device this Select is a part of to tie it into the [device registry](https://developers.home-assistant.io/docs/en/device_registry_index.html). Only works through [MQTT discovery](/docs/mqtt/discovery/) and when [`unique_id`](#unique_id) is set. At least one of identifiers or connections must be present to identify the device." + required: false + type: map + keys: + connections: + description: 'A list of connections of the device to the outside world as a list of tuples `[connection_type, connection_identifier]`. For example the MAC address of a network interface: `"connections": ["mac", "02:5b:26:a8:dc:12"]`.' + required: false + type: list + identifiers: + description: 'A list of IDs that uniquely identify the device. For example a serial number.' + required: false + type: [list, string] + manufacturer: + description: The manufacturer of the device. + required: false + type: string + model: + description: The model of the device. + required: false + type: string + name: + description: The name of the device. + required: false + type: string + sw_version: + description: The firmware version of the device. + required: false + type: string + via_device: + description: 'Identifier of a device that routes messages between this device and Home Assistant. Examples of such devices are hubs, or parent devices of a sub-device. This is used to show device topology in Home Assistant.' + required: false + type: string +enabled_by_default: + description: Flag which defines if the entity should be enabled when first added. + required: false + type: boolean + default: true +icon: + description: "[Icon](/docs/configuration/customizing-devices/#icon) for the entity." + required: false + type: icon +json_attributes_template: + description: "Defines a [template](/docs/configuration/templating/#processing-incoming-data) to extract the JSON dictionary from messages received on the `json_attributes_topic`." + required: false + type: template +json_attributes_topic: + description: The MQTT topic subscribed to receive a JSON dictionary payload and then set as entity attributes. Implies `force_update` of the current select state when a message is received on this topic. + required: false + type: string +name: + description: The name of the Select. + required: false + type: string +optimistic: + description: Flag that defines if the select works in optimistic mode. + required: false + type: boolean + default: "`true` if no `state_topic` defined, else `false`." +options: + description: List of options that can be selected. + required: true + type: list +qos: + description: The maximum QoS level of the state topic. Default is 0 and will also be used to publishing messages. + required: false + type: integer + default: 0 +retain: + description: If the published message should have the retain flag on or not. + required: false + type: boolean + default: false +state_topic: + description: The MQTT topic subscribed to receive update of the selected option. + required: false + type: string +unique_id: + description: An ID that uniquely identifies this Select. If two Selects have the same unique ID Home Assistant will raise an exception. + required: false + type: string +{% endconfiguration %} + +