UtilitechAS / amsreader-firmware

ESP8266 and ESP32 compatible firmware to read, interpret and publish data to MQTT from smart electrical meters, both DLMS and DSMR is supported
Other
382 stars 73 forks source link

Day and month plot numbers are gone. #792

Closed ycagwyn closed 5 months ago

ycagwyn commented 5 months ago

All of a sudden the day and month plot numbers were replaced by some very huge numbers. I have tried to patch the figures into the .cfg file and after some struggle managed to upload them to the device. Graphs looks OK until there is a change of hour when it gets back to show one very large number for previous hour. Downloaded the configuration after upload and noticed that the latter half (export) of day and month plot series were missing. Instant power readings are still transmitted OK to the MQTT-server every 10 second while energy measurements looks as bad as on the GUI.

image

ArnieO commented 5 months ago

Huh, interesting. Do you see any sign in your data that this could be a number format / rollover error? What order of magnitude are the "normal" numbers?

ycagwyn commented 5 months ago

Hi Arnie!

Thank you for the quick reaction. Since I’m not that closely familiar with the product I cannot tell whether it’s format /rollover problem or not but I would guess so. My normal daily import/export readings are 0-60 kWh and hourly 0-15 kWh. This is how it looks today: 

Daily figures seemed OK after my path yesterday and here is what the downloaded .cfg says now:

amsconfig version v2.3.5 boardType 5 meterBaud 2400 meterParity 8N1 meterInvert 0 meterDistributionSystem 2 meterMainFuse 25 meterProductionCapacity 10 dayplot 6 1715238018 320277.240 3 20000 18000 16000 15000 10000 12000 10000 0 0 0 1000 1000 1000 2000 1000 2000 1000 6000 6000 18000 79000 24000 6000 14000 30917.920 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30915000 0 0 0 0 0 0 monthplot 7 1715205617 320151.360 3 12000 18000 17000 19000 33000 23000 28000 347000 18000 55000 35000 14000 26000 60000 22000 23000 33000 31000 57000 64000 38000 33000 28000 49000 41000 46000 28000 26000 15000 14000 0 30915.420 36000 29000 38000 36000 1000 27000 38000 30915000 27000 6000 1000 16000 11000 3000 18000 5000 15000 12000 0 3000 2000 15000 33000 30000 0 1000 3000 19000 22000 30000 0 energyaccounting 6 5 68.56 287.41 557.62 -26.03 -16.09 189.48 8 79.00 9 20.00 7 46.96 4 5.51 5 9.97 1138.79 325.80

Ha de´ Kenneth

8 maj 2024 kl. 22:52 skrev ArnieO @.***>:

Huh, interesting. Do you see any sign in your data that this could be a number format / rollover error? What order of magnitude are the "normal" numbers?

— Reply to this email directly, view it on GitHub https://github.com/UtilitechAS/amsreader-firmware/issues/792#issuecomment-2101423237, or unsubscribe https://github.com/notifications/unsubscribe-auth/BILUX2QRNNVK5YLXYXS7XPDZBKF7RAVCNFSM6AAAAABHNSW2UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRGQZDGMRTG4. You are receiving this because you authored the thread.

ArnieO commented 5 months ago

I see nothing special about those values, just normal household consumptions.

So where is the problem...

You marked off the total accumulated energy meter reading yesterday: image Is this the wrong value? This should correspond to the value you see on the LCD screen of your meter. What do you see on the meter LCD? A photo would be great.

ycagwyn commented 5 months ago

9 maj 2024 kl. 09:22 skrev ArnieO @.***>:

I see nothing special about those values, just normal household consumptions.

So where is the problem...

You marked off the total accumulated energy meter reading yesterday: image.png (view on web) https://github.com/UtilitechAS/amsreader-firmware/assets/10295178/de51a409-2d33-404b-9ccd-54acc66c13a6 Is this the wrong value? This should correspond to the value you see on the LCD screen of your meter. What do you see on the meter LCD? A photo would be great.

