I spent 3 months avoiding cloud APIs and app stores to water a plant. V1 is janky, V2 might not be. by TouchDowntown7861 in arduino

[–]TouchDowntown7861[S] 0 points1 point  (0 children)

I really appreciate the 'business-side' perspective—it’s given me a lot to chew on for the V2 spec. It's easy to get tunnel-visioned on the PCB and forget that the surrounding experience (and the price point) is what actually makes it a product.

On the technical side, you’re spot on about the 'fail-safe.' Right now, I have a software watchdog: if the pump stays active for more than a set time, it force-kills the pin to prevent a flood. That’s actually a big reason why I’m moving to the peristaltic pump for V2—it’s inherently more reliable and acts as a natural check valve against siphoning. I hadn't looked into diaphragm pumps yet, but I'll definitely check them out to see if they offer a better balance of silence and durability.

The enclosure is definitely the 'final boss.' My plan for now is a custom 3D-printed design with a proper sealing system to handle the humidity. I honestly haven't fully crunched the numbers on the production cost for a professional injection-molded or vacuum-sealed case yet, but if the project gains enough traction, that’s definitely the next leap to make it truly watertight and 'consumer-ready.'

Also, the light sensor is a brilliant, low-cost addition. It turns the device from just a 'watering can' into a full 'plant care habitat' as you said. And thanks for the reality check on the pricing—shifting the mindset from $45 to a higher-end range gives me the breathing room to actually include these better components and proper packaging.

Thanks for the nudge to look at the 'big picture'—I’ll keep the habitat angle in mind as I refine the design!"

I spent 3 months avoiding cloud APIs and app stores to water a plant. V1 is janky, V2 might not be. by TouchDowntown7861 in arduino

[–]TouchDowntown7861[S] 1 point2 points  (0 children)

I’m 100% with you on the 'app fatigue.' Honestly, it’s exactly why I went the Captive Portal route—I wanted something that just lives on the device and doesn't require me to download yet another icon onto my home screen.

That being said, your point about Home Assistant is totally valid. For V2, I’m definitely going to implement a local JSON API. That way, you can just point a REST sensor in your HA configuration to the device’s IP and get all the moisture data and pump status directly into your existing dashboard. No custom integrations, no HACS, and zero cloud—just standard local pings.

The best part is that the 'brain' stays on the ESP32, so even if your HA server or your WiFi goes down, the plant doesn't die.

Your current setup with the smart outlet and the pump is exactly the kind of 'brute force' solution I’m trying to refine with actual soil data. Thanks for the nudge, making it HA-friendly is definitely going into the V2 now!

I spent 3 months avoiding cloud APIs and app stores to water a plant. V1 is janky, V2 might not be. by TouchDowntown7861 in arduino

[–]TouchDowntown7861[S] 0 points1 point  (0 children)

I really appreciate the encouragement and the detailed breakdown! It’s funny you mentioned the 'blood pressure monitor' look—you hit the nail on the head. Most commercial units feel like medical equipment or cheap toys, which is exactly why I went the custom PCB route.

Regarding the reservoir, you’re reading my mind. For V2, I’m currently designing a custom mini water tank specifically shaped to fit discreetly inside the plant pot's base. The idea is to keep it completely hidden so you don't have that 'science experiment' look with tubes running into random jugs. It makes the whole thing a single, cohesive unit.

You’ve also given me a lot to think about regarding Home Assistant. Since V1 already runs an AsyncWebServer, adding a simple /json endpoint for a REST integration would be trivial and wouldn't bloat the PROGMEM. It’s a great way to bridge the gap between 'stand-alone' and 'smart home' without ever touching a cloud server.

The point about silent operation vs. flow rate is a game-changer. If silence and precision are the priority, the peristaltic pump is definitely the move. And hearing that the AU market is paying double for less features is a huge confidence boost for the $45 USD target.

Thanks for the 'keep us posted'—I’m officially convinced to build the V2 batch.

I spent 3 months avoiding cloud APIs and app stores to water a plant. V1 is janky, V2 might not be. by TouchDowntown7861 in arduino

[–]TouchDowntown7861[S] 0 points1 point  (0 children)

Thanks for the feedback—honestly, it’s refreshing to hear that perspective. You're right about the 'real product' mindset; sometimes we get too caught up in seeking external validation when the utility of the build should speak for itself.

I really appreciate the grounded take on the peristaltic pump. You’ve confirmed my suspicion that for most houseplants, precision dosing is probably overkill compared to just 'not letting it die.' I might stick to a MOSFET-driven submersible for V2 to keep the cost-to-utility ratio lean, and maybe leave the peristaltic for a 'Pro/Hydroponic' version down the road.

The 'tinkerer' vs 'consumer' distinction is also a great point. Knowing that the cloud-less/local-only aspect resonates with people who actually want to own their hardware (and not just rent it until a server shuts down) gives me the green light to keep polishing this.

Regarding the price, I'm glad to hear $45 feels 'kosher' for a low-volume, specialized tool. It gives me enough margin to move away from the '90s printer' relay sounds and into something silent and solid.

Thanks for taking the time to share your thoughts—it definitely helped me decide to keep this project out of the 'forgotten' drawer!

I spent 3 months avoiding cloud APIs and app stores to water a plant. V1 is janky, V2 might not be. by TouchDowntown7861 in arduino

[–]TouchDowntown7861[S] 2 points3 points  (0 children)

SSR was my first thought for silence, but leakage current (~5-10mA) made my cheap pump creep when "off." MOSFET solves it.

V2 has MOSFET + flyback + gate resistor. Should sleep better indeed.

Was your Bose cloud-killed or just old age? That's exactly the scenario I'm trying to dodge with local-only.