add smart-home to the IoT category

[e154]

We want to ensure high quality of the packages. Make sure that you've checked the boxes below before sending a pull request.

• I have read the Contribution Guidelines
• I have read the Maintainers Note
• I have read the Quality Standards

Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• The repo documentation has a pkg.go.dev link.
• The repo documentation has a coverage service link.
• The repo documentation has a goreportcard link.
• The repo has a version-numbered release and a go.mod file.
• The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• Continuous integration is used to attempt to catch issues prior to releasing this package to end-users.

Please provide some links to your package to ease the review

• forge link (github.com, gitlab.com, etc): https://github.com/e154/smart-home
• pkg.go.dev: https://pkg.go.dev/github.com/e154/smart-home
• goreportcard.com: https://goreportcard.com/report/github.com/e154/smart-home
• coverage service link (codecov, coveralls, etc.): https://app.codecov.io/gh/e154/smart-home

Pull Request content

• The package has been added to the list in alphabetical order.
• The package has an appropriate description with correct grammar.
• As far as I know, the package has not been listed here before.

Category quality

Note that new categories can be added only when there are 3 packages or more.

Packages added a long time ago might not meet the current guidelines anymore. It would be very helpful if you could check 3-5 packages above and below your submission to ensure that they also still meet the Quality Standards.

Please delete one of the following lines:

• The packages around my addition still meet the Quality Standards.

Thanks for your PR, you're awesome! 😎

[sourcery-ai]

We have skipped reviewing this pull request. All the files appear to be documentation files, which we're not great at reviewing... yet!

[github-actions]

Thank you for contributing to awesome-go. We will review your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• repo link
• pkg.go.dev
• goreportcard.com
• coverage

Your project is under review. It may take a few days to be approved.

[riccardopinosio]

@e154 I think you're missing the full stop "." at the end of the added line

[e154]

@e154 I think you're missing the full stop "." at the end of the added line

thanks for the note, fixed it

[phanirithvij]

Is it not possible to improve the code coverage or atleast have e2e tests? I can think of having a self-hosted github actions runner and do integration tests (test all features basically) or do you have something similar like a test rig? If so I don't mind the low code coverage.

[e154]

In the application, important parts of the functional code are covered by unit tests and e2e tests in the test directories. I test the rest of the parts locally. I won’t be able to fully cover it with automated tests, because the application is very large and I don’t have enough effort and resources. Hopefully this will improve over time as the app's community of users expands and more helpers appear.