Added a note in the documentation regarding stand-alone mode#367
Added a note in the documentation regarding stand-alone mode#367no-gram wants to merge 2 commits intocustom-components:masterfrom
Conversation
…ection about prevent charging auto start
|
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? |
|
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. |
|
Ok, in that case, I think it belongs as a sub-point under the |
…-alone mode must be disabled to use the controls at the Installation-level. Also updated a dead link for disabling Zaptec Sense.
|
Agree. See latest commit. |
steinmn
left a comment
There was a problem hiding this comment.
Good catch on the dead link 👍
|
Not sure what's going on with the unit test CI job. It fails with some strange error. |
|
@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. |
Added a note in the documentation regarding stand-alone mode in the section about prevent charging auto start