-
Notifications
You must be signed in to change notification settings - Fork 2
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
HACS Install instructions a little off. #1
Comments
Thanks I should probably make this more clear in the README. My initial plan was to publish the repository in HACS but it was such a pain in the ass to get it published there with all the tests and the requirement of having an icon in the HomeAssistant brands repository where I again got rejected because the name could be confused with an official intagration thet does not exist... So I just decided to close all pull requests and maintain the repo myself until HA gets official support for Gotify. |
I'm too stupid to figure it out as well I've installed it, but it looks to me the instructions are saying you can add something like this to yaml files action:
But I keep getting Message malformed: extra keys not allowed @ data['action'] The default UI for the actions doesn't seem to send messages. I know it's not a help thingy here but the instructions do help for newbies like me lol |
What you posted goes into the action part of your automation (or you can configure it via the GUI like any other notification provider). To the YAML file you have to add the code that's under Configuration |
I get the following error, when i sent a message via the automation. |
Just an FYI, Your custom component isn't listed in the default HACS when you search. People need to first add your github URL
In HACS go to integrations and click the 3 dots in the upper right add a new custom repository
Input
https://github.com/1RandomDev/homeassistant-gotify
as the URLSelect
Integration
as the category then click add.Now someone can search for Gotify Notifications and it will show up.
The text was updated successfully, but these errors were encountered: