MrWorf

It's controlling 4x 60w equivalent CREE LED lights. These kind of lights are used throughout our home without any issues, both with SwitchLinc Dimmers and other KeypadLinc Dimmers. The KeypadLinc was able to turn off the load IF I pressed OFF on another device which controlled it (ie, another member in the same scene). But direct control didn't work. After I restored the device and confirmed the links last night, it worked again. This morning, less than 12hrs later, one record in the device link table is corrupt again. ISY has it showing: E2 01 40.52.B4 01 00 01 While the KeypadLinc Dimmer claims: EA 01 40.52.B4 01 00 01 Which, according to http://forum.universal-devices.com/topic/15893-losing-control-of-dimmer/?do=findComment&comment=136807 is OK, but I'm still concerned about the fact that yesterday multiple records were corrupted (and not just the E2 vs EA issue). And the fact that the button on the dimmer was unable to turn it off even though the other members in the same scene was able to. Is there any diagnostics mode for KeypadLincs to find out if it's broken?

Has anyone ever had a KeypadLinc Dimmer (8 buttons) which won't turn off the lights attached to the dimmer? Normally, an insteon device will always control the locally connected light without any way of overriding that behavior, but I have one which will turn on the connected light but not turn it off. The logs show that the KeypadLinc is issuing what seems to be a turn on command even though it's turned on already. However, another insteon device is able to issue a off command which it responds to. Here's the corresponding logs from ISY: Sun 01/22/2017 09:25:16 PM : [INST-SRX ] 02 50 40.FC.B3 00.00.01 CB 11 00 LTONRR (00) Sun 01/22/2017 09:25:16 PM : [Std-Group ] 40.FC.B3-->Group=1, Max Hops=3, Hops Left=2 Sun 01/22/2017 09:25:16 PM : [D2D EVENT ] Event [40 FC B3 1] [DON] [0] uom=0 prec=-1 Sun 01/22/2017 09:25:16 PM : [ 40 FC B3 1] DON 0 Sun 01/22/2017 09:25:16 PM : [INST-SRX ] 02 50 40.FC.B3 40.52.B4 40 11 01 LTONRR (01) Sun 01/22/2017 09:25:16 PM : [Std-Cleanup ] 40.FC.B3-->ISY/PLM Group=1, Max Hops=0, Hops Left=0 Sun 01/22/2017 09:25:16 PM : [INST-DUP ] Previous message ignored. Sun 01/22/2017 09:25:16 PM : [INST-SRX ] 02 50 40.FC.B3 11.04.01 CF 06 00 (00) Sun 01/22/2017 09:25:16 PM : [Std-Group ] 40.FC.B3-->11.04.01, Max Hops=3, Hops Left=3 Sun 01/22/2017 09:25:16 PM : [INST-INFO ] Previous message ignored. 40.FC.B3 is the offending KeypadLinc ... When I compared the links on the device with ISY, there was discrepancies found. Which is odd since I did a complete walkthrough end of last year, doing compare and restore until all devices matched ISY database, so I know this one was correct earlier, and now it's corrupted. Did a new restore today and now it's back to showing identical. But still, the most worrisome thing here is that the 1st button, which controls the connected load, was not allowing me to turn it off, only on. Is this an indication that the entire thing is broken? If anyone wonders, it's controlling 4x 60w equivalent CREE LED lights. These kind of lights are used throughout our home without any issues, both with SwitchLinc Dimmers and other KeypadLincs.

That's not half as fun though

LeeG, The link is on the Switch, it's kinda half-linked, so the switch listens to events from motion, but motion does not care about switch. And the problem is that ISY has a record of it. My plan is to backup, edit the <insteon id>.REC file with a hex editor and replace AA with 22 (deleted) and restore the backup. After that, I should be able to issue a restore device to the switch and presto, motion sensor should no longer trigger my switch. I'll let you know about my result later tonight

If AA is a valid one, then why can't I remove it? It has broken our house setup right now. Going to try my hack tonight and see if it works, because now the lights go on/off at random based on the motion sensor which is annoying, wasteful and generally displeasing Moving this discussion to http://forum.universal-devices.com/topic/20453-what-is-an-aa-record-for-2477s-and-why-cant-i-remove-it

@LeeG: If you happen to have a list of all Record Types, that would be awesome I found two more odd ones (value 62) and it would be great to know if it was expected or not. Also, this script in bash can be used to probe the *.REC files in the ISY backup: #!/bin/bash function getrecord() { BASE=$((180 + $2 * ) hexdump -v -s $BASE -n 8 -e '8/1 "%02x " "\n"' $1 } FILE=$1 HIDE=$2 HIDE=${HIDE:=false} I=0 TYPE="" while [ "$TYPE" != "00" ]; do REC=$(getrecord $FILE $I) TYPE="${REC:0:2}" case "$TYPE" in e2|a2|22|02|00) if ! $HIDE ; then printf "%02d: %s - OK\n" $I "$REC" fi ;; *) if $HIDE ; then printf "%02d: %s - WARNING (%s)\n" $I "$REC" "$FILE" else printf "%02d: %s - WARNING\n" $I "$REC" fi ;; esac I=$(($I+1)) done like so: for F in *.REC ; do ./screen-rec.sh $F true ; done 1st argument is the file to probe, 2nd argument is true to only show odd values or false (or skipped) to show all records.

