diff --git a/source/_integrations/dsmr.markdown b/source/_integrations/dsmr.markdown
index a32c90faf68..5d75ed56c6d 100644
--- a/source/_integrations/dsmr.markdown
+++ b/source/_integrations/dsmr.markdown
@@ -10,7 +10,7 @@ ha_iot_class: Local Push
 
 A sensor platform for Dutch Smart Meters which comply to DSMR (Dutch Smart Meter Requirements), also known as 'Slimme meter' or 'P1 poort'.
 
-- Currently support DSMR V2.2, V3, V4 and V5 through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
+- Currently support DSMR V2.2, V3, V4, V5 and V5 Belgian through the [dsmr_parser](https://github.com/ndokter/dsmr_parser) module by Nigel Dokter.
 - For official information about DSMR refer to: [DSMR Document](https://www.netbeheernederland.nl/dossiers/slimme-meter-15)
 - For official information about the P1 port refer to: <https://www.netbeheernederland.nl/_upload/Files/Slimme_meter_15_a727fce1f1.pdf>
 - For unofficial hardware connection examples refer to: [Domoticx](http://domoticx.com/p1-poort-slimme-meter-hardware/)
@@ -35,6 +35,7 @@ USB serial converters:
 - <https://sites.google.com/site/nta8130p1smartmeter/webshop>
 - <https://www.sossolutions.nl/slimme-meter-kabel>
 - <https://tweakers.net/gallery/269738/aanbod/>
+- <https://nl.aliexpress.com/item/32945187155.html>
 
 Serial to network proxies:
 
@@ -60,7 +61,7 @@ sensor:
     required: false
     type: string
   dsmr_version:
-    description: "Version of DSMR used by meter. Choices: 2.2, 4, 5. Defaults to 2.2."
+    description: "Version of DSMR used by meter. Choices: 2.2, 4, 5, 5B (For Belgian Meter). Defaults to 2.2."
     required: false
     type: string
   precision:
@@ -83,10 +84,10 @@ group:
   meter_readings:
     name: Meter readings
     entities:
-      - sensor.power_consumption_low
-      - sensor.power_consumption_normal
-      - sensor.power_production_low
-      - sensor.power_production_normal
+      - sensor.energy_consumption_tarif_1
+      - sensor.energy_consumption_tarif_2
+      - sensor.energy_production_tarif_1
+      - sensor.energy_production_tarif_2
       - sensor.gas_consumption
 ```
 
@@ -102,10 +103,10 @@ group:
   meter_readings:
     name: Meter readings
     entities:
-      - sensor.power_consumption_low
-      - sensor.power_consumption_normal
-      - sensor.power_production_low
-      - sensor.power_production_normal
+      - sensor.energy_consumption_tarif_1
+      - sensor.energy_consumption_tarif_2
+      - sensor.energy_production_tarif_1
+      - sensor.energy_production_tarif_2
       - sensor.gas_consumption
 ```
 
diff --git a/source/_integrations/utility_meter.markdown b/source/_integrations/utility_meter.markdown
index ad3f92b5b92..c8a4b0cf95e 100644
--- a/source/_integrations/utility_meter.markdown
+++ b/source/_integrations/utility_meter.markdown
@@ -46,7 +46,7 @@ offset:
   description: "Cycle reset occur at the beginning of the period (0 minutes, 0h00 hours, Monday, day 1, January). This option enables the offsetting of these beginnings. Supported formats: `offset: 'HH:MM:SS'`, `offset: 'HH:MM'` and Time period dictionary (see example below)."
   required: false
   default: 0
-  type: time 
+  type: time
   type: integer
 net_consumption:
   description: Set this to True if you would like to treat the source as a net meter. This will allow your counter to go both positive and negative.
@@ -67,7 +67,7 @@ offset:
   # At least one of these must be specified:
   days: 1
   hours: 0
-  minutes: 0 
+  minutes: 0
 ```
 
 ## Services
@@ -153,8 +153,8 @@ When using the [DSMR component](/integrations/dsmr) to get data from the utility
 
 If you want to create a daily and monthly sensor for each tariff, you have to track separate sensors:
 
-- `sensor.power_consumption_low` for off-peak power
-- `sensor.power_consumption_normal` for peak power
+- `sensor.energy_consumption_tarif_1` for tarif 1 power (for example off-peak)
+- `sensor.energy_consumption_tarif_2` for 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.
@@ -162,26 +162,26 @@ So, tracking daily and monthly consumption for each sensor, will require setting
 ```yaml
 utility_meter:
   daily_power_offpeak:
-    source: sensor.power_consumption_low
+    source: sensor.energy_consumption_tarif_1
     cycle: daily
   daily_power_peak:
-    source: sensor.power_consumption_normal
+    source: sensor.energy_consumption_tarif_2
     cycle: daily
   daily_gas:
     source: sensor.gas_consumption
     cycle: daily
   monthly_power_offpeak:
-    source: sensor.power_consumption_low
+    source: sensor.energy_consumption_tarif_1
     cycle: monthly
   monthly_power_peak:
-    source: sensor.power_consumption_normal
+    source: sensor.energy_consumption_tarif_2
     cycle: monthly
   monthly_gas:
     source: sensor.gas_consumption
     cycle: monthly
 ```
 
-Additionally, you can add template sensors to compute daily and monthly total usage. 
+Additionally, you can add template sensors to compute daily and monthly total usage.
 
 {% raw %}
 ```yaml