PurdueGuy

Could it be that the 2 good dual band devices have comm issues? I realize they work all the time, but they might not have any hops left. Capture a trace at level 3, and toggle both the good devices one at a time, and see how many hops are left. If zero hops are left, then they can't relay the message from the sensor.

There are no differences in how other devices react to the button presses of A vs G. You might try resetting/restoring the target device (FanLinc). I suppose it is possibly it has two links for the device. You never linked manually (by hand) did you?

Our post crossed. In this new scheme: BLUE = device as controller Green = ISY as controller Red = device to modify It might help to rename your devices and scenes, to avoid name collisions. The ISY doesn't care, but it makes it hard to explain.

That is not the correct interpretation. Red would be the controller, and blue is the device you want to modify with respect to that controller. For the first choice (the red one) you have two choices for this scene: - Chose the SCENE NAME if you want to modify it when ISY is controller - Chose the CONTROLLER NAME if you want to modify it for that controller According to your pictures above, you have two devices: Master_Bedroom_Fan_Light - this is the light node of the FanLinc Master_Bedroom_Light_Fanlinc - this is a KPL button, associated to the Fanlinc light Are those correct?

Do you have another device to try linking? Any chance you are out of PLM links? Could you post the level 3 event viewer for the time when you press/release the plunger?

According to the programs you showed earlier, you had the main scene selected. In doing so, that is when ISY is controller. Have you tried my suggested program from post #4? Since your scene name and device name are so similar, be very sure you have the right things selected in the drop down boxes.

