301 Access Denied on person/:id

post by decompiled on Apr 6, 2022

Hi there,

I’m just getting my new Rachio 3 setup and wanted to add it to my Home Assistant smart home. It calls /public/person/info, retrieves my logged in user ID, and then attempts to call /public/person/PERSON_ID to get further information about my account. But that second call gets a HTTP 401 response with a JSON body indicating Access Denied. I can reproduce this in Postman as well. I am retrieving my API Key from my account settings and the call into /public/person/info works just fine. What am I missing?

post by daveoley on Apr 8, 2022

I was having the same issue. Do you have any of your zones’ vegetation types set to “Flower beds”? I found that when I change one of my zones to Flower beds, I get the Access denied message when calling any of the API calls.

post by decompiled on Apr 8, 2022

That was it – I changed my Flower Bed zones to Shrubs or Perennials and the issue went away. Thanks!

Seems like a bug on Rachio’s end still. But glad I have a workaround.

post by dane on Apr 11, 2022

Thanks for flagging this! We’ve identified the issue and we’ll pushing out a fix.

post by VACInc on Apr 14, 2022

Any idea when the fix for this is coming?

post by dane on Apr 14, 2022

This will be fixed soon. While I cannot give an exact date, I’m confident the fix will be released in the next couple of weeks. The team was able to get it into the current sprint and is actively engaging it right now. I will update here in the thread once the fix has been rolled out.

post by VACInc on Apr 14, 2022

“current sprint” works for me! Thank you for the quick response and transparency @dane

post by jnewland on Apr 14, 2022

I also ran into this today, and was guided here by a helpful support rep. Changing my zones from flower beds to shrubs fixed the 301 errors I was seeing previously.

post by dane on Apr 20, 2022

Hi @VACInc @jnewland @daveoley @decompiled

This should be resolved. Please let me know if you are still having issues.

Best.