Bladerunner

After Z-Wave removing the devices in Eisy, I then went over to HA. I attempted to delete the devices but it said they couldn't be found. So, it seems that they were gone but that the devices were not removed from the integration. So all is well it seems. I guess.....

Well it was Z-Wave and I didn't remove them via the Z-Wave menu. I went back and removed then via that menu options allowing Eisy to remove them. Tried a reboot of Ha and it still shows them. Will keep trying.....

Interesting. I did a full HA reboot and I still see those devices.

I removed some devices from Eisy. I then went over to HA and reloaded the Universal Devices integration, expecting the devices to be gone. They were not. I thought that reloading the integration would cause the Eisy to be queried and only the existing devices/entities would be there. Do I have to remove those devices manually?

Yeah, I need to learn a lot more before I start getting this deep. I'm a whole 4 days into my Home Assistant adventure on a new Yellow. Getting this up and running wasn't bad, now it's how deep is the lake. And it seems pretty deep. I just went through the migration from ISY994i to the Eisy. And I love that the Elk M1 I installed communicates with my serial RCS thermostat and Eisy and now can be front ended with HA as well as UD Mobile. I used Homeseer on Windows with a non communicating Ademco alarm panel not long ago. I had to get off Windows on to dedicated platforms before I lost my mind. The whole goal for HA is to build a simple dashboard that fits my wife's needs that can be on her phone.

That link was great to actually see the template code. I have not, however, in HA been able to find that template code and pull it up to mess with it. How do you get to the template code in HA? I'm trying to watch vids and learn but it's vast topic. I have several things in Eisy that I would like to use and I can see that I need to create some states of things that make them more usable in HA. I see references to templates but I cannot find where to get to the actual code. It's a pain starting in something completely new.

I like your dashboard. I was a computer systems engineer and data architect for my career. Suits me fine. And thanks for the template tip! HOWEVER, I am married to a very analog human. They can be hard to interface with even in simple vocal communication so I am looking for a much simpler version of a dashboard for her. Something reminiscent of the car dashboard with simple indicator lights and a few buttons. I know she occasionally looks at the big dial with the needle as she comments about it when I'm driving but those little gauges showing coolant temp, battery, etc. not so much. She REALLY dislikes that I enter addresses in the GPS with latitude and longitude. Kidding aside, I actually have changed things around in the house so I could get to Home Assistant just so I could build more usable dashboards for her. I have two Fire tablets that will be getting reused for this with Fully Kiosk. Now I just have to learn the HA ecosystem. There's a lot there. I was previously on Homeseer and ISY994i so this is quite a change.

Thanks, I did not see an Elk integration in the store so I didn't think one existed. I installed it in HA and it does work. The only issue seems to be that it needs a code entered to arm the system. Not sure why as I don't need it on the Elk keypads or on the UD Mobile interface. I wasn't sure how to edit the cards yet, that's how new I am in HA. Maybe it's possible to set an arming code in HA YAML. I was actually trying to use the Elk devices from the Eisy but I didn't see how to get that one going. I really need to read more on that UDI interface. I hope to build a simple dashboard that my wife can use just for what's important. That's that got HA into the mix.

I have my Home Assistant Yellow up and running. I have it using the UDI integration. This took more time than expected but got it done. I'm glad I already had the Eisy in place and fully migrated from the ISY994i. I can see my Eisy devices. I see the Elk Connector and I can see the device Home Alarm. The Home Alarm has several variables that include the alarm state and armed state, etc. These are well represented in UD Mobile and I have been able to arm the system. Works well. Has anyone added the Elk alarm to a Home Assistant dashboard, including buttons to arm/disarm/status etc? I would appreciate any info or examples. I have a LOT to learn about the HA and its terminology. I'm developing an appreciation for all those nice HA dashboards I see on Youtube! I want to be able to build a simple dashboard for my wife that allows her to control those things important to her and simple to use.

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.

I have just migrated to Eisy and loaded the ELK plugin. Working through issues so I can get to using Elk M1 sensors in statements in Eisy. The unit is the https://elk-datasheets.s3.amazonaws.com/ELK-6032-Data-+Sheet.pdf It worked well in my ISY994i where I used it to turn on my back patio light. In the M1 status window, it will show violated. It reports EOLR normally and then Shorted when violated. No voltage report. However, in the ELK plugin there is no reaction. The board in the Optex sensor is an Elk two way transmitter. This is the Elk two way wireless system. I tried setting the Send On to Short but that made no difference. Just a guess, I'm too new to Eisy and the plugin, Has anyone had a sensor not respond and corrected?