smokegrub

Michel: The email problem disappeared last evening, but it has reappeared today. Moreover, I have had numerous other bizarre things happening. For example, last evening when I tried to load the Admin Console I could not because the local IP address had disappeared. I manually added the address and opened the Console but that has never happened before. Also, when linking new devices, adding or changing programs, etc. changes are occurring with other devices and/or programs that are entirely unrelated. Thus far I have resolved these with Write Updates or Queries but the fact they occurred is alarming. I have a ticket submitted and, hopefully, this can be resolved quickly. Thanks for your feedback.

The email mysteriously began working again but now the local IP was dropped by the Admin Console. Just another in a growing list of bizarre things that have been happening. I have submitted a ticket to UDI. I suspect I am going to have to replace the firmware.

Yesterday evening email notifications were being successfully sent. This morning they have failed. I have been using the Default setting in Emails/Notifications w/o problem for months. I tried not using the Default settings and I get the same message when I run a test: Mail Server Failure [unsupported authentication method]. When I test my email conventionally it works fine. I have had several settings in the Admin Console change inexplicably since I started using 4.2.10.

I went to the desired location and it was slow at first but seems to be working fine now. If that changes, I will link it there. Thanks again, LeeG.

I finally fixed the Deck Sensor by Write Updates also. Why I needed to do that with a device I had done nothing to in terms of programming or, anything for that matter, is disconcerting at best. My sincere thanks and appreciation to all of you, and especially, LeeG. These Hidden Door Sensors have been the biggest challenge I have faced with ISY. Oh, for the day when ISY moves more toward plug and play!

I did Write Updates for the Bathroom Fan device and that problem resolved. I put the Hidden Door Device that I could not get to show its status into linking mode and queried it. I pressed the set button twice to get it out of linking mode, pressed and released the Contact Plunger and it now shows its status. The Hidden Door sensor that has worked beautifully since its install now has gray icons beside its nodes in the device tree. What does that signify and how can I remedy it? I hope I don't have to remove it from its location. This is, hopefully, the last step toward getting things staightened out.

Bizarre and down-right frightening. Although I never touched them in the device tree I have now lost the link to a device controlling a bathroom fan and the link to the hidden door sensor that I had previously linked. I deleted, reset and relinked the bathroom fan and it now has a green icon adjacent to it and no longer responds to a program that controls how long it runs. I deleted the program and rewrote it but each time the device was referenced in the program it had the green icon adjacent to it and the resulting program will not run. The formerly successful door sensor nodes all have gray icons adjacent to them and the program managing their sending notifications has failed. Once again, I never messed with anything related to these devices. All I have been doing is trying to link a new door sensor. I have a backup for conditions prior to this debacle, but will it reconnect these devices and restore previously successful functions.

4.2.10 offers a linking selection of Sensors > Hidden Door Sensor. I returned to that method and gave it a try. I linked with it and waited untile the device's green light stopped flashing. I then tried pressing the Constact Plunger. Still no device status reporr for the door sensor. I then pressed the Set Button and tried the Plunger again. No success. I must be doing something wrong but for the life of me I can't figure out what it is! The irony is I have one functioning perfectly that I setup earlier!

I am using 4.2.10. I will try linking as you suggest. By the way, MikeD, I pressed the Set Button while the device was flashing and it changed rates in flashing. I pressed the Set Button Again and the LED turned off. I pressed the Contact Plunger twice and still no status given for the Door Sensor!

LeeG: I received the replacement door sensors today and you were correct, as usual, the original devices apparently weren’t defective. Let me review my process for linking and setting up the devices and, perhaps, you will see something I am doing incorrectly: 1. When the battery tab is pulled I wait until the Status LED stops flashing. 2. I place the device within 18-inches of the PLM. 3. Link Management > New Insteon/A10/X10 Device > Remove Existing Links 4. Press and hold the Set Button on Device until it beeps and the Status LED flashes green.. 5. Execute the Link. 6. All 3 nodes for the device appear in the Device Tree. 7. I wait until the green light in the device stops flashing (about 5 minutes). 8. I press the Contact Plunger until the Status LED turns green. I release the Contact Plunger and the device turns red. 9. Checking the Current State of the device in the Admin Console shows no status. 10. Writing Updates to the device gives a response that ISY cannot communicate with the device and a red exclamation point appears adjacent to all 3 nodes in the device tree.

