From 0410dd45606ddd357aefab548845a2fdc186e324 Mon Sep 17 00:00:00 2001 From: Sven Serlier <85389871+wrt54g@users.noreply.github.com> Date: Mon, 1 May 2023 23:34:12 +0200 Subject: [PATCH] Component to integration (#27228) --- source/_integrations/utility_meter.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown index 8588ae9d39d..0853b40ffae 100644 --- a/source/_integrations/utility_meter.markdown +++ b/source/_integrations/utility_meter.markdown @@ -243,7 +243,7 @@ utility_meter: ## Advanced Configuration for DSMR users -When using the [DSMR component](/integrations/dsmr) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` component. +When using the [DSMR integration](/integrations/dsmr) to get data from the utility meter, each tariff (peak and off-peak) has a separate sensor. Additionally, there is a separate sensor for gas consumption. The meter switches automatically between tariffs, so an automation is not necessary in this case. But, you do have to setup a few more instances of the `utility_meter` integration. If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors: @@ -251,7 +251,7 @@ If you want to create a daily and monthly sensor for each tariff, you have to tr - `sensor.energy_consumption_tarif_2` for tarif 2 power (for example peak) - `sensor.gas_consumption` for gas consumption -So, tracking daily and monthly consumption for each sensor, will require setting up 6 entries under the `utility_meter` component. +So, tracking daily and monthly consumption for each sensor, will require setting up 6 entries under the `utility_meter` integration. ```yaml utility_meter: