krlaframboise / hubitat Goto Github PK

Any chance this repo could be added to Hubitat Package Manager? I believe this is something you would need to add, but I find HPM very useful in keeping Hubitat apps and drivers up to date. More here: https://hubitatpackagemanager.hubitatcommunity.com

My Aeotec Siren 6 devices started to fire randomly or not at all after Hubitat updated to the Aeotec Siren 6 New device driver. As a last resort before ditching my Siren 6 devices in favor of the Dome siren, I made an attempt to migrate your Aeotec Siren 6 SmartThings device handler to Hubitat: I replaced all instances of physicalgraph with hubitat per instructions on the Hubitat community forum. Although I was expecting Hubitat to throw errors after installing the migrated driver, it worked for me. Another Hubitat user has me for your modified driver, but I wanted to ask your advice and permission on how to proceed. File is attached.
user_driver_scottmil_Aeotec_Siren_6_886.groovy.zip

I'd like to begin by saying thank you for your work on this app for using the Zooz Zen16 as a garage door controller. It is a far better solution than the MyQ system I had been using for several years, and I am thankful for people like you that publish these kinds of solutions for the larger community.

That said, while on vacation this past week, we experienced a situation where our garage doors opened when power was restored after an outage caused by a lightning storm. Thankfully, my neighbors noticed the doors were open (happened late one evening, on the first day of our week long vacation), and texted us to let us know. Unfortunately, the multirelay was in some kind of state that then prevented the openers from responding to either the wall switches or the remote key pad. My neighbors had to disconnect the doors from the openers to manually close them. Upon returning home today, I found that manually cycling the relays on and off restored the control capability.

After experimenting today, it seems that the default state of the parameter "On/Off Status Recovery After Power Failure" which is "Restore Relay States From Before Power Failure" does not work as it describes. The normal state of the relay is 'Off', only toggling 'On' momentarily to trigger an open or close event. My relay was most certainly in the off state when the power went out, so I would have assumed it would resume function in the off state. However, when I unplugged the power to the relay, then plugged it back in, I found that both of my doors opened. This suggests that the relays actually toggle on then off when power is interrupted and then restored.

After changing this parameter to be "Turn All Relays Off", the power interruption no longer triggered the doors to open. Not sure if the app or driver can be updated to override this parameter, or if instructions just need to be provided to users to change that setting. But as the instructions are currently written, step 5 says "Do NOT change any of the advanced setting from the MultiRelay (even the switch input type)." My experience would suggest this is not correct, that it opens a security vulnerability for the user that is highly undesirable.

Hello! Any chance we can have separate delays for opening and closing? Or can we perhaps ignore the delay on manual close? Many put the tilt sensor high on the door which allows quick response when opening the door. However based on existing code, I'm seeing the same delay applied as the door closes, and when the sensor is at the top, this amounts to a 10-15 second delay well after the door is closed.