LeeG: When I paste in this manner I get code--not readible.

Teken: Your program is spot on! You also taught me something using the enabled/disabled feature. Many thanks.

I have a pro and I am nowhere near the device limit. The replacements are in the mail. If they don't link.....

Objective: When KPL G is pressed, wait 5 minutes to give me time to exit the door, then send an email notification any time thereafter that the door is opened or until KPL G is turned off. If Kitchen KPL G is 100% Then Wait 5 minutes Run Deck Door Open (Disabled) Else No Action Run Deck Door Open Program (Disabled): If Door Sensor is On Then Send Notification Else No Action The program runs only for one cycle and all further door openings do not result in a notification. By the way, I still haven't been able to figure out how to post programs here.

LeeG: Thanks for all your help. It was very much appreciated. I contacted Smarthome and reviewed all we had done with this problem and they agreed the firmware in the batch beginning with the device number 2B.2F. was likely defective. They have agreed to replace the devices. Again, many thanks.

I have looked for the firmware level and I obviously do not know where the "right side of the node display is located".

I linked a different Door Sensor this morning and it also will not report its state. I queried the device and got the following message: Subscriber didn’t reply to event:1 147 No network connection [DHCP) state = RENEW} I then exited the ISY and reentered with my password. I queried the device again and got the message: Subscriber didn’t reply to the event. What is interesting is that the device that is successfully installed and reporting is 2C.71.97. The two failed devices are 2B.2F.35 and 2B.2F.26. These latter two devices both begin with the preface 2B.2F and may have something intrinsic to their manufacture that is defective. I look forward to any feedback.

I am going to knock off for the day; I am getting tired. Will do a factory reset tomoroow and go through the drill. If that diesn't work, II will then try the one additional device I have on hand. If it links successfully, I will call Smarthome and get a replacement for the one that doesn't work.

It wasn't, but I carried it back to within 2 feet of the PLM and tapped the button. Nothing. The firmware is 4.2.10. As I stated above, I have already linked one of these devices, programmed it and it is working beautifully.

I have already done that several times and it still does not show its state.

I deleted the device, factory reset it, linked it and waited until the flashing light was off (several minutes). The device's current state is still not displayed. The Low Battery state is presented; the Heartbeat is not.

Didn't know that. will chack again later.

I was able to get the device to link by positioning it near the PLM. However, it does not display its state after linking. Moreover, the linking display on the device (flashing green light) keeps blinking after linking. I have deleted the device from ISY, factory rest the device and relinked with the same result.

Here is the events log: Fri 10/03/2014 02:57:13 PM : [ IR] 014A Press Fri 10/03/2014 02:57:24 PM : [ IR] 0156 Press Fri 10/03/2014 02:58:03 PM : [ IR] 014A Press Fri 10/03/2014 02:58:26 PM : [2B 2F 26 ] Added to list of devices to link to ISY Fri 10/03/2014 02:58:26 PM : [iNST-TX-I1 ] 02 62 2B 2F 26 0F 0D 00 Fri 10/03/2014 02:58:26 PM : [iNST-ACK ] 02 62 2B.2F.26 0F 0D 00 06 (00) Fri 10/03/2014 02:58:35 PM : [iNST-TX-I1 ] 02 62 2B 2F 26 0F 0D 00 Fri 10/03/2014 02:58:35 PM : [iNST-ACK ] 02 62 2B.2F.26 0F 0D 00 06 (00) Fri 10/03/2014 02:58:44 PM : [iNST-TX-I1 ] 02 62 2B 2F 26 0F 0D 00 Fri 10/03/2014 02:58:44 PM : [iNST-ACK ] 02 62 2B.2F.26 0F 0D 00 06 (00) Fri 10/03/2014 02:58:48 PM : [2B 2F 26 0 ] Failed to add device, reason 3

I have already linked and I am using a Hidden Door Sensor (2845-222). I am trying to link a second device and, under Link Management, I have selected Link a Sensor, Hidden Door Sensor, typed in the device’s address and assigned it a name. I then put the device in linking mode and proceed. I get the message “Cannot determine Insteon Engine". I then tried Link Management, New Insteon/A10/X-10 device with the same results. I have done a factory reset and repeated the foregoing steps with the same outcome. The device is located the width of a doorway from 2 dual band devices that are linked and functioning properly.