Home Assistant Integration
Answered
Are there any users running Home Assistant for home automation? I'm starting work on a plug-in to be able to bring the data from the Flair sensors into HA. It would be great to have another user to compare data or eventually run test versions of the client with.I'd also like to get ideas of what features would be expected so I can build the support in as I start.
-
Hey Steve Stratoti I am curious... Have you published your Flair custom node red flows somewhere? I am looking into building something like this too but would hate starting from scratch when other have most probably gone through that already. I did not find it in your github.
Waiting for my new Oauth2 credentials to update to Robert Drinovac latest beta!
If anyone's looking to do the same, this is flair's form to request your OAuth2 own credentials: https://forms.gle/
VohiQjWNv9CAP2ASA Thanks.
-
Received my OAuth2 credentials yesterday afternoon, re-setup Robert Drinovac HA Flair integration from OAuth 1 to 2 at night... Works like a charm! Amazing work!
-
Here is my Node-Red Flow for controlling a single vent. What I did was recreate how Flair handles opening and closing vents based on the hysteresis concept. You can find a link to the Node-Red code below the image followed by an explanation.
Flow Explained:
1. "Flair HVAC Mode" - Every 30 seconds the state of a climate entity gets polled and sent to the function node. In my case, I have ecobee sensors so I am using a climate entity for a Flair room via the Flair HA integration - I essentially use the Room setpoint from a Flair room on my account that has a supported temp sensor. However, you can use whatever climate entity you want such as your thermostat.
2. "function" - This node essentially sets the HVAC mode and temp of the climate entity as flows so they can be retrieved later by other nodes. It does this for the state (HVAC mode), upper temperature (I take the set point temp set on the climate entity and then add 1 Fahrenheit to it), and lower temp (I take the set point temp set on the climate entity and then subtract 1 Fahrenheit from it).
3. "Upstairs Bathroom Temp" - This node just polls a temp sensor that is located in the room where the vent is. In my case this is a zigbee sensor that Flair doesn't support, but I want to use to determine if the vent needs to be open or closed. You will replace this entity with whatever temp sensor you will be using.
4. "Lower & Upper Temp" - This node takes the temp from the temp sensor and compares it to the lowertemp and uppertemp flows that we set in the "function" node. Depending on which option it satisfies, the flow will continue on that path.
I'll go through the lowertemp path as once you know one path, the other is self explanatory.
So, let's say our climate entity has a current state of cool and and a set point of 73. In that case, the uppertemp will be 74 and the lowertemp will be 72. Now, let's say that our temp sensor is reading 71.5F. In that case, the temp sensor reading is less than or equal to the lowertemp and the flow will continue upwards towards the "Current Mode" node.
The "Current Mode" node checks to see what state (HVAC mode) your climate entity is in based on the flow.currentmode that we set in the function node. Since, in this example, we are in cool, it will go up towards the "Vent Open?" node. If the vent is open, we have a set point of 73, and our temp sensor reading is 71.5, then we know we need to close the vent. Since that condition is satisfied, we make a service call to close the vent. The red nodes that you see check if there were any errors when trying to execute service calls (there is one for every service call in the flow). If, for example, the flow tried to close the vent, but Home Assistant threw an error, it would activate the associated red node, after which a 30 second timer is started. Once the 30 seconds have elapsed, it will retry the service call and sends me a notification to my phone letting me know the vent failed to close. The red node would get reactivated again followed by a 30 second timer if the second service call were to also fail.....so, if I continue to get notified on my phone, I know that I need to check and see what kind of a problem occurred. However, if I stop getting notifications, then I know the service call went through and there is nothing for me to look into.
Going back to the "Current Mode" node: If the climate entity was actually in heating mode, then I know that the vent should be opened when the temp sensor reading is at or below the set point - 1F. So, if we were in heat mode, I actually check to see if the vent is closed. If it is, send a service call to open the vent.
Note: I have yet to have a single service call fail for the vent, but I like to have the catch nodes (red nodes) just in case. I have some SOMA smart blinds that love taking ~2-3 service calls before one successfully goes through, which is when I started incorporating catch nodes into my flows.
Hope this Node-Red example helps!
-
I set up the integration, and its working great. Lots of info in HA about each vents, more than I would have expected but thats the beauty of HA, something I might not care about might mean a whole lot to someone else.
Great job on creating this. The timing on you delivery was perfect for me. I installed my vents like 2 days before your release.
Thanks for contributing to the community.
-
Glad HA is already supported, even if by a 3rd party, I submitted my auth request, can't wait to try it out.
Support sent me a cool graph of signal strength over time (troubleshooting a vent that often disconnects), that I did not see in the stats UI menu (that only shows temps), is RSSI included in HA/MQTT integration?
-
The HA integration does include RSSI. All features included/notes about them as well as instructions can be found at https://github.com/RobertD502/home-assistant-flair
-
Hello, I’m a recent HA user but have been learning fast, I’m a controls engineer by day. I’ve been using flair for a while to control a mini split.
I stumbled upon this thread and all of the fantastic work/effort that’s taken place. I created a login to post/contribute to this.
I reached out for API access and will attempt the HACS integration.
Will report back after I install and great work!
*Update* I received my OAuth2 credentials the other day. I finally had a moment to get the HACS integration installed this morning while drinking my morning coffee. Robert Drinovac, a few cups of coffee are coming your way, well done! -
Andrew What sort of update are you looking for? The Home Assistant integration is located at https://github.com/RobertD502/home-assistant-flair . Once integrated into Home Assistant, you can use the HomeKit Bridge integration to push entities created by the Flair integration into HomeKit.
-
Yes, the Pucks (Set each one to "Gateway") control the Vents.
But in HA you can tell what the vent to do! (https://github.com/RobertD502/home-assistant-flair)
You can also do Automation at the Vent Temp -- for example i have automation where the Vent temp goes above 80*F they close (they're upstairs so id want to divert the heat to the downstairs) , Under 78*F they open (cooling top floor to bottom floor)
-
Flair Bridge support has been added to the 0.2.0 release: https://github.com/RobertD502/home-assistant-flair/releases/tag/0.2.0
Other additions:
- Associated gateway sensor has been added to Pucks and Vents allowing you to see what gateway each one of your devices is using.
- Network repair mode switch has been added to the Flair Structure, allowing you to start and stop a network repair right from within Home Assistant!
A big thanks goes out to Chrissie and Kenny Tay who sent a bridge out to me so that I can add support for it in the Home Assistant integration!!!
-
Robert Drinovac - nice work and congrats on the release!
Please sign in to leave a comment.
Comments
105 comments