M1XEP not sending out emails/testing while in RP?

[newalarm]

I was setting up partitions/Areas yesterday, and while in RP, i noticed that i was not getting emails. I have a few trigger emails to be sent if the front door is opened, and if the system goes into alarm or is disarmed after an alarm. None were going out while i was in RP. I tested the XEP by hitting the test button, and it sent an email, but when i opened the front door or triggered alarm situation, nothing.
 
I went into rules, and there is another test button for rules. When I test a rule, it should execute the "then" commands. But nothing worked. Later, front door emails started being sent again. Prior and after working in RP, everything was working normally.
 
All rules have been there for a while and all were active.
 
Anyone ever had this problem? Could it be something with RP?

 

[apostolakisl]

When you are running RP and are connected to the Elk via its xep, the xep shuts down all connections with other devices.  While I can not say for certain that this includes email servers,  I would pretty much expect it to.

 

[newalarm]

I have noticed that XEP sometimes cuts off/resets itself at random moments. But It seemed connected and I was able to send test emails in XEP interface, but not sending tests through the rules screen.

 

[jpmargis]

This is normal and well documented M1XEP operation.  Nothing other than test communications with RP connected and you must wait a minimum of eight minutes after power up before connecting RP otherwise it will disconnect at random intervals.

 

[newalarm]

You need to wait 8 min after powering up the control? I am confused.

 

[jpmargis]

Not the control; the M1XEP.  Same for a reboot.

 

[newalarm]

Are you saying when you connect to it with RP, you need to wait 8 min prior to doing anything else with the XEP? I guess it is initializing or something?

 

[apostolakisl]

Are you saying when you connect to it with RP, you need to wait 8 min prior to doing anything else with the XEP? I guess it is initializing or something?

 
 
No, he is saying that after you reboot the xep, don't connect to it for a while (8 minutes).  
 
Connecting to the xep using ElkRP doesn't do a reboot and you can start changes rules or whatever right away.
 
Rebooting the xep is not something you should need to do often.  Pretty much after firmware updates or changes in the IP settings.
 
When you test your rules to see if they are doing the stuff they are supposed to be doing, you should not have Elk RP connected.  When ElkRP connects, pretty much nothing else happens network wise.

 

[newalarm]

Ok, i think i understand. But why the heck do they have a test button in the rules section of RP if you can't use it? And how would you test the rules? Can you test rules through the keypads?

 

[apostolakisl]

Ok, i think i understand. But why the heck do they have a test button in the rules section of RP if you can't use it? And how would you test the rules? Can you test rules through the keypads?

 
Being connected to Elk via ElkRP and the XEP only ties up the network communications.  Everything else works fine.

 

[newalarm]

so.... the answer is that the button does not work and is useless right?

 

[thill]

Lou Apo, on 07 Feb 2013 - 07:58, said:
Being connected to Elk via ElkRP and the XEP only ties up the network communications. Everything else works fine.

Adding to what Lou has said, as long as a rule doesn't involve an email then the test button works fine. It is not useless, it's just that rules involving emails being sent out cannot be tested only because the network is tied up. There are lots of other uses for the rule test button.

 

[newalarm]

Ah... got it. I guess most of my rules involve emails so I did not think of non email rules. Would be nice if they made a note of that in RP... or maybe I missed it.
 
Thanks all.