From 0f9f6a0e14b17beb28ebcfaf87d5926f45491111 Mon Sep 17 00:00:00 2001 From: nrb <freifunk@nicoboehr.de> Date: Sun, 3 Jan 2021 13:05:42 +0100 Subject: [PATCH] add some texts --- update_checker.html | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/update_checker.html b/update_checker.html index b36d72c..c160bba 100644 --- a/update_checker.html +++ b/update_checker.html @@ -57,8 +57,10 @@ </script> </head> <body> - <h1>Update downloaded and offline</h1> + <h1>Update Checker</h1> <p>Last update: <span id="lastUpdate">(never)</span></p> + <h2>Update downloaded and offline</h2> + <p>These nodes have downloaded a firmware update from the server, have never been observed running the updated firmware and are currently offline. It is not guaranteed they are offline because of the update. It could also mean they are running the new firmware fine, but they currently don't have a connection to the mesh or they were interrupted before installing the update etc.</p> <table> <tr> <th>Hostname</th> @@ -72,7 +74,8 @@ </tr> <tbody id="downloadedOffline"></tbody> </table> - <h1>Update downloaded</h1> + <h2>Update downloaded</h2> + <p>These nodes have downloaded a firmware update from the server, but are still running the old firmware version. It is normal for a node to appear here for a short period of time. When a node stays in this state for more than 10-20 minutes, this usually means the node couldn't verify the update's signature and will try to re-download, increasing the number in the <em>Download Count</em> column. Common causes for this problem is a unstable connection, but in rare cases it can also be an issue with the update package itself.</p> <table> <tr> <th>Hostname</th> -- GitLab