Yes, it still only returns one temp. We designed both APIs to support thermostats that do support multiple temperatures even though the Venstar currently doesn't.

bluenoise wrote:Well, starting last night, I've got a new wrinkle.

I have a simple script called "Run Fan 30 Minutes" that does just that. When it cools off outside, I open some windows, close some interior doors, and it does a good job of bringing in cooler outside air, like a whole-house fan. Last night, I tried to run it from Indigo Touch and nothing happened. I tried a couple of times and also tried "manually" turning on the fan from the devices page. I then launched Indigo to check the log. It said there was no acknowledgement from the thermostat. I tried again from Indigo Touch and it worked fine. This isn't after Indigo exits and updates things during the process. All I did was launch the app and look at the log. Communication was re-established simply by opening it. I never lost communications with any other device.

This morning, I ran into exactly the same problem. Last night, I was running the previous beta. I updated to the latest last night, so this morning's version is b9.

So, now it seems launching Indigo resets my connection to the thermostat.

Here is the log snippet:

Code: Select all

Sep 30, 2011 7:29:12 AM
  WebServer                       Indigo Touch client connected from x.x.x.x
  Action Group                    Run Fan 30 Minutes
  Action Group                    Run Fan 30 Minutes
  Error                           "Thermostat" turn fan always on; send failed (no acknowledgment)
  Error                           "Thermostat" turn fan always on; send failed (no acknowledgment)
  Error                           "Thermostat" turn fan always on; send failed (no acknowledgment)
  Error                           "Thermostat" turn fan auto on; send failed (no acknowledgment)
  Error                           "Thermostat" turn fan always on; send failed (no acknowledgment)
  Error                           "Thermostat" turn fan auto on; send failed (no acknowledgment)
  Schedule                        Update Weather Variables
  Sent INSTEON                    "Thermostat" turn fan always on
  Sent INSTEON                    "Thermostat" turn fan auto on
  Indigo Cocoa client connected
  Sent INSTEON                    "Thermostat" turn fan always on
  Sent INSTEON                    "Thermostat" turn fan auto on
  Action Group                    Run Fan 30 Minutes
  Sent INSTEON                    "Thermostat" turn fan always on


I'm *this close* to just giving up on having an automated thermostat. Over the past several weeks, communications have just gotten worse to where I now seem to have zero communications between the Venstar and Indigo. For a while there, Indigo was receiving all button presses and temperature updates from the thermostat, but would not receive a single command from Indigo. Hats off to the good folks at Smartlabs for working with me, but we're nearly out of ideas. The latest thing Smartlabs suggested trying is swapping out the transformer that powers the thermostat, but I have little faith that's the problem and I'm tired of spending more money on getting it to work. I just don't know what else to do, but it is very frustrating.

Usually, I'm good at troubleshooting things, but this one has me stumped.

Bluenoise, have you tried a different access point, or moving your current one right next to the thermostat? I had no end of dropped commands until I put APs within just a few feet of the thermostats. And then they occasionally die or get flaky with no obvious signs.

hamw wrote:Bluenoise, have you tried a different access point, or moving your current one right next to the thermostat? I had no end of dropped commands until I put APs within just a few feet of the thermostats. And then they occasionally die or get flaky with no obvious signs.

Smartlabs swapped out my access point and I've tried it in the nearest available outlet, though that's about seven feet away through a wall. I'll try plugging my heavy-duty extension cord into the back of my 2414 and putting the AP on the other end right next to the thermostat and see what happens then. That should rule out or confirm any RF issues, I believe.

Also try temporarily unplugging all RF appliances/equipment you have in the house (cordless phones, Wi-Fi, baby monitors, mobile phones, etc.).

I think something may be up with my access point. I unplugged it for several minutes while I retrieved my long extension cord. When I plugged it in, the LED gave a brief red blink and the internal buzzer chirped. After that, no steady green LED. I clicked the set button a few times and it began chirping and blinking as if to pair with another, but I cancelled it. I tried a few other tricks with the set button and finally just unplugged it for another several minutes just to let it chill. When I plugged it in again, I got the red blink and chirp, but no steady light. Nonetheless, I tried re-adding my thermostat to my devices and it worked this time, which is a great thing.

I don't know what is the proper behavior of the LED on the access point, but I never see it light up or blink, even with Insteon traffic flowing through it.

I believe APs should blink whenever they see any traffic...

A cursory check shows mine do. They are on and turn off (or dim a lot) when they see traffic. Just my observed behavior.

Hmm...I wonder if my new access point is somewhat defective. It's currently working, but it's also sitting on the floor under the thermostat at the end of a long extension cord. When I move it away from the thermostat back toward where the cord is plugged in, communications becomes flaky at about 15 feet line-of-sight (no obstructions). The LED being always off makes me think it's not working at 100%. Is there some kind of full-reset for an access point?

Don't know - check with Smarthome.

Update:

It seems to be fixed! Here's what it apparently took to solve the problems I was having with my thermostat communications:

1. Reset thermostat adapter
2. Move Access Point closer to thermostat
3. Reset Access Point
4. Move 2414 to outlet on wall, thereby eliminating a potentially-noise power strip with its flickering neon light

Any one of these fixes didn't help, but all taken together seems to have done the trick. It's been working with 100% communications since last weekend!

just upgraded to Indigo 5, and can no longer control my thermostat. I have the access point for the thermostat (both Insteon, thermostat adapter 2441V, access point 2443). They both worked fine with Indigo version 4. I've set up the Access Point as a new device, but keep getting the 'cannot communicate' error dialogue box whenever I try to connect. Any suggestions?

John

Access Points are bridges - they don't need to be added to Indigo.

When you try to adjust something on the thermostat, what shows up in the Event Log window?

This is from the event log when I tried to modify the settings of thermostat:

"Thermostat" turn all off; send failed (no acknowledgment)
Error "Thermostat" mode request; send failed (no acknowledgment)
Error "Thermostat" temperature request; send failed (no acknowledgment)
Error "Thermostat" setpoint request; send failed (no acknowledgment)
Error "Thermostat" set heat setpoint to 68.0; send failed (no acknowledgment)
Error "Thermostat" set heat setpoint to 69.0; send failed (no acknowledgment)

This is from the event log window when I tried to link the access point:

PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
PowerLinc Linking - no id request response from device
PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
PowerLinc Linking - sending id request for device information
Error Linking - device failed to send identification information
Error linking failed
PowerLinc Linking - entered discovery linking mode (240 seconds)

Update: while I was posting my last response, I tried unplugging and replugging both the access point and thermostat controller, and everything seems to work. Note: I still have not officially set up the access point (doesn't really make sense to me). Will Indigo automatically recognize the access point without needing to set it up as a separate device?

As I said above - Access Points are bridging/repeating devices. They work automatically without any configuration in Indigo. Indigo doesn't need to know about them which is why you can't add them.