hart2hart

Michel: I upgraded to 3.2.4. However, I don't have old laptop (win XP) to access ISY which had telnet. I'll have to find another telnet program for Win 7? Been so long ... do I need to telenet in via rs232 or can I go in via IP address? Paul

My ISY with latest official release (3.1.17) was getting many errors attempting to sync with NTP service so I reboooted it. ISY restarted with normal query all sequence but then it displayed an additional very slow moving work in progress bar (about 10 minutes to get to 100%). I have a program that sends me a text message at startup so I can review a couple program states and the text message did not arrive until after the progress bar finished so I took a quick look at error log to see if something was wrong and found the following: (BTW I get error messages about opening elk files even though I do not have the module ... no big deal unless it suaggests something larger) Time User Code Message Wed 2012/04/18 08:52:46 AM System -170001 [HTTP] Socket not active#2 30 Wed 2012/04/18 08:52:48 AM System -170001 [HTTP] Socket not active#2 33 Wed 2012/04/18 08:53:04 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:53:25 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:53:51 AM System -170001 [HTTP] Socket not active#2 33 Wed 2012/04/18 08:54:16 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:54:40 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:55:05 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:55:30 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:55:54 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:56:19 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:56:39 AM System -170001 [sLF] FileOpen Failed: /CONF/ELK.CNF Wed 2012/04/18 08:56:39 AM System -170001 [sLF] FileOpen Failed: /CONF/ELK.CNF Wed 2012/04/18 08:57:33 AM System -170001 [HTTP] Invalid socket 30 Wed 2012/04/18 08:57:58 AM System -170001 [HTTP] Invalid socket 30

...just assumed program had to have a condition. Thanks for information about 3.1.?, UD always has solid software and the best support of any product I've ever purchased. I've had HS for years starting in X10 days -- only use it today for interface to DSC panel so I'm look forward to upgrading to variables, implementing DSCLink and retiring HS 2.x. We'll see if 3.x adds any value but I doubt it since all I read is Zwave as in waving goodbye

I want to run a program at reboot (power failure) so I can manually reset the value of a couble program variables that need to be persisted. I'll upgrade to 3.1.? when I have time but system is rock solid and I don't need another project now Easy enough to say run at startup but what "if" condition should I use? Device status, schedule etc?

Okay Thanks. I also want the button to run the then or else branch of the program to set its state. How do I do this without infinite loop? My first thought was make KPL button a controller instead of responder but I think this would create loop issue.

I just added 8 button keypadlinc. I want three buttons to follow the state of 3 programs corresponding. My thought was to turn the button on in the then branch and turn it off in the else branch. Please clue me in as to the nomenclature of Insteon command action for keypadlinc buttons with format of: On 99 / Off 99 (Backlight Level)

I've added 12 IRLinc TX devices to ISY following ISY console onscreen instructions. It appears that the resulting IRLinc TX devices must be added to a scene and then that scene must be turned On for the IR command to be issued. Is this correct or can the IR command be issued for on and/or off command ... or am I missing details on how this works. Thanks.

Upgraded from 2.7.15 to 2.8.15 went well .. yesterday.

Thanks.

Just making sure there is not some quirk or definition difference when using same day vs next day.... In essense, when using "From" and crossing midnight boundary on "To" the proper setting is "Next Day"? The following program would be true starting at 8:00pm tonight (January 30) until 6:14:59am in the morning (January 31)? If From 8:00:00PM To 6:14:59AM (next day) Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Was not near ISY when I posted but this is what I came up with... Look good? If On Mon, Tue, Wed, Thu, Fri From 9:29:00AM To 4:29:00PM (same day) And Program 'Security:Away from Home Status' is False Then Set 'Basement / Basement:HotH2ORecirculate' On Else - No Actions - (To add one, press 'Action')

I have a hot water recirculating pump that has been running 24x7. I qant to automate it to run off when not needed which is basicaly time and security system based. 1)Program Turns unit off at 10:15 pm 2)Program Turns unit on at 5:30 am 3)Turns unit Off at 9:30am MTWThF if "Away from Home" is True 4)Turns Unit on at 4:30pm MTWThF I want to do 5th program/update existing program to turn unit on if I get home early through the work week. That is to say ... it is it is between 9:31am - 4:29 pm MTWThF and "Away from Home" becomes false. What is the most straight forward ISY programing method to accomplish this task? The old school programming methods I learned 25 years ago blind me to the elegant methods possible within the ISY event/program construct (which is fantastic).

