Entering the Service tab within the Hub settings menu itself, we can find a series of parameters.
This parameter means that, after having confirmed the loss of connection with the Hub, the cloud sends a Polling failure, but it will wait 30 seconds before communicating said loss of connection to those connected to the Hub (basic users, PRO users and CRA) .
This parameter regulates the determination of the polling fault.
The AJAX Hub will always send 3 Polling pings, and in this section we can configure the time interval between each ping to the cloud. If after these 3 pings there has been no communication, the Polling failure is determined.
So, if we configure 30 seconds of alarm delay in the first parameter described, the cloud will do the following:
- send 3 packets, 1 every 10 seconds, to confirm the connection loss (as configured in the second parameter)
- after the last ping sent and no response, it will wait another 30 seconds before sending the connection loss notification (as configured in the first parameter). If in that time the cloud receives another ping, it will NOT send the Polling failure notification.
Therefore, how long will it take to receive the connection loss notification?
With the configured parameters, the answer is: (10 x 3) + 30 = 60 seconds
The reader will have already understood that in the "Service" tab the order of these settings is inverted, that is, the first one that appears is the delay time after the loss of pings, while the second parameter that appears is related to the time between pings --> chronologically these times are applied in reverse order with respect to their order of appearance in the menu we have just analyzed.
ADDITIONAL COMMENT
Knowing all this we want to differentiate this notification (object of the article) and the E602 event; this last event is the periodic test of the Hub that confirms its correct communication with the cloud
This periodic test depends on the type of connection established between the Hub and the CRA:
- Cloud connection: 15 minutes, not configurable (supervision request from Security Companies ).
- Direct connection + cloud: configurable from 1 minute to 24 hours in Monitoring Center.
The periodic test describes the communication status of the Hub itself, and is only of interest to the ARC.
On the other hand, the Polling failed signal describes the status of the connection between Hub and cloud, and eventually produces a notification that reaches both the apps and the CRA (Event E350).
To summarize:
- Periodic test (E602) confirms the connection between Hub and cloud.
- Polling loss (E350) notifies of failed connection between Hub and cloud