oatflake Posted December 3, 2011 Posted December 3, 2011 Hello aotflake, Thanks so very much for the information. The best debugging tool would be: 1. Remove RL from your ISY 2. Open Event Viewer on Device Communications level 3. Add RL to your ISY 4. Save the Event Viewer contents and clear it 5. Go to Tools | Diagnostics | Show PLM Links Table and click Start 6. Once done, save the contents Please send me both 4 and 6. With kind regards, Michel My PLM Links Table is blank once I turn off my Access Points, since all of the devices are only reachable on the other phase of my house. This is the output from the Event Viewer when I add the device without the Access Points, placing it about 4 feet away from my PLM: Fri 12/02/2011 07:00:04 PM : [iNST-SRX ] 02 50 14.75.62 00.00.01 CB 13 01 LTOFFRR(01) Fri 12/02/2011 07:00:04 PM : [standard-Group][14.75.62-->Group=1] Max Hops=3, Hops Left=2 Fri 12/02/2011 07:00:04 PM : [iNST-SRX ] 02 50 14.75.62 00.00.01 CB 13 01 LTOFFRR(01): Process Message: failed Fri 12/02/2011 07:00:04 PM : [standard-Group][14.75.62-->Group=1] Max Hops=3, Hops Left=2 Fri 12/02/2011 07:00:04 PM : [iNST-SRX ] 02 50 14.75.62 00.00.01 CB 13 01 LTOFFRR(01) Fri 12/02/2011 07:00:04 PM : [standard-Group][14.75.62-->Group=1] Max Hops=3, Hops Left=2 Fri 12/02/2011 07:00:04 PM : [iNST-SRX ] 02 50 14.75.62 00.00.01 CB 13 01 LTOFFRR(01): Process Message: failed Fri 12/02/2011 07:00:04 PM : [standard-Group][14.75.62-->Group=1] Max Hops=3, Hops Left=2 Fri 12/02/2011 07:00:43 PM : ---- Initializing the linked devices ---- Fri 12/02/2011 07:00:43 PM : ---- All Linked Devices are now initialized ---- Fri 12/02/2011 07:00:43 PM : ---- Add remaining devices ---- Fri 12/02/2011 07:00:43 PM : [ 14 75 62 1] Writing High Water Mark at Link 0 Fri 12/02/2011 07:00:43 PM : [14 75 62 1 ] Querying engine version Fri 12/02/2011 07:00:43 PM : [iNST-ACK ] 02 62 14.75.62 0F 0D 00 06 (00) Fri 12/02/2011 07:00:52 PM : [iNST-ACK ] 02 62 14.75.62 0F 0D 00 06 (00) Fri 12/02/2011 07:01:01 PM : [iNST-ACK ] 02 62 14.75.62 0F 0D 00 06 (00) Fri 12/02/2011 07:01:05 PM : [14 75 62 1 ] Failed getting engine version. Reverting to i1 Fri 12/02/2011 07:01:05 PM : [14 75 62 1 ] Using engine version i2 Fri 12/02/2011 07:01:05 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 07:01:09 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F FF 01 00 01 19 73 47 FF 1F 01 00 Fri 12/02/2011 07:01:09 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 12/02/2011 07:01:09 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:18 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:27 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:31 PM : [14 75 62 1 ] ** Not added ** Remove device links failed" Fri 12/02/2011 07:01:31 PM : ---- All Remaining Device Added ---- Fri 12/02/2011 07:01:31 PM : [All ] Writing 0 bytes to devices
LeeG Posted December 3, 2011 Posted December 3, 2011 The Show PLM Links Table is not affected by the Access Points or other devices. There is no communication with devices other than the PLM itself over the Serial interface when reading PLM Link Records. It should never be empty unless a Factory reset has been done without a follow up Restore Modem (PLM) request. The Event Log shows the first record of the RemoteLinc2 (14.75.62) link database was successfully read with an Extended ALDB command. The record returned is an End Of List record so the RemoteLinc2 has no active link records. Fri 12/02/2011 07:01:05 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 07:01:09 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F FF 01 00 01 19 73 47 FF 1F 01 00 Fri 12/02/2011 07:01:09 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 The ISY tries to write a link record using the same Extended ALDB command and it fails to get any response from the RemoteLinc2. Note the time stamps on each of the next three attempts. The nine second gap is the timeout waiting for the RemoteLinc2 to send a response. After 3 no responses the activity is terminated. Fri 12/02/2011 07:01:09 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:18 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:27 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Not sure what this actually means at first glance. The PLM was able to communicate with the RemoteLinc2 for reading but got no response when attempting to write to the RemoteLinc2. I will trace my device add of the RemoteLinc2 to see if there is any difference. The posted messages look good but it is worth checking against a working example. This might mean a Factory Reset of the RemoteLinc2 is needed or maybe a Factory Reset of the PLM. The RemoteLinc2 is the most logical candidate at this point. I’ll post back after comparing to a successful device add of a RemoteLinc2.
oatflake Posted December 3, 2011 Posted December 3, 2011 The Show PLM Links Table is not affected by the Access Points or other devices. There is no communication with devices other than the PLM itself over the Serial interface when reading PLM Link Records. It should never be empty unless a Factory reset has been done without a follow up Restore Modem (PLM) request. Yes, this puzzled me as well. I also noticed during this time that all of the "status" parts in the java admin tool were blank (no on or off status for any devices) yet I could see the correct status using the /rest interface and the Devices web page. After maybe 10-15 minutes java tool locked up my browser, I had to restart Firefox. After a few more more minutes the status returned to the java console, and the PLM Links Table was populated with all of my devices again. It might have just been the java tool acting up? Fri 12/02/2011 07:01:09 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:18 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 07:01:27 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Not sure what this actually means at first glance. The PLM was able to communicate with the RemoteLinc2 for reading but got no response when attempting to write to the RemoteLinc2. I will trace my device add of the RemoteLinc2 to see if there is any difference. The posted messages look good but it is worth checking against a working example. This is my log of what it looks like when I succesfully add it using my Access Point if that helps. By the way, I can add it using my Access Point right away without having to do a factory reset of the motion sensor. Fri 12/02/2011 08:14:34 PM : ---- Initializing the linked devices ---- Fri 12/02/2011 08:14:34 PM : ---- All Linked Devices are now initialized ---- Fri 12/02/2011 08:14:34 PM : ---- Add remaining devices ---- Fri 12/02/2011 08:14:34 PM : [ 14 75 62 1] Writing High Water Mark at Link 0 Fri 12/02/2011 08:14:34 PM : [14 75 62 1 ] Querying engine version Fri 12/02/2011 08:14:34 PM : [iNST-ACK ] 02 62 14.75.62 0F 0D 00 06 (00) Fri 12/02/2011 08:14:34 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 0D 01 (01) Fri 12/02/2011 08:14:34 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:34 PM : [14 75 62 1 ] Retrieved engine version is i2 Fri 12/02/2011 08:14:34 PM : [14 75 62 1 ] Calibrating engine version ensuring support for i2 Fri 12/02/2011 08:14:34 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:35 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:35 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:35 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F FF 01 E2 01 19 73 47 FF 1F 01 00 Fri 12/02/2011 08:14:35 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 12/02/2011 08:14:35 PM : [14 75 62 1 ] Using engine version i2 Fri 12/02/2011 08:14:35 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:36 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:36 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:36 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F FF 01 E2 01 19 73 47 FF 1F 01 00 Fri 12/02/2011 08:14:36 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 12/02/2011 08:14:36 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 00 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 08:14:37 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:37 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:37 PM : [ 14 75 62 1] Adding device to ISY t=10.01.0000 Fri 12/02/2011 08:14:37 PM : [LivRmMotion-Sensor] Start : Adding device to ISY Fri 12/02/2011 08:14:37 PM : [LivRmMotion-Sensor] Finish : Adding device to ISY was Successful Fri 12/02/2011 08:14:37 PM : [14 75 62 1 ] Link 0 : 0FF8 [E201197347FF1F01] Saving [E201197347FF1F01] Fri 12/02/2011 08:14:37 PM : [LivRmMotion-Dusk/Dawn] Start : Adding device to ISY Fri 12/02/2011 08:14:37 PM : [LivRmMotion-Dusk/Dawn] Finish : Adding device to ISY was Successful Fri 12/02/2011 08:14:37 PM : [14 75 62 2 ] Link 1 : 0FF0 [E202197347FF1F02] Saving [E202197347FF1F02] Fri 12/02/2011 08:14:37 PM : [LivRmMotion-Low Bat] Start : Adding device to ISY Fri 12/02/2011 08:14:37 PM : [LivRmMotion-Low Bat] Finish : Adding device to ISY was Successful Fri 12/02/2011 08:14:37 PM : [14 75 62 3 ] Link 2 : 0FE8 [E203197347FF1F03] Saving [E203197347FF1F03] Fri 12/02/2011 08:14:37 PM : [ 14 75 62 3] ST 0 Fri 12/02/2011 08:14:38 PM : [14 75 62 1 ] Device added to ISY Fri 12/02/2011 08:14:38 PM : ---- All Remaining Device Added ---- Fri 12/02/2011 08:14:38 PM : [All ] Writing 24 bytes to devices Fri 12/02/2011 08:14:38 PM : [14 75 62 1 ] Using engine version i2 for 'LivRmMotion-Sensor' Fri 12/02/2011 08:14:38 PM : [14 75 62 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............] Fri 12/02/2011 08:14:38 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:39 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:39 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:39 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F E7 01 00 01 14 76 42 FF 1F 01 00 Fri 12/02/2011 08:14:39 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 12/02/2011 08:14:39 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F E7 08 00 01 14 76 42 FF 1F 01 00 06 (00) Fri 12/02/2011 08:14:40 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:40 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:40 PM : [14 75 62 1 ] Link 4 : 0FD8 : Writing High Water Byte Fri 12/02/2011 08:14:40 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:40 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:40 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:41 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 00 Fri 12/02/2011 08:14:41 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 12/02/2011 08:14:41 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:42 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:42 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:42 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 00 Fri 12/02/2011 08:14:42 PM : [Extended-Direct][14.75.62-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Fri 12/02/2011 08:14:42 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:43 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:43 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:43 PM : [14 75 62 1 ] Using engine version i2 for 'LivRmMotion-Sensor' Fri 12/02/2011 08:14:43 PM : [14 75 62 1 ] Link 0 : 0FF8 [E201197347FF1F01] Writing [E201197347FF1F01] Fri 12/02/2011 08:14:43 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F FF 08 E2 01 19 73 47 FF 1F 01 00 06 (00) Fri 12/02/2011 08:14:43 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:43 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:43 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 14 75 62 10 01 00 15 Fri 12/02/2011 08:14:43 PM : [PLM ] Group 1 : Writing Responder Link matching [14 75 62 1 ] Link 0 : 0FF8 [E201197347FF1F01] Fri 12/02/2011 08:14:43 PM : [14 75 62 1 ] Using engine version i2 for 'LivRmMotion-Sensor' Fri 12/02/2011 08:14:43 PM : [14 75 62 1 ] Link 1 : 0FF0 [E202197347FF1F02] Writing [E202197347FF1F02] Fri 12/02/2011 08:14:44 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F F7 08 E2 02 19 73 47 FF 1F 02 00 06 (00) Fri 12/02/2011 08:14:44 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:44 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:44 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 14 75 62 10 01 00 15 Fri 12/02/2011 08:14:44 PM : [PLM ] Group 2 : Writing Responder Link matching [14 75 62 1 ] Link 1 : 0FF0 [E202197347FF1F02] Fri 12/02/2011 08:14:44 PM : [14 75 62 1 ] Using engine version i2 for 'LivRmMotion-Sensor' Fri 12/02/2011 08:14:44 PM : [14 75 62 1 ] Link 2 : 0FE8 [E203197347FF1F03] Writing [E203197347FF1F03] Fri 12/02/2011 08:14:45 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 02 0F EF 08 E2 03 19 73 47 FF 1F 03 00 06 (00) Fri 12/02/2011 08:14:45 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:45 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:45 PM : [MNG-LNK-RSP ] 02 6F 41 A2 03 14 75 62 10 01 00 15 Fri 12/02/2011 08:14:45 PM : [PLM ] Group 3 : Writing Responder Link matching [14 75 62 1 ] Link 2 : 0FE8 [E203197347FF1F03]
LeeG Posted December 3, 2011 Posted December 3, 2011 Sorry about calling it RemoteLinc2. Looking at too many posts tonight. There is an Insteon message that is not being processed by the PLM when it is handling the RF communication. The first two trace entries are from the first trace using the PLM for RF. The 02 62 outbound message should have been followed by an 02 50 inbound Standard message which is missing. It is there when using your Access Point and it is there when I am using my PLM for RF communication. From your trace using PLM RF – 02 50 Standard message missing Fri 12/02/2011 07:01:05 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 07:01:09 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F FF 01 00 01 19 73 47 FF 1F 01 00 These are from my Motion Sensor add. There is an 02 62 outbound, the 02 50 inbound Standard message, followed by the 02 51 inbound Extended message. Fri 12/02/2011 11:46:51 PM : [iNST-ACK ] 02 62 14.69.A7 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 11:46:52 PM : [iNST-SRX ] 02 50 14.69.A7 19.70.15 2B 2F 00 (00) Fri 12/02/2011 11:46:52 PM : [standard-Direct Ack][14.69.A7-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Fri 12/02/2011 11:46:52 PM : [iNST-ERX ] 02 51 14 69 A7 19 70 15 11 2F 00 00 01 0F FF 01 E2 01 19 70 15 FF 1F 01 00 These are from your last post using Access Points. The 02 50 Standard message is present as it should be. Fri 12/02/2011 08:14:34 PM : [iNST-ACK ] 02 62 14.75.62 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Fri 12/02/2011 08:14:35 PM : [iNST-SRX ] 02 50 14.75.62 19.73.47 27 2F 00 (00) Fri 12/02/2011 08:14:35 PM : [standard-Direct Ack][14.75.62-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 12/02/2011 08:14:35 PM : [iNST-ERX ] 02 51 14 75 62 19 73 47 11 2F 00 00 01 0F FF 01 E2 01 19 73 47 FF 1F 01 00 It looks like the PLM RF is not handling the 02 50 Standard message that comes first, but does handle the following 02 51 Extended Response message. It looks like it hangs the subsequent attempt to write to the Motion Sensor. Since my v98 is working the only thing I can suggest is to Factory Reset the PLM ONLY. Do a Restore Modem (PLM) to get the link database back and try adding the Motion Sensor again using the PLM for RF.
Michel Kohanim Posted December 4, 2011 Posted December 4, 2011 Lee, As always, you are amazing! I never noticed the missing 02 51 and I am now convinced that this is the same issue as I have seen with others who use RF devices in conjunction with the new dual band PLM. Thanks so very much! With kind regards, Michel
oatflake Posted December 4, 2011 Posted December 4, 2011 Since my v98 is working the only thing I can suggest is to Factory Reset the PLM ONLY. Do a Restore Modem (PLM) to get the link database back and try adding the Motion Sensor again using the PLM for RF. Unfortunately this did not resolve it for me; it still behaves the same way. My new PLM should arrive on Monday; I'll test it out with that one then.
oatflake Posted December 6, 2011 Posted December 6, 2011 My new PLM should arrive on Monday; I'll test it out with that one then. Smarthome sent me a new PLM and that one works correctly! I did some range testing and it appears the PLM has a relatively short "programming" range. I'd say you need to place the device within about 2-4 feet for it to work reliably. Anything beyond about 8 feet away and it has trouble seeing the device consistently. However, for just receiving on/off signals it appears you can go about 20-30 feet away without much trouble. Thanks again for your help, LeeG and Michel especially for helping me diagnose this!
TJF1960 Posted December 6, 2011 Posted December 6, 2011 I did some range testing and it appears the PLM has a relatively short "programming" range. I'd say you need to place the device within about 2-4 feet for it to work reliably. Anything beyond about 8 feet away and it has trouble seeing the device consistently. However, for just receiving on/off signals it appears you can go about 20-30 feet away without much trouble. Doesn't it seem that the rf range should be as good as a AP? Tim
oatflake Posted December 6, 2011 Posted December 6, 2011 I did some range testing and it appears the PLM has a relatively short "programming" range. I'd say you need to place the device within about 2-4 feet for it to work reliably. Anything beyond about 8 feet away and it has trouble seeing the device consistently. However, for just receiving on/off signals it appears you can go about 20-30 feet away without much trouble. Doesn't it seem that the rf range should be as good as a AP? Tim Possibly - it's good enough for me, since I actually bought an extra AP, and where I have my ISY it's actually really close to my motion sensor so it hasn't been a big deal. I imagine if I were to install this in a location where I could use one of the APs and the PLM to bridge phases this would matter to me more. I suspect it's not ever going to be as good as an AP because the PLM has a lot more functions in that little box than the AP which are likely to always cause radio interference.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.