Yes, I know (product specific) but in this case it's not valid. It causes ISY to hide the link, it makes the switch turn on when there is motion, and I cannot remove it or block it. So while valid, it's not valid for this product (2477S)

I have a similar issue as the person in this thread, my 2477S (Wall switch) has been corrupted with a device link record of type AA and the address of one of my motion sensors. Now, I could go through the remove/readd, but I don't feel that is the proper way, so I've done some digging in the ISY (since that's the source of the corruption) and it seems possible to backup the isy, edit the record manually (replacing AA with A2 which is responder) and then restore. This should correct the incorrect value in the ISY and a subsequent "Restore Device" should then replace the faulty link with a responder link which ISY will allow me to remove. I'll let you know how it works (might be doomed if ISY produces a checksum for its backups) BUT! If anyone from Universal Devices are reading this, we need a way to find errors like this (you should know what's considered valid values) and issue warnings and also allow a manual "erase" of such links. Because editing a backup and the restoring it makes me feed uncomfortable

Odd that it only affects the one device which is in-between. Oh well, problem solved

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

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

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.

And it stopped working again

This is weird, today when I tried with the log open, it worked ?!?! Odd, thanks though!

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?

Each dimming sequence consists of 256 levels. Especially if you use programming and want to hook up the ISY to Alexa and use the dimmer by voice (set dimmer 40% or similar), scenes are simply not enough. And while I agree with the preset concept, why can it only accept on/off and not 0-255 (0 = off, 255 = on), in terms of commands, it would be same amount of data. On top of that, a scene can easily consist of 5 to 15 devices, sending an individual dim command to each will first of all not set the scene to the the correct state (causing linking to not show the correct state) as well having severe delays (since issuing commands too fast would cause collisions on the INSTEON network) and finally it would look like crap But, as I said before, this is a INSTEON protocol issue and not ISY's fault. I guess long term I will have to find an alternate solution to replace lighting controls around the house (and hue is not the solution, I want the nicely integrated switches/dimmers). Hue would be nice otherwise since it's actually capable of all of this plus color control ... Meh, would be too expensive anyway ($50/light ... REALLY?)

I find it very simple. It's percentages ... all of it. So if a scene is defined as Device A at 40% and Device B at 100%, setting the scene to 100% yields just that, 40 & 100 percent. But if you set the scene to 50%, it will be 20 + 50 percent. And then you ask, what if I have a on/off only device in the scene? Well my friend, try setting an on/off device to any value between 1 and 255, you'll find it will turn it on. This is the only reasonable behavior. No one should expect that dimming commands work on non-dimmable devices, but I would expect a scene to be dimmable and that devices do their best to accomodate. But I guess in the end it's all down to INSTEON itself, and after closer investigation it would seem that this is a limitation of INSTEON and not ISY. Such a shame Maybe documentation should be updated to not mention that scenes can be set to a specific level?

I'm trying to use the REST API to set a scene to 50% light, using the following call: http://isy994i/rest/nodes/5189/cmd/DON/128 But it always ends up going 100% instead. If I execute the same call using the device ID instead, it works as expected. But even the ISY SDK says (on page 64) /rest/nodes/<node-id>/cmd/<command_name>/<param1>/<param2>/.../<param5> eg: /rest/nodes/<node-id>/cmd/DOF - turn off a device or a scene Insteon - /rest/nodes/<node-id>/cmd/DON/128 - turn on a scene to 50% UPB - /rest/nodes/<node-id>/cmd/DON/50 - turn on a scene to 50% I'm using ISY version 4.2.30

Sorry for my late reply. Didn't get a notification for some reason. Anyhow, yes, all three dimmers are controller/responders for my bedroom scene. The code is to make sure the others are able to make the loaded dimmer go to 100% or 10% (as the case may be). I have seen issues that the indicator light on the dimmers sometimes show the wrong state (indicating 10% when it's actuall 100%) but the functionality as such has always worked. I don't know how I would make it do the 10/100 setting without programming it. If anyone knows, please enlighten us

I don't know if this has already been solved, but today I installed a bunch of dimmers and my goal was to make the bedroom light somewhat smarter. My setup consists of 3 dimmers all linked together as a scene on the ISY994. This works fine. But now I wanted to spice things up by having the ISY change the dim level from 100% to 10% after 10pm. Easy, just "Adjust Scene" and set the load for the scene... Erhm, right. After digging around and tearing at my hair, I finally solved it by setting the "scene" on-load for the load dimmer to 10% and then every individual dimmer would also be tweaked to 10% for both itself and the load dimmer it was controlling (at least, that's what I had to do, let me know if there is an easier way). But this only half the solution. By setting the dimmer to 10% I get the benefit of having the second "on" tap to go 100%. But this is where it got tricky. This second "on" tap didn't work on any other dimmer than the one controlling the actual load. The other ones just sat there. The solution is to have an additional program (actually, one for each un-loaded dimmer) which monitors for change and then fakes it. Basically it issues a 100% level change to the load dimmer while simultaneously applying 100% locally AND to any other un-loaded dimmer (that's important, don't miss it). Now, any dimmer will go to the initial 10% and a second tap, on any of them will go to 100% and finally the third tap (again, on any) will bring it back down to 10%. Off works as expected. I've attached screenshots from the ISY Admin of the programs. Hope this helps someone in the same situ as me