I have a series of scheduled events with a program condition for "Away from Home" that occur during the day to make the house look lived in. As each time passes the events become true and stay true until the program flag "Away from Home becomes" False when I disarm the security system at the end of the day. I get what is happening. Other than thinking, they might have become false when the scheduled time passed. Without having the next event run the else branch of the previous event (or some other complex to remember for future updates), is there a simple way to have the event be true during its time slot and false when the next scheduled event starts. Not a big deal and will only make change if easy and does not require me to fix/maintain some "scheme"in future bacause it works great as is. More of an inquiring minds question.... So ISY programing gurus, is there a simple way?

Thanks.

I've been very busy and have remained with 2.7.15 but have been watching all the great progress. Preparing to update with next "Golden" release. From the post segment quoted above .... Does this mean we will not be able to connect to ISY Consloe via internet ever again or that we must configure for internet access. Regardless, I assume this change will have no impact on products like Conductor (best $7.95 I've ever spent. Hoping for ipdad version someday!)

This is truly a great product and a great firm which means great people. I replaced a bad KeypadLinc that was linked with an overhead light, 4 lamp modules, RemoteLinc, IRLinc, and PLM. It took the ISY 15 minutes to update all links -- the investment in ISY paid for itself by me not having to do all this work manually.

Michel: The PLM is v72. Do the 5011 and 110022 codes listed in above post suggest more about this issue or is this just normal startup behavior? Paul

Michel: I am rebooting it by removing power when I find it locked. Not certain if it has rebooted itself at other times that I did not notice. Thanks, Paul

