Adds new integration [muppet3000/homeassistant-growatt_server_api] #1660
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
hacs-bot
bot
changed the title
|
Running checks on muppet3000/homeassistant-growatt_server_api |
|
https://hacs.xyz/docs/publish/include
|
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.
Link to successful HACS action: https://github.com/muppet3000/homeassistant-growatt_server_api/actions/runs/3859655263/jobs/6584063052
Link to successful hassfest action (if integration): https://github.com/muppet3000/homeassistant-growatt_server_api/actions/runs/3859655263/jobs/6584062992
Addition of growatt_server_api integration: https://github.com/muppet3000/homeassistant-growatt_server_api
See README for more info.
This intention of this repo is for it to be an upstream repo for the core integration here: https://www.home-assistant.io/integrations/growatt_server/ (documentation update to follow) so that changes/fixes/issues can be addressed in a quick/beta manner before being rolled up into a monthly PR to the Core repository.
I believe I've followed all of the requests and expectations laid out in the documentation for this repo, please let me know if there are any issues.