Jump to content

Restored PLM now scenes are failing

atmarosi

Recommended Posts

atmarosi Experienced

atmarosi

Posted
Posted

Greetings Party People,

Got a 994 on 5.0.16C.  PLM (2413S) stopped working so recapped a spare and restored modem/plm.  Devices work fine but scenes seems to not work via the UD Console/Admin nor alternate means (scenes on linked at the switch seem to work fine). 

If I run a scene test it will report failed.  Here is the output from a test and then trying to operate the same scene from the console. 

Sun 09/18/2022 21:45:32 : [GRP-RX      ] 02 61 1A 13 00 15 

<html><font color="red">----- Living Room2 Test Results -----</font></html>
<html><font color="red">[Failed]</font> LivingRoomSofaOutlet (2A 68 E0 1)</html>
<html><font color="red">[Failed]</font> Living Room - South Floor Lam (2C 12 29 1)</html>
<html><font color="red">[Failed]</font> Living Room Floor Lamp (3F F9 5C 1)</html>
<html><font color="red">[Failed]</font> Living Dinig Room Floor Lamp (2B C6 5A 1)</html>
<html><font color="red">----- Living Room2 Test Results -----</font></html>
Sun 09/18/2022 21:46:02 : [INST-TX-I1  ] 02 62 2A 68 E0 0F 19 00

Sun 09/18/2022 21:46:02 : [INST-ACK    ] 02 62 2A.68.E0 0F 19 00 06          LTSREQ (LIGHT)

Sun 09/18/2022 21:46:02 : [INST-SRX    ] 02 50 2A.68.E0 40.D2.CB 2F 14 FF    LTOFF-F(FF)

Sun 09/18/2022 21:46:02 : [Std-Direct Ack] 2A.68.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

Sun 09/18/2022 21:46:02 : [INST-TX-I1  ] 02 62 2B C6 5A 0F 19 00

Sun 09/18/2022 21:46:02 : [INST-ACK    ] 02 62 2B.C6.5A 0F 19 00 06          LTSREQ (LIGHT)

Sun 09/18/2022 21:46:02 : [INST-SRX    ] 02 50 2B.C6.5A 40.D2.CB 2F 10 FF    ID-REQ (FF)

Sun 09/18/2022 21:46:02 : [Std-Direct Ack] 2B.C6.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

Sun 09/18/2022 21:46:02 : [INST-TX-I1  ] 02 62 2C 12 29 0F 19 00

Sun 09/18/2022 21:46:02 : [INST-ACK    ] 02 62 2C.12.29 0F 19 00 06          LTSREQ (LIGHT)

Sun 09/18/2022 21:46:03 : [INST-SRX    ] 02 50 2C.12.29 40.D2.CB 2B 14 FF    LTOFF-F(FF)

Sun 09/18/2022 21:46:03 : [Std-Direct Ack] 2C.12.29-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 09/18/2022 21:46:03 : [INST-TX-I1  ] 02 62 3F F9 5C 0F 19 00

Sun 09/18/2022 21:46:03 : [INST-ACK    ] 02 62 3F.F9.5C 0F 19 00 06          LTSREQ (LIGHT)

Sun 09/18/2022 21:46:04 : [INST-SRX    ] 02 50 3F.F9.5C 40.D2.CB 23 0A FF    LNK-OFF(FF)

Sun 09/18/2022 21:46:04 : [Std-Direct Ack] 3F.F9.5C-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2A 68 E0 1] [ST] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  2A 68 E0 1]       ST 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:04 : [D2D-CMP 001F] STS [2A 68 E0 1] ST Converted values Event=255 Condition=255 prec=0

Sun 09/18/2022 21:46:04 : [D2D-CMP 001F] STS [2A 68 E0 1] ST op=1 Event(val=255 uom=100 prec=0) is Condition(val=100 uom=51 prec=0) --> true

Sun 09/18/2022 21:46:04 : [D2D-CMP 001E] STS [2A 68 E0 1] ST Converted values Event=255 Condition=0 prec=0

