-
Notifications
You must be signed in to change notification settings - Fork 105
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: Compatibility with secrets.yaml #18
Comments
To do that, I think we'd need to parse the |
We no longer require secrets to be stored in the config, as long as you're using the MQTT broker within Home Assistant. Does that solve this need for you? |
The main addon documentation still says that "the absolute minimum that you need to specify in the config file is the MQTT connection and authentication information: Is that not still the case? Additionally, for people using auto discovery and an external MQTT server location, plaintext secrets are still stored in the config. I suppose using manually configured entities and/or using the Mosquito broker within HA would be able to eliminate this issue, but there are still some edge-case scenarios to think about. |
No, it's not, and we should improve that text.
Yes, that's what I was trying to get at - there's no way for us to autodetect those credentials. secrets.yaml would be a nice improvement for those setups, and while I don't expect to prioritize it myself (since I wouldn't use it!) I'm glad to review and test PRs. |
Somewhat related to #8, are you able to add compatibility with the Home Assistant secrets file to avoid having plaintext credentials stored in the config?
The text was updated successfully, but these errors were encountered: