AD8BC

Hi Michel, Should I try the .14b to see if it solved my .13b problems?

Gotcha, thanks Michel, I'll wait!

That depends, I'm a little behind the times here... what would constitute i1 only mode? I never ever had problems with the PLM locking up. Maybe this weekend I'll try to reload the .13 firmware and see if I can replicate the problems again.

Sure Michel, it comes up v52.

Well, Michel, version .8 has been running reliably since last Thursday. All statuses seem to be reporting just fine to the ISY (with the exception of the motion sensor, I may have to re-install it into the ISY.

Michel, Unfortunately, with the exception of the one new Icon relay switch, two Icon lamplinks (that have been running fine) and the motion sensor, the rest of the items on my network that I have been having difficulty with are 14-20 months old, unless the new items are somehow corrupting communications with the old ones. This morning everything seems to be running well since I manually ran the "Query All" last night, with the exception that my motion sensor doesn't seem to be reporting to the ISY -- could this be because I went from .13b to .8? I'll play a little more after work this evening. Thanks for your help! Oh, what did you mean by how long more on my 30 day? -- Bill

It has gotten more interesting. I downgraded back to 2.6.8... Same issues. But I did some further poking around... It still did not reliably hear when devices turned ON. But it always heard FAST ON, OFF, FAST OFF. But here's the kicker -- in some cases, on the affected devices that are dimmers, I could not use the ON command from the Administrative Console... If the light was ON at any level, clicking on ON would turn the unit OFF. Then, after doing a REFRESH ALL, everything seems to work again.

Well since I got back home from vacation I have been doing a little playing around. I still have the same issue with my new Icon Relay switch for the bedroom closet. When I turn it on locally, the status does not change in the ISY. However, it always seems to recognize a Fast ON and I think it recognizes an ON after that. Or, the same old Query Device works and then it will also recognize the Local ON after that for a time. I also seem to have an issue with at least three other switches... two SWLs and one KPL. And with these it's not always a local ON that isn't recognized... it's sometimes a remote group ON that will do it. I know I have a problem because I have a group that illuminates a KPL LED when any inside light is on (uses an ISY program). Sometimes when one of these lights is turned ON the progam won't run because it won't get the status. And this all seemed to noticeably happen after upgrading to .13. I loaded the beta after having issues with .11 and my motion sensor... I'm at work now but I'll get rev levels of the devices I am having difficulty with tonight or tomorrow.

Thanks Michel! And be sure to take time to enjoy the holiday! I'll be back home in a week and then I can do some troubleshooting for you.

Michel, if I weren't getting ready to catch a plane, I'd go take it out of the wall and look I can tell you it's an Icon, one of the ones that they just discontinued. If this helps, it shows up in the ISY as a (2876S) Icon On/Off Switch v.35 -- this may mesh with the SL v.35 problem you mentioned.

No I didn't check the log, I watched the device directly on the screen. I'll update the firmware after I get back home from Christmas vacation and give it a shot.... Thanks!

I recently installed a new Insteon motion sensor in our big closet, and an Icon relay switch on the closet light. I wrote a program in my ISY-26 that operates like this: When the switch is manually turned ON, and the motion sensor is OFF then it waits one minute and turns off the switch. That way if someone walks into the closet with the light on, it resets the timer. It works great... EXCEPT... sometimes, when the switch is turned ON the ISY doesn't see it turn ON. I can sit there sometimes and cycle the switch over and over and the status won't change. If I do a manual query on the device, or do a manual query on everything, afterwards it seems to work perfectly for hours. I first noticed this after I installed 2.6.11 (my existing revision didn't have a motion sensor option) and saw that many people were having some similar issues so I installed 2.6.12 beta and it all went away except for this new Icon. Anybody have any more ideas?

I concur. Programming is just so darned easy with the ISY, start from scratch, you might even enjoy it!

Mine did the same thing. My outdoor lights didn't come on 20 mins before sunrise or turn off 20 mins after sunrise -- they were still dim at 8:00 AM (they dim at midnight)... so the morning timers didn't run at sunrise when the ISY thought that it was March 1. At 7:45 AM I synced the date to the computer and my evening timers didn't run at sunset when it thought it was February 29. We'll have to see what happens in the morning..... A leap year bug is hard to catch in testing, so I'll let this one slide Thanks Michel! -- Bill Cahill

I had a weird anomaly with one of my KPLs. But it went away after I re-downloaded the link tables from the ISY. Try restoring that device. If not, try to see what does turn it on and restore that device.

Michel, this is the kind of product engineering that they don't teach you in college. Great idea!

Red-Bull, man!!!!!! Seriously.... There are only two people in the world that I would truly want to work for..... Glenn Beck and his radio show (although I have neither the talent nor the comedic wit to actually make that happen), and.... UDI, but that would mean that I would need to move to California.... and I could never afford that. Kudos to Michel and staff. I have never, ever seen such great and fast customer service.

You know, I had been meaning to bring that suggestion over to this thread.... Remember that old X10 alarm clock that would send X10 commands to a specific address at a specific time? Would be great if UDI created a networked alarm clock that would send updated alarm times as variables to the ISY over the Ethernet connection. You could write specific programs and then enable/disable/set the time for each one remotely.....

Thanks Chris! I never thought of doing it that way.

Here is what I would be interested in. If I run a program, I would like to be able to call another program and run the "Then" or the "Else" based on the "If" of the secondary program... In other words, have programs that only run if called by other programs. Right now, it seems that if a program calls another program, it immediately runs the "Then"

I don't know if this is correct... but while watching the indicator lights on the PLM and the Access Point, it looks like one command is sent when the dim or bright button is first pushed, and one more is sent when it is let go--like a "start dim" and a "stop dim" command.... does anybody know if I am right?

For some reason, on an ISY reboot it seems that some of my programs run. Doesn't look like they are supposed to but I haven't done enough troubleshooting to ask Michel yet.

I was trying to telnet into my ISY and was having difficulties with Windows Vista not knowing how to Telnet. Turns out telnetting is disabled by default in Vista. Here is an excellent place to learn how to turn it on: http://www.windowsitpro.com/Article/Art ... 93952.html

Jeez. I had to do it too. Far out man.

That answers my question! Turns out I have lots more links available.