Skip to content
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

Help with Iskraemeco AM550 in Slovenia #869

Open
nori-modelar opened this issue Nov 15, 2024 · 45 comments
Open

Help with Iskraemeco AM550 in Slovenia #869

nori-modelar opened this issue Nov 15, 2024 · 45 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@nori-modelar
Copy link

nori-modelar commented Nov 15, 2024

Hello team,

first of all thanks for the hard work you've put in this, i greatly appreciate it even though i can not get this to work. The irony here is that Iskraemeco is from my country (Slovenia) and it works flawlessly for people living in other EU countries, but not for us here. This is also an edited post for other people coming from Slovenia, specifically from Elektro Ljubljana, who would like to get it working...

So the problem story:
-first i bought Slimmelezer+, did not work, no data
-bought Homewizard P1 meter, did not work, no data or extremely weird
-flashed Slimmelezer+ with AMSreader, does not work

Specs:

  • Country: Slovenija
  • Meter: Iskraemeco AM550 ED1.21 (picture attached)
  • Encryption : provider( El. Ljubljana) said the port is open, no encryption
  • AMS reader: slimmelezer+

Firmware:

  • Version: 2.3.9
  • Played around with different settings, baud etc. nothing helped.
  • Also played around with hardware section UART0&2 and also invert etc..nothing changes.

Now i did found on the web that im supposed to set the baud to 38400 for this Slovenian meter, if this is of any help
Telnet messages are down in the comments :)

Strangely I also found out on the web that some Slovenian users managed to get it working on the first try with homewizard reader, with the same meter and same electricity company here.

Any help would be very appreciated!

Screenshot 2024-11-15 at 23 11 22

IMG_8550

@AdmiralStipe

@ArnieO
Copy link
Contributor

ArnieO commented Nov 16, 2024

There seems to be some particular issues with the payload formats used by Slovenian grid companies.
Did you read this thread? #615
"Each of the grid disti's has their own variant. So practically approx. 9 different versions in Slovenia."

  • Do you have any documentation from your electricity company of your meter, especially the format of the data coming from it?
  • Run a Telnet debug to look at the raw data from the meter - and compare with the thread I linked.

@TimotejHofbauer
Copy link

TimotejHofbauer commented Nov 17, 2024

Managed to get data coming in, here is the section:
I am running on MacOS, so i could not really find telnet function to save a file of the data coming in.

Second question: No, currently not...will try to get it.
Seeing thread #615 , should I flash it with the "custom" fw in there? Will that solve anything?

(V) HDLC frame:
(V) 7E A0 61 CF 02 23 13 63 CA E6 E7 00 0F 00 04 56
(V) 0D 0C 07 E8 0B 11 07 15 1A 2C 00 FF C4 00 02 09
(V) 09 10 49 53 4B 31 30 32 30 37 38 34 36 30 35 38
(V) 38 37 09 0B 49 53 4B 38 34 36 30 35 38 38 37 06
(V) 00 00 01 75 06 00 00 00 00 06 00 00 00 00 06 00
(V) 00 00 00 12 08 FD 06 00 00 00 00 06 00 00 00 00
(V) 8D 22 7E
(V) LLC frame:
(V) E6 E7 00 0F 00 04 56 0D 0C 07 E8 0B 11 07 15 1A
(V) 2C 00 FF C4 00 02 09 09 10 49 53 4B 31 30 32 30
(V) 37 38 34 36 30 35 38 38 37 09 0B 49 53 4B 38 34
(V) 36 30 35 38 38 37 06 00 00 01 75 06 00 00 00 00
(V) 06 00 00 00 00 06 00 00 00 00 12 08 FD 06 00 00
(V) 00 00 06 00 00 00 00
(V) DLMS frame:
(V) 0F 00 04 56 0D 0C 07 E8 0B 11 07 15 1A 2C 00 FF
(V) C4 00 02 09 09 10 49 53 4B 31 30 32 30 37 38 34
(V) 36 30 35 38 38 37 09 0B 49 53 4B 38 34 36 30 35
(V) 38 38 37 06 00 00 01 75 06 00 00 00 00 06 00 00
(V) 00 00 06 00 00 00 00 12 08 FD 06 00 00 00 00 06
(V) 00 00 00 00
(D) Received valid DLMS at 30
(V) Using application data:
(V) 02 09 09 10 49 53 4B 31 30 32 30 37 38 34 36 30
(V) 35 38 38 37 09 0B 49 53 4B 38 34 36 30 35 38 38
(V) 37 06 00 00 01 75 06 00 00 00 00 06 00 00 00 00
(V) 06 00 00 00 00 12 08 FD 06 00 00 00 00 06 00 00
(V) 00 00
(V) DLMS

