I shared this project simply as a working solution for other WH1080 users who might find it useful.
If the discussion is going to focus mainly on terminology, documentation details, or how the project was developed rather than on testing or improving the actual solution, I don’t think there is much more for me to add.
I’m happy to discuss technical issues that help improve the project, but I’d rather not turn a shared solution into an argument.
The term Add-on has been deprecated quite a while back and new software should now all refer to them as an App.
That said you also have to test and change things like install instructions here and in your Git so users will be able to use your stuff. This will not work, for instance:
Also if you used an AI to write some of this code for you, you should really credit it and any other contributions.
Hi Walter, don’t be so easily offended!
I would think that sharing a project is meant as a way to inspire others and not only to show off.
By using the right terminology and making sure that your installation instructions do work, you make it easier on yourself so you (or anybody else) don’t have to help in case the installation doesn’t go as planned.
That addition about AI is about just sharing how this came to life.
I understand your point, and I have no problem with constructive feedback or corrections.
What I wanted to clarify is that I didn’t share the project to show off or to “brag”. I shared it because I had this problem myself, couldn’t find a simple solution, and ended up developing and testing one that worked for me.
Once I had it working, I thought it might be useful to other people with the same WH1080/Home Assistant problem, so I shared it.
That’s really all there was behind the post. There was no intention to show off or claim that the project was perfect.
I didn’t imply that you did this to show off and since your intention was to share it with other people, why not adjust your write-up so it becomes fool proof?