PalChgo

I will try that, which log is the most pertinent one that I should be looking at.

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.

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.

I have the kwikset locks also they are very finicky when trying to add them. I messed with them for a long time. It's been some time but if I recall I had to have it "unlocked" in order to get them added. Maybe that was the secret to getting them added maybe it wasn't. Glad you got them to work

Hey hey, you got it! Thank you so much!! Now I can start playing with it.

No, this is the first time I have tried using Nvremote and the Eisy for the Nvidia so this part is all new to me. I'm migrating off of Homeseer. I had a 994 back when Insteon was still around and I had switched out my controller and devices. I will turn on debugging next but might not get to revisit this till next weekend.

So I found how to turn the developer option on in the Nvidia, I also rebooted the Nvidia just to be sure. I did not see any options in the developer tools for authorized users that you thought might be an issue. This is the first time I'm trying to use the nvidia in this way, anyhow I removed and reinstalled AVR, Clicked the add Nvidia in the config screen and inputted my ip address. When I look at the log I do see a connection refused, see below for a snippit. If it's refusing the connection it makes me think the port of 5555 is not right or its just not turned on in the Nvidia, Not sure if this is a good test but I also tried telnetting from the dos command prompt to the port and I was getting a connection refused.. Just one note I do keep getting a notification that version 2.07 I stop it, update and then restart it and it keeps going back to 2.015. Could this possibly be part of the issue? File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 678, in _sock_connect_cb File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 678, in _sock_connect_cb raise OSError(err, f'Connect call failed {address}') raise OSError(err, f'Connect call failed {address}') ConnectionRefusedError: [Errno 61] Connect call failed ('10.0.0.189', 5555) ConnectionRefusedError: [Errno 61] Connect call failed ('10.0.0.189', 5555) 2025-07-13 09:08:59.771 Command udi_interface ERROR remotedevice:execute_command: Error sending command to Inputs 2025-07-13 09:08:59.771 Command udi_interface ERROR remotedevice:execute_command: Error sending command to Inputs Traceback (most recent call last): Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b902713e_5/poly/remotedevice.py", line 75, in execute_command File "/var/polyglot/pg3/ns/0021b902713e_5/poly/remotedevice.py", line 75, in execute_command self.device_driver.execute_command(self.prefix + command['cmd'] + self.suffix, command.get('value')) self.device_driver.execute_command(self.prefix + command['cmd'] + self.suffix, command.get('value')) File "/var/polyglot/pg3/ns/0021b902713e_5/drivers/base_driver.py", line 112, in execute_command File "/var/polyglot/pg3/ns/0021b902713e_5/drivers/base_driver.py", line 112, in execute_command result['output'] = self.send_command_raw(command_name, command, args) result['output'] = self.send_command_raw(command_name, command, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

That would make sense. I've never seen where I would set something like that in the nvidia. I'm searching for it now. I'll report back as to what I come up with.

Hi, I'm trying to get my Nvidia shield installed on the eisy. I've installed AVremote and it added it to the admin console. I don't remember my sequence of events as I've been working on this off and on for a few days. In my device list nvidia, navigation, audio, etc,,, showed up along with all my other devices. But it shows that it is not online "False" I've seen the new options also listed in the avremote polyglot interface and I just messed around with different things to get this to work to no avail. I've tried uninstalling avremote and starting over a few times. So what I am asking for is a sequence of events on how to try and get it installed correctly, assuming I will start fresh by uninstalling AVremote and deleting the Nvidia and its counterparts in my device list on the eisy and rebooting it. I have my ip address of nvidia at 10.0.0.189. I can access that via my phone app with no problems. Thanks!

Yeah I did put in new batteries and even went so far as to be a few feet from the eisy when I tried the linking. It's really strange that I can't get these items to link. I've turned on compatibility mode, security mode off, basically anything I could find in the eisy setup that maybe might make a difference. The only thing that makes these different than maybe some other devices is that they can be used as a controller, but going through the instructions I don't see any special instructions for linking when it's not used as a controller. I haven't given up just yet It could be something really simply stupid but it's escaping me what that is. I may reach out to support and see if they have any ideas, it certainly couldn't hurt.

I have all devices cleaned up and responding as expected. I tried factory resetting and then linked them again but each time it's the same issue, but what's odd to me is both of them exhibit the exact same issue. But if I use a different hub (HS4) it does work as expected so could there be some sort of bug in eisy? Overall I am quite happy with the device, I used to have an isy994 many years ago so I am familiar with how it works. I did buy a few zooz dimmer keypads and the repeater so just waiting for that stuff to get here so I can swap a few older ones out that are switch only devices.

Thanks for the info. My only guess is perhaps eisy is not picking up or interpreting something in the interview to create the items it needs. A may need UD's help on that as I know it works with other platforms. When adding those keypads I went as far as laying the device on top of the eisy All those other devices devices are battery only devices. I've queued them up to update but it hasn't occurred yet. I can't say I've had any real delays on stuff happening but I do want it to run smooth so I'll look at the sale, there might be something else I want

There's almost nothing on the screen to really interact with. From my understanding this can be a controller and you can link other devices to it, or at least that's how I read the instructions but in homeseer I could always detect a button press or a hold down or a fast on etc. and was able to set an interaction based on that. I bought these a really long time ago but there is no support for them that I'm aware of. I do have a switch close to my tank and I'm thinking about putting a zooz zen32 switch in its place. That will at least allow me to get some special buttons back to use with my tank. I'm surprised no one has a good keypad only option for Zwave either AC power or a handheld like this one. Eaton made one and I had a few of those but there was always something lacking with them and I had a hard time to get them to work reliably. Thanks for that reminder on the backing up of Zwave devices, homeseer also had that same issue that you had to back up the zwave stuff separately and I got burned on a restore once and had to start from scratch. When doing a backup maybe they should have a popup to warn you to also back that up and have it included in the zip you download so you have the most current information for the restore. It was a real let down that the backup wasn't all there. It's literally an entire day pissed away having to relearn the devices and then fix the events/programs.

Those are different devices, Not sure why they haven't finished with writing. I like that idea of moving the other stuff out of the main into another folder. It is way to crowded and hard to find stuff. I'm gonna keep plugging away on this, sooner or later I'll get these things working or find a different keypad option.

Yes I am using the usb board that UD recommended. Everything is working fine so far. The 2 kwikset 916 locks took some work but I finally got through that. It only creates those 2 items at the bottom left. So all I can select in the events is like a battery query or a device responding. It should allow me to pick any of the 8 buttons dependiing on how I push the buttons but those options just don't show up. I have 2 of these and they both do the same thing. I've tried reinterviewing and switching compatibility mode.