@ArnieO
Copy link
Contributor

ArnieO commented Nov 18, 2024

I am running on MacOS, so i could not really find telnet function to save a file of the data coming in.

This is just fine! The DLSM section can be decoded using this tool, which gives the folloing in XML format:

<DataNotification>
  <LongInvokeIdAndPriority Value="0004560D" />
  <!--2024-11-17 21:26:44-->
  <DateTime Value="07E80B1107151A2C00FFC400" />
  <NotificationBody>
    <DataValue>
      <Structure Qty="09" >
        <!--ISK1020784605887-->
        <OctetString Value="49534B31303230373834363035383837" />
        <!--ISK84605887-->
        <OctetString Value="49534B3834363035383837" />
        <UInt32 Value="00000175" />
        <UInt32 Value="00000000" />
        <UInt32 Value="00000000" />
        <UInt32 Value="00000000" />
        <UInt16 Value="08FD" />
        <UInt32 Value="00000000" />
        <UInt32 Value="00000000" />
      </Structure>
    </DataValue>
  </NotificationBody>
</DataNotification>

This looks quite similar to some of the payloads in that thread , but is apparently not identical.

The test firmware that @gskjold published in the thread is integrated in the project now, so it will not help you.

It seems like the problem is this: #615 (comment)

HI All; I did some calls today - and its true.
Each of the grid disti's has their own variant. So practically approx. 9 different versions in Slovenia.

And the answer from @gskjold right after:

That is unfortunate... But I will keep this in mind in case I can think of a good way to support this

I will put it the issue on our agenda to see if something can be done to handle your case.

Note:
As the payload does not use OBIS codes to identify the list of parameters, we will need the same type of information for your meter / grid operator as what @svaliv49 provided at the end of this post: #615 (comment)

@TimotejHofbauer
Copy link

Managed to obtain some info from an employee at Elektro Ljubljana (distributer), sorry for the delay.

Communication:
image008

Telegram per second:
image009

Telegram 15min:

Unknown

image012

Is this enough? I am having hard times explaining to him what exactly to send over so if anything more is needed just let me know and make it specific.

@ArnieO
Copy link
Contributor

ArnieO commented Nov 22, 2024

Is this enough?

Yes, this seems to be it - and the "per second telegram" (it is maybe 5 seconds interval?) seems to correspond with what you sent earlier.

In order to proceed, we also need you to capture a "15 minute telegram". Can you do that?

@nori-modelar
Copy link
Author

The person from El.Ljubljana said it is 1s telegram and attached the picture above. And when im running telnet I believe im seeing data refreshing every second.

Here you can see (when i run DLS translator) that we have data for the 59th second and then the 15min data, one after another...meaning 1 second refresh if i get it right.
But in the last line you can see something i was not able to find anywhere on Github-therefore bellow i have attached another run of the code for the next quarter 15min reading.

Data for UTC 19:45 and one second before here:

