Hi @RBoy
I have a pretty cool setup for my home alarm through smartthings, but to be perfectly honest I did find it quite problematic to get set up.
One of the main components is @arnb’s SHM Delay, which works wonderfully - allows the system to be put into Armed mode with an audible beeper whilst the system gives enough time for the user to exit/enter without firing the alarm (stupid miss from the original Samsung SHM).
Over time I’ve got this set up pretty much the way I want it. The issue is that to have done that, I have a combination of smartlighting rules, routines and even a bit of webcore all hacked together to keep things right.
I did try to simplify things down by moving as much as possible to webcore (for neatness) , but found that the cloud based aspects meant that it was too damn laggy. For example, I have a cheap Rfid keypad with simple NO & NC connections to a fibaro UBS. Pressing a button on the keypad opens a contact on the Fib, and a smartlighting rule sets the system to armed. Pressing on a Rfid tag closes a contact, and sets the system to disarmed.
Various smartlighting rules and routines are in use to ensure that certain virtual and physical switches are flicked to the correct position when the mode changes, and I’ve found this all pretty much worked beautifully. But it was a lot of hassle and time/effort to set up to ensure that everything stays ‘synced’.
One problem was due to cloud delays which meant that say, you armed the alarm, and then realised you weren’t actually ready to leave, so you disarmed it. But maybe by that point a routine was part way through firing or whatever, and basically, the sync would get lost (eg. ShM would show as disarmed, but my motion lights were still disabled… A routine just wasn’t completing in full).
Attempting to swap entirely to webcore just exasperated these delays. Unusable.
The current set up seems to be pretty much faultless relying heavily on (local) virtual/physical switches and (minimal) routines with more complex smartlighting rules which seems to be the most robust way of dealing with things. For whatever reason. Webcore pistons just don’t cut it, or take far too long to react due to cloud. Might only be 5-10 seconds, but that’s a lifetime when you’re just trying to exit or enter and you don’t want to stand there wondering if your button press has actually registered, so to speak.
I’m a little concerned about the complexity and the reproducibility of what I’ve made. If the hub happened to die, I’d really struggle to set this up from scratch without some serious note taking prior. Not ideal for any system. Also, the new app won’t have routines and I’d like to know that whatever I set up now, will keep working.
Would you recommend this app to replace my setup? Cheers.!