I have an issue that has been plaguing me for months and I have run out of ideas on how to approach this to try and solve the problem. I have a modest size condo single floor for the most part, about 1200 square feet, I have about 35 switches/dimmers, and probably 12 or so outlet plugins, dimmer outlets, a few shelly products and some others, homeseer hsm plugin etc. I also have about 8 battery motions, and several battery door sensors, and probably about 10 battery water sensors and 2 older kwikset locks. I started with an Eisy and am now on an eisy r2. A few of the switches are quite old and I have replaced the majority of them to newer models so I'm not inclined to think that is the issue.

So what happens is at times things will become very delayed, specifically with the motion devices. You walk into the room which has a motion switch and it may take 10 seconds to come on sometimes even longer, other times it is so fast (which is what I want). I can see the motion pick me up but the program to turn on the light doesn't always trigger right away. I can walk through multiple rooms and they can all exhibit the same behavior, then all of the sudden its like the bottleneck is gone and they all turn on. I also have some zooz scene dimmers and even those buttons do not always activate immediately, other times it's perfect, so I am down to only 2 possible ideas. I have a signal/interference issue, or something behind the scenes in the eisy is taking up processing time, be it the OS of the box itself or something in eisy's programming. I have repeaters, I have tried healing the network many times, my eisy is in the center of the condo. There is no specific times that it tends to be slow its very random.

I initially thought it was the battery motion sensors just not being strong enough so I swapped out key areas with the Zooz Zen12 motion dimmer. I have it change the parameter at night so it does not activate when the cats are milling around and in the morning I switch it back to activating (via a program) but alas I still have the same issue. I thought maybe my first eisy was not robust enough so I had a second eisy-r2 I was going to put at my office but instead decided to use it here to solve this problem. I backed up the eisy. Took the restore files and restored the new eisy-r2. I thought everything was great but once again the delays started occurring. I do love these new switches btw!

( As a side NOTE on the restore of the new eisy, after restore it would not recognize any of my zwave devices until I took the zwave/zmatter dongle off the old eisy and used it on the new one. So how would one restore all their devices if they had to replace the zwave dongle??? The backup is somehow tied specifically to that controller. The last thing I wanted to do was start from scratch and have to redetect each device and then rewrite all my programs which I have done previously over the years. )

So here I am not sure what my next step would be aside from starting from scratch. I've looked at the different logs and honestly they are so cryptic and hard to read that they are of little help. Just looking for some ideas as to what I should try next. I'm very close to starting all over but dreading that option, it will take months to get everything back the way I want it

Just a little background, I am an electrician so installing devices is a snap. I am very familiar with UD products. I had a 994 pro many years ago and then when insteon was heading out and zwave was taking over I had switched out to homeseer,software and then later their version of the pi. Eventually I got fed up with their product when on 3 separate occasions the box wouldn't load up their interface and it was just wiped. I suspect it was something with writing their "events" (programs) and it would cause some sort of corruption so I switched back over to UD and the eisy. Each system has it strengths and weaknesses so I wouldn't pick one over the other. I am glad to see them switching out the java to a more web based system so you can edit this stuff almost anywhere.

Are all your devices zwave, or do you also have Insteon (especially in your initial list of "about 35 switches/dimmers, and probably 12 or so outlet plugins", and various battery sensors? If you have a mix of technologies, that might help in getting an idea if it's a communications issue or the controller itself. If you do have Insteon, are there any pending writes (little red wave icons beside some devices in admin console)? That can slow things down while updates are being attempted. Another Insteon communications issue hint is direct commands between devices, like scenes triggered from a switch or keypad. If those are sometimes slow, then there might be a problem there. If both insteon and zwave become slow at the same time, then it does sound more like a controller issue. A tight loop in a program can be hard to find.

Thanks for the response Guy, There are no insteon devices anymore. Everything is zwave. I have a very small handful of old zwave devices from many years ago, which would not be long range. I've been eliminated them as needed. I can only think of maybe 3 of these switches left. The majority of my stuff is Zooz Products. They seem to be more on top of it than some of the others as far as feature rich products. I even have a few relay modules for my fish tank.

If using beta repo for upgrades I would first verify the issue, is the status slow to update or is the program scene slow to execute. Open the event viewer on you phone before you walk into a room if the status change immediately and there is a delay then investigate that path. If status does not update immediately then investigate that path.

For the latter, try removing the devices and specify long range (only available in beta) during inclusion.

An alternative, if both devices support local linking add both as mesh in a scene (although this may cause other issues depending on your setup).