(V) HDLC frame:
(V) 7E A0 61 CF  02 23 13 63  CA E6 E7 00  0F 00 0A E7 
(V) 82 0C 07 E8  0B 16 05 14  2C 3B 00 FF  C4 00 02 09 
(V) 09 10 49 53  4B 31 30 32  30 37 38 34  36 30 35 38 
(V) 38 37 09 0B  49 53 4B 38  34 36 30 35  38 38 37 06 
(V) 00 00 02 50  06 00 00 00  00 06 00 00  00 00 06 00 
(V) 00 00 70 12  09 09 06 00  00 00 00 06  00 00 00 00 
(V) 13 66 7E 
(V) LLC frame:
(V) E6 E7 00 0F  00 0A E7 82  0C 07 E8 0B  16 05 14 2C 
(V) 3B 00 FF C4  00 02 09 09  10 49 53 4B  31 30 32 30 
(V) 37 38 34 36  30 35 38 38  37 09 0B 49  53 4B 38 34 
(V) 36 30 35 38  38 37 06 00  00 02 50 06  00 00 00 00 
(V) 06 00 00 00  00 06 00 00  00 70 12 09  09 06 00 00 
(V) 00 00 06 00  00 00 00 
(V) DLMS frame:
(V) 0F 00 0A E7  82 0C 07 E8  0B 16 05 14  2C 3B 00 FF 
(V) C4 00 02 09  09 10 49 53  4B 31 30 32  30 37 38 34 
(V) 36 30 35 38  38 37 09 0B  49 53 4B 38  34 36 30 35 
(V) 38 38 37 06  00 00 02 50  06 00 00 00  00 06 00 00 
(V) 00 00 06 00  00 00 70 12  09 09 06 00  00 00 00 06 
(V) 00 00 00 00  
(D) Received valid DLMS at 30
(V) Using application data:
(V) 02 09 09 10  49 53 4B 31  30 32 30 37  38 34 36 30 
(V) 35 38 38 37  09 0B 49 53  4B 38 34 36  30 35 38 38 
(V) 37 06 00 00  02 50 06 00  00 00 00 06  00 00 00 00 
(V) 06 00 00 00  70 12 09 09  06 00 00 00  00 06 00 00 
(V) 00 00 
(V) DLMS
(V) HDLC frame:
(V) 7E A0 37 CF  02 23 13 99  84 E6 E7 00  0F 00 0A E7 
(V) 83 0C 07 E8  0B 16 05 14  2D 00 00 FF  C4 00 02 04 
(V) 09 08 38 34  36 30 35 38  38 37 11 00  06 00 78 EB 
(V) A1 06 00 00  00 00 85 7B  7E 
(V) LLC frame:
(V) E6 E7 00 0F  00 0A E7 83  0C 07 E8 0B  16 05 14 2D 
(V) 00 00 FF C4  00 02 04 09  08 38 34 36  30 35 38 38 
(V) 37 11 00 06  00 78 EB A1  06 00 00 00  00 
(V) DLMS frame:
(V) 0F 00 0A E7  83 0C 07 E8  0B 16 05 14  2D 00 00 FF 
(V) C4 00 02 04  09 08 38 34  36 30 35 38  38 37 11 00 
(V) 06 00 78 EB  A1 06 00 00  00 00 
(D) Received valid DLMS at 30
(V) Using application data:
(V) 02 04 09 08  38 34 36 30  35 38 38 37  11 00 06 00 
(V) 78 EB A1 06  00 00 00 00  
(V) DLMS
(D) NOT Ready to update (internal clock 19:45:05 UTC, meter clock: 00:00:00, list type 3, est: 0)

Data for UTC 20:00 and one second after:

(V) HDLC frame:
(V) 7E A0 37 CF  02 23 13 99  84 E6 E7 00  0F 00 0A EB 
(V) 09 0C 07 E8  0B 16 05 15  00 00 00 FF  C4 00 02 04 
(V) 09 08 38 34  36 30 35 38  38 37 11 00  06 00 78 EC 
(V) 38 06 00 00  00 00 12 17  7E 
(V) LLC frame:
(V) E6 E7 00 0F  00 0A EB 09  0C 07 E8 0B  16 05 15 00 
(V) 00 00 FF C4  00 02 04 09  08 38 34 36  30 35 38 38 
(V) 37 11 00 06  00 78 EC 38  06 00 00 00  00 
(V) DLMS frame:
(V) 0F 00 0A EB  09 0C 07 E8  0B 16 05 15  00 00 00 FF 
(V) C4 00 02 04  09 08 38 34  36 30 35 38  38 37 11 00 
(V) 06 00 78 EC  38 06 00 00  00 00 
(D) Received valid DLMS at 30
(V) Using application data:
(V) 02 04 09 08  38 34 36 30  35 38 38 37  11 00 06 00 
(V) 78 EC 38 06  00 00 00 00  
(V) DLMS
(D) READY to update (internal clock 20:00:05 UTC, meter clock: 00:00:00, list type 3, est: 0, using clock: 1)
(D) Updating data storage using actual data
(D) Clearing hours from 19 to 20
(D) Clearing days from 22 to 22
(D) Day is not happy
(D)  - normal
(I) Saving data
(V) HDLC frame:
(V) 7E A0 61 CF  02 23 13 63  CA E6 E7 00  0F 00 0A EB 
(V) 0A 0C 07 E8  0B 16 05 15  00 00 00 FF  C4 00 02 09 
(V) 09 10 49 53  4B 31 30 32  30 37 38 34  36 30 35 38 
(V) 38 37 09 0B  49 53 4B 38  34 36 30 35  38 38 37 06 
(V) 00 00 02 57  06 00 00 00  00 06 00 00  00 00 06 00 
(V) 00 00 5D 12  09 07 06 00  00 00 00 06  00 00 00 00 
(V) 4B E1 7E 
(V) LLC frame:
(V) E6 E7 00 0F  00 0A EB 0A  0C 07 E8 0B  16 05 15 00 
(V) 00 00 FF C4  00 02 09 09  10 49 53 4B  31 30 32 30 
(V) 37 38 34 36  30 35 38 38  37 09 0B 49  53 4B 38 34 
(V) 36 30 35 38  38 37 06 00  00 02 57 06  00 00 00 00 
(V) 06 00 00 00  00 06 00 00  00 5D 12 09  07 06 00 00 
(V) 00 00 06 00  00 00 00 
(V) DLMS frame:
(V) 0F 00 0A EB  0A 0C 07 E8  0B 16 05 15  00 00 00 FF 
(V) C4 00 02 09  09 10 49 53  4B 31 30 32  30 37 38 34 
(V) 36 30 35 38  38 37 09 0B  49 53 4B 38  34 36 30 35 
(V) 38 38 37 06  00 00 02 57  06 00 00 00  00 06 00 00 
(V) 00 00 06 00  00 00 5D 12  09 07 06 00  00 00 00 06 
(V) 00 00 00 00  
(D) Received valid DLMS at 30
(V) Using application data:
(V) 02 09 09 10  49 53 4B 31  30 32 30 37  38 34 36 30 
(V) 35 38 38 37  09 0B 49 53  4B 38 34 36  30 35 38 38 
(V) 37 06 00 00  02 57 06 00  00 00 00 06  00 00 00 00 
(V) 06 00 00 00  5D 12 09 07  06 00 00 00  00 06 00 00 
(V) 00 00 
(V) DLMS

