Jump to content

Recommended Posts

Posted

It's kind of strange that this is the only device that is having the communication problem. There is a 2450 and a 2456S3 on the opposite side of the wall on the same circuit and they have never had a problem. The only difference that I can see is this switch is controlling a fluorescent light. What can I do to further trace this problem? I have an extra 2476S that isn't installed yet. Would you suggest that I try it on the same light or on one right next to it? I have both a fluorescent light and an incondescent light right next to this switch on the same circuit.

 

As an after thought, here's what is probably a newbie question. If the switch is not communicating with the ISY, then how does the ISY trace show the address of the switch (1C.BF.16)? I delete the device from the ISY, which should erase all knowledge of that device, then run the start linking process which immediately shows the 1C.BF.16 device. This seems to indicate that the ISY is getting some kind of response from the 2476S.

Posted

Disconnect and cap the red load wire. New INSTEON Device can also be tried. Enter the Insteon address, Name, leaving the Device Type set to Auto Discover. Have the Event Viewer active as before so the command responses can be analyzed if it does not work.

 

The message resulting from the Set button press reached the PLM. The commands sent from the PLM got no response. Impossible to tell from the trace if the commands failed to reach the device or the responses failed to come back.

 

After the single Set button message was received (0253) there were no other 025X (inbound) messages from the device.

Posted

I removed the load wire (red) and then did a "start linking" to register it. It registered the first try and now responds to on/off commands from the ISY. I've seen this happen before so I'll leave the load wire disconnected for a day or so to see if the problem comes back. I have some X10 XPNR noise reducers which I used on X10 installations to help with noise on fluorescent lights. Would these filters also work for Insteon?

 

I've included the trace file because when I try to attach it, this web page doesn't allow me to attach a *.txt file.

 

Thanks,

Ken

 

Thu 05/24/2012 04:30:59 PM : [LNK-BGN ] 02 64 01 00 06

 

Thu 05/24/2012 04:31:24 PM : [iNST-SRX ] 02 50 1C.BF.16 00.00.01 CB 17 01 LTMCON (UP)

 

Thu 05/24/2012 04:31:24 PM : [standard-Group][1C.BF.16-->Group=1] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:31:24 PM : [iNST-SRX ] 02 50 1C.BF.16 00.00.01 CB 17 01 LTMCON (UP): Process Message: Ignored

 

Thu 05/24/2012 04:31:24 PM : [standard-Group][1C.BF.16-->Group=1] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:31:32 PM : [LNK-STAT ] 02 53 M(01) gid=00 1C.BF.16 021C 41

 

Thu 05/24/2012 04:31:32 PM : Linked: Linked 1C.BF.16.00 type=02.1C.41

 

Thu 05/24/2012 04:31:32 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00

 

Thu 05/24/2012 04:31:32 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00)

 

Thu 05/24/2012 04:31:32 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 0D 02 (02)

 

Thu 05/24/2012 04:31:32 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:31:32 PM : [1C BF 16 0 ] Calibrating engine version

 

Thu 05/24/2012 04:31:32 PM : [1C BF 16 1 ] Start : Adding device to ISY

 

Thu 05/24/2012 04:31:32 PM : [1C BF 16 1 ] Finish : Adding device to ISY was Successful

 

Thu 05/24/2012 04:31:32 PM : [All ] Writing 0 bytes to devices

 

Thu 05/24/2012 04:31:32 PM : [LNK-BGN ] 02 64 01 00 06

 

Thu 05/24/2012 04:31:33 PM : [iNST-SRX ] 02 50 1C.BF.16 00.00.01 CB 18 00 LTMCOFF(00)

 

Thu 05/24/2012 04:31:33 PM : [standard-Group][1C.BF.16-->Group=1] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:31:51 PM : [ 1C BF 16 1] SMAN 0

 

Thu 05/24/2012 04:31:51 PM : ---- Initializing the linked devices ----

 

Thu 05/24/2012 04:31:51 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)

 

Thu 05/24/2012 04:31:51 PM : [1C BF 16 1 ] Link 0 : 0FF8 [A2001BFD4DFF1F01] Saving [A2001BFD4DFF1F01]

 