Sun 09/18/2022 21:46:04 : [D2D-CMP 001E] STS [2A 68 E0 1] ST op=1 Event(val=255 uom=100 prec=0) is Condition(val=0 uom=51 prec=0) --> false

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2A 68 E0 1] [OL] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  2A 68 E0 1]       OL 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2A 68 E0 1] [RR] [31] uom=25 prec=0

Sun 09/18/2022 21:46:04 : [  2A 68 E0 1]       RR  31 (uom=25 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2B C6 5A 1] [ST] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  2B C6 5A 1]       ST 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2B C6 5A 1] [OL] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  2B C6 5A 1]       OL 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2B C6 5A 1] [RR] [28] uom=25 prec=0

Sun 09/18/2022 21:46:04 : [  2B C6 5A 1]       RR  28 (uom=25 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2C 12 29 1] [ST] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  2C 12 29 1]       ST 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2C 12 29 1] [OL] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  2C 12 29 1]       OL 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [2C 12 29 1] [RR] [28] uom=25 prec=0

Sun 09/18/2022 21:46:04 : [  2C 12 29 1]       RR  28 (uom=25 prec=0)

Sun 09/18/2022 21:46:04 : [D2D EVENT   ] Event [3F F9 5C 1] [ST] [255] uom=100 prec=0

Sun 09/18/2022 21:46:04 : [  3F F9 5C 1]       ST 255 (uom=100 prec=0)

Sun 09/18/2022 21:46:11 : [INST-TX-I1  ] 02 62 00 00 1A CF 13 00

Sun 09/18/2022 21:46:11 : [INST-ACK    ] 02 62 00.00.1A CF 13 00 06          LTOFFRR(00)

 Any ideas?

Thanks in advanced!

Andy

Techman Advanced

Techman

Posted
Posted

Scene data links are stored in each device and the PLM

If you disconnect the PLM and then activate a member of a scene all the other scene members should respond as they are not dependent on the PLM

Being that the scenes work but not from the ISY, the restore PLM should correct your issues.

atmarosi Experienced

atmarosi

Posted
  • Author
Posted

Interesting....I did that once I powered up the ISY (after powering up the PLM of course).  Just odd I have to touch so much.

 

I'll test the update of the programs once at home.  This dang day job gets in the way...

lilyoyo1 Advanced

lilyoyo1

Posted
Posted (edited)
2 hours ago, atmarosi said:

Restored each device already - guess I'll work through the programs and see if that helps with that portion.  Thanks for the advice!

Did you restore PLM AND choose restore devices. Many people skip the last part

Edited by lilyoyo1
lilyoyo1 Advanced

lilyoyo1

Posted
Posted
3 minutes ago, atmarosi said:

Great question....I don't recall getting a prompt to restore devices on restore PLM...wonder if it's because i'm on 5.0.16C....

It's not a prompt. You have to choose it under the file tab like you do with restore plm

Geddy Advanced

Geddy

Posted
Posted

 

21 minutes ago, atmarosi said:

Can't say I have it:

Look up one line!

image.png

 

You can also right click on any device and "restore device" if you don't want to do them all.

image.png

  • Thanks 1
Geddy Advanced

Geddy

Posted
Posted

No worries. It's simple issue. I actually was going more for the option of doing the restore for device specific menu when I read @lilyoyo1's post again and looked at the screen shot and saw it right away. 

Did that process resolve your issues? Hopefully you're running right again. 

atmarosi Experienced

atmarosi

Posted
  • Author
Posted

Got home and gave the system a whirl…
Scenes: seems to be good to go
Programs: I have several programs for fast on/off and they will either turn on/off devices/scenes….none of these work. Even after going through each program line and hitting update, and then saving the programs tab - they don’t execute. Ran a “Restore devices” for good measure, let it complete and tested a program for fast on - and nothing even shows up on the level 3 logs.

Any ideas?

Geddy Advanced

Geddy

Posted
Posted