— Reply to this email directly, view it on GitHub https://github.com/UtilitechAS/amsreader-firmware/issues/792#issuecomment-2102102816, or unsubscribe https://github.com/notifications/unsubscribe-auth/BILUX2TN76MEO6I67CPNG33ZBMP2RAVCNFSM6AAAAABHNSW2UWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBSGEYDEOBRGY. You are receiving this because you authored the thread.

ArnieO commented 5 months ago

You need to log into Github to attach photos, not send by email.

ycagwyn commented 5 months ago

IMG_1310

ycagwyn commented 5 months ago

PastedGraphic-1 Todays view

ArnieO commented 5 months ago

Thank you, that is interesting. Your LCD seems to show 3 decimals..? Mine does not show decimals on the LCD.

Is the accumulated export value also wrong in your GUI? image

ArnieO commented 5 months ago

Can you run a Telnet debug so that we can see what data the meter sends? https://www.amsleser.no/module/ets_blog/blog?id_post=24

ycagwyn commented 5 months ago

According to the netowner Boo Energi and the PV readings from APSystems ECU-C I have exported around 3800 kWh since installation end of June 2023 so I guess that is what should be presented as accumulated export. I'll try to run a Telnet debug as soon as I figured out how its done on Mac

ArnieO commented 5 months ago

I'll try to run a Telnet debug as soon as I figured out how its done on Mac

Good question! I'd greatly appreciate if you could send me a short description when you find out, so that I can add that information to the bog post.

The kWh values in your GUI are off by a factor ten. Please open the config page and set multiplier to 0.1 to fix that. We think this could be a root cause for the issues you are seeing. image

Is this something that suddenly happened, or did it show correct values previously? Maybe your meter has received a firmware update. We unfortunately have no way of knowing the number of decimals the meter sends, and it is not consistent. So in some cases a correction must be done by using the multipliers.

ycagwyn commented 5 months ago

Change of multipliers had no effect until I used dot(.) as decimal separator instead of comma(,) which is default at the GUI! Saw that decimals are used in Power saving dBm as well. Now my accumulated import and export numbers appears to be OK. Do you (as I) think it could be an idea to patch the plot numbers back into the cfg file?

ArnieO commented 5 months ago

It is unfortunately difficult to find a way to accept both decimal comma and point in the GUI, we are a bit stuck with the libraries we use.

Do you (as I) think it could be an idea to patch the plot numbers back into the cfg file?

If you mean editing the cfg file and load it back: Yes, sure. You can always keep a copy and revert if it does not do the trick. Editing the cfg file is a good way to restore in such a situation.

ycagwyn commented 5 months ago

So the conclusion is that my problem probably was caused by a firmware upgrade of the power meter which is fixed by changing multipliers kWh from 1 to 0.1. Also found that decimal sign used in GUI does not follow browsers locale. Thank you so much for your help. (I'll try Telnet on Mac and supply instructions if successful.)

ArnieO commented 5 months ago

So the conclusion is that my problem probably was caused by a firmware upgrade of the power meter which is fixed by changing multipliers kWh from 1 to 0.1.

Power meter firmware upgrade is my best hypothesis, if this suddenly appeared.

Also found that decimal sign used in GUI does not follow browsers locale.

Unfortunately correct.

Thank you so much for your help.

You're welcome!

(I'll try Telnet on Mac and supply instructions if successful.)

That would be great! 👍

(Please close thread if you consider issue solved.)

ycagwyn commented 5 months ago

Sorry but got this after reset of "Enable debugging" and reboot. Retried typing 0.1 as kWh multiplier. What did I do wrong, do I have to wait for accumulated figures? image

ycagwyn commented 5 months ago

Yes wait was the answer, sorry about that.

ycagwyn commented 5 months ago

Hello again. Promised make some notes regarding telnet on a Mac and this is what came out of it. Feel free to use it anyway you want. Telnet AMS-reader on Mac.pdf

ArnieO commented 5 months ago

Fantastic - thank you! Will add it to the blogpost ASAP.