As described in #361 we are on borrowed time in this github organization (custom-components) and repo (zaptec). We have no admin that can help out and none other than me (that's active at least) can release anything and we can't invite new members.
I've started an experiment to set us up as a separate organization:
https://github.com/ha-zaptec-community
This repo have been forked into
https://github.com/ha-zaptec-community/ha-zaptec
In addition, the Zaptec API parts have been split out into a separate access library (which is how HA wants it, see #257):
https://github.com/ha-zaptec-community/pyzaptec
This have been released on PyPi https://pypi.org/project/pyzaptec/ as this was needed to get the CI up and running. The Zaptec integration here use the new pyzaptec library. The devcontainer have been updated and modernized and is working. With a small step (which currently is undocumented see DEVELOPMENT.md) its easy to set up the dev container to edit both pyzaptec and ha-zaptec, so it is easy to use simultaneously.
Now what?
Right now the project is in sync with this repo as it is today (2026-07-26) and it is planned to be kept in sync with master. If I were to attempt to wing a timeline, I'd say that the upcoming 0.8.8 should be the last release from this repo, while we migrate to the new setup in 0.9.0. We'll need to keep both alive for some time and maybe overlap releases. There are details to be decided later.
I'd like your feedback, opinions and comments about this initiative, please.
Naming
So why ha-zaptec-community, pyzaptec and ha-zaptec? Essentially its to be very clear that we are not an official organization and library made by the Zaptec company and that we're an open source community. Using explicit names show clearly what this is and hopefully what it is not. Using the bare zaptec name I think is not a good choice. None of these names are locked in stone and they can all be changed.
As described in #361 we are on borrowed time in this github organization (custom-components) and repo (zaptec). We have no admin that can help out and none other than me (that's active at least) can release anything and we can't invite new members.
I've started an experiment to set us up as a separate organization:
This repo have been forked into
In addition, the Zaptec API parts have been split out into a separate access library (which is how HA wants it, see #257):
This have been released on PyPi https://pypi.org/project/pyzaptec/ as this was needed to get the CI up and running. The Zaptec integration here use the new pyzaptec library. The devcontainer have been updated and modernized and is working. With a small step (
which currently is undocumentedseeDEVELOPMENT.md) its easy to set up the dev container to edit bothpyzaptecandha-zaptec, so it is easy to use simultaneously.Now what?
Right now the project is in sync with this repo as it is today (2026-07-26) and it is planned to be kept in sync with master. If I were to attempt to wing a timeline, I'd say that the upcoming
0.8.8should be the last release from this repo, while we migrate to the new setup in0.9.0. We'll need to keep both alive for some time and maybe overlap releases. There are details to be decided later.I'd like your feedback, opinions and comments about this initiative, please.
Naming
So why
ha-zaptec-community,pyzaptecandha-zaptec? Essentially its to be very clear that we are not an official organization and library made by the Zaptec company and that we're an open source community. Using explicit names show clearly what this is and hopefully what it is not. Using the barezaptecname I think is not a good choice. None of these names are locked in stone and they can all be changed.