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

Packages configuration seems a little buggy #9864

Closed
VDRainer opened this issue Oct 14, 2017 · 3 comments
Closed

Packages configuration seems a little buggy #9864

VDRainer opened this issue Oct 14, 2017 · 3 comments

Comments

@VDRainer
Copy link
Contributor

VDRainer commented Oct 14, 2017

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.55.0, but see this issue since using packages.

Python release (python3 --version):
3.5.2

Component/platform:
https://home-assistant.io/docs/configuration/packages/

Description of problem:
After making changes in a packages file, you always have to restart HA.
Reload customizing, groups, scripts and automations never works.

Also a strange problem with the name of a subfolder in the packages directory:
https://community.home-assistant.io/t/automation-error-assistance/29533?u=vdrainer

Expected:

Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

@arsaboo
Copy link
Contributor

arsaboo commented Oct 15, 2017

This feature is not implemented and given the focus to move towards GUI, it is not a core focus for the devs currently.

It is not a bug, so please close the issue and add in the Feature Request section in the forums.

@VDRainer
Copy link
Contributor Author

What a shame.
IMO packages are the ONLY way to keep track of your configuration.

@arsaboo
Copy link
Contributor

arsaboo commented Oct 15, 2017

Packages have their own issues and are not very well suited for the GUI editor, which is where we want to be.

@home-assistant home-assistant locked and limited conversation to collaborators Mar 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants