Flick 2 Honest Review — Is the Hype Justified?

Introduction

I've been using the Flick 2 for several months as a small, always-on control point around my apartment. I bought it because I wanted a physical, low-friction way to trigger routines—turn lights on or off, start a playlist, and run a few automations without pulling out my phone or yelling at a voice assistant. After living with the Flick 2 in the kitchen, bedroom, and living room for roughly four months, I can say I have a clear sense of where it shines and where it falls short.

What is the Flick 2 (briefly)?

In my experience, the Flick 2 is a compact smart button that connects over Bluetooth Low Energy to a phone or a hub and lets you map single press, double press, and long press actions to smart home tasks. It’s small enough to mount on a wall, stick to a bedside table, or carry in a pocket, and the core idea appealed to me: make a simple physical control that doesn’t require voice or an app for every interaction.

How I tested it

To get a realistic sense of the Flick 2 I used it in three typical ways over the months: paired directly with my phone for quick local actions; connected through a small hub (to expose the button to my Hue Bridge and several cloud services); and in a more minimal setup where it triggered only on-device shortcuts. I set up several routines—morning lights, an “all off” scene, a few music shortcuts, and a panic shortcut to trigger a smart plug—so I could repeatedly use the Flick 2 in different contexts and measure responsiveness and reliability during daily life.

Design and build: solid, pleasantly minimal

What I appreciated first was the physical design. The Flick 2 is compact, unobtrusive, and has a tactile click that feels satisfying without being loud. The finish I chose resists fingerprints and the button sits snugly in its housing—after months of use it still looks good. I mounted one on the kitchen backsplash with the included adhesive and it stayed put through multiple dishwashing sessions nearby (I didn’t submerge it, of course).

Mounting options are decent: the magnet/dock solution and sticky mounts both work, and I liked being able to move the button around if I wanted to. One small annoyance: the adhesive that ships with it is strong but not reusable, so once I popped it off to try a different spot I had to replace the pad. I would've appreciated a higher-quality reusable puck for experimenting with positions.

Performance and reliability

In my home—two floors, a few walls, typical Wi‑Fi noise—the Flick 2 performed well most of the time. For local phone-connected actions (simple shortcuts that run on the phone), response time was nearly instant: press, action, done. That responsiveness made it genuinely useful; I found myself reaching for it instead of my phone for quick tasks.

That said, reliability varied depending on how I connected it. When paired directly to my phone, it was very reliable as long as the phone stayed in the apartment and Bluetooth didn’t sleep that particular connection. When I bridged it through my hub to control the Hue lights or to expose it to routines in a cloud service, I saw occasional delays—sometimes a second or two, and only a couple of times the action failed the first attempt and required a second press. Those failures were rare, but they frustrated me when I was in a hurry.

Range is what you'd expect from a BLE device: good for a single room and adjacent rooms, but if you hide the hub or phone several rooms away you can hit limits. The hub helps extend reach, but hub placement becomes critical.

Battery life and charging

Battery life is one area where expectations can diverge depending on use. In my experience, with moderate daily use (around 10–20 presses per day across single/double/long presses) the Flick 2 ran for weeks between charges. I charged it roughly once every 3–4 weeks; if I used it heavily it was closer to three weeks. Charging is straightforward and fairly quick, and the design lets you keep it mounted while charging in most setups.

One thing I noticed: low-battery notifications are provided via the companion app, which I appreciated. It gave me enough notice to plan a charge instead of being surprised. That said, because I rely on the device for everyday tasks, the downtime while it charges (even a short one) is annoying—so if you rely on it for critical tasks, plan for a backup or keep more than one button.

App, software, and integrations

The companion app is where Flick 2's usefulness really becomes visible. Setting up single, double, and long-press actions is straightforward: I mapped short press to toggle the main living-room lights, double press to activate a “movie” scene that dims Tony’s lamps and closes the shades, and long press to run a phone-based shortcut that started a specific playlist.

Integrations were mostly good. I could make it talk to my Hue lights (via hub), trigger webhooks, and run shortcuts on my phone. In my experience, integrations relying purely on cloud services were convenient but introduced extra latency and a dependence on external services. When possible, I preferred keeping automations local or phone-based for speed and reliability.

Where the app could be better: the UI sometimes felt cluttered, and discovering advanced options (like setting long-press thresholds or combining multiple actions) required digging through menus. I was also annoyed that some integrations required an additional hub or intermediary service; I expected more native compatibility out of the box.

Everyday use cases and how it fit into my routines

Over the months, I found the Flick 2 fits best when used for a small set of repeatable actions rather than trying to replace every smart control. A few things I set up and used frequently:

