Jump to content

FredT

Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

FredT's Achievements

Newbie

Newbie (1/6)

3

Reputation

  1. Thanks Paul, that did it. Although I did have to check the "LED" box for the unit in the Admin Console.
  2. Hello- Had to replace my PML. Did a restore PLM and restore devices. This seemed to get most things working. Howerver, I have two Mini Remotes (4-switch) and neither work properly. I seem to remember have this problem years ago. I think the fix was to manually relink the remotes to the PLM. Is this correct? And if so, how does one do that? Thanks. ...Fred
  3. Finally got it to work. Moving the remote closer to the PLM did not help, I had tried that many times before. Same for the factory reset. Then I got the idea to move it closer to some other dual band devices. First near a back of three recently purchased SwitchLincs that are on another AC phase, only five feet from the PLM but on the other side of a common wall. Still no joy. Then I thought to try something on the same AC phase as the PLM. I tried a brand new on/off module that I had purchased for the Christmas tree, but hadn't used. Plugged it in, set the remote to linking mode, and put it down about five feet from the module. Presto, the ISY was able to link to it. Once linked, the on/off module is not needed. The ISY sees button presses on the remote and can respond with complex commands as I had wanted. I'm guessing that for some reason the remote was having problems seeing the engine query. Could be a weak receiver on the remote or some interference or a combination. The ISY has absolutely no problem sense key presses on the remote in any room in my house. So what the communication problem was, it was asymmetrical. ...Fred
  4. LeeG: Still doesn't work. What next? My problem doesn't seem to be too different than that reported by goldband in April 2013 GuitarBuilder in May and buzzhazard in December in this thread: viewtopic.php?f=28&t=11233&hilit=2342 It seems they gave up without a resolution. I think my problem is not unique to me. I'm not sure whether this is an UDI or SmartLabs issue. But, as a customer of both, I'd be annoyed if the two companies couldn't come together with a solution. Can't be that hard. ...Fred
  5. Yes, I've been doing as you say. Just wasn't aware it was necessary. But sorry to say, still does not work even when I place the Mini within 2 feet of the dual band PLM. Although the two remotes I own look identical, the older remote is a RemoteLinc2 Model 2444A2 v1.1 and works as expected with the ISY. The new remote is a Mini Remote Model 2342-2 v1.4 and is being very stubborn with the ISY. Is there any significants to this difference?
  6. I thought all I needed to do was to wake the RemoteLinc by toggling one of its switches just prior to linking with the ISY. My PLM is dual mode and I am doing the linking attempts in the same room, about 10 ft. from the PLM. I tried again from about 5 ft. and again at about 2 ft. Still same. I know I have the correct address because I can check it using the UDI admin console by display the link tables of devices (switches) that I have linked to it. I have another, much older RemoteLinc 2 (V1.1) that I had already linked to the ISY years ago. It works fine when used at the same location.
  7. By "linking mode", I assume you mean holding the link button until the LED flashes green as I did when I linked it to the wall switches. Just tried that but sadly the same result: Fri 02/07/2014 02:11:12 PM : [26 88 6C ] Added to list of devices to link to ISY Fri 02/07/2014 02:11:12 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00 Fri 02/07/2014 02:11:12 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00) Fri 02/07/2014 02:11:20 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00 Fri 02/07/2014 02:11:21 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00) Fri 02/07/2014 02:11:29 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00 Fri 02/07/2014 02:11:29 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00) Fri 02/07/2014 02:11:33 PM : [26 88 6C 0 ] Failed to add device, reason 3 Fri 02/07/2014 02:11:33 PM : [All ] Writing 0 bytes to devices Do I need to do anything to the PLM?
  8. If you mean just prior, no. If you mean ever, then less; it is linked to some switches now. Yes, it works fine controlling the linked switches. Fri 02/07/2014 01:20:08 PM : [26 88 6c ] Added to list of devices to link to ISY Fri 02/07/2014 01:20:08 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00 Fri 02/07/2014 01:20:08 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00) Fri 02/07/2014 01:20:17 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00 Fri 02/07/2014 01:20:17 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00) Fri 02/07/2014 01:20:25 PM : [iNST-TX-I1 ] 02 62 26 88 6C 0F 0D 00 Fri 02/07/2014 01:20:25 PM : [iNST-ACK ] 02 62 26.88.6C 0F 0D 00 06 (00) Fri 02/07/2014 01:20:29 PM : [26 88 6C 0 ] Failed to add device, reason 3 Fri 02/07/2014 01:20:29 PM : [All ] Writing 0 bytes to devices
  9. I have seen other posts about difficulties adding this device. It seem the solutions others worked out don't for me. I have recently purchased an ISY-994i to replace my 99, specifically because of this problem. I have also upgraded the 994's firmware to V4.1.1. I've attempted to add it as a RemoteLinc2 and generic Insteon device to no avail. Every attempt results in the dreaded "Cannot determine Insteon Engine" and the following is shown in the Event Viewer: Fri 02/07/2014 11:44:22 AM : [26 88 6C ] Added to list of devices to link to ISY Fri 02/07/2014 11:44:44 AM : [26 88 6C 0 ] Failed to add device, reason 3 Fri 02/07/2014 11:44:44 AM : [All ] Writing 0 bytes to devices I've set the remote to factory defaults. The particular Mini Remote is: 2342-2 v1.4 1337. Help!! ...Fred
  10. Me too. After Java update on Win7.
  11. Thanks. That did the trick. I think the problem crept into my sytem when I swamped PLMs to troubleshoot a communication problem. ...Fred
  12. I would think that the ISY status would respond to manual lighting changes, but I don't see that happening. For example I have a INSTEON wall switch controlling a light. When I use either the web interface or the Admin Console to change turn the switch on or off, the status of the change is reflected in the displayed state. However, if I manual push the wall switch, neither ISY program shows a status change. I must query the device through either program for it to show this status change. I see no status update messages in the event viewer when I manually press switches. Do I need to cross-link the switch back to the PLM? ...Fred
×
×
  • Create New...