mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-15 21:36:52 +00:00
Merge branch 'next' into rc
This commit is contained in:
Franck Nijhof
commit
e0e7c2904d
@ -905,6 +905,8 @@ The numeric functions and filters raise an error if the input is not a valid num
|
||||
- `max([x, y, ...])` will obtain the largest item in a sequence. Uses the same parameters as the built-in [max](https://jinja.palletsprojects.com/en/latest/templates/#jinja-filters.max) filter.
|
||||
- `min([x, y, ...])` will obtain the smallest item in a sequence. Uses the same parameters as the built-in [min](https://jinja.palletsprojects.com/en/latest/templates/#jinja-filters.min) filter.
|
||||
- `average([x, y, ...], default)` will return the average value of the sequence. If list is empty or contains non-numeric value, returns the `default` value, or if omitted raises an error. Can be used as a filter.
|
||||
- `median([x, y, ...], default)` will return the median value of the sequence. If list is empty or contains non-numeric value, returns the `default` value, or if omitted raises an error. Can be used as a filter.
|
||||
- `statistical_mode([x, y, ...], default)` will return the statistical mode value (most frequent occurrence) of the sequence. If the list is empty, it returns the `default` value, or if omitted raises an error. It can be used as a filter.
|
||||
- `e` mathematical constant, approximately 2.71828.
|
||||
- `pi` mathematical constant, approximately 3.14159.
|
||||
- `tau` mathematical constant, approximately 6.28318.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Midea CCM15 Data Converter
|
||||
title: Midea CCM15 AC Controller
|
||||
description: Instructions on how to integrate a Midea CCM15 module into Home Assistant.
|
||||
ha_category:
|
||||
- Climate
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 2023.07.0
|
||||
ha_release: 2024.1
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@ocalvo'
|
||||
@ -23,20 +23,7 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [Configuration](#configuration)
|
||||
- [Climate](#climate)
|
||||
|
||||
## Configuration
|
||||
|
||||
Adding a CCM15 data converter to your Home Assistant instance can be done via the user interface, by using this My Button:
|
||||
{% my config_flow_start badge domain=page.ha_domain %}
|
||||
|
||||
{% details "Manual configuration steps" %}
|
||||
|
||||
1. Browse to your Home Assistant instance.
|
||||
2. Go to **{% my integrations title="Settings > Devices & Services" %}**.
|
||||
3. In the bottom right corner, select the
|
||||
**{% my config_flow_start icon domain=page.ha_domain %}** button.
|
||||
4. From the list, select **CCM15** and follow the instructions on screen.
|
||||
|
||||
{% enddetails %}
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Climate
|
||||
|
||||
|
||||
@ -46,75 +46,16 @@ It currently supports presenting the current temperature, the setting temperatur
|
||||
|
||||
## Presence detection
|
||||
|
||||
The `tado` device tracker is using the [Tado Smart Thermostat](https://www.tado.com/) and its support for person presence detection based on smartphone location by geofencing.
|
||||
The Tado device tracker is using the [Tado Smart Thermostat](https://www.tado.com/) and its support for person presence detection based on smartphone location by geofencing.
|
||||
|
||||
This tracker uses the Tado API to determine if a mobile device is at home. It tracks all devices in your home that Tado knows about.
|
||||
This tracker uses the Tado API to determine if a mobile device is at home.
|
||||
|
||||
To use the Tado platform in your installation, add the following to your `configuration.yaml` file:
|
||||
By default the Tado device tracker will track all devices known to Tado associated with your home. The Tado app needs to have the `Geolocation` permission enabled for the device to be tracked.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for Tado
|
||||
device_tracker:
|
||||
- platform: tado
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
home_id: YOUR_HOME_ID
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
username:
|
||||
description: The username for your Tado account.
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password for your Tado account.
|
||||
required: true
|
||||
type: string
|
||||
home_id:
|
||||
description: The id of your home of which you want to track devices. If provided, the Tado device tracker will track *all* devices known to Tado associated with this home. See below how to find it.
|
||||
required: false
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
After configuration, your device has to be at home at least once before showing up as *home* or *away*.
|
||||
Your device has to be at home at least once before showing up as *home* or *away*.
|
||||
Polling Tado API for presence information will happen at most once every 30 seconds.
|
||||
|
||||
See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked. Beware that the Tado (v2) API does not provide GPS location of devices, only a bearing, therefore Home Assistant only uses `home`/`not-home` status.
|
||||
|
||||
### Finding your `home_id`
|
||||
|
||||
Find your `home_id` by browsing to `https://my.tado.com/api/v2/me?username=YOUR_USERNAME&password=YOUR_PASSWORD`. There you'll see something like the following:
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "Mark",
|
||||
"email": "your@email.tld",
|
||||
"username": "your@email.tld",
|
||||
"homes": [
|
||||
{
|
||||
"id": 12345,
|
||||
"name": "Home Sweet Home"
|
||||
}
|
||||
],
|
||||
"locale": "en_US",
|
||||
"mobileDevices": []
|
||||
}
|
||||
```
|
||||
|
||||
In this example `12345` is the `home_id` you'll need to configure.
|
||||
|
||||
### Finding your `home_id` alternative
|
||||
|
||||
If the above method returns an unauthorized error. The `home_id` can also be found using Chrome developer tools. Whilst logged into https://my.tado.com/webapp, take the following steps:
|
||||
|
||||
- Select the "Network"' tab
|
||||
- Filter for "home"
|
||||
- Under "Name", select "users"
|
||||
- Click on the "Response" tab
|
||||
|
||||
The `home_id` appears in the response for users as `"id":12345`
|
||||
|
||||
In this example `12345` is the `home_id` you'll need to configure.
|
||||
Beware that the Tado (v2) API does not provide GPS location of devices, only a bearing, therefore Home Assistant only uses `home`/`not-home` status.
|
||||
|
||||
## Services
|
||||
|
||||
|
||||
@ -4,13 +4,15 @@ description: Instructions on how to integrate Trend binary sensors into Home Ass
|
||||
ha_category:
|
||||
- Binary sensor
|
||||
- Utility
|
||||
- Helper
|
||||
ha_release: 0.28
|
||||
ha_iot_class: Calculated
|
||||
ha_quality_scale: internal
|
||||
ha_domain: trend
|
||||
ha_platforms:
|
||||
- binary_sensor
|
||||
ha_integration_type: integration
|
||||
ha_config_flow: true
|
||||
ha_integration_type: helper
|
||||
ha_codeowners:
|
||||
- '@jpbede'
|
||||
---
|
||||
@ -21,7 +23,19 @@ at least two updates of the underlying sensor to establish a trend.
|
||||
Thus it can take some time to show an accurate state. It can be useful
|
||||
as part of automations, where you want to base an action on a trend.
|
||||
|
||||
## Configuration
|
||||
{% include integrations/config_flow.md %}
|
||||
{% configuration_basic %}
|
||||
Name:
|
||||
description: The name the sensor should have. You can change it again later.
|
||||
Entity that the sensor tracks:
|
||||
description: The sensor entity that is to be tracked and whose trend is to be detected.
|
||||
Attribute of the entity that the sensor tracks:
|
||||
description: The attribute of the previous selected sensor entity that this sensor tracks. If no attribute is specified then the sensor will track the state.
|
||||
Invert the result:
|
||||
description: Invert the result. A `true` value would mean descending rather than ascending.
|
||||
{% endconfiguration_basic %}
|
||||
|
||||
### YAML Configuration
|
||||
|
||||
To enable Trend binary sensors in your installation,
|
||||
add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -6,7 +6,7 @@ date: 2023-12-27 00:00:02
|
||||
date_formatted: "December 27, 2023"
|
||||
author: Bruno Pantaleão
|
||||
comments: true
|
||||
categories: iOS, Release-Notes
|
||||
categories: iOS Release-Notes
|
||||
og_image: /images/blog/2023-12-ios-lets-go/ios-og.png
|
||||
---
|
||||
|
||||
@ -50,6 +50,4 @@ This does not mean your iOS 12, 13, or 14 devices have become unusable. You can
|
||||
|
||||
## On the roadmap
|
||||
|
||||
Wondering what we have on the roadmap for our Apple apps? We’re still working on it, but you can expect further developments to make Home Assistant on the Apple ecosystem more integrated, bringing shared features between iPhone, Apple Watch, iPad, and Mac - and I’m looking forward to getting my hands on Apple Vision Pro and seeing the possibilities it brings to the Open Home. We’re also planning on improvements to Siri shortcuts widgets and as many new sensors as possible. Another feature that is on our radar is Assist; in 2023, we completed the Year of the Voice. Android users benefitted from some extra functions compared to iOS users, and we want to make sure we catch up and bring these features to iPhones as well!
|
||||
|
||||
If you’re an Android user, good news is also coming to your beloved Companion App! We are looking for an Android engineer to join Nabu Casa to bring the Android Companion App to the next level. We have yet to officially open up a job, but if you know someone or would already like to apply yourself, feel free to send us a message at apply@nabucasa.com.
|
||||
Wondering what we have on the roadmap for our Apple apps? We’re still working on it, but you can expect further developments to make Home Assistant on the Apple ecosystem more integrated, bringing shared features between iPhone, Apple Watch, iPad, and Mac - and I’m looking forward to getting my hands on Apple Vision Pro and seeing the possibilities it brings to the Open Home. We’re also planning on improvements to Siri shortcuts widgets and as many new sensors as possible. Another feature that is on our radar is Assist; in 2023, we completed the Year of the Voice. Android users benefitted from some extra functions compared to iOS users, and we want to make sure we catch up and bring these features to iPhones as well!
|
||||
Loading…
x
Reference in New Issue
Block a user