Following is from HyperTerminal when restarting ISY Starting the Device Starting Device Communications Services Initializing the Driver PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module Waiting 2sec to start 'A' to abort Configured IP = 0.0.0.0 Configured Mask = 0.0.0.0 MAC Address= 00:21:b9:01:01:64 --- Product : (1050) ISY 99i 1024 IR --- Max Nodes & Scenes: 1024 Starting ISY Configuring the File System Loading System Configuration Refreshing Device Configurations Loading Nodes Configuration Starting the Logger Service Starting the Time Services Initializing SSL Services SSL Key Size: 512 SERIAL:Connect: port=0 baud=19200 stop=1 data=8 parity=0 : synch=true pd=3 Starting the Alarms & Notifications Service Retrieving Nodes Starting the Logical Device Updater Service Binding the UPnP Device Starting the Security System Starting the Sheü Please Log in Username: Starting the Device Starting Device Communications Services Initializing the Driver PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-10103 : H_ERROR:-10011 : LOGGER:-10103 : n=[null] c=[null] a=[null] LOGGER:-10011 : n=[null] c=[null] a=[null] Waiting 2sec to start 'A' to abort Configured IP = 0.0.0.0 Configured Mask = 0.0.0.0 MAC Address= 00:21:b9:01:01:64 --- Product : (1050) ISY 99i 1024 IR --- Max Nodes & Scenes: 1024 Starting ISY Configuring the File System Loading System Configuration Refreshing Device Configurations Loading Nodes Configuration Starting the Logger Service Starting the Time Services Initializing SSL Services SSL Key Size: 512 SERIAL:Connect: port=0 baud=19200 stop=1 data=8 parity=0 : synch=true pd=3 Starting the Alarms & Notifications Service Retrieving Nodes Starting the Logical Device Updater Service Binding the UPnP Device Starting the Security System Starting the Sheü Please Log in Username: Starting the Device Starting Device Communications Services Initializing the Driver H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module LOGGER: -2 : n=[13 48 FB 1] c=[ ] a=[ ] H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 LINK: Cannot write high water byte: FF8 : 0 : to device A 34 B9 1 Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-140005 : Net Module Rule: 14 LOGGER:-140005 : n=[null] c=[Net Mod] a=[null] Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-110022 : /CONF/A34B9.REC H_ERROR:-110012 : /CONF/A34B9.REC LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] Log file open failed /LOG/A.LOG H_ERROR:-100002 : LOGGER:-100002 : n=[null] c=[null] a=[null] LOGGER:-100002 : n=[null] c=[null] a=[null] H_ERROR: -2 : [uNKNOWN ] 02 E1 LOGGER: -2 : n=[null] c=[[uNKNOW] a=[null] Installed Modules: 1. (21010) Open Auto-DR 2. (21040) Networking Module H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] H_ERROR:-140005 : Net Module Rule: 1 LOGGER:-140005 : n=[null] c=[Net Mod] a=[null] Password: Authentication failed Please Log in Username: Password: Authentication failed Please Log in Username: Password:Waiting 2sec to start 'A' to abort Configured IP = 0.0.0.0 Configured Mask = 0.0.0.0 MAC Address= 00:21:b9:01:01:64 --- Product : (1050) ISY 99i 1024 IR --- Max Nodes & Scenes: 1024 Starting ISY Configuring the File System Loading System Configuration Refreshing Device Configurations Loading Nodes Configuration Starting the Logger Service Starting the Time Services Initializing SSL Services SSL Key Size: 512 SERIAL:Connect: port=0 baud=19200 stop=1 data=8 parity=0 : synch=true pd=3 Starting the Alarms & Notifications Service Retrieving Nodes Starting the Logical Device Updater Service Binding the UPnP Device Starting the Security System Starting the Sheü Please Log in Username: Starting the Device Starting Device Communications Services Initializing the Driver H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null] PLM: E.D9.1 v72 Starting the SSDP Agent Starting the Secure Web Server Starting Telnet Service Starting Module Services H_ERROR:-110022 : /CONF/ELEC.CFG LOGGER:-110022 : n=[null] c=[/CONF/E] a=[null] H_ERROR:-110022 : /CONF/ADR.CFG LOGGER:-110022 : n=[null] c=[/CONF/A] a=[null] H_ERROR:-110022 : /CONF/FYP.CFG LOGGER:-110022 : n=[null] c=[/CONF/F] a=[null] H_ERROR:-110022 : /CONF/WEB.CFG Starting the Schedule/Trigger Service LOGGER:-110022 : n=[null] c=[/CONF/W] a=[null] Starting IR Query All Devices H_ERROR:-5012 : LOGGER:-5012 : n=[null] c=[null] a=[null] H_ERROR:-5012 : LOGGER:-5012 : n=[null] c=[null] a=[null] UDQPOST: Queue Full: LD H_ERROR:-5012 : H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 . . Many of same repeats removed . H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 LOGGER:-5012 : n=[null] c=[null] a=[null] H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 H_ERROR:-5011 : uuid:00:21:b9:01:01:64,0 LOGGER:-5011 : n=[null] c=[uuid] a=[null] . . Many of same repeats removed . LOGGER:-5011 : n=[null] c=[uuid] a=[null] H_ERROR:-110022 : /CONF/134A6F.REC H_ERROR:-110012 : /CONF/134A6F.REC LOGGER:-110022 : n=[null] c=[/CONF/1] a=[null] LOGGER:-110012 : n=[null] c=[/CONF/1] a=[null]

A couple weeks ago I found that my ISY was locked up. It had not been rebooted in a long time so I restarted it and it worked fine. In last few days, the same problem has occured 5 times. The ISY will not respond to admin console requests, web server requests, or to the HomeSeer plugin. It just locked up and before I could plug in a serial cable to view via RS232 interface we had a power outage .. it restarted and looks okay. What should I look at now or after it locks up again? The error message in the HomeSeer log follows: 8/14/2010 5:40:18 PM ISY Insteon COMM: ISY network communication failed to read message data: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Thanks for the lesson in ISY Event activation and Programming. ...so does this mean that the action 'Set Garage Light on/off' does not run the two programs that are activated by 'is Switched on/off'

I've got a : Program folder with condition "if Garage Light is Off" Program within folder above which says If Motion sensor is switched on Then Set Garage Light on Wait 10 Minutes Set Garage Light off The light never goes off so what am I doing wrong. I've read big debates about program triggers vs condtions so I understand this does not work work like old school programmmer thinks but ....

No. It is not a problem. Only mentioned it because of questions about gigabit switches.

I thought the issue was resolved by a power cycle of the ISY but it still shows up a couple times each day. Here it is directly from the HS log .... 5/17/2010 6:04:04 PM ISY Insteon COMM: ISY configuration failed to get current log level.

Things are going well with 2.7.15 but I saw your question about gigabit switches. I installed one a few weeks ago and now get error reports when homeseer plugin trys to determine the ISY log level. Not a big deal but it did start when I installed gigabit switch.