I would as well!
1 Like
My controller has been offline for a couple of days now. The 10 second technique hasn’t worked for me this time. My controller is running 632, so I’ll wait for the next fix before attempting to reconnect again.
rpn314: It might have started before firmware 632 was released, I’m not sure. I just happened to notice about a week or so ago that it was it was showing “Not Responding” (I hadn’t thought about turning on my irrigation system before then, so I didn’t pay attention). Anyway, that’s when I discovered this thread.
Can someone (particularly the Rachio engineers) respond to the IPv6 issue I raised in my previous post. I found it VERY surprising that (according to the Network Analyzer App) of the 14 HomeKit devices I have on my network, my Rachio 3 is the ONLY one that does not appear to be IPv6 compatible. I believe IPv6 compatibility is required for HomeKit (not sure when that requirement went into effect).
So, is the Rachio 3 IPv6 compatible? If not, was iIPv6 removed (accidentally) in the 632 Firmware update?
Any info would be appreciated.
Thanks!
Jay
Firmware 615 was the last version to work with HomeKit - Not for everyone but for many it worked… V631 broke HomeKit for everyone as far as I know. V632 didn’t help HomeKit but brought other functionality… Franz, the Co-Founder / CTO at Rachio and his new engineer Michael are working hard on this. Lets give them some time… I know, I know… it’s been over a year. I started this thread but, let’s let them work the problem… I’m confident they will fix this.
1 Like
Glad to find this post after wasting an hour today trying to get mine back into the Home app.
Not sure when it disappeared but I guess it happened after an auto update of the device (Rachio).
Any timeframe for fixing this?
Connecting spins and spins and spins and spins…
@Michael_I I would be glad to help test the beta version. Please add me to the list.
1 Like
Laura, is there something special that has to be done for it to work with mesh routers? I have a mesh setup at my house and I can’t get my Rachio to show up. I reset it (using the stop button) and reconnected it to the network. It shows up in the app and seems to be otherwise fine, but it’s not broadcasting as a device in HomeKit. I have google wifi, if that makes a difference.
Afternoon everyone. Here is our update for May 8th, 2020 for our work to solve the HomeKit connectivity issue.
Our WiFi chip manufacturer originally had their own interface with the Apple Development Kit (ADK) that interfaced with HomeKit. In their latest version, they are asking us to go directly against the ADK.
They have provided us an example of how to go from their version of HomeKit with their legacy approach to the new direct to ADK approach. The engineer working on the solution was able to replicate the issue some of you have reported in the example project. We have reported this experience to our chip manufacturer and they are investigating. In the meantime, our team is continuing to examine the new ADK and our implementation so we can understand how to integrate with the ADK directly once the issue has been resolved.
That’s where we are this week, thank you for your patience. We are working to resolve this as quickly as possible. I am trying to balance being transparent and providing details without being overly technical. Please let me know if you have any questions or if my updates are too in the weeds.
Thanks everyone, thank you for being Rachio customers and have a fantastic weekend.
Michael
2 Likes
Thanks for the update Michael.
*This question has been asked before… I looked back and never saw an answer… Please let me ask again - Since a previous firmware version (615) worked for many (not all) users, is there anyway to roll back to that version in the interim? If nothing else, it may help to provide some answers…
If this is not possible it’'s not a problem -but- I DO think that v 631 was the moment that HomeKit integration became broken for most if not all users…
Is this possible?
3 Likes
These are great! Of course I wish we had a already (as everyone else here) but I appreciate the status updates. And no, they’re not too in the weeds; I’d be happy if they were even more technical. A TLDR for those who don’t want the full technical details with the full details would be a good balance I think.
YES!! PLEASE!!
1 Like
Thanks @rpn314, a tl;dr at the top would be a helpful addition to the status updates. Let me check on rolling back to a previous firmware version and get back you.
Appreciate the feedback and solution oriented suggestion!
Michael
1 Like
@rpn314 and @Macsterguy, after researching the issue, here is out suggested problem solving route:
Can you do a factory reset by holding the stop (up) arrow until the light bar fully turns yellow. Once the controller is reset, you will need to re-add to wifi, then pair their flow meter. All of your zone and scheduling data will remain intact.
If this approach doesn’t work, we can look at rolling back firmware. At a minimum you would still need to re-pair your flow meter and we have had cases where rolling back firmware can brick (make completely inoperable) your controller, so that is our last resort.
Can you try the reset and let me know if that solves the problem?
Thanks,
Michael
Hello Michael,
I have tried that exact factory reset procedure a number of times in the past. As many as 5 times just since the last update: iro3–firmware-hk-5-632
I may have been one of the first users to try v 632. Franz pushed it to my controller before it was announced you were working this problem with Rachio.
I am willing to try again but confident 631 AND 632 will not work. I really do think the last time users had HomeKit functionality was with v 615
Are you willing to take on the risk of going back to 615?
Thanks.
What are the risk that going back to 632 wouldn’t fix?
I suspect he’s referring to this, but I’m not sure why; as long as I haven’t fried the chip or destroyed the bootloader, I can always recover a bricked electronic (not referring to Rachio specifically, just in my experience with STM powered devices and computer BIOSes) and install a firmware that works. Even with a destroyed bootloader if you have a programmer it’s usually fixable.
Hey @Macsterguy, just to confirm you are on 632 correct? I was referring to the risk of going from 632 back to 615. There is a risk that going backwards can brick your controller and that is the risk I was referring to. Apologies for not being clear.
Thanks,
Michael
We have reverted controllers back to 615 and none have experienced any type of bricking. Should be good in that area. 
1 Like
I’m good to go to 615 if there are no Insurmountable issues. I can test it all out this weekend
Sign me up as well