Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Reload from cloud on failure or on demand #166

Open
davethetallguy opened this issue Sep 18, 2024 · 0 comments
Open

Feature Request: Reload from cloud on failure or on demand #166

davethetallguy opened this issue Sep 18, 2024 · 0 comments

Comments

@davethetallguy
Copy link

I normally operate my system with prefer_cache = true.

Twice in the last few months, I've made a change in a Kumo level system parameter (using my MHK controller) and the hass-kumo integration has subsequently stopped working.

By going into the core configuration, I edited (via VIM) "prefer_cache": from true to false, saved the file, rebooted home assistant, and the integration reloaded and immediately connected successfully. I couldn't find any other way to change this preference than editing the core file.

While this works, it might be nice to either have a default timeout on "unavailable" status (1 hour?) or even a selection to "use kumo cloud on next boot" in order to force this without diving into a config file that isn't normally intended for meat-sacks to be editing directly.

Thanks as always for a solid integration.

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

No branches or pull requests

1 participant