dlms smartmeter support thread #1
Comments
|
will try your impl in the next days/weeks. I have a |
no hurry, thanks
yeah naming things is hard ... 🤣. But let's start with checking if it works. I think a working implementation is more important than some naming detail :). |
|
yes not the most important thing. i would call it |
|
maybe this overview helps: https://cms.shrdzm.com/wp-content/uploads/Smartmeter-scaled.jpg |
I already know this chart, but how should this help? This implementation is only intended for the ones providing an m-bus interface (or identical data format / structure provided with other converters to the the esp uart). If you mean grid operator vs energy provider, yes I know the difference. (I don't actually have EVN as energy provider here, but netz nö as grid operator). |
|
I only added as an overview for all the possible providers/devices that are there in austria |
This comment was marked as resolved.
This comment was marked as resolved.
|
@jenskn83 seems like it complains something about mqtt. Neither the component itself nor your attached yaml contains anything mqtt related. Did you try / use the DomiStyle/esphome-dlms-meter implementation before? - seems to cause conflicts here. Furthermore: because you have vkw you probably have to comment out (put # at beginning) |
|
@SimonFischer04 i got it some minutes before to work. i needed some time to figure out i flipped TX and RX on the ESP32. the only thing is that my smart meter doesn't support "Reactive energy" |
|
@ximex means you got it working? And about the "Reactive Energy": the provided yaml above is just a "maximum configuration" you can just remove the sensor and everything should still just work. |
|
yes works now. but i have some strange spikes (ignore that the sensor is name BME280 - reused it for this test) |
|
@ximex great to here that you got it working. I find it hard to believe that my impl could somehow create these spikes. Did you use some other impl before to read data from your smartmeter before and did not experience this issue? |
|
I tested the last days with https://cms.shrdzm.com/produkt/smartmeter-modul/ i got now another spike but i have now the logs open. See "Active power taken from grid": masked the meter number Are this warnings expected? Edit: also got now one with 0V after removing the debug logs and the reactive energy i'm now down to ~130ms: Edit2: |
Do you by chance remember how often this sends data? If there is a greater than 5sec delay its very possible they also do some filtering
Kind of. Unfortunately I don't see much i can do here as reading the data and decrying takes time and I also dont want to miss a byte while reading. Also sending that much logs takes time for the esp - but verbose logging should be enabled only for debugging anyways. But should not be a problem, a lot of other components also create such warnings. Just mean other components are blocked while this one is working. (Do webserver f.e. does sometakes take some time to render,...)
I will (hopefully) look through the decrypted packet you provided a bit more tomorrow to see if this gives some more insight.
Do you by chance have the full decrypted packet for this one also? |
Thanks for your answer. i tried with a new setup. now i receive a different error message: [09:40:43][E][dlms_meter:072]: MBUS: Frame too big for received data i attached the Log file. (logs_test2_logs.txt) when i switch to logging level "Very_Verbose" the built failed with several error messages (logs_test2_VERY_VERBOSE.txt) here the yaml (meter.yaml) can you help me with these issues please? |
according to this data it seems unfortunately that the smartmeter is in fact sending wrong data.
Reading this seems like they got partly just junk data. Don't think how it could result in (single) packets with such peeks. i guess adding a filter as workaround is the best option we have so far. see here f.e. (also others discussing / seeing weird values): DomiStyle/esphome-dlms-meter#16 (comment) |
I assume: you set "baud_rate: 0" in the logger section of your yaml because you use an 8266 which has only 1 uart (therefore you get the logs from the webserver). right?
this alone does not give much insight unfortunately
very weird that it can't compile basic esphome logging functionality. can you please try with loglevel VERBOSE. Furthermore: are you able to temporarily test with an esp32? So we better pinpoint the root issue. 8266 should theoretically work, but I'm using an esp32 here and did not hook up the smartmeter and fully test the 8266 version. |
|
@SimonFischer04 thanks a lot. with an esp32 your implementation runs out of the box! Jens |
Thanks for reporting back and great that it works for you. I guess I will test the 8266 implementation again myself and see if I can get it working. |
|
just updated the initial comment to clarify / provide examples for the generic and netznoe grid operator settings. |
|
Running a ESP8266 d1_mini EVN KaifaMA309M without any issue 👍 |
|
Hello Simon, FYI: I' ve used following adapter: mind: use 3.3 V NOT 5 V (Vin) when wireing to ESP32 |
|
Hey Simon, My setup is: ESP32, Kaifa MA309M and my engery provider is TINETZ! |
|
@ximex hast du mittlerweile eine Lösung für die Spikes in den Rohdaten gefunden? Viele Grüße |
|
sorry hab es noch nicht weiter untersucht |
|
Hi all, and i'm working on getting it upstreamed: esphome#8009 |
|
Wtf, stupid actions-bot. This is a fork, not esphome main repo ... |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Hi,
I recently started creating an esphome component for reading data from dlms encryped smartmeters. (used a lot in Austria)
Great thanks to DomiStyle(https://github.com/DomiStyle/esphome-dlms-meter) and firegore for the basic implementation.
But - as custom-components are deprecated now - I implemented it in a proper esphome-component, added support for evn smartmeters and did some more smaller fixes / changes.
Requirements esp(32 or 8266) and some mbus to uart converter. More details see for example: https://github.com/DomiStyle/esphome-dlms-meter?tab=readme-ov-file#requirements
Here is a basic yaml config you can try out for now:
If you have Netz NÖ / EVN:
any other grid operator:
Would love to get some feedback if it works for you also / you encounter some problems.
If you test please report back your findings here:
At least for now, this issue should be seen also as a (general) discussion thread around esp(home) / reading dlms encrypted data from smartmeters. So any input / feedback is welcome!
To help with debugging, please provide logs after enabling logger: level: VERBOSE (and tx_buffer_size: 1024 - required to log full packets)
PS: be careful with VERY_VERBOSE, as this also logs the decryption key (like the logs also warn at the very beginning)!
PS: my plan is to ultimately get this upstreamed into main esphome repo itself, but want to get some feedback / testing first.
Links to other issues I found around this topic:
The text was updated successfully, but these errors were encountered: