Reorder rooms in Flair app?
-
Official comment
Hi Jeff Day,
Thank you for this suggestion. Several other customers have echoed this sentiment as well.
We have a feature request related to this and I will add your request to that.
Regards,
The Flair Team
Comment actions -
been waiting for so long for this...
https://support.flair.co/hc/en-us/community/posts/7329063825677/comments/7505186226573
-
While we're looking at reodering the rooms, maybe we could also add more rooms wide.
Currently its only 3 rooms wide....when we have 22" 1080p monitors. Why set a fixed number of 3, when our screens are so much wider, and our resolutions are so much higher. There's plenty of space for more (5+) -
Several other customers have echoed this sentiment as well.
We have a feature request related to this and I have added your request. We cannot guarantee a timeline for implementation but when this is rolled out we will let everyone following this thread know.
Regards,
The Flair Team.
-
I have had these products since 2018 and wanted this simple “feature” to be able to sort or re-order the rooms. I am starting to think that you are no longer updating your app. The standard response of we will add this to our list of requests seems like those are not really getting addressed. I am feeling like your systems are getting dated now. Please start supporting your apps again.
-
Is flair not there, or does flair not care? I have ten vents, an assortment of pucks, bridges, on the verge of getting another 10 vents, but if they can’t do the simple stuff in 3 yrs, what chance do we have for a little more robust progress? Have you spent all your r&d money on which colors to include on your face plates? Cmon guys, make us proud to be your customers.
-
Flair Customer Support would appreciate the feedback on this feature, it's been years... These days you can solve it with one prompt and just a few tokens...
Here are some ideas:1. Model it in your backend
- Add something like
sortOrder(integer) orpositionon the room (or structure-room) record, scoped per home/structure so each building has its own list. - Default: assign order when rooms are created (e.g. incrementing, or derived from current behavior) so nothing changes until someone edits order.
- API responses that return rooms for a dashboard should
ORDER BY sort_order, id(or name as tie-breaker).
2. Expose it in your API
-
Read: Include
sortOrderin the room payload; list endpoints return rooms already sorted. -
Write: Either:
-
PATCH /rooms/:idwith{ sortOrder: N }, or -
PUT /homes/:id/rooms/orderwith an ordered array of room ids:[ "uuid-1", "uuid-2", … ](often nicer for drag-and-drop: one call, no gaps).
-
Validate ids belong to that home; use a transaction so reorder is atomic.
3. Build the in-app UX
- Settings (or room management): “Reorder rooms” with drag-and-drop (or move up/down).
- On save, call the reorder API; optimistic UI optional; refetch or apply local state from response.
- All clients (web, iOS, Android) use the same API so order is consistent everywhere.
4. Decide scope: home vs user
- Home-level order (one list for everyone in the household): simplest and matches “how the house is laid out.”
-
Per-user order only if you explicitly want “my view” vs “their view” (more complexity: separate table keyed by
user_id+home_id).
For a whole-home HVAC view, home-level is usually right.
5. Operational concerns
-
Backfill: Set
sort_orderfrom current stable ordering (e.g. id or name) once. -
New rooms: Append at end or insert with
max(sort_order)+1. -
Deleted rooms: No need to renumber immediately; compacting
sort_ordercan be a background job or on next save.
6. What not to rely on
- CSS-only or client-only order does not scale to “all customers”: it isn’t stored, isn’t consistent across devices, and isn’t something support can reason about.
In short: persist order per home, sort in the API, reorder via one clear endpoint, render lists from that order on every app surface. If you later need Flair-specific integration (their API vs your own app), say which system owns “rooms” and we can narrow the schema and endpoint shape.
- Add something like
Please sign in to leave a comment.
Comments
13 comments