rabbit1543

My versions attached. Hope this helps neje_double.stl neje_single.stl

FWIW i also have the red baseplate on my NEJE. I dont know the size offhand but the template linked above was too small and i had to resort to making my own. I can upload the files later. I believe the model i have is the Neje DK-BL 1000. I can post the redesigned template later for anyone that may need it

I don't have a myq opener. I do have two newer style openers that came with lcd wall mounted openers. They don't support the old doorbell method of control. I was able to get both of my units to work with iolincs by running wires from the iolinc to the LCD panel rather than to opener. I had to open the panel and locate the solder points for the buttons. I was able to piggy back on them and control the opener with my isy. You can try this method before soldering by simply holding the wires to the iolinc on the solder points for the built in switches, then trigger the relaying the iolinc. What this does is trick the opener to think that you are pressing the button on the wall mounted unit. Another alternative is to open up one of the wireless remotes and wire up the iolinc to the remote in the same fashion Polyglot is also a wonderful solution to look into. I'm using for various other integrations with great success. Sent from my Pixel 2 XL using Tapatalk

Please see attached. First is the mention of alexa categories Second is when you send spokens to google home the dialog box says "gome" instead of home Sent from my SM-G920V using Tapatalk

Someguy, Glad you found this useful. I still give most the credit to Belias who came up with the original programs. Without his work I don't think I could have come up with these programs on my own. First, there are two types of leak sensors. Early generations would automatically return to dry if a leak were to dry up while later generations always need to be reset manually after a leak is detected. This is done by making sure the sensor is dry and pressing the button on the top of the sensor. Personally I don't have any of the early generations that would reset on their own so I can't say if or how well this set of programs work with these types of sensors. I would like to think that everything would work fine with the early gen sensor but cant confirm. Considering that these are designed to help mitigate water damage to your home, I highly recommend that everyone test, test and test again. There is alot going on with these programs and one simple mistake in the program can be detrimental if a leak went unnoticed. Sent from my SM-G920V using Tapatalk

Stu This is what I originally had and it worked before I changed out the original contact closures that you already linked to with the new garage kit. The original contact closures allowed for wiring in n/o and n/c while the the new ones only allow for n/c. I'm think I'm going to just try and put the original contact closures back and see if I still run into problems where the the garage would be stuck open while it was actually closed Sent from my SM-G920V using Tapatalk

Larry, I did try this and if memory serves me right it breaks the kpl button integration. Out art least I could not get it to work like I wanted but could be missing something there then also Sent from my SM-G920V using Tapatalk

Thanks again. I haven't pulled the trigger yet, still undecided. My ISY is in the garage and would be within feet of the mimo so I would hope it works without additional zwave devices, but like stu says you won't know until you try it. Sent from my SM-G920V using Tapatalk

Thanks for all of the suggestions and advice. I have been a looking at the fortrezz mimo2+ to replace the two iolincs im currently using for my garage doors. Considering my ISY is also in the garage is it safe to assume that i shouldnt need additional devices t this point to create a mesh like mwareman suggests?

I actually have those for both my garages as part of the original garage kit sold by smarthome. I was running into some problems where they ISY thought the garages were open when they were closed. I was in need for a couple of iolinc for a separate project so i ordered the new kits as which are not as flexible and replaced the contact closures with the new style. When i replaced the contact closures is when i had to enable the trigger reverse. Maybe i will try to put the old contact closures back in and place and see if i still get the occasional false opens. If not i will purchase replacement contact closures. @mwareman I do have the zwave module in my isy but have yet to purchase any zwave components to play with. Is there a zwave setup that you can recommend for this application.

MWareman, Thanks for the response. While this is not the answer i was hoping for it confirms what i am seeing. This brings up another strange behavior then. I have query run at boot enabled which will trigger my Garage OPEN alerts which is based on the "ON" status of a sensor. However the query all that runs nightly does not seem to be triggering this nor do i see the incorrect status after the 3am query all. I have checked and the query all is running nightly according to the summary tab The reason for using the ON status is that im using a KPL button that is configured for "ToggleOn" which is also a controller of a scene that triggers the relay to open/close the garage. This same KPL button is also a responder to another scene that contains the sensor. This setup allows the KPL button to control the control the garage and light up if the garage is open.

