constant communication error reports

[apostolakisl]

This has been going on for the whole time my system has been installed (about 2 years) and I have been just ignoring it.

 

The deal is that I regularly get pop up messages on the ISY java console telling me that a communication error ocurred. However, the Insteon device still did what it was supposed to do. In addition, if upon seeing the message pop up, I immediately query the switch, it responds without delay.

 

This happens with some switches more than others, but many of them do it.

 

I find it hard to believe that noise is on the line causing the com error and then 2 seconds later when I do the query it responds no prob in a split second.

 

Any ideas on how to get rid of this?

[Michel Kohanim]

Hello apostolakisl,

 

Those error pop ups do NOT mean that the problem happened right then. You see, when ISY tries to do anything with those devices and in case the device either sends a NACK or does not respond at all, then ISY flags that device as having comm errors till the next time anything is done to it. The best method of figuring out when those errors actually happened is to look at the error log and search for -2 (device communication error).

 

It's quite possible that these errors are time dependent and this way we can narrow down what could be causing them.

 

With kind regards,

Michel

[apostolakisl]

So are you saying that when the ISY console is up and running on my computer and my wife walks into the pantry and turns the light on, then 3 minutes later the ISY program runs to conclusion and shuts the light off (which it does do) and simultaneously the error message pops onto my screen, that the error isn't a result of that communication right then and there?

 

Anyway, I pulled up the log and it shows hundreds of -2's. Most occur during "my lighting" querys and may list from 1 to 15 devices in a row out of about 40 Insteon devices. Many of these querys ocurred in the middle of the night when everything in the house would have been off except fridges/HVAC. There are many more querys that have no errors following them (probably 75%)

 

Also, when the ISY sends to excel, it doesn't seem to be sending in the universal date format. I can't change things around.

[Michel Kohanim]

Hello apostolakisl,

 

There are two cases:

1. Admin Console is up and running and there's an error in which case you will see it immediately. This can be caused by two things:

a. ISY cannot communicate with the device

b. The device is sending a NACK

2. Admin Console is not running. At some time in the past, there has been errors which are flagged. As soon as you bring Admin Console up, they will pop up till such time that they are cleared by successful communications

 

The first thing I recommend is figuring out why the 2:00 AM query causes so many device communication errors. This is not normal. Once we have that figured out then we can move on to the rest of the issues.

 

With kind regards,

Michel

[apostolakisl]

I am not sure where to begin with this. Upon closer examination it looks like probably 90% of the "my lighting" querys go off without a hitch.

 

Failures can be anything from one device to as many as 15. Usually it is a few.

 

I don't have a clue as to how to solve the com errors. It seems so random. I don't know where to begin.

 

Ideas?

[Michel Kohanim]

Hello apostolakisl,

 

If you have any FilterLincs around, the first thing I would do is to put some of the devices that are on at 2:00 AM on a FilterLinc (one at a time). Since you have good communications most of the time, the problem must be something that turns on intermittently. And, since most of the errors are happening at 2:00 AM I must suspect a device that is on at that time.

 

So, I think it would be best to start with FilterLincs.

 

With kind regards,

Michel

 

I am not sure where to begin with this. Upon closer examination it looks like probably 90% of the "my lighting" querys go off without a hitch.

 

Failures can be anything from one device to as many as 15. Usually it is a few.

 

I don't have a clue as to how to solve the com errors. It seems so random. I don't know where to begin.

 

Ideas?

[apostolakisl]

Actually it is that the system querys happen in the middle of the night. I get errors during the day too, but they happen one at a time and much less frequently becuase they only have opportunity to pop up when the devices are actually used.

 

At least I do know that whatever is going on, it happens when people aren't running stuff.

 

Other than refridgerators, I can't think of anything that is on at night that isn't on 100% of the time. I hadn't heard of fridges being electrically noisey. Am I wrong?

[oberkc]

I hadn't heard of fridges being electrically noisey. Am I wrong?

 

I have always suspected mine of being a contributor to some noise on the powerlines. My recollection is that there are others around who have voices similar concerns.

[Brian H]

Over in the X10 forums where I assist.

We have seen many new devices that have electronic controls. Causing problems with power line noise and signal absorption.

 

Some of the new electronically controlled HVAC units and furnaces also.

