Hello,
I’m developing a Python library for communicating with LCN installations through the native protocol rather than PCK, primarily to support Home Assistant.
It provides module discovery, status monitoring and everyday control of lights, relays, shutters and sensors. Neither the library nor the integration programs the installation—configuration remains in LCN-PRO. Valid PCHK and LCN-PRO licenses are still required; the project does not replace or bypass licensing and valid ones are still required for both PCHK and LCN-PRO.
The work uses public documentation and analysis of communication within my own installation. With modern tools, including AI, this kind of analysis is increasingly accessible to individual enthusiasts. It seems likely that independent implementations will emerge sooner or later, so I would prefer to approach this openly and constructively.
The relevant EU framework includes:
- Article 5(3), allowing lawful users to observe, study or test software during permitted use to understand its underlying ideas and principles.
- Article 6, allowing necessary decompilation for interoperability under specific conditions, including where the required information is not readily available, with limits on its use and disclosure.
These provisions are contained in Directive 2009/24/EC (https://eur-lex.europa.eu/legal-content/...32009L0024); I recognise that their conditions and applicable national law must be respected.
Before publishing, I’d welcome Issendorff’s perspective and any interoperability documentation or guidelines you could share. My goal is to complement the LCN ecosystem and make integration with other systems easier.
Kind regads,
K.M.
I’m developing a Python library for communicating with LCN installations through the native protocol rather than PCK, primarily to support Home Assistant.
It provides module discovery, status monitoring and everyday control of lights, relays, shutters and sensors. Neither the library nor the integration programs the installation—configuration remains in LCN-PRO. Valid PCHK and LCN-PRO licenses are still required; the project does not replace or bypass licensing and valid ones are still required for both PCHK and LCN-PRO.
The work uses public documentation and analysis of communication within my own installation. With modern tools, including AI, this kind of analysis is increasingly accessible to individual enthusiasts. It seems likely that independent implementations will emerge sooner or later, so I would prefer to approach this openly and constructively.
The relevant EU framework includes:
- Article 5(3), allowing lawful users to observe, study or test software during permitted use to understand its underlying ideas and principles.
- Article 6, allowing necessary decompilation for interoperability under specific conditions, including where the required information is not readily available, with limits on its use and disclosure.
These provisions are contained in Directive 2009/24/EC (https://eur-lex.europa.eu/legal-content/...32009L0024); I recognise that their conditions and applicable national law must be respected.
Before publishing, I’d welcome Issendorff’s perspective and any interoperability documentation or guidelines you could share. My goal is to complement the LCN ecosystem and make integration with other systems easier.
Kind regads,
K.M.