@nori-modelar
Copy link
Author

Totally missed that, but at least something is working. When i checked status on the physical meter and then AMS reader, this number is correct. 7925kWh

This is the comulative sum of high&low energy use (kWh) from the date when this meter was set up.
This number updates every 15min, checked.

Screenshot 2024-11-22 at 21 21 40

@ArnieO
Copy link
Contributor

ArnieO commented Nov 23, 2024

Thank you - I'll check that 15 minute telegram later.
Are you two @nori-modelar and @TimotejHofbauer with the same distributor (El.Ljubljana)?

@ArnieO
Copy link
Contributor

ArnieO commented Nov 23, 2024

This is the comulative sum of high&low energy use (kWh) from the date when this meter was set up.

That would be the sum of these two:
image

Which is correct, as we do not handle day/night tariffs in this firmware.
So on meters that have separate counters for day/night tariff we add the two.

It seems like we then just need a tweek to recognize correctly the other data points in the telegram. I know @gskjold has a busy period right now - so please be patient until he gets a chance to look into this.

@ArnieO ArnieO added the enhancement New feature or request label Nov 23, 2024
@nori-modelar
Copy link
Author

nori-modelar commented Nov 23, 2024

@ArnieO It is just me, logged in from another account by mistake. I am also seeing at least two others Slovenians (Dist: El. Ljubljana) under discussion and other issues so I hope they will have the chance to test it together with me once the fix is out.

Seems like that yes, thanks for the help so far!

@ArnieO
Copy link
Contributor

ArnieO commented Nov 23, 2024

@ArnieO It is just me, logged in from another account by mistake.

No problem, I just wanted to be sure the logs and the info from the grid company was for the same meter.

@mutymaster
Copy link

settings-configfile

Hi, I'm also from Slovenia and this are my settings for AMS reader using Slimmelezer+ together with HA via MQTT.
Try to set HAN RX to UART2 :)

@nori-modelar
Copy link
Author

@mutymaster You did not clarify if this solves anything? Will try when i get back home but i believe you got green HAN only because you are at 20:30 therefore the 15min interval is received and the HAN goes green for a few seconds-otherwise nothing else is received like it should be.

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

Hi, I'm also from Slovenia and this are my settings for AMS reader using Slimmelezer+ together with HA via MQTT.
Try to set HAN RX to UART2 :)

Thank you for that @mutymaster - but the issue here is that the firmware currently does not handle all the various payload formats used in Slovenia.

Unfortunately, the format and content of payloads varies significantly. As long as the content includes so called "OBIS codes" that identify each parameter, our firmware will be able to recognize the parameter.

