Skip to content
Snippets Groups Projects
Commit 0f9f6a0e authored by Nico's avatar Nico
Browse files

add some texts

parent a6c8143d
No related branches found
No related tags found
No related merge requests found
...@@ -57,8 +57,10 @@ ...@@ -57,8 +57,10 @@
</script> </script>
</head> </head>
<body> <body>
<h1>Update downloaded and offline</h1> <h1>Update Checker</h1>
<p>Last update: <span id="lastUpdate">(never)</span></p> <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> <table>
<tr> <tr>
<th>Hostname</th> <th>Hostname</th>
...@@ -72,7 +74,8 @@ ...@@ -72,7 +74,8 @@
</tr> </tr>
<tbody id="downloadedOffline"></tbody> <tbody id="downloadedOffline"></tbody>
</table> </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> <table>
<tr> <tr>
<th>Hostname</th> <th>Hostname</th>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment