Illusion

Could you elaborate on that a little. Was this supposed to happen? Is this fixable? How do I stop the device from responding to scenes it is not a member of? Sent from my iPhone using Tapatalk

Device added under 3.1.5. Modified nodes and scene memberships a bit under 3.1.10 No -11000X errors to report.

If I delete the 'Livingroom Fan High' scene, should it also delete the offending link, since the ISY know it is there, even though it does not show in the UI. There should be only one group 91 right. So deleting that scene should delete all the 5b link records that the ISY knows aobut? This has gotten largely academic for me. I am not going to delete the device and re-add it back. As this should never have happened in the first place, as I never had that module as a responder to said scene, what is to say it would not happen again. It would be easier for me to modifiy my behavior than redo that module. This does get me thinking. Group 91 seems kinda like a low number for how new the scene is and how many scenes I have. Is is possible that this was a scene of mine long ago, before I streamlined the IR TX scenes, that did include the IR TX. Hypothetically, I have a scene. It gets assigned group #91. It has only the IR TX iPod Play/Pause node in it as a responder. I delete the scene during clean-up cause I find it is a duplicate or whatever. If the link record does not get deleted, at some point in the future group #91 would get reused by the PLM/ISY and the IR TX would respond, right? But in my case, the ISY knows about the links that should not exist...

Here are the link records that have a 5b but not all have the PLM address. 0F28 : A2 5B 13.24.AA 00 00 0D 0E90 : A2 5B 13.24.AA 00 00 22 0E88 : A2 5B 13.24.AA 00 00 01 0E70 : A2 5B 13.24.AA 00 00 0A 0E58 : A2 5B 13.24.AA 00 00 0F 0E40 : A2 5B 13.00.AA 00 00 05 0E28 : A2 5B 13.24.AA 00 00 13 0E10 : A2 5B 13.24.AA 00 00 0E 0DF8 : A2 5B 13.24.AA 00 00 03 0DE0 : A2 5B 13.24.AA 00 00 24 0DC8 : A2 5B 13.24.AA 00 00 08 0DB0 : A2 5B 13.24.AA 00 00 07 0D98 : A2 5B 13.24.AA 00 00 21 0D80 : A2 5B 13.24.AA 00 00 1F 0D68 : A2 5B 13.24.AA 00 00 1D 0D50 : A2 5B 13.24.AA 00 00 14 0D38 : A2 5B 13.24.AA 00 00 15 0D20 : A2 5B 13.24.AA 00 00 16 0D08 : A2 5B 13.24.AA 00 00 17 0CF0 : A2 5B 13.24.AA 00 00 18 0CD8 : A2 5B 13.24.AA 00 00 1A 0CC0 : A2 5B 13.24.AA 00 00 1B 0CA8 : A2 5B 13.24.AA 00 00 1C 0C90 : A2 5B 13.24.AA 00 00 12 0C78 : A2 5B 13.24.AA 00 00 23 I did the compare and came up with two record mismatches: [Record mismatch]0E40 : A2 5B 13.00.AA 00 00 05 Device link table 0E40 : A2 5B 13.24.AA 00 00 05 ISY link table [Record mismatch]0CF8 : A2 11 00.F5.69 00 00 17 Device Link Table 0CF8 : A2 11 12.F5.69 00 00 17 ISY link table

Okay did the rest thing. Came up with this: 33176 Livingroom Fan High 49280 91 16 7C 18 6 12 F5 69 11 14 9D 29 2 F C1 DE 3 So I am looking for the number 91 (5b?) in the second byte of a link record. In this example what value is the second byte? 06? 0CD0 : A2 06 16.7C.18 00 00 1A