Im not sure if this is expected or not but when i query an iolinc that has trigger reverse enabled the sensor (closed) reports as ON when i am expecting to see OFF When i query the iolinc the result of the sensor status is always ON regardless of the physical state of the contact closure Manual trigger of the sensor rectifies this as i would expect. Open sensor = ON Closed sensor = OFF ISY is running 5.0.8

After running some tests i believe i have found the issue and come up with 2 options to fix the missed heartbeat self repair issue. The error lies simply in the else statement of the "Leak Startup Alert" program. I believe that i overlooked a real life test and was simulating missed heartbeats by modifying the variables. While the program worked for startup detection it had a flaw that would repair a missed heartbeat once one was detected. I was trying to minimize the amount of programs needed for this and was trying to initiate the missed heartbeat detection on start and wrongly included this in the else statement of the "Leak Startup Alert" program. I urge anyone that uses the set of programs to run tests of their own to ensure everything is working as expected. Please let me know if you run see any other bugs. Again I apologize for any inconvenience this may have caused anyone. FIX 1 (dirty fix not recommended) This fix assumes that your leak sensors are in working order and will rely on a heartbeat of the sensor which will start the process of missed heartbeat after a reboot. Simply remove the else statement from the Leak Startup Alert program. Missed heartbeat detection will not be started after a reboot of ISY until a heartbeat is received from the leak sensor FIX 2 (best option) Step 1 modify leak startup alert program to look similar to this and enable to "Run At Startup" Leak Startup Alert - [ID 0083][Parent 008A][Run At Startup] If $iStartup is 0 And ( $sLeakHotWaterTank is 1 Or $sLeakDishwasher is 1 Or $sLeakMasterBathSink is 1 Or $sLeakWashingMachine is 1 Or $sLeakHotWaterTankHB is 0 Or $sLeakMasterBathSinkHB is 0 Or $sLeakDishwasherHB is 0 Or $sLeakWashingMachineHB is 0 ) Then Send Notification to 'Default' content 'Leak Sensor Startup Alert' Else - No Actions - (To add one, press 'Action') Enable this to run at startup. If a leak or missed heartbeat is detected at startup an alert will be sent No further notifications will be sent for pre-existing leaks until the devices send a heartbeat status update Step 2 Create new program for ISYstartup as follows and enable "Run At Startup" ISYStartup - [ID 0086][Parent 008A][Run At Startup] If $iStartup is 0 Then Wait 2 minutes $iStartup = 1 Else - No Actions - (To add one, press 'Action') Enable this to run at startup. This will give your ISY time to boot up and prevent false repairs of missed heartbeats at boot Step 3 Create new program to start missed heartbeat detection on bootup and enable "Run At Startup" Leak Startup Heartbeat - [ID 0084][Parent 008A][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 15 seconds Run Program 'HotWaterTank - Heartbeat Missed' (Then Path) Run Program 'Dishwasher - Heartbeat Missed' (Then Path) Run Program 'MasterBathSink - Heartbeat Missed' (Then Path) Run Program 'WashingMachine - Heartbeat Missed' (Then Path) Else - No Actions - (To add one, press 'Action') Enable this to run at startup. This will kick off missed heartbeat detection at ISY start up If a heartbeat is sent the detection restarts otherwise Missed heartbeat will be sent out 25 hours post startup The wait is needed to allow the isy to boot up and populate the variables. Without the wait the startup alert may not contain the information of the leak sensors status Depending on your ISY the wait period may need to be changed but should remain lower that the wait period specified in the ISY startup program

Been doing sime real life tests which unfortunately take time when heartbeats are involved. Hope to have a fix in next few days. Sent from my SM-G920V using Tapatalk

I got my isy back up and running after the power supply failed. I ran some test and there is a bug in this particular program. It was intended to notify you at isy startup if there was a leak or missed heartbeat and the isy had lost power or rebooted during one of these conditions. I had run a test by leading the battery out of one of my sensors and then powered up the isy after it had been off for almost a week. After 24 hours I got two emails. First email was a notification that the heartbeat was missed and the shortly after that it was repaired. I left things as they were for another 24 hours and got the same two emails. While this is not the intended behavior it's didn't appear to be completely broken. Heartbeats are being detected and notifications are being sent but they are self healing when they shouldn't. Im going to muck around a bit see where I went wrong. I'm terribly sorry to anyone using this setup but for now it might make sense to disable the startup program and perform a test of missed heartbeat. Disabling this program should allow everything else to run as intended but you will certainly not have any notification if your isy reboots during a leak or missed heartbeat Sent from my SM-G920V using Tapatalk