Here we go. had a 994 for ever . Upgraded to an eisy (5226), running 6.0.4 . Started from scratch, built many porgrams and addd a bunch of zwave

(and some insteon) devices. Ok - were cookin! . Well, not so fast. The machine started freezing, per no schedule, and the ony way to get in it is to pulll th plug

and power it back up. Tallked to Michel, and he has tried to get this fixed. Says a program may have some loop that is causing this, but that is a llittle confusing becuase my programs

are pretty simple, Had toreset the dongle, which of course brought it ack to scratch. Rebuilt all prgorams again (door locks sucked because i'm on acerage and the ony way to program them

is to pull them off the doors and bring them in close to unit. Tried again. Michel says no to upgrade. (yet) . He asked if i have any green icons next to programs. I do have one -

next to a driveway monitor (thought i was clever - put a window alarm switch on a driveway monitor - when someone comes here, sets off a zwave series of chimes we can hear from anywhere

in the house). So, that program does have a green icon next to it. Don't know what hat means. Sent in anoter ticket just a few ago.

ANyone elese have any ideas? Stumpped on what to do.

Toolman

If I'm not mistaken, green means that the program is running. You could try something simple, like disabling that program (right click, disable) and see if that makes a difference. If it does, then that program would need to be examined.

Green is that the conditions for the program are true. It may be running, the Then, or it may have completed the program steps for the Then.

Either way, a solid green means the conditions of the program are true ... and remaining true. So it's going to be hard to give a straight answer without seeing the program and a short description of how it's expected to work.

Another possibility tied with the eisy locking up report is that the program's "Then" has an infinite loop tied with a condition that is always true. Shutting it off, per @Guy Lavoie 's suggestion, will make that apparent. If you disable it, it can't loop and the eisy won't crash.

Edited Friday at 04:12 PM4 days by paulbates

Hey Paul : thanks. i'm what i'll call a "convicted user" still learning about the device and it's programing. I keep looking at this driveway sensor.

Maybe what you said above will help. It has to have certain variables to work - namely "always open" until the drive senses a car or person, then it

signals and the window alarm closes which then eaisy's program notifies some chimes in the house. I'm gonna look at this one again. Thanks for the input.

On 7/2/2026 at 7:49 PM, Palmer marketing said:

Tallked to Michel, and he has tried to get this fixed. Says a program may have some loop that is causing this, but that is a llittle confusing becuase my programs are pretty simple, Toolman

I experienced a lockup as well, first time ever since migrating away from my ISY. It was such an unusual event that I felt Michel should have a look. My programs are pretty straight forward as well. I have mostly Insteon switches and a few of zigbee devices which were added since the migration.

Anyway Michel blamed it on a loop as well.

One thing to watch out for are programs that aren't triggered by external events, such as recalculating a variable value based on it's initial value. That can cause a tight loop.

I'm curious ... how do you tell if the EISY is in a loop? Is there a way to see how much CPU usage it is consuming (like you would with Windows for instance)? I don't believe I've coded a looping situation (yet), so I'm wondering how I would know if I did.

Thanks.

27 minutes ago, IndyUDIuser said:

I'm curious ... how do you tell if the EISY is in a loop? Is there a way to see how much CPU usage it is consuming (like you would with Windows for instance)? I don't believe I've coded a looping situation (yet), so I'm wondering how I would know if I did.

Thanks.

It starts to become sluggish in admin console. You try to edit a variable and nothing seems to happen. You can view cpu activity by accessing it with ssh and run the "top" command.

23 hours ago, Guy Lavoie said:

One thing to watch out for are programs that aren't triggered by external events, such as recalculating a variable value based on it's initial value. That can cause a tight loop.

The only thing I would consider unusual is my use of REST.

I retrieve temp data from an external website and set variables to trigger programs (switches).

I also trigger lights based on motion on BlueIris NVR.

These were never a problem on the ISY.

Thanks for the tip.

I've never used SSH to get into my ISY. Can you give me a quick instruction how?

"CPU Usage" would be a nice feature to put in Admin Console or the new UI version of the console (I forget what it's called).

58 minutes ago, IndyUDIuser said:

Thanks for the tip.

I've never used SSH to get into my ISY. Can you give me a quick instruction how?

"CPU Usage" would be a nice feature to put in Admin Console or the new UI version of the console (I forget what it's called).

From your pc dos prompt:

ssh admin@eisy.local

Or..

ssh admin@<ip address>

Then enter your admin password. The first time it will ask if you want to add the fingerprint, answer yes.

1 hour ago, mmb said:

The only thing I would consider unusual is my use of REST.

I retrieve temp data from an external website and set variables to trigger programs (switches).

I also trigger lights based on motion on BlueIris NVR.

These were never a problem on the ISY.

If you suspect that a calculation program is causing issues, add a statement to wait a couple of seconds, to have it wait a bit between recalculations.