Jump to content
Monthly Subscriptions Are Here Read more... ×
aks_Dale

Internet Connection History Tech Overview Request

Recommended Posts

aks_Dale

Just installed a new Raspberry PI w/ Domotz. This site is showing the Internet connection is bouncing with over 650 up/down entries in 20 hours. The connection is via wireless distribution to a site about 2 miles away. Normally a solid connection, currently the Internet is spotty at best.

 

To present to the client and the wireless distribution provider, I'd like a technical overview of how Domotz monitors/records the internet connection history.

 

Thanks!

Share this post


Link to post
Share on other sites
henriquesalvador

Hi @aks_Dale,

 

Here's a detailed explanation about the Downtime tab:

Network Health Analysis --> Downtime Tab: Agent Connection Lost Alert (marked with a bell) vs Simple Disconnections

The two features ( Agent Connection Lost Alert - Simple Disconnections) are similar in the idea, but technically speaking they have been implemented in a very different way. This is very important, because it is a good way to guarantee that both are working correctly, or to identify if there is a misalignment in one of the two mechanisms

Basically, every Domotz Agent sends a packet (or train) of 4 ‘pings’ toward "echo.domotz.com" (alias of Google DNS - 8.8.8.8) once every minute. It also sends a Heartbeat to our cloud, to notify our backend that the agent is still alive.

Agent Perspective: Missing Ping --> triggers an entry in the Downtime Tab - Simple Disconnections

If we do not receive a reply on at least one of the pings in the packet, (either the DNS is failing, or there is not any internet connection, network cable is detached from the Domotz Box/Pi, or simply our ping server - echo.domotz.com is not available) the Domotz Agent tracks the time that the first ping was lost.


Two minutes after we start receiving replies to our ping messages again, the Agent notifies our backend that the connection is UP again and that there was a Downtime of X minutes (starting from the first ping lost). This is going to populate the Downtime Tab. (This delay is to ensure that the connection has become stable again before recording the data).

What happens if the Domotz Agent is turned off (unplug the power cable from the Domotz Box/Pi)? In this case, the Agent does not send any ping (of course) and cannot be aware if there is connectivity or not. Therefore, there will be no entry in the Downtime Tab, for the whole period the Domotz Agent is off.
However, our backend is still aware that something is going on. See next:

Cloud Perspective: Missing Heartbeat --> triggers the alert (if configured in the Alert management) and mark disconnection with Bell
 

After Five(5) minutes have passed since our backend received the last Heartbeat from an Agent, the backend declares that Agent to be OFFLINE.


If the Agent Connection Lost alert is configured, you will receive an email from our backend stating that the we haven’t received any information from that agent in the last five minutes. In any the disconnection in the Downtime tab is marked with a bell.

As soon as the Agent starts sending the Heartbeats again, you will receive an email from our backend stating that the connection to the Agent was recovered.
This last mechanism works both if you disconnect the power cable or the network cable from the Domotz Box/Pi, because it's triggered by our backend.

 

If you still believe there may be a problem with the Agent, please contact our support (support@domotz.com) informing your Domotz account and Agent Mac Address.

 

Kind regards,

Henrique Salvador

Domotz Support

Share this post


Link to post
Share on other sites
aks_Dale

Ok. That explains why the Domotz is reporting that the network is bouncing....I can't ping 8.8.8.8 from within the network from any box. The ISP (a local wireless internet provider) appears to be blocking 8.8.8.8. I'll have to discuss the implications with them.

 

Today, the Internet connection appears solid from the user's viewpoint, but, Domotz is reporting bouncing about every minute.

 

At least your explanation gives me a point of reference and direction to move.

 

Hopefully, others will find this helpful.

 

Dale

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×