Bladerunner

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?

I am considering using the Aotec Nano Dimmer and Switch. I primarily wanted to use them as in box controllers with no switches. However, they seem appropriate to use with wall switches as well. However, I have read some bad things on their swipe plate. Has anyone found a great slim double throw momentary that doesn't take up too much room in the box and leaves space for the Nano? Any input appreciated. I have googled but not found a home acceptable switch for this.

I'm brand new here. I have previously lived in the Homeseer world since it's start. I have mostly still X10. So my programs set several X10 lights off. I have some waits in between these X10 commands. At the end of the program, I have the Elk speak "Done". However, the Elk "Done" comes out quickly and the X10 commands are still executing. Is there a way to make the program wait until the X10 command is complete? Thanks.