Thu 05/24/2012 04:31:51 PM : [1C BF 16 1 ] Link 1 : 0FF0 [E2011BFD4DFF1F01] Saving [E2011BFD4DFF1F01]

 

Thu 05/24/2012 04:31:51 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1

 

Thu 05/24/2012 04:31:52 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00)

 

Thu 05/24/2012 04:32:01 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1

 

Thu 05/24/2012 04:32:01 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00)

 

Thu 05/24/2012 04:32:01 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2E 00 (00)

 

Thu 05/24/2012 04:32:01 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:01 PM : [iNST-ERX ] 02 51 1C BF 16 1B FD 4D 11 2E 00 01 01 00 00 00 00 1C FF 20 00 00 06 00 00

 

Thu 05/24/2012 04:32:01 PM : [Extended-Direct][1C.BF.16-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Thu 05/24/2012 04:32:02 PM : ---- All Linked Devices are now initialized ----

 

Thu 05/24/2012 04:32:02 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 19 00

 

Thu 05/24/2012 04:32:02 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 19 00 06 LTSREQ (LIGHT)

 

Thu 05/24/2012 04:32:02 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 01 FF (FF)

 

Thu 05/24/2012 04:32:02 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:02 PM : ---- Initializing the linked devices ----

 

Thu 05/24/2012 04:32:02 PM : ---- All Linked Devices are now initialized ----

 

Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] OL 255

 

Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] RR 28

 

Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] ST 255

 

Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] OL 255

 

Thu 05/24/2012 04:32:02 PM : [ 1C BF 16 1] RR 28

 

Thu 05/24/2012 04:32:02 PM : [All ] Writing 16 bytes to devices

 

Thu 05/24/2012 04:32:02 PM : [1C BF 16 1 ] Link 0 : 0FF8 [A2001BFD4DFF1F01] Writing [A2001BFD4DFF1F01]

 

Thu 05/24/2012 04:32:02 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F FF 08 A2 00 1B FD 4D FF 1F 01 93

 

Thu 05/24/2012 04:32:02 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F FF 08 A2 00 1B FD 4D FF 1F 01 93 06 (00)

 

Thu 05/24/2012 04:32:03 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00)

 

Thu 05/24/2012 04:32:03 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:03 PM : [MNG-LNK-RSP ] 02 6F 40 E2 00 1C BF 16 02 1C 41 06

 

Thu 05/24/2012 04:32:03 PM : [PLM ] Group 0 : Writing Controller Link matching [1C BF 16 1 ] Link 0 : 0FF8 [A2001BFD4DFF1F01]

 

Thu 05/24/2012 04:32:03 PM : [1C BF 16 1 ] Link 1 : 0FF0 [E2011BFD4DFF1F01] Writing [E2011BFD4DFF1F01]

 

Thu 05/24/2012 04:32:03 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F F7 08 E2 01 1B FD 4D FF 1F 01 5A

 

Thu 05/24/2012 04:32:03 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F F7 08 E2 01 1B FD 4D FF 1F 01 5A 06 (00)

 

Thu 05/24/2012 04:32:04 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00)

 

Thu 05/24/2012 04:32:04 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:04 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 1C BF 16 02 1C 41 15

 

Thu 05/24/2012 04:32:04 PM : [PLM ] Group 1 : Writing Responder Link matching [1C BF 16 1 ] Link 1 : 0FF0 [E2011BFD4DFF1F01]

 

Thu 05/24/2012 04:32:04 PM : [1C BF 16 1 ] Link 2 : 0FE8 [0000000000000000] Writing [00..............]

 

Thu 05/24/2012 04:32:04 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9

 

Thu 05/24/2012 04:32:04 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06 (00)

 

Thu 05/24/2012 04:32:05 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00)

 

Thu 05/24/2012 04:32:05 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:05 PM : [1C BF 16 1 ] Link 3 : 0FE0 : Writing High Water Byte

 

Thu 05/24/2012 04:32:05 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA

 

Thu 05/24/2012 04:32:05 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00)

 

Thu 05/24/2012 04:32:05 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00)

 

Thu 05/24/2012 04:32:05 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:06 PM : [iNST-ERX ] 02 51 1C BF 16 1B FD 4D 11 2F 00 01 01 0F E7 00 00 00 00 00 00 00 00 00 D9

 