@atmarosi

I'd try to create a new program (identical to existing programs) and see if a new program works. Also, I assume that you're process of testing the program that you just "run then" and nothing worked. 

I don't use "fast on" so have you tried to just use "on", or is there a reason that it's a "fast on" trigger?

Do other programs work and it's just the ones that turn scenes on/off?

Do the programs that aren't working happen to be in a folder? Is there a chance there are folder settings that aren't allowing those programs to run? If they're in a folder move them to the root program level and see if they work. If they do then you have something in folder settings that aren't allowing programs to run.

 

dex Experienced

dex

Posted
Posted (edited)

After my migration to IoP (5.4.4), none of my scenes would function from the ISY interface until I did the following...

  • For each device right-click > Diagnostics > Query Insteon Engine 
  • Go into each scene and, for each device in the scene, at least click the "Update" button (in the lower section).  For many scenes, I also had to provide the desired settings for that device for that scene.  

This seemed to trigger some final cleanup or configuration that then made the scenes function properly from ISY and from programs.

This was quite tedious, but worked consistently on all scenes.

Edited by dex
atmarosi Experienced

atmarosi

Posted
  • Author
Posted
On 9/20/2022 at 6:13 AM, Geddy said:

@atmarosi

I'd try to create a new program (identical to existing programs) and see if a new program works. Also, I assume that you're process of testing the program that you just "run then" and nothing worked. 

I don't use "fast on" so have you tried to just use "on", or is there a reason that it's a "fast on" trigger?

Do other programs work and it's just the ones that turn scenes on/off?

Do the programs that aren't working happen to be in a folder? Is there a chance there are folder settings that aren't allowing those programs to run? If they're in a folder move them to the root program level and see if they work. If they do then you have something in folder settings that aren't allowing programs to run.

 

So I made this 'test' program: 

<?xml version="1.0" ?><triggers><d2d><trigger><id>121</id><name>TEST</name><parent>25</parent><if><and /><control id="DFON" node="2A 3C 4E 1" op="IS"></control></if><then><cmd id="DFON" node="26014"></cmd></then><else></else><comment></comment></trigger></d2d></triggers>

If Kitchen Over head Three way is switch fast on then set the kitchen lights scene to fast on...

didn't work and this was all that was in the event viewer - tried double tapping (fast on) twice: 

Fri 09/23/2022 15:47:19 : [D2D EVENT   ] Event [n004_6c5ab0e2c692] [GV0] [0] uom=2 prec=0
Fri 09/23/2022 15:47:19 : [n004_6c5ab0e2c692]      GV0   0 (uom=2 prec=0)
Fri 09/23/2022 15:47:19 : [D2D EVENT   ] Event [n004_6c5ab0e2963c] [GV0] [0] uom=2 prec=0
Fri 09/23/2022 15:47:19 : [n004_6c5ab0e2963c]      GV0   0 (uom=2 prec=0)
Fri 09/23/2022 15:47:49 : [D2D EVENT   ] Event [n004_6c5ab0e2c692] [GV0] [1] uom=2 prec=0
Fri 09/23/2022 15:47:49 : [n004_6c5ab0e2c692]      GV0   1 (uom=2 prec=0)
Fri 09/23/2022 15:47:49 : [D2D EVENT   ] Event [n004_6c5ab0e2963c] [GV0] [1] uom=2 prec=0
Fri 09/23/2022 15:47:49 : [n004_6c5ab0e2963c]      GV0   1 (uom=2 prec=0)
Fri 09/23/2022 15:48:19 : [D2D EVENT   ] Event [n004_6c5ab0e2c692] [GV0] [0] uom=2 prec=0
Fri 09/23/2022 15:48:19 : [n004_6c5ab0e2c692]      GV0   0 (uom=2 prec=0)

Don't seen any insteon devices in there....not sure what's up...

atmarosi Experienced

atmarosi

Posted
  • Author
Posted
On 9/21/2022 at 8:29 AM, dex said:

