Community-maintained device integrations created with SENTRON Power Device Engineer.
Independent community project. Not an official Siemens repository or product. Provided as is, without warranty, to the extent permitted by law. See the MIT License and project disclaimer.
Deutsch · Browse integrations · Contribute · Request an integration
This repository collects redistributable, community-authored JSON device integrations, their compatibility information and documented test results. The intended product environment includes SENTRON Powermanager and Powercenter 3000. Compatibility must be established for each integration and software version; it is not implied by being listed here. Siemens software, firmware and proprietary device libraries are not included.
The collection starts empty. Templates are examples for contributors, not working device integrations or validated register maps.
- Browse
integrations/<manufacturer>/<model>/<version>/. - Read that version's
README.mdandmetadata.json: check the exact model, firmware, target product/version, test status and possible write operations. - Download the files listed in
exportsin the metadata. The repository'smetadata.jsonis a catalog record and must not be imported into Siemens software. - Follow the import procedure for your exact target software version. Back up configuration first and validate measurements against a reference before use.
Do not edit an exported file merely to satisfy a presumed Siemens schema. This repository does not define that schema. Older files may require reopening and resaving with a compatible Power Device Engineer version; consult Siemens guidance.
- Ready integration: fork the repository, add a versioned device folder and open a pull request. Step-by-step guide.
- Contribution without Git experience: open Submit an integration from the issue chooser. A maintainer can help prepare the pull request.
- Missing device: open Request a device integration. Supply the exact model and a link to publicly available protocol/register documentation.
- Problem: open Report an integration issue with versions and expected/actual behavior.
Anyone may propose a contribution. Maintainers decide which pull requests to merge. Public access does not give contributors write access to this repository. Requests do not create an obligation or deadline to deliver an integration.
| Status | Meaning |
|---|---|
untested |
No successful target import is documented. |
import-tested |
Import succeeded in the stated target version; device behavior is unverified. |
device-tested |
Import and the documented checks against a real device succeeded. |
device-tested is a contributor's documented result for a specific setup, not a
manufacturer certification, universal compatibility claim or safety approval.
CI checks metadata, paths and JSON syntax only. It cannot verify device behavior,
the absence of confidential data, or publication rights.
| Path | Purpose |
|---|---|
integrations/ |
Versioned device exports and documentation |
templates/integration/ |
Documentation and metadata template; no real export |
CONTRIBUTING.md |
Submission, review and rights requirements |
DISCLAIMER.md, LICENSE |
Project notice, liability limits and license |
SECURITY.md |
Private reporting of security-sensitive issues |
docs/SETUP.de.md |
Repository setup and branch protection for maintainers |
scripts/validate.py |
Dependency-free structural validation |
Run locally with Python 3.10 or newer:
python3 scripts/validate.py
python3 -m unittest discover -s testsPublish only content you may distribute under MIT, including any required employer permission. Exporting from a tool is not proof of permission to redistribute its embedded content. Keep third-party notices intact. Link to manufacturer manuals instead of uploading copies without permission.