They have now shut the door and said that they will not provide any further support.
Can anyone tell if that log output suggests that the port is encrypted (my suspicion), or any other obvious issue that would stop it working?
That answer is weird, but to be honest you have received far more information then any electricity company would give.
If you have that log in hex format, then you can paste it here to get it decoded:
Actually, you can paste that ASCII into the decoder to get it converted to hex as well.
Try to adjust your setting according the description on the image:
115200 8N1
If it is still not working try to invert the the serial.
Where is that log came from? Have you turned on verbose mode on the AMSREADER? You should be able to see there any messages in HEX coming from the meter.
Otherwise if you would post text instead of images, then we could help to decode it.
You may tweak these parameters.
port – Device name or None.
baudrate (int) – Baud rate such as 9600 or 115200 etc.
bytesize – Number of data bits. Possible values: FIVEBITS, SIXBITS, SEVENBITS, EIGHTBITS
parity – Enable parity checking. Possible values: PARITY_NONE, PARITY_EVEN, PARITY_ODD PARITY_MARK, PARITY_SPACE
stopbits – Number of stop bits. Possible values: STOPBITS_ONE, STOPBITS_ONE_POINT_FIVE, STOPBITS_TWO
timeout (float) – Set a read timeout value in seconds.
xonxoff (bool) – Enable software flow control.
rtscts (bool) – Enable hardware (RTS/CTS) flow control.
dsrdtr (bool) – Enable hardware (DSR/DTR) flow control.
write_timeout (float) – Set a write timeout value in seconds.
inter_byte_timeout (float) – Inter-character timeout, None to disable (default).
exclusive (bool) – Set exclusive access mode (POSIX only). A port cannot be opened in exclusive access mode if it is already open in exclusive access mode.
Or you don’t display the information correctly.
Tweak the bit order too.
What I do is to use an oscilloscope when I really have difficulties to read a message on a serial line. You can find values like “speed” quite easily.
If you provide an hex dump, I can try to see if I find something.
Tasmota is able to read the ISKRA SM’s P1 port, extract the values for the OBIS codes delivered out of the HDLC/DLMS encoded binary telegram and publish them towards a topic of your MQTT broker.
Unfortunately, this currently only works for unencrypted DLMS APDUs which is the case for RE. The reason is that ISKRA uses a HDLC segmentation approach different from other SM.
The reason that amsReader is only capable to extract very few values (those delivered in frame no. 1) boils down to the same problem with the inability to correctly reassemble the 3 HDLC frames.
This problem should, can and will eventually be fixed. The c++ code is open-source. It’s just a matter of time and priorities.
As long as the DLMS APDU is being pushed unencrypted, Tasmota is already capable of diging the values out of the binary telegram, thanks to its user configurable pattern-matching through its admin webUI.
For more information on SM CII in Switzerland, you may want to search forume.ch or have a look at gPlug.ch.
you are right, I made a mistake with the LG one. I have to get access here to check which one of the model I have (SIL indicates the Iskra and LG as counters they install !
Hello everyone,
Romande Energie just installed Iskra AM550 and I would like to take the data to home assistant.
Based on different posts, can someone just summarize what i need to go forward in term of hardware and software?
I just received my Slimmelezer and I tried all of the listed suggestion here but I cannot get it to read any value. I always have this warning “[dsmr:092]: Timeout while reading data for telegram” what am I missing?
Thank you for your answer. It’s an Iskra AM 550 provided by Romande Energie switzerland. I think the port is active since I can power the p1meter from the rj12 only.