Syslog reports Envisalink4 "Going down for REBOOT" every 3 minutes

[norm]

I have recently installed a Envisalink4 to my DSC system, updated firmware to 1.2.136 and then connected a syslog client.

Is it normal for the Envisalink to reboot constantly when there is no activity (ie. zones opening/closing)?

From the syslog, Envisalink is reporting "Going down for REBOOT" every 3 minutes during the middle of night or when I am away from home.

[K-Man]

If the module cannot connect to its alerting server then you may see this. Make sure you have Internet connectivity and you have not firewalled access to Envisacor servers.

[norm]

Hi K-Man,

Thank you for the reply.

Yes you are correct- I have intentionally firewalled all internet access.
Also, after reading through this forum in detail, you posted this:

The Envisalink is programmed to reboot if it doesn't see any traffic from our servers or from the TPI in an 20 minute period.

So, taking this into account, it is my understanding that without a connection to Envisacor's servers for 20 minutes, Envisalink4 will perpetually reboot every 3 minutes until a connection is established unless a TPI command is locally sent to it.

[K-Man]

Hi K-Man,

Thank you for the reply.

Yes you are correct- I have intentionally firewalled all internet access.
Also, after reading through this forum in detail, you posted this:

The Envisalink is programmed to reboot if it doesn't see any traffic from our servers or from the TPI in an 20 minute period.

So, taking this into account, it is my understanding that without a connection to Envisacor's servers for 20 minutes, Envisalink4 will perpetually reboot every 3 minutes until a connection is established unless a TPI command is locally sent to it.

That may have been true back then but now the Envisalink just looks for incoming IP unicast traffic. Just hit it with some, any, traffic at least once in a 20 minute period to keep it alive.