hart2hart

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.

Great solution and some of the best support and customer service I've seen in many years!

I getting the same results adding a triggerlinc and remotelinc as adding Motion Sensor so appears to be rf device related. When you perform button press on triggerlinc the access point led flashes as expected

This issue still exists. Just added every device from scratch and created scene with same results as 2.7.9 version.

It appears it is only possible to add one device to a scene at a time. Selecting several devices and right clicking to pick add to scene "deselects" all but current device.

I cannot get 2420 motion sensors added using "New Insteon Device" and selecting 2420m as device type. I've factory reset motion sensors but get same error with both: [-200000] failed writing the hightwarer mark[n/a] [-200000]Node not added - failed removing links[11 9A 95 10] Same messsage for other with different address. Motion sensors are 3 feet from access point which is plugged into PLM. Turned off all WIFI.

EDIT:Unless I misread, the following describes the issue and that it is resolved. Should have read a few more posts before typing... http://forum.universal-devices.com/viewtopic.php?t=3785 --------------------------------------------------- I've got a scene with: 3 Switchlinc Dimmers 1 Keypadlinc Dimmer as load 1 button on above kpld 2 IRLinc Devices one on and one off I can set the scene with 100% on with a 30 second ramp and it sets up but setting the keypadlinc button with same settings appears to work until you click another device and and then back to button device and it either shows a very low on level or 100% on and .1 second ramp rate. Ive removed and added devices and the scene and it does not fix.

I have taught IRLinc about 30 IR commands and have linked them successfully to Scenes with lamplincs, switchlincs, and thermostats. Yesterday, I replaced three non-responsive switches. I removed the old switches and added new switches and then included them in scenes. At least one of the scenes included IRLinc Devices. I could see ISY saying it was updating the IRLinc devices as it worked throught the scene setups. Later, I discovered that none of the IRLinc devices were working so I used the restore feature and had some success (a couple still will not respond). Today, I was teaching IRLinc a couple of new IR commands to replace what appears to have "gone bad". In the recent past (using 2.7.9), I would send IR command to teach IRLinc and create link to ISY. I followed this by sending the IR command to confirm learning and linking worked by seeing status of OFF or ON flash on console. However, today, I had to exit ISY console and re enter before pressing remote button would cause state of ON/OFF to appear on console. I then added the IRLinc Devices to scenes and they do not respond. What should I capture in event viewer to help diagnose?

Thanks. I re-read my post and it does have a ring of panic. Really though, I've replaced several switches after working to remove noise and make sure electrical legs were properly joined so I've likely seen the v35 problem without knowing it. In fact I've got two on cross ship with SH now and, yes, they have been great about replacing. My post was to see if I could quickly locate any other switches which may be weak in signal recogition and get them replaced at one time. Back to one of my original questions, does the insteon protocol have a weakenss with the group commands in that you can not confirm that all scene devices responded/get retries on failed SW. SH sure implies it has retry logic etc. Hi Paul, I hope you don't mind that I chime in a bit... Please do not panic because all your switches are v.35, most of them function perfectly. From my conversations with installers it is usually only one or two out of a "houseful" of switches and Smarthome is very good about replacing those. Rand

Is there anyway via physical inspection or testing I can determine if mine were in that "small batch" because I have a house full of v35 SWL that were purchased in a Jan-Feb and April timeframe last year. If I got newer versions, would the group command limitation still exist -- I'd just have SWL that were more "responsive" to commands in general? Thanks, Paul

Thanks. They are v35. Has this been fixed in a later SWL version or is it just a SWL Scene/Group limitation?

Soldered C32 pads on two T1700 using wire end cut from small resistor (make change reversable by clipping small wire). Both reporting 0% humidity and no insteon messages for humidity in 30 minutes. Assuming no unintended effects -- looks good.

I have not looked inside thermostat in a few days so forgive me if this will be obvious when viewing board. Could we get a photo or illustration posted so there can be no mistake which contact points they are referencing? I seem to remember 3 that were close together.