Hi All,
Has someone a good working yaml file for the iskar MT382 dsmr 2.2?
I can’t get it to work 
on my own
Hi Pele, I’m not so familiar with smart meters, but have you tried the firmware specific for DSMR2.2/3.0? There’s something mentioned about it here on Marcel’s website under “Firmware for older meters (DSMR2.x)”: https://www.zuidwijk.com/product/slimmelezer/
That directed me to a fork of the code which might shed some insight. https://github.com/michielappelman/dsmr
thx i wil try that
installed the firmware specific for DSMR2.2.
However waited for hours but no data is coming in 
Anyone has a clue how to handle,solve it or what to check?
Hey Pele,
Maybe there is something in here that can help: https://github.com/esphome/esphome/pull/2157#issue-712837636
It looks like Michiel Appelman probably knows what to do, perhaps you can get in touch with him on GitHub.
After running fine over 2 months, I looked into the ESPhome dashboard, where I hadn’t been for a while and noticed an update notice for the ‘slimmelezer’. After running this right from there, everything went black. Tried to reflash with the latest and older firmware files OTA, but it stopped everytime after it’s done a few %.
Here’s what happened when updating over the air…
Uploading: [========== ] 17%
ERROR Error sending data: [Errno 104] Connection reset by peer
Removed the slimmemeter from the integrations and ESPhome dashboard and worked my way back to the point where ‘slimmemeter’ reports as accesspoint and connected. That worked as the integration was found again. But: no entry in the ESPhome dashboard so no way to reconfigure anything. And my data from the past 2 months was lost.
I cannot seem to restore it. It has an IP, I can reach its own local page directly, but all values except network related values (it has an IP) are empty.
Updating this is not for the faint of heart 
Got it back on track. Deleted everything, both from the Integrations section as well as from the ESPHome web dashboard. Uploaded latest firmware via USB. Added it to HA via the ‘slimmelezer’ AP.
Went to manually add a new ESPHome entry in the ESPHome web dashboard. Downloaded binary, uploaded that back via USB. Restored my old stats by adding the old sensors to the Energy configuration.
Not touching it anymore for now 
After yesterdays re-install, I have a fluke in my readings. It has a major negative reading (I have no solar panels nor delivering anything back in any way). I guess it’s not doable, but is there a way to get that reading out of the stats?
HI,
has installed Slimmelezer + on HA and works, in addition to Energy Consumed tariff 1, 2, 3, nan kWh Produced tariff 1,2,3. nan kWh.
How do you update the slimmelezer when its installed in HA with ESPHome?
What is the best way?
My config is as it was after originally installing it:
I have been updating my slimmelezer.yaml based on the yaml in the Github repo and look at the latest slimmerlezer.yaml and then manually look at the differences. I did not find another source for the yaml. However on multiple occasions the slimmelezer.yaml in the repo was not working, so can not recommend it.
Personally I kind of abandoned the idea of updating the slimmelezer.yaml and ESPHome myself for slimmelezer and will just flash new firmwares when provided from the slimmelezer website which occasionally get updated.
I wish the slimmelezer could check for updates itself and then I just press a button to install it instead instead of doing the manual check, download, update steps. Maybe it is something that is possible now with the new Update entities in HA.
There is a way to update directly via the ESPHome add-on web interface in Home Assistant, no? I’m not entirely sure what is updated actually, since when I did this just now the YAML version did not change in the configuration…
After selecting to update as shown, you need to choose a connection method (if you have set up slimmelezer normally, “wirelessly” should work). You can see the update progress in the logs. Unfortunately, at least in the HA mobile interface, you need to wait for the update to finish and then click “stop” to dismiss the UI. There is some purple and green text when the update is complete, followed by logging of the incoming P1 telegrams from your smart meter (shown here).
Updating though the ESPHome dashboard updates the ESPHome version/code (if you hover over the Update button it will tell to what ESPHome version it will update). The yaml will not change automatically as that is something you have to provide. The yaml is basically a configuration for ESPHome on how to work with the hardware board connected to the ESP and expose the data to HA.
Most of the time no changes are needed to the yaml, but there have been some changes with the buffer lengths at some point, which I thought were needed for (more?) reliable operation if I recall correctly.
Works perfectly in Luxembourg! Great thanks for the description 
1 Like
hi,
I just got the device. seems to be update to the latest version. It was detected by HA and seems to get all data from the Meter.
the problem I have is that the Energy dashboard is not populated at all. I set a fix price for the daily consumption, but nothing happens.
my original post is here: ESPhome slimmelezer energy config
Hope you can advice.
thank you
I have recently moved to an other house and plugged in the slimme lezer into the new meter. I get nan state output so i guess i have to reset the id or something. How do i do that?
Any one else having problems after updating to 2024.2.1?
I get NA on everything now 
I tried downgrading, even restored my whole home assistant, but could not get it to work.
Hi! I got the Slimme Lezer delivered with ESP-link. It has been working for the past year with no issues but it is the only ESP-link based device I have. I would be happy to migrate to ESPHome. Does anyone know if I can do that, rename the entities to what they are called now and in this way keep the history of energy use etc?
Hi, i hv a problem with the connection to a KAIFA Smartmeter in Austria. Here are the log entry which i cant solve:
[09:31:27][W][component:237]: Component took a long time for an operation (1855 ms).
[09:31:27][W][component:238]: Components should block for at most 30 ms.
[09:31:27][E][espdm:053]: MBUS: Start bytes do not match
[…]
My UART config:
uart:
tx_pin: GPIO1
rx_pin: D7
baud_rate: 2400
rx_buffer_size: 1700
id: mbus
Thanks a lot for your help !!!
Erich
This is my yaml:
substitutions:
device_name: slimmelezer
device_description: "DIY P1 module to read your smart meter"
esphome:
name: ${device_name}
comment: "${device_description}"
platform: ESP8266
board: d1_mini
includes:
- /config/esphome/esphome-dlms-meter
# Enable logging
logger:
level: DEBUG # (VERBOSE funktioniert nicht)
baud_rate: 0
# Enable Home Assistant API
api:
encryption:
key: !secret api_encryption_key
ota:
password: "af528ad48112c9d8a37b7e8d7901de61"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# fast_connect: true
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Smartmeter Fallback Hotspot"
password: !secret wifi_password
# captive_portal:
web_server:
port: 80
uart:
tx_pin: GPIO1
rx_pin: D7
baud_rate: 2400
rx_buffer_size: 1700
id: mbus
sensor:
- platform: template
id: meter01_voltage_l1
name: meter01_voltage_l1
unit_of_measurement: V
accuracy_decimals: 1
device_class: "voltage"
state_class: "measurement"
- platform: template
id: meter01_voltage_l2
name: meter01_voltage_l2
unit_of_measurement: V
accuracy_decimals: 1
device_class: "voltage"
state_class: "measurement"
- platform: template
id: meter01_voltage_l3
name: meter01_voltage_l3
unit_of_measurement: V
accuracy_decimals: 1
device_class: "voltage"
state_class: "measurement"
- platform: template
id: meter01_current_l1
name: meter01_current_l1
unit_of_measurement: A
accuracy_decimals: 2
device_class: "current"
state_class: "measurement"
- platform: template
id: meter01_current_l2
name: meter01_current_l2
unit_of_measurement: A
accuracy_decimals: 2
device_class: "current"
state_class: "measurement"
- platform: template
id: meter01_current_l3
name: meter01_current_l3
unit_of_measurement: A
accuracy_decimals: 2
device_class: "current"
state_class: "measurement"
- platform: template
id: meter01_active_power_plus
name: meter01_active_power_plus
unit_of_measurement: W
accuracy_decimals: 0
device_class: "power"
state_class: "measurement"
- platform: template
id: meter01_active_power_minus
name: meter01_active_power_minus
unit_of_measurement: W
accuracy_decimals: 0
device_class: "power"
state_class: "measurement"
- platform: template
id: meter01_active_energy_plus
name: meter01_active_energy_plus
unit_of_measurement: Wh
accuracy_decimals: 0
device_class: "energy"
state_class: "total_increasing"
- platform: template
id: meter01_active_energy_minus
name: meter01_active_energy_minus
unit_of_measurement: Wh
accuracy_decimals: 0
device_class: "energy"
state_class: "total_increasing"
- platform: template
id: meter01_reactive_energy_plus
name: meter01_reactive_energy_plus
unit_of_measurement: Wh
accuracy_decimals: 0
device_class: "energy"
state_class: "total_increasing"
- platform: template
id: meter01_reactive_energy_minus
name: meter01_reactive_energy_minus
unit_of_measurement: Wh
accuracy_decimals: 0
device_class: "energy"
state_class: "total_increasing"
text_sensor:
- platform: template
id: meter01_timestamp
name: meter01_timestamp
- platform: wifi_info
ip_address:
name: "IP Address"
ssid:
name: "Wi-Fi SSID"
bssid:
name: "Wi-Fi BSSID"
mqtt:
broker: "192.168.1.30"
port: "1883"
username: "AAA"
password: "bbb"
id: mqtt_broker
discovery: true
custom_component:
- lambda: |-
auto dlms_meter = new esphome::espdm::DlmsMeter(id(mbus));
uint8_t key[] = {0xXX, 0xD2, 0x40, 0x24, 0xXX, 0xB4, 0xD3, 0xB3, 0x2F, 0x8F, 0x80, 0x3A, 0x01, 0xE3, 0x1F, 0xDC};
dlms_meter->set_key(key, 16);
dlms_meter->set_voltage_sensors(id(meter01_voltage_l1), id(meter01_voltage_l2), id(meter01_voltage_l3));
dlms_meter->set_current_sensors(id(meter01_current_l1), id(meter01_current_l2), id(meter01_current_l3));
dlms_meter->set_active_power_sensors(id(meter01_active_power_plus), id(meter01_active_power_minus));
dlms_meter->set_active_energy_sensors(id(meter01_active_energy_plus), id(meter01_active_energy_minus));
dlms_meter->set_reactive_energy_sensors(id(meter01_reactive_energy_plus), id(meter01_reactive_energy_minus));
dlms_meter->set_timestamp_sensor(id(meter01_timestamp)); // Set sensor to use for timestamp (optional)
dlms_meter->enable_mqtt(id(mqtt_broker), "meter01/data");
return {dlms_meter};
Additional Info - i activated the uart debug - here my results:
[10:41:52][D][uart_debug:114]: <<< 6A:6B:5A:6B:52:6B:4B:6A:4A:4A:4A:6A:10:43:6B:6A:63:18:52:63:43:63:63:6B:52:10:4B:62:62:4A:6B:52:52:6A:42:52:42:52:4B:4B:62:4B:10:12:4A:6B:62:43:4B:43:42:63:6B:42:43:4B:43:62:63:4A:6B:58:5A:52:18:63:4B:6B:6B:63:1A:5A:52:4A:58:4A:52:6B:6A:43:12:50:12:6B:6A:4A:5A:4B:43:62:12:50:4B:6B:6B:58:63:1A:63:4B:42:62:6B:6A:63:6B:5A:6A:42:43:4B:43:1A:6B:6A:4A:6A:58:6A:5A:62:6B:58:63:1A:4B:18:43:42:42:62:4A:6A:1A:42:10:6B:43:4B:4B:4A:4B:6B:1A:52:62:63:6A:63:4A
[10:41:52][W][component:237]: Component <unknown> took a long time for an operation (1868 ms).
[10:41:52][W][component:238]: Components should block for at most 30 ms.
[10:42:12][E][espdm:053]: MBUS: Start bytes do not match
[10:42:12][D][uart_debug:114]: <<< 62:62:52:42:58:4B:62:6A:6A:CB
[10:42:17][D][uart_debug:114]: <<< 6A:6B:5A:6B:52:6B:4B:6A:4A:4A:4A:6A:10:63:6A:63:63:12:52:43:4A:4B:6B:6A:5A:42:4B:58:62:12:6B:6A:52:5A:43:6A:63:4A:4B:4B:10:18:43:6A:6B:43:6A:42:12:4A:50:43:43:62:63:62:4A:43:6B:63:12:42:58:10:18:6A:4A:6B:62:12:58:4B:5A:1A:43:6A:63:1A:43:4A:6B:63:42:4B:52:6A:62:10:4A:4B:6A:50:58:42:4B:5A:52:5A:6A:10:5A:18:43:6A:43:12:63:6A:12:6B:42:4A:63:6B:62:42:4A:1A:4B:58:62:1A:52:4B:4B:62:12:50:6B:5A:43:4B:5A:6B:5A:12:43:42:62:62:62:6B:4A:1A:4B:4A:42:5A:4A:52
[10:42:17][W][component:237]: Component <unknown> took a long time for an operation (1878 ms).
[10:42:17][W][component:238]: Components should block for at most 30 ms.
[10:42:17][E][espdm:053]: MBUS: Start bytes do not match
[10:42:17][D][uart_debug:114]: <<< 4B:18:4B:1A:4B:43:4B:6B:42:5A:4A:1A:63:62:42:FC
[10:42:22][D][uart_debug:114]: <<< 6A:6B:5A:6B:52:6B:4B:6A:4A:4A:4A:6A:10:43:6B:6B:62:43:6B:1A:6A:58:6B:6B:43:63:42:62:42:6B:6B:6A:63:52:4A:62:12:6B:63:6B:6B:5A:43:6B:42:50:4A:62:6B:6B:62:4A:52:43:6B:6B:4A:4B:43:43:62:50:4A:62:6A:63:6B:6B:63:5A:5A:6A:63:4B:43:4B:4B:12:6A:63:50:63:4A:10:52:63:6A:6B:58:50:63:6B:6B:50:63:6B:6B:1A:62:43:4B:6A:58:1A:43:50:6A:42:4B:62:10:62:6B:12:5A:43:42:43:4B:4B:18:42:6B:43:63:6B:63:62:52:58:6B:58:4B:6A:43:6B:4B:12:42:62:5A:4B:58:62:4A:42:6B:4A:63:63
[10:42:22][W][component:237]: Component <unknown> took a long time for an operation (1856 ms).
Erich