Vents Stuck Closed

Follow
Avatar
Joshua Pilkington
  • Edited
Very often (about every 3 days), I will get a vent stuck in the closed position even though on the app/website, it is being reported as being connected and open. Just today, my Office was at 75 F and the vent was closed but it was supposed to be open as the setpoint is 72 for the office. The vent itself had a good RSSI signal and in the app, the vent was being reported as open. The only way to remedy is to unplug the gateway the vent is connected to and wait for the vent to open after connecting to another one. Vents will also correct themselves after quite a period of time (usually several hours). Having to deal with this is not something I want to be doing long-term. Can someone look into this? It appears to be a bug either in the vent or puck firmware.
1

Comments

5 comments

Sort by Date Votes
  • Avatar
    Burton Tarvin

    Happened to me more than three times with different vents.  I'm over it.  Had the system for a month and all I got from support is: Check the batteries and re-power the vent, are you sure the vent in the room is labeled correctly?  This system over the last 30 days has been a constant headache.  A vent that is closed but is read as open by the APP will damage the HVAC system.  I'm out ... $1,400 into this system and I'm done.  Returning tomorrow!

    1
    Comment actions Permalink
  • Avatar
    Burton Tarvin

    5 days and no response.

    0
    Comment actions Permalink
  • Avatar
    James Clarke

    Hi Joshua Pilkington and Burton Tarvin,

    Joshua, we have created a support ticket from your post and a member of our support team will be in touch in the next 24 hours to discuss your issue and to look at your Flair home.

    Burton,

    I know you have a call scheduled with our team this afternoon.  

    Thank you both.

    Regards,

    The Flair Team.

     

    2
    Comment actions Permalink
  • Avatar
    Tom Mathison

    Flair sucks

    0
    Comment actions Permalink
  • Avatar
    Joshua Pilkington
    • Edited

    @James Thanks for responding and creating the ticket. I had forgotten to reply earlier. It was mentioned in the support ticket that that a new firmware was being developed to address the issue. I am not sure if I have had it installed yet or not, but I have not seen any instances of this issue happening within the past couple of months (knock on wood).

    0
    Comment actions Permalink

Please sign in to leave a comment.