Releases: RobertD502/home-assistant-flair
0.0.5.9
Changes
- Bumped
hass-flair-helper
to0.2.0
0.0.5.8
Changes
- Bumped
hass-flair-helper
to0.1.9
: Uses forked version of Flair's API wrapper which utilizes arequests Session object
to reuse the same TCP connection to Flair's servers instead of establishing a new connection for every request.
Acknowledgments
Thanks @fcfort for bringing the Session object to my attention!
0.0.5.7
Changes
Climate Entities
: code changed to useHVACAction
andHVACEnum
to replace HVAC_MODE_* and CURRENT_HVAC_* constants which are deprecated as of 2022.5.0
0.0.5.6
Changes
1. Bumped hass-flair-helper
library to 0.1.8:
-
Uses single client session for all Flair API endpoints. This has cut down the integration setup time in half.
-
Current plan, within the next month or so, is to write a new backend library which will be asynchronous and wrap Flair's API itself without relying on Flair's API python wrapper.
Note
- The new library WILL REQUIRE OAUTH2 CREDENTIALS. If you don't already have OAuth2 credentials, be sure to get them
before this library change is made.
2. Code changes made to reflect deprecations introduced in 2022.5.0
0.0.5.5
Breaking Changes
-
Vents are no longer represented as
Fan
Entities - Vents are now represented asCover
Entities with the appropriatedamper
device class - thanks @arifeinberg
- Note: Although cover entities support a
tilt position
between 0 to 100, Flair vents only support a tilt position of0, 50, or 100
. Usage of a tilt position other than 0, 50, or 100 will be interpreted as 50!
Other Changes
- Bumped hass-flair-helper to 0.1.2 - Fixes onboarding issue for users with IR devices that don't have an
ON
key within HVAC mode
0.0.5.1
Bumped helper library to 0.1.1
Fixes issue of phantom (previously deleted from within the Flair App) HVAC units raising exceptions
0.0.5.0
This release is a major rewrite of the Flair integration. With this being the case, there are breaking changes. I encourage you to check any automations that you may have and to read the documentation.
Notable Changes
- Mini Splits are now supported
- Pucks, Mini Splits, Rooms, Structures, and Vents are now integrated as
Devices
with entities within each device. - Attributes are no longer used. The previous attributes are now presented as separate entities.
- Additional control has been added to Structures
Set Sechedule
service is no longer used. Instead, schedules are picked using a select entity within a Flair Structure.
Documentation Below
Devices
Each Flair mini-split, puck, room, structure, and vent is represented as a device in Home Assistant. Within each device
are several entities described below.
Structure
Each structure has the following entities:
Entity | Entity Type | Additional Comments |
---|---|---|
Home/Away Mode |
Select |
Please read Flair's documentation regarding Home/Away Mode |
Schedules |
Select |
Schedules and this entity are only available if the Flair System Mode is set to "Auto". All schedules created within the Flair app will appear here. To turn off a schedule, select "No Schedule" |
Structure Mode |
Select |
Please read Flair's documentation regarding Structure mode |
System Mode |
Select |
Please read Flair's documentation regarding Auto mode and Manual mode |
Puck
Each puck has the following entities:
Entity | Entity Type | Additional Comments |
---|---|---|
Humidity |
Sensor |
|
Light Level |
Sensor |
|
Temperature |
Sensor |
|
RSSI |
Sensor |
|
Voltage |
Sensor |
Displays the current voltage of the puck. If using batteries to power your puck, this can be used to monitor battery health. |
Note About Pucks
Flair statement regarding Puck Light Level sensor:
It is not calibrated. The sensor itself, if the nominal reference is 1, can range from 0.3 to 1.6. This also doesn't take into account the mechanical loss in the Puck. In short, this is not an accurate lux sensor.
Vent
In order to control vents that are in Flair Rooms that have a temperature sensor, the System setting in the Flair app needs to be set to Manual
(see image above). If you have it set to Auto
, you will still be able to control your vents, however, eventually Flair will override your changes. This mode can also be set using a Flair Structure's System Mode select entity
within Home Assistant. Any vents in Flair Rooms that don't report temperature can be controlled regardless of current mode set.
Each Vent has the following entities:
Entity | Entity Type | Additional Comments |
---|---|---|
Vent |
Fan |
Has a state of either on or off . If your vent is either 50 or 100 percent open, the state will be on . If your vent is 0 percent open, the state will be off . Turning the vent fan entity on manually will fully open the vent (100 percent). Turning the vent fan entity off manually will completely close the vent (0 percent). You are also able to manually open the vent halfway (50 percent) by either changing the speed to 50 via the UI or by using the service fan.set_percentage and setting percentage to 50 - the same goes for fully open with 100 or fully closed with 0 . |
Duct Pressure |
Sensor |
|
Duct Temperature |
Sensor |
|
RSSI |
Sensor |
|
Voltage |
Sensor |
Displays the current voltage of the vent. If using batteries to power your vent, this can be used to monitor battery health. |
Room
Each Room has the following entities:
Entity | Entity Type | Additional Comments |
---|---|---|
Activity Status |
Select |
Rooms can be set to Active or Inactive. |
Room |
Climate |
Temperature set points can be changed on a room by room basis. Changing HVAC mode on a room by room basis is not supported as room HVAC mode (for all rooms) is controlled by a Flair structure. Changing HVAC mode for all rooms can be done using a structure's Structure Mode entity. |
Duct Temperature |
Sensor |
|
RSSI |
Sensor |
|
Voltage |
Sensor |
Displays the current voltage of the vent. If using batteries to power your vent, this can be used to monitor battery health. |
Additional Notes
Changing the temperature for a room climate entity will change the set temperature of the corresponding room. This change will remain for until next scheduled event
, 3h
, 8h
, 24h
, or forever
- this depends on the setting in the Flair app under Home Settings > System Settings > Default Hold Duration.
Mini Split
Each Mini Split has the following entities:
Entity | Entity Type | Additional Comments |
---|---|---|
Mini Split |
Climate |
To fully control your mini split unit, the associated Flair structure needs to be in Manual Mode . If your structure is set to Auto Mode you will only be able to control Fan speed and Swing (if available for your unit). In addition, mini split set points are controlled by rooms if a Flair structure is set to Auto Mode . Changing the temperature of this climate entity will result in changing the room set point when in Auto Mode . |
0.0.4.6
Important!!!!!
Only update to this release if you are currently running one of the Home Assistant 2021.12 betas or wait until 2021.12 is released
Changes:
- Update code to use new device_class introduced in 2021.12
- Update code to use extra_state_attributes instead of device_state_attributes (fixes log warnings in 2021.12)
0.0.4.5
Important!!!!!
Only update to this release if you are currently running one of the Home Assistant 2021.12 betas or wait until 2021.12 is released
Changes:
- Update code to use new device_class introduced in 2021.12
0.0.4.4
Updated hass-flair-helper to version 0.0.9
Changes in 0.0.4.4:
This update addresses phantom structures and rooms preventing users from installing the integration
- If you already have the Flair integration set up, this does not apply to you!
- Setting up Flair structures and deleting them (within the Flair App) can sometimes result in rooms within those deleted structures remaining associated with your account.
- Phantom structures and rooms prevent the Flair Home Assistant integration from setting up as Flair's API attempts to get information about rooms associated with phantom structures that are no longer linked to a user's account
0.0.4.4
now checks and gathers information only about rooms that are associated with structures linked to a user's account