Bladerunner

I have checked all of those settings. They were good. However, you did say something that caught my eye. Only one connection can be made to the Elk at a time. What all can be connected to the Elk? I am not in Elk's software, nor any other software from my PC. My router certainly isn't involved. That leaves one place to look. Home Assistant. So I went into the devices integrations section and I see an Elk integration, not from the Universal Devices integration but it's own! I am not sure when that integration came about. Seriously. I don't remember ever adding it. Maybe I accepted it one of those mornings at 3am when I decided to update HA and I just accepted it in my half sleep. I like to update HA while the spouse is not aware of changes. So I will have to try shutting down HA and with that see if Eisy gets in as expected. Good thoughts, DennisC! Honestly, this could be it.

December 24th, Michel helped me past the Eisy not coming back online. From that point forward, I don't see the Elk connecting. The settings look good still, and I have made no changes to the Elk. Any ideas? It's still just disconnected. Since it has always worked, I really don't know where else to look other than the settings and IP addresses, all are still good.

I just opened a ticket on mine. I noticed that Elk in Home Assistant nodes were showing unknown. After some investigation, like you I find it connected. I can log into my Elk and it's fine as well. No weird IP changes or anything. Then I notice in Home Assistant, there are two entities (sensors) with the same name but one is under Elkm1 and one is under House Area. The one under House Area no longer works. Seems like something changed in the Eisy update and shifted. However, even after reloading the module in Home Assistant the problem persists. Interested to see how this shakes out. I can reselect all the entities but I don't like the double names in Home Assistant and would rather see it resolved. I hope to hear soon.

I'm not sure if this will help but here's the commands that Michel used to get me out of trouble. "Watch the monitor and then, login using admin (for login) and admin (for password), then issue the following commands. If prompted for password, type admin sudo rm /var/udx/.upgrade_status sudo rm /var/udx/.udx_install_cleanup sudo dhclient re0 sudo service udx restart Please send me a picture." I second that. I can't believe that Michel got back with me on Christmas eve. I expected to wait until after Christmas. It isn't just the device, it's the support behind it.

Every time I make a change, I back it up. At least I am good about that. I should keep a USB drive ready too.

LOL, neither have I. With all the interaction between the Eisy and other devices, it has been just running. I do updates on devices, etc and always gen a backup. When we lived with my dad caring for him for 11 months in another city, I was able to access Eisy and use it to make our house look lived in, and check on house heat/cooling, etc. I still find that pretty remarkable. A monitor mount is on its way from Amazon. It will stay there and there will be ready.

I should mention. I don't know why but in Home Assistant, all of the helpers that I created to convert switches to lights were gone. I had to recreate them.

Oberkc, Yeah my usual would be unplug and plug it back in. I did try that at first but nothing worked. The blue light was lit so the box was operational just not in a usable state. Michel had me connect up the monitor and keyboard and press the power off and then back on. That final screen gave him enough info to help me. The 994i and the eisy have been so reliable that I really don't mess with it at all. I use the java interface to code devices etc and backup, and UD Mobile to activate lights manually when I need to.

I wasn't able to get to eisy at all. No network connect. I created a ticket and Michel responded! I didn't expect that, it's Christmas Eve. I dug up a monitor and keyboard and he gave me the entries to complete what appeared to be an incomplete update. It's back up and running. Thank you Michel! I'm not sure why it was updating but it appeared to have started one. And it had gotten to a couple of hours so it wasn't a completed update. I first noticed it when I finished a brisket in the smoker at 5am and walked up to the back door with a hot brisket in my hands and the lights didn't turn on. There will now be a monitor, keyboard, and mouse mounted in my network/home automation area and with KVMs to systems.

I had not updated my Eisy yet. Yes, I am very late on that. Family things and house things needed fixing and Eisy was working just fine. So tonight, I noticed some things not working. They are through the Eisy. Usually, this is just the Eisy losing connection to HA and HA can't turn on a light when I attempt a voice command. As I checked the Eisy, it says it is updating. And that update never finishes. So it's no longer available, it still has a nice blue on/off button on the front though. I did just open a ticket. Any ideas how to proceed? A wiki that I haven't found or just wait for a ticket response? This kills a lot of stuff in my house. Eisy is integral.

i recently replaced an older X10 Pro inline device with a new Insteon inline device. So, the definition in Eisy is wrong for that device. It still sees it as an X10 device. Is there any way to replace a device in Eisy with its new configuration? I only see where you can set the device type as you enter a new device. If an Insteon device is set to issue an X10 command, does it not act or identify as an Insteon device? I have several Insteon devices that are set to issue X10 as that was the basis in my old Homeseer system. These all should be changed to the appropriate Insteon device.

After a session where I went into PG3 and looked at ELK where it reported no nodes (not sure why), I went ahead and shutdown Eisy and restarted. When all came back up, ELK reporting 38 nodes instead of the 39 I had seen earlier. The only thing Jim could conclude was that when I had switched the light setting to NONE, it reduced a node. My guess, my assumption, is that my incorrect setting caused issues. That exterior battery powered motion sensor was the highest number in my connected sensors. It is also possible, I am guessing, that my batteries could have been weak in that sensor. So after switching out the batteries and setting that variable in ELK correctly, the exterior motion sensor is reporting correctly. It even reports the opening of the sensor as OPEN and Violated vs SHRT and Violated. So, it's corrected now and Eisy will turn on the back porch light when it sees the motion sensor violated as it should. Small steps...... Happy to finally be off the ISY994i to get things moving. I hated to leave it as it was totally solid but having UD Mobile and more options is great in Eisy. Thanks, Jim, for your support!

I did just try my shed sensor. It is the same Elk Two Way wireless tech as the basis of the motion sensor. It however, does reflect the violation. The mystery deepens!

@kzboray There's communication. I can see other sensors go from normal to violated as expected. And quickly. Impressive. I can even set the alarm to stay mode through UD Mobile, and also set my RCS thermostat attached to my Elk. It seems there's something odd about this sensor state. It is the only wireless motion sensor I have. It is on the Elk two way wireless protocol.

Jim, log sent. There are references to zone_35 which is the zone in question.