I’ve been following this thread for a year now. Being in the software development world myself, I can’t imagine having an outstanding issue like this in my product, especially one that has many displeased customers posting on the public internet about it.
Personally, at about the second month of this thread I moved my Rachio to Homebridge and have never looked back. I realize that Homebridge is not for everyone, and that Rachio is a consumer product that shouldn’t need that kind of “tinkering” to get an advertised feature to work, but it has been a good solution for me.
What it comes down to, in my opinion, is that Rachio is not a software company; they are a lawn/landscape care company that felt like they could make a IoT product and be early to market with a compelling feature like Homekit integration. Their reliance on third party code and consultations with Apple and their vendors to attempt to find a solution shows this, in my view. Since we know the first version that broke, and the last version that worked, doing a simple compare of the code differences between those versions should at least shed light on the issue, if not point it out explicitly.