My PLM died for the 3rd time and I replaced it with a new one. Everything is back up and restored except for the two RemoteLincs (2440) which seem to be giving me endless problems. Did all the other wireless devices without any issues at all by clicking 'Write updates to device' after entering linking mode for each device.

 

So with the RemoteLincs I put one of them into linking mode by holding down the 'Bright' and 'Dim' buttons until it began flashing and tried to write the updates but got a message 'cannot determine insteon engine' or something similar. Tried this numerous time but no joy. Tried the second remote but received the same error.

 

I then deleted the remotelinc from ISY and attempted to add it again and continued to get the same error. Reset the remotelinc, still the same problem.

 

Anyone have any ideas on why this is so difficult. Best way forward?

 

 

Thanks.

Did you use the Link a  Remotelinc choice in the Link Management drop down menu?

Or try selecting the 2440 from the drop-down list.

That message indicates NO communication with the RemoteLinc. RemoteLinc did not respond to the first command sent which asks for the Insteon Engine. All devices should respond to this command and it is issued three times before the ISY stops.

 

Move the RemoteLinc near the new PLM or other Dual Band device.

Also, in case the above fails to work this problem is also present when the battery state is very low. This causes low RF reception on the remote control.

 

So, if its been awhile since you changed the battery you might consider changing them out and standing closer to a dual band device and trying again.

So firstly I replaced the batteries in both remotes then placed a remotelinc right next to the new PLM and selected 'Add new Insteon Device' and chose Remotelinc 2440.

 

Result:

 

Then with the second remotelinc I attempted to 'Write updates to device' by clicking on the small grey 1011 icons in the device tree and

got the following result:

 

For each pair of 02 62 ..... outbound messages there should have been an 02 50 ...... response from the RemoteLinc.

 

Was each RemoteLinc put into linking mode before starting New INSTEON Device and taken out of linking mode before starting with the next RemoteLinc?

 

What ISY firmware and UI (Help | About) is being used?

 

The new PLM is a 2413?

 

Just realized the second device must have added to the ISY as a Write Update is being tried.

Edited November 8, 201410 yr by LeeG

Tap the Set button on PLM 4 times and check other Dual Band devices to confirm RF messages are being received.

Here are the results after ensuring that I did as you suggested i.e put in linking mode - added - taken out of linking mode etc

 

Now this has happened before where the device is entered into ISY BUT there is still some info not written to device according to event

viewer. You can also see the red exclamation marks in device tree.

 

Tap the Set button on PLM 4 times and check other Dual Band devices to confirm RF messages are being received.

 

I just checked, yes they are.

ISY Firmware is 4.0.5

New PLM is 2413S

 

The second device has the same issue as described in previous post.

Originally 0A.35.31 would not add to the ISY. The last trace shows the device added but will not handle Write Updates.

 

Was the RemoteLinc put into linking mode before clicking Write Updates?

 

The ISY and UI should be updated to 4.2.18.

>Originally 0A.35.31 would not add to the ISY

 

As I said, this partial success has happened before. That's how the second RL got there, but it wont write updates.

 

Yes the RL was put into linking mode before *Adding* it as a new device. After attempting to add it the result is what you see in that image I just posted. If I then put it into linking mode again and attempt to write those updates to device it fails again.

 

The ISY and UI are at 4.0.5 which as far as I know is the latest official version. The remotelincs have previously worked on that version.

Same issue, a command (Set MSB for Write Updates) is sent three times and the device fails to answer any of the three requests. Perhaps something is blocking RF such as a thermostat stuck On. That has been known to happen. Perhaps 4.0.5 has an intermittent issue. Yes, 4.0.5 is the last Official release. There have been many ZWave updates in the last 18 months that have slowed moving something into Official status.

I'll step aside and let someone else play with 4.0.5.

Are you saying that there could be a problem with 4.0.5 and remotelincs? I have no ZWave devices and thats pretty much why I haven't bothered to update to release candidates. I can update if you believe that would help but I'm not really interested in updating for the sake of it as that has the potential to compound a problem when we know that these devices have worked on 4.0.5 before.

 

All the other wireless devices updated instantly without any issues.

 

Thanks for you help Lee.

Looking at the environment from the other perspective ...

 

4.0.5 has been working fine so the issue is not there

Insteon network is fine because other RF devices and powerline devices work

That leaves 2 RemoteLincs that are not working, or they are fine

 

If both RemoteLincs are fine then there is no problem. 4.0.5 is good, Insteon network is good, RemoteLincs are good.

 

What is left if everything has been eliminated by process of elimination.

 

Good luck.

Hence my frustration.

 

The other piece of info that might help is that I was able to link the Remotelincs directly to Lamplincs. Both worked without issue.

Edited November 8, 201410 yr by wwat

I'm having the same issue. Just replaced the PLM a few months ago straight from Smarthome. My 3 PLM.

 

All the other wireless sensors updated just fine when "write updates to device" were selected.

 

But both remotelincs won't update. They actually still work because the links are still the same but the ISY thinks they need to be updated.

 

Brand new batteries in the remotelincs. 

Interesting. So I tried something different. I selected the dropdown and selected remotelinc. I then added the address and pressed OK(even though this remotelinc is in my device list already). It started writing and immediately blew through the first 3 links in the list. It then stuck on 4 until it finally stopped. The write updates icon remained next to the switches on the remotelinc so it obviously didn't finish. I did get responses from the remtelinc for the first three lincs so it's not a transceiver hardware failure. Seems more like a bug.

 

Additional repeat attempts have it coming up starting at link 4 and just sitting there.

Edited September 2, 20169 yr by sorka

The 2440 needs to be distant from the ISY, but near any dual band device to successfully add it to the ISY. For most of my 2440s (I have seven) 40' was far enough, but one needed to be 60' distant.

The 2440 needs to be distant from the ISY, but near any dual band device to successfully add it to the ISY. For most of my 2440s (I have seven) 40' was far enough, but one needed to be 60' distant.

 

Yup. Very odd. So I did that and it actually worked. Why???????

The 2440 seems to be the only RF device with that particular problem and that specific solution. Lot's of speculation, but no definitive answers as to why.

Edited September 3, 20169 yr by stusviews

Did this connectivity issue with the 2440 RemoteLinc ever get solved?  The thread is getting pretty stale.

 

I've got 2 RL's that have served me well  over the years, and which have been connected to ISY without incident going back many versions, starting out with an ISY-99iR.  But now that I've migrated to the ISY994i and firmware 4.6.2, connecting the 3rd RL - I've had it sitting on the shelf as a spare, just recently pressed into service to replace a failed RL - to ISY has proven challenging.  I've tried the methods presented in this thread, but can't get rid of that small "101010" icon next to the 6 channels.  It works just fine directly linked to other Insteon devices as a controller, it just doesn't seem to play well with ISY.

 

Did anyone from Insteon or Universal Devices ever comment on this problem?

It's unlikely that the problem will ever see a solution as the 2440 RemoteLinc has been discontinued somewhat more than a year ago, maybe even longer. Considering time constraints, in particular, improving current features and adding new ones, no one wants to spend their time working on something that's no longer available.

 

All but one of my 2440 RemoteLincs shows the dreaded 1011, but they do function