Skip to content

v1.7.6

Choose a tag to compare

@snazzybean snazzybean released this 23 Aug 19:57

This one is mostly about seeing what RoomMind is up to. The analytics chart can draw the setpoint sent to each device, rooms sharing an outdoor compressor now say when protection is holding them back, and a room will learn from an air conditioner even when you are the one running it.

What's New

  • Device target on the analytics chart: The analytics chart can now plot the temperature setpoint RoomMind sends to your TRVs and air conditioners over time, hidden by default and toggleable from the chart legend (#375, thanks @Psykar).
  • Compressor protection status: Rooms that share an outdoor compressor now show a badge when short-cycle protection is holding them idle or keeping them running, with an info tooltip explaining why (#386, thanks @florianmulatz).

Bug Fixes

  • Disappearing room entities: Fixed a room's override, target, mode and control entities being removed when another room's name starts with the same words (for example "Kid 1" and "Kid 1 Room") (#340).
  • Learning from manually run devices: When a room's climate control is disabled and you run an air conditioner or heat pump yourself, RoomMind now recognizes heating and cooling for its statistics and learning, including devices in combined heat/cool (auto) mode (#332).
  • Device setpoint display in mixed rooms: Fixed the "Device set to X°" value showing a misleading number in rooms that combine a direct-mode air conditioner with a proportional TRV; it now reflects the actual target sent to the device (#385, thanks @florianmulatz).
  • "Turn off devices" ignored by air conditioners: When "Action when schedule is off" (or the presence equivalent) is set to Turn off devices, devices are now really turned off instead of falling back to their own When idle setting, which could leave an air conditioner circulating air in fan-only mode. Thermostats set to Low keep that behavior, since they stop responding to commands after being turned off (#368, thanks @LupaioliS).
  • Schedules in the wrong timezone: Fixed schedule periods being evaluated in the server's timezone instead of your Home Assistant timezone, which could leave rooms heating to comfort overnight or backing off during the day for anyone not on UTC (#318, thanks @Psykar).
  • Stuck presence entities: Presence entities that were deleted from Home Assistant now still appear in a room's presence editor with a warning marker, so you can uncheck them and clear them from the room (#397).

Note: After updating, restart Home Assistant and clear your browser cache (Ctrl+Shift+R / Cmd+Shift+R) to ensure the new frontend is loaded.

See the v1.7.5 release notes for earlier changes.

ko-fi