Skip to content
Open
Show file tree
Hide file tree
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
4 changes: 4 additions & 0 deletions src/content/docs/components/climate/mitsubishi_cn105.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,11 @@ sensor:
> This is an advanced feature; users are expected to understand the implications of overriding the internal sensor. Depending
> on the unit, it may be necessary to explicitly call `climate.mitsubishi_cn105.clear_remote_temperature` to restore normal
> operation. Improper use may lead to unexpected behavior.
>
> Check out the [remote temperature example in the Cookbook](/cookbook/mitsubishi_cn105_remote_temp/) to see a possible way to
> implement this functionality.

## See Also

- [Climate Component](/components/climate/)
- [Remote temperature example in the Cookbook](/cookbook/mitsubishi_cn105_remote_temp/)
84 changes: 84 additions & 0 deletions src/content/docs/cookbook/mitsubishi_cn105_remote_temp.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,84 @@
---
description: "Instructions for setting up remote temperature sensors with Mitsubishi CN105-compatible heatpumps."
title: "Remote sensor with Mitsubishi CN105 heatpump"
---

Mitsubishi heatpumps equipped with the `CN105` internal connector support reading temperature values from remote sensors.
The advantage of this feature is that a remote sensor can be placed more optimally in the room to get information about the
real temperature.

The [Mitsubishi CN105 Climate](/components/climate/mitsubishi_cn105/) component supports this feature by providing [actions and lambdas](/automations/) to update the hardware
with values from any temperature sensor available in ESPHome.

The following is a possible configuration to implement this. Some heatpumps require frequent temperature updates to prevent from
falling back to their internal sensor, `update_interval` and `force_update` take care of this. The filters are to guard from
failing sensors - that's when one would still want to continue operation, based on the internal sensor. The `select` offers the
possibility to choose at run time between which temperature source to use with the heatpump.

```yaml
climate:
- platform: mitsubishi_cn105
id: ac
...

sensor:
- platform: ...
id: my_temp
...
accuracy_decimals: 1
update_interval: 10s
force_update: true
filters:
- filter_out: nan # occasional NaNs are OK
- timeout: 1800s # sent value will be NaN after this amount of time to guard from sensor failures
on_value:
- if:
all:
- select.is:
id: sel_temp
options: "External"
- lambda: return (!isnan(x));
then:
- climate.mitsubishi_cn105.set_remote_temperature:
id: ac
temperature: !lambda 'return x;'
else:
- climate.mitsubishi_cn105.clear_remote_temperature:
id: ac

select:
- platform: template
id: sel_temp
name: "Temperature Source"
optimistic: true
restore_value: true
options:
- Internal
- External
initial_option: "Internal"
on_value:
- if:
condition:
select.is:
id: sel_temp
options: "Internal"
then:
- climate.mitsubishi_cn105.clear_remote_temperature:
id: ac
- if:
condition:
select.is:
id: sel_temp
options: "External"
then:
- climate.mitsubishi_cn105.set_remote_temperature:
id: ac
temperature: !lambda 'return id(my_temp).state;'
```

## See Also

- [Mitsubishi CN105 Climate](/components/climate/mitsubishi_cn105/)
- [Sensor](/components/sensor/)
- [Template Select](/components/select/template/)
- [Automation](/automations/)