-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Renaming this integration #62
Comments
If I recall correctly, HA will prioritize an internal integration over a HACS integration with the same name. Renaming this integration will ensure existing users can choose which integration they want to use, but it's not blocking to add the luxtronic core integration. |
Okay, good to know. |
As I mentioned in @BenPru 's PR home-assistant/core#59788 (comment) I'll happily rename this integration in favor of his if it gets merged into core to avoid misunderstandings. Maybe we should try to name it luxtronik2 instead of luxtronik because I have a request of someone if I could help create an integration for a Luxtronik1 controller. The underlying protocoll is completely different from the one used by luxtronik2 controllers so supporting both in one integration is pointless in my eyes ... Let me know what you think! |
This conflicts with my current integration. 😵💫 In the normal case I use Long talking, short message: |
I am currently trying to process and provide my further development of this integration as a ha core integration.
We had already discussed renaming this integration in the past.
Do you still want to tackle this? luxtronik_legacy or similar?
The text was updated successfully, but these errors were encountered: