Jump to content

One way communication between switches and ISY


klebel

Recommended Posts

Hi All,

 

My PLM died.  I bought a replacement, and followed the steps in the Wiki to a T.  I read over a dozen different threads on here before I tackled the replacement.  I did not do a delete of the PLM.  I know better.  BUT, after doing a restore of the PLM none of my scenes worked.  It didnt even show they were triggered in the event viewer.  So I did some more reading and decided to try and do a restore of all my devices.  I let that run to completion and still no deal.  So I read some more in the forum and read that one guy had to delete and recreate his Scenes for some reason.  So I have tried that on a few and it worked.  BUT here is the deal.  If I turn on a light from the switch itself it is not reporting back to the ISY that it has been turned on.  If I execute the command for ON, OFF or anything else from the ISY it all syncs just fine.  

 

Any ideas what is going on with my scenes and why the switches are not reporting status back to the ISY even after a full restore of the PLM AND a restore of the devices?

 

Thanks all,

 

Kerry

Link to comment

For the SwitchLinc that does not report local change to ISY (PLM) do a Show Device Links Table.

 

Looking for a link record that is

 

E2 01 xx.yy.zz .. .. ..

 

where xx.yy.zz is new PLM Insteon address

 

and a Show PLM Links Table

 

that is

 

A2 01 aa.bb.cc .. .. ..

 

where aa.bb.cc is Insteon address of SwitchLinc 

Link to comment

Interestingly the PLM table shows all the switches and most of the switches do not have the above record for the PLM you mentioned.  There are a few with E2 00 and E2 18 and E@ 12 records for the PLM but that is it.  How do I get the PLM records into the switches now?

Link to comment

Without the E2 Controller records in each device local activation is not sent to the PLM.   Normally the Controller information is in the ISY but since the Restore Devices did not bring the information back first thing is to look at ISY Firmware and UI levels.   Help | About displays both ISY Firmware and UI (Admin Console) levels.

Link to comment

Interestingly the PLM table shows all the switches and most of the switches do not have the above record for the PLM you mentioned.  There are a few with E2 00 and E2 18 and E@ 12 records for the PLM but that is it.  How do I get the PLM records into the switches now?

 

If I understand correctly you will only show an E2 if the device has been added to a scene as a controller.  Otherwise your device links table will show A2 for responder.

 

 

Jon...

Link to comment

klebel

 

There must be an E2 in the device and an A2 in the PLM for local switch activity to be reported to the ISY.   Standard Insteon requirement forever.

 

For the E2  links not to be in the devices something happened during the process of replacing the PLM.   ISY and PLM not powered in the correct sequence, I cannot say without knowing exactly what was done during the PLM replacement.  Since now the ISY does not have the correct information with multiple Restore Devices not fixing, the next step would be to Restore ISY with backup taken before PLM was replaced.  Then do a Restore Modem (PLM) followed by another Restore Devices.

Link to comment

klebel

 

The E2 in device and A2 in PLM is an Insteon Scene.  It is created when the device was initially added to the ISY and must be there at all times for the device to work correctly.

 

So if the E2 is missing from the device is the only fix to re-pair them?  Not sure how I ended up in this situation just be replacing the PLM.  Ugh.

Link to comment

When the Restore Modem (PLM) and Restore Devices does not fix the missing link the next step is to Restore ISY and repeat Restore Modem (PLM) and Restore Devices.

 

If a current ISY backup is not available (or the ISY Backup does not fix problem because the issue existed when backup taken) the next step would be to delete device, factory reset, and add device to ISY.

 

Not sure what you are referring to "re-pair" device.

Link to comment
Sorry I was being generic in my terminology.  I meant to re-link the switch to the ISY.  LeeG I dont know if you remember a few weeks back Michel cleaned up a corrupt file system for me.  I have a bad feeling this might be leftover mess from that issue.  So using the old backup would be of little good.

Link to comment
  • 1 month later...

Any updates to this?  I find myself in the exact same situation.  Appears that my PLM may have died at about the same time as well.

The additional issue that I have, which Klebel has not had (or not reported) is that two of my devices which are impacted also no longer have an LED lit up on the local switch.  They respond if I switch them on and off from the ISY Admin console, but not from the local switch too.

Any news?  Any ideas?

Link to comment

On the two ones with no LEDs

Try a power cycle reset.

By pulling the Air gap Switch out for ten seconds. Then push the Air Gap switch back to its normal position. Using care you don't push it all the way in.

 

When you replaced the PLM did you power down the ISY controller and the old PLM?

Power up the new PLM first so it can totally initialize.

Power Up the ISY controller so it detects the new PLM's ID.

Then do a Restore Modem (PLM)?

You did not use the Delete Modem (PLM) at any point?

Link to comment

On the two ones with no LEDs

Try a power cycle reset.

By pulling the Air gap Switch out for ten seconds. Then push the Air Gap switch back to its normal position. Using care you don't push it all the way in.

 

When you replaced the PLM did you power down the ISY controller and the old PLM?

Power up the new PLM first so it can totally initialize.

Power Up the ISY controller so it detects the new PLM's ID.

Then do a Restore Modem (PLM)?

You did not use the Delete Modem (PLM) at any point?

Regarding the PLM - yes, all of that is correct.  I followed the instructions exactly and at no point did I delete the PLM.

 

Regarding the power cycle reset - I'll try tonight and let you know.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...