matapan

After performing a number of factory resets, and moving the Morninglinc around, installing it next to the PLM, I decided to capture the logs, presented below. The first log is from the action of adding Morninglinc to the network. The second log is a capture of what happens when Morninglinc is added to a scene. Can anyone knowledgable about these traces tell me what is wrong here? Thanks. Morninglinc Device Add Log: Sat 01/28/2012 09:12:29 AM : [LNK-BGN ] 02 64 01 00 06 Sat 01/28/2012 09:12:42 AM : [LNK-STAT ] 02 53 M(01) gid=00 18.EF.7C 0F06 3A Sat 01/28/2012 09:12:42 AM : Linked: Linked 18.EF.7C.00 type=0F.06.3A Sat 01/28/2012 09:12:42 AM : [iNST-ACK ] 02 62 18.EF.7C 0F 28 0F 06 SET-MSB(0F) Sat 01/28/2012 09:12:42 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 28 0F SET-MSB(0F) Sat 01/28/2012 09:12:42 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:12:42 AM : [iNST-ACK ] 02 62 18.EF.7C 0F 2B F8 06 PEEK (F8) Sat 01/28/2012 09:12:43 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 27 2B A2 PEEK (A2) Sat 01/28/2012 09:12:43 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sat 01/28/2012 09:12:43 AM : [18 EF 7C 1 ] MorningLinc database accessible Sat 01/28/2012 09:12:43 AM : [18 EF 7C 1 ] Start : Adding device to ISY Sat 01/28/2012 09:12:43 AM : [18 EF 7C 1 ] Finish : Adding device to ISY was Successful Sat 01/28/2012 09:12:43 AM : [18 EF 7C 2 ] Start : Adding device to ISY Sat 01/28/2012 09:12:43 AM : [18 EF 7C 2 ] Finish : Adding device to ISY was Successful Sat 01/28/2012 09:12:43 AM : [All ] Writing 0 bytes to devices Sat 01/28/2012 09:12:43 AM : [LNK-BGN ] 02 64 01 00 06 Sat 01/28/2012 09:12:51 AM : ---- Initializing the linked devices ---- Sat 01/28/2012 09:12:51 AM : [18 EF 7C 1 ] Reading all links Sat 01/28/2012 09:12:51 AM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Sat 01/28/2012 09:12:51 AM : [18 EF 7C 1 ] Using engine version i2 for '18.EF.7C-On' Sat 01/28/2012 09:12:52 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:12:52 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:12:52 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:12:53 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 FF 01 A2 00 13 22 2E FF 00 00 00 Sat 01/28/2012 09:12:53 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:12:53 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:13:02 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:13:02 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 27 2F 00 (00) Sat 01/28/2012 09:13:02 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sat 01/28/2012 09:13:03 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 FF 01 A2 00 13 22 2E FF 00 00 00 Sat 01/28/2012 09:13:03 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:13:03 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:13:12 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:13:12 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:13:12 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:13:12 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 FF 01 A2 00 13 22 2E FF 00 00 00 Sat 01/28/2012 09:13:12 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:13:12 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:13:17 AM : ---- All Linked Devices are now initialized ---- Sat 01/28/2012 09:13:17 AM : ---- Start: Generate Scenes from links ---- Sat 01/28/2012 09:13:20 AM : ---- End: Generate Scenes from links ---- Sat 01/28/2012 09:13:20 AM : ---- Initializing the linked devices ---- Sat 01/28/2012 09:13:20 AM : ---- All Linked Devices are now initialized ---- Sat 01/28/2012 09:13:20 AM : [All ] Writing 0 bytes to devices Sat 01/28/2012 09:13:20 AM : [All ] Writing 0 bytes to devices MorningLinc Add to Scene Log: Sat 01/28/2012 09:05:15 AM : [18.EF.7C-Off] Start : Adding to scene 'Garage Door Lock' Sat 01/28/2012 09:05:15 AM : [18.EF.7C-Off] Making 'Garage Door Lock' a Controller Sat 01/28/2012 09:05:15 AM : [MNG-LNK-RSP ] 02 6F 40 E2 3A 18 EF 7C 0F 06 3A 06 Sat 01/28/2012 09:05:15 AM : [18 EF 7C 2 ] Link 0 : 0FF8 [A23A13222EFF0001] Saving [A23A13222EFF0001] Sat 01/28/2012 09:05:15 AM : [18.EF.7C-Off] Finish : Adding to scene 'Garage Door Lock' was Successful Sat 01/28/2012 09:05:16 AM : [All ] Writing 8 bytes to devices Sat 01/28/2012 09:05:16 AM : [18 EF 7C 1 ] Using engine version i2 for '18.EF.7C-On' Sat 01/28/2012 09:05:16 AM : [18 EF 7C 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Sat 01/28/2012 09:05:16 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:05:16 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:05:16 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:05:17 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 F7 01 00 00 00 00 00 00 00 00 00 Sat 01/28/2012 09:05:17 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:05:17 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:05:26 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:05:26 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:05:26 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:05:35 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:05:36 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:05:36 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:05:36 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 F7 01 00 00 00 00 00 00 00 00 00 Sat 01/28/2012 09:05:36 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:05:36 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:05:40 AM : [18 EF 7C 1 ] Link 1 : 0FF0 [0000000000000000] *Failed Writing [00..............]

LeeG: Thanks for the reply. I am curious if the factory reset procedure supplied with the product is actually accurate, if it does not remove the linkage to the lock itself. What constitutes a reset? If the links are removed in the ISY's device discovery process, does this permanently prevent the device from being used with the controller? I am perplexed with the Morninglinc's behavior and its inability to be added to a scene. Would a device events trace help illuminate what is happening during the add to scene process?

LeeG: I'm not sure if what I am experiencing is a communication problem. I have no problem adding the device, nor do I have any problem toggling it as a device. The only time a communication error with the Morninglinc occurred is when I attempted to add the Morninglinc to a scene as a responder. Moving the Morninglinc closer to the PLM does not yield any different results. Same thing occurs: There's no problem adding the device, or toggling it as a device. Adding it to a scene causes the communication error to come up.

I have a Morninglinc with firmware v3A which I added a while ago. I could always lock and unlock the device by toggling the On Off state in the Admin Console. Having read the posting related to the purpose of the two nodes created for Morninglinc, I decided to create a new scene and add the Morninglinc device to the scene. During this operation of adding the device to the scene, the Admin Console will return a Communication Error. Both Morninglinc device nodes now have a red exclamation mark on their icons. The selected Morninglinc device node also appears in the scene, with the red exclamation mark. Yet, I can still toggle the device and lock/unlock the lock with no apparent problem. I believe I added the device following the procedure outlined in the Wiki, but there might be a possibility I added the device and removed existing links. I reset the device using the procedure outlined in the Morninglinc user guide. However, I'm not certain if the factory reset procedure actually worked - I was able to press the set button after the reset to toggle the lock still. Is this by design, or have I failed to factory reset the unit properly?

Have you tried deleting the dual band Keypadlinc from the My Lighting list, then adding it back after the ISY firmware upgrade?

What is the error reported in the log?

Would assigning X10 commands to the individual Keypadlinc buttons directly solve the problem?

I tried using scenes for button grouping today. The intent was to set up a group where only one button in the group could be on at a time. The scene I created works, except for the fact that the button that is ON can be toggled off, creating the state where all of the buttons in the scene are off. What can I do to ensure one button in the group is always on?

I have a simple program which sends a X10 command when a Keypadlinc button is turned ON: If Status 'KPL A' is On Then Send X10 'A1/On (3)' Else - No Actions - When executed and the Keypadlinc button is turned on, the X10 device that is supposed to respond to the program does not respond. I tried running the Then path of the program manually. This worked just fine. Next, I tried adding delays in the program: If Status 'KPL A' is On Then Wait 2 seconds Send X10 'A1/On (3)' Else - No Actions - This worked, but the delay makes the program unusable in its context. Sending multiple commands seemed to be the only workaround so far: If Status 'KPL A' is On Then Send X10 'A1/On (3)' Send X10 'A1/On (3)' Else - No Actions - Question: Is there a better way to implement this and eliminate the delay or duplicate command? Presumably, this is an artifact of some power line signal collision that is occurring. The event log trace shows the X10 command clearly being transmitted.

Would it be helpful to adjust the timeout period for different periods of the day as a means to account for the amount of activity that may occcur in the home when someone is present? The best example of this is late night, when everyone is sleeping, vs. early morning or early evening, when there might be more activity, where a shorter timeout might be in order.

I second LeeG's suggestion for a programmatic check. If ISY will evolve into a more mainstream consumer oriented device, such checks are particularly useful in reducing the number of calls or posts generated.

I'm using the latest version of the motion sensor now. Three of them. Has anyone experienced any erratic behavior of the motion sensor under very low voltage, real world conditions, or does the unit simply stop working when the battery goes flat? I would prefer having the sensor not send any ON/OFF commands randomly when the battery goes low, instead simply stop sending ON/OFF commands altogether when the device cannot run correctly with the voltage available.

Would it be useful to put a validation check at startup of the Admin Console so the correct version of the AC is run with the correct firmware version? If the AC and ISY firmware versions don't match, return an error showing the firmware version on the ISY and the AC version being run. A reminder to clear your Java cache if you are have loaded an AC version that doesn't match the ISY firmware version might also be useful, if clearing the cache under the circumstances is important.

I recently started to think about the states in which the Admin Console loses its subscription to the ISY device and stops presenting device and program state information. In version 3.1.16, I've distilled down several scenarios and their actual outcomes below: Sleep Level Low - user walks away from computer and screen power save is initiated while Admin Console is session is open. Actual Outcome Upon return, user is prompted to log in to Admin Console (expected result) Moderate/High - laptop clamshell is closed, putting machine in moderate powersave state, or machine is explicitly placed in hibernation while Admin Console is running. Actual Outcome Upon return, user is not prompted to login to Admin Console. State information presented is no longer valid, or is missing. Resolution: Closing the browser completely, and restarting the Admin Console resolves the issue. Is there a way to handle the moderate/high use case described above in a similar manner that the low sleep state use case is handled now? This would be ideal - I'd prefer not to restart the browser if at all possible. I was wondering if this behavior with how the subscription is handled might have some relevance to some of the sync issues I'm experiencing with Mobilinc Pro currently.

LeeG: The Start Linking command was used, to confirm. My understanding is that if the Keypad load button is pressed for 10 seconds, it's supposed to go into linking mode, at which point, the KPD identifies itself to ISY. Isn't that the way it works? I know it does for my other devices, like Switchlincs. I'll try manually adding the device using the auto discover device type setting the next time I'm around the device. Thanks!

LeeG, Regarding Q2: this is the auto discover scenario. 1. Set up ISY to initiate linking via auto discover mode. 2. Set KPD in linking mode. Expect: KPD to be discovered and show up in Admin Console. Actual: No device shows up in the Admin Console. With other devices, the expected result usually occurs.

I am starting to write a lot of programs, organizing them in folders. The programs appear in a reasonable order in the Program Details tab, with related programs in a folder organized under the folder hierarchy. In the Program Summary tab, the individual programs appear in alphabetical order in a flat organization. The hierarchy is displayed in a column which shows the path. This is hard to read and use. Is there any way to display programs in hierarchical order?

I have some old v1.3 Keypadlincs that could not be auto-discovered by ISY when the Keypadlinc was added to the network. I was able to add them manually to the network by providing the address of the device and specifying the device type. ISY99 is aware of these devices and can talk to them. The firmware version shows up as "v00" if one adds devices manually. I've discovered that this is normal from reading the postings here. Questions: 1. Is it possible for ISY to retrieve the device firmware version and update the Admin Console and its own database via an explicit command? 2. Why are some devices not auto discoverable? Is this an artifact of attempting to discover an older device?

Would the last execution time of a selected set of programs provide some indication of activity, particularly if the programs themselves relied on control changes?

I happened to be setting up Notifications on an ISY-26 with firmware version 2.7.15 when I noticed there was no Customizations tab for entering the text to be sent. Was this feature available in firmware version 2.7.15 for ISY-26?

Doesn't the ISY sync its time to a NTP server? I think my Mac and most Windows machines now have the same capability. So, theoretically, the time wouldn't be that far off, would it?

That's also what I've done as well, using checks for Control rather than status. Going further, I check both cases: If Device is Switched on and The devIce is not switched off The resulting program stays using such a check seems to yield results more in line with one's expectations as well.

Would a Dual-Band PLM and an Access Point near the breaker box provide a possible solution in the scenario described?

Thank you for the reply, LeeG. What is the relationship between the columns and the tree below in the same dialog?

I'm still on 3.1.14 and also experienced problems with incorrect Keypadlinc secondary button status. I'll be upgrading to 3.1.15 tonight to see if the upgrade also clears up the problem for me.