Please keep Harmony switch entity - it's the only one that works properly with Siri voice

[ballakers]

Switch entity is the only thing that works properly with Siri voice commands - why do we have to get rid of it. Using select turns on last activity selected which is always "TV off" so the TV remains off when you ask Siri to turn it on. The remote entity also doesn't;t work properly. Can we just keep the switch entity for harmony as it's the only one that actually works, also it says deprecated since June release but it actually still works on my 6.2 release. I understand changing things for the better but this isn;t for the better and the reference to Google home having issues should also have Siri grouped into it.
Below message copied from past post that is locked:

          I'll go ahead and merge this now:

• There's no need for the harmony integration to have three ways of selecting an activity. Given that the state of a remote entity is on/off and not the current activity, it's however motivated to expose the activity also as a set of switches or as a select entity.
• The harmony switch platform was added before the select entity existed. If the select entity already existed, we would not have allowed selecting an activity via a set of switches.
• If Google Assistant has problems interacting with select entities, that's not something we should work around in the harmony integration.

Originally posted by @emontnemery in #92787 (comment)

[joostlek]

It has been removed now

[joostlek]

You can use template entities to do the same thing again

[ballakers]

It has been removed now

Is it only removed for when you create a new Harmony integration? Because my switches are still present and working fine - just the dumb warning keeps popping up. I'll check out the templates but seems silly to make more work for something that was simple and working fine. What was the reason for removing? aside from saying there were three ways to control something

[joostlek]

It will be removed from 2024.7.

The reason is literally that there are 3 ways to control it. Why do we need so many? Use the right tool for the job and don't overdo things

[joostlek]

Closing this as this isn't a bug but rather a feature request