I sent an email to all my active contributors today about the new update procedure effective immediately.
After some investigation with my e-commerce solution provider, I’ve found the following solution:
Instead of “pushing” updates by emails, you’ll now be able to download the new versions when you feel it’s most appropriate for you.
Currently, with the original “Sellfy” download link, you can download up to 5 times (or 5 versions spread over time) of the product(s) you’ve contributed to.
With the new update procedure I sent to all my active contributors, they will be able to download unlimited
"minor updates" when they feel it’s the most appropriate for them.
Please take note that I will no longer “push” updates by emails.
with your app, is it possible to read the temperature settings (actual temperature and set temperature) for use with the NST Manager as a remote sensor for the nest thermostat? The original Flair integration with Nest doesn’t seem to do anything.
Yes, it’s possible, but just to warn you, the puck temperature needs to be offset as it’s known to be higher than the actual ambient temperature. It used to be documented also in the Flair forum.
P.S. You’d need to contact Flair support to properly set those attributes, as the APIs documentation is thin. I’ve worked to expose them to SmartThings, but there are subtleties that need to be addressed with Flair.
There are some pluses and minuses for both solutions…
Flair suffers less interferences with its proprietary protocol as Keen uses Zigbee… But at my home, Keen has been working fine (with the Keen Bridge has a repeater under ST) for more than 2 years (I haven’t changed the batteries yet with my DTH)…
I’ve had Flair for more than a year now and it’s working well so far… As it’s a cloud to cloud integration, it takes more time to set a level (0,50,100) due to servers load, network latency, etc… You cannot set a more precise level like Keen (ex. 25, 75,90)…
However, the Flair vents are usually less expensive than Keen.
Just my 2 cents…
I made a small change to My Flair Vent in v1.1.2 to reflect some recent changes that were made on the Flair APIs side. Now, the vent readings don’t report a closed vent state as the vent readings’ level is set to 1 even if the vent is closed.
So, I implemented a work around in the DTH to reflect a closed vent state when the vent’s level is not greater than 5.
My contributors can download the new code using the sellfy download link that was sent to them when they originally contributed at my store.
Please also take into account the vent level limitations as documented at the ST community wiki:
I just installed a Flair Puck and purchased the DTH. In Smartthings, it is showing a temperature 10-11 degrees higher that what the Puck itself is showing or what a multi sensor is showing. For instance, right now It says the temperature is 79 while the Puck and the multisensor both say 68. The Recently tab shows wacky values also. Is this a known problem?
And, it’s also documented at the Flair community forum here:
The room’s current temperature is somehow more accurate under the following DTH’s attributes:
rmCurrentTemperatureDisplay
rmCurrentTemperature
So, I’d recommend to use that value if you need it for your HA scenarios with Core/WebCore.
I’m just showing the data that come from the Flair APIs. The die temperature has never been documented, so I don’t know what this value represents. You may contact Flair support for more details.
Regards.
Hi, I was hoping that Flair would fix their APIs at one point as the puck’s temperature value coming from the APIs is too high…
But, it seems that my assumption was wrong, so in the meantime, I worked on a workaround to substitute the puck’s temperature with the room’s temperature which is more accurate.
You can download the new version of the Puck Device (v1.1.3) at my store using the original download link.
To update the code, just copy and paste the new DTH code over your existing code, save & publish in the IDE.
@yvesracine, I’ve read all this topic and I have a few questions to “close the deal” with Flair and your apps
That’s my setup: ST Hub, 2 Samsug HiWall Split (one at my living room and one at my master bedroom).
Questions: what hardware do I need? Two Flair pucks? Anything else?
Which of your apps or bundle you recommend to perform actions like: turn On AC if the room temps reach a certain value? Turn Off AC if nobody is in the room after a certain time? Control the AC using my ST App?
Sorry for all these questions!
Regards
Hi, first you need to check with Flair (contact support at flair.co) if the Samsug HiWall Split is supported (it should be as Samsung is a major brand, but they may not support all models). If so, you’d need 2 pucks (one for each split as the puck uses IR) and the following bundle at my store:
My HVAC unit bundle ($15) at my store.
With the bundle, you can expose your unit to SmartThings as a thermostat and a switch, so you can control it by turning it on/off manually (using the DTH) or define a setpoint (target temperature).
For your custom rules, you can use WebCore as my zoned heating/cooling smartapps usually control the units based on a master thermostat at your home (ex. Nest, ecobee, honeywell, any ST connected thermostats).
The ScheduleTstatZone smartapp can turn on/off the units based on your active (using your motion sensors) & scheduled zones at your home and keep the slave thermostats’ setpoints in synch with your master thermostat. I don’t know if you have such a configuration or not. Most people use splits for cooler/hotter rooms and still have a master thermostat for central heating/cooling.
I’m From Brasil and don’t have a master thermostate. The big issue is if flair based temp sensor in the room Will automatically turn On the AC when temp reach a pre set trigger temp.
Example: during my sleep at night the temp reaches 26°C and setpoint is 24. The flair will turn the AC on…
Based on your answer and apps resources, I think it will work just fine