Please post your program (copy/paste it, screenshot, something.....don't type it out). Per your initial screenshot, they were not being set correctly. ISY and Insteon and fully capable of doing what you want. I do it all the time.

You do not need the "Control....switched on" here. The KPL is already a controller. At 7:30 PM & 9:30 PM, it simply modifies the on level and ramp level. If you add the "Is switch on" the light will turn on immediately to 100% (or whatever it is set to), ISY will reset the on and levels, and then it will go to the new levels. That is not what is desired.

It looks like you are setting the on level and ramp rate for the main scene, when ISY is the controller. The "In scene" drop down is used to select the controller. Choose the scene name for when ISY is controller, choose a specific device when when that device is controller. This allows flexibility. For your situation, first choose the actual controller (in your case "Master_Bedroom_Light_Fanlinc") and then set "Master_Bedroom_Fan_Light" as appropriate. I think it will be something like: If From 7:30:00PM To 9:30:00PM (same day) Then In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 8.5 Sec (Ramp Rate) In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 25% (On Level) Else In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 0.5 Sec (Ramp Rate) In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 100% (On Level) If you also want ISY to have the same way of handling it should you invoke it from a program, do both: If From 7:30:00PM To 9:30:00PM (same day) Then In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 8.5 Sec (Ramp Rate) In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 25% (On Level) In Scene 'Master_Bedroom_Fan_Light' Set 'Master_Bedroom_Fan_Light' 8.5 Sec (Ramp Rate) In Scene 'Master_Bedroom_Fan_Light' Set 'Master_Bedroom_Fan_Light' 25% (On Level) Else In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 0.5 Sec (Ramp Rate) In Scene 'Master_Bedroom_Light_Fanlinc' Set 'Master_Bedroom_Fan_Light' 100% (On Level) In Scene 'Master_Bedroom_Fan_Light' Set 'Master_Bedroom_Fan_Light' 0.5 Sec (Ramp Rate) In Scene 'Master_Bedroom_Fan_Light' Set 'Master_Bedroom_Fan_Light' 100% (On Level)

For interoperability, I think you will get much further with Z-Wave. As you mentioned, with Zigbee, sometimes things just won't work. Now with Z-Wave, you will most likely get at least basic functionality (on/off/dim/brighten), setting parameters, etc. As they get further along in Z-Wave and 5.x releases, you will get more control (multi-channel devices, for one). If you want a smart meter app, you might be better off adding something else. I am waiting in my Neurio to be delivered. https://www.neur.io

For a few devices, programs work fine. I have several scenes which affect nearly every light in the house (home, away, alarm, etc). For things like that, it would take far to long to accomplish with direct commands, and setting up the programs would be annoying too. Right now, I just have 1 scene called "All Lights" and use that where needed. I think I call it from about 5 different programs.

I have a 2B.2F.xx Hidden Door Sensor that linked just fine, once I realized I realized I needed to upgrade to Pro, as I hit the non-Pro device limit.

Use programs to set a variable based on the sensor, and set the init value for the variable too. Then base your programs off the variable instead of the actual status of the sensor.

That's one of the standard ways to link. How were you doing it before? Were you not going into linking mode in the ISY?

Set the Event Viewer at Level 3, try the linking again, and post the trace here.

As mentioned, it isn't the # of programs I had, it is the number of devices/scenes. Standard has a limit of 256. Pro has a limit of 1024. There is a limit of 300 programs for a Standard, and 1000 for Pro. Upgrade purchased and rebooting!

Thanks for all your help! I'm surprised support didn't notice that. They should add a nice up-sell message! I had to delete a couple more things to get all the nodes.

Oh my....why wouldn't this be more obvious in the log?! I guess I hit the limit of a non-pro system. I deleted a test scene, and the device added without issue! *bangs head on desk*

Your trace appears identical (except for PLM and device addresses). In mine, it looks like ISY just gives up. I asked what "reason 1" was, but didn't get an answer. Maybe Michel can chime in.

The only different is the first ALDB record. Since I factory reset mine, it is set to all zeros. Your's still has a link to your PLM. I had factory reset mine between delete and re-add. Mine should be ok...the "in use" bit is 0, and the "high-water mark" is 0, so that means an empty ALDB, as you'd expect. I guess it's bedtime here.

OK, that's what I was leaning towards. I find it odd that I could add it before, delete it, and not re-add it. Got an extra sensor that you can add, delete, and re-add?

I'm running 4.2.10 UI and firmware. As promised, here is my parsing of the trace. Everything looks good, until the sensor responds with an empty first ALDB record. Perhaps ISY doesn't lime the empty record? I'm also curious why the record address is 0x0FFF, and ISY says "Using Database Link Table offset 0x0FF8." I guess that could mean it will start at 0x0FF8 and continue for 8 bytes to 0x0FFF (ISY uses the lower byte to address, and the device uses the upper byte to address). DoorSensor_FailToAdd.txt

It's so strange that it added once. I did switch it to a 2-node config. I wonder if that has something to do with it? I am almost done decoding the messages, but I disagree on what the sensor is reporting. My trace has: Wed 09/10/2014 10:33:09 PM : [iNST-SRX ] 02 50 2B.2F.99 10.11.43 8B 02 11 (11) The items in red mean category 0x10, subcategory 0x11, version 0x43, which is all correct. The message decodes as: Wed 09/10/2014 10:33:09 PM : [INST-SRX ] 02 50 2B.2F.99 10.11.43 8B 02 11 (11) Wed 09/10/2014 10:33:09 PM : [Std-Broadcast] 2B.2F.99-->10.11.43, Max Hops=3, Hops Left=2 02 = Start 50 = INSTEON standard message receive 2B.2F.99 = From (Hidden Door Sensor) 10.11.43 = To (Cat = 0x10, Subcat = 0x11, Version = 0x43) 8B = Message Flags (100 0 10 11 = Broadcast, Standard, 2 hops remaining, 3 hops max)) 02 = Controller Only 11 = Hardware version I'll post the entire decoded trace when I'm done.

I just re-read your first message, and notice that you also had it previously linked to something. I wonder if the door sensor firmware has a bug, and is ignoring these new link requests. I'll see if I can dig up my developer documentation and see what the "INST-ERX" message is.

I have been emailing with Steve about this. I can't get mine added to 4.2.10. I had it added once for testing (not sure which firmware), thought I was giving it away so I deleted it, then got it back. So no amount of trying gets it added. I have factory reset the device multiple times, been close to ISY/PLM (comms seem fine), and rebooted the PLM, and ISY. Here is the event trace. The line that has "INST-ERX" is where something bad happens and it gives up. It does get far enough to see that it is a v.43 Hidden Door Sensor. I have added by going to: Link Management -> Link a sensor -> Hidden Door Sensor Link Management -> New Insteon Device (both selecting from the drop down and letting ISY auto determine the device type). I did a screen recording while adding it: https://www.dropbox.com/s/64vopo76d01fbvw/Isy_FailToAdd_B.mov?dl=0 Wed 09/10/2014 10:33:07 PM : [2B 2F 99 ] Added to list of devices to link to ISY Wed 09/10/2014 10:33:07 PM : [INST-TX-I1 ] 02 62 2B 2F 99 0F 0D 00 Wed 09/10/2014 10:33:07 PM : [INST-ACK ] 02 62 2B.2F.99 0F 0D 00 06 (00) Wed 09/10/2014 10:33:08 PM : [INST-SRX ] 02 50 2B.2F.99 24.1C.5A 2B 0D 02 (02) Wed 09/10/2014 10:33:08 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 09/10/2014 10:33:08 PM : [INST-TX-I1 ] 02 62 2B 2F 99 0F 10 00 Wed 09/10/2014 10:33:08 PM : [INST-ACK ] 02 62 2B.2F.99 0F 10 00 06 ID-REQ (00) Wed 09/10/2014 10:33:09 PM : [INST-SRX ] 02 50 2B.2F.99 24.1C.5A 2B 10 00 ID-REQ (00) Wed 09/10/2014 10:33:09 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 09/10/2014 10:33:09 PM : [INST-SRX ] 02 50 2B.2F.99 10.11.43 8B 02 11 (11) Wed 09/10/2014 10:33:09 PM : [Std-Broadcast] 2B.2F.99-->10.11.43, Max Hops=3, Hops Left=2 Wed 09/10/2014 10:33:09 PM : [2B 2F 99 0 ] Calibrating engine version Wed 09/10/2014 10:33:09 PM : [INST-TX-I2CS] 02 62 2B 2F 99 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 09/10/2014 10:33:09 PM : [INST-ACK ] 02 62 2B.2F.99 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 09/10/2014 10:33:09 PM : [INST-SRX ] 02 50 2B.2F.99 24.1C.5A 2B 2F 00 (00) Wed 09/10/2014 10:33:09 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 09/10/2014 10:33:09 PM : [INST-ERX ] 02 51 2B 2F 99 24 1C 5A 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1 Wed 09/10/2014 10:33:09 PM : [Ext-Direct ] 2B.2F.99-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Wed 09/10/2014 10:33:09 PM : [2B 2F 99 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Wed 09/10/2014 10:33:10 PM : [2B 2F 99 0 ] Failed to add device, reason 1 Wed 09/10/2014 10:33:10 PM : [All ] Writing 0 bytes to devices