Lots of the INSTEON modules will send duplicates of commands, especially if it thinks that they aren't being received. Indigo tries to suppress the logging in some of these cases, but its time window for not showing them is relatively short (it is better to show too many than not enough).

You might try moving your dual-band modules or AccessPoint RFs around. That will change up the signal path and might help the problem.

So if there is noise on that circuit the module would somehow (??) be aware of that and thus increase the likelihood of multiple commands being sent? Or do these modules just send a bunch of commands routinely and some slip by Indigo's filtering?

I'm not sure.

I believe that some modules will broadcast out a command and then, if it doesn't hear that hopped by any modules (that is, it broadcasts and then there is silence), it will re-broadcast the command just to be safe.

Normal message hopping also causes lots of duplicates, but Indigo is good about suppressing the logging of those because it can see that the hop count is being decreased.

Forgive me if this has been covered elsewhere, but I just installed one of the new Rev 2.5 adapters. I'm seeing "current setpoint temperature unknown (ignoring adjust command)" log entries when I attempt to change the set point. If I look at the device in Indigo, it shows both heat and cool set points = 0. Known issue??

Temporarily change the mode to Auto, then send it a status request. Indigo is confused because it doesn't know the cool setpoint (it isn't always broadcast by the adapter).

matt (support) wrote:Temporarily change the mode to Auto, then send it a status request. Indigo is confused because it doesn't know the cool setpoint (it isn't always broadcast by the adapter).

Yup. that did it. Thanks Matt.

I recently installed the venstar 1 day insteon integrated thermostat and I've noticed that it's very spotty as to whether commands that are sent to the thermostat either directly from indigo server interface or through the indigo touch iphone app ever reach the thermostat. I've noticed also, that the thermostat seems to be able to send status updates to indigo fairly regularly as the temperature readings equipment status entries seem to appear in the activity log.

It appears that the communication with the thermostat is largely 1 way. I have not less than 20 dual mode devices fairly evenly spread throughout the house, with 4 in the same room as the troublesome thermostat. While I also see that it's triplicating and quadruplicating log entries, I'm more concerned with the inability to regularly control that thermostat.

Any thoughts?

Do you see failures in the log? Copy/paste a few of them in a reply if so.

Jay,
Thanks for the quick response. Below are a set of entries from this afternoon. The thermostat in question is "THERMOSTAT MASTER"


ep 21, 2012 4:40:23 PM
Received INSTEON "THERMOSTAT MAINFLOOR" humidity changed to 54.0
Received INSTEON "THERMOSTAT MASTER" temperature changed to 70.0
Received INSTEON "THERMOSTAT MASTER" temperature changed to 70.0
Received INSTEON "THERMOSTAT MASTER" temperature changed to 70.0

Sep 21, 2012 4:45:47 PM
Sent INSTEON "THERMOSTAT MAINFLOOR" set cool setpoint to 71.0
Received INSTEON "THERMOSTAT MAINFLOOR" cool setpoint changed to 71.0
Error "THERMOSTAT MASTER" set cool setpoint to 70.0; send failed (no acknowledgment)

Sep 21, 2012 4:48:00 PM
Received INSTEON "THERMOSTAT MASTER" on (button 1)
Received INSTEON "THERMOSTAT MASTER" temperature changed to 71.0
Received INSTEON "THERMOSTAT MASTER" temperature changed to 71.0
Received INSTEON "THERMOSTAT MASTER" temperature changed to 71.0
Received INSTEON "THERMOSTAT MASTER" temperature changed to 71.0

Sep 21, 2012 4:49:08 PM
Received INSTEON "THERMOSTAT MAINFLOOR" humidity changed to 55.0

Sep 21, 2012 4:52:27 PM
Trigger ETHAN COMES HOME
Action Group TEXT WELCOME ETHAN HOME
Smartphone Radar "PHONE ETHANS" state is now Home.
Google Voice SMS Sending 'WELCOME HOME, ETHAN' to
Google Voice SMS Message sent successfully.

Sep 21, 2012 4:53:45 PM
Error "THERMOSTAT MASTER" mode request; send failed (no acknowledgment)
Error "THERMOSTAT MASTER" temperature request; send failed (no acknowledgment)
Error "THERMOSTAT MASTER" setpoint request; send failed (no acknowledgment)

Yeah, definitely looks like a signal issue, though it could be a problem with the adaptor. I'd switch out the mainfloor adaptor with the master adaptor and see if the problem follows the adaptor or stays at the master location - that will pretty much tell you if you have a signal issue or if the adaptor is having a problem.

Jay,
the master thermostat is the venstar with the integrated insteon adaptor. The main floor is the new smarthome insteon thermostat with the blue screen.

Thoughts on a signalinc or access points as solutions to enhance the signal?

Thanks again for the quick response!

It can rarely hurt to add another access point - so it's up to you whether you want to spend the $ on an AP that may or may not help. If you really have 20 dual-band devices split pretty evenly throughout your house then it makes me a bit doubtful that it's going to help.

Instead of adding a new AccessPoint, how about moving your existing AccessPoint RFs (and/or dual-band modules) to different outlets? That will change up the signal path, and might avoid the problem you are seeing.

Thanks Jay! I'll give it a shot. Based on what you said, I believe that something could be wrong with that Thermostat.

I have an Insteon Thermostat (2441TH) that was just installed today. It operates fine as a simple programmable thermostat, but I'm unable to link it to Indigo. I have dozens of Insteon devices throughout my house and this is the first time I've seen this issue. Indigo "sees" the device, but is unable to complete linking. Here's my log output:

PowerLinc Linking - entered discovery linking mode (240 seconds)
PowerLinc Linking - received module button pressed from 1D.6E.1F

Oct 2, 2012 8:46:59 PM
PowerLinc Linking - syncing PowerLinc links (address 0F.DD.3D)
PowerLinc Linking - . . adding: INSTEON plc link to controller 1D.6E.1F, flags 03, group 01, data 00 00 FF
PowerLinc Linking - . . adding: (not added -- probably already exists)
PowerLinc Linking - sync complete
PowerLinc Linking - sending engine version request to 1D.6E.1F
PowerLinc Linking - PowerLinc links updated
PowerLinc Linking - received engine version 01 from 1D.6E.1F
PowerLinc Linking - sending id request for device information to 1D.6E.1F
PowerLinc Linking - received id request response from 1D.6E.1F
PowerLinc Linking - initializing remote device "Foyer Thermostat" (address 1D.6E.1F, firmware version 91)
PowerLinc Linking - . reading: settings and date/time
Error request for date/time not acknowledged
PowerLinc Linking - initialize complete
PowerLinc Linking - syncing remote device "Foyer Thermostat" (address 1D.6E.1F, firmware version 91)
PowerLinc Linking - syncing all links

Oct 2, 2012 8:47:36 PM
Error failed to fetch data from remote module
Error Linking - syncing failed
Error linking failed
PowerLinc Linking - entered discovery linking mode (240 seconds)
PowerLinc Linking - exited linking mode