OK, is it just me or is the ELK a tad finicky about rules order of events, timing etc. I admit I am used to PLC programming with a full range of Boolean logic, but now that I am getting close to having all my expanders / devices in, and getting a bit deeper into the rules woods, it seems I have to fudge around a bit to keep the ELK happy.
Also just a couple of things I have noticed that perhaps others have run across / worked around:
1) I can't get the system to switch arm modes consistently with rules, unless I disarm within the rules first. Anyone have rules that are doing this successfully?
2) When I disable a rule in RP, anytime I connect again, RP shows conflicts. This is more just a note, as I now have figured out that the rule is actually removed from the control. I made a new account connected and downloaded the rules and found the "disabled" ones missing, since I couldn't figure out why it found conflicts right after sending the rules all the time.
3) In RP, I am using a FOB, and wanted to create a user that matched the FOB ID, just so I could add a name to it so it was more easily found in the log. If I add a new user and tick the checkbox that they have a FOB, the code box is set all zeros, I save the user, switch to another user or any other screen in RP, and then return to the just created user, the FOB checkbox is un-ticked. Now the control will log with the named user correctly, but a conflict gets reported every time because it reverts back to unchecked. Obviously if you make other changes and send to the control this user will be uploaded incorrectly. Am I missing something?
I will post some more items here in the coming weeks to see if anyone has ideas on streamlining my rules, and to document a couple items I have done. Nothing ground breaking, but hoping to give a little back to where I have learned much.
Also just a couple of things I have noticed that perhaps others have run across / worked around:
1) I can't get the system to switch arm modes consistently with rules, unless I disarm within the rules first. Anyone have rules that are doing this successfully?
2) When I disable a rule in RP, anytime I connect again, RP shows conflicts. This is more just a note, as I now have figured out that the rule is actually removed from the control. I made a new account connected and downloaded the rules and found the "disabled" ones missing, since I couldn't figure out why it found conflicts right after sending the rules all the time.
3) In RP, I am using a FOB, and wanted to create a user that matched the FOB ID, just so I could add a name to it so it was more easily found in the log. If I add a new user and tick the checkbox that they have a FOB, the code box is set all zeros, I save the user, switch to another user or any other screen in RP, and then return to the just created user, the FOB checkbox is un-ticked. Now the control will log with the named user correctly, but a conflict gets reported every time because it reverts back to unchecked. Obviously if you make other changes and send to the control this user will be uploaded incorrectly. Am I missing something?
I will post some more items here in the coming weeks to see if anyone has ideas on streamlining my rules, and to document a couple items I have done. Nothing ground breaking, but hoping to give a little back to where I have learned much.