[IndyMike]

At least I do know that whatever is going on, it happens when people aren't running stuff.

 

Other than refridgerators, I can't think of anything that is on at night that isn't on 100% of the time. I hadn't heard of fridges being electrically noisey. Am I wrong?

 

Your powerline exhibits a characteristic impedance per unit length. Each time you turn on a load, you essentially form a voltage divider which will reduce communication signal levels on that branch circuit. Insteon sidesteps this characteristic by allowing each device to repeat the communication and thereby restore the signal level.

 

The same voltage divider applies to noise signals. The situation you have described may be due to a noise source that is transmitting into a lightly loaded powerline (all devices off). Under these conditions, the noise source may be generating at a sufficient amplitude to interfere with your Insteon devices.

 

When you turn loads on during the day, the noise source lacks sufficient capacity to drive the noise signal into the loaded line - and your Insteon system works well.

 

Look for cell phone chargers, PS3 power supplies, etc, that typically go unnoticed and have a habit of moving around.

 

The scene test can be rather handy here since it turns your Insteon devices off, and then performs a one-hop (worst case) communication test. I have a whole house scene test setup for just this purpose.

 

IM

[apostolakisl]

I am not familiar with the "scene test" to which you refer. Could you tell me alittle about that? Thanks.

 

I am getting failed com errors at all times of the day and night. I just get big batches of them at night when the full system queries run. But most of those queries execute with no errors, some with just a few, and some with 15. For example isy was up on my computer and I was eating breakfast two days ago. My wife went into the pantry and turned the light on and a failed to comm warning popped up on the screen.

 

Would it help to say run a full query every hour for a week or two and see if any patterns show up?

[Brian H]

The Scene Test is described in this wiki page.

http://www.universal-devices.com/mwiki/ ... Tools_Menu

[apostolakisl]

Thanks Brian.

 

Here are the results of one scene. A lot of failures are listed yet the scene did execute in full both on and off. Would this mean that I have some low level noise that just barely messes things up on occasion?

 

Mon 10/11/2010 07:56:50 AM : [GRP-RX ] 02 61 1D 13 00 06

 

Mon 10/11/2010 07:56:50 AM : [iNST-SRX ] 02 50 00.2C.36 0F.D5.71 62 13 1D LTOFFRR(1D)

 

Mon 10/11/2010 07:56:50 AM : [standard-Cleanup Ack][00.2C.36-->ISY/PLM Group=0] Max Hops=2, Hops Left=0

 

----- Night Routine Test Results -----

[Failed] Family Rm/Lamp (6 54 2B 1)

[succeeded] Upstairs/Arches L (0 2C 36 1)

[Failed] Dining Room/China Cab L (0 64 7F 1)

[Failed] Living Rm/Piano L (7 7E A6 1)

[Failed] Living Rm/Eyeball (3 71 3A 1)

[Failed] Foyer/Niche (13 42 65 1)

----- Night Routine Test Results -----

Mon 10/11/2010 07:56:58 AM : [iNST-ACK ] 02 62 00.00.1D CF 13 00 06 LTOFFRR(00)

 

Mon 10/11/2010 07:59:06 AM : [iNST-SRX ] 02 50 03.6E.56 00.00.01 C3 11 00 LTONRR (00)

 

Mon 10/11/2010 07:59:07 AM : [standard-Group][03.6E.56-->Group=1] Max Hops=3, Hops Left=0

 

Mon 10/11/2010 07:59:07 AM : [ 3 6E 56 1] DON 0

 

Mon 10/11/2010 07:59:07 AM : [ 3 6E 56 1] ST 155

 

Mon 10/11/2010 07:59:07 AM : [iNST-SRX ] 02 50 03.6E.56 0F.D5.71 41 11 01 LTONRR (01)

 

