brennanj Posted May 5, 2015 Posted May 5, 2015 Imeter worked fine several years ago. After a few years of it being out of service I reinstalled 2423A1 and it will not link error 10. I also get unsupported device in the start linking drop down. Two address come up on the link screen, one different than what is printed on the imeter. I have found the imeter in the New insteon Device window under linking. If it is still supported (isy994i v4.2.30) what are the steps to get it linked.
LeeG Posted May 5, 2015 Posted May 5, 2015 I used New INSTEON Device. Entered Insteon Address, Name of choice, and Auto Discover.
Brian H Posted May 5, 2015 Posted May 5, 2015 (edited) I used the instructions LeeG gave. IMeter Solo Hardware V1.1 1044. Firmware reported by ISY v.87 My 2423A1 IMeter Solo was added to my firmware v.4.3.1 ISY994i but I am not sure it was added correctly. Both the 2423A1 and PLM link information showed one entry. 0: 0FEF8 : 00 00 00 00 00 00 00 00 Also showed it was a responder to no devices. Though when I did a Query on it. It shows the 100 watt light bulb I had on it and the accumulated current. The reset command did zero the accumulated current information. Edited May 5, 2015 by Brian H
LeeG Posted May 5, 2015 Posted May 5, 2015 The Energy Display 2448A2 creates a Responder link in the iMeter Solo. The ISY does not support the 2448A2 so the link between iMeter Solo and Energy Display has to be established manually.
cmccartney Posted June 8, 2015 Posted June 8, 2015 Can the ISY support more than three iMeters? I know the Energy Display is limited to three, but what would happen if I added a fourth to the ISY?
LeeG Posted June 8, 2015 Posted June 8, 2015 (edited) The Energy Display is not supported by the ISY so there is no ISY limit regarding those. The iMeter Solo has no dependencies on other devices so 1, 2, 3, 4, 5,... etc iMeter Solo devices should work okay. EDIT: I have 1 iMeter Solo installed under 3.3.1. It has no dependencies on other ISY known devices and works well. Edited June 8, 2015 by LeeG
MrWorf Posted January 7, 2016 Posted January 7, 2016 Just tried adding mine and no matter what I do it doesn't work. Automatic linking never sees it. Adding it manually as described by LeeG gives me "Cannot determine Insteon engine" error. I'm running ISY994 with v4.3.26 Any tips or clues?
LeeG Posted January 7, 2016 Posted January 7, 2016 Sounds like a comm issue but need more detail. Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Attempt to add device using New INSTEON Device. Enter Insteon address, Name of choice, and Auto Discover. Post the event trace. Also check Help | About to be sure UI and Firmware both indicate 4.3.26.
MrWorf Posted January 8, 2016 Posted January 8, 2016 This is weird, today when I tried with the log open, it worked ?!?! Odd, thanks though!
Teken Posted January 8, 2016 Posted January 8, 2016 And it stopped working again Can you elaborate as to what isn't working?!?
MrWorf Posted January 8, 2016 Posted January 8, 2016 So I followed LeeG's advice to grab a log, when I tried that, for some reason the pairing succeeded and it started showing some data. But I think it was a dud, because it didn't update and when I did a query it failed. The ISY links table show all zeros if it means anything.
jerlands Posted January 8, 2016 Posted January 8, 2016 As per LeeG's reply #8 do the event viewer trace and post the results. Jon...
MrWorf Posted January 8, 2016 Posted January 8, 2016 Removed it and tried again, this time I got the old error: Thu 01/07/2016 08:00:23 PM : CLI-HAMW: Connecting to api.aerisapi.com Thu 01/07/2016 08:00:23 PM : CLI-HAMW: Successfully Processed HAMW Response Thu 01/07/2016 08:00:23 PM : CLI-HAMW: Connecting to api.aerisapi.com Thu 01/07/2016 08:00:24 PM : CLI-HAMW: Successfully Processed HAMW Response Thu 01/07/2016 08:00:24 PM : CLI-HAMW: Connecting to api.aerisapi.com Thu 01/07/2016 08:00:25 PM : CLI-HAMW: Successfully Processed HAMW Response Thu 01/07/2016 08:00:25 PM : [MOD 2 2 1 15] 50000.000000 Weather - Gust Speed = 5 mph Thu 01/07/2016 08:00:25 PM : [MOD 5 5 1 16] 10149.000000 SmartMeter - Inst Demand = 1.0149kW-kWh Thu 01/07/2016 08:00:42 PM : [19 89 DF ] Added to list of devices to link to ISY Thu 01/07/2016 08:00:42 PM : [INST-TX-I1 ] 02 62 19 89 DF 0F 0D 00 Thu 01/07/2016 08:00:42 PM : [INST-ACK ] 02 62 19.89.DF 0F 0D 00 06 (00) Thu 01/07/2016 08:00:43 PM : A 2016/01/07 7:59:45 PM Log M instantaneousDemand 972 Thu 01/07/2016 08:00:43 PM : A 2016/01/07 8:00:05 PM Log M instantaneousDemand 972 Thu 01/07/2016 08:00:43 PM : A 2016/01/07 8:00:27 PM Log M instantaneousDemand 1015 Thu 01/07/2016 08:00:43 PM : A 2016/01/07 8:00:44 PM Log M instantaneousDemand 1002 Thu 01/07/2016 08:00:43 PM : [MOD 5 5 1 16] 10020.000000 SmartMeter - Inst Demand = 1.0020kW-kWh Thu 01/07/2016 08:00:51 PM : [INST-TX-I1 ] 02 62 19 89 DF 0F 0D 00 Thu 01/07/2016 08:00:51 PM : [INST-ACK ] 02 62 19.89.DF 0F 0D 00 06 (00) Thu 01/07/2016 08:00:53 PM : [INST-SRX ] 02 50 30.92.CD 23.97.FD 0B 6F 31 (31) Thu 01/07/2016 08:00:53 PM : [Std-Direct ] 30.92.CD-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:00:53 PM : [D2D EVENT ] Event [30 92 CD 1] [CLIHUM] [49] uom=0 prec=-1 Thu 01/07/2016 08:00:53 PM : [ 30 92 CD 1] CLIHUM 49 Thu 01/07/2016 08:00:55 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 CB 11 01 LTONRR (01) Thu 01/07/2016 08:00:55 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:00:55 PM : [D2D EVENT ] Event [32 88 79 1] [DON] [1] uom=0 prec=-1 Thu 01/07/2016 08:00:55 PM : [ 32 88 79 1] DON 1 Thu 01/07/2016 08:00:55 PM : [D2D-CMP 0051] CTL [32 88 79 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 01/07/2016 08:00:55 PM : [D2D EVENT ] Event [32 88 79 1] [ST] [255] uom=0 prec=-1 Thu 01/07/2016 08:00:55 PM : [ 32 88 79 1] ST 255 Thu 01/07/2016 08:00:56 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 CB 11 01 LTONRR (01) Thu 01/07/2016 08:00:56 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:00:56 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:00:56 PM : [INST-SRX ] 02 50 32.88.79 23.97.FD 41 11 01 LTONRR (01) Thu 01/07/2016 08:00:56 PM : [Std-Cleanup ] 32.88.79-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Thu 01/07/2016 08:00:56 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:00:56 PM : [INST-SRX ] 02 50 32.88.79 11.01.01 CB 06 00 (00) Thu 01/07/2016 08:00:56 PM : [Std-Group ] 32.88.79-->11.01.01, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:00:56 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:00:56 PM : [INST-SRX ] 02 50 32.88.79 11.01.01 CB 06 00 (00) Thu 01/07/2016 08:00:56 PM : [Std-Group ] 32.88.79-->11.01.01, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:00:56 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:00:57 PM : [INST-TX-I1 ] 02 62 00 00 2A CF 11 00 Thu 01/07/2016 08:00:57 PM : [INST-ACK ] 02 62 00.00.2A CF 11 00 06 LTONRR (00) Thu 01/07/2016 08:00:57 PM : [Std MH ] Unexpected Ack imCmd=62 cmd1=LTONRR 0x11 Thu 01/07/2016 08:00:59 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 CB 13 01 LTOFFRR(01) Thu 01/07/2016 08:00:59 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:00:59 PM : [D2D EVENT ] Event [32 88 79 1] [DOF] [1] uom=0 prec=-1 Thu 01/07/2016 08:00:59 PM : [ 32 88 79 1] DOF 1 Thu 01/07/2016 08:00:59 PM : [D2D EVENT ] Event [32 88 79 1] [ST] [0] uom=0 prec=-1 Thu 01/07/2016 08:00:59 PM : [ 32 88 79 1] ST 0 Thu 01/07/2016 08:00:59 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 C7 13 01 LTOFFRR(01) Thu 01/07/2016 08:00:59 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=1 Thu 01/07/2016 08:00:59 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:00:59 PM : [INST-SRX ] 02 50 32.88.79 23.97.FD 41 13 01 LTOFFRR(01) Thu 01/07/2016 08:00:59 PM : [Std-Cleanup ] 32.88.79-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Thu 01/07/2016 08:00:59 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:01:00 PM : [INST-SRX ] 02 50 32.88.79 13.01.01 C7 06 00 (00) Thu 01/07/2016 08:01:00 PM : [Std-Group ] 32.88.79-->13.01.01, Max Hops=3, Hops Left=1 Thu 01/07/2016 08:01:00 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:00 PM : [INST-SRX ] 02 50 32.88.79 13.01.01 C7 06 00 (00) Thu 01/07/2016 08:01:00 PM : [Std-Group ] 32.88.79-->13.01.01, Max Hops=3, Hops Left=1 Thu 01/07/2016 08:01:00 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:01 PM : [INST-SRX ] 02 50 27.B3.0D 00.00.01 CB 11 01 LTONRR (01) Thu 01/07/2016 08:01:01 PM : [Std-Group ] 27.B3.0D-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:01 PM : [D2D EVENT ] Event [27 B3 D 1] [DON] [1] uom=0 prec=-1 Thu 01/07/2016 08:01:01 PM : [ 27 B3 D 1] DON 1 Thu 01/07/2016 08:01:01 PM : [D2D-CMP 0051] CTL [27 B3 D 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 01/07/2016 08:01:01 PM : [ Time] 20:01:01 0(0) Thu 01/07/2016 08:01:01 PM : [INST-SRX ] 02 50 27.B3.0D 00.00.01 CB 11 01 LTONRR (01) Thu 01/07/2016 08:01:01 PM : [Std-Group ] 27.B3.0D-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:01 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:01:01 PM : [INST-SRX ] 02 50 27.B3.0D 23.97.FD 41 11 01 LTONRR (01) Thu 01/07/2016 08:01:01 PM : [Std-Cleanup ] 27.B3.0D-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Thu 01/07/2016 08:01:01 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:01:01 PM : [INST-SRX ] 02 50 27.B3.0D 11.01.01 CB 06 00 (00) Thu 01/07/2016 08:01:01 PM : [Std-Group ] 27.B3.0D-->11.01.01, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:01 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:01 PM : [INST-SRX ] 02 50 27.B3.0D 11.01.01 CB 06 00 (00) Thu 01/07/2016 08:01:01 PM : [Std-Group ] 27.B3.0D-->11.01.01, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:01 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:02 PM : [INST-TX-I1 ] 02 62 00 00 2A CF 11 00 Thu 01/07/2016 08:01:02 PM : [INST-ACK ] 02 62 00.00.2A CF 11 00 06 LTONRR (00) Thu 01/07/2016 08:01:02 PM : [Std MH ] Unexpected Ack imCmd=62 cmd1=LTONRR 0x11 Thu 01/07/2016 08:01:02 PM : [INST-TX-I1 ] 02 62 19 89 DF 0F 0D 00 Thu 01/07/2016 08:01:02 PM : [INST-ACK ] 02 62 19.89.DF 0F 0D 00 06 (00) Thu 01/07/2016 08:01:03 PM : A 2016/01/07 8:01:03 PM Log M instantaneousDemand 1003 Thu 01/07/2016 08:01:03 PM : A 2016/01/07 8:01:04 PM Log M meterStatus -- Thu 01/07/2016 08:01:03 PM : A 2016/01/07 8:01:04 PM Log M currSumDelivered 67153471 Thu 01/07/2016 08:01:03 PM : A 2016/01/07 8:01:04 PM Log M deltaEnergyDelivered 38 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:04 PM Log M numPeriodsDelivered 20 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:04 PM Log M lastIntervalDataValue 11758 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:04 PM Log M lastIntervalDataEndTime 2016/01/07 20:00:00 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:04 PM Log M currDayDelivered 16197 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:05 PM Log M 136 Running 2016/01/07 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:05 PM Log M 137 Scheduled 2016/01/08 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:05 PM Log M 137 Scheduled 2016/01/08 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:05 PM Log M 136 Running 2016/01/07 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:04 PM : A 2016/01/07 8:01:05 PM Log M 136 Running 2016/01/07 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:04 PM : [MOD 5 5 1 9] 671534710.000000 SmartMeter - Curr Summ Del = 67153.4710kW-kWh Thu 01/07/2016 08:01:04 PM : [MOD 5 5 1 16] 10029.000000 SmartMeter - Inst Demand = 1.0029kW-kWh Thu 01/07/2016 08:01:04 PM : [MOD 5 5 1 20] 380.000000 SmartMeter - Curr Delta Del = 380 Thu 01/07/2016 08:01:04 PM : [SEP-DEV] Price is not enabled Thu 01/07/2016 08:01:04 PM : [MOD 8 8 1 4] 3.000000 SEP Price - Price Status = Running Thu 01/07/2016 08:01:05 PM : A 2016/01/07 8:01:06 PM Log M 137 Scheduled 2016/01/08 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:06 PM : A 2016/01/07 8:01:06 PM Log M 137 Scheduled 2016/01/08 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:06 PM : A 2016/01/07 8:01:06 PM Log M 136 Running 2016/01/07 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:06 PM : A 2016/01/07 8:01:06 PM Log M 136 Running 2016/01/07 12:00:00 AM 86400 USD kWh 5 19824 62 Tier2 Thu 01/07/2016 08:01:06 PM : [SEP-DEV] Price is not enabled Thu 01/07/2016 08:01:06 PM : [19 89 DF 0 ] Failed to add device, reason 3 Thu 01/07/2016 08:01:06 PM : [All ] Writing 0 bytes to devices Thu 01/07/2016 08:01:22 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 C7 11 01 LTONRR (01) Thu 01/07/2016 08:01:22 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=1 Thu 01/07/2016 08:01:22 PM : [D2D EVENT ] Event [32 88 79 1] [DON] [1] uom=0 prec=-1 Thu 01/07/2016 08:01:22 PM : [ 32 88 79 1] DON 1 Thu 01/07/2016 08:01:22 PM : [D2D-CMP 0051] CTL [32 88 79 1] DON op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 01/07/2016 08:01:22 PM : [D2D EVENT ] Event [32 88 79 1] [ST] [255] uom=0 prec=-1 Thu 01/07/2016 08:01:22 PM : [ 32 88 79 1] ST 255 Thu 01/07/2016 08:01:23 PM : [INST-TX-I1 ] 02 62 00 00 2A CF 11 00 Thu 01/07/2016 08:01:23 PM : [MOD 5 5 1 16] 11000.000000 SmartMeter - Inst Demand = 1.1000kW-kWh Thu 01/07/2016 08:01:23 PM : [INST-ACK ] 02 62 00.00.2A CF 11 00 06 LTONRR (00) Thu 01/07/2016 08:01:23 PM : [D2D EVENT ] Event [2B FE 64 5] [ST] [255] uom=0 prec=-1 Thu 01/07/2016 08:01:23 PM : [ 2B FE 64 5] ST 255 Thu 01/07/2016 08:01:23 PM : [D2D EVENT ] Event [2C 85 AF 1] [ST] [255] uom=0 prec=-1 Thu 01/07/2016 08:01:23 PM : [ 2C 85 AF 1] ST 255 Thu 01/07/2016 08:01:23 PM : [INST-SRX ] 02 50 32.88.79 23.97.FD 46 11 01 LTONRR (01) Thu 01/07/2016 08:01:23 PM : [Std-Cleanup ] 32.88.79-->ISY/PLM Group=1, Max Hops=2, Hops Left=1 Thu 01/07/2016 08:01:23 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:01:24 PM : [INST-SRX ] 02 50 32.88.79 11.01.01 C7 06 00 (00) Thu 01/07/2016 08:01:24 PM : [Std-Group ] 32.88.79-->11.01.01, Max Hops=3, Hops Left=1 Thu 01/07/2016 08:01:24 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:24 PM : [INST-SRX ] 02 50 32.88.79 11.01.01 CB 06 00 (00) Thu 01/07/2016 08:01:24 PM : [Std-Group ] 32.88.79-->11.01.01, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:24 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:27 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 CB 13 01 LTOFFRR(01) Thu 01/07/2016 08:01:27 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:27 PM : [D2D EVENT ] Event [32 88 79 1] [DOF] [1] uom=0 prec=-1 Thu 01/07/2016 08:01:27 PM : [ 32 88 79 1] DOF 1 Thu 01/07/2016 08:01:27 PM : [D2D EVENT ] Event [32 88 79 1] [ST] [0] uom=0 prec=-1 Thu 01/07/2016 08:01:27 PM : [ 32 88 79 1] ST 0 Thu 01/07/2016 08:01:28 PM : [INST-SRX ] 02 50 32.88.79 00.00.01 CB 13 01 LTOFFRR(01) Thu 01/07/2016 08:01:28 PM : [Std-Group ] 32.88.79-->Group=1, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:28 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:01:28 PM : [INST-SRX ] 02 50 32.88.79 23.97.FD 41 13 01 LTOFFRR(01) Thu 01/07/2016 08:01:28 PM : [Std-Cleanup ] 32.88.79-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Thu 01/07/2016 08:01:28 PM : [INST-DUP ] Previous message ignored. Thu 01/07/2016 08:01:28 PM : [INST-SRX ] 02 50 32.88.79 13.01.01 C7 06 00 (00) Thu 01/07/2016 08:01:28 PM : [Std-Group ] 32.88.79-->13.01.01, Max Hops=3, Hops Left=1 Thu 01/07/2016 08:01:28 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:29 PM : [INST-SRX ] 02 50 32.88.79 13.01.01 CB 06 00 (00) Thu 01/07/2016 08:01:29 PM : [Std-Group ] 32.88.79-->13.01.01, Max Hops=3, Hops Left=2 Thu 01/07/2016 08:01:29 PM : [INST-INFO ] Previous message ignored. Thu 01/07/2016 08:01:43 PM : [MOD 5 5 1 16] 11310.000000 SmartMeter - Inst Demand = 1.1310kW-kWh The device is 19.89.DF
Teken Posted January 8, 2016 Posted January 8, 2016 I am not sure whether or not you're on 4.4.2 Beta firmware but it should be noted this release resolves the iMeter Solo's reset button not functioning. I would suggest you upgrade to this level of firmware and report back success / failure. You should probably hard reset the device prior to adding it back to the 994 Series Controller. Ensure you clear the Java Cache and select all option box's and down load the correct Admin Console for 4.4.2. Verify via the Help -> About that both UI / Firmware indicate the same.
jerlands Posted January 8, 2016 Posted January 8, 2016 [19 89 DF 0 ] Failed to add device, reason 3 <<-- reason 3 = lack of communication... You could try plugging it into the same outlet as the PLM (with extension cord) or somewhere near on the same circuit and see if that helps. Jon...
LeeG Posted January 8, 2016 Posted January 8, 2016 (edited) MrWorf The iMeter is not responding to three attempts to process the command to access Insteon Engine information. Here is what should happen .... Fri 01/08/2016 02:59:26 AM : [All ] Writing 1 bytes to devices Fri 01/08/2016 02:59:26 AM : [iNST-TX-I1 ] 02 62 18 F5 40 0F 0D 00 Fri 01/08/2016 02:59:26 AM : [iNST-ACK ] 02 62 18.F5.40 0F 0D 00 06 (00) Fri 01/08/2016 02:59:26 AM : [iNST-SRX ] 02 50 18.F5.40 22.80.0B 2B 0D 01 (01) Fri 01/08/2016 02:59:26 AM : [std-Direct Ack] 18.F5.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 01/08/2016 02:59:26 AM : [18 F5 40 0 ] Calibrating engine version Fri 01/08/2016 02:59:26 AM : [18 F5 40 0 ] May not fully support i2, reverting to i1 Fri 01/08/2016 02:59:27 AM : [iNST-ERX ] 02 51 18 F5 40 22 80 0B 1B 82 00 00 04 01 FF 00 91 00 01 00 00 00 00 F0 79 Fri 01/08/2016 02:59:27 AM : [Ext-Direct ] 18.F5.40-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 The event trace shows no iMeter response to the three attempts. Note that I have no link records in my iMeter Solo. There is much activity going on while trying to add iMeter Solo. Not sure if that is having a negative impact or simply a comm issue with current location. jerlands suggestion to move to the PLM plug point is good. Also if you can suspend some of the current activity that might help. I am running 4.4.2. 4.3.26 is the latest Official release. Edited January 8, 2016 by LeeG
MrWorf Posted January 16, 2016 Posted January 16, 2016 I found out what it was. The washer (which was connected to it) would interfere with the communications. Once I placed a filter between the iMeter and the Washer, I was able to communicate properly. Odd
Brian H Posted January 16, 2016 Posted January 16, 2016 Washer probably has electronic controls. To keep its internal electronic noise from getting onto the power lines. Most likely they put a simple AC rated capacitor across the AC Power. That will kill the internal noise but also absorb Insteon and X10 power line signals. I have seen similar electronic washer, dryer and even refrigerators found as trouble makers reported on the X10 Forums.
MrWorf Posted January 16, 2016 Posted January 16, 2016 Odd that it only affects the one device which is in-between. Oh well, problem solved
Recommended Posts