Thu 05/24/2012 04:32:06 PM : [Extended-Direct][1C.BF.16-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Thu 05/24/2012 04:32:06 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA

 

Thu 05/24/2012 04:32:06 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06 (00)

 

Thu 05/24/2012 04:32:06 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00)

 

Thu 05/24/2012 04:32:06 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:07 PM : [iNST-ERX ] 02 51 1C BF 16 1B FD 4D 11 2F 00 01 01 0F E7 00 00 00 00 00 00 00 00 00 D9

 

Thu 05/24/2012 04:32:07 PM : [Extended-Direct][1C.BF.16-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

Thu 05/24/2012 04:32:07 PM : [iNST-TX-I2CS] 02 62 1C BF 16 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1

 

Thu 05/24/2012 04:32:07 PM : [iNST-ACK ] 02 62 1C.BF.16 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00)

 

Thu 05/24/2012 04:32:08 PM : [iNST-SRX ] 02 50 1C.BF.16 1B.FD.4D 2B 2F 00 (00)

 

Thu 05/24/2012 04:32:08 PM : [standard-Direct Ack][1C.BF.16-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Thu 05/24/2012 04:32:08 PM : [All ] Writing 0 bytes to devices

Posted

It didn't take long (about 15 minutes) for the 2476S to stop responding to on/off commands with the load wire still disconnected. I tried registering it again and it doesn't work. I'm going to put my other 2476S in this circuit and see what happens.

 

Ken

 

Thu 05/24/2012 04:48:00 PM : ---- Initializing the linked devices ----

 

Thu 05/24/2012 04:48:00 PM : ---- All Linked Devices are now initialized ----

 

Thu 05/24/2012 04:48:00 PM : ---- Add remaining devices ----

 

Thu 05/24/2012 04:48:00 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00

 

Thu 05/24/2012 04:48:00 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00)

 

Thu 05/24/2012 04:48:08 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00

 

Thu 05/24/2012 04:48:08 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00)

 

Thu 05/24/2012 04:48:17 PM : [iNST-TX-I1 ] 02 62 1C BF 16 0F 0D 00

 

Thu 05/24/2012 04:48:17 PM : [iNST-ACK ] 02 62 1C.BF.16 0F 0D 00 06 (00)

 

Thu 05/24/2012 04:48:21 PM : ---- All Remaining Device Added ----

 

Thu 05/24/2012 04:48:21 PM : [All ] Writing 0 bytes to devices

Posted

Unless the switch is malfunctioning I suspect there is something else that is interfering with communication. When it worked the Hops Left counts were indicating good communication between the switch and the PLM. The second small trace (duplicate of first small trace) indicates nothing from the switch. Some other lighting or appliance is cycling On and Off. When On it is blocking communication. When Off Hops Left are good indicating clean communication. Could be a coupling issue. If a 240v appliance is cycling On and Off it could be coupling when On and lose coupling when Off.

Posted

I have an ISY 99i/IR PRO with the A10/X10 module installed. I use MobiLinc HD with an iPad and an iTouch.

While refreshing MobiLinc HD or syncing MobiLinc HD, I get these error messages in the Event Log:

 

 

Thu 05/24/2012 10:17:43 PM : [FileOpen ] Open failed for [/CONF/FF0D0B.REC] ®

Thu 05/24/2012 10:17:43 PM : DB: Cannot init FF0D0B.REC

 

 

I have determined that this is an X10 device (Address: M11) that I added to the Main Tree. And I get an error like this for every X10 device that I add. If I delete the X10 device, the error stops. If I add it back, the error comes back. Is this a bug with Release 3.2.6? Or is this something else?

Posted

Hello Lee,

 

I've replaced the 2476S switch on the fluorescent light with my spare one and so far, it's working just fine. It looks like I may have received a bad switch. Do I contact AARTECH about replacing it if the replacement continues to work?

 

Thanks

Ken

Posted

OK, the new switch also quit responding to commands so it's not a bad switch so we are back to the noise theory. I've been running a trace when testing and have noticed that when the switch quits working, I get an "ERR 1" line. What is that?

 

Fri 05/25/2012 08:14:58 AM : [iNST-SRX ] 02 50 1C.C2.15 1B.FD.4D 2B 13 00 LTOFFRR(00)

 

