Jump to content
AT&T to end email-to-text ×

Scenes Not Quite Right After New PLM Install


alixer

Recommended Posts

Posted

I have a Polisy running version 5.9.1 and my home is pretty much all Insteon devices. I think there are around 70 switches and outlets. 

Recently my Serial PLM failed and I had to purchase a new one. I followed the instructions from the docs to install a new PLM including the last step of "Restore Modem". But this step doesn't really seem to be doing what I think it should be doing. My PLM "works" as in it is connected and shows all of my devices in its link table. I can add new scenes and test those scenes and everything works perfectly. However, when I test old scenes all the devices fail (lights do not turn on or off and log simply reports failure). So old scenes do not seem to be linked to the PLM even though the individual devices are. I believe the individual devices are linked because their link tables show the PLM and I can control the individual devices via the admin console. Maybe I am assuming too much?

I can fix a scene by simply going into the scene on the admin console and adjusting the "On" parameter of each device and hitting the "Update" button. Or I can delete the scene and recreate it. However this is extremely cumbersome with 70+ devices, dozens of scenes and Echo integrations. I want to avoid doing this manual fix for every single device in every single scene if I can.

I tried doing a "Restore PLM" a second time but that didn't help anything. Any ideas how I might force a scene to re-link with the PLM without adjusting every single device within the scene?

Thanks

Posted
1 hour ago, alixer said:

I can fix a scene by simply going into the scene on the admin console and adjusting the "On" parameter of each device and hitting the "Update" button. Or I can delete the scene and recreate it. However this is extremely cumbersome with 70+ devices, dozens of scenes and Echo integrations. I want to avoid doing this manual fix for every single device in every single scene if I can.

I tried doing a "Restore PLM" a second time but that didn't help anything. Any ideas how I might force a scene to re-link with the PLM without adjusting every single device within the scene?

It sounds like your new PLM address did not get written to your older devices.  Not quite sure why.

When you adjust the parameters of scene devices you are re-writing the scene AND the PLM address.  That's why things work properly after the update.  I can understand why you wouldn't want to do this for all of your scenes - you probably have a life.

Could you try performing a Link Table Read/compare on one of your problem devices and posting the results?  Please also post the new/old PLM address.  This will tell us if the ISY contains the correct information.  If it does, a simple "restore device" should correct the problem.  

If it doesn't, things get a bit more complicated...

  • Like 1
Posted
55 minutes ago, Techman said:

It  sounds like some of your link tables didn't get written to the new PLM.  Did you exactly follow the attached replace PLM procedure?

After you get everything working be sure to do a backup.

Replace PLM Procedure (EISY or POLISY).pdf 170.85 kB · 0 downloads

Yes, this is the exact doc I followed. It's pretty basic so hard to miss any of the steps. And like I mentioned, the devices have the correct PLM (indicated by the fact that I can control a device from the admin console). It's only the scenes that cannot be controlled from the admin console.

25 minutes ago, IndyMike said:

When you adjust the parameters of scene devices you are re-writing the scene AND the PLM address.  That's why things work properly after the update.  I can understand why you wouldn't want to do this for all of your scenes - you probably have a life.

In order to get the scene to work correctly I have to adjust every single device in the scene. 

Also, doing a "restore device" does not fix that device within a scene. Only adding/removing it from the scene or adjusting it's parameters within the scene will fix it.

Posted
24 minutes ago, alixer said:

Also, doing a "restore device" does not fix that device within a scene. Only adding/removing it from the scene or adjusting it's parameters within the scene will fix it.

That's unfortunate.  It indicates that the ISY does not have the correct scene information.  

You could try installing an ISY backup (restore ISY, restore modem, restore devices) , but that may be more work than "refreshing" you scene devices.  

  • Like 1
Posted
On 4/26/2025 at 12:57 PM, IndyMike said:

That's unfortunate.  It indicates that the ISY does not have the correct scene information.  

That was basically my conclusion as well but surely there must be a way to force the scene to be written to the ISY right? I don't mind if I have to touch every scene. I just don't want to have to touch every device in every scene. Even add/removing a device from a scene does not "fix" it. The only thing I have found is changing a parameter on every single device in the scene. 

Posted
3 hours ago, alixer said:

That was basically my conclusion as well but surely there must be a way to force the scene to be written to the ISY right? I don't mind if I have to touch every scene. I just don't want to have to touch every device in every scene. Even add/removing a device from a scene does not "fix" it. The only thing I have found is changing a parameter on every single device in the scene. 

I'd start from the begining to ensure each step was followed correctly. 

 

Unplug Plm and isy. Note Plm Insteon address. Plug Plm in while holding the set button to factory reset. Once beeping stops, let go. Wait 30 seconds and plug isy into power. Verify new pom is showing in isy. Once done, go to file>restore plm>restore devices. 

  • Like 2
Posted
15 hours ago, alixer said:

That was basically my conclusion as well but surely there must be a way to force the scene to be written to the ISY right? I don't mind if I have to touch every scene. I just don't want to have to touch every device in every scene. Even add/removing a device from a scene does not "fix" it. The only thing I have found is changing a parameter on every single device in the scene. 

@alixer, when you performed the "restore device", was the ISY able to complete write the link table (no errors)?

If this is the case, then your device has the correct PLM address and the scene information is incorrect.  I say this because newer devices (I2CS units produced after 2012) will not allow the ISY to read/write to them unless the PLM address is in their link table.  It may still be helpful is you could post your device link table, ISY device link table, and PLM address.  The membership tree on the right is also helpful since it shows how many scenes the device is associated with.

 

image.thumb.png.62e3cbe4f4458be5ed2886d346d52bf6.png  

If your link table compare looks similar to mine above (no missing or mismatched entries) then the ISY believes the device has the correct link table/scene information.

If the device does not respond correctly to a scene command (assuming that it received the command), then the ISY Link Table for the device is incorrect.  The ISY maintains link tables for each Insteon device and for some reason, yours may have been corrupted. 

You can correct this by manipulating the device settings within the scene, causing a re-write to the device (as you are doing) OR your can restore the ISY from backup.  Obviously, the backup may also have incorrect information, or be missing information on your more recent devices.  

If you do choose to restore a ISY backup, please follow with the process that @lilyoyo1 outlined above.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...