Remove abandoned Salus iT600 repository from HACS defaults

[Jordi-14]

Repository

https://github.com/epoplavskis/homeassistant_salus.git

Checklist

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

Why should this be removed?

Repository to remove

https://github.com/epoplavskis/homeassistant_salus

Why should this be removed?

This repository appears abandoned and is no longer maintained. Users are still discovering and installing it from HACS defaults, then hitting compatibility problems with current Home Assistant / Salus gateway behavior.

Attempts to contact the maintainer and request a deprecation notice have not received a response.

A maintained successor/fork exists here:

https://github.com/Jordi-14/homeassistant_salus
Being maintained by @Jordi-14 and @leonardpitzu

The maintained fork includes current Home Assistant compatibility work and support for newer Salus gateway behavior, including UGE600/UG800 work. It also solves the majority of still open issues in the to-be-removed repo.

Evidence

• Open issues/PRs unanswered: https://github.com/epoplavskis/homeassistant_salus/issues/ Add SQ610 thermostat support improvements epoplavskis/homeassistant_salus#86 Changes in HVAC Action to align with HASS 2025.8.2 epoplavskis/homeassistant_salus#78
• Maintainer contact attempt: Add SQ610 thermostat support improvements epoplavskis/homeassistant_salus#86 (comment)
• Maintained fork release history: https://github.com/Jordi-14/homeassistant_salus/releases

Requested outcome

Please remove epoplavskis/homeassistant_salus from HACS defaults, or advise on the correct replacement/deprecation process so users are not directed to an abandoned integration.

Link to issue

epoplavskis/homeassistant_salus#86 (comment)

[hacs-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

[ludeeus]

CC @epoplavskis