• Bedside lights: One press to turn the lights on at dim level, double press to start a white-noise playlist, long press to trigger “do not disturb” on my phone. It’s a far nicer interaction than fumbling for a phone at night.
• Kitchen quick actions: Mounting one near the stove, I used it to turn exhaust fan and under-cabinet lights on/off. A double-press lit the prep lights bright for chopping vegetables.
• Music control: Mapping a press to play/pause and double-press to skip worked well when my phone was out of reach. Latency was minimal when the control was phone-connected.
• Panic/shortcut: I set up a long-press that toggled a smart plug and sent a notification. It worked but required ensuring the chain (button → hub → cloud → action) was solid.

In practice, the Flick 2 excels as a "small set of reliable shortcuts" device. When I tried to make it do too many things or to depend on cloud-only automations, friction increased.

Privacy and security

I liked that many of my common automations could be kept local—paired to my phone or routed through a local hub—so I wasn’t forced to send everything to the cloud. That reduced my concerns around data privacy. The app asks for sensible permissions and shows battery/connection status. If you’re privacy-conscious, verify which integrations insist on cloud access and plan accordingly.

What I liked (specifics)

• I appreciated the tactile, reliable click and compact design; it feels like a high-quality gadget.
• Instant response for phone-based shortcuts made it genuinely useful for quick tasks.
• Flexible mounting options let me try different locations; I eventually settled on three favorite spots.
• Good battery life for normal use—charging every few weeks is reasonable.
• Ability to map multiple press types (single, double, long) to different routines made the button far more powerful than a single-action switch.

What bothered me (specific disappointments)

• Occasional latency or failed triggers when the action chain depended on cloud services. That hurt trust in urgent moments.
• The app’s deeper settings are not always discoverable; tweaking advanced options required hunting through menus.
• Adhesive mounts are not reusable, which made experimenting with placement unnecessarily messy.
• Range is typical for BLE but can be limiting in larger homes without careful placement of hubs or phones.

Pros & Cons

• Pros:
  • Compact, well-built, pleasant tactile feel
  • Quick local actions when paired with a phone
  • Multiple press types make it versatile
  • Good battery life for everyday use
  • Works with a range of smart home services when bridged
• Cons:
  • Occasional lag or missed triggers when cloud services are involved
  • Mounting adhesive not reusable
  • App UI can be clunky for advanced configuration
  • BLE range limitations in larger homes

Comparison: Flick 2 vs common alternatives

Buying guide: Is Flick 2 right for you?

Here’s how I’d think about whether the Flick 2 makes sense for your setup, based on what I learned firsthand.

Check your ecosystem

If you rely heavily on a single ecosystem (Hue, HomeKit, Alexa, Google), verify how you’ll integrate the Flick 2 before buying. In my setup I had to use a small hub to reach some services, and that added complexity. If you want the simplest experience, choose a button that natively speaks your main platform.

Decide how you’ll connect

Do you want it to act locally with your phone (fast, private) or do you need hub/cloud integrations (more powerful, potentially slower)? I favored local phone shortcuts for speed and reliability, but if your goal is to trigger cloud-only automations you should expect occasional delays.

Plan for placement and range

Bluetooth is great for single-room control but not for whole-home coverage unless you strategically place a hub. Think about where you’ll mount the button and whether it will reliably reach the phone or hub. I relocated my hub once to improve consistency.

Think about redundancy

If the button controls something mission-critical for you (security, safety), plan a backup. I kept a second small button for the “all off” routine during battery charging or if the button misfired.

Consider the battery model

If you prefer "set and forget" with multi-year coin cells, a device with replaceable batteries may be better. If you don’t mind charging every few weeks for a sleeker rechargeable design, the Flick 2’s battery life worked fine for my daily needs.

Evaluate the app and configurability

If you like deep customization, make sure the app exposes the settings you need. The Flick 2 app lets you do quite a bit, but I often had to hunt for the less obvious options. If you value an instantly intuitive app, try the app first if possible.

Conclusion

After several months with the Flick 2, I can say the hype is partly justified. For what it is—a compact, tactile, configurable smart button that adds physical control to your smart home—the Flick 2 delivers a lot of value. It shines when used for a handful of repeatable, phone-based shortcuts where speed and simplicity matter. I enjoyed the feel, the battery life, and the small but powerful set of actions you can map to short/long/double presses.

That said, it’s not perfect. My frustrations were real: adhesive mounts that aren’t reusable, the occasional cloud-induced delay, and an app that could make advanced features easier to discover. If you expect flawless cloud automations every time, or need whole-home BLE coverage without thinking about hubs and placement, you may run into limits.

In my experience, if you want a small, flexible button to make everyday smart home interactions simpler and faster—and you’re willing to accept a few practical trade-offs—the Flick 2 is worth considering. It changed a few small daily moments for the better in my home, and those small wins added up over time.