Insteon load controller 2477SA2

Hi,

I bought an Insteon load controller 2477SA2 but I am unable to sync it with Indigo (4.1.9). In the linking process, Indigo receive the 2477 address but when starting, I receive this message: "Failed to establish a link with the device." Here is a screen snapshot:

[jay (support)]

Try linking again, but this time paste in whatever entries show up in the event log.

Here it is:


2010-06-18 13:01:47
PowerLinc Linking - sending id request for device information
PowerLinc Linking - received id request response from 14.32.87
Error Linking - no match found for device type ID 2315 with firmware version 3A
Error linking failed
PowerLinc Linking - entered discovery linking mode (240 seconds)
PowerLinc Linking - exited linking mode

[jay (support)]

OK, this a new device which Indigo doesn't yet support. We'll get it into the next build. That's an odd type ID, though, so we'll need to check with Smarthome about it so it may take a week or so.

This is not the same Load Controller mentioned in your 4.1.8 version's announcements?

Thanks, I will wait

[jay (support)]

Apparently not - either that or Smarthome changed the type ID on us (which has been known to happen).

[jay (support)]

Yep, it looks like they changed the identifier between beta and release. We'll get a build out soon with the new type ids.

[matt (support)]

Give Indigo 4.1.10 a try. We've corrected the ID number for the normally closed (NC) load controller. The normally opened model had the correct ID already.

Working fine.

Thanks for the very fast service again, if only we could have the same from many others companies! I really don't regret my choice of buying Indigo.

Hi, new problem with this module, it's continuously sending from "button 2" but there is no "button 2", here is a log:

2010-06-24 23:08:51
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)
Received INSTEON "Chauffe piscine" off (button 2)
Received INSTEON "Chauffe piscine" on (button 2)

"Chauffe piscine" is the 2477SA2

[matt (support)]

The "button" label is a bit of a misnomer in this case. It is really the group/scene #2, not button. The Normally Closed version of the load controller has a built in load sense feature that sends out group (button) 2 ON and OFF commands as it detects when the load is ON or OFF. It sends out group 1 ON / OFF commands if you locally control the relay (via the button).

What type of load are you controlling? Is the "Load Active" LED on the module turning ON and OFF when you see those lines in the Event Log?

I am controlling a heat pump and seems to work well. Yes the load button is flashing when the on or off is received in the log window.

[matt (support)]

I presume the logging is happening more often than the heat pump is really cycling? If so, it sounds like the load controller module is a bit confused by the pump.

Try the factory reset procedure from the 2477SA Manual. That will clear out the link that Indigo added for the Load Sense feature.

I think you'll still be able to use Indigo to turn it ON and OFF like this, and the broadcasts back to Indigo should stop. However, it is a bit of a temporary solution -- if you Re-Sync the Device in Indigo, then it will add the links back.

Presuming the factory reset works, we'll think about how to make that link Indigo is adding optional in a future version.

Thanks, the resetting worked. It is always a good way to start: "resetting the device that goes crazy". And I always forget.

MOVED TO INSTEON FORUM on 12/17/2014.

I use the 2477SA2 (normally closed) unit. I am having a strange issue, analogous to the message above. When I turn off the unit using Indigo at night, then a motion detector is causing Indigo to appear to turn the 2477SA on. Actually, it appears to signal that the load is on "button 2".
This is happening with motion detectors that apparently transmitting through one dual band switch.
Attempted remediation:
I have swapped both the 2477SA and several motion detectors to assure the latest firmware in each.
I have factory reset the 2477SA, the motion detectors and the switchlinc dimmer unit that routes the signal from the motion detector.
It does not occur when Indigo is offline and the 2413U is left online; nor does it occur when both Indigo and the 2413U are offline.

Here is an excerpt from the log file; the 2477SA is the "Water Heater":

2014-12-04 23:25:49.631Received INSTEON"MB Motion Sensor" on (button 1)
2014-12-04 23:25:50.078Received INSTEON"Hall Closet Hot Water Heater" off (button 2)
2014-12-04 23:26:49.418Received INSTEON"MB Motion Sensor" off (button 1)
2014-12-04 23:26:49.946Received INSTEON"Hall Closet Hot Water Heater" on (button 2)
2014-12-04 23:49:59.952Received INSTEON"MB Motion Sensor" on (button 1)
2014-12-04 23:51:04.759Received INSTEON"MB Motion Sensor" off (button 1)
2014-12-04 23:51:05.590Received INSTEON"Hall Closet Hot Water Heater" off (button 2)
2014-12-04 23:54:39.497Received INSTEON"MB Motion Sensor" on (button 1)
2014-12-04 23:54:40.584Received INSTEON"Hall Closet Hot Water Heater" on (button 2)
2014-12-04 23:55:39.301Received INSTEON"MB Motion Sensor" off (button 1)

The 2477 is not going on and off; just messaging about the load going on and off.

Any ideas why the "button2" action and subsequent message is happening right after
a motion sensor message? Seems weird to me.

Any other tests/changes I might try?

Matt had mentioned improving the message handling in a 2010 blog entry. Any ideas to work around this?