HoustonFirefox
Active Member
Hi All,
I've been scratching my head on this one and can't figure it out:
I have about 5 people who have access codes to disarm my Elk M1.
Currently, if ANYONE disarms the system then my Elk sends a text message to my cell phone as well as an email message to my work.
Ideally, I would like to write a rule that if anyone OTHER THAN MYSELF disarms the system then send me an email.
I know I can write an individual rule for each user but that takes up space on the Elk and is a PITA to manage in the current rules editor.
If the Elk people could figure out how to program correctly they would have added a NOT operator in the rules programming: i.e; WHENEVER system is disarmed and Last User was NOT Administrator THEN Send Email Message.
I work with Microprocessors for a living (at the machine-code level) and have been doing so since 1976. EVERY processor since then has the NOT operator built in (and an OR operator as well!). Why Elk can't figure out how to put this into the system is beyond me. I would suggest firing (or demoting) the current programmer and getting someone in there that knows how to program on something other than a beginner level.
My apologies for venting , but this is frustrating as heck only because it is such a simple thing to include.
Heck, while I'm at it, would it be so hard for Elk to put on thier website what features are being expected in the next release of firmware or software? It wouldn't have to be written in stone but at least would give us faithful customers something to look forward to.
Regards,
Hobbled Elk in Houston
I've been scratching my head on this one and can't figure it out:
I have about 5 people who have access codes to disarm my Elk M1.
Currently, if ANYONE disarms the system then my Elk sends a text message to my cell phone as well as an email message to my work.
Ideally, I would like to write a rule that if anyone OTHER THAN MYSELF disarms the system then send me an email.
I know I can write an individual rule for each user but that takes up space on the Elk and is a PITA to manage in the current rules editor.
If the Elk people could figure out how to program correctly they would have added a NOT operator in the rules programming: i.e; WHENEVER system is disarmed and Last User was NOT Administrator THEN Send Email Message.
I work with Microprocessors for a living (at the machine-code level) and have been doing so since 1976. EVERY processor since then has the NOT operator built in (and an OR operator as well!). Why Elk can't figure out how to put this into the system is beyond me. I would suggest firing (or demoting) the current programmer and getting someone in there that knows how to program on something other than a beginner level.
My apologies for venting , but this is frustrating as heck only because it is such a simple thing to include.
Heck, while I'm at it, would it be so hard for Elk to put on thier website what features are being expected in the next release of firmware or software? It wouldn't have to be written in stone but at least would give us faithful customers something to look forward to.
Regards,
Hobbled Elk in Houston