In the case of Slovenia:

  1. The payloads do NOT include OBIS codes that identify the parameters (Example: Help with Iskraemeco AM550 in Slovenia #869 (comment))
  2. There seems to be (at least) nine grid companies that use slightly different content in the payloads. See No data is displayed/decoded although connection to meter is OK #615 (comment)

In order to handle such payloads, we need to write some code for each variant - and will then need documentation to identify the payload content.

@mutymaster
Copy link

@mutymaster You did not clarify if this solves anything? Will try when i get back home but i believe you got green HAN only because you are at 20:30 therefore the 15min interval is received and the HAN goes green for a few seconds-otherwise nothing else is received like it should be.

You are wrong. It's sending data all the time continuously in 5s intervals. HAN is GREEN all the time... In HA I am monitoring live data to operate current limit on the phases and consumption.

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

HAN is GREEN all the time..

Green all the time?
image

@mutymaster
Copy link

mutymaster commented Nov 28, 2024

I am not aware of OBIS codes, I just wanted to say that it works for me and my needs of live data sampling from the meter. Sorry for old photo - the point were the settings, not sure why HAN was offline at that moment. It sure is online now all the time. I have restarted it and here you go:
ams

ams2

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

I am not aware of OBIS codes, I just wanted to say that it works for me and my needs of live data sampling frome the meter.

Which is great! 👍
We know that we currently handle some Slovenian formats - but not yet all.

Which grid company / distributor are you with?

@mutymaster
Copy link

mutymaster commented Nov 28, 2024

Which grid company / distributor are you with?

Elektro Gorenjska

The only issue I am facing with slimmelezer+ is that I need to start it with powering it over the usb-c connector and after it booted, I can disconnect it and it will work on its own over the LAN cable. Also, when the Wi-Fi signal is lost it powers off and I need to revive it again. Haven't yet figure that out.

@mutymaster
Copy link

HAN is GREEN all the time..

Green all the time? image

Ok, I have checked and tested it again, both HAN RX and TX should be set to UART2 so HAN is green and working all the time. I am apologizing for spamming wrong informations before.

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

I am apologizing for spamming wrong informations before.

No problem at all, confirmation on working setups is always interesting. And thank you for confirming your distributor is Elektro Gorenjska.

@nori-modelar
Copy link
Author

nori-modelar commented Nov 28, 2024

Yeah, i am facing same issues with the slimmelezer...seems like there is not enough power for the startup. Although i did manage to power it up without the powerbank, just plug it in really fast two times so some energy is still stored in the capacitors form the first unsuccessful power up. The settings in AMSreader do not really change anything (power db)

I am definitely buying AMSreader HW if this power-up thing can be solved.

When it comes to your case, glad to see it working, but i did notice yes that Elektro Gorenjska is working for multiple users while Elektro Ljubljana is still a mystery :)

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

I am definitely buying AMSreader HW if this power-up thing can be solved.

We do not see this issue on our hardware.

Elektro Ljubljana is still a mystery :)

Not a mystery! 😄 We have the input we need, it is just a matter of @gskjold finding time to do some code adjustments.

@nori-modelar
Copy link
Author

@ArnieO So which HW is the right for my use? It needs to be on WIFI. I believe it would be fair to contribute to you and @gskjold in that way!

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

@ArnieO So which HW is the right for my use? It needs to be on WIFI. I believe it would be fair to contribute to you and @gskjold in that way!

It is the Pow-P1 - and you will see the recommendation if you use the Selection guide in our webshop: https://www.amsleser.no/index.php?fc=module&module=ams_selector&controller=display (We will add Slovenia to the list of known countries for Iskraemeco AM550 with a note regarding which distributors are currently covered.)

You can place order on Lectronz: https://lectronz.com/products/pow-p1-reader-for-power-meter-with-p1-port

@svaliv49
Copy link

Just jumping in here, we had that discussion last year - hello All. Great seeing progress with the multi-standard country Slovenia 😠. I am on Elektro Celje - had to write my own script to get it working on a RPI4 and than in HA. But would definitely go with the AMSreader once Elektro Celje (ECE) would be implemented 👍.

@ArnieO ArnieO changed the title Help with Iskraemeco AM550 Help with Iskraemeco AM550 in Slovenia Nov 28, 2024
@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

once Elektro Celje (ECE) would be implemented

It would be great if you could post example payloads (both the 5 second and 15 minute) and content definitions. We could then implement in parallell with Elektro Ljubljana.

@svaliv49
Copy link

sure. let me do this when I return from my trip and am back in office.

@rvetrsek
Copy link

rvetrsek commented Nov 28, 2024

Hi all, I started playing around with my Slimmelezer+ again today here in Slovenia on an AM550 meter, and while it still doesn't work, I thought I would share my frames to see if it helps the developers add support or if someone has some pointers for me to try.

My setup is like this:

  • Meter: AM550
  • Location: Slovenia
  • Distributor: Elektro Ljubljana (GEN-i)
  • I need to enable decryption so the red message about authentication disappears. I have some description keys from when I first started playing with this.
  • Board: Slimmelezer+
  • Communication: Passive
  • Serial conf.:
    • Inverted: false
    • 38400
    • 8N1
    • 512
  • Voltage: 230V
  • Main fuse: 20
  • Production: 0
  • Multipliers: false
  • HAN RX: UART2
  • HAN TX:
  • Pullup: false
  • Inverted: true
  • AP button: 0
  • LED:
  • RGB inverted: false
  • RGB:
  • LED dis. GPIO: 0
  • Temperature:
  • Analog temp:
  • Vcc offset: 0
  • Multiplier: 1
  • Boot limit: 2.6