After my migration to IoP (5.4.4), none of my scenes would function from the ISY interface until I did the following...

  • For each device right-click > Diagnostics > Query Insteon Engine 
  • Go into each scene and, for each device in the scene, at least click the "Update" button (in the lower section).  For many scenes, I also had to provide the desired settings for that device for that scene.  

This seemed to trigger some final cleanup or configuration that then made the scenes function properly from ISY and from programs.

This was quite tedious, but worked consistently on all scenes.

If I hit the 'fast on' on the scene in question in the above reply from me - in the console - it will turn on the devices just fine as it should.  When I use a program with If control is fast on - then scene fast on; it doesn't do it....

Thoughts?

Geddy Advanced

Geddy

Posted
Posted
2 minutes ago, atmarosi said:

So I made this 'test' program:

If you're trying to post what the program is for you need to right click the program then COPY to Clipboard then past to the forum. I think you did "export to clipboard" to get the "xml" in the post above. Copy to Clipboard is the very last option when you right click the program. 

image.png

 

If you're physically flipping the switch and the ISY still doesn't see the device then there's communication issue. I've never gone through the replace PLM process so kind of at a loss for why it seems to work when you created a new scene, but now they programs don't work. But, now if you're physically triggering a switch and the ISY does not see the event then the PLM links are not there. You might need to factory reset the devices that it doesn't see. 

 

atmarosi Experienced

atmarosi

Posted
  • Author
Posted

Here's the prog:

TEST - [ID 0079][Parent 0019]

If
        'Kitchen Over Head Three way L' is switched Fast On
 
Then
        Set 'Kitchen - Lights' Fast On
 
Else
   - No Actions - (To add one, press 'Action')
 

 

Forgot about where it was; thanks for the reminder :)

 

If i press the switch up/on once - it'll turn the the lights it's physically connected to on.  If i go to the switch in the console it won't show the status as on until i refresh.  Some thing is def up....just not sure what....

 

  • Like 1
kclenden Advanced

kclenden

Posted
Posted
22 minutes ago, atmarosi said:

Some thing is def up....just not sure what....

Insteon works by linking devices to each other via Links Tables in each device.  Given that you've replaced your PLM, and the issues you're having, it seems likely that your Links Table(s) are not correct.  You can do a cursory check of this by looking for device addresses in the corresponding Links Tables.

First, determine what your PLM address is.  Do this by using Tools->Diagnostics->PLM Info/Status.  You should see an address specified by 3 hexadecimal numbers separated by periods in the form xx.xx.xx.

Next look at the switch's Links Table.  Do this by right-clicking on the switch and choosing Diagnostics->Show Device Links Table.  You should see several rows of links that consist of 8 hexadecimal numbers.  The 3rd, 4th, and 5th are the address of a linked device.  You should see your PLM address in several of the rows.  Do you?

kclenden Advanced

kclenden

Posted
Posted (edited)
1 hour ago, atmarosi said:

seems kosher.....

Not quite kosher.  The first hexadecimal number of each row indicates whether the the device is a responder or controller.  There should be an "Ax" and an "Ex" row that contains the address of the PLM.

For example, the first row and seventh row that starts with "A2" says that the switch is a responder to the PLM.  The second hexadecimal number "00" and "19" indicate the scene.

There is no "E2" record for the PLM.  That row would indicate that the switch is a controller of the PLM.  It needs to be there so that when the switch changes states, it will send a command to the PLM.

Note the "EA" records in the 4th-6th rows.  Those indicate that the switch is a controller of other devices (presumably other switches).  Because they're there, the switch will send a command to those other devices whenever it changes states.  Without an "Ex" record for the PLM, the switch will not communicate its state changes to the PLM.

At the bottom of the dialog that shows the device links should be a "Compare" button.  Click it and it will compare the device links with what the ISY thinks the device links should be.

Edited by kclenden
Add info about "compare"
  • Like 1
Guest
This topic is now closed to further replies.
Go to topic listing
×
×
  • Create New...