Please remove mcaonline/nanoleaf-essentials-hass since not mainted / deprecated

[mcaonline]

Repository

mcaonline/nanoleaf-essentials-hass

Checklist

• [x] I understand that this form should only be used for repositories that needs to be removed from HACS
• [x] I understand that a bug is not reason enough to have a repository removed
• [x] The repository is currently shipped as a default repository in HACS
• [x] I have tried to get the authors attention to the reason for removal

Why should this be removed?

I am the author of this repository. I will it archive it and it will be no longer maintained. Please remove it from the default HACS list. Project deprecated and archived, please remove from default HACS repository. Thank you!

Link to issue

https://github.com/mcaonline/nanoleaf-essentials-hass

[hacs-bot[bot]]

Thank you for opening an issue in the HACS.

Before proceeding, please verify the following:

Select the correct issue template: HACS provides different templates for different types of bugs. Choosing the right template ensures you're asked the right questions and helps route your bug appropriately.

Complete the ENTIRE issue template: Make sure you've read the issue guidelines and filled out every single field in the issue template, even if some fields seem unrelated to your specific situation.

Fill out everything, even if it seems unnecessary: Don't skip fields because they "don't seem relevant" to your bug. The template asks for specific information because:

• Problems often have unexpected causes that surface through "unrelated" details
• What seems unrelated to you might be the key to solving your bug
• Incomplete information requires follow-up questions, delaying resolution
• The template is designed based on years of troubleshooting experience
• Missing information forces those helping to make assumptions, which can lead to wrong solutions

Issues with incomplete templates take significantly longer to resolve or may be closed without resolution.

If you're experiencing a similar bug: If your bug is identical to an existing one, please:

• Add a 👍 reaction to the original issue description
• Subscribe to notifications on that issue to stay updated
• Do not add comments like "same here", "I have this too", or "+1"

Adding duplicate comments creates noise and makes it harder to track and resolve issues. Reactions help prioritize issues based on how many users are affected.

Getting help: If you need assistance filling out the template or understanding your issue:

• Issue Guidelines - Detailed instructions for reporting issues
• HACS Discord - Community support and real-time help

What happens next: Maintainers and community members will review your issue and may:

• Ask for additional information if the template is incomplete
• Provide a solution or workaround
• Label the issue appropriately for tracking
• Link it to related issues or pull requests