Weird question maybe - Don't even know how to refer to it

[wpmjones]

Hey Lee - Likeminded techno junkies unite! Let's get this thing figured out. Won't be able to do it til tomorrow night, but I'll follow what you've outlined and let you know what happens. Thanks for the help! I do enjoy some good troubleshooting!

[Sub-Routine]

It seems you are on a battle with a bad PLM.

 

Please call Smarthome and request a replacement instead of wasting more time.

 

 

Rand

[wpmjones]

I'll make you a deal, Rand. I'm cross-shipping with SmartHome. I'll play with the one I have until the new one arrives. See what we can figure out. Sound fair?

[LeeG]

wpmjones

 

I’ve had an email conversation with Michel and the question has come up over which Link Management | Advanced Options is selected. You should be running with the “Automatic†option and not the “Device Reported†option. This has to do with the way the ISY is attempting to write the link records in the ICON Appliance module. It should have nothing to do with the PLM link records.

 

Lee

[wpmjones]

When I re-add them this evening, I'll make sure I chose that option. Thanks!

[wpmjones]

Seeing some success using the Automatic option. I have everything re-added except the TriggerLinc which is giving me trouble now. But everything else is working as expected and reporting back to ISY instantly. The PLM Links are even there.

 

When I try to add the TriggerLinc, I get this...

Failed writing the highwater mark

Node not added - failed removing links

 

Here is the log

Fri 09/17/2010 07:06:22 PM : ---- Initializing the linked devices ----
Fri 09/17/2010 07:06:22 PM : ---- All Linked Devices are now initialized ----
Fri 09/17/2010 07:06:22 PM : ---- Add remaining devices ----
Fri 09/17/2010 07:06:22 PM : [  13 E7 32 1] Removing all links
Fri 09/17/2010 07:06:40 PM : [iNST-ACK    ] 02 62 13.E7.32 0F 0D 00 06                 (00)
Fri 09/17/2010 07:06:44 PM : [13 E7 32 1  ] Failed getting engine version. Reverting to i1.
Fri 09/17/2010 07:06:44 PM : [13 E7 32 1  ] Using engine version i2
Fri 09/17/2010 07:06:44 PM : [iNST-ACK    ] 02 62 13.E7.32 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)
Fri 09/17/2010 07:06:53 PM : [iNST-ACK    ] 02 62 13.E7.32 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)
Fri 09/17/2010 07:07:02 PM : [iNST-ACK    ] 02 62 13.E7.32 1F 2F 02 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06        (02)
Fri 09/17/2010 07:07:06 PM : [  13 E7 32 1] ** Not added ** Remove Device Links failed
Fri 09/17/2010 07:07:06 PM : ---- All Remaining Device Added ----

 

Process:

Link Management > New INSTEON Device

Entered Info, selected 2421 TriggerLinc

Put TriggerLinc in Link Mode

Left Remove Links selected

Clicked OK

Received the above error message

 

Thoughts?

[LeeG]

The initial command Get INSTEON Engine (0x0D) failed to get any response from the TriggerLinc ....

 

Fri 09/17/2010 07:06:40 PM : [iNST-ACK ] 02 62 13.E7.32 0F 0D 00 06 (00)

Fri 09/17/2010 07:06:44 PM : [13 E7 32 1 ] Failed getting engine version. Reverting to i1.

 

This can happen either because the TriggerLinc was not in linking mode (which you indicated it was) or the TriggerLinc is not in range of an Access Point (or equivalent) so RF communication was not possible.

 

Move the TriggerLinc near an Access Point (or equivalent) and be sure the TriggerLinc is in linking mode and has not timed out of linking mode. I just added a TrggerLinc under 2.8.2 successfully.

 

EDIT: once the process reverted to I1 the process was over. The TriggerLinc does not have the Peek/Poke commands necessary for I1.

[wpmjones]

Finally got the darned thing on there. I had it pretty close to begin with so I don't think distance was the issue. Remember that I switched from Device Reported to Automatic for the Icons? Well I had to switch back to get the TriggerLinc on. At least that what seems to have finally worked. So I'll just remember - Device Reported for the TriggerLinc and Auto for everything else.

 

The good news, all 7 devices are in ISY and show up in the PLM Links Table. All devices are reporting back to the PLM instantly. Only one test left and that is to see if the ToggleLinc that started this whole mess will successfully disable and reenable the program that I have working with.

 

Not sure I've mentioned it, but all of this is for my 4 year old son who has Prader-Willi Syndrome. The primary symptom of which is that he never feels full. So he will often wake up early in the morning and sneak out of his room and into the kitchen. I needed an effective (and fool-proof) way to know when he leaves his room. So when the TriggerLinc is opened, the lights in our bedroom and bathroom flash 3 times, then stay on. I wanted to use the ToggleLinc on our family room light as an "arm/disarm" control for the alarm program. So if this works right (will be testing soon), when the alarm goes off, you come out to the family room, Fast On the family room light and the alarm is disarmed and the bedroom lights shut off (in case the spouse is still sleeping). If it's time to stay up, we just leave the alarm disabled. If it's still early, we put him back to bed, Fast Off the family room light which will re-arm the alarm.