hart2hart

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.

I have a scene with 4 SwitchLinc Relays and they are all responders (they are controllers for other scenes). I turn the scene on via ISY console or HomeSeer events through Plugin and all 4 SL show ON status on ISY console page. However one switch is not physically ON so I query it and it returns OFF. In these cases, how is the Insteon retry logic working/not working. The PLM and hence ISY are acting as controller, correct? Should there be error message to say SL did not respond? If I control a single device via ISY and there are comm issues, it will give the status bar and show system busy -- this does not occur in this case. I've deleted scene and devices a couple times but it still occurs.

Thanks for the explanation. I had just created a scene that included a KPL button as a controller and was having issues. Turns out that the Switchlinc is bad. It will not accept any links. Performed all steps reset etc but replaced with spare and it works well.

What would a sympton of this bug look like? I need more detail to understand.

Specifically, could this messsage traffic, if it occurs during the middle of creating a scene etc., cause a problem?

So to be clear, what I'm asking for would be an unlink "IRLinc Device" from the PLM?

Michel: Thanks. Currently, I've moved them to a folder so they don't accidently get selected for scenes and to keep clutter down. Not a big deal but it would be good to get rid of them if possible. Would their slots in the IRLinc be opened to learn other IR commands and create links? Paul

Michel: I've had great success with 2.7.9 -- thanks to you and your staff. However, while adding IRLinc devices, I discovered I was not holding the key on the remote long enough and the device would get added but it is not responsive to future button presses. Can these "bad" devices be removed without having to start over with the IRLinc. At this point, removing one IRLinc device deletes them all. Not Sure if I'm missing a feature or making a feature request? Again Thanks, Paul

I've got two of the t1700 sending these phantom updates. I hadn't fully considered that the protocol may allow configuration of the adapter on which variables to update. In fact, I felt it was odd that the (v1 adapter with t1700) and ISY combination showed a humidity value. I opened a t1700 thermostat and the location for the humidity sensor and the jumper are on the t1700 board. I'll be curious to see if this is a floating ground issue -- would shorting one or both of these locations on the board stop or keep the humidity setting constant? Any EE have a quess?