| Name | PyKMP JSON |
| Version |
0.0.1
JSON |
| download |
| home_page | |
| Summary | Library for the KMP protocol used with Kamstrup electricity/energy meters (e.g. MULTICAL® 30x/40x/60x). |
| upload_time | 2023-09-24 21:34:04 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.10 |
| license | Apache License 2.0 |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
<!--
SPDX-FileCopyrightText: 2023 Gert van Dijk <github@gertvandijk.nl>
SPDX-License-Identifier: Apache-2.0
-->
# PyKMP – a Kamstrup meter toolset
[](https://python.org/)
[](https://mypy.readthedocs.io/en/stable/)
[](https://github.com/psf/black)
[](https://github.com/charliermarsh/ruff)
[](https://www.apache.org/licenses/LICENSE-2.0)
[](https://reuse.software/)
This module is developed for reading out Kamstrup meters using their vendor-specific KMP
protocol.
Tested with a MULTICAL® 403, based on documentation of the protocol for the older
MULTICAL® models.
Current state: *alpha* – based on the documentation it "should work" with a MULTICAL®
30x/40x/60x, but for other models: YMMV.
*Pull requests welcome!*
## Features ✨
*Note that this is a **library**, intended primarily for development or integration.*
- A **bundled CLI tool** to interact with the meter for testing/development purposes
with JSON format output (optional).
- Read **multiple registers in one go** to conserve the meter's internal battery as much
as possible.
- Having it all **fully type-annotated** (mypy strict, zero `type: ignore`s) should make
using this library a breeze.
- **100% test coverage** (library, not the tool yet).
- Ability to decode the base-10 variable length floating point values in registers
**without loss of significance**.
- **CRC checksum** verification (and adding).
- Agnostic to the direction for message encoding, ie. you could go wild and
**emulate a meter** using your IR head. 🤓
## Hardware requirements
For software: Python 3.10+ (and some generic dependencies).
For most situation you would want to use the optical/infrared interface.
For that, you will need an IR optical read-out head with serial (or serial-to-USB)
interface.
Using
[Ali-Express: 'USB to optical interface IrDA near-infrared magnetic adapter'][ali-e-link-optical-head]
this is confirmed working with the MULTICAL® 403 (IR head positioned upside down).
## Getting started 🚀
> [!IMPORTANT]\
> This project is not affiliated with Kamstrup A/S, Kamstrup B.V. or any other entity of
> the Kamstrup corporation.
>
> Please be informed about the battery consumption impact, read the note below.
>
> Use at your own risk.
First of all, you'll need Python 3.10+ (sorry, using modern Python features).
There's no release of this library yet, so I suggest you install the source
package using `pip` in a virtualenv.
E.g.:
```
$ git clone https://github.com/gertvdijk/PyKMP.git
$ cd PyKMP
$ python -m venv /tmp/venv
$ source /tmp/venv/bin/activate # every time in a new session to activate this venv
$ pip install -U pip setuptools # good idea to have an up-to-date pip & setuptools
$ pip install .[tool] # install from source with CLI tool dependencies
```
> [!NOTE]\
> 💡 If you intend to make changes to the library itself, may want to pass the
> `--editable` option ['Development Mode'][pip-install-editable] to the last command.
Let's explore some of the features by using the CLI tool first.
```
$ source venv/bin/activate # activate this venv in every new session
$ pykmp-tool --help
```
Retrieve some interesting metrics:
```
$ export PYKMP_SERIAL_DEVICE=/dev/ttyUSB0 # env var for convenience, less repetition
$ pykmp-tool get-register \
--register 60 \
--register 68 \
--register 80 \
--register 74 \
--register 86 \
--register 87 \
--register 266
GetRegister response(s):
60 → Heat Energy (E1) = 0.303 GJ
68 → Volume = 11.388 m³
80 → Current Power = 0.0 kW
74 → Flow = 3 l/h
86 → Temp1 = 61.62 °C
87 → Temp2 = 54.02 °C
266 → E1HighRes = 84208 Wh
```
> [!NOTE]\
> 💡 Add `--json` to get structured machine-readable output.
Debug the communication and decoding using `-vv`:
```
$ pykmp-tool get-register --register 1002
WARNING:pykmp.tool.__main__:Unknown register ID(s); please report this if you have more information.
GetRegister response(s):
1002 → <unknown reg 1002> = 200132 hh:mm:ss
$ pykmp-tool -vv get-register --register 1002
DEBUG:pykmp.client:Request encoded: 803F100103EA4CB70D
INFO:pykmp.client:Sending GetRegisterRequest...
DEBUG:pykmp.client:Received bytes on serial: '403F1003EA2F040000030E33B2320D'
DEBUG:pykmp.codec:Checksum verification OK [raw=3f1003ea2f040000030e33b232, crc_given=b232, crc_calculated=OK]
DEBUG:pykmp.messages:Decoding register bytes. [raw='03EA2F040000030E33', length_min=6]
DEBUG:pykmp.messages:Decoded register values: [id=1002, unit=47, value_bytes=040000030E33, remaining bytes=0]
WARNING:pykmp.tool.__main__:Unknown register ID(s); please report this if you have more information.
GetRegister response(s):
DEBUG:pykmp.codec:Decoding parts of floating point data. [data='040000030E33', integer_length=4]
DEBUG:pykmp.codec:Decoded floating point data: Decimal('200243') [data='040000030E33', man=200243, si=False, se=False, exp=0]
1002 → <unknown reg 1002> = 200243 hh:mm:ss
```
Clearly, some registers appear undiscovered and the formatting for some units need some
love. 😅
So far we've only seen GetRegister commands/responses.
Another command is 'GetSerialNo':
```
$ pykmp-tool get-serial
Meter serial is: 123456
```
To do the above programmatically:
```python
from pykmp import GetSerialRequest, PySerialClientCommunicator
multical = PySerialClientCommunicator(serial_device="/dev/ttyUSB0")
response = multical.send_request(message=GetSerialRequest())
print(f"Meter serial is: {response.serial}")
```
And for the registers:
```python
from pykmp import (
REGISTERS,
UNITS_NAMES,
FloatCodec,
GetRegisterRequest,
PySerialClientCommunicator,
)
multical = PySerialClientCommunicator(serial_device="/dev/ttyUSB0")
response = multical.send_request(
message=GetRegisterRequest(registers=[60, 68, 74, 80, 86, 87, 89, 266])
)
for reg in response.registers.values():
name, unit = REGISTERS.get(reg.id_, "?"), UNITS_NAMES.get(reg.unit, "?")
print(f"Register {reg.id_} ({name}) data: {FloatCodec.decode(reg.value)} {unit}")
```
## Store and graph metrics 📊
That's not really in scope of this library, but a separate project could (should) use
this library.
Anyway, it's planned to build that too!
`<img src="under-construction.gif">`
In the meantime, you could try to automate the output in JSON format using
`pykmp-tool get-register --json [...]`.
## Resources 📚
### KMP Protocol documentation
Technical description of meters sometimes show a little information of the design and
generic specification of the protocol.
This gives some clues about device-specific registers or a graphical explanation of the
OSI layers.
However, important details are in a separate document which is seemingly only available
under NDA. 😢
> **12.3 Data protocol**
>
> Utilities and other relevant companies who want to develop their own communication
> driver for the KMP protocol can order a demonstration program in C# (.net based) as
> well as a detailed protocol description (in English language).
Some more clues can be found in related communcation interfaces like MODBUS where
registers are listed:
[Modbus/KMP TCP/IP module for MULTICAL® 603 Data sheet][multical-hu-kmp-modbus-datasheet]
Nice people from the MeterLogger project have left [some notes][meterlogger-wiki-kmp]
for the development of the MeterLogger for Kamstrup meters.
Access to the vendor's own software to communicate with the meters ('Metertool HCW') is
not available (or at least not for free).
## Troubleshooting
### Unable to run the tool `pykmp-tool: command not found`
Using a Python package manager (e.g. pip) should ensure the entry point should be
installed somewhere in a directory that's on your PATH, but apparently that failed.
As an alternative, you can try to substitute `pykmp-tool` with `python -m pykmp.tool`.
### Unable to get a reading (connection timeout)
- Make sure your IR head has an included magnet that activates the meter's IR circuit.
If in doubt, activate it by pressing any button and try to get a reading while the
display is active.
- Make sure the RX/TX is aligned with the meter.
It's most if not all cases the IR head has to be placed in upside-down position.
- Try to re-align around the position of the IR eye while keeping a command running in a
loop in your shell.
## Other notes & TODOs ✍️
### Warning: battery consumption 🪫
Most Kamstrup meters for heat are battery-powered.
Using the optical/infrared interface will draw extra power from the battery and it may
deplete sooner when using this on a regular basis.
Extending the interval of reading should help, as well as requesting all data you need
in a single request (rather than looping).
Reading the battery level is not (yet) possible.
Some (older) models may require periodic re-activation of the IR-circuit.
### Connecting over the network (ser2net)
It's not always practical to communicate with the meter via (USB-to-)serial.
Using [ser2net][ser2net-github] on a (small) device close to the meter you can expose it
on your network.
Example configuration:
```yaml
connection: &mykamstrup
accepter: tcp,2002
connector: >-
serialdev,
/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0,
1200n82
options:
max-connections: 1
```
This above example uses TCP port 2002 on the host.
A connection can be made from any other host using:
```
$ pykmp-tool --serial-device socket://hostname:2002 [...]
```
Or use the environment variable to not having to specify it in every command:
```
$ export PYKMP_SERIAL_DEVICE=socket://hostname:2002
```
### Possible reading of higher resolution registers
In Kamstrup MULTICAL® 403 Technical description section
*11.3 Reading high resolution registers.* you'll find:
- E1ExtraDigit (9 digits instead of 8)
- E1HighRes ('internal' resolution, but truncated to include LSB)
It mentions kWh/Wh digits in that document, but the registers referred to can be
configured for MWh/GJ too, depending on the B-code (section 7.2). So, it may
work for configurations that display in GJ as well.
The register numbers and encodings aren't specified, though. However, the
MULTICAL® 302 Technical description section 13.1.1 mentions E1HighRes is
register ID 266 (decimal).
## Thanks to... 🙏
This project's existence is mainly thanks to all the information and regarding the KMP
protocol people have put online over the years.
As mentioned above, the MeterLogger project have left [some notes][meterlogger-wiki-kmp]
for the development of the MeterLogger for Kamstrup meters. Also the work by
Poul-Henning Kamp (and later Ronald van der Meer) in
[GitHub: `ronaldvdmeer/multical402-4-domoticz`][github-ronaldvdmeer-multical402]
was inspiring to get started with exploring possibilities and testing my hardware.
Finally, also a shoutout to the Dutch community Tweakers where a forum topic pointed out
the possibilities integrating these MULTICAL® meters (as provided by Dutch utilities) to
non-cloud smart home.
[GoT: Kamstrup Multical 402 stadsverwarmingsmeter RPI3+IR-kop][got-multical402-topic]
## License
The majority of the project is [Apache 2.0][apache-license-2] licensed.
Files deemed insignificant in terms of copyright such as configuration files are
licensed under the public domain "no rights reserved" [CC0] license.
The repository is [REUSE][reuse-home] compliant.
Read more on contributing in [CONTRIBUTING.md][contributing-md].
[ali-e-link-optical-head]: https://www.aliexpress.com/item/1005003509520122.html
[pip-install-editable]: https://setuptools.pypa.io/en/latest/userguide/development_mode.html
[multical-hu-kmp-modbus-datasheet]: https://www.multical.hu/upload/files/Modbus_KMP_TCP_IP.pdf
[ser2net-github]: https://github.com/cminyard/ser2net
[meterlogger-wiki-kmp]: https://github.com/nabovarme/MeterLogger/wiki/Kamstrup-Protocol
[github-ronaldvdmeer-multical402]: https://github.com/ronaldvdmeer/multical402-4-domoticz
[got-multical402-topic]: https://gathering.tweakers.net/forum/list_messages/1776625
[CC0]: https://creativecommons.org/share-your-work/public-domain/cc0/
[apache-license-2]: https://www.apache.org/licenses/LICENSE-2.0
[reuse-home]: https://reuse.software/
[contributing-md]: ./CONTRIBUTING.md
Raw data
{
"_id": null,
"home_page": "",
"name": "PyKMP",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": "",
"keywords": "",
"author": "",
"author_email": "Gert van Dijk <github@gertvandijk.nl>",
"download_url": "https://files.pythonhosted.org/packages/35/7b/a68b8207db0d923846ab8962f2e53c011449c98dd3771929559e9ab2bccf/PyKMP-0.0.1.tar.gz",
"platform": null,
"description": "<!--\nSPDX-FileCopyrightText: 2023 Gert van Dijk <github@gertvandijk.nl>\n\nSPDX-License-Identifier: Apache-2.0\n-->\n\n# PyKMP \u2013 a Kamstrup meter toolset\n\n[](https://python.org/)\n[](https://mypy.readthedocs.io/en/stable/)\n[](https://github.com/psf/black)\n[](https://github.com/charliermarsh/ruff)\n[](https://www.apache.org/licenses/LICENSE-2.0)\n[](https://reuse.software/)\n\nThis module is developed for reading out Kamstrup meters using their vendor-specific KMP\nprotocol.\n\nTested with a MULTICAL\u00ae 403, based on documentation of the protocol for the older\nMULTICAL\u00ae models.\n\nCurrent state: *alpha* \u2013 based on the documentation it \"should work\" with a MULTICAL\u00ae\n30x/40x/60x, but for other models: YMMV.\n*Pull requests welcome!*\n\n## Features \u2728\n\n*Note that this is a **library**, intended primarily for development or integration.*\n\n- A **bundled CLI tool** to interact with the meter for testing/development purposes\n with JSON format output (optional).\n- Read **multiple registers in one go** to conserve the meter's internal battery as much\n as possible.\n- Having it all **fully type-annotated** (mypy strict, zero `type: ignore`s) should make\n using this library a breeze.\n- **100% test coverage** (library, not the tool yet).\n- Ability to decode the base-10 variable length floating point values in registers\n **without loss of significance**.\n- **CRC checksum** verification (and adding).\n- Agnostic to the direction for message encoding, ie. you could go wild and\n **emulate a meter** using your IR head. \ud83e\udd13\n\n## Hardware requirements\n\nFor software: Python 3.10+ (and some generic dependencies).\n\nFor most situation you would want to use the optical/infrared interface.\nFor that, you will need an IR optical read-out head with serial (or serial-to-USB)\ninterface.\n\nUsing\n[Ali-Express: 'USB to optical interface IrDA near-infrared magnetic adapter'][ali-e-link-optical-head]\nthis is confirmed working with the MULTICAL\u00ae 403 (IR head positioned upside down).\n\n## Getting started \ud83d\ude80\n\n> [!IMPORTANT]\\\n> This project is not affiliated with Kamstrup A/S, Kamstrup B.V. or any other entity of\n> the Kamstrup corporation.\n>\n> Please be informed about the battery consumption impact, read the note below.\n>\n> Use at your own risk.\n\nFirst of all, you'll need Python 3.10+ (sorry, using modern Python features).\n\nThere's no release of this library yet, so I suggest you install the source\npackage using `pip` in a virtualenv.\n\nE.g.:\n\n```\n$ git clone https://github.com/gertvdijk/PyKMP.git\n$ cd PyKMP\n$ python -m venv /tmp/venv\n$ source /tmp/venv/bin/activate # every time in a new session to activate this venv\n$ pip install -U pip setuptools # good idea to have an up-to-date pip & setuptools\n$ pip install .[tool] # install from source with CLI tool dependencies\n```\n\n> [!NOTE]\\\n> \ud83d\udca1 If you intend to make changes to the library itself, may want to pass the\n> `--editable` option ['Development Mode'][pip-install-editable] to the last command.\n\nLet's explore some of the features by using the CLI tool first.\n\n```\n$ source venv/bin/activate # activate this venv in every new session\n$ pykmp-tool --help\n```\n\nRetrieve some interesting metrics:\n\n```\n$ export PYKMP_SERIAL_DEVICE=/dev/ttyUSB0 # env var for convenience, less repetition\n$ pykmp-tool get-register \\\n --register 60 \\\n --register 68 \\\n --register 80 \\\n --register 74 \\\n --register 86 \\\n --register 87 \\\n --register 266\nGetRegister response(s):\n 60 \u2192 Heat Energy (E1) = 0.303 GJ\n 68 \u2192 Volume = 11.388 m\u00b3\n 80 \u2192 Current Power = 0.0 kW\n 74 \u2192 Flow = 3 l/h\n 86 \u2192 Temp1 = 61.62 \u00b0C\n 87 \u2192 Temp2 = 54.02 \u00b0C\n 266 \u2192 E1HighRes = 84208 Wh\n```\n\n> [!NOTE]\\\n> \ud83d\udca1 Add `--json` to get structured machine-readable output.\n\nDebug the communication and decoding using `-vv`:\n\n```\n$ pykmp-tool get-register --register 1002\nWARNING:pykmp.tool.__main__:Unknown register ID(s); please report this if you have more information.\nGetRegister response(s):\n1002 \u2192 <unknown reg 1002> = 200132 hh:mm:ss\n\n$ pykmp-tool -vv get-register --register 1002\nDEBUG:pykmp.client:Request encoded: 803F100103EA4CB70D\nINFO:pykmp.client:Sending GetRegisterRequest...\nDEBUG:pykmp.client:Received bytes on serial: '403F1003EA2F040000030E33B2320D'\nDEBUG:pykmp.codec:Checksum verification OK [raw=3f1003ea2f040000030e33b232, crc_given=b232, crc_calculated=OK]\nDEBUG:pykmp.messages:Decoding register bytes. [raw='03EA2F040000030E33', length_min=6]\nDEBUG:pykmp.messages:Decoded register values: [id=1002, unit=47, value_bytes=040000030E33, remaining bytes=0]\nWARNING:pykmp.tool.__main__:Unknown register ID(s); please report this if you have more information.\nGetRegister response(s):\nDEBUG:pykmp.codec:Decoding parts of floating point data. [data='040000030E33', integer_length=4]\nDEBUG:pykmp.codec:Decoded floating point data: Decimal('200243') [data='040000030E33', man=200243, si=False, se=False, exp=0]\n1002 \u2192 <unknown reg 1002> = 200243 hh:mm:ss\n```\n\nClearly, some registers appear undiscovered and the formatting for some units need some\nlove. \ud83d\ude05\n\nSo far we've only seen GetRegister commands/responses.\nAnother command is 'GetSerialNo':\n\n```\n$ pykmp-tool get-serial\nMeter serial is: 123456\n```\n\nTo do the above programmatically:\n\n```python\nfrom pykmp import GetSerialRequest, PySerialClientCommunicator\n\nmultical = PySerialClientCommunicator(serial_device=\"/dev/ttyUSB0\")\nresponse = multical.send_request(message=GetSerialRequest())\nprint(f\"Meter serial is: {response.serial}\")\n```\n\nAnd for the registers:\n\n```python\nfrom pykmp import (\n REGISTERS,\n UNITS_NAMES,\n FloatCodec,\n GetRegisterRequest,\n PySerialClientCommunicator,\n)\n\nmultical = PySerialClientCommunicator(serial_device=\"/dev/ttyUSB0\")\nresponse = multical.send_request(\n message=GetRegisterRequest(registers=[60, 68, 74, 80, 86, 87, 89, 266])\n)\nfor reg in response.registers.values():\n name, unit = REGISTERS.get(reg.id_, \"?\"), UNITS_NAMES.get(reg.unit, \"?\")\n print(f\"Register {reg.id_} ({name}) data: {FloatCodec.decode(reg.value)} {unit}\")\n```\n\n## Store and graph metrics \ud83d\udcca\n\nThat's not really in scope of this library, but a separate project could (should) use\nthis library.\n\nAnyway, it's planned to build that too!\n`<img src=\"under-construction.gif\">`\n\nIn the meantime, you could try to automate the output in JSON format using\n`pykmp-tool get-register --json [...]`.\n\n## Resources \ud83d\udcda\n\n### KMP Protocol documentation\n\nTechnical description of meters sometimes show a little information of the design and\ngeneric specification of the protocol.\nThis gives some clues about device-specific registers or a graphical explanation of the\nOSI layers.\nHowever, important details are in a separate document which is seemingly only available\nunder NDA. \ud83d\ude22\n\n> **12.3 Data protocol**\n>\n> Utilities and other relevant companies who want to develop their own communication\n> driver for the KMP protocol can order a demonstration program in C# (.net based) as\n> well as a detailed protocol description (in English language).\n\nSome more clues can be found in related communcation interfaces like MODBUS where\nregisters are listed:\n[Modbus/KMP TCP/IP module for MULTICAL\u00ae 603 Data sheet][multical-hu-kmp-modbus-datasheet]\n\nNice people from the MeterLogger project have left [some notes][meterlogger-wiki-kmp]\nfor the development of the MeterLogger for Kamstrup meters.\n\nAccess to the vendor's own software to communicate with the meters ('Metertool HCW') is\nnot available (or at least not for free).\n\n## Troubleshooting\n\n### Unable to run the tool `pykmp-tool: command not found`\n\nUsing a Python package manager (e.g. pip) should ensure the entry point should be\ninstalled somewhere in a directory that's on your PATH, but apparently that failed.\n\nAs an alternative, you can try to substitute `pykmp-tool` with `python -m pykmp.tool`.\n\n### Unable to get a reading (connection timeout)\n\n- Make sure your IR head has an included magnet that activates the meter's IR circuit.\n If in doubt, activate it by pressing any button and try to get a reading while the\n display is active.\n- Make sure the RX/TX is aligned with the meter.\n It's most if not all cases the IR head has to be placed in upside-down position.\n- Try to re-align around the position of the IR eye while keeping a command running in a\n loop in your shell.\n\n## Other notes & TODOs \u270d\ufe0f\n\n### Warning: battery consumption \ud83e\udeab\n\nMost Kamstrup meters for heat are battery-powered.\nUsing the optical/infrared interface will draw extra power from the battery and it may\ndeplete sooner when using this on a regular basis.\n\nExtending the interval of reading should help, as well as requesting all data you need\nin a single request (rather than looping).\n\nReading the battery level is not (yet) possible.\n\nSome (older) models may require periodic re-activation of the IR-circuit.\n\n### Connecting over the network (ser2net)\n\nIt's not always practical to communicate with the meter via (USB-to-)serial.\nUsing [ser2net][ser2net-github] on a (small) device close to the meter you can expose it\non your network.\n\nExample configuration:\n\n```yaml\nconnection: &mykamstrup\n accepter: tcp,2002\n connector: >-\n serialdev,\n /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0,\n 1200n82\n options:\n max-connections: 1\n```\n\nThis above example uses TCP port 2002 on the host.\nA connection can be made from any other host using:\n\n```\n$ pykmp-tool --serial-device socket://hostname:2002 [...]\n```\n\nOr use the environment variable to not having to specify it in every command:\n\n```\n$ export PYKMP_SERIAL_DEVICE=socket://hostname:2002\n```\n\n### Possible reading of higher resolution registers\n\nIn Kamstrup MULTICAL\u00ae 403 Technical description section\n*11.3 Reading high resolution registers.* you'll find:\n\n- E1ExtraDigit (9 digits instead of 8)\n- E1HighRes ('internal' resolution, but truncated to include LSB)\n\nIt mentions kWh/Wh digits in that document, but the registers referred to can be\nconfigured for MWh/GJ too, depending on the B-code (section 7.2). So, it may\nwork for configurations that display in GJ as well.\n\nThe register numbers and encodings aren't specified, though. However, the\nMULTICAL\u00ae 302 Technical description section 13.1.1 mentions E1HighRes is\nregister ID 266 (decimal).\n\n## Thanks to... \ud83d\ude4f\n\nThis project's existence is mainly thanks to all the information and regarding the KMP\nprotocol people have put online over the years.\n\nAs mentioned above, the MeterLogger project have left [some notes][meterlogger-wiki-kmp]\nfor the development of the MeterLogger for Kamstrup meters. Also the work by\nPoul-Henning Kamp (and later Ronald van der Meer) in\n[GitHub: `ronaldvdmeer/multical402-4-domoticz`][github-ronaldvdmeer-multical402]\nwas inspiring to get started with exploring possibilities and testing my hardware.\n\nFinally, also a shoutout to the Dutch community Tweakers where a forum topic pointed out\nthe possibilities integrating these MULTICAL\u00ae meters (as provided by Dutch utilities) to\nnon-cloud smart home.\n[GoT: Kamstrup Multical 402 stadsverwarmingsmeter RPI3+IR-kop][got-multical402-topic]\n\n## License\n\nThe majority of the project is [Apache 2.0][apache-license-2] licensed.\n\nFiles deemed insignificant in terms of copyright such as configuration files are\nlicensed under the public domain \"no rights reserved\" [CC0] license.\n\nThe repository is [REUSE][reuse-home] compliant.\n\nRead more on contributing in [CONTRIBUTING.md][contributing-md].\n\n[ali-e-link-optical-head]: https://www.aliexpress.com/item/1005003509520122.html\n[pip-install-editable]: https://setuptools.pypa.io/en/latest/userguide/development_mode.html\n[multical-hu-kmp-modbus-datasheet]: https://www.multical.hu/upload/files/Modbus_KMP_TCP_IP.pdf\n[ser2net-github]: https://github.com/cminyard/ser2net\n[meterlogger-wiki-kmp]: https://github.com/nabovarme/MeterLogger/wiki/Kamstrup-Protocol\n[github-ronaldvdmeer-multical402]: https://github.com/ronaldvdmeer/multical402-4-domoticz\n[got-multical402-topic]: https://gathering.tweakers.net/forum/list_messages/1776625\n[CC0]: https://creativecommons.org/share-your-work/public-domain/cc0/\n[apache-license-2]: https://www.apache.org/licenses/LICENSE-2.0\n[reuse-home]: https://reuse.software/\n[contributing-md]: ./CONTRIBUTING.md\n",
"bugtrack_url": null,
"license": "Apache License 2.0",
"summary": "Library for the KMP protocol used with Kamstrup electricity/energy meters (e.g. MULTICAL\u00ae 30x/40x/60x).",
"version": "0.0.1",
"project_urls": {
"homepage": "https://github.com/gertvdijk/PyKMP",
"repository": "https://github.com/gertvdijk/PyKMP.git"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "e548c46d9b7db61a42c403b10297bcc4448e23c4056b6ea8ffde1ec28c44ddf4",
"md5": "fda8ef962800172487e8a746ca2bb391",
"sha256": "46bd5763c31fd541a0b997afbd6811538a2c8fd49e9f234455cacf0d5d4e5644"
},
"downloads": -1,
"filename": "PyKMP-0.0.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "fda8ef962800172487e8a746ca2bb391",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 33979,
"upload_time": "2023-09-24T21:34:02",
"upload_time_iso_8601": "2023-09-24T21:34:02.014283Z",
"url": "https://files.pythonhosted.org/packages/e5/48/c46d9b7db61a42c403b10297bcc4448e23c4056b6ea8ffde1ec28c44ddf4/PyKMP-0.0.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "357ba68b8207db0d923846ab8962f2e53c011449c98dd3771929559e9ab2bccf",
"md5": "c7ddff16ec933cfc97c20b3cc41eda80",
"sha256": "aa22b27dc50463305289204e952fbf914c91d8c5e5777e428764664571362882"
},
"downloads": -1,
"filename": "PyKMP-0.0.1.tar.gz",
"has_sig": false,
"md5_digest": "c7ddff16ec933cfc97c20b3cc41eda80",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 52131,
"upload_time": "2023-09-24T21:34:04",
"upload_time_iso_8601": "2023-09-24T21:34:04.036980Z",
"url": "https://files.pythonhosted.org/packages/35/7b/a68b8207db0d923846ab8962f2e53c011449c98dd3771929559e9ab2bccf/PyKMP-0.0.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-09-24 21:34:04",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "gertvdijk",
"github_project": "PyKMP",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"lcname": "pykmp"
}