I have a 2411T IRLinc Trasmitter. It has 24 nodes. One of those nodes is the IR code for play/pause on my iPod. I put some fanlincs in, and created some scenes for these. One of these scenes is called Livingroom Fan High. This scene has 4 members IR RX-Liv Fan H (a 2411R IRLinc Reciever) as a controller a secondary KPL button as a responder another secondary KPL button as a controller from a different KPL Living room Fan-motor (of course) This scene works fine when controlled from either of the member controllers; however, when I trigger it from the ISY it causes my IR Tranmitter 2411T to send the code to play/pause my iPod. It should have nothing whatsoever to do with this scene. So I figured errant half link or something. So I tried adding the iPod Play/Pause node of the IR TX to the scene, then delete it, but it persists. But only when triggered from the ISY. So I tried adding every node of the IR TX to the scene, then deleting it. Same thing the ISY initiation of the scene cause the Play/Pause node of the IR TX to fire. Thoughts?

A cool idea, using disable. But my requirements are that should the conditions become false during the wait, the action does not execute.

So, just out of curiosity, as the state variable idea is working great, how would we have done this before variables?

Thanks for the quick reply!! Works great. An interesting distinction between variables and using programs as flags. It had not occurred to me that setting up a variable as a 1 or 0 would be any different that the true-false condition of a program, but here we are. And indeed you solution works perfectly.

I think I am having a brain failure. I should know this but I am stumped. I have a really complex program that is re-entering execution during a wait and I want to fix this today, but I cannot figure out what to do. So I made a small program that is simple and explanatory of my issue: If Status 'Kitchen / Kitchen Fan-Light' is On Or Status 'Kitchen / Kitchen LEDs' is On Or Status 'Office / Office Fan' is On Or Status 'Office / Office Hutch Lights' is On Then Wait 10 seconds Set 'Office / Office Desk Lamp' On Else - No Actions - (To add one, press 'Action') For this example I want the desk lamp to come on 10s after any of the other units in the if come on. The problem here is that as long as I am changing some of the units in the condition I can keep the desk lamp from coming on. Even though the program is always true as I leave one of the conditions units on, the new status of another device in the if causes a re-entry into the wait and the desk lamp does not come on. So I logically split this into two programs: If Status 'Kitchen / Kitchen Fan-Light' is On Or Status 'Kitchen / Kitchen LEDs' is On Or Status 'Office / Office Fan' is On Or Status 'Office / Office Hutch Lights' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') If Program 'Test Program' is True Then Wait 10 seconds Set 'Office / Office Desk Lamp' On Else - No Actions - (To add one, press 'Action') But this suffers the same issue. Even though the test program is true, and an event causes an evaluation of the status that results in 'true' so the program status does not change, the second program re-evaluates and I can keep the desk lamp from coming on as long as I change conditions in the test program before it gets through its wait, but always being true. How do I set this up so the desk lamp comes on 10s after any of the other units come on, but not if all of the units are off before the wait expires? In the real program, the issue is that I have lots of conditions. I want something to happen, but only after 10m of 'True'. I do not care how the conditions change, as long as it has been 'True' for 10m. If at anytime in the 10m wait there is a condition of 'False' I do not want execution.

As always, thanks LeeG. A very thorough and informative answer.

So we can see what the ISY thinks the link tables of a device should be. Why is that option not available for the PLM? It would be nice to get a quick count on total number of links in the PLM. Under Tools>Diagnostics>Show ISY Links Table there is as drop down menu where you get to pick the device that you wish to view the links ISY thinks the device should have. Why is the PLM not one of the devices available to choose in this list?

Adding my IR RX after deleting it and factory resetting it due to previously mentioned issue. Ready/Busy Flag flashes to Busy and a Progress bar pops up when adding a node/code. Immediately goes back to Ready and pop up progress bars disappears even though it is not done writing to device and write flag on device does show still writing.

The tendrils of this have been discussed in other topics, but I thought it would be nice to have all the hard limits in one place. Also I do not know what all these values are so chime in if you know something. ISY Maximums: Pro: Max. Devices/Scenes 1024 Max. Programs 1000 Base: Max. Devices/Scenes 256 Max. Programs 300 PLM Maximums: V 63 and below 417 links maximum above v 63 2000 links but the processor was only able to handle about 800 really reliably Dual Band PLM 1023 links with a processor that can handle all that. Questions: The real limit on scenes is 255 right? So what does Max. Devices/Scenes mean? Is the program limit a hard number, or is it an available memory issue? and therefore an estimate?

