Document additional TeslaMate configuration changes #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As detailed in #66, the links in the Grafana dashboards don't link to the correct TeslaMate location, and the TeslaMate dashboard links don't link back to the correct Grafana location, unless you set the "Web app" and "Dashboard" settings in TeslaMate.
This PR adds documentation for these values and also adds a little bit of a helper message in the logs to make it easier for people to discover the correct ingress URLs. The helper message is only shown if the "Web app" URL hasn't been set to a value that includes
api/hassio_ingress.I couldn't find a way to reliably determine the HA URL so I'm leaving that as an exercise for the user.
Closes #66