Repo inquery

[krbaker]

Keith, I sent you an email (the email address in your profile on here) when you invited me to take this repo over, and never heard back. So I don't really want to take this repo over because I don't think it's wise that I put my fixes/updates here, and when it gets pushed out to peoples system via HACS, it blows up their system because they didn't pay attention to the release notes telling them it was going to change a bunch of stuff. So why not send people my way, you can then retire this repo, and yourself, and not work on code you don't even use, unless you want. PS My version already fixes the multi-pvs issues.

Originally posted by @smcneece in #120 (comment)

[krbaker]

This actually goes to the comment I made on the PR. While I don't have a lot of time to manage this, I think its not great for the users to be forced into that sort of choice of forks - unless you want them all pointed your way, in which case same problem (but happy to do so)? (i can't even count the number of Enphase integrations there are, I'd rather avoid this).

[smcneece]

Why not just send people over? To get my version going they are going to have to read the fine print, only it's in bold text, there is no going back without a backup, but it's a nice path forward. I've added some awesome features if I do say so myself. With a few more beta testers, especially battery users, I would be super confident in my version for everyone.

Your version could just stay in its current state by archiving it (can be reversed), If people really want it, it's still here, and they wont break any automations, dashboards, etc. like my version with the updated/fixed binary sensors would. This change alone that I did pretty much means there has to be two repo's, the internet is full of people who didn't read the release notes, and broke something, hell I'm guilty of it as well.

You could put in the top of your repo README.md that you've archived it,, and no patches will be done by you. This includes future HA changes that would require code updates. Just like staying on Windows 10, people can, but they're not going to get support. You still maintain control of your repo, because it was your hard work that you put into it. And you get to see it grow and you don't have any headaches of fixing issues, unless you want to help over on my repo.

You could even merge this latest fix that XD-Builder did to fix the multi PVS support, and in that release note something along the lines that it would likely be the last one, and a link to my repo.