in-linelinc dimmable device problem

[C Martin]

I have been experiencing the following problems since version 3.1.5 (see picture).

I am using a remote 2475D in-linelinc .

If I go to the closet area and activate the companion switch, then I can trigger the write to the device.

is anyone else using any devices like these and having similar problems?

 

Clarence

[Michel Kohanim]

Hi Clarence,

 

This means that there are pending device updates that ISY has tried programming into the device but has failed. Please right mouse click on the green 0101 icon and then choose Write updates to device. If that fails, then you have communications issues with that device.

 

With kind regards,

Michel

[C Martin]

Michel,

I did some testing today. It seems that I need to make sure that the Companion Switch is in the off State for the updates to take place. If the Companion Switch isnot off (Verified by the LED) then the updates don't seem to happen.

This is not very consistent. I will monitor events and update any other problems that I might have with these.

FYI, I have a program that changes the dim values for the in-linelink, depending on the time of day. So there are updates that are sent to the in-linelink device. My example shows the Scenes that get changed by my program.

 

Clarence

[LeeG]

Assuming the In-line Linc turns On/Off correctly otherwise (correctly wired) the type of load the device is controlling can be a problem. What type of load (CFL, LED, simple incandescant, etc) is the In-Line Linc controlling?

[C Martin]

LeeG,

can you please explain what you mean by wired correctly?

 

Michel and LeeG,

I have had my in-linlink in service for more than 6 months. It worked without exception for most of that time. I only started having problems recently with the versions starting 3.1.5.

I had another event this morning and I did right click and it was able to update the device. My in-linelinc has 2 program changes per day and that is where the problem is coming up.

If I didn't need to use this device, I wouldn't. But I have to because of the "No Hot wire" situation in my closet area. The other problem occurs if the companion switch is turned on. It won't allow updates in any case (manually or automatic), unless the switch is turned off.

I hope that someone else can verify or confirm this scenario with the updates.

 

Clarence

[LeeG]

C Martin

 

"can you please explain what you mean by wired correctly?"

 

When a symptom is described as it works unless I turn On x, at which point it never works, how the device(s) is wired is a consideration. The other consideration is what type of load is receiving power when x is turned On. There are a number of noise generating/signal absorbing devices that can interfere with Insteon when powered On.

 

What type load is the In-Line Linc controlling?

 

Perhaps if the companion switch can be explained. What is it, how is it wired relative to the In-Line Linc, when On what is its relationship to the In-Line Linc.

 

I am not disputing that this started at 3.1.5. The last OP that described the symptom in the context of starting when image x.x.x was installed turned out to be a noise/surge suppressing power strip. It is normal to relate to installing an image but most times symptoms involved with intermittent communication with a device, particularly when no communication is possible when x is turned On, has anything to do with a particular firmware level.

 

Lee

[C Martin]

I am switching a incandescent flood.

the number is 2474D

[LeeG]

I am familiar with the 2-wire diagram. If turning the 2474D On, which acting as a Controller to the In-Line Linc should be turning the In-line Linc load On, prevents communication with the In-Line Linc, there is a problem there. Would expect to see the same problem if the In-Line Linc is turned On through the Admin Console.

 

This configuration required retasking the existing wiring. Has the wiring been verified with a voltage meter?

[C Martin]

OK,

I am stupid. I actually caused this problem.

I toggled the auto write update off.

The problem turns out to be operator error.

But, I will check the wiring -- or retest the non-write errors if the companion switch is turned on problem

I apologize for creating my own problem.

 

Thanks,

 

Clarence