Unified climate entity per room

[snazzybean]

Description

Replace the current scattered per-room entities (sensors, switches, override climate entity) with a single, full climate entity per room. This is the HA-native way to represent climate control and was suggested by @c2who in #91.

Current state (per room)

• sensor.roommind_{area}_target_temp
• sensor.roommind_{area}_mode
• climate.roommind_{area}_override
• switch.roommind_{area}_climate_control

Proposed

One climate.roommind_{area} entity that covers everything:

Climate feature	Maps to
HVAC mode (heat/cool/heat_cool/off)	Room mode + enable/disable (replaces switch.*_climate_control)
Presets (eco/boost/comfort)	Override mechanism (replaces climate.*_override)
Target temperature slider	Direct target temp control (replaces sensor.*_target_temp)
hvac_action (heating/cooling/idle)	Current state (replaces sensor.*_mode)

Benefits

• One entity instead of four per room
• Works natively with HA dashboards, automations, voice assistants (Google Home, Alexa)
• Standard HA UX. No RoomMind-specific entity knowledge needed.

Considerations

• Breaking change for users with automations targeting current entities. Needs migration path or transition period.
• RoomMind's target resolution (override > vacation > presence > schedule > comfort/eco) must map cleanly to the climate entity model.
• The existing climate.*_override entity can serve as the starting point and be expanded.

References

• Toggle control for each room individually #91 (original discussion by @c2who)

[hecktech27]

might be a good chance to add support for #83 ;)