Skip to content

Added a note in the documentation regarding stand-alone mode#367

Open
no-gram wants to merge 2 commits intocustom-components:masterfrom
no-gram:master
Open

Added a note in the documentation regarding stand-alone mode#367
no-gram wants to merge 2 commits intocustom-components:masterfrom
no-gram:master

Conversation

@no-gram
Copy link

@no-gram no-gram commented Feb 26, 2026

Added a note in the documentation regarding stand-alone mode in the section about prevent charging auto start

@steinmn
Copy link
Contributor

steinmn commented Feb 26, 2026

Could you add a bulletpoint about this in the Requirements-section as well? Judging by your description in #366, the integration was pretty much useless as long as the charger was in stand-alone mode, right?

@no-gram
Copy link
Author

no-gram commented Feb 27, 2026

When stand-alone mode is activated the integration works as expected. The charging started immediately and the state was correctly updated in HA. I could turn off the charging through the integration and I was considering this as a workaround now that I could not prevent the auto start. Stand-alone is supported by the integration and as far as I see it, it works as expected. It should not be a requirement that stand-alone mode is turned off.

@steinmn
Copy link
Contributor

steinmn commented Feb 28, 2026

Ok, in that case, I think it belongs as a sub-point under the If you want to use the controls at the Installation level:-point. If the available-current-setting is ignored, it doesn't just impact auto-start, so it should be mentioned among the requirements.

…-alone mode must be disabled to use the controls at the Installation-level. Also updated a dead link for disabling Zaptec Sense.
@no-gram
Copy link
Author

no-gram commented Mar 1, 2026

Agree. See latest commit.

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.

Good catch on the dead link 👍

@sveinse
Copy link
Collaborator

sveinse commented Mar 2, 2026

Not sure what's going on with the unit test CI job. It fails with some strange error.

@steinmn
Copy link
Contributor

steinmn commented Mar 2, 2026

@sveinse The pycares-package released its 5.0-version in january, which contained breaking changes. The old ha-version we currently have in requirements.txt relies on an older aiodns-version that relies on the older pycares-version without having the <5.0-guard in its setup.

TLDR: I've updated requirements.txt in #362 to use HA 2026.2.3, and the tests pass. I suggest merging that and then (rebasing and) merging this PR.

@sveinse
Copy link
Collaborator

sveinse commented Mar 2, 2026

@no-gram can you please merge in master to get #362 included? It seems I can't do this from the web and we should have the CI tasks rerun with the new config.

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.

3 participants