Jay,
Sorry for the delayed reply. Been busy with the holidays and I've done a fair bit of...experimenting...in an attempt to figure out what is going on.
Let's start with the basics -- I work in IT infrastructure (networking/communication is my thing) and have been using Insteon devices (and Indigo!) for about eight years now. At this point, I'm quite familiar with how the system should work, so please feel free to get as technical as you wish with me.
I followed your advice/suggestions first, but these steps had no effect on the behavior. That said, I've since tried a number of other things...and this is about to turn into a very long reply. (Sorry about that.)
Here goes...
First and foremost, following your lead, I've been focused on getting the wired thermostat itself to behave...in some manner that would be/should be expected. While only keeping it linked with the wired thermostat alone, I've not attempted any further programming/linking with the wireless thermostat throughout everything I've done/tried. Also, I've been watching closely and I do not have any communication errors or other red text appearing in the logs.
To date, I have gone so far as to remove both thermostats--completely--from Indigo (removed from all scenes, removed references to them in actions, unlinked, etc.). After having done so, I factory-reset both thermostats. Before doing anything else, I updated the program in the wired thermostat based on my preferences and schedule (although I'd prefer to just let Indigo control it -- more on this later). After having done that, I've tried in varying order (I've attempted this a few times now): 1. add wired thermostat back into Indigo 2. add wireless thermostat back to Indigo 3. link wired and wireless thermostats together. After every attempt, regardless of the order of adding/linking the devices, I still see the same/original behavior.
Out of frustration, at this point, I tried the procedure in the manual for linking the wired thermostat to another Insteon controller -- in this case, I used button 8 on a KeypadLinc I have installed here. I set the thermostat as desired, linked with the KPL, and linking seemed to work. I changed the settings on the thermostat to something else, pressed the button on the KPL and...viola...the thermostat jumped to the settings it had when they were linked. That said, linking with another Insteon device would appear to work as expected.
This all established, I am still seeing other bizarre behavior that I just can't explain on a (at least) daily basis. Even with the wired thermostat programmed (times at which changes in the set temperatures are expected), I still see the thermostats jump to different modes and/or temperatures at seemingly random times. I don't have these modes or temperatures programmed or linked to
anything, anywhere. The one pattern that I have been able to identify is that the mode typically advances by one when this happens -- so, for example, if set to "Heat" mode, they'll advance (just as if you'd pressed the Mode button) to "Cool" mode. If in "Auto" mode, they'll advance to "Auto program" mode. Of course, once they advance themselves to "Auto program" mode, a while later, they'll advance to "Off" mode (which has been just lovely to wake up to as the weather here has been sub-zero almost every night since Christmas -- I'm getting concerned about pets and water pipes!).
It's worth noting that I have these thermostats installed at my parent's house, as well. I tried many of these same processes/procedures there, too, just to rule out that it's something with these devices (since they're newer, I was thinking/hoping it was a firmware revision or something like that). They appear to behave the same way. In any event, I installed these thermostats for them about two years ago and they'd been complaining of behavior just like what I'm now experiencing for quite a while -- at first, I thought they were crazy, but now I'm seeing this for myself. I ended up creating an hourly trigger to reset the thermostats there to a known setting, which I'll likely end up doing here. When they work, they're great, but this unexpected behavior on a daily basis is just not acceptable. I'm pretty confident saying that these are the most unreliable Insteon devices that I have ever seen -- I know for sure that the Venstar Thermostat Adapter did not suffer from these problems. (The only reason I switched was because I wanted something that would work with the Insteon Hub Pro so that I could try out HomeKit...don't get me started on how that went...speaking of buggy Insteon products...) The only reason I bring this all up is because I don't think this is simply a botched install or bad device. I think this behavior is more or less typical of these things, which is just not acceptable behavior for any thermostat.
In any event, I hope all this information is helpful. I am happy to provide/share anything else regarding my hardware and/or experiences if/when needed.
Jay, is there anything we can troubleshoot/debug regarding programming the wired thermostat into a scene within Indigo? If there's a way to at least get that working, life would be much better. Creating an action to set each and every thermostat parameter works, but man is it tedious...
Hope you had a wonderful holiday!