-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISSUE: abnormal data in home assistant #16
Comments
Info: Found a similar problem here: |
I had this happen once last year, unfortunately I didn't log the values sent by the smart meter at the time it happened so I'm not sure if it's the smart meter that sent invalid data or if the value of the smart meter rolled over somehow. If it happens again I will add a limiter to the values the smart meter can send and ignore unrealistic values. Unfortunately deleting values from the Home Assistant energy database is also a pain. |
Thanks to home assistant 2022.4 you can now easily edit the malformed value directly from dev tools. |
So... i have now gathered more logs, seeing that the smartmeter is pushing wrong values from time to time.
Normal value at 20:10:30: Malformed value at 20:10:45: Back to normal at 20:11:00: My ESPHOME config is as follows: api: ota: wifi: logger: uart: mqtt: sensor:
text_sensor:
custom_component:
Maybe someone can see the problem. |
In what intervals does this usually happen? |
unregularly - there is no specific time when that happens. i had it once at the 12th of April at 6pm, the once at 11:20pm and again yesterday at 08:10pm. i cannot find any issue with esphome itself or with the lambda calculations. your code must be correct as it gets values from the smartmeter, so i assume there is a problem with either the smartmeter or the MBUS Slave Click. The system is wired as you suggested. +3v3 is coming from the esp32 chip. the rj11 cable is shielded. |
one more info: my smartmeter is connected via lte insteaf of powerline to vkw and i have enabled the 1/4 hour transmission in vorarlbergnetz portal. |
I also had these issues, but i can´t code and so i added some filters to remove the bad values.
Works good enough for me, but just a workaround. Tinetz smartmeter, so prob not an issue with the vorarlberg one |
Thank you Exolor, will try that. |
This would be what my sensors look like, i still get a wrong value with the power sensors sometimes, or i forgot i used the oven at 4 in the morning. If you still get incorrect data with the energy sensors, you can increase the window_size. As they dont change a lot, it doesnt really matter anyways. |
Thank you @Exolor - it works perfectly fine now. I can live with that workaround. |
One wrong bit in the payload can mess up all values. I would suggest to check the encrypted APDU. We could verify the APDU by checking a Datatype. At least that should work for EVN. I gues it is the same for other providers. |
Since actual spec sheets for the protocol(s) are available now and there is much less guessing going on I rewrote the entire parsing logic so these kind of errors should hopefully be detected by the M-Bus checksum and the length fields. The changes are in the master branch if anybody wants to give it a try. |
Nope - exchanged all the files, recreated the image and uploaded to the esp. same problem as before. |
@cococheaf The smart meter is probably really providing invalid data then. It's unlikely that errors are not detected by the checksum multiple times. |
No problem.
I keep the meridian function running, that works very well.
Thank you - Rgds - Andre
Am 07.10.2022 20:07, schrieb Dominik:
@cococheaf [1] The smart meter is probably really providing invalid
data then. It's unlikely that errors are not detected by the checksum
multiple times.
--
Reply to this email directly, view it on GitHub [2], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Same for me, didnt seem to change anything, so as Domi said, prob a problem with the smart meter. |
No it is not. We change hardware to a different esp and problems are gone. |
Could very well be, i dont use one from AZ but another chinese board. |
I can confirm running on ESP32-CAM and ESP32 D1 Mini (random manufacturer from amazon). The ESP32 node mcu from AZ was only able to receive data when 3.3v was not connected but still unstable. I don't realy understand how this can happen as the code should log an error and drop the invalid payload. |
I think i have found the problem regarding the abnormal data. Maybe someone else with an esp32-dev module can verify that?
|
Also located in Höchst. |
@zibous I'm located in Luschnou ;) .. Have a m-bus slave click from mikroe left over, if you need one :) |
Hi
Super, würde den nehmen - wie kann ich den bekommen ? |
u got mail ... ruf einfach kurz an ✌🏽 |
Sorry - hab erst vorher die Mails durchgeschaut - hat sich aber in dem Fall schon erledigt :) LG |
Hi,
i have found another issue, not sure if its the code, but I have the following problem:
I have now implemented the meter in home assistant and added it to the energy dashboard.
The problem now is that the meter is reporting data correctly, until once a completely malformed data is being sent from the meter.
See pictures attached:
How does it behave at yours?
I have activated the quarter-hour setting at Vorarlbergnetz. Just to be precise.
PS: Sorry, wenn ich auf deutsch schreiben soll einfach sagen :9
Und sorry wenn ich dich damit nerve, ich bin nur sehr interessiert an dem Ding.
Würde mich interessieren ob der Fehler bei dir auch auftritt.
Thank you for your support.
Andre
The text was updated successfully, but these errors were encountered: