- Posted on
Thu Apr 05, 2018 5:38 pm
-
Professor Falken
offline
-
- Posts: 289
- Joined: Mar 29, 2015
As promised, I'm reporting back here with my experiences in case anyone else later has similar issues. I'm also having at least one lingering issue that I'm hoping someone might have some ideas on.
Rachio sent a gen2 controller to replace my gen1, which was great. This installed simply, and within their app/system was working correctly from the start, which I guess means something went bad in my gen1 causing it to act squirrelly. I wish they had a way to quickly import all the settings from an old controller rather than having to rebuild all zones/schedules/etc but that's a minor quibble. In fact, looking a the newest app update (just dropped yesterday, I think-- 36 hours after I needed it) they may have actually added this feature going forward.
Unfortunately, I was unable to successfully transfer my Indigo Rachio device to the new box. I reconfigured the Indigo device to the new controller (which Indigo could see), but it still wouldn't control the zones, etc. I noticed that it was still listing schedules from the old controller, for example, so I assume it wasn't able to fully make the jump to the newer box..
So I bit the bullet and just created a new Rachio device in Indigo. This necessitated a bunch of CP changes, as well as searching through a few scripts, but overall not that difficult. I think I found everything.
At this point the native controls in Indigo seem to be working (i.e., the ones on the device page). In addition, CP controls seem able to trigger zones correctly. I haven't fully tested schedules, as we've just had a rather cold snap here, but I'm assuming they will work.
About 24 hours after the above, I started getting those "too many API call" errors that others had reported. I thought this was odd since I had left the config untouched in the newest plugin version and understood those to be set below the max number/day allowed. It took me a few minutes to realize that the two Indigo Rachio devices were probably creating the issues. Deleting the old one (which now served no purpose anyway) seemed to solve that.
Which brings me to the one little thing I can't seem to fix...
On my sprinkler CP's, I have an image for each zone. It's basically a device state linked image set of a property map with sprinklers running in the correct zone. For some reason I can't quite get this to work correctly. Zones 1,2, and 3 show the correct image. Zone 4 shows the zone 5 image, and zone 5 shows the zone 4 image. Zone 6 (last zone in my system) shows the zone 3 image again. If I swap the zone 4 and 5 images (which you would think would at least solve that pair) they still show up reversed, even after restarting the app on my phone.
Even though I am keying on the "active zone name" device state, the images are named ...+1.png, +2.png, etc., as I learned last year (on a tip from Matt I think) that for some reason that's the way the plugin wants the images named. That's a bit weird, since if you display the exact same state as text instead of as an image, it will show the text name of the zone (not 1,2,3...). Just to see, I did try renaming the images with the actual zone names but none of them showed, so I guess it still wants the zone number on the png image names. I am pretty sure all the zones are named correctly-- you can look in the scheduling feature under actions, and it shows the zone names in the order of zone number (including the unused zones 7 and 8 in my system).
I am almost positive this is an issue with the image cache on Indigo Touch, because when I load the CP through a browser, all of the images behave correctly. Is there a trick to clear the cache on the iphone beyond force restarting the app? I also rebooted the phone without effect.