One thing I notice in your configuration, and something I neglected to convey in mine… I actually removed one of my Eeros which made things run smoother, so now I only have 5 and probably only need 4… but I have 3 of the 5 hardwired via Cat6… one on each floor and then the 2 that are meshed via wireless are peripheral…
As hard as that may be perhaps you might try figuring out how to get some of the mesh backhauled via Cat6? See if that helps…
Another thing… When I switched from Apple to Eero, I started with a new Apple Home as well… Took days with that many devices, but I felt it was worth the effort and so far it seems to have been.
Lastly, We have 1GB down and 40MB up, through Spectrum… but their service is terrible, goes out multiple times per week and sometimes things don’t recover well when that happens. So, I do end up having to reboot my network about once every 6-8 weeks or so…
Oh, and I have a reserved IP address for every Smart Device on my network…
For instance things like routers, wifi mesh nodes, ip phones, storage area network devices and printers are on the 192.168.5.0 network between .1.2 & .1.99, desktop computers and servers start at .5.1.100. Smarthome devices, TV’s, and Audio Equipment are on the 192.168.6.0 network… transient devices like cell phones and laptops are not reserved and hook at the 192.168.7.0 network, but everything is on the same 255.255.240.0 subnet…
Thanks again! I can hardwire the non-gateway eero Pros with great difficulty. As a home built in 1905-1906, there are no chases between floors and cabling would either have to penetrate the floor/ceiling (frowned upon by the Historic Commission), or penetrate outer walls and run up the exterior (frowned upon even more). So WiFi is it and hence my multiplicity of eero Pros. But backhaul is a real issue and you make a good point. Possibly eero tech support could be helpful to me.
As to a new Apple Home, I never used Home at all on the previous Apple network, so for me with the eero network it was a new setup. And I’ve “Removed Home” from the app and restarted everything from scratch at least 5 times…no joy. I’ve kept iOS up-to-date (now on v13.4.1) on all iOS devices so Home should be whatever is the most current version as well.
I’ve rebooted current and all previous routers about once a week. Shouldn’t be necessary but I’ve found performance tends to improve just after a reboot on every router I’ve had. I’ve asked the ISP to reboot my modem occasionally (I can’t get to it) but have seen no real need to do so…just a troubleshooting step to eliminate a possible trouble source.
I do like your IP addressing schemes and dedicated addresses. I’ll try that as a next step…something I’ve never done so that should be both a learning experience and reason for addition adult beverage consumption.
Thank you again for taking the time to assist…very encouraging!
@TTeuer So why not backup to before 631??? What was added after that, that was so great, worth keeping this issue broken for this long…
It sounds like they just don’t want to fix it…
But then that makes me wonder… if I dig out one of my old Apple Airports, setup a hidden WiFi access point backhauled to the same network as my Eero network via Cat6, and connect my Rachio exclusively to that hidden WiFi network which will actually be on the same network… maybe that might keep it connected? Has this been attempted?
Running into same problem since installing 631 firmware
I removed the Rachio from HomeKit, and now trying to reinstall it, entered the8 digit code, and not finding the accessory. Why did this firmware BREAK more than it FIXED?
@franz how is this going? For over a year homekit hasn’t worked and rachio’s response has ranged from, “i don’t know what is wrong” to “we almost have a fix” to “it is apple’s fault”.
When I use your developer apis, I see "homeKitCompatible":false,"model":"GENERATION3_16ZONE","name":"Rachio",
Which looks like homekit has been disabled. So it makes sense that Rachio is never discovered in the Home app. What is your plan for fixing the problem and what is the timeframe?
Yeah, this is absolute garbage… My Rachio 3 has been up and down for the past year, and for a product that is advertised with Homekit support this is unacceptable. However since it decided to update itself to firmware 631 it is not even working with HomeKit at all. At least previously I could reboot it and get a day or two out of it. In fact I installed a smart outlet so I could remotely power-cycle it to force it back online.
I too have a full Ubiquiti network installed with multiple access points, but I do NOT accept this is the problem, as the Rachio is always accessible via the app and online.
I agree that HomeKit support is basic at best, but that is all I wanted it for. The ability to be working in the garden and issue a Siri command to water or stop watering a zone that I am working on it the whole reason I bought it.
I agree with the earlier comment that a year down the track Rachio is still blaming Apple is garbage. All of my other devices just work - Rachio does not. This and the fact that the 631 firmware completely broke HomeKit integration tells you it’s Rachio’s problem.
@franz to whom should we direct a request for a refund on a faulty product?
Great post. @MaydayDarkhorse
An app update came out today on IOS. You would think they would have fixed this issue. Nope. Still can’t add Rachio v3 to the Homekit, and Rachio remains silent on a fix. Pathetic. And I have neighbors who I was going to recommend this product to…
Try reserving it address for each MAC address for each device in the system, but then make sure you change the dhcp range for the router outside of the numbers you set the reserved ips to.
Example, set the router dhcp range from .10 through .100. Reserve your ip addresses in that range. Then change the dhcp range to .101 to .254…
That’s an example… I have had to do this myself as sometimes t\routers seem to have issues with identical devices on my router, even if they have different Mac addresses. This got me around that issue. Could be some of your issue.
Back to this HomeKit issue. I can’t get mine added to HomeKit either right now.
I’d suggest they look through all their code from the previous software to this one and see if anything in there changed to cause this.
I have a feeling there is more than one thing going on here. Could be mesh systems have issues, which has caused issues for some, and the new firmware caused more issues and hit everyone.
While HomeKit is important to me, it’s not making or breaking the product for me. The best part is I don’t have to hardly ever do anything with it in the first place.
I can say with absolute certainty that if one of my mobile devices, especially my cellular Apple Watch, is on the same network as the controller when I leave my house and my device switches from my house WiFi to cellular it will often knock the controller offline from HomeKit. I’ll see all my other devices as they switch to connecting cellular will say updating and even say offline for a brief time but the controller will often stay offline. My workaround has been to place all my mobile devices on my 5ghz network and the controller on my 2.4 ghz network. But my Apple Watch will only do a 2.4 ghz network so I just leave WiFi off on it but if the watch is updated it turns wifi back on and if I forget to turn it back off it will knock the controller offline.
We’ve determined that the HomeKit integration has difficulty connecting to mesh/merged routers, depending on the physical configuration of the home network.
There is a way, however, to try to remedy this situation and re-establish the communication between your controller and HomeKit. To give it a try, please follow the steps below:
Factory reset the controller without removing from the Rachio account, using just the buttons (How do I factory reset my controller?) You will not lose any settings.
Its obvious they don’t know what is causing the issue, as this seems to be a canned response FYI, I do not have a mesh router/system, the HomeKit has worked fine for the 1 1/2yrs i have had it connected with my rachio, no hardware changes occurring, only major change was the latest firmware update to to rachio. 60 other random IOT devices in my home have 0 HomeKit issues, so it can be narrowed down to an issue with the rachio FW. Also, the steps outlined above did not resolve the issue. Only resolve will be issuing a fix firmware.
Also - the regular Wi-Fi connection (aside from HomeKit) is rock solid and never gets dropped…and I’m guessing they aren’t using a completely separate Wi-Fi radio to connect to HomeKit. Seems a bit odd to blame this on network topology when they are able to handle the same topology with their regular Wi-Fi implementation.
Firmware 631 broke everyone’s controllers integration with HomeKit. —> • <— period. The least Rachio could do would be to roll back to 615 (or whatever FW it was before 631) and let those of us that can make it work get it working. It would at least show that they care enough to work with US and not Jack with us With the same troubleshooting steps they have been suggesting for over a year