What is the function of 'Responding' when the status of a device is selected in the If of a program? If Status 'Bathroom / Bathroom Shower Fan' is Responding Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Correct Sent from my iPhone using Tapatalk

No. I still only have one node with an address. That node now responds to two distinct different IR commands. I had 18 or so distinct individual IR codes programmed into the module. Each node responds to different unique IR codes. I need some additional controls. So I find some valid unassigned NEC codes. I know they are valid because the green talkback LED responds to their sending to the module. I know they are not currently assigned to any node as I use the event viewer to verify no insteon communications with initiation of that unique IR code. I add the new IR code using the procedure prescribed by ISY pop-up window. No new node is added to the tree. But now I have an existing node that responds to two different unique IR codes. To me it appears that the ISY did not recognize that I already had 18 nodes with this module. Then when I started adding additional codes it started incrementing the node numbers by one assigning the new unique IR codes to existing nodes that now respond to two different IR commands. Sent from my iPhone using Tapatalk

I do not know if this is related to the beta, but I thought I would mention it here just in case. I have an IRLinc receiver. 2411R. I attempted to add a several buttons to the device and it was a disaster. The first button I added got the address of xx.xx.xx 1 the second xx.xx.xx 2 and so on. This was a disaster because those node values already existed in the ISY. So the ISY was not adding new nodes to the tree. It appeared that the new IR code got added to an already existing node. So now when I send the IR code stored in node xx.xx.xx 1 the node shows a control on. Also if I send the first new code I tried to learn tonight the node xx.xx.xx 1 shows a control on. I had about 18 nodes on this device before trying to add more tonight. I tried adding about 7 buttons to try and figure out what was going on and each new button added got added to the next higher already existing node. At this point I can figure nothing to do but delete, factory reset the module, and begin again. The first button I added tonight should have been xx.xx.xx 18 or FF or whatever the value would be, not xx.xx.xx 1 and I should have gotten a new node.

As a Mac user, thanks for that. Interesting.

An observation: 6 button KPL v.2D. I want to have the big off button have its LEDs off as referenced in this post: viewtopic.php?f=27&t=2623 If I set this as a toggle in the ISY, it functions as expected with the LEDs illumated behind the big 'On' button when pressed, and behind the big 'Off' button when pressed. Using the methodology mentioned in the referenced post, if I make the main button a non-toggle off, the big LED never illuminates. If I make it a non-toggle on, I cannot make the big 'On' buttons LED ever turn off. I still have to invoke the manual tap method to get the button to function, but have the big 'Off' LEDs never on. A function I have never had much success with from the ISY, despite others seeming to have success with setting this behavior from within the ISY.

Lee, Thanks for taking the time to post. Query Insteon Engine fixed everything!!! Is that a new feature in the 3.XX series. I do not remember that function?

