Skip to content

Move Zaptec API functionality to separate zaptec/ directory.#308

Merged
sveinse merged 1 commit intocustom-components:masterfrom
sveinse:feature-move-api-to-zaptec
Aug 28, 2025
Merged

Move Zaptec API functionality to separate zaptec/ directory.#308
sveinse merged 1 commit intocustom-components:masterfrom
sveinse:feature-move-api-to-zaptec

Conversation

@sveinse
Copy link
Collaborator

@sveinse sveinse commented Aug 28, 2025

This is done to split the responsibility between the API facing parts and the HA facing parts.

There is no functional change in this PR, just moving around and fixing the imports. I plan to make subsequent PRs for improving and cleaning up the separation between the API facing parts and the HA facing parts.

Fixes #306

This is done to split the responsibility between the API facing parts and the HA facing parts.
Copy link
Contributor

@steinmn steinmn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sveinse sveinse merged commit 473437c into custom-components:master Aug 28, 2025
4 checks passed
@sveinse sveinse deleted the feature-move-api-to-zaptec branch August 28, 2025 18:11
@sveinse sveinse added this to the v0.8.3 milestone Aug 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move api.py into zaptec/ to separate HA integration from API

2 participants