Code positions are irrelevant to the overall function, just indexes in the list - so they must be unique for each code you want to use, or it will overwrite the previously stored code at that index. The same code can be used for all functions - just enter the programmed code, then press the desired arming mode button.
Also compatible with the built-in Lock Code Manager app - if you already have locks integrated and use this to add/remove codes
Since the update my siren is now silent when triggered (the red led does flash though). I've tried setting it to a few different levels between 1-10 and I click 'configure' and then 'save' but it's still stilent. Anyone else having this issue or know what's wrong?
I tried that a few times with a few different number between 1-10 but it doesn't work. The 'state' on the right hand side of the screen updates but the keypad is still silent when manually triggering the alarm (although the red LED flashes).
This switch needs a disclaimer. When HSM is armed and a contact sensor is tripped, HSM goes into intrusion-delay. during that, all you have to do is press the "arm home" or "arm away" button - HSM will forget that it's in intrusion-delay and just re-arm. so someone broke in your house, and cancelled the alarm by just pressing a button.
I just tried again a few times, ensuring I hit off between tests and also trying at a few different volume levels but still no sound. Any ideas what I can try next? Here are the logs:
Strobe works (when triggered with 'siren' button and also when triggered with 'strobe' button
The speaker on the keypad works and it can make sounds. I'm probably not going to trigger the siren as an alarm event anyway - and use text notifications, lights and maybe speakers instead. So please don't spend any more time trying to problem solve unless other people start running into the same issue.
I should have said this in the first post; thanks for all your efforts on this driver - it's brilliant!
Thanks, sorry I get that part working for you. I would try removing the keypad, factory reset it and add it back in. At least you know then that it's a clean slate.
@bptworld I'm seeing the user name and code exposed as "debug" logging with the current version of the driver. Is this intended or left over from some testing? I do have debugging turned off.