petermadams Posted November 5, 2012 Share Posted November 5, 2012 Hello, I just purchase two RemoteLinc-2 devices, charged them up and tried to link then to my ISY994i, but I never get any response. I have the devices on the desk beside me, alongside two RemoteLinc devices, and a dual-band light module plugged in 6ft away. Since I can never connect to either device, could this be an issue with the v3.3.3 firmware? I tried manually linking them to an appliance module (I understand that linking should always be through an ISY scene) just to test the wireless connection. Both devices seem to work. -PeterM Link to comment
LeeG Posted November 5, 2012 Share Posted November 5, 2012 Use New INSTEON Device, enter the Insteon Address, Name of choice, and leave the Device Type set to Auto Discover. Before clicking OK put the RemoteLinc2 into linking mode by pressing the Set button until the LED blinks continuously. Put only one RemoteLinc 2 into linking mode at a time. Putting both into linking mode will cause the linking mode to be cancelled. Also suggest standing the RemoteLinc2 vertically rather than laying horizontally. Link to comment
petermadams Posted November 5, 2012 Author Share Posted November 5, 2012 Thanks Lee. I have been trying exactly as you describe. Thanks for the confirmation. I am only doing one at a time, and I just tried it 'vertically'. I still get the "cannot determine the Insteon engine" error. Here is the event log: Mon 11/05/2012 02:11:29 PM : [1c 4a ff ] Added to list of devices to link to ISY Mon 11/05/2012 02:11:47 PM : [iNST-TX-I1 ] 02 62 1C 4A FF 0F 0D 00 Mon 11/05/2012 02:11:47 PM : [iNST-ACK ] 02 62 1C.4A.FF 0F 0D 00 06 (00) Mon 11/05/2012 02:11:51 PM : [1C 4A FF 0 ] Failed to add device Since I have two new devices, I find it hard to believe both are not working, and so I suspect something with my ISY setup/version 3.3.3. But I am not sure how to debug further (I am still a newbie to all this). -PeterM Link to comment
LeeG Posted November 5, 2012 Share Posted November 5, 2012 I do not think it is a RemoteLinc2 problem. The error message is the result of not getting back the expected 02 50 inbound message from the RL2. The following is a trace from 3.3.3 of the Query Insteon Engine (same command in your trace) which shows the missing 02 50 inbound message because I failed to put the RL2 into linking mode (not your situation but same result. Without being in linking mode the command was not received so it would not be answered Mon 11/05/2012 05:39:47 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 0D 00 Mon 11/05/2012 05:39:47 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 0D 00 06 (00) Mon 11/05/2012 05:39:55 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 0D 00 Mon 11/05/2012 05:39:55 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 0D 00 06 (00) Mon 11/05/2012 05:40:04 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 0D 00 Mon 11/05/2012 05:40:04 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 0D 00 06 (00) Mon 11/05/2012 05:40:08 PM : [ 1C 27 E3 1] ERR 1 The following is what the trace should look like when the RL2 can communicate with the ISY PLM. Mon 11/05/2012 05:40:51 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 0D 00 Mon 11/05/2012 05:40:51 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 0D 00 06 (00) Mon 11/05/2012 05:40:52 PM : [iNST-SRX ] 02 50 1C.27.E3 19.70.06 2B 0D 01 (01) With multiple RL2s having the same problem they are not in range of a Dual Band device or the phase coupling is not working. Applications like the ISY have control over the RF aspects of the Insteon mesh network. RF communication is automatic and autonomous. There could be interference from things like baby monitors which operate on the same frequencies as Insteon RF. Could be out of range or the phases are not coupled because the Dual Band devices are out of range of each other or are not on opposite 120v legs. Change the location of the RL2. If the ISY PLM is Dual Band move the RL2 to the PLM location. EDIT: some of the older Venstar dongles had comm problems which blocked RF communication. Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 I am having an issue with the Remotelinc-2 as well. Just won't pair. Got close a time or two AFTER it is basically timing out. I even put it ON the access point Sat 12/15/2012 08:35:29 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:35:29 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:35:29 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:35:29 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:29 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:35:38 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:38 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:35:48 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:48 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:35:52 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:35:52 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:35:57 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:35:57 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:35:57 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:35:57 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:35:57 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:06 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:06 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:15 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:15 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:19 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:36:19 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:36:19 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:36:19 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:36:19 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:19 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:19 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:36:28 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:28 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:37 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:37 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:36:41 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:36:41 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:36:59 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:36:59 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:36:59 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:36:59 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:36:59 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:08 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:08 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:17 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:17 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:21 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:37:21 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:37:21 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:37:21 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:37:21 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:21 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:21 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:37:30 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:30 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:39 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:39 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:43 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:37:43 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:37:43 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:37:43 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:37:43 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:43 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:37:43 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:37:52 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:37:52 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:01 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:01 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:05 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:38:05 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:38:05 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:38:05 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:38:05 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:05 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:38:05 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:14 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:14 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:23 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:23 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:27 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:38:27 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:38:47 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:38:47 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:38:47 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:38:47 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:47 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:38:56 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:38:56 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:39:05 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:39:05 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:39:09 PM : ---- All Remaining Device Added ---- Sat 12/15/2012 08:39:09 PM : ---- Initializing the linked devices ---- Sat 12/15/2012 08:39:09 PM : ---- All Linked Devices are now initialized ---- Sat 12/15/2012 08:39:09 PM : ---- Add remaining devices ---- Sat 12/15/2012 08:39:09 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:39:09 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Sat 12/15/2012 08:39:09 PM : [All ] Writing 0 bytes to devices Sat 12/15/2012 08:39:18 PM : [iNST-TX-I1 ] 02 62 1C 3D 83 0F 0D 00 Sat 12/15/2012 08:39:18 PM : [iNST-ACK ] 02 62 1C.3D.83 0F 0D 00 06 (00) Link to comment
LeeG Posted December 16, 2012 Share Posted December 16, 2012 There is no response from the device with Insteon address 1C 3D 83. There will be trace entries that start with 02 50 or 02 51 when the device is communicating. Sitting on an Access Point may not be the best thing compared to a few feet away. Set the RL2 vertically rather than laying flat. Be sure the RemoteLinc2 LED is blinking showing it in linking mode before starting the device add process. Double check the device address. Sometimes 8s and Bs look the same. Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 That is the part that is maddening. Been all over the house. Once when I had my tongue the correct way, the write failed after it got it going. The only other time it communicated was just as the rl2 timed out! Also having trouble with a motion sensor taking the write from the isy. I can watch the access point blink right when the RL2 goes into linking mode. Alan Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 And a silly question. Does the remote linc 2 need to be linked to the access point first, or do they blindly relay every radio wave insteon command they get? Link to comment
Brian H Posted December 16, 2012 Share Posted December 16, 2012 Access Points do not link to anything. The set button on them starts the communications tests with the four tap sequence. Users manual has details on how this test works. If you have not verified proper phase coupling and communications. I suggest you do the tests with the Access Points. Link to comment
LeeG Posted December 16, 2012 Share Posted December 16, 2012 arw01 As Brian has already indicated nothing is linked to Access Points. All RF aspects of the Insteon mesh network are automatic. Once a Dual Band device has power the RF side is functional. The Motion Sensor symptom is consistent. There is some problem with RF where the devices are being tested. Could be interfering with RF activity or the powerline signal is not reaching the PLM location. Are there Venstar thermostats with the Insteon dongle. Some of the older units have been known to create RF issues but I thought SH had replaced as those dongles. Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 Access Points do not link to anything.The set button on them starts the communications tests with the four tap sequence. Users manual has details on how this test works. If you have not verified proper phase coupling and communications. I suggest you do the tests with the Access Points. Three access points all in proper LED mode, and 2 dual band PLM's (one being used to test what's up with houselinc) Any other testing I can do there? I confirmed by watching each individual led, that when either the 2420M set button is pressed the access point(s) blink. Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 arw01 As Brian has already indicated nothing is linked to Access Points. All RF aspects of the Insteon mesh network are automatic. Once a Dual Band device has power the RF side is functional. The Motion Sensor symptom is consistent. There is some problem with RF where the devices are being tested. Could be interfering with RF activity or the powerline signal is not reaching the PLM location. Are there Venstar thermostats with the Insteon dongle. Some of the older units have been known to create RF issues but I thought SH had replaced as those dongles. No Venstar here. I have run houselinc with a second plm I have, just a plain 2413S and can confirm both the motion sensor links and the remote linc links up. I can see the traffic with the verbose logs by pressing a button on the remotelinc 2. Therefore I can accurately surmise there is at least SOME rf working around here. Took a walk around the house, see houselinc log below: 2012-12-16 08:50:59,546 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:50:59,765 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:52:48,859 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:52:49,078 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:52:54,812 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:52:54,968 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:53:14,875 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:53:15,093 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:53:22,656 [11] DEBUG - Checking gateway communication... 2012-12-16 08:53:22,671 [11] DEBUG - Tx: Get PLM Config Flag 2012-12-16 08:53:22,671 [16] DEBUG - Rx: PLM Ack, 02 73 48 00 60 06 2012-12-16 08:54:04,796 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:05,015 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.02, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:16,375 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:16,593 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:25,312 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.04, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:25,531 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.04, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 00 2012-12-16 08:54:33,515 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.03, Flag: C3 (Hops: 0/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:33,640 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.03, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:54:41,265 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:54:41,500 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 13 (Light OFF), C2: 01 2012-12-16 08:54:53,656 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: CB (Hops: 2/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:54:53,937 [16] DEBUG - Rx: Std Msg, From: 14.1A.66, To: 00.00.01, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 01 2012-12-16 08:55:09,750 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.05, Flag: C3 (Hops: 0/3), C1: 11 (Light ON), C2: 00 2012-12-16 08:55:09,890 [16] DEBUG - Rx: Std Msg, From: 1C.3D.83, To: 00.00.05, Flag: C7 (Hops: 1/3), C1: 11 (Light ON), C2: 00 Link to comment
oberkc Posted December 16, 2012 Share Posted December 16, 2012 I confirmed by watching each individual led, that when either the 2420M set button is pressed the access point(s) blink. This is not necessarily enough to confirm being on opposite legs of your electrical system. You also need to follow the included directions for this test. Given your description, it sounds as if you have good RF communication between remotelinc and access points. Given this I would start to suspect comm is not reaching PLM. One thing I would check for is other equipment on the circuit with the PLM. D you have a quantity of other devices on this circuit? Computers? Surge suppressors? UPS? Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 Got em just moments ago, both are added now.. Wierdness. I even unplugged the second PLM just in case that was the reason they linked up, and they are still received. I will unplug the 3rd access point and try them around the house again to make sure the other 2 access points and the ISY 2413SHplm pick them up. Then that third access point can go out to the shop or garage if it's in range, and I can use the remotelinc as the control of my dust collector as planned. Alan Link to comment
LeeG Posted December 16, 2012 Share Posted December 16, 2012 I can't think of anything to test. RF is not under control of the application (ISY in this case). RF should be automatic when the Dual Band devices have power. If the PLM is a 2413 try placing the RL2 or Motion Sensor a few feet from the PLM which would eliminate the other aspects of the Insteon network. Not that it matters to RF but HouseLinc will not run with a standard 2413 PLM. It has to be a 2413SH or 2413UH. Also note that the Group 1 message sequence from the devices is not complete and there is no outbound traffic to the devices. For HL PLM to accept these messages there must be a link in the PLM for the device addresses. That PLM should not be powered while trying to link those devices to the ISY Link to comment
arw01 Posted December 16, 2012 Share Posted December 16, 2012 I can't think of anything to test. RF is not under control of the application (ISY in this case). RF should be automatic when the Dual Band devices have power. If the PLM is a 2413 try placing the RL2 or Motion Sensor a few feet from the PLM which would eliminate the other aspects of the Insteon network. Not that it matters to RF but HouseLinc will not run with a standard 2413 PLM. It has to be a 2413SH or 2413UH. I happen to have both. The 2413SH is connected to the ISY. I think that the 2413SH is only needed when you first setup Houselinc, once it's up and running, it has never cared which of my two PLM's I use. Also note that the Group 1 message sequence from the devices is not complete and there is no outbound traffic to the devices. For HL PLM to accept these messages there must be a link in the PLM for the device addresses. That PLM should not be powered while trying to link those devices to the ISY I happen to have both PLM's connected, the 2413S to the HL, and 2413SH to the ISY when I was finally able to get the Remotelinc and the first motion sensor going. When I connected the second motion sensor, I had only the ISY plm connected. Yep, some strange stuff there, but it's up! Link to comment
LeeG Posted December 16, 2012 Share Posted December 16, 2012 Glad to hear the devices are defined. Unfortunately since the RF issue was not identified it will likely appear again. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.