REplaced Serial Modem, now comms problems

[walkman9999]

Hi all,

After replacing my PLM, I am having problems hoping I can get some direction. 

 

I used "Restore Modem" command to replace the PLM and since then it seems the ISY cannot communicate with some devices. Things work as expected with existing scenes and commands when executed from a device (e.g. switch, keypad), but when I execute scenes or programs from ISY some work and some don't. The ISY seems to think things have worked, it shows status of devices as "on" when a scene would turn them on, but in reality the devices are not on.

Note that powerline/RF comms have not been a problem in the past. This is existing setup for 7 years.

I have attempted "Restore Devices" which seems to succeed (although I didn't watch the whole thing, it took about an hour).

Looking for advice about what to try next and/or what output to capture to assist troubleshooting. 

 

Some communication events from the log at attached:

write-updates to device.txt shows what happens when I try to write pending updates to a device. The device happens to be battery powered, but is in linking mode.

scene-on-then-fast-on.txt: shows the output when I try to turn a scene "ON" (which fails) and then use "Fast ON" (which also fails)

query-back-door-writeupdates.txt: shows a query command sent to a door sensor in linking mode, followed by a write updates command which all fail.

Thanks in advance for anyone who wants to offer some advice!

 

:Mike (Walkman9999)

query-back-door-writeupdates.txt scene-on-then-fast-on.txt write-updates to device.txt

[Brian H]

When you swapped the PLM. Did you power down both the old PLM and the ISY994i? Then swap the PLM and power it up first. Then power up the ISY994i so it could find the new PLM at boot up.

If you just swapped the PLM and not a power cycle. The ISY994i is still using the old PLM's ID.

[walkman9999]

Thanks for reply. I thought I did per those instructions, but I am not 100% sure. What would be the remedy if this is the case?

And, is there a way to check the ISY to see if this is the case?

[lilyoyo1]

1 hour ago, walkman9999 said:

THanks for reply. I thought I did per those instructions, but I am not 100% sure. What would be the remedy if this is the case?

Do it again but make sure the plm is powered up and connected to the isy before powering up the isy

[walkman9999]

My assumption was that if the ISY was trying to talk to the previous/wrong PLM that no comms would take place between ISY and devices, but I do see some successful comms when monitoring through the event viewer. I am interested to know if this is expected with the  wrong PLM scenario?

That said, I came for advice from more knowledgeable people so I'm going to take the advice given and will report back. Thank you.

[walkman9999]

Hi all,

I repeated the process to replace the PLM modem but still had same symptoms. I then used the the "Restore Devices" command, but still have same symptoms.

1) The ISY seems to think it is activating some scenes/devices, but it has no effect on the actual devices in the scenes (status shows things being "ON" when triggered by scene but they are not). Pictures "Image1.jpg" and "image2.jpg" illustrate this. Other scenes seem to work fine.

2) The ISY cannot communicate with some devices in the house, but others are fine (attached to case is an example of this "writeupdatestodevices.txt")

The logs for the replace modem and restore devices commands are attached ("ISY-Events-Log.v4.8.0__Fri 2020.08.28 08.22.21.txt").

Can anyone suggest a test to capture what might be happening?

Thanks in advance for anyone willing to help!

 

:Mike

ISY-Events-Log_v4.8.0__Fri_2020_08.28_08_22_21.txt

[Michel Kohanim]

@walkman9999,

What you need to do is to find a backup from before the PLM died, and then do:

https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Devices

With kind regards,
Michel

[walkman9999]

Thank you - I have a backup and will follow this procedure and report back.

[walkman9999]

Oh man...am I totally f#cked?

(see attached)

[Michel Kohanim]

@walkman9999,

Why are you upgrading? You need to use File | Restore ISY AND make sure your backup is on a local disk and not a network disk.

With kind regards,
Michel

[walkman9999]

Crap. The file that I have been keeping as a backup of my ISY config is actually an upgrade file. That is embarrassing, but mostly a bummer because I don't have another backup.

[walkman9999]

I feel like all I can do is rebuild from scratch, the system runs the house and the wife isn't happy with the current situation.

Is there a resource of the least painful way to start over?  

[lilyoyo1]

3 minutes ago, walkman9999 said:

I feel like all I can do is rebuild from scratch, the system runs the house and the wife isn't happy with the current situation.

Is there a resource of the least painful way to start over?  

Reboot the isy and clear your Java cache and then try before starting over

[walkman9999]

Thank you, but this was done early in process. Is there any other possibility before I take the "nuclear option"?

And, if I need to go that route, is there a way to "save" any of the scenes, programs or variable configs to save some work. I assume I'll need to re-add the devices from scratch

[lilyoyo1]

After you rebooted your isy and cleared your Java, are you still getting that message

[walkman9999]

Unfortunately, yes.

 

[lilyoyo1]

What did you try to upgrade to?

[walkman9999]

I wasn't trying to upgrade, I was trying to restore a backup. The file I thought was a backup (uuid.00.21.b9.02.00.88.zip) was not able to be opened by ISY - for some reason, it thought the file was an upgrade (even though I did FIle | Restore option) (screenshot above). I assume backup was corrupted or something. THis is all an attempt to fix same problem described above.

At this point I'm willing to bite the bullet and rebuild the config from scratch. Hoping there is some way to save some work by importing only scenes or programs. 

10 years of Insteon/ISY and this is the first time I've had to rebuild, but I don't see an alternative because suggestions above are not working.

[lilyoyo1]

I'd submit a ticket directly to UDI. They may be able to come up with something. You don't have any backups at all? Even an older one would beat starting from scratch

[Brian H]

That file title does not look like a backup files title.

Mine start with ISY-Backup, the the firmware version, date and time of the backup.ZIP

[larryllix]

That file title does not look like a backup files title.
Mine start with ISY-Backup, the the firmware version, date and time of the backup.ZIP

He attempted to restore from an ISY image file.

I doubt it would injure ISY in any way.

Sent using Tapatalk

[walkman9999]

I found an older backup and I restored from it successfully. Then, following instructions from the Wiki, I allowed the ISY to complete its initial scan/query and then did a  File | Restore Devices. This took about 45 minutes and completed with no errors.

Some progress. At this point: 

• Scenes and devices work from the physical control (switch, keypad, etc.)
• Devices work individually from ISY with use of "ON" or "Fast ON", etc.
• Scenes do not work from ISY. Running a Scene test results in most (but not all) devices saying "[Failed]" and, the devices that say "[Succeeded]" do not actually come on.
  • see attached logfile "scene-test.txt"

 

scene-test.txt

[lilyoyo1]

You must do restore modem and restore devices

[walkman9999]

This worked. What a saga.I know some of this is self-imposed drama, but not being familiar with the tech means some wrong turns. Appreciate all the help from the community.

 

Case closed.