These are my DLMS frames:

1s

Raw

0F 00 34 25  28 0C 07 E8  0B 1C 04 0F  0F 01 00 FF
C4 00 02 09  09 10 49 53  4B 31 30 33  30 37 37 37
34 37 38 35  38 36 06 00  00 02 71 06  00 00 00 00
06 00 C3 28  BE 06 00 57  7A 26 06 00  6B AE 98 06
00 00 00 FA  06 00 00 00  70 06 00 00  00 8A

Translated

<DataNotification>
  <LongInvokeIdAndPriority Value="00342528" />
  <!--2024-11-28 15:15:01-->
  <DateTime Value="07E80B1C040F0F0100FFC400" />
  <NotificationBody>
    <DataValue>
      <Structure Qty="09" >
        <!--ISK1030777478586-->
        <OctetString Value="49534B31303330373737343738353836" />
        <UInt32 Value="00000271" />
        <UInt32 Value="00000000" />
        <UInt32 Value="00C328BE" />
        <UInt32 Value="00577A26" />
        <UInt32 Value="006BAE98" />
        <UInt32 Value="000000FA" />
        <UInt32 Value="00000070" />
        <UInt32 Value="0000008A" />
      </Structure>
    </DataValue>
  </NotificationBody>
</DataNotification>

15m

Raw

0F 00 34 25  26 0C 07 E8  0B 1C 04 0F  0F 00 00 FF
C4 00 02 04  09 08 37 37  34 37 38 35  38 36 11 00
06 00 C3 28  BD 06 00 00  00 FA

Translated:

<DataNotification>
  <LongInvokeIdAndPriority Value="00342526" />
  <!--2024-11-28 15:15:00-->
  <DateTime Value="07E80B1C040F0F0000FFC400" />
  <NotificationBody>
    <DataValue>
      <Structure Qty="04" >
        <!--77478586-->
        <OctetString Value="3737343738353836" />
        <UInt8 Value="00" />
        <UInt32 Value="00C328BD" />
        <UInt32 Value="000000FA" />
      </Structure>
    </DataValue>
  </NotificationBody>
</DataNotification>

@ArnieO
Copy link
Contributor

ArnieO commented Nov 28, 2024

@rvetrsek : The parameter list for Elektro Ljubjana is given here: #869 (comment).

(And please - this is not the right forum for discussing how to configure Slimmelezer; thank you for your understanding!)

@ArnieO
Copy link
Contributor

ArnieO commented Dec 5, 2024

Those of you that are with Elektro Lubljana: Please see: #858 (comment)

We need to understand if payloads from meters with Elektro Lubljana work (or not) with correct bitrate setting.
Are there maybe differences between 1- and 3-phase meters?

@rvetrsek
Copy link

rvetrsek commented Dec 5, 2024

If I may, I have those settings, and it produces a seemingly correct output when debugging with telnet. However, the HAN indicator stays red, and no data is shown on the dashboard.

I'm with Elektro Ljubljana on a 3-phase connection.

@gskjold
Copy link
Member

gskjold commented Dec 5, 2024

Here is a test firmware for those who still have issues:
esp32s3.zip
esp32solo.zip
esp32.zip
esp8266.zip
esp32c3.zip
esp32s2.zip

@gskjold gskjold added this to the v2.4.0 milestone Dec 5, 2024
@ArnieO
Copy link
Contributor

ArnieO commented Dec 5, 2024

If I may, I have those settings, and it produces a seemingly correct output when debugging with telnet. However, the HAN indicator stays red, and no data is shown on the dashboard.

I'm with Elektro Ljubljana on a 3-phase connection.

Have you set baud rate to 38 400 and parity to 8N1?

@rvetrsek
Copy link

rvetrsek commented Dec 5, 2024

Yes, these are my current settings:
image