Mon 10/11/2010 07:59:07 AM : [standard-Cleanup][03.6E.56-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

 

Mon 10/11/2010 07:59:11 AM : [iNST-SRX ] 02 50 03.6E.56 00.00.01 C7 13 00 LTOFFRR(00)

 

Mon 10/11/2010 07:59:11 AM : [standard-Group][03.6E.56-->Group=1] Max Hops=3, Hops Left=1

 

Mon 10/11/2010 07:59:11 AM : [ 3 6E 56 1] DOF 0

 

Mon 10/11/2010 07:59:11 AM : [ 3 6E 56 1] ST 0

 

Mon 10/11/2010 07:59:11 AM : [iNST-SRX ] 02 50 03.6E.56 0F.D5.71 41 13 01 LTOFFRR(01)

 

Mon 10/11/2010 07:59:11 AM : [standard-Cleanup][03.6E.56-->ISY/PLM Group=1] Max Hops=1, Hops Left=0

 

Mon 10/11/2010 07:59:11 AM : [iNST-SRX ] 02 50 03.6E.56 0F.D5.71 42 13 01 LTOFFRR(01)

 

Mon 10/11/2010 07:59:11 AM : [standard-Cleanup][03.6E.56-->ISY/PLM Group=1] Max Hops=2, Hops Left=0

 

Mon 10/11/2010 07:59:11 AM : Duplicate: ignored

 

Mon 10/11/2010 07:59:11 AM : [iNST-SRX ] 02 50 03.6E.56 0F.D5.71 42 13 01 LTOFFRR(01): Process Message: failed

 

Mon 10/11/2010 07:59:11 AM : [standard-Cleanup][03.6E.56-->ISY/PLM Group=1] Max Hops=2, Hops Left=0

[Michel Kohanim]

Hello apostolakisl,

 

Just a quick question: are any of the failing devices SwitchLinc v35?

 

It's very normal for the scene test to fail while the devices actually respond: either they did NOT send group cleanup (ACK) or the signal got lost.

 

If you have SWL v35s, this is basically what happens to most of them.

 

With kind regards,

Michel

[IndyMike]

Hello apostolakisl,

 

Please see Michel's comment on the V35 devices.

 

Mon 10/11/2010 07:56:50 AM : [standard-Cleanup Ack][00.2C.36-->ISY/PLM Group=0] Max Hops=2, Hops Left=0

 

The above is the cleanup "Ack" response from your "Upstairs Arches" device. It's the only device that responded. Curiously, this device was given 2 Hops to respond. I've never seen a 2 hop response to a scene test (only 1 hop). Not sure what the implications are here.

 

The following is what I get for a large scene test. Note that the Lamplinc (highlighted red) did respond during the test. It "failed" because it did not respond with an "Off" condition - the lamp is turned off locally.

 

Mon 10/11/2010 04:01:50 PM : [GRP-RX ] 02 61 30 13 00 06

Mon 10/11/2010 04:01:50 PM : [iNST-SRX ] 02 50 00.35.8A 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:50 PM : [standard-Cleanup Ack][00.35.8A-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:50 PM : [iNST-SRX ] 02 50 01.42.D4 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:50 PM : [standard-Cleanup Ack][01.42.D4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:51 PM : [iNST-SRX ] 02 50 01.42.DC 13.22.F9 E1 13 FE LTOFFRR(FE)

Mon 10/11/2010 04:01:51 PM : [iNST-SRX ] 02 50 03.42.48 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:51 PM : [standard-Cleanup Ack][03.42.48-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:51 PM : [iNST-SRX ] 02 50 03.5F.77 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:51 PM : [standard-Cleanup Ack][03.5F.77-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:51 PM : [iNST-SRX ] 02 50 03.7C.4C 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:51 PM : [standard-Cleanup Ack][03.7C.4C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:52 PM : [iNST-SRX ] 02 50 03.82.89 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:52 PM : [standard-Cleanup Ack][03.82.89-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:52 PM : [iNST-SRX ] 02 50 03.82.89 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:52 PM : [standard-Cleanup Ack][03.82.89-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:52 PM : [iNST-SRX ] 02 50 03.82.89 13.22.F9 61 13 30 LTOFFRR(30): Process Message: failed

Mon 10/11/2010 04:01:52 PM : [standard-Cleanup Ack][03.82.89-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:52 PM : [iNST-SRX ] 02 50 03.C5.2B 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:52 PM : [standard-Cleanup Ack][03.C5.2B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:52 PM : [iNST-SRX ] 02 50 03.D3.46 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:52 PM : [standard-Cleanup Ack][03.D3.46-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:52 PM : [iNST-SRX ] 02 50 05.55.B2 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:52 PM : [standard-Cleanup Ack][05.55.B2-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:53 PM : [iNST-SRX ] 02 50 05.57.66 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:53 PM : [standard-Cleanup Ack][05.57.66-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:53 PM : [iNST-SRX ] 02 50 09.8C.CD 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:53 PM : [standard-Cleanup Ack][09.8C.CD-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:53 PM : [iNST-SRX ] 02 50 0A.A9.A5 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:53 PM : [standard-Cleanup Ack][0A.A9.A5-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:53 PM : [iNST-SRX ] 02 50 0A.DB.0B 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:53 PM : [standard-Cleanup Ack][0A.DB.0B-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:54 PM : [iNST-SRX ] 02 50 0A.E5.EC 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:54 PM : [standard-Cleanup Ack][0A.E5.EC-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:54 PM : [iNST-SRX ] 02 50 0C.77.D2 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:54 PM : [standard-Cleanup Ack][0C.77.D2-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:54 PM : [iNST-SRX ] 02 50 0C.7A.38 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:54 PM : [standard-Cleanup Ack][0C.7A.38-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:54 PM : [iNST-SRX ] 02 50 0D.04.E2 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:54 PM : [standard-Cleanup Ack][0D.04.E2-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

Mon 10/11/2010 04:01:55 PM : [CLEAN-UP-RPT] 02 58 06

Mon 10/11/2010 04:01:55 PM : [iNST-SRX ] 02 50 0F.82.A9 13.22.F9 61 13 30 LTOFFRR(30)

Mon 10/11/2010 04:01:55 PM : [standard-Cleanup Ack][0F.82.A9-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

----- Link Test Test Results -----

[succeeded] Foyer (3 C5 2B 1)

[succeeded] Mud KPL 3 - 1st Floor (9 8C CD 3)

[succeeded] Mud KPL 4 - 2nd Floor (9 8C CD 4)

[succeeded] Fam Fan (5 55 B2 1)

[succeeded] Mud KPL 1 - Entry Garage (9 8C CD 1)

[succeeded] Master Fan (5 57 66 1)

[succeeded] Foyer KPL 5 - Kitchen Cans (A E5 EC 5)

[succeeded] Foyer KPL 6 - Dinnette (A E5 EC 6)

[succeeded] Foyer KPL 3 - Foyer (A E5 EC 3)

[succeeded] Foyer KPL 4 - Bar Cans (A E5 EC 4)

[succeeded] Foyer KPL 1 - Bar Lamp (A E5 EC 1)

[succeeded] Family Room Lamplinc (1 42 D4 1)

[Failed] Family Room LampLinc (1 42 DC 1)

[succeeded] Matt Switch (3 82 89 1)

[succeeded] Master KPL 2 - Matt (A DB B 2)

[succeeded] Master KPL 1 - Master Overhea (A DB B 1)

[succeeded] Master KPL 4 - David (A DB B 4)

[succeeded] Master KPL 3 - Kath (A DB B 3)

[succeeded] Master KPL 5 - 1st Floor (A DB B 5)

[succeeded] Master KPL 7 - Flood (A DB B 7)

[succeeded] Entry Patio (C 7A 38 1)

[succeeded] BSMT Lamplinc (F 82 A9 1)

[succeeded] David Switch (3 7C 4C 1)

[succeeded] Fireplace Spots (0 35 8A 1)

[succeeded] Fam KPL 1 - Wall (A A9 A5 1)

[succeeded] Entry Porch (3 42 48 1)

[succeeded] Fam KPL 2 - Fireplace Spots (A A9 A5 2)

[succeeded] Bar Cans (3 5F 77 1)

[succeeded] Kitchen Cans (D 4 E2 1)

[succeeded] Kath Icon (3 D3 46 1)

[succeeded] Fam KPL 4 - Fan (A A9 A5 4)

[succeeded] Fam KPL 3 - Lamps (A A9 A5 3)

[succeeded] Fam KPL 6 - Entry (A A9 A5 6)

[succeeded] Fam KPL 5 - 1st Floor (A A9 A5 5)

[succeeded] Entry Deck (C 77 D2 1)

----- Link Test Test Results -----

 

Please proceed as follows -

1) Verify that you do not have V35 devices in the scene. If you do, try another scene that does not include V35 devices.

2) Turn off "automatic updates" and re-try your scene test.

3) If both of the above fail, try relocating your PLM. It's possible that you have a noise source near the PLM that is not allowing it to hear the devices responding. The devices can hear the PLM, not vice-versa.

 

At one time, I did have problems with a CFL that interfered with my PLM reception. That post is located here - http://forum.universal-devices.com/viewtopic.php?t=4265&start=0&postdays=0&postorder=asc&highlight=

[apostolakisl]

Thanks for the suggestions.

 

I don't have any v35 switchlincs anywhere in the house. That scene had an appliance link, a lamp linc, an icon lamplinc, two switchlincs, and an icon dimmer switch.

 

I am not sure what is meant by "turn off automatic updates". Could you be more specific?

 

I will try running an extension cord from another ciruit to the plm for testing.

 

I was considering turning off circuits in the house one at a time and running tests to see if that spots any problems. Of course this will give false positives when it trys to communicate with insteon items that are located on powered down circuits.

[apostolakisl]

Figuring out these errors is not making sense. I have found that the same kpl will fail and succeed in two different scenes. For example, I have a kpl next to my bed, one button controls a local scene in the bedroom and another controls a distant set of lights. The local scene passes, the distant scene fails (the other switches in the scenes passed). I repeated the test a bunch of times and it does the same each time. How?????

 

Also, I will have multiple switchlincs in the same gang box. One switch passes in its scene and another nest to it fails in its scene.

 

One time when I started testing scenes, every single thing failed. I didn't have time to look for a noise source at the time, but that situation hasn't repeated itself.

 

I did plug the PLM into a different circuit, that doesn't seem to have changed anything.

 

I am at a loss.

[IndyMike]

Hello apostolakisl,

 

Sorry the "automatic updates" was poor terminology on my part. I should have said "Automatic writes to devices". These can interfere with the scene test. Please see below -

 

 

Beyond the above, I have encountered scene test failures due to -

1) CFL noise affecting the PLM (post I linked to previously).

2) Device link table errors.

 

Let's take this a step at a time -

 

Since you have a KPL that passes in one scene and fails in another, I would suspect a link table error in that device. Please perform a link table comparison on this device:

 

1) Show device links table - Wiki - Show Links Table

2) After the link table scan is complete - click the compare button (lower right in the window) and the links will be compared to the ISY.

3) If there are differences between the device and the ISY, try a restore on the device.

 

Please re-try your scene test(s) and post the results,

 

IM

[apostolakisl]

Thanks for clarifying things.

 

So I ran a links table on the device and did a comparison. There was one mismatch and 2 extras. I restored the device and now there are 2 mismatches but the extras are gone.

 

Should I keep doing this until it gets it right?

[Brian H]

IndyMike; I take it the "Do Not Automatically Write Changes To Devices" is an added feature in the Plus Version of ISY. Since I have no such choices.

[apostolakisl]

So I did a second restore device and this time the tables matched. Then I ran two scene tests involving button c and the master on/off button for the kpl (the same ones I ran before). Again, just as before, the button c scene failed and the master on/off button passed.

 

Just a note here, but I have only run a sampling of scene tests, this is not an exhaustive all inclusive fail/pass rate.

[IndyMike]

Please post the results of your scene tests. If your KPL load button responds properly, the C button should also.

 

Please also check that you have "Automatic" selected under \link management\advanced options\.

 

So I did a second restore device and this time the tables matched. Then I ran two scene tests involving button c and the master on/off button for the kpl (the same ones I ran before). Again, just as before, the button c scene failed and the master on/off button passed.

 

Just a note here, but I have only run a sampling of scene tests, this is not an exhaustive all inclusive fail/pass rate.

[IndyMike]

Hello Brian,

 

I thought this was standard across all the ISY-99. Are you using an ISY-26?

 

IndyMike; I take it the "Do Not Automatically Write Changes To Devices" is an added feature in the Plus Version of ISY. Since I have no such choices.

[apostolakisl]

OK, I ran the scene test again and got the same result.

 

The first listed scene test is a simple scene involoving only two switches, the KPL and a second switch which controls the load.

 

The second scene has a few more switches and involves button C on the same KPL. The one switch that failed is actually absent as a result of bad paddle issue. Fedex is scheduled to drop off the replacement tomorrow.

 

This is one example of at least 3 where the same hardware is succeeding in one scene and failing in another scene.

 

Also, the "automatic" setting under link management/advanced was checked.

 

 

Thu 10/14/2010 08:04:43 PM : [GRP-RX ] 02 61 1C 13 00 06

 

Thu 10/14/2010 08:04:43 PM : [iNST-SRX ] 02 50 12.29.64 0F.D5.71 61 13 1C LTOFFRR(1C)

 

Thu 10/14/2010 08:04:43 PM : [standard-Cleanup Ack][12.29.64-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Thu 10/14/2010 08:04:43 PM : [CLEAN-UP-RPT] 02 58 06

 

Thu 10/14/2010 08:04:43 PM : [iNST-SRX ] 02 50 05.15.36 0F.D5.71 62 13 1C LTOFFRR(1C)

 

Thu 10/14/2010 08:04:43 PM : [standard-Cleanup Ack][05.15.36-->ISY/PLM Group=0] Max Hops=2, Hops Left=0

 

----- Master Bed S Test Results -----

[succeeded] Master/Cans over Bed (12 29 64 1)

[succeeded] Master Bedroom Keypad (5 15 36 1)

----- Master Bed S Test Results -----

 

 

And now the second scene test

 

Thu 10/14/2010 08:04:03 PM : [GRP-RX ] 02 61 17 13 00 06

 

Thu 10/14/2010 08:04:06 PM : [iNST-SRX ] 02 50 0D.16.85 0F.D5.71 61 13 17 LTOFFRR(17)

 

Thu 10/14/2010 08:04:06 PM : [standard-Cleanup Ack][0D.16.85-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Thu 10/14/2010 08:04:06 PM : [iNST-SRX ] 02 50 0D.19.7C 0F.D5.71 61 13 17 LTOFFRR(17)

 

Thu 10/14/2010 08:04:06 PM : [standard-Cleanup Ack][0D.19.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Thu 10/14/2010 08:04:06 PM : [CLEAN-UP-RPT] 02 58 06

 

Thu 10/14/2010 08:04:06 PM : [iNST-SRX ] 02 50 00.7B.38 0F.D5.71 61 13 17 LTOFFRR(17)

 

Thu 10/14/2010 08:04:06 PM : [standard-Cleanup Ack][00.7B.38-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

----- Upstairs Hall S Test Results -----

[succeeded] Upstairs Frt Bed/Hall (D 16 85 1)

[Failed] Mstr Bed Key C Upstairs (5 15 36 5)

[Failed] Upstairs by Utility/Hall (3 87 88 1)

[succeeded] Upstairs by Gst/Hall L (D 19 7C 1)

[succeeded] Foyer @ Stairs/A (0 7B 38 3)

----- Upstairs Hall S Test Results -----

[IndyMike]

apostolakisl,

 

Thank you for again posting the scene test results. There may actually be a pattern here. Your "problem" KPL isn't responding correctly in either test.

 

Thu 10/14/2010 08:04:43 PM : [GRP-RX ] 02 61 1C 13 00 06

 

The above is a group command instructing the scene devices to turn off and provide an acknowledge with "1 hop" (1 transmission).

 

Thu 10/14/2010 08:04:43 PM : [iNST-SRX ] 02 50 12.29.64 0F.D5.71 61 13 1C LTOFFRR(1C)

Thu 10/14/2010 08:04:43 PM : [standard-Cleanup Ack][12.29.64-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

The above is the response from your "master cans". It responded properly in one hop (the indicated "61").

 

Thu 10/14/2010 08:04:43 PM : [iNST-SRX ] 02 50 05.15.36 0F.D5.71 62 13 1C LTOFFRR(1C)

Thu 10/14/2010 08:04:43 PM : [standard-Cleanup Ack][05.15.36-->ISY/PLM Group=0] Max Hops=2, Hops Left=0

 

Your "Master bed KPL" responded, but indicated 2 hops (the 62 indicated). This was not what the ISY requested, and is an error in my mind (I've never encountered this). If the KPL mis-interpreted this communication, I have no idea what it did for your other scene that used the "C" button.

 

At the moment I'm thinking you have a "rogue" KPL. Please post the firmware version and date code. It's possible that others can help with this anomaly.

 

IM