Techman Posted July 17, 2015 Posted July 17, 2015 Being that there's no way to query a Range Extender to know if it's working, and some forum members have reported failures, I've replaced mine with on/off modules which can be queried. It's my understanding that the range extenders are basically on/off modules or dual band lampllincs with some of the hardware removed.
LeeG Posted July 17, 2015 Posted July 17, 2015 Unfortunately a Query is communicating with the device over powerline (which may involve RF but no assurance). Suggest running PLM Beacon test (4 taps on PLM Set button) to see the Range Extender LED response (color and blinking pattern) to determine if in range of PLM and on same/opposite 120v leg.
Techman Posted July 17, 2015 Author Posted July 17, 2015 I agree that there's no way to test the RF portion without a tap test, It was my understanding that the failures of the Range Extenders was due to its power supply, possibly bad caps. A query should disclose that failure. Just a thought.
LeeG Posted July 17, 2015 Posted July 17, 2015 Good point. I was looking at them as bridge devices, not whether they were functional.
Brian H Posted July 17, 2015 Posted July 17, 2015 The Version 2, 2443 Access Points had the power supply problems. Same base board with caps as the 2413S PLM's One of mine the LED was almost out and it didn't even try to start the Communications tests. My second one just didn't do the communications tests until I cycled the AC power to it. Unregulated 12 volts {~18-19 volts} measured around 7 volts. I don't remember seeing any of the 2992-222 Range Extenders being reported as having issues but I may have missed it. Yes mine looks like the 2457D2 Dual Band LampLinc and it even has the same FCC ID:SBP2457D2A. As the Dual Band LampLinc.
Techman Posted July 18, 2015 Author Posted July 18, 2015 The Version 2, 2443 Access Points had the power supply problems. Same base board with caps as the 2413S PLM's One of mine the LED was almost out and it didn't even try to start the Communications tests. My second one just didn't do the communications tests until I cycled the AC power to it. 24 volts measured around 7 volts. I don't remember seeing any of the 2992-222 Range Extenders being reported as having issues but I may have missed it. Yes mine looks like the 2457D2 Dual Band LampLinc and it even has the same FCC ID:SBP2457D2A. As the Dual Band LampLinc. I wonder if the Range Extenders have an Insteon address but it's just not published. It would be nice if there were some way to remotely query it.
Brian H Posted July 18, 2015 Posted July 18, 2015 Mine has the six digit Insteon ID on it. I believe it has a different Insteon Catalog and SubCatalog ID. I will try again to add it to my ISY994i but if memory serves me it was an unknown device or just didn't answer to the request to add it.
Brian H Posted July 18, 2015 Posted July 18, 2015 Tried both Auto Discover and Start Linking. Event Viewer Level 3. Auto Discover:Fri 07/17/2015 08:18:28 PM : [23 53 27 ] Added to list of devices to link to ISYFri 07/17/2015 08:18:28 PM : [iNST-TX-I1 ] 02 62 23 53 27 0F 0D 00Fri 07/17/2015 08:18:28 PM : [iNST-ACK ] 02 62 23.53.27 0F 0D 00 06 (00)Fri 07/17/2015 08:18:36 PM : [iNST-TX-I1 ] 02 62 23 53 27 0F 0D 00Fri 07/17/2015 08:18:36 PM : [iNST-ACK ] 02 62 23.53.27 0F 0D 00 06 (00)Fri 07/17/2015 08:18:45 PM : [iNST-TX-I1 ] 02 62 23 53 27 0F 0D 00Fri 07/17/2015 08:18:45 PM : [iNST-ACK ] 02 62 23.53.27 0F 0D 00 06 (00)Fri 07/17/2015 08:18:49 PM : [23 53 27 0 ] Failed to add device, reason 3Fri 07/17/2015 08:18:49 PM : [All ] Writing 0 bytes to devicesStart Linking:Fri 07/17/2015 08:21:09 PM : Start Insteon Device Linking ModeFri 07/17/2015 08:21:09 PM : [LNK-BGN ] 02 64 01 00 06Fri 07/17/2015 08:21:39 PM : [LNK-STAT ] 02 53 M(01) gid=00 23.53.57 001D 42Fri 07/17/2015 08:21:39 PM : [23.53.57 00] Linked device type=00.1D fw=42Fri 07/17/2015 08:21:39 PM : [23 53 57 0 ] Added to list of devices to link to ISYFri 07/17/2015 08:21:39 PM : [LNK-BGN ] 02 64 01 00 06Fri 07/17/2015 08:22:12 PM : Stop Insteon Device Linking Mode, Final processing to followFri 07/17/2015 08:22:12 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)Fri 07/17/2015 08:22:12 PM : [iNST-TX-I1 ] 02 62 23 53 57 0F 0D 00Fri 07/17/2015 08:22:13 PM : [iNST-ACK ] 02 62 23.53.57 0F 0D 00 06 (00)Fri 07/17/2015 08:22:13 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 0D 02 (02)Fri 07/17/2015 08:22:13 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Fri 07/17/2015 08:22:13 PM : [23 53 57 0 ] Calibrating engine versionFri 07/17/2015 08:22:13 PM : [iNST-TX-I2CS] 02 62 23 53 57 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0Fri 07/17/2015 08:22:13 PM : [iNST-ACK ] 02 62 23.53.57 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)Fri 07/17/2015 08:22:14 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 2F 00 (00)Fri 07/17/2015 08:22:14 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3Fri 07/17/2015 08:22:14 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 23 2F 00 (00)Fri 07/17/2015 08:22:14 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=0Fri 07/17/2015 08:22:14 PM : [iNST-ERX ] 02 51 23 53 57 34 E9 19 15 2F 00 01 01 00 FF 00 A2 00 2B 96 A5 FF 1C 00 ADFri 07/17/2015 08:22:14 PM : [Ext-Direct ] 23.53.57-->ISY/PLM Group=0, Max Hops=1, Hops Left=1Fri 07/17/2015 08:22:14 PM : [23 53 57 0 ] Using Database Link Table offset 0x00F8 (reported 0x00F8)Fri 07/17/2015 08:22:14 PM : [23 53 57 0 ] Failed to add device, reason 10Fri 07/17/2015 08:22:14 PM : [All ] Writing 0 bytes to devicesFri 07/17/2015 08:22:14 PM : [All ] Writing 0 bytes to devicesIf I read the event viewer correctly It is a Catalog 00, SubCat 1D with a firmware of 42
LeeG Posted July 18, 2015 Posted July 18, 2015 The Auto Discover variation is using the wrong Insteon unless two Range Extenders were being used. Auto Discover is using 23.53.27, Start Linking is using 23.53.57. 23.53.27 did not respond to the three command attempts. Subcat 1D is not in the list of supported devices on 4.3.10.
Techman Posted July 18, 2015 Author Posted July 18, 2015 Is It possible for UDI to add the range extender as a supported device, if so it could then be queried which would at least show if it's getting power. We could also then add notes to the device to show its location etc.
Michel Kohanim Posted July 19, 2015 Posted July 19, 2015 Hi Techman, By "supported device", ISY needs to know what can be done to that device. Unfortunately we do not have any API documentation for Access Points. With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.