They are the only way I could get the results I posted in the comment above (#869 (comment)).

I'll try the test firmware @gskjold posted and see if that makes any difference.

@ArnieO
Copy link
Contributor

ArnieO commented Dec 5, 2024

Yes, these are my current settings:

Interesting: One user with Elektro Ljubljana can read, an other cannot.
Strange situation. Could one of you "locals" try to contact Elektro Ljubljana and find out whether there are different payloads being used? For instance single phase vs 3-phase meters?

@nori-modelar
Copy link
Author

nori-modelar commented Dec 5, 2024

So just to clarify telnet shows proper data (picture bellow) only when at this settings no matter the buffer size setting.
I am on single phase connection, therefore @rvetrsek setup should be working as he has the same config as the @davidg-o from the https://github.com/UtilitechAS/amsreader-firmware/discussions/858#discussioncomment-11462856 , but apparently it is not working even though both of them are on the same three phase from elektro ljubljana.

And i would also assume that the meters are the same it is only a matter of connecting one or three phases through it.

Anyway, I tested @gskjold custom fw but it is the same. Only 15min interval updates the total kWh number on the front page.

Screenshot 2024-12-05 at 20 19 55

@zitko
Copy link

zitko commented Dec 8, 2024

Hi all! I'm joining this thread as my grid company is also Elektro Ljubljana. I have POW-P1 device attached to IskraEmeco AM550 meter (exact model is AM550-ED1.21). The grid company configured P1 port on the meter to unencrypted mode.
My communication settings are set to 38400/8N1, unencrypted, not inverted.

@gskjold thank you very much for the updated firmware! I flashed my device but it doesn't seem to improve the situation. It correctly detects the meter as Iskra and shows the summary consumption (as was the case with 2.3.9). It does not show the current input and/or historical data.

Screenshot 2024-12-08 at 18 56 23

Posting some frames I get through telnet interface below. Posting both LLC and DLMS frames just in case, I understood that LLC is just a wrapper around DLMS ...

LLC frame

Raw

E6 E7 00 0F  00 25 2E 9E  0C 07 E8 0C  08 07 13 05
1E 00 FF C4  00 02 0A 09  10 49 53 4B  31 30 32 30
37 38 35 37  36 36 36 34  39 09 0B 49  53 4B 38 35
37 36 36 36  34 39 06 00  00 02 1C 06  00 00 00 00
06 00 00 00  00 06 00 00  01 1A 12 09  20 12 01 16
06 00 00 02  1C 06 00 00  00 00

XML

<GatewayRequest>
  <NetworkId Value="231" />
  <PhysicalDeviceAddress Value="" />
  <DataNotification>
    <LongInvokeIdAndPriority Value="00252E9E" />
    <!--2024-12-08 19:05:30-->
    <DateTime Value="07E80C080713051E00FFC400" />
    <NotificationBody>
      <DataValue>
        <Structure Qty="0A" >
          <!--ISK1020785766649-->
          <OctetString Value="49534B31303230373835373636363439" />
          <!--ISK85766649-->
          <OctetString Value="49534B3835373636363439" />
          <UInt32 Value="0000021C" />
          <UInt32 Value="00000000" />
          <UInt32 Value="00000000" />
          <UInt32 Value="0000011A" />
          <UInt16 Value="0920" />
          <UInt16 Value="0116" />
          <UInt32 Value="0000021C" />
          <UInt32 Value="00000000" />
        </Structure>
      </DataValue>
    </NotificationBody>
  </DataNotification>
</GatewayRequest>

DLMS frame

Raw

0F 00 25 2E  9E 0C 07 E8  0C 08 07 13  05 1E 00 FF
C4 00 02 0A  09 10 49 53  4B 31 30 32  30 37 38 35
37 36 36 36  34 39 09 0B  49 53 4B 38  35 37 36 36
36 34 39 06  00 00 02 1C  06 00 00 00  00 06 00 00
00 00 06 00  00 01 1A 12  09 20 12 01  16 06 00 00
02 1C 06 00  00 00 00

XML

<DataNotification>
  <LongInvokeIdAndPriority Value="00252E9E" />
  <!--2024-12-08 19:05:30-->
  <DateTime Value="07E80C080713051E00FFC400" />
  <NotificationBody>
    <DataValue>
      <Structure Qty="0A" >
        <!--ISK1020785766649-->
        <OctetString Value="49534B31303230373835373636363439" />
        <!--ISK85766649-->
        <OctetString Value="49534B3835373636363439" />
        <UInt32 Value="0000021C" />
        <UInt32 Value="00000000" />
        <UInt32 Value="00000000" />
        <UInt32 Value="0000011A" />
        <UInt16 Value="0920" />
        <UInt16 Value="0116" />
        <UInt32 Value="0000021C" />
        <UInt32 Value="00000000" />
      </Structure>
    </DataValue>
  </NotificationBody>
</DataNotification>

@gskjold
Copy link
Member

gskjold commented Dec 8, 2024

Alright, lets try this again:
esp32s3.zip
esp32solo.zip
esp32.zip
esp8266.zip
esp32c3.zip
esp32s2.zip

@zitko
Copy link

zitko commented Dec 8, 2024

@gskjold, great, thank you for your quick response and new firmware!

Flashed my POW-P1, seems it's working now (HAN indicator is green)!

This is how the dashboard looks like with the latest firmware:
Screenshot 2024-12-08 at 21 02 00

Is there anything else I should check to confirm it's working?

@gskjold
Copy link
Member

gskjold commented Dec 8, 2024

Nice, just keep using it and see if you notice anything that does not seem right :)

