Thank you, Thank you, Thank you!!!!
I will give the new betas a try!!!
I appreciate all your work and effort with this!
I can only imagine the frustration trying new code out... having to wait for flair to respond!
Typical of web based stuff! This is a BIG reason I do NOT like web based apps, but until we can get local control of our vents, this is the best thing out there!
Yeah totally get that. And of course this is your prerogative. However, in case you don’t already know, HPM allows the user to specify whether to update to stable or beta versions so “buyer beware” is built-in IYKWIM.
Thanks @mluck I will research more and see how to setup the beta via HPM, probably by next weekend
@ljbotero
Well it looks like things are working GREAT!!!
The log is controllable and works WELL!!! Thank you!
The ability to set all vents to inactive and open them to 100% and they STAY that way seems to be working great!
I HATE web based stuff though... NOT YOUR FAULT!!! I know this is what we have to deal with now, and I am not complaining about your app!
My vents don't seem to be following what they are told to do. Like set to 50% they are more like 30 and 80% more like 50.... I might try calibrating them again by pressing the reset on each vent.....
I think it cycles the damper and finds 0 and 100.
Once again I thank you for your effort!
OK great. I'd prefer not to create the app and devices from scratch as it would mean swapping devices in and out of a bunch of rules. So, in the meantime, would I be safe to just overwrite the current app and driver code with your latest beta version or do I need to install from scratch?
As a practical matter, does this mean if we install the new app in HE manually, that one needs to activate oauth in HE app code manually as well?
Sorry Jaime I having version control problems. Lots of unusual HPM errors. So I thought I’d install manually for now, but I’m not sure what’s the latest version. This thread seems to say v0.17, but HPM is seeing v0.18. But the groovy code doesn’t show the version number that I can find.
Can you clarify the correct versioning?
Edit: the link above is dead. And HPM shows this:
@mluck Thanks for catching the version confusion and the dead link!
To answer your questions:
1. Updating to Beta
Yes, you can safely overwrite your existing app and driver code with the beta versions - no need to start from scratch. Your devices and configuration will remain intact.
2. OAuth 2.0 Clarification
The OAuth 2.0 mentioned doesn't require enabling OAuth in the Hubitat app code. It refers to Flair's OAuth 2.0 authentication - you just need to enter your Flair Client ID and Client Secret in the app preferences.
3. Version Numbers
Sorry for the confusion! The current beta is v0.18. The version numbers are tracked in packageManifest.json, not in the groovy files themselves.
Beta Installation - Now with HPM Support!
I apologize for the confusion with the beta installation process. I've removed the separate packageManifest-beta.json file to properly align with HPM's manifest schema. The beta channel is now configured directly in the main packageManifest.json.
Preferred Method - HPM Beta Channel:
The beta should now be available through HPM:
Go to HPM → Modify → Select "Flair Vents"
Toggle "Install Beta Version"
Click "Next" to update to v0.18
Note: HPM may cache manifest files, so if you don't see the beta option yet, it should appear within a few hours. If anyone can successfully install the beta via HPM, please let me know as I haven't been able to fully test this due to potential caching.
Alternative - Manual Installation:
If HPM isn't showing the beta option yet, you can manually update:
Vent Driver: https://raw.githubusercontent.com/ljbotero/hubitat-flair-vents/refs/heads/Beta/src/hubitat-flair-vents-driver.groovy
The v0.18 beta includes all the fixes from v0.17 plus new Flair Pucks support. New feature: Pucks can now be used as temperature sensors/thermostats for Dynamic Airflow Balancing (DAB)! This should give you more flexibility in room temperature monitoring.
Please report back if you encounter any issues with the HPM beta installation - your feedback will help ensure everything is working correctly!
My HPM has gotten completely corrupted now and I don’t know how to resolve. I believe I have a beta Flair version and a main Flair version. The main version shows up in HPM as “vnullbeta”, per screen shot above. The beta version shows up as pv0.17.
I suspect the main version is actually your v0.18 but the HPM label of vnullbeta has me suspicious. And, I don’t see anywhere in your code where you have a comment with the version number indicated (am I just missing it?) so I have no way to doublecheck versioning.
Then, on the beta version, everything I try inside HPM (repair, uninstall, upgrade) throws fatal/serious errors that I can’t get past. As you can imagine, at this point, I’m prepared to delete it all and start from scratch but HPM won’t allow that either.
Not sure how to get past all this. And despite all this, I still have only appreciation for what you’ve done with HE<>Flair!
As an aside, there’s a minor bug in the app. If you create multiple app instances (each with their own home ID of course), later when you open one of the app instances it often has a different home ID. Which wouldn’t be a big deal, unless you need to Discover again, in which case it creates mayhem, as I’m sure you can imagine!
I did notice when running HPM updates that Flair continued to be listed for updating, but never seemed to update.
I am also not running a puck but just the bridge, but the puck driver still was downloaded and listed in my driver list. I guess it isn't being used by anything though.
I did not see what you were seeing in HPM though, and it would be handy if there was some way to distinguish version, either a note in the driver or in the name of the driver.
Also, question. To turn on/off "close vents in inactive rooms" in a rule, what command is used?
An unused device in HPM is harmless, no worries.
This is a red herring. Assuming you’ve configured the app correctly, the act of making a room inactive will close the vents and freeze further DAB until the room is reactivated.
For anyone else using HPM with Flair, what version number does HPM show when you select "View Apps and Drivers" from the HPM main menu? I continue to see "vnullbeta" and am therefore concerned I have the wrong version.
Not working for me @ljbotero, although it could be just a labeling issue, per above.
No it is not!
I have the app configured correctly, and when a room is inactive, the vent DOES close.
BUT seeing as how you don't know WHY I asked the question, your response was insulting and derogatory!
I guess I will have to PM the developer directly to get an answer to my question without being demeaned and insulted!
Being Mr. Perfect does have negative consequences!
Ouch completely sorry for insulting. Absolutely not my intention. What I was trying to explain — clearly not well — was that the function you were asking about isn’t operationalized at the rule level; it’s managed by the app AFAIK.
Thus my use of the term red herring. In my work environment, the term is never used in a derogatory fashion, just to convey information efficiently, but I totally appreciate how you could receive the way you did. So again, I apologize.
@mluck @pomonabill220 - I found the issue with HPM beta access!
The beta versions require enabling pre-release support in HPM first:
Go to HPM → Package Manager Settings
Toggle ON: "When updating, install pre-release versions. Note: Pre-releases often include more bugs and should be considered beta software"
Save the settings
Go to HPM → Update
You should now see "Flair Vents" with beta version 0.18 available
This explains why some of you were seeing "vnullbeta" or having issues - HPM wasn't configured to show pre-release versions.
@mluck - The "vnullbeta" display is likely because HPM couldn't properly parse the version when pre-releases were disabled. After enabling the setting above, you should see the proper version 0.18. If your HPM is still corrupted, you might need to:
First enable pre-release versions as described above
Try "Repair" from HPM
If that fails, manually remove the app/drivers and reinstall through HPM with pre-releases enabled
Version Numbering - You're right that version numbers aren't in the groovy files. They're tracked in packageManifest.json. I'll consider adding version comments to the groovy files in future releases for easier identification.
Multiple App Instances Bug - Thanks for reporting the home ID switching issue! I'll investigate this for the next release. As a workaround, always verify the correct home is selected before running Discovery.
@pomonabill220 - The puck driver is included even if you don't have pucks - it's harmless and allows for future expansion if you add pucks later.
Let me know if enabling pre-release versions in HPM resolves the beta access issues!
Thanks on all, @ljbotero.
For next release, can I request naming of app instances? With multiple home IDs, I end up with multiple instances of the app with the exact same name. Not a big deal, but it'd be helpful for sure.
Jaime, in case it's helpful for you to know, this is not my experience. I had prerelease enabled in HPM, and still ended up with vnullbeta. In fact, because I was convinced I made some error, I wiped Flair clean (from HPM and from app/driver code) and installed from scratch and I'm still getting vnullbeta. Even ran repair, still the same.
I don't think it matters because I just installed your code manually, just pretty sure I'm fine, but figured you'd want to know. Cheers...
HHmmm interesting! I will have to remember that incase I see that in other HPM updates that don't seem to go right, whether Flair or others.
I did not have the pre release option selected, so I did, then ran update and HPM found the 0.18 version listed and installed it.
Seemed to go ok?!
I did notice that afterwards, when opening Jamie's flair app it took a while to load... about 12 seconds, but since then it takes about 9 seconds to load which is what it used to take.
Not a deal breaker but just something to note.
Download the Hubitat app
