few communication issues
Posted 09 September 2011 - 07:02 PM
I have a couple of questions.
1. I recently replaced some devices that a were controlled by a keypadLinc 8. when I look at the device controller/responder info it looks as if it was OK. the keypadlinc button does not control them. they do work manually.
I did try the 'restore' feature a few times and it does not seem to work. it writes for a long time, like 10 of minutes.....
2. when I do make changes to the switches it seems to write to the devices for a long, long, long time. is that normal?
3. I recently had a power outage and one of my keypadLinc 8 reset back to a keypad 6 setup. I have tried to restore the device and it does not change it back to the 8 button setup. should that happen?
4. I seem to have to reset the 99i with a power unplug at times and not sure why it is hung. I do this after the java window will not pop up or the login window. not sure why but it seems very unstable.
Any suggestions would be great.
Posted 23 September 2011 - 05:36 AM
When configured, the viewer will show all of the communication ISY sees when a specific action is initiated, like a device restore. The log can be reviewed by someone knowledgeable about Insteon communication to identify what may be causing a communication issue.
To use, navigate to Tools | Diagnostics | Event Viewer.
Specify "Device Communication Events" for the viewing level.
Clear any existing entries by pressing (Clear)
Leave the Event Viewer window open and set focus back on the main Admin Console Window.
Run a specific action you have an issue with
Look at the Event Viewer window and save the log information captured for the action.
Posted 23 September 2011 - 10:24 AM
Posted 16 November 2011 - 12:22 PM
However since the update, and adding the RemoteLinc 2, and replacing a bad Switchlinc (because doing 3 things at once makes troubleshooting so much more fun), I am having massive communication issues. Switches that were working fine are no longer doing what they did yesterday, and My Lighting reports that it cannot communicate with 5-6 devices that were working fine before, and that I did not touch. I can still control the devices from My Lighting.
I do not know where to start.
I cleared the event log, and then tried to query a keypadlinc that is giving me problems, and then I tried to write to device. I get an error, cannot communicate with device.
Also, in trying to upload my event log, it tells me extension txt is not allowed.
Wed 11/16/2011 12:15:12 PM : [INST-ACK ] 02 62 01.1C.D1 0F 19 00 06 LTSREQ (LIGHT)
Wed 11/16/2011 12:15:12 PM : [INST-SRX ] 02 50 01.1C.D1 0F.D6.57 23 01 00 (00)
Wed 11/16/2011 12:15:12 PM : [ 1 1C D1 1] ST 0
Wed 11/16/2011 12:15:12 PM : [ 1 1C D1 1] OL 255
Wed 11/16/2011 12:15:12 PM : [INST-ACK ] 02 62 01.1C.D1 0F 19 01 06 LTSREQ (01)
Wed 11/16/2011 12:15:12 PM : [ 1 1C D1 1] RR 93
Wed 11/16/2011 12:15:21 PM : [INST-ACK ] 02 62 01.1C.D1 0F 19 01 06 LTSREQ (01)
Wed 11/16/2011 12:15:22 PM : [INST-SRX ] 02 50 01.1C.D1 0F.D6.57 23 01 D0 (D0)
Wed 11/16/2011 12:15:30 PM : [1 1C D1 1 ] Using engine version i1 for 'Hall by Master'
Wed 11/16/2011 12:15:30 PM : [1 1C D1 1 ] Link 0 : 0FF8 [A2071C27B1FF1F06] Writing [A2071C27B1FF1F06]
Wed 11/16/2011 12:15:30 PM : [INST-ACK ] 02 62 01.1C.D1 0F 28 0F 06 SET-MSB(0F)
Wed 11/16/2011 12:15:31 PM : [INST-SRX ] 02 50 01.1C.D1 0F.D6.57 23 28 0F SET-MSB(0F)
Wed 11/16/2011 12:15:31 PM : [INST-ACK ] 02 62 01.1C.D1 0F 2B F8 06 PEEK (F8)
Wed 11/16/2011 12:15:40 PM : [INST-ACK ] 02 62 01.1C.D1 0F 28 0F 06 SET-MSB(0F)
Wed 11/16/2011 12:15:49 PM : [INST-ACK ] 02 62 01.1C.D1 0F 28 0F 06 SET-MSB(0F)
Wed 11/16/2011 12:15:49 PM : [INST-SRX ] 02 50 01.1C.D1 0F.D6.57 23 28 0F SET-MSB(0F)
Wed 11/16/2011 12:15:49 PM : [INST-ACK ] 02 62 01.1C.D1 0F 2B F8 06 PEEK (F8)
Wed 11/16/2011 12:15:50 PM : [INST-SRX ] 02 50 01.1C.D1 0F.D6.57 23 2B A2 PEEK (A2)
Wed 11/16/2011 12:15:50 PM : [INST-ACK ] 02 62 01.1C.D1 0F 28 0F 06 SET-MSB(0F)
Wed 11/16/2011 12:15:59 PM : [INST-ACK ] 02 62 01.1C.D1 0F 28 0F 06 SET-MSB(0F)
Wed 11/16/2011 12:15:59 PM : [INST-SRX ] 02 50 01.1C.D1 0F.D6.57 23 28 0F SET-MSB(0F)
Wed 11/16/2011 12:15:59 PM : [INST-ACK ] 02 62 01.1C.D1 0F 2B F9 06 PEEK (F9)
Wed 11/16/2011 12:16:08 PM : [INST-ACK ] 02 62 01.1C.D1 0F 28 0F 06 SET-MSB(0F)
Wed 11/16/2011 12:16:12 PM : [1 1C D1 1 ] Link 0 : 0FF8 [A2071C27B1FF1F06] *Failed Writing [A2071C27B1FF1F06]
Posted 16 November 2011 - 12:49 PM
What is 01.1C.D1
Could be the device itself or something has happened to the phase coupling devices such as Access Points were moved to support the RemoteLinc2 or a new source of powerline interference has developed such as aging CFLs, or some new appliance.
Posted 16 November 2011 - 01:49 PM
I did not move the access points because I knew that could be a source of problems. I had someone from Insteon come to my house and he told me where to put my access points. I have 3 and I will not move them.
I cannot think of anything else that has changed in my house. I do not use CFL's. No new appliances.
The problems all started when I did this upgrade to 3.1.10. I know that does not make sense either.
Any suggestions on where to start looking, or how to go about it? (I think I did not do a reset of the keypadlinc (01.1C.1D) since the problem started.)
One of the changes I made was to replace a switch. The new switch is not accepting commands from the ISY, however, like, the keypadlinc, I can control the keypadlinc, and the new switchlinc from My Lighting, even though I do not seem to be able to write to them.
Posted 16 November 2011 - 02:32 PM
The difference between direct device control and updating the link record is the total number of commands that have to work. To turn the KeypadLinc On or Off requires a single command and Insteon hardware will retry that command several times. To update a link record requires a minimum of 9 commands, possibly 17 commands, to work for the update to complete successfully. Hard to get 9-17 commands to work compared to a single command when there is unreliable communication.
Posted 16 November 2011 - 02:40 PM
Is there a way to test for the communication problem as I start plugging things back in?
Posted 17 November 2011 - 03:42 AM
Is there a way to test for the communication problem as I start plugging things back in?
The ISY offers the scene test as a tool to give one some clue about communication robustness. There are a few tricks to using it effectively, but I have found it to be pretty useful. The primary thing to remember is that if you have any programs enabled that could change the status of any device in your scene-under-test, temporarily disable these programs for the scene test.
Posted 17 November 2011 - 10:16 PM
I then reset my ISY. In the past, to do this, I just disconnected the network cables to it. This time I also unplugged the PLM. I think that was productive.
I can control any switch or device from My Lighting. I am not getting the communication errors I was (I think). I can query. I can restore and write to device.
However, no switch in my house will control any other switch. I have about 37 Insteon devices and instantly, no switch will control another. Also, the timed programs no longer run. I can still control scenes and switches with an IR command, and the ControlLinc, and RemoteLinc 2. Other than that, I have no control.
I can tap-tap to link the switches, but then what is the point of the ISY.
Any suggestions would be greatly appreciated.
Posted 17 November 2011 - 10:45 PM
Suggest picking two devices, a Controller where the paddle is pressed (stay away from KeypadLincs for now) and the Responder that should turn On/Off in response to the paddle press. Right click on the Controller node in the My Lighting tree, select Diagnostics | Show Device Links Table which will display all the link records in the Controller. When complete click on Compare which is a button along the bottom of the Show window. The ISY will compare the link records found against what it thinks should be there. Do the same thing for the Responder device. If any discrepancies are found right click on the device node and select Restore Device which directs the ISY to rewrite all the device link records.
The other thing I would check is that phase coupling is working. Tap the Set button 4 times on one of the Access Points and look at the other Access Point LED to confirm RF communication is happening and they are on opposite phases.
Posted 17 November 2011 - 11:18 PM
(Also, I upgraded to 3.1.12.)
I restored the devices (which I do not think is actually doing anything). I do not see a difference.
Posted 17 November 2011 - 11:29 PM
How many ISY Scenes is this device defined in?
Posted 18 November 2011 - 08:13 AM
(BTW, thank you for the help and for responding so quickly).
Posted 18 November 2011 - 08:15 AM
Posted 18 November 2011 - 08:34 AM
The Request Failed (and some other popup messages) at Admin Console startup problem has been found and will be fixed in the next Beta drop.
With the device listed in Scenes but having the links in the device to support the Scene is a problem. Suggest trying a Restore Device on one device. Repeat the Show Device Links Table after the Restore Device to see if that corrects the missing links. If more links show up then the process will have to be repeated for each device that is not responding. If additional link records are not displayed after the Restore Device the device should be removed from the scene and added back. That should cause the ISY to create the link records to support the Scene. This will have to be done on any device that does not show the required Scene link records.
Posted 18 November 2011 - 08:41 AM
It sounds like starting over might be my best bet. Would that work? Is there an easy was to do that or do I have to manually reset each device in my house? I am not really sure how to go about resetting my whole system (if that is my best bet right now).
Posted 18 November 2011 - 08:53 AM
I would write down the device addresses (Admin Console shows address), delete each device and add it back with New INSTEON Device using top option, erase existing links. Using New INSTEON Device allows the entire process to be done without moving around to each device and a meaning name can be assigned at the same time. Once all the devices have been added back define ISY Scenes and add the appropriate devices to each Scene for device to device control/linking. When adding a device to an ISY Scene as a Controller it is assumed to also be a Responder so all cross-linking is done automatically to keep devices in multi-way circuits in sync.
Posted 18 November 2011 - 09:28 AM
Posted 18 November 2011 - 09:49 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users