@nori-modelar
Copy link
Author

@gskjold It is indeed working for me as well! Great job, many thanks so far!

Import power seems to be accurate, i measured it with other device just to be sure.

Funny I do not see any current going through though, and I believe me and @zitko are on the same setup, except for the measuring HW atm (slimmelezer vs yours)

Second thing is that under "Import" gauge we see Iskra and NOT the sum of Low + High energy, but rather this number is just the Low energy import within the lifespan of our meters. Before your custom fw we saw the sum of both. Which metric should be displayed here?

Third, Real time calculations are off, but again I don't know what should be the proper way of displaying them.

Screenshot 2024-12-08 at 21 53 01 Screenshot 2024-12-08 at 21 47 06

@rvetrsek
Copy link

rvetrsek commented Dec 9, 2024

Hey guys, the latest firmware that @gskjold posted finally brought at least some numbers into my dashboard, which is fantastic after months of trying different things and failing! Thank you, @gskjold! 👏

There is one weird thing. It seems that I'm exporting all my energy, which can't be because I don't have any alternative energy sources. So, is there a setting to let it know that that is the consumed energy?

image

@zitko
Copy link

zitko commented Dec 9, 2024

@gskjold, posting my observations after using firmware 0947d33 for about 24 hours:

  • Import gauge seems correct
  • not sure what should be shown directly under the Import gauge (- / kWh)?
  • the kWh right to the Iskra label (under import gauge) seems off as it has drastically decreased from v2.3.9. It might be only the low energy (and not low + high), as noted by @nori-modelar
  • Voltage & Amperage seem correct
  • Real time calculations / Consumptions are not adding up. I assume the Hour part is ok but not the other three (Day, Month, Last month)
  • Real time plot (W) seems correct
  • Energy use last 24 hours is empy, so is Energy use last 30 days (kWh)

This is dashboard screenshot:
Screenshot 2024-12-09 at 19 45 33

What I noticed in the debug logs are the following debugs (were not there in v2.3.9):

(D t:82718302ms) READY to update (internal clock 18:58:38 UTC, meter clock: 00:00:00, list type 2, est: 1, using clock: 1)

When the clock hits 19:00, the following is reported:

(D t:82809254ms) Updating data storage using actual data
(D t:82809258ms) Clearing hours from 18 to 19
(D t:82809258ms) Clearing days from 9 to 9
(D t:82809269ms) Day is not happy
(D t:82809273ms)  - normal
(I t:82809274ms) Saving data

from there on, debugs like this are reported:

(D t:82834289ms) NOT Ready to update (internal clock 19:00:34 UTC, meter clock: 00:00:00, list type 2, est: 1)

My guess is that when clock hits 20:00 it will switch to READY debugs again...

My wild guess would be that the readings received from the meter are not stored for some reason, might be the clock discrepancy between the internal clock/meter? That would explain missing historical data (anything >1 hour)?

@gskjold
Copy link
Member

gskjold commented Dec 12, 2024

Thank you all for thorough testing!

@nori-modelar :

Funny I do not see any current going through though, and I believe me and @zitko are on the same setup, except for the measuring HW atm (slimmelezer vs yours)

There seem to be two different payloads, one that contains current and one that does not. I don't know why some meters are different

Second thing is that under "Import" gauge we see Iskra and NOT the sum of Low + High energy, but rather this number is just the Low energy import within the lifespan of our meters. Before your custom fw we saw the sum of both. Which metric should be displayed here?

Code type-o on my end, sorry, should be fixed now!

Third, Real time calculations are off, but again I don't know what should be the proper way of displaying them.

Day and month real-time rely on the data in the day and month graph. If the graph is not populated, the real time calculation will also be off. The issue with the graph should be fixed in the attached version

@rvetrsek :

There is one weird thing. It seems that I'm exporting all my energy, which can't be because I don't have any alternative energy sources. So, is there a setting to let it know that that is the consumed energy?

Code type-o on my end, sorry, should be fixed now!

@zitko :

I think most your questions got answered above. I must commend your post though, very tidy report of your findings, the way I like it!

My wild guess would be that the readings received from the meter are not stored for some reason, might be the clock discrepancy between the internal clock/meter? That would explain missing historical data (anything >1 hour)?

The reason was a "list type" variable in the code, that indicated that these payloads did not have kWh meters in them. I have adjusted the setting of these variables to better reflect the content in the payloads. I am pretty sure we should see data now.

New version label should be 3bc40cb:
esp32s3.zip
esp32solo.zip
esp32.zip
esp8266.zip
esp32c3.zip
esp32s2.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

8 participants