Dsmr-parser

Latest version: v1.4.2

Safety actively analyzes 685670 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 8

0.11

- NULL value fix in checksum (`PR 26 <https://github.com/ndokter/dsmr_parser/pull/26>`_)

0.10

- bugfix: don't force full telegram signatures (`PR 25 <https://github.com/ndokter/dsmr_parser/pull/25>`_)
- removed unused code for automatic telegram detection as this needs reworking after the fix mentioned above
- InvalidChecksumError's are logged as warning instead of error

0.9

- added DSMR v5 serial settings

0.8

- added support for DSMR v3
- added support for DSMR v5

**IMPORTANT: this release has the following backwards incompatible changes:**

- Removed TelegramParserV2_2 in favor of TelegramParser
- Removed TelegramParserV4 in favor of TelegramParser

0.7

- Internal refactoring related to the way clients feed their data into the parse module. Clients can now supply the telegram data in single characters, lines (which was common) or complete telegram strings. (`PR 17 <https://github.com/ndokter/dsmr_parser/pull/17>`_)

**IMPORTANT: this release has the following backwards incompatible changes:**

- Client related imports from dsmr_parser.serial and dsmr_parser.protocol have been moved to dsmr_parser.clients (import these from the clients/__init__.py module)
- The .parse() method of TelegramParser, TelegramParserV2_2, TelegramParserV4 now accepts a string containing the entire telegram (including \r\n characters) and not a list

0.6

- Fixed bug in CRC checksum verification for the asyncio client (`PR 15 <https://github.com/ndokter/dsmr_parser/pull/15>`_)
- Support added for TCP connections using the asyncio client (`PR 12 <https://github.com/ndokter/dsmr_parser/pull/12/>`_)

Page 7 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.