M1ZTS Temp Sensor Rule Issue - ELK Products

M1ZTS Temp Sensor Rule Issue

M1 Support Forum M1ZTS Temp Sensor Rule Issue

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #10050
    Doug G

      I have this M1ZTS Temp Sensor hardwired to zone 4 and have the rule created that is referenced in the instructions that if the temperature falls below a certain temp that Output 1 is used. I tested out the rule and it is fine and passed, but when I run a “Check For Conflict”. I get conflicts with Rules And Texts and when I send them up to the M1, but if I disable the rule the conflicts go away. I see for both “Rules And Texts” that “This item has been modified in the database. If it is correct it should be downloaded. Does something need to be filled out in the Text field for the Rule I am using?  I just do not know what I am missing here. Thank you.

      #10051
      Brad Weeks

        Do you have any rules that “Then Send Text ….”

        How do you have your Temp Rule written? You should not be turning on Output 1. Output 1 is the interior Speaker terminal for spoken Voice and Siren Sounds.

        #10052
        Doug G

          I do have one rule that sends text to my Z-Wave Door lock to unlock and lock the door based on arming and disarming based on certain dates and times, which have worked for 10 years with no issues. I have tried all outputs, and I get the same result, but my ideal choice would be to use the voice and siren sound and not my alarm horn loud siren that is on output 2. I have it set to exactly the same rule that is in the documentation and get the same result each time along with many other variants. Anything else I should try?

          #10053
          Brad Weeks

            The M1ZTS Instructions Rule example is turning on Output 3 not Output 1.

            If you have a Rule “Disabled” this will cause a Conflict when ElkRP2 connects to the M1. If the Rules are not Disabled then try Select the Conflict and Send Checked Items to System

            #10054
            Doug G

              Yes I am aware of that, but I followed that rule to the “T” is what I am saying and using Output 3 as the instructions mention and I get the same error message and I also tried other outputs and got the same result.

              I have disabled rules in the list for years and have not ever happened this happen at all until adding the temperature sensor rule. I disable the temperature sensor rule and the conflicts are resolved.

              So the issue is a new one for me that I have never seen and been using this alarm for 10 years so I am just now getting around to adding these new items / sensors I bought.

              #10055
              Doug G

                Update:

                I enabled all rules as per your instruction and the conflicts cleared, but now when I disable the other rules back to the way they were I get the conflict again (which goes along with your statement you mention “If you have a Rule “Disabled” this will cause a Conflict when ElkRP2 connects to the M1”) and the purpose of those disabled rules is when I go on vacation. Is there a way to enable all the rules but only enable a rule set for when I am out on vacation and enable a rule set for when I am NOT on vacation? That will then satisfy the keep all rules enabled issue that you have mentioned to me.

                Why would this only happen when I add the temperature sensor rule?

                #10058
                Brad Weeks

                  Create two separate Accounts one with the Rules and One without the Rules to avoid the “Conflicts”

                  #10066
                  Doug G

                    Will there be an option to address this in a future update of the software? Maybe a Vacation mode of the rule handling as a roadmap item. I would have to maintain two accounts at that point, and it can become a little daunting and that is the point of the automation to eliminate the human / interaction as errors can be made. Thank you.

                    #10111
                    Doug G

                      Is this a Roadmap item or even a possibility for future releases? I just do not see a point of disabled rules if I am not able to use them in my one account. Why wouldn’t the M1EXP just ignore those rules? Thank you.

                      #10115
                      Brad Weeks

                        The feature to “Disable” a rule allows you to turn OFF a rule without removing it from the ElkRP2 programing for testing and so forth . This way you do not have to re-create the rule(s) if you do not need to. To the best of my knowledge this will not change and if a Rule is “Disabled” this will cause a Conflict alerting you you may have forgotten to re-enable the rule.

                      Viewing 10 posts - 1 through 10 (of 10 total)
                      • You must be logged in to reply to this topic.
                      Scroll to Top