Skip to content

Add set_program service action to miele #38670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: next
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 27 additions & 5 deletions source/_integrations/miele.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Miele
description: Instructions on how to set up the Miele integration within Home Assistant.
ha_category:
- Climate
- Hub
- Light
- Sensor
Expand All @@ -12,6 +13,7 @@ ha_codeowners:
- '@astrandb'
ha_config_flow: true
ha_platforms:
- climate
- diagnostics
- light
- sensor
Expand Down Expand Up @@ -81,13 +83,11 @@ The integration configuration may ask for the *Client ID* and *Client Secret* cr
- Some appliances don't report data while they are turned off, so corresponding entities will not appear in the Miele integration after loading until the appliances are turned on.
{% endnote %}

### Sensor
### Climate

{% details "List of sensors" %}
{% details "List of climate entities" %}

- **Operation state**:
- **Status**: Represents the current operation state of the device. The default entity name is just the appliance type. For example, "Dishwasher".
- **Temperature**: Represents the current temperature in refrigerators, freezers, and ovens. Entities are created for up to 3 zones depending on the device capabilities.
Climate entities are used to control target temperatures in refrigerators, freezers, and wine cabinets. One, two, or three zones can be controlled depending on the capabilities of the appliance.
{% enddetails %}

### Light
Expand All @@ -98,6 +98,28 @@ The integration configuration may ask for the *Client ID* and *Client Secret* cr
- **Ambient light**: Some models of cooker hoods have ambient light that can be turned on and off.
{% enddetails %}

### Sensor

{% details "List of sensors" %}

- **Operation state**:
- **Status**: Represents the current operation state of the device. The default entity name is just the appliance type. For example, "Dishwasher".
- **Temperature**: Represents the current temperature in refrigerators, freezers, and ovens. Entities are created for up to 3 zones depending on the device capabilities.
{% enddetails %}

## Actions

### Action `miele.set_program`

Set and start a program for applicable appliances. Note that the device must be in a state where it will accept a new program, for example, most washing machines must be in state `On`. An error message is displayed if the device did not accept the action command.
The service action can be set up by UI in Automations editor or Developer tools.

| Data attribute | Optional | Description |
| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------- |
| `device_id` | no | Select device in GUI mode, then switch to YAML mode to see the device_id. |
| `program_id` | no | Enter the program_id number. The easiest way to find the number is to fetch a diagnostic download while running the actual program. Use the value from the key `state::programId::value_raw`.|
| `duration` | yes | Set desired program duration in minutes for ovens. |
| `temperature` | yes | Set desired target temperature for oven program. |
## Automation examples

Get started with these automation examples
Expand Down