Smart yard devices: controller, timer and mower requirements
By SmartHomeWorkflow Team · Last updated 2026-10-12
Choose the job first: sprinkler zones, a hose tap or mowing. Then check the exact product’s installation and platform route. These are researched records, not performance rankings or hands-on tests.
◐Works; valve and on/off unconfirmedAmazon Alexa: Works; valve and on/off unconfirmed — see the catch
◐Works; valve and on/off unconfirmedGoogle Home: Works; valve and on/off unconfirmed — see the catch
?InconclusiveApple Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi
No
?
—
Netro Sprite Smart Sprinkler Controller — the catch, per ecosystem ~$99 at time of research — $99.00 for the 6-zone Sprite on Netro's own US store, read 2026-08-18, with the 12-zone listed beside it at $129.00. Both prices are the vendor's own. Never treated as a live price.
◐ Amazon Alexa: Works; valve and on/off unconfirmed — Netro connects its controllers to Alexa through the NetroHome skill, which you turn on in the Alexa app and sign in to with your Netro account. Netro's Alexa guide says the skill takes spoken requests ("Alexa, ask Netro Home to …") to water all zones, water one zone, or stop watering, but the guide is written for Netro controllers in general and does not name the Sprite, so starting a zone and turning watering on and off are unconfirmed for this model.
◐ Google Home: Works; valve and on/off unconfirmed — Netro connects its controllers to Google Home when you link your Netro account in the Google Home app (Works with Google). Netro's Google Home guide says you can then start and stop watering from the app or by voice ("OK Google, start watering"), but the guide is written for Netro controllers in general and does not name the Sprite, so starting a zone and turning watering on and off are unconfirmed for this model.
? Apple Home: Inconclusive — Not established. Apple, Apple Home, HomeKit and Matter appear nowhere on Netro's product page for this model. Recorded as unknown rather than as an evidenced absence, since the page publishes a promotional ecosystem list rather than a compatibility field.
? SmartThings: Inconclusive — Not established. SmartThings appears nowhere on the page, and we read no Samsung page naming this product.
? Home Assistant: Inconclusive — Not established. Home Assistant is not named by Netro, and we read no Home Assistant documentation naming this controller. ⊕ The page does name 'If This Then That' as a supported ecosystem, which is a cloud automation service rather than a local one — we note it as context, not as Home Assistant support.
Connection: Wi-Fi · Hub for full use: No — verified that none is needed · Works offline: Not checked — we have not established whether this keeps working without the internet
◐PartialAmazon Alexa: Partial support — see the catch
◐PartialGoogle Home: Partial support — see the catch
◐PartialApple Home: Partial support — see the catch
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
✓WorksHome Assistant: Works with this ecosystem
Wi-Fi · Bluetooth
Yes
Partly
—
Rachio Smart Hose Timer — the catch, per ecosystem ~$99.99 $99.99 on Rachio's own US store, re-read 2026-09-19 at the same figure, with a live Add to Cart control and the item listed as in stock. Read what that buys carefully, because it is the whole reason this product is priced the way it is: the $99.99 is a bundle of one valve AND one WiFi Hub, and the valve does nothing smart without the hub. Rachio states that 'Each WiFi Hub can manage eight valves', so the second and subsequent valves are the cheap part of an expanding system while the first one carries the hub's cost. Anyone comparing this against a Bluetooth-only timer on price alone is comparing a two-box system to a one-box one.
◐ Amazon Alexa: Partial — First-party and concrete about the mechanism: Rachio's voice-control documentation instructs you to 'enable the Rachio Smart Hose Timer skill in the Alexa app', which is a dedicated skill for this product rather than the sprinkler-controller skill doing double duty. The documented command set is what holds this at partial rather than full — the published capability is opening and closing a valve by its name and querying its state, with a voice-triggered open defaulting to 'the default Quick Run time before automatically closing'. Useful, and more than most vendors in this category document, but it is valve on/off rather than access to the schedule, the weather logic or the zones. One requirement Rachio states that is easy to trip over: the devices 'must be owned by your Rachio account and will not work with Rachio devices that are shared', so a household member who was given access rather than ownership cannot use voice at all. The hub is also a prerequisite — voice needs the timer 'connected to a Rachio WiFi Hub'.
◐ Google Home: Partial — First-party, and documented with the most specific example on the whole record: Rachio states that once linked, 'all valves associated with your account can be opened and closed using Google Assistant and Google Home', and gives the working phrasing — 'Hey Google, open Potted Plants' for a valve named Potted Plants, plus status queries such as 'Hey Google, is Garden closed?'. Naming the actual sentences is a real capability statement, not a compatibility badge. Partial for the same reason as Alexa: the scope published is open, close and query, and nothing suggests schedules or weather behaviour are reachable by voice. Same two prerequisites apply — an owned rather than shared device, and a connected WiFi Hub.
◐ Apple Home: Partial — There IS an Apple answer here, and it is the most commonly misreported fact about this product — so read the distinction carefully, because it decides whether this fits your house. Rachio's own voice-control documentation offers Siri through 'Apple Shortcuts integration to Quick Run your Rachio Smart Hose Timer'. That is Shortcuts, not HomeKit. What you get is a Siri phrase that triggers a Quick Run; what you do NOT get is a device in the Apple Home app, a tile you can tap, a valve any HomeKit automation can address, or anything shareable with the rest of the household through Home. Anyone reading 'works with Siri' as 'works with Apple Home' will be disappointed on the first day. Recorded 'partial' precisely because the route is real and first-party rather than absent — this is one of the few products in the yard category with any Apple story at all, and Eve Aqua's native HomeKit-over-Thread in this same subcategory is what a full one actually looks like. We could not confirm a Matter certificate for Rachio.
? SmartThings: Inconclusive — Rachio has not said, and neither has Samsung. It is worth being precise about why, because the page that looks like it answers this does not: Rachio's voice-control documentation lists the assistants it supports — Amazon Alexa, Siri, Google Assistant and Google Home — and that list is complete as far as it goes. But it is a list of voice assistants, and SmartThings is a hub rather than a voice assistant, so it was never a candidate for that list and its absence from it proves nothing either way. No Samsung documentation naming this timer was found either. Neither side has spoken, so the honest answer is that nobody knows.
✓ Home Assistant: Works — The strongest cell on this record, and it comes entirely from the other side — Rachio's own pages name Home Assistant nowhere. Home Assistant ships an OFFICIAL Rachio integration, IoT class 'Cloud Push', and its documentation covers hose timers explicitly rather than by implication: it provides 'a switch for each smart hose timer valve' and 'A calendar entity will be added for each smart hose timer base station'. That is per-valve control plus the schedule surfaced as a calendar, which is more than any of the three voice platforms offer. It runs through Rachio's cloud, so it is not a local control path despite the depth. ⚠ One discrepancy is recorded rather than reconciled, because both sides are first-party to their own claim and this catalogue does not adjudicate between them: Rachio says 'Each WiFi Hub can manage eight valves', while Home Assistant's integration documentation says 'Up to 4 valves can be paired to a single base station'. That may be a difference between what the hardware supports and what the integration exposes, or it may be one of the two being out of date. If you are planning a system around valve count, verify against your own hardware before buying the eighth valve.
Connection: Wi-Fi · Bluetooth · Hub for full use: Yes (Yes, and it is included in the $99.99 — but it is a real architectural constraint rather than a packaging detail, so it is worth understanding before you buy a second one. Rachio describes the chain in its own words: 'The Timer uses Bluetooth to communicate with the WiFi hub, and the WiFi Hub communicates to your WiFi router or access point via 2.4 GHz WiFi.' So the valve on the tap speaks only Bluetooth; everything remote — scheduling, voice, app control from away, weather adjustment — depends on a mains-powered hub indoors being in Bluetooth range of it. Two consequences. First, the 2.4 GHz requirement is stated and absolute, which matters on a modern mesh router that hides its bands. Second, that hub-to-tap range decides whether this works at the far end of a garden, and Rachio does publish a figure for it: 'The Timer Valve should connect to the WiFi hub up to 200 ft away with no obstructions between the valve and the hub. Dense walls, appliances, and other objects can diminish that range.' Read the two halves of that sentence together — 200 feet is the clear-line-of-sight number, and a house wall between the hub and the tap is exactly the obstruction Rachio is warning about. Capacity is stated too: 'Each WiFi Hub can manage eight valves', so the system expands cheaply once the first hub is in place.) · Works offline: Partly — some of it keeps working without the internet and some of it does not
◐PartialAmazon Alexa: Partial support — see the catch
?InconclusiveGoogle Home: We researched this and the evidence doesn't settle it — the catch explains why
✗Doesn't workApple Home: Verified: does not work with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi · Bluetooth
Yes
Yes
—
Orbit B-hyve XD 4-Outlet Hose Faucet Timer with Hub — the catch, per ecosystem ~$134.99 $134.99 on Orbit's own US store, read 2026-09-13, shown 'in stock, ready to be shipped' with a live Add to cart control. This is the bundle SKU — model 24639, the four-outlet timer WITH the WiFi hub included. Orbit sells a hub-less sibling of the same timer under model 24634, and that distinction is the one to keep straight when comparing prices: a cheaper 24634 figure found elsewhere is a Bluetooth-only device with no remote access at all, not a discount on this product. Recorded at the bundle price because the bundle is what this record describes.
◐ Amazon Alexa: Partial — Orbit's product page for this model lists Alexa, and its help centre for the XD hose timer explains how to link it through the B-hyve Alexa skill. Our record classifies this as partial, for two reasons. First, only one B-hyve device can be linked to an Alexa account at a time, so a household that already controls a B-hyve sprinkler controller or another hose timer by voice cannot add this one alongside it. Second, control is by spoken request to the skill ("Alexa, ask B-hyve to..."): stop, skip, off and auto modes, running a program or a numbered station for a set number of minutes, and rain delays. Orbit does not say the timer shows up as a device in the Alexa app or works in Alexa routines, and it does not say whether commands depend on its internet service. This rests on Orbit's own documentation; we could not confirm it against Amazon's skill listing.
? Google Home: Inconclusive — Not confirmed, even though Orbit now names Google. The product page for this model lists Google alongside Alexa, and Orbit's help centre for the XD hose timer has Google setup instructions, but every command in them starts with "Talk to Orbit Bhyve". That wording looks like the older kind of Google Assistant voice app, which Google switched off for every company on June 13, 2023, and Orbit's instructions do not say the timer can be added as a device in the Google Home app. This stays unconfirmed until Google's own list of supported devices, or a direct statement from Orbit, settles it. If it does work, Orbit states the same limit as Alexa: only one B-hyve device can be linked to a Google account at a time.
✗ Apple Home: Doesn't work — No route on any evidence. Orbit's product page for this model names Google and Alexa and never mentions Apple, HomeKit or Siri. There is no Matter path either, and this is where the record's most careful finding sits: a keyword search of the CSA-IoT certified-products database for 'B-hyve' returns zero certified products, and a search for 'Orbit' returns twelve — every single one of which is a 'Magical.Homes Orbit Series Switch Panel' certified by Longan Link Tech Co., LTD, an unrelated company that happens to use 'Orbit' as a product-series name. A brand keyword matching a registry entry is not the same as a brand holding a certificate, and reading those twelve hits as Orbit Irrigation's would have been a straightforward error.
? SmartThings: Inconclusive — Not established. Orbit's page for this model names Google and Alexa and not SmartThings, and no Samsung documentation naming this product was located, so neither side speaks. Recorded unknown on both.
? Home Assistant: Inconclusive — Nothing confirmed for this product. Home Assistant ships no official B-hyve or Orbit integration — there is no listing for either name in its integration directory — and Orbit names Home Assistant nowhere. A community-built B-hyve add-on exists outside Home Assistant's official list and is noted on the Orbit B-hyve XR page on this site, but we found no evidence it covers hose-timer valves as opposed to sprinkler controllers, and one product's integration is not extended to another just because they share a brand. Marked unknown, with the specific thing to check scheduled for the next review. Compare the Rachio Smart Hose Timer in this same category, whose official Home Assistant integration names hose-timer valves explicitly — if Home Assistant is where your automations live, that is the difference between the two products.
Connection: Wi-Fi · Bluetooth · Hub for full use: Yes (Yes for anything smart, and Orbit is unusually clear about it — the site labels the whole product line 'Requires 2.0 Hub To Activate Smart Functions', and this SKU includes that hub in the box. What sets it apart from a hub-only design is that Orbit publishes three tiers of control rather than one: the timer can be programmed on the device itself, locally over Bluetooth from a phone standing next to it, or remotely through the hub's WiFi. Orbit's own words are 'You have the flexibility to program remotely from the B-hyve mobile app, and the confidence to program on-device in a pinch.' and 'If you have a B-hyve Smart Gen 2 Hub (included) and a Wi-Fi router, you can control the timer anywhere in the world where your smartphone has reception.' The practical value of that ladder is failure behaviour: if the hub dies or the network drops, this timer still has buttons and still has a phone-side Bluetooth path, where a hub-dependent design has neither. Orbit says the distance from the timer to the hub may be 50 to 150 feet depending on how your home is built, so the hub's spot indoors matters. It gives no range for the Bluetooth link between your phone and the timer.) · Works offline: Yes — the core function runs on the device or your home network
?InconclusiveAmazon Alexa: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveGoogle Home: We researched this and the evidence doesn't settle it — the catch explains why
✓WorksApple Home: Works with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
✓WorksHome Assistant: Works with this ecosystem
Thread · Bluetooth
No
Yes
—
Eve Aqua — the catch, per ecosystem ~$164.95 Eve's own US price, $164.95, re-read on 2026-09-19 from the product page's own price data — the same figure this record has carried since 2026-08-02, so the price has not moved in that time. Eve sells direct and the page adds 'Free UPS Ground shipping to US locations with $99 purchase'. Two things to know about this number: it is a hose-tap timer, not a whole-system controller, so it is priced against a single outdoor tap rather than against the multi-zone controllers elsewhere in this category; and the Eve Store was running a promotional code on the day of the re-read, valid only on Eve's cameras and not on this product, which is why it does not touch the figure here.
? Amazon Alexa: Inconclusive — Eve's product page names no Amazon platform: it lists the Eve app, Apple's Home app and Siri as the ways to control Eve Aqua, and it describes the product as a HomeKit accessory that talks over Thread. A Matter certificate would be the route to Alexa. The Matter certification records could only be checked one way when we looked on 2026-10-06: the official certification list kept for Matter devices shows no Eve Aqua, but the public product directory could not confirm it, so the absence of a certificate is not settled. Either would settle it: Eve stating Alexa or Matter support for Eve Aqua, or a Matter certificate that names it.
? Google Home: Inconclusive — Not confirmed either way. Eve lists the Eve app, Apple's Home app and Siri as the ways to control Eve Aqua and does not name Google Home. The Matter ledger lists 32 Eve products and not Eve Aqua, but the certification body's own product search no longer works as a second check, so we do not record a firm no. Either would settle it: Eve naming Google Home or Matter for Eve Aqua, or a Matter certificate that names it.
✓ Apple Home: Works — The only product in this launch tranche with a real Apple Home story, and it is real precisely because it predates Matter rather than depending on it. This is a native HomeKit accessory — Eve calls it a 'HomeKit-enabled accessory' — running over Thread and Bluetooth, controlled from the Home app, the Eve app, Siri or the button on the unit. Full rather than partial because Apple Home is the platform this product was built for rather than one it was adapted to. Two requirements Eve states plainly and buyers routinely miss: 'Controlling this HomeKit-enabled accessory automatically and away from home requires a HomePod or an Apple TV (4th generation or later)', and using Thread rather than Bluetooth needs a Thread border router, which for Apple means a HomePod, the 2021 Apple TV 4K or the Wi-Fi + Ethernet 2022 model. Eve also lists under Requirements 'iPhone or iPad with the latest version of iOS/iPadOS' — there is no Android path to this product at all.
? SmartThings: Inconclusive — Not confirmed either way. Eve lists the Eve app, Apple's Home app and Siri as the ways to control Eve Aqua and does not name SmartThings. The Matter ledger lists 32 Eve products and not Eve Aqua, but the certification body's own product search no longer works as a second check, so we do not record a firm no. Either would settle it: Eve naming SmartThings or Matter for Eve Aqua, or a Matter certificate that names it.
✓ Home Assistant: Works — Home Assistant controls Eve Aqua locally through its official HomeKit Device integration, which supports Thread accessories and brings HomeKit valves in as switches you turn on and off, so you can start and stop the water from Home Assistant. Its IoT class is 'Local Push': direct, local, no cloud and no polling delay. Thread needs a border router, which can be Home Assistant's own hardware ('Home Assistant Yellow, Connect ZBT-1, or Connect ZBT-2') rather than an Apple device. The condition to know before you buy: a HomeKit accessory pairs with one controller at a time, and Home Assistant's documentation says to 'Remove the device from the Apple Home app' first, so it is Apple Home or Home Assistant, not both. Schedules set in the Eve app are stored on the device itself.
Connection: Thread · Bluetooth · Hub for full use: No (It depends entirely on what you want, and Eve is unusually clear about it. Standing at the tap with your phone, nothing is needed — it pairs over Bluetooth and the Eve app works directly. Schedules also run without a hub, and Eve is explicit about why: 'As schedules are stored directly on Eve Aqua, they can be run at any time – no matter if Eve Aqua is connected to your iPhone or the internet, and all without requiring a bridge or gateway.' The schedule lives on the device. What needs a hub is remote control and automation: Eve states that 'Controlling this HomeKit-enabled accessory automatically and away from home requires a HomePod or an Apple TV (4th generation or later)'. And to use Thread at all rather than Bluetooth, you need a Thread border router — a HomePod mini, a HomePod (2nd gen), the 2021 Apple TV 4K or the Wi-Fi + Ethernet 2022 model in an Apple household, or Home Assistant hardware with Thread enabled if you go that route.) · Works offline: Yes — the core function runs on the device or your home network
◐Works; valve and on/off unconfirmedAmazon Alexa: Works; valve and on/off unconfirmed — see the catch
◐Works per the maker; details unconfirmedGoogle Home: Works per the maker; details unconfirmed — see the catch
✗Doesn't workApple Home: Verified: does not work with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi · Bluetooth
No
No
—
Orbit B-hyve XR Smart Sprinkler Timer — the catch, per ecosystem ~$169.99 Re-checked 2026-08-18 and unchanged: 'Current price $169.99' on Orbit's own store for the 8-station model 57985, listed 'in stock, ready to be shipped'. ⊕ Orbit's own copy says the line supports 'up to 16 zones/stations', so a larger version exists at a price this page does not cover. Never treated as a live price.
◐ Amazon Alexa: Works; valve and on/off unconfirmed — Orbit connects B-hyve devices to Alexa through the B-hyve Alexa skill, which you turn on in the Alexa app before choosing the device in the B-hyve app; only one B-hyve device per account can be connected to Alexa. Orbit's Alexa guide lists spoken requests to the skill ("Alexa, ask B-hyve to …") to stop watering, switch between off and auto modes, run all programs, or water a numbered station for a set time, but the guide is filed under a different B-hyve controller and does not name the XR, so starting a zone and turning watering on and off are unconfirmed for this model.
◐ Google Home: Works per the maker; details unconfirmed — Orbit says this timer integrates with Google smart home control, in the same sentence as Alexa. It does not say how it connects to Google Home or which controls Google gets, so valve and on/off are unconfirmed there.
✗ Apple Home: Doesn't work — No Apple route on any evidence. Orbit's product page names exactly two smart-home platforms and Apple is not among them — a full-text read returns zero occurrences of 'Apple', 'HomeKit' and 'Siri'. There is no Matter path either: keyword searches of the CSA-IoT certified-products database for 'B-hyve' and 'bhyve' both return zero certified products, and a search for 'Orbit' returns only unrelated 'Magical.Homes Orbit Series' switch panels from a different company. This is a positive 'none' rather than an unknown: the vendor states which platforms it works with, and Apple is excluded from a list it took the trouble to write.
? SmartThings: Inconclusive — Unknown rather than a firm no, and the distinction rests on what kind of sentence Orbit's page actually carries. The only platform statement on it is a marketing bullet in a feature list — 'Integrates with Google and Alexa smart home control' — sitting between a bullet about valve voltages and one about the phone app. That is a highlight, not a compatibility table, and a highlight that names two platforms has not told you what the third one does. Orbit publishes no compatibility list for this timer, Samsung publishes nothing naming it, and community-built SmartThings integrations for B-hyve have existed in the past without our being able to establish their current state. So this records that nobody has published an answer, rather than asserting a no from a marketing line's silence.
? Home Assistant: Inconclusive — Not established. Orbit names no Home Assistant route for this timer, and Home Assistant ships no B-hyve integration of its own. Community-built add-ons reach B-hyve timers, but neither Orbit nor Home Assistant stands behind them.
Connection: Wi-Fi · Bluetooth · Hub for full use: No (No hub. The controller has its own Wi-Fi — Orbit advertises 'Dual Wi-Fi signals' for connection reliability — and everything else runs through Orbit's B-hyve cloud service and the free B-hyve app. The app is not optional: it is how the controller is configured and how every remote and voice feature reaches it.) · Works offline: No — the core function depends on the vendor's servers
◐Works; valve and on/off unconfirmedAmazon Alexa: Works; valve and on/off unconfirmed — see the catch
◐Works; valve and on/off unconfirmedGoogle Home: Works; valve and on/off unconfirmed — see the catch
?InconclusiveApple Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi
No
?
—
Netro Spark Smart Sprinkler Controller — the catch, per ecosystem ~$179 at time of research — $179.00 for the 8-zone Spark on Netro's own US store, read 2026-08-18, with the 16-zone listed beside it at $199.00. Both are the vendor's own prices. Never treated as a live price.
◐ Amazon Alexa: Works; valve and on/off unconfirmed — Netro connects its controllers to Alexa through the NetroHome skill: you turn it on in the Alexa app and sign in with your Netro account. Netro's Alexa guide lists three spoken requests you make to the skill by name: water all zones, water one zone, and stop watering. The guide doesn't name the Spark or any other model, so starting a zone and turning watering on and off are unconfirmed for this controller there. Netro says the skill controls only the first Netro controller on an account.
◐ Google Home: Works; valve and on/off unconfirmed — Netro connects its controllers to Google Home when you add Netro through Works with Google in the Google Home app and sign in with your Netro account. Netro's Google Home guide says you can then start and stop watering from the app or by voice, but it doesn't name the Spark or any other model, so starting a zone and turning watering on and off are unconfirmed for this controller there. Netro says Google Home can't set a watering time, so a start waters all zones for five minutes by default.
? Apple Home: Inconclusive — Not established. Apple, Apple Home, HomeKit and Matter appear nowhere on Netro's product page for this model.
? SmartThings: Inconclusive — Not established. SmartThings appears nowhere on the page, and we read no Samsung page naming this product.
? Home Assistant: Inconclusive — Not established. Home Assistant is not named by Netro, and we read no Home Assistant documentation naming this controller. ⊕ The page does name 'If This Then That' as a supported ecosystem, which is a cloud automation service rather than a local one — context, not Home Assistant support.
Connection: Wi-Fi · Hub for full use: No — verified that none is needed · Works offline: Not checked — we have not established whether this keeps working without the internet
✗Doesn't workApple Home: Verified: does not work with this ecosystem
◐Works per the maker; details unconfirmedSmartThings: Works per the maker; details unconfirmed — see the catch
✓WorksHome Assistant: Works with this ecosystem
Wi-Fi
No
Partly
—
Rachio 3 Smart Sprinkler Controller — the catch, per ecosystem ~$199.99 Rachio's own store price on 2026-08-02 for the 8-zone configuration. The 16-zone is $249.99 on the same page, and the two are one product in two sizes rather than two products, so they share this record. The lower figure is recorded as the entry price. Worth knowing before you shop: the page's own specification table still lists '4-zone, 6-zone, 8-zone, 12-zone and 16-zone models', but only the 8- and 16-zone configurations are offered for sale on it today — so a 12-zone listing found elsewhere is an older or third-party channel, not something Rachio currently sells direct.
✓ Amazon Alexa: Works — The most fully documented integration on this controller, and the only one on this record where the vendor states granularity rather than just naming the platform. Rachio's own page: 'With Alexa integration, you can turn Rachio on and off, run watering zones, or set rain skips using more than 100 different commands.' Running an individual watering zone by voice is the useful part — most irrigation integrations in this category are whole-controller only — and 'more than 100 different commands' is Rachio's own count, recorded as their claim rather than as a verified inventory. It runs through Rachio's cloud, so it stops working when your internet does.
✓ Google Home: Works — Rachio connects the Rachio 3 to Google Home when you link your Rachio account through Works with Google in the Google Home app. Rachio's help page for the Rachio 3 lists what Google can do: "Hey Google, start watering" runs every active zone for three minutes, and "Hey Google, stop watering" stops it. Picking a single zone by voice is described only for Alexa. Rachio says this works only on a controller owned by your Rachio account, not one shared with it. It runs through Rachio's cloud, so it stops working when your internet does.
✗ Apple Home: Doesn't work — This is the single most-repeated false claim about this product, and it has been false since 2022. Rachio added HomeKit support to the Rachio 3 in 2018 and marketed it heavily; retail listings, buying guides and older reviews still describe it as 'Apple HomeKit compatible'. Rachio suspended it indefinitely on 2022-10-03 after failing to resolve persistent 'No Response' errors, stating: 'We are suspending this work indefinitely. We did not make this decision lightly. Although it seems like we have come closer to determining the root cause, our recent findings have led to more unknowns than answers.' The company offered to reimburse the full cost of the controller to any owner who could not use HomeKit and preferred a competitor's product; that return programme was itself closed on 2023-09-29. Rachio's current product page names Alexa, Google Assistant, IFTTT, Alarm.com and SmartThings and contains zero occurrences of 'HomeKit', 'Apple' or 'Siri' — the marketing was withdrawn along with the feature. We could not confirm a Matter certificate for Rachio. So this is a positive 'none' rather than a silence: the vendor removed the capability, said so, and paid people back.
◐ SmartThings: Works per the maker; details unconfirmed — Rachio lists SmartThings only by name, in a line that reads "Works with, Amazon Alexa, Google Assistant, IFTTT, Alarm.com, SmartThings and more." It does not say how the controller connects to SmartThings or which controls SmartThings gets, so starting a zone and turning watering on and off are unconfirmed there.
✓ Home Assistant: Works — Home Assistant ships an official Rachio integration — not a community add-on — and it is unusually complete for a cloud irrigation product: switches for zones, valves, schedules, standby mode and rain delay, binary sensors for system status, and calendar entities. Its IoT class is 'Cloud Push', which is the good end of the cloud spectrum: Home Assistant is told when something changes rather than polling for it. The catch is what push costs you — Home Assistant's own documentation states that for switches and sensors to update in real time, 'your Home Assistant instance must be accessible from the internet, either via Home Assistant Cloud or another method', because Rachio's servers deliver the updates by webhook. So the local-first crowd gets an official integration that is nonetheless not local in any sense, and requires exposing their instance or paying for Nabu Casa. Introduced in Home Assistant 0.73 and reported by Home Assistant's own analytics as running on 1.3% of active installations.
Connection: Wi-Fi · Hub for full use: No (No hub. The controller joins your Wi-Fi directly and everything else runs through Rachio's cloud — the voice assistants, the weather-based schedule skips, and the Home Assistant integration all talk to Rachio's servers rather than to the box on your wall. There is no local way to control it, so an internet outage is a loss of remote control, not just of convenience features.) · Works offline: Partly — some of it keeps working without the internet and some of it does not
?InconclusiveAmazon Alexa: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveGoogle Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveApple Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
✗Doesn't workHome Assistant: Verified: does not work with this ecosystem
Wi-Fi
No
?
—
Worx Landroid Vision Cloud — the catch, per ecosystem ~$1199.99 $1,199.99 is Worx's own US store price for the quarter-acre model (WR310.1) on 2026-08-21, shown in stock. The full ladder from Worx's own models page the same day: quarter acre $1,199.99, half acre $1,799.99 (WR320.1), one acre $2,299.99 (WR340). The entry figure is recorded because it is the cheapest way into this product; a buyer whose lawn needs the one-acre model pays nearly double, so the ladder matters more than the single number. Price at time of research.
? Amazon Alexa: Inconclusive — Worx names no smart-home platform anywhere we read: the product page, the models comparison page and the Vision technology page. Recorded as unknown rather than 'no', because silence on a sales page is not the maker saying there is no route, and mower makers add voice skills between app releases. The trap on this product is that Worx does sell something called Voice Control, and it is not this: it is a paid hardware module that clicks into the robot and understands speech on the device itself, with no internet involved. It is the mower listening to you in the garden, not your assistant talking to the mower. A buyer searching 'robot mower voice control' will find that option and reasonably conclude the opposite. As of 2026-09-02 Worx has removed its US page for it; the European page is still live and still ranks, so the confusion now arrives from a foreign-market page.
? Google Home: Inconclusive — Same silence as Alexa, from the same pages, and the same reasoning: unknown, not 'no'. See the Alexa entry for the Voice Control trap, which is the thing most likely to mislead a buyer here.
? Apple Home: Inconclusive — No Apple route is documented and none is claimed. Held at unknown rather than closed as 'no': we did not check the Matter certification database for this mower, and robot mowers are in any case outside what Matter covers today, so the honest position is that the question was not answered, not that the answer is no.
? SmartThings: Inconclusive — Nothing on Worx's side, and nothing sought on Samsung's. Unknown.
✗ Home Assistant: Doesn't work — Home Assistant ships an integration literally called 'Worx Landroid', and it does not cover this mower, which is exactly the trap worth publishing. Its own documentation says it reports state, battery level and error status for the Worx Landroid WG796E.1 or WG797E, older wire-guided models set up by typing the mower's network address by hand. It names the models it drives, and the Vision Cloud line (WR310.1, WR320.1, WR340) is not among them. Recorded as 'no' on that basis, the same one we use whenever a platform lists its supported models and this one is absent. A buyer searching 'Home Assistant Worx Landroid' will find a green integration page and reasonably conclude their mower is supported.
Connection: Wi-Fi · Hub for full use: No (No hub, no boundary wire and no antenna to site in your yard — Worx's own line is "No boundary wire, no antenna, no hassle", and the RTK correction that replaces the antenna comes over the internet from Worx's service rather than from hardware you mount. ⚠ What replaces the hub dependency is a COVERAGE dependency, and it is the most important thing on this record: Worx puts an "Is RTK available at my address?" checker on the product page itself, which is a vendor telling you in advance that the service may not reach where you live. Check it before ordering. No third-party hub, bridge or controller is involved anywhere, and none would help.) · Works offline: Not checked — we have not established whether this keeps working without the internet
◐PartialAmazon Alexa: Partial support — see the catch
◐PartialGoogle Home: Partial support — see the catch
✗Doesn't workApple Home: Verified: does not work with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi · Bluetooth · Cellular
No
?
—
Segway Navimow X315 — the catch, per ecosystem ~$1999 $1,999.00 on Navimow's own US store, read 2026-08-05, with a working Add to cart control and no strikethrough or compare-at price — so this is the regular price rather than a promotion. Worth knowing before you compare quotes elsewhere: the X315 is the entry model of a four-model page, and the other three variants on that same page are the X330 at $2,299.00, the X350 at $2,799.00 and the X390 at $4,499.00. A '$2,299 regular price' attached to this mower in a third-party listing is the X330's figure, not a discount on this one. Note also that Navimow's own X3 specification table publishes MSRPs of $2,799 / $3,499 / $4,999 for those three larger models — higher than what the store charges for them — so the manufacturer is running store prices below its own stated MSRP across the line. No MSRP is published for the X315 at all.
◐ Amazon Alexa: Partial — Confirmed first-party on this model's own product page, and unusually specific about what the voice commands actually do — which is the opposite of the usual finding in this category. Navimow publishes it as 'Mow with Voice Commands: Enhance convenience with Alexa and Google Home voice control for managing mowing tasks. Start, stop, or schedule effortlessly', and the specification table carries a 'Smart Home Integration: Alexa & Google Home' row. Naming start, stop and schedule is a real capability statement, not just a badge. Recorded partial rather than full for two reasons. First, three verbs is a fraction of what the app does — nothing published suggests you can set a cutting height, pick a zone or query progress by voice. Second, and more concretely: the specification table that carries the Smart Home Integration row has no X315 column, so the row is a series-level statement, and this model's own feature copy is what actually pins it to this mower. Both sources say the same thing, which is why the cell is not 'unknown' — but the depth behind it is unpublished.
◐ Google Home: Partial — Identical footing to Alexa, and named in the same breath every time it appears — 'Alexa and Google Home voice control' on this model's feature copy, 'Alexa & Google Home' in the specification table's Smart Home Integration row. That parity is itself the finding: Navimow documents both platforms to exactly the same depth, and the same three verbs (start, stop, schedule) are all that is published for either. Partial for the same reasons — a real, vendor-stated integration whose scope stops at three commands, on a series-level row that does not have this model in its columns.
✗ Apple Home: Doesn't work — Not supported, and the shape of the evidence is worth stating rather than hiding. Navimow names its smart-home support explicitly and twice — 'Smart Home Integration: Alexa & Google Home' in its specification table, and 'Mow with Alexa and Google Home' as a feature heading — and Apple, Siri and HomeKit appear nowhere on any Navimow page read for this record. That is a vendor enumerating what it supports rather than a vendor answering the Apple question, which is a weaker form of evidence than an outright 'not with Siri'. It is recorded as 'none' anyway, because the structural check agrees with it from the other side: there is no Matter route either, because no mower of any brand can currently take one — Matter has no robotic-mower device type through release 1.6. If you run an Apple household, this is a phone-app product, controlled through the app, with Siri having nothing to say to it.
? SmartThings: Inconclusive — Unknown, and deliberately not turned into a 'no'. Navimow's specification table answers the smart-home question with exactly two names, 'Alexa & Google Home', and SmartThings is not one of them — but a maker listing two things it supports is not a maker saying it doesn't support a third. We found no Samsung documentation naming a Navimow mower either, so neither side speaks, and the honest answer is unknown on both. One forward-looking note that makes this more than a formality: Navimow advertises upcoming open access for outside developers to the X3 Series' Expansion Bay, and that kind of openness is exactly what lets a third party build a connection the maker never announces.
? Home Assistant: Inconclusive — Nothing established on either side, which is a genuinely different answer from the other mowers we cover and worth being precise about. Home Assistant has no Navimow or Segway integration — there is no integration page for either name — so there is no official route, and no community-built add-on has been promoted into Home Assistant's own list either. Navimow's own pages don't mention Home Assistant anywhere. We don't treat that as a 'no', because a robot mower with a documented cloud service is exactly the kind of product a community add-on appears for without either company announcing it, and Home Assistant's own list doesn't tell you what exists outside it. So it stays unknown. Compare the Husqvarna mower in the same category, which has an official Home Assistant integration deep enough to set cutting height and switch work areas — if Home Assistant is where your automations live, that difference is the most important line on this page.
Connection: Wi-Fi · Bluetooth · Cellular · Hub for full use: No (No hub, and no boundary wire either — this is the wire-free half of the category. Navimow states the app 'supports Bluetooth, Wi-Fi and 4G' for activation and control, so the mower has all three radios and does not depend on any single one of them the way a cellular-only mower does. Setup is wire-free in Navimow's own framing: 'Effortless wire-free setup in just three steps, without needing professional help', with the app mapping the lawn automatically rather than you walking a perimeter. What replaces the wire is satellite positioning — Navimow's EFLS 3.0, which combines RTK with visual mapping (VSLAM) and visual-inertial odometry. Where Network RTK coverage reaches, that needs no antenna at all: 'Where Network RTK coverage is available, there's no need to install a local antenna.' Where it does not, you are installing and siting a physical RTK reference antenna, and Navimow ships a coverage checker on its own site precisely because the answer is address-specific. Check your postcode before you buy — this is the single fact that decides whether setup is a one-hour job or a mounting project.) · Works offline: Not checked — we have not established whether this keeps working without the internet
?InconclusiveAmazon Alexa: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveGoogle Home: We researched this and the evidence doesn't settle it — the catch explains why
✗Doesn't workApple Home: Verified: does not work with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi · Cellular
No
?
Optional*
Mammotion LUBA 3 AWD — the catch, per ecosystem ~$2399 $2,399.00 is the LUBA 3 AWD 1500's price on Mammotion's own US store, re-read 2026-09-27 and unchanged, and it buys the smallest of three very different machines sold under one product name. ⚠ THE LADDER HAS MOVED SINCE 2026-08-05 AND THE SHAPE OF IT NOW MATTERS MORE THAN THE HEADLINE. As published on 2026-09-27: LUBA 3 AWD 1500 (0.37 acre) $2,399.00 with no comparison price · LUBA 3 AWD 3000 (0.75 acre) $2,109.00 against a struck-through $2,799.00 · LUBA 3 AWD 5000 (1.25 acres) $3,299.00 with no comparison price. The 3000 was $2,799.00 in August. So while the discount lasts, the middle machine — twice the acreage, and the one that ships with the RTK reference station and the free lifetime iNavi service the 1500 is excluded from — costs $290 LESS than the entry model. A buyer comparing on the headline figure alone would reach for the wrong one. The $2,399.00 figure is kept as this record's price because it is the 1500's ordinary, undiscounted price and the 1500 is the configuration this record describes; the 3000's number is a promotion with a stated regular price behind it, which is a different kind of fact. Each model is offered in a High Version (2.2"–4.0" cutting height) and a Standard Version (1.0"–2.7") at the same price, so the cutting-height choice costs nothing but is not reversible after purchase — and on 2026-09-27 stock decides it for you: Mammotion's store sells the 1500 only in the High Version, and the 3000 and 5000 only in the Standard Version, with the other version of each shown out of stock. The 5000 was recorded out of stock from 2026-08-05 to 2026-09-21; its Standard Version can be ordered again.
? Amazon Alexa: Inconclusive — Not established, and this is the finding that most separates this mower from its direct rival. Mammotion's own product page for the LUBA 3 AWD names no smart-home platform at all — Alexa, Google Home, Apple, SmartThings, Home Assistant and Matter each appear zero times across the full page. That silence is total rather than selective, which is why this is 'unknown' rather than 'none': a vendor that lists two platforms and omits a third has told you something, whereas a vendor that mentions none has told you nothing, and Mammotion sells this product entirely on its app. Compare the Navimow X315 at a similar price, which states 'Alexa & Google Home' first-party and says what the commands do. If voice control is why you are buying, this record cannot confirm you will get it.
? Google Home: Inconclusive — Identical footing to Alexa, and for the identical reason: Mammotion's product page names no smart-home platform anywhere, so there is nothing to record on either side. Not converted into a 'no' — total vendor silence on the whole category of integration is an absence of evidence, not evidence of absence, and this catalogue does not turn one into the other.
✗ Apple Home: Doesn't work — No route, and the evidence is an absence rather than a vendor statement — which is stated plainly because it is a weaker kind of finding than a vendor answering the question. Apple, Siri and HomeKit appear nowhere on Mammotion's product page for this mower; neither does any other smart-home platform, so this is not a case of Apple being conspicuously left off a list. It is recorded as 'none' rather than 'unknown' because the structural check agrees from the other side: there is no Matter route either, because no mower of any brand can currently take one — Matter has no robotic-mower device type through release 1.6. If you run an Apple household, this is a phone-app product and Siri has nothing to say to it.
? SmartThings: Inconclusive — Not established. Mammotion names no smart-home platform on the pages read, and no Samsung documentation naming a Mammotion mower was located, so neither side speaks. Recorded unknown on both.
? Home Assistant: Inconclusive — Not established. Home Assistant ships no Mammotion integration and Mammotion names Home Assistant nowhere. Several community add-ons aim at LUBA mowers, with start, pause, stop and return-to-dock controls, but neither Mammotion nor Home Assistant stands behind them, and their own setup advice is a second Mammotion account shared to the mower, because signing in with your main account logs the official app out.
Connection: Wi-Fi · Cellular · Hub for full use: No (No hub and no boundary wire — Mammotion's whole pitch is 'No Wire, No RTK Installation' — but read that second half carefully, because it is only true of part of the range. Navigation is what Mammotion calls Tri-Fusion Positioning: '360° LiDAR + NetRTK + Dual Camera AI Vision'. NetRTK is network-delivered positioning that removes the need for a physical antenna, and it is exactly what the paid iNavi service provides. The 1500 is the model that genuinely needs no RTK install — it works on LiDAR and vision 'without the need for RTK/NetRTK' — and Mammotion's own box contents confirm it: 'LUBA 3 AWD 1500/1500H does not include the RTK reference station, RTK Antenna, RTK Extension Cable or RTK Power Supply.' The 3000 and 5000 ship all four of those parts in the box, which is a physical install with a sited antenna, and separately get iNavi free for life so they can skip it where network coverage reaches. Connectivity is the other thing to understand. Mammotion publishes a 'Built-in 4G Module' on every model and its own service terms recommend Wi-Fi for unlimited yard monitoring, so both radios are present. What is NOT published anywhere this catalogue could find is a plain connectivity specification listing Bluetooth — Mammotion's comparison table is delivered client-side and returns no specification content to a direct request, so no Bluetooth claim is made here.) · Works offline: Not checked — we have not established whether this keeps working without the internet
◐PartialAmazon Alexa: Partial support — see the catch
◐PartialGoogle Home: Partial support — see the catch
✗Doesn't workApple Home: Verified: does not work with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
✓WorksHome Assistant: Works with this ecosystem
Bluetooth · Cellular
No
?
—
Husqvarna Automower 435X AWD — the catch, per ecosystem ~$2999.99 Husqvarna publishes $2,999.99 for this mower on its own US product page, labelled as the suggested retail price and read on 2026-09-19. The page itemises what that figure buys: the mower (part number 967 85 33-05), a charging station, six spare blades, 33 feet of low-voltage cable and a power supply unit. It also names what is not in the box, and it is the part a boundary-wire mower cannot run without — the loop wire and the stakes to peg it down, both bought separately. Read the figure as a suggestion rather than a checkout price. There is no add-to-cart control for the mower anywhere on the page; the purchase route Husqvarna offers is a dealer store locator, with professional installation available, and its published availability is in-store. So the dealer who sells and commissions the machine still sets what you actually pay, and Husqvarna attaches a validity date of 2026-10-20 to the published figure. This is the price at the time of this reading, not a standing quote. It is also a change: until this reading Husqvarna published no price for this mower at all.
◐ Amazon Alexa: Partial — First-party and real, and unusually well qualified for this category — Husqvarna states the requirement rather than just the brand name: 'Husqvarna Automower® models with cellular or Wi-Fi connectivity, or those equipped with the Automower® Connect Kit can connect to Google Home or Amazon Alexa.' This model has cellular, so it qualifies on the vendor's own terms. Recorded partial rather than full for one reason: nowhere does Husqvarna publish what the voice integration can actually do. The product page offers 'convenient voice control and status updates' and the smart-home page says you can 'control' the mower, and that is the whole of it — no command list, no statement of whether you can start, park, or send it to a specific work area by voice. The integration plainly exists; its scope is unpublished, and this catalogue does not assume a scope on a vendor's behalf. It runs through Husqvarna's cloud over the mower's cellular link.
◐ Google Home: Partial — Identical footing to Alexa, and named in the same breath by Husqvarna both times — 'can connect to Google Home or Amazon Alexa' on the smart-home page, and 'Compatible with Amazon Alexa and Google Home for convenient voice control and status updates' on the product page. That parity is itself the finding, and it is the opposite of what this catalogue usually sees: most vendors in the yard category document one voice platform properly and leave the other as a name in a list. Husqvarna documents both to exactly the same depth — which happens to be shallow. Partial for the same reason as Alexa: the integration is confirmed first-party and its capabilities are published nowhere.
✗ Apple Home: Doesn't work — The only first-party statement in this launch set where a manufacturer names the platform it does not support, and it is worth crediting. Husqvarna's own US smart-home page says it plainly: 'At present, you can control your Automower® robotic lawn mower with Google Assistant and Amazon Alexa, but not with Siri.' That is a positive 'none' — the vendor answering the question rather than leaving a reader to infer an absence from a list that stops short. There is no Matter route either: no mower of any brand can be a Matter device today because the standard has no robotic-mower device type through Matter 1.6. Note Husqvarna's own hedge, 'At present' — this is the company's current position, not a permanent one.
? SmartThings: Inconclusive — Not established, and deliberately not turned into a no. Husqvarna's smart-home page lists four ways to connect the mower — Google Home, Amazon Alexa, IFTTT and a published developer connection — and SmartThings is not among them. But a maker listing four things it does support is not the same as saying it does not support a fifth. That distinction matters more than usual here, because Automower Connect is an open platform that publishes how other software can talk to it, which is exactly the arrangement that lets an outside developer build a connector the maker never mentions. No Samsung documentation naming this mower was found either. So the honest state is unanswered on both sides rather than a no resting on a maker's silence.
✓ Home Assistant: Works — Home Assistant ships an official Husqvarna Automower integration — introduced in Home Assistant 2024.3, IoT class 'Cloud Push' — and it is the most complete platform integration on this record by a wide margin, which is the reverse of the usual pattern where the vendor's own voice integrations are the deep ones. It provides a lawn mower entity, a device tracker for the mower's position, a number entity for cutting height, a select for headlight mode, calendar entities for schedules, switches for work areas, stay-out zones and schedule enable, buttons to confirm errors, reset blade usage and sync the clock, and battery and error sensors. It needs a Husqvarna account with OAuth2 credentials and a mower with Automower Connect, so it is cloud all the way through despite the depth. Two documented limits, both stated by Home Assistant: 'The mower can only be started using the lawn_mower.start_mowing action during the schedules configured in the Automower Connect App' — so automation cannot mow outside the schedule you set in Husqvarna's app — and 'Stay-out zone handling is not supported for mowers equipped with EPOS technology', which does not bind this wire-boundary model but will matter if you compare it against Husqvarna's satellite-navigated line. Now the part that is easy to get wrong: Home Assistant ALSO ships a second, separate integration, husqvarna_automower_ble, introduced in 2024.11, which is genuinely local — 'This allows connecting and controlling an Automower without any accounts, cloud, or network connection.' It is built on 'AutoMower-BLE, an unofficial reverse engineered Husqvarna Automower Connect BLE library', and its documentation publishes no list of supported models, naming only the 305 as a pairing example. Whether it works with this mower is therefore not established, and this record does not claim it does. The cloud integration is what is documented for this model class, and that is what the 'full' rating rests on.
Connection: Bluetooth · Cellular · Hub for full use: No (No hub, and no home Wi-Fi either. Husqvarna states this model's connectivity as 'Bluetooth®, Cellular' — the mower carries its own SIM and talks to Husqvarna's servers over the mobile network, so the app, the voice assistants and the Home Assistant integration all work without the mower ever joining your network. That is unusual and mostly good: nothing in your house has to be online for the mower to be reachable. The cost is that everything remote runs through Husqvarna's cloud over a cellular link you do not control, and the local Bluetooth path is a separate story told in the Home Assistant cell below.) · Works offline: Not checked — we have not established whether this keeps working without the internet
?InconclusiveAmazon Alexa: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveGoogle Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveApple Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
✓WorksHome Assistant: Works with this ecosystem
Wi-Fi
No
?
Optional*
Hunter Pro-HC (Hydrawise) — the catch, per ecosystem
? Amazon Alexa: Inconclusive — Unknown, and the reason is access rather than absence — a distinction we insist on. Hunter documents an Alexa integration for Hydrawise in its support library, but that library is unreachable to us: the old Hydrawise support address now forwards to Hunter's main irrigation site, which refuses our reader outright. Neither of the two Hunter pages that DID answer — the controller specifications page and the subscription pricing page — names Alexa, Google, Apple or any voice assistant anywhere. So the position is that an integration is understood to exist and we could not read its scope from Hunter itself. Rather than describe what it can do from memory or from a search result, this stays unknown until the documentation can be read.
? Google Home: Inconclusive — Unknown for exactly the same reason as Alexa: Hunter's support documentation is closed to us, and the two pages of its own we can reach name no voice platform at all. We make no assumption that Google matches Alexa here — that assumption is one of the more common errors in this category, and Rachio's own page is the proof, documenting a detailed Alexa capability list next to a single vague sentence about Google.
? Apple Home: Inconclusive — Not confirmed either way. Hunter names no Apple platform on its own pages, and no bridge to Apple Home. The other route, Matter, could not be checked both ways: the certification body's product search no longer filters by name, and the Matter ledger lists no company called Hunter Industries or Hydrawise. A Hunter page naming Apple Home or Matter, or a Matter certificate for this controller, would settle it.
? SmartThings: Inconclusive — Unknown. No SmartThings claim appears on either reachable Hunter surface, and no Samsung documentation naming the Pro-HC was located. With Hunter's support library unreadable, silence on two pages is not enough to call this a positive 'none'.
✓ Home Assistant: Works — The most fully documented integration on this page, and it comes entirely from the other side — Hunter's reachable pages never mention Home Assistant. Home Assistant ships an official Hydrawise integration, introduced in version 0.71, giving you switches for automatic and manual watering per zone, valve controls with automatic shutoff, sensors for water usage, next scheduled watering time and remaining cycle time, and indicators for whether Hydrawise's service is reachable, whether the rain sensor is tripped and whether a zone is running. It works by asking Hydrawise's servers for an update at intervals rather than being told the moment something changes, which is the weaker of the two arrangements and means what you see can lag reality between checks. Home Assistant states the account requirement plainly: 'you must first set up an online account at https://app.hydrawise.com'. There is no way to control it on your own network alone.
Connection: Wi-Fi · Hub for full use: No (No hub. The controller has integrated Wi-Fi and connects to Hunter's Hydrawise cloud service, where the scheduling intelligence lives. Hydrawise accounts support multiple controllers, which is the design intent — this is a product line built for people who manage more than one site, and the free tier's controller limit is the first thing that reflects it.) · Works offline: Not checked — we have not established whether this keeps working without the internet
✗Doesn't workAmazon Alexa: Verified: does not work with this ecosystem
✗Doesn't workGoogle Home: Verified: does not work with this ecosystem
✗Doesn't workApple Home: Verified: does not work with this ecosystem
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
✓WorksHome Assistant: Works with this ecosystem
Bluetooth
No
Yes
—
Melnor 4-Zone Bluetooth Water Timer — the catch, per ecosystem
✗ Amazon Alexa: Doesn't work — No route, for the same structural reason as Apple. Melnor names no platform anywhere, and there is no hub, no account and no internet-facing service for a voice assistant to talk to — an Alexa skill needs something on the vendor's side to connect to, and this product has nothing of the kind. Recorded as a no rather than as unknown, because what is missing is not documentation but any way in at all. The radio it was built with is the whole reason: this timer speaks only Bluetooth, to a phone standing within about 30 feet of the tap, so there is nothing for Alexa to reach even from the next room.
✗ Google Home: Doesn't work — No route, identically to Alexa: no platform named by the vendor, and no cloud service through which Google Home could reach a Bluetooth-only valve. Recorded 'none' on the architecture rather than on silence alone.
✗ Apple Home: Doesn't work — No route, and the architecture rather than the vendor's silence is what settles it. A full-text read of Melnor's product page returns zero occurrences of 'Apple', 'Alexa', 'Google', 'SmartThings', 'Home Assistant' and 'Matter' — no platform of any kind is named. We could not confirm a Matter certificate for Melnor. And unlike a Wi-Fi product that could gain a cloud integration tomorrow, a Bluetooth-only timer with no hub and no account has no mechanism through which Apple Home could reach it. Recorded 'none' rather than 'unknown' on that combination — vendor silence, no Matter certificate we could confirm, and the absence of any transport that could carry such an integration.
? SmartThings: Inconclusive — Recorded unknown rather than none, and the distinction from the three cells above is deliberate rather than an inconsistency. SmartThings is the one platform that could in principle reach this device without a vendor cloud, because a SmartThings hub with Bluetooth radios could theoretically talk to a Bluetooth valve directly — the same shape of local path Home Assistant actually uses here. Whether any such support exists is not documented on either side: Melnor names no platform, and no Samsung documentation naming this product was located. So neither side speaks and the honest state is unknown.
✓ Home Assistant: Works — The finding of this record, and a genuinely surprising one: the manufacturer that names no smart-home platform anywhere is the one whose product Home Assistant supports officially and locally. Home Assistant ships an OFFICIAL Melnor integration — introduced in Home Assistant 2022.9, IoT class 'Local Polling' — and it is fully local: 'The devices are set up through Bluetooth and don't need any additional bridge or gateway.' It provides sensor and switch entities, and it discovers devices automatically once Home Assistant's own Bluetooth integration is running. The class match to this product is explicit rather than inferred: the documentation states that '1-zone, 2-zone, and 4-zone valves are supported', and this is the 4-zone valve. Two limits belong on the cell honestly. First, no model numbers are published — the support statement is by zone count and by brand (Melnor and Eden), so a buyer is matching a class rather than a part number, and this catalogue would rate the cell higher still if a model list existed. Second, and practically: Home Assistant must be within Bluetooth range of the tap, since there is no hub or cloud to bridge the distance — the same 30 ft constraint that governs the phone app governs this too, which for many gardens means a Bluetooth proxy rather than the server itself. Recorded 'full' because the integration is official, current, covers this device's stated class, and delivers the product's whole function; and 'local' because it genuinely is — this is the only record in the subcategory with a control path that touches no vendor server at all.
Connection: Bluetooth · Hub for full use: No (No hub, no account, no network — and unlike most 'no hub required' claims in this catalogue, that is not a marketing framing but a hard architectural limit that cuts both ways. The timer speaks Bluetooth to a phone and to nothing else. Melnor states the working distance plainly: scheduling happens 'from your smart device via the app within a 30 ft. range', and the app requires iOS 9 or Android 7.0 with Bluetooth 4.0. What you get is genuine independence — no vendor cloud, no hub to buy or power, no account to lose, and nothing that stops working when the internet does. What you give up is everything remote: there is no way to check or change this timer from work, from holiday, or from the other end of a large garden. The schedules themselves run on the timer, so it waters correctly whether your phone is present or not; you simply cannot reach it from outside those 30 feet.) · Works offline: Yes — the core function runs on the device or your home network
?InconclusiveGoogle Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveApple Home: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveSmartThings: We researched this and the evidence doesn't settle it — the catch explains why
?InconclusiveHome Assistant: We researched this and the evidence doesn't settle it — the catch explains why
Wi-Fi
No
?
—
Rain Bird ST8O-2.0 Smart Irrigation WiFi Timer — the catch, per ecosystem
✓ Amazon Alexa: Works — Documented by Rain Bird itself, though the document is old: its own press release names 'ST8-WIFI controllers' among the Alexa-enabled models and states that 'Users of Rain Bird controllers featuring the company's LNK WiFi Module can now talk to their irrigation systems', with 'over 180 commands and inquiries'. Setup runs through the Rain Bird app: enable Alexa in the app's settings and log into an Amazon account to enable the Rain Bird Skill. ⚠ The release is dated 14 February 2018, so this records a documented path rather than a re-verified current capability, and the current product page names no assistant at all.
? Google Home: Inconclusive — Not established on a first-party surface. Google, Google Home and Google Assistant appear nowhere on this model's Rain Bird product or support page, and the Alexa press release does not mention Google. Third-party listings do claim it; those are not used here. Recorded as unknown rather than none — the support page carries a 'Rain Bird® Smart Home Integration' document whose contents we could not read, and that is exactly where such support would be stated.
? Apple Home: Inconclusive — Not established. Apple, Apple Home, HomeKit and Matter appear nowhere on Rain Bird's product or support page for this model.
? SmartThings: Inconclusive — Not established. SmartThings appears nowhere on Rain Bird's product or support page for this model, and no Samsung-owned page naming it was read.
? Home Assistant: Inconclusive — Genuinely unsettled, and the reason is worth reading before buying. Home Assistant ships a Rain Bird integration whose IoT class is 'Local Polling' and which works against 'LNK WiFi module of the Rain Bird Irrigation system' using the device's IP address — a real local path. But it names the LNK module rather than this timer or its LNK2 successor, and it carries this warning: 'The new Rain Bird 2.0 App and Firmware is not compatible with Home Assistant. The upgrade process will migrate devices to require use of the new Rain Bird IQ4 cloud, and Home Assistant will not be able to access the device.' Whether a product Rain Bird itself calls ST8O-2.0 is on the far side of that migration is not stated by either party, so this stays unknown rather than being recorded as support or as a denial.
Connection: Wi-Fi · Hub for full use: No — verified that none is needed · Works offline: Not checked — we have not established whether this keeps working without the internet
Sorted by price, low to high — an objective order, not a ranking or a verdict. Tap any row’s + (or a phone card) to read every catch. ✓ works · ◐ works, with an exception · ✗ doesn’t work (verified) · ? not checked yet · ? inconclusive — we researched it and the evidence doesn’t settle it. ◇ brand claim — the maker states it for its range; we have not verified it for this model. In the decision columns, ? means the same thing — we have not established it, which is never the same as “no.” *Prices at time of research — never live prices. Data last verified 2026-10-08; every fact links to its sourced profile.
Don’t see the exact model you own? Two options, and they’re different:tell us and we’ll add it to the research queue (free), or get aSetup Check — a personalized, human-checked report that researches your whole list, including products we haven’t profiled yet.
Sprinkler controllers
Rachio 3 has an official cloud Home Assistant integration and specific Alexa commands. Google Home can start and stop watering on every active zone, while picking one zone by voice is documented only for Alexa. Its SmartThings functions are less established, and its former HomeKit support was suspended in 2022.
Orbit XR names Google without itemising commands. Orbit’s Alexa command list is filed under a different B-hyve controller and does not name the XR. Home Assistant support is not established through an official integration. Other controllers in the table have their own zone, wiring, sensor and account conditions; do not transfer a competitor’s route.
Hunter Pro-HC has an official cloud Hydrawise integration. Its free plan includes scheduled watering, while sensor-triggered irrigation and some reporting/notification functions need the paid tier. The maker does not publish a usable price for that tier in the record.
Hose timers
Rachio’s timer includes a hub and stores a limited number of run events on the valve. Voice and remote functions still need the hub/cloud route.
Orbit’s 24639 bundle includes a hub; 24634 does not. Both have on-device and nearby Bluetooth programming, but their platform answers are not interchangeable.
Eve Aqua is HomeKit over Thread, not a Matter model. It has nearby Bluetooth control and on-device schedules. Apple remote access and automations need a home hub. Home Assistant’s local HomeKit route requires removing the Apple pairing first, with a border router needed for Thread.
Melnor’s four-zone timer has nearby Bluetooth operation. Home Assistant’s official integration supports the brand’s valve classes by zone count, rather than exact part numbers. Confirm your model and Bluetooth coverage; it is not a documented remote app service.
Mowers
Navimow X315 documents limited voice commands and an address-dependent antenna requirement. LUBA 3 and mini 2 have exact-variant positioning and cellular-renewal conditions. Their unknown platform answers are not established exclusions.
Husqvarna 435X AWD has an official cloud Home Assistant route. Its free cellular-connectivity term has network/market conditions; it is not a promise of free service forever. A separate Bluetooth integration is not established for this exact model.
Worx Vision Cloud needs confirmed positioning coverage at your address. Home Assistant’s older Worx Landroid integration names other models and does not establish support for this line. See the mower comparison for the difference between positioning and remote service.
Before ordering
Check exact-model wiring, water pressure or lawn conditions, battery and winter-storage requirements, and any required professional installation. Manufacturer ranges and capacity figures are not SHWF measurements.
A Matter connection, a voice phrase and an accessory in Apple Home are different answers. Read the recorded caveat, then confirm any essential unknown with the manufacturer. The checker helps inspect the platform route.
Frequently asked questions
Does every hose timer have remote control?
No. Some use nearby Bluetooth, some need a separately purchased hub, and others include one. Check the exact bundle and remote-access conditions.
Does an official integration guarantee the exact model works?
No. Check whether its documentation names your model or a supported class, and whether it uses local control or a cloud service.
Sources for this guide· 17 product records
Product facts come from the linked research records; other cited sources appear below. Read each claim with its source date and any stated limit. Prices, features and support can change after a check. These are research profiles, not hands-on reviews.Report a correction if a source now gives a different answer.