Before I go changing anything, here is an event trace of a failure with a v.40 2476D: Thu 04/12/2012 11:42:17 AM : [ Time] 11:42:17 1(0) Thu 04/12/2012 11:42:17 AM : [All ] Writing 2 bytes to devices Thu 04/12/2012 11:42:17 AM : [18 E4 13 1 ] Memory : Write dbAddr=0x0264 [F2] cmd1=0x2E cmd2=0x00 Thu 04/12/2012 11:42:17 AM : [iNST-TX-I1 ] 02 62 18 E4 13 0F 28 02 Thu 04/12/2012 11:42:17 AM : [iNST-ACK ] 02 62 18.E4.13 0F 28 02 06 SET-MSB(02) Thu 04/12/2012 11:42:17 AM : [iNST-SRX ] 02 50 18.E4.13 13.24.AA 2B 28 02 SET-MSB(02) Thu 04/12/2012 11:42:17 AM : [standard-Direct Ack][18.E4.13-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:42:17 AM : [iNST-TX-I1 ] 02 62 18 E4 13 0F 2B 64 Thu 04/12/2012 11:42:18 AM : [iNST-ACK ] 02 62 18.E4.13 0F 2B 64 06 PEEK (64) Thu 04/12/2012 11:42:18 AM : [iNST-SRX ] 02 50 18.E4.13 13.24.AA 2B 2B 19 PEEK (19) Thu 04/12/2012 11:42:18 AM : [standard-Direct Ack][18.E4.13-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:42:18 AM : [iNST-TX-I1 ] 02 62 18 E4 13 0F 29 F2 Thu 04/12/2012 11:42:18 AM : [iNST-ACK ] 02 62 18.E4.13 0F 29 F2 06 POKE (F2) Thu 04/12/2012 11:42:18 AM : [iNST-SRX ] 02 50 18.E4.13 13.24.AA 2B 29 F2 POKE (F2) Thu 04/12/2012 11:42:18 AM : [standard-Direct Ack][18.E4.13-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:42:18 AM : [iNST-TX-I1 ] 02 62 18 E4 13 0F 24 00 Thu 04/12/2012 11:42:19 AM : [iNST-ACK ] 02 62 18.E4.13 0F 24 00 06 (00) Thu 04/12/2012 11:42:19 AM : [iNST-SRX ] 02 50 18.E4.13 13.24.AA 2B 24 00 (00) Thu 04/12/2012 11:42:19 AM : [standard-Direct Ack][18.E4.13-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:42:19 AM : [18 E4 13 1 ] Memory : EPROM Refreshed And here is success with a v.40 2477D: Thu 04/12/2012 11:48:03 AM : [ Time] 11:48:04 1(0) Thu 04/12/2012 11:48:04 AM : [All ] Writing 2 bytes to devices Thu 04/12/2012 11:48:04 AM : [1A D F6 1 ] Memory : Write dbAddr=0x0264 [19] cmd1=0x2E cmd2=0x00 Thu 04/12/2012 11:48:04 AM : [iNST-TX-I1 ] 02 62 1A 0D F6 0F 28 02 Thu 04/12/2012 11:48:04 AM : [iNST-ACK ] 02 62 1A.0D.F6 0F 28 02 06 SET-MSB(02) Thu 04/12/2012 11:48:04 AM : [iNST-SRX ] 02 50 1A.0D.F6 13.24.AA 2B 28 02 SET-MSB(02) Thu 04/12/2012 11:48:04 AM : [standard-Direct Ack][1A.0D.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:48:04 AM : [iNST-TX-I1 ] 02 62 1A 0D F6 0F 2B 64 Thu 04/12/2012 11:48:04 AM : [iNST-ACK ] 02 62 1A.0D.F6 0F 2B 64 06 PEEK (64) Thu 04/12/2012 11:48:04 AM : [iNST-SRX ] 02 50 1A.0D.F6 13.24.AA 2B 2B F2 PEEK (F2) Thu 04/12/2012 11:48:04 AM : [standard-Direct Ack][1A.0D.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:48:04 AM : [iNST-TX-I1 ] 02 62 1A 0D F6 0F 29 19 Thu 04/12/2012 11:48:04 AM : [iNST-ACK ] 02 62 1A.0D.F6 0F 29 19 06 POKE (19) Thu 04/12/2012 11:48:05 AM : [iNST-SRX ] 02 50 1A.0D.F6 13.24.AA 2B 29 19 POKE (19) Thu 04/12/2012 11:48:05 AM : [standard-Direct Ack][1A.0D.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:48:05 AM : [iNST-TX-I1 ] 02 62 1A 0D F6 0F 24 00 Thu 04/12/2012 11:48:05 AM : [iNST-ACK ] 02 62 1A.0D.F6 0F 24 00 06 (00) Thu 04/12/2012 11:48:05 AM : [iNST-SRX ] 02 50 1A.0D.F6 13.24.AA 2B 24 00 (00) Thu 04/12/2012 11:48:05 AM : [standard-Direct Ack][1A.0D.F6-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 04/12/2012 11:48:05 AM : [1A D F6 1 ] Memory : EPROM Refreshed

Were there adjustments to the LED Backlight settings in this round of updates since the last official release? Half of my Switchlincs did not dim their LEDs last night after upgrading from 3.1.17.

Upgrade progressed smoothly until ISY lock-up with PWR RX and TX leds on solid. Hard re-boot and all is well.

Should be 3.2.4