Fri 05/25/2012 08:14:58 AM : [standard-Direct Ack][1C.C2.15-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Fri 05/25/2012 08:14:58 AM : [ 1C C2 15 1] ST 0

 

Fri 05/25/2012 08:23:37 AM : [iNST-TX-I1 ] 02 62 1C C2 15 0F 11 FF

 

Fri 05/25/2012 08:23:37 AM : [iNST-ACK ] 02 62 1C.C2.15 0F 11 FF 06 LTONRR (FF)

 

Fri 05/25/2012 08:23:41 AM : [ 1C C2 15 1] ERR 1

 

Fri 05/25/2012 08:26:15 AM : [iNST-TX-I1 ] 02 62 1C C2 15 0F 11 FF

 

Fri 05/25/2012 08:26:15 AM : [iNST-ACK ] 02 62 1C.C2.15 0F 11 FF 06 LTONRR (FF)

 

------ No response after this -------

 

If this is a noise problem and the noise disappears, why doesn't the switch start working again. Why do I have to do a "delete from ISY, factory reset, reconfigure switch" to get it back?

 

Thanks,

Ken

Posted

Note the timestamp on the last 02 62 outbound message and the ERR 1 message. This is the ISY timing out after not getting a response from the On command.

 

Fri 05/25/2012 08:23:37 AM : [iNST-TX-I1 ] 02 62 1C C2 15 0F 11 FF

 

Fri 05/25/2012 08:23:37 AM : [iNST-ACK ] 02 62 1C.C2.15 0F 11 FF 06 LTONRR (FF)

 

Fri 05/25/2012 08:23:41 AM : [ 1C C2 15 1] ERR 1

 

There is likely a red ! to the left of the device node when this happens. Right click the node and select Query for the ISY to attempt to communicate with the device again. When the ISY is able to Query the device the red ! will go away and commands should work until the powerline issue comes back.

 

If the powerline issue remains the Query will fail and the ISY will hold communcations until the condition is cleared and the next Query works. Otherwise the ISY would continue to be held up waiting for responses to come back.

Posted

Thanks for the help. I can't seem to trace down the source of the noise but I've added 3 more modules around the house and after I added them, the switch hasn't failed. I see it do retries some times but at least it doesn't fail. I plan on adding more devices so hopefully, that will continue to improve the one switch.

Posted

Thank you. I configured my system with FTWR1 station and it seems that there has been no rain yesterday/today. As I have to reconfigure my system back to our station, would you be kind enough to let me know when you have rain-rate > 0?

 

Thanks again and with kind regards,

Michel

 

We get most of our rainfall one week in the year. :) It finally rained again today, and FTWR1 should be showing non-zero values for rainfall-rate and max-rainfall rate.

 

Thanks for looking into it!

mrp

Posted

Hello mrp!

 

Thanks so very much. Yes, indeed I have:

rain today: 0.26 inches

rain rate: 0.12 inches/hour

 

We are not getting any max rain rates for some reason. It's blank coming from WB ... sorry.

 

With kind regards,

Michel

Posted

Ever since I upgraded from 3.1.17 to 3.2.6 (Lastnight) I get this strange authentication problem.

 

When I login to the Admin GUI, everything appears fine, the Current states show up fine and then about 20 seconds later, another prompt appears asking me to login with my username/password again even though I am in. If I click cancel, I get logged off the Admin gui. If I click my username/password and click OK, I do not get the prompt again untill next time I reopen the Admin gui...

Posted

Hello OmegaQuest,

 

Thank you. Do you have Windows Firewall? This is indeed really odd because all the symptoms point to the fact that ISY can not establish a connection to the Admin Console and thus expires the session.

 

If you go to Help | About, is the UI version 3.2.6?

 

With kind regards,

Michel

Posted

Is it possible that the ISY's static address is within the DHCP range on your router and the address has been issued to another device on your network (ip conflict) ?

 

-Xathros

Posted

hbsh01-

 

Don't worry. Everything is retained through the upgrade. The first part of the update process prompts you to make a backup just in case anything goes wrong. Make sure you clear your Java cache AFTER the upgrade and BEFORE you attempt to log back into the admin console.

 

-Xathros

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...