After hub reboot and I temporarily disable the Flair HE app, then enabled the Flair HE app, it was quiet UNTIL I tried one of my rules to set all vents active, then THIS:
And ALL my vents are STILL closed so HOW do I get them to open?
I’m getting the same error messages. While I certainly don’t know any more than you do, I’m interpreting the error message to mean that Flair is throttling (limiting use of) their cloud API. I don’t know if it’s a change in their policy implementation, or if @ljbotero’s latest version is more loquacious with the API. Either way, my vents are no longer updating.
FWIW I reached out to Flair customer service yesterday asking about the throttling. He acknowledged the outreach and said he’d speak to engineering and revert. Will share what I hear when I hear it.
Thank you for the info!
It did sort of appear that throttling was going on, but I don't know what I might have done to trigger the throttling
I did power down the Flair hub and of course the errors went away and all my vents opened like they should have.
I, like yourself, saw the same outcome of the vents not updating as well.
GAWD I hate cloud based things!!! We are at the mercy of Flair, and have long delays when things work, and no response when they don't.
Of course, it is NOT the "fault" of this HE app! When Flair decides to have their servers running, it works great, but we are still at their mercy!
It will be interesting to see what Flair says about their end of things, and what is causing this!
@mluck, the app instance naming suggestion makes a lot of sense when you're managing multiple homes. If you could open a feature request on the GitHub repo, that would help me track it properly alongside other enhancement requests. The GitHub issue tracker really helps keep everything organized.
About the "vnullbeta" display, that's definitely strange, especially since you had pre-release enabled. The detailed info you provided helps narrow down what might be happening with the HPM integration. Since your manual installation is working fine, you're all set, but I'll look into the manifest configuration to figure out what's causing this.
Now, about those log messages that have been flooding your logs, I can see why they'd be concerning. Let me clear this up: those aren't actually errors. They're debug messages showing the app is managing its communication with Flair's API properly.
In version 0.19, I added some API management to prevent overwhelming Flair's servers. The app limits concurrent requests to 3 at a time, caches responses to avoid redundant calls, and queues requests when we hit rate limits. Those "throttling" messages? That's the app respecting Flair's limits and queuing requests appropriately. It's working as intended.
To stop these messages from appearing in your logs, go to the Flair Vents app settings and set the Debug Level to "None". I also just pushed version 0.2 of the beta which reduces log verbosity further, plus includes other improvements.
Version 0.2 fixes:
All vents in the same room now get identical efficiency rates
Automatic OAuth authentication (no more manual authenticate button)
Better temperature sensor handling
Client Secret field now displays as a password field
You can see the full changelog here: hubitat-flair-vents/CHANGELOG.md at Beta · ljbotero/hubitat-flair-vents · GitHub
If you run into other issues or have suggestions, feel free to create GitHub issues. It helps me keep track of everything and ensures nothing gets missed.
The bottom line: set debug level to "None" to clean up your logs, and know that those throttling messages mean the app is properly managing API limits, not encountering errors.
Thanks Jaime. Sounds like I should withdraw my support ticket with Flair? Fair to say it was the prior version of this app that was too talkative with the API, which you believe you’ve now fixed?
HPM is not showing any new versions despite having beta enabled. Tried matching and repairing, but still no joy. I’m happy to install manually — is it just the app that changed or the device drivers too?
Yep I did that previously. See item #3 in Issue 4 on your GitHub.
Updated to 0.2 but now when I try and set a room active/inactive, the room status stays active.
Also, when using the HE dashboard to manually control the vent, the vent doesn't move:
tried the kitchen 8x8 vent to test:
Before 0.2 this did work.
To add, on the Flair android app I can control my vents manually.
It appears that the incorrect command is being sent to flair now?
I wonder — Is it possible you’re still being throttled? I know I am. FWIW Flair just told me via email that throttling lasts for 24 hours post the last bad behavior (i.e., overuse of API as defined by them).
So since I installed v0.20 earlier today, I was going to wait until tomorrow and then see what happens.
Just speculating out loud ….
Good to know that the throttling lasts for 24 hours.
It could be!
I will wait and see what happens tomorrow.
Thanks for the info!
Jaime, I saw v0.21 come through HPM so I tried it. All my vents are still not updating. I'm also no longer getting throttling messages, so not sure what's going on.
Is there some troubleshooting you'd recommend that we can try?
EDIT: when I try to manually change level, I get: org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: java.lang.String.call() is applicable for argument types: (com.hubitat.app.DeviceWrapper, java.math.BigDecimal) values: [Vent Frog South, 100] Possible solutions: wait(), chars(), any(), trim(), grep(), find() (patchVent) -- same as @pomonabill220 from yesterday.
Just got a note back from Flair saying they are no longer throttling the API. Guess whatever issue there was in an earlier beta version is now handled (thanks @ljbotero).
I imagine, by process of elimination, the problem we're experiencing is with the HE integration?
@mluck @pomonabill220 - Thank you both for catching this critical issue and taking the time to report it! I really appreciate your patience and detailed feedback.
You're absolutely right - there was a serious bug in v0.21 that broke all vent control functionality. The error you both encountered was caused by a coding mistake I made when updating the app. This has now been completely fixed in version 0.22.
@mluck - Regarding your questions from post #287:
Flair Support Ticket: Yes, you can withdraw that support ticket. You were right that it wasn't a Flair API issue - this was entirely my fault. The bug in v0.21 prevented any commands from reaching Flair at all.
Which Files Changed: For the fix, only the main app needs to be updated. The drivers are fine, so you only need to update the app itself.
App Instance Naming: Thanks for confirming you already created the GitHub issue! I saw it and it's definitely on my list.
I accidentally broke something when making improvements in v0.21. Basically, the app stopped being able to send commands to your vents. This affected:
Manual vent level changes
Dashboard vent controls
Room active/inactive status changes
All automated vent adjustments
@mluck - The reason HPM might not be showing v0.22 yet is that I just released it. Try:
HPM → Update (with pre-release versions enabled)
If that doesn't work, you can install manually - it's just the app file
I've added extra checks to prevent this kind of issue from happening again. Sometimes when you're making improvements, you can accidentally break something basic - which is exactly why community feedback like yours is so valuable.
I really appreciate both of you sticking with this integration and taking the time to provide detailed reports. Long-time community members like yourselves make projects like this better for everyone.
@pomonabill220 - Your detailed screenshots and logs were incredibly helpful for figuring out exactly what went wrong. That kind of thorough reporting makes fixing issues much faster.
Let me know if v0.22 gets everything working again for you both!
Yeah maybe so. But you also get ALL THE CREDIT for doing this work without any remuneration whatsoever, so you'll only get appreciation from me and I bet @pomonabill220 too!
Bad news -- installed v0.22 and still no joy.
Since I have multiple Home IDs, I tried it two different ways so you'd have more testing feedback:
Unfortunately I'm dead in the water for now. Keep thinking I must have done something dumb, but can't figure out what it could be. 
@ljbotero this is a fantastic app!!! You have busted a gut getting this put together and are very responsive to questions (I know I have asked TONS), and trying to fix the problems quick!
I know we all are at a handicapt with this web based product, but "we" and YOU are doing the best you can to get it to work!
I appreciate all your hard work!
Thank you1
I just wonder if Flair has done something without telling us, that has crippled the HE app!?!?
I am just leaving the HE app disabled and all my vents open until this hickup is solved.
I have been busy with appointments the last few days so haven't been able to help diagnose, but this weekend things are going to let up a little and I will give it a shot!
Update from further testing…..I noticed after 15-20 minutes the devices all started behaving and the log errors went away — as if it took Flair’s cloud awhile to get configured. That doesn’t sound plausible, but device behavior seemed to sort itself out after a little while. With one exception, no issues since then with v0.22.
The one small issue: Jaime, I wonder if there’s been a regression with Voltage. You added it as an attribute at my request awhile ago, but the last few betas don’t seem to update voltage. I see the attribute in the driver, but it doesn’t show up in any of the vent devices.
EDIT: to further clarify the voltage issue, I can see events with the name “system-voltage” and feasible values in the event log, but the attribute doesn’t show up as an attribute in the device.
EDIT #2: Noticed system-voltage is starting to show up in some vent devices — maybe they’re on slower update polling than the rest? Dunno. However, this new attribute is not exposed to RM like it was previously so I can’t do anything with it. We use it to alert when batteries need changing fwiw.
@mluch, thank you so much for the follow-up and detailed testing feedback. I'm really glad to hear that the system sorted itself out after 15-20 minutes and that v0.22 is working well overall for you now. That delay behavior is actually consistent with some of the caching and initialization changes in recent versions, where the system takes a bit longer to fully synchronize all the device states and API communication patterns.
Regarding the voltage attribute issue, you've identified a real regression that I need to fix. You're absolutely right that the voltage attribute was working before and should be available in Rule Machine for your battery monitoring alerts. What's happening is that the system-voltage events are being received and logged correctly from the Flair API, but there's a problem with how that data is being mapped to the voltage attribute that Rule Machine can see. The attribute declaration in the driver isn't properly exposing it to the automation system even though the raw data is there. I'll need to update the driver code to fix the attribute mapping and ensure it shows up correctly in Rule Machine so you can continue using it for your battery change alerts. This should be a straightforward fix and I'll get it addressed in the next update.
I "took the plunge" and re-enabled the HE Flair app and my vents seem to be working GREAT!
The log doesn't show errors either, but a TON of caching and ignoring, which is expected I think.
I am just curious what is going on.
VERY nice update! Thank you!
Download the Hubitat app
