index.html 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517
  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4. <meta charset="utf-8" />
  5. <title>ESP Web Tools</title>
  6. <meta
  7. name="description"
  8. content="Easily allow users to flash new firmware for their ESP-devices on the web."
  9. />
  10. <meta name="viewport" content="width=device-width" />
  11. <meta property="og:title" content="ESP Web Tools" />
  12. <meta property="og:site_name" content="ESP Web Tools" />
  13. <meta
  14. property="og:url"
  15. content="https://esphome.github.io/esp-web-tools/"
  16. />
  17. <meta property="og:type" content="website" />
  18. <meta
  19. property="og:description"
  20. content="Easily allow users to flash new firmware for their ESP-devices on the web."
  21. />
  22. <meta
  23. property="og:image"
  24. content="https://esphome.github.io/esp-web-tools/static/social.png"
  25. />
  26. <meta name="twitter:card" content="summary_large_image" />
  27. <meta name="twitter:title" content="ESP Web Tools" />
  28. <meta
  29. name="twitter:description"
  30. content="Easily allow users to flash new firmware for their ESP-devices on the web."
  31. />
  32. <meta
  33. name="twitter:image"
  34. content="https://esphome.github.io/esp-web-tools/static/social.png"
  35. />
  36. <meta name="color-scheme" content="dark light" />
  37. <style>
  38. body {
  39. font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI",
  40. Roboto, Ubuntu, sans-serif;
  41. padding: 0;
  42. margin: 0;
  43. line-height: 1.4;
  44. }
  45. .content {
  46. max-width: 600px;
  47. margin: 0 auto;
  48. padding: 12px;
  49. }
  50. h2 {
  51. margin-top: 2em;
  52. }
  53. h3 {
  54. margin-top: 1.5em;
  55. }
  56. .projects {
  57. display: flex;
  58. text-align: center;
  59. flex-wrap: wrap;
  60. gap: 24px;
  61. justify-content: center;
  62. }
  63. .projects a {
  64. color: initial;
  65. text-decoration: none;
  66. }
  67. .project .logo img {
  68. height: 50px;
  69. }
  70. .project .name {
  71. margin-top: 8px;
  72. }
  73. a {
  74. color: #03a9f4;
  75. }
  76. .screenshot {
  77. text-align: center;
  78. }
  79. .screenshot img {
  80. max-width: 100%;
  81. box-shadow: rgb(0 0 0 / 20%) 0px 2px 1px -1px,
  82. rgb(0 0 0 / 14%) 0px 1px 1px 0px, rgb(0 0 0 / 12%) 0px 1px 3px 0px;
  83. border-radius: 4px;
  84. }
  85. .screenshot i {
  86. margin-top: 4px;
  87. display: block;
  88. }
  89. .videoWrapper {
  90. position: relative;
  91. padding-bottom: 56.25%; /* 16:9 */
  92. height: 0;
  93. margin-bottom: 25px;
  94. background: #ccc;
  95. }
  96. .hidden {
  97. display: none;
  98. }
  99. .content pre {
  100. display: block;
  101. padding-left: 8px;
  102. overflow-y: scroll;
  103. }
  104. .footer {
  105. margin-top: 24px;
  106. border-top: 1px solid #ccc;
  107. padding-top: 24px;
  108. text-align: center;
  109. }
  110. .footer .initiative {
  111. font-style: italic;
  112. margin-top: 16px;
  113. }
  114. table {
  115. border-spacing: 0;
  116. }
  117. td {
  118. padding: 8px;
  119. border-bottom: 1px solid #ccc;
  120. }
  121. @media (prefers-color-scheme: dark) {
  122. body {
  123. background-color: #333;
  124. color: #fff;
  125. }
  126. a {
  127. color: #58a6ff;
  128. }
  129. }
  130. </style>
  131. <script
  132. type="module"
  133. src="https://unpkg.com/@justinribeiro/lite-youtube@1.3.0/lite-youtube.js"
  134. ></script>
  135. <script module>
  136. import(
  137. // In development we import locally.
  138. window.location.hostname === "localhost"
  139. ? "/dist/web/install-button.js"
  140. : "https://unpkg.com/esp-web-tools@9.0.5/dist/web/install-button.js?module"
  141. );
  142. </script>
  143. </head>
  144. <body>
  145. <div class="content">
  146. <h1>ESP Web Tools</h1>
  147. <p>
  148. User friendly tools to manage ESP8266 and ESP32 devices in the browser:
  149. </p>
  150. <ul>
  151. <li>Install &amp; update firmware</li>
  152. <li>Connect device to the Wi-Fi network</li>
  153. <li>Visit the device's hosted web interface</li>
  154. <li>Access logs and send terminal commands</li>
  155. <li>
  156. Add devices to
  157. <a href="https://www.home-assistant.io">Home Assistant</a>
  158. </li>
  159. </ul>
  160. <div class="videoWrapper">
  161. <lite-youtube
  162. videoid="E8bdATqXM8c"
  163. videotitle="ESP Web Tools in action"
  164. ></lite-youtube>
  165. </div>
  166. <h2 id="demo">Try a live demo</h2>
  167. <p>
  168. This demo will install
  169. <a href="https://esphome.io">ESPHome</a>. To get started, connect an ESP
  170. device to your computer and hit the button:
  171. </p>
  172. <esp-web-install-button manifest="static/firmware_build/manifest.json">
  173. <i slot="unsupported">
  174. The demo is not available because your browser does not support Web
  175. Serial. Open this page in Google Chrome or Microsoft Edge instead<span
  176. class="not-supported-i hidden"
  177. >
  178. (but not on your iOS device)</span
  179. >.
  180. </i>
  181. </esp-web-install-button>
  182. <h2 id="used-by">Products using ESP Web Tools</h2>
  183. <div class="projects">
  184. <a href="https://install.wled.me" target="_blank" class="project">
  185. <div class="logo">
  186. <img src="static/logos/wled.png" alt="WLED logo" />
  187. </div>
  188. <div class="name">WLED</div>
  189. </a>
  190. <a
  191. href="https://arendst.github.io/Tasmota-firmware/"
  192. target="_blank"
  193. class="project"
  194. >
  195. <div class="logo">
  196. <img src="static/logos/tasmota.svg" alt="Tasmota logo" />
  197. </div>
  198. <div class="name">Tasmota</div>
  199. </a>
  200. <a href="https://td-er.nl/ESPEasy/" target="_blank" class="project">
  201. <div class="logo">
  202. <img src="static/logos/espeasy.png" alt="ESPEasy logo" />
  203. </div>
  204. <div class="name">ESPEasy</div>
  205. </a>
  206. <a
  207. href="https://canair.io/installer.html"
  208. target="_blank"
  209. class="project"
  210. >
  211. <div class="logo">
  212. <img src="static/logos/canairio.png" alt="CanAirIO logo" />
  213. </div>
  214. <div class="name">CanAirIO</div>
  215. </a>
  216. <a href="https://web.esphome.io" target="_blank" class="project">
  217. <div class="logo">
  218. <img src="static/logos/esphome.svg" alt="ESPHome logo" />
  219. </div>
  220. <div class="name">ESPHome</div>
  221. </a>
  222. <a
  223. href="https://2smart.com/docs-resources/platform-updates/platform-updates-13-07-2022"
  224. target="_blank"
  225. class="project"
  226. >
  227. <div class="logo">
  228. <img src="static/logos/2smart.png" alt="2Smart logo" />
  229. </div>
  230. <div class="name">2Smart</div>
  231. </a>
  232. </div>
  233. <h2>How it works</h2>
  234. <p>
  235. ESP Web Tools works by combining
  236. <a
  237. href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_API"
  238. >Web Serial</a
  239. >, <a href="https://www.improv-wifi.com/">Improv Wi-Fi</a> (optional),
  240. and a manifest which describes the firmware. ESP Web Tools detects the
  241. chipset of the connected ESP device and automatically selects the right
  242. firmware variant from the manifest.
  243. </p>
  244. <p>
  245. Web Serial is available in Google Chrome and Microsoft Edge
  246. browsers<span class="not-supported-i hidden">
  247. (but not on your iOS device)</span
  248. >. Android support should be possible but has not been implemented yet.
  249. </p>
  250. <h3 id="improv">Configuring Wi-Fi</h3>
  251. <p>
  252. ESP Web Tools supports the
  253. <a href="https://www.improv-wifi.com/serial"
  254. >Improv Wi-Fi serial standard</a
  255. >. This is an open standard to allow configuring Wi-Fi via the serial
  256. port.
  257. </p>
  258. <p>
  259. If the firmware supports Improv, a user will be asked to connect the
  260. device to the network after installing the firmware. Once connected, the
  261. device can send the user to a URL to finish configuration. For example,
  262. this can be a link to the device's IP address where it serves a local
  263. UI.
  264. </p>
  265. <p>
  266. At any time in the future a user can use ESP Web Tools to find the
  267. device link or to reconfigure the Wi-Fi settings without doing a
  268. reinstall.
  269. </p>
  270. <p class="screenshot">
  271. <img
  272. src="./static/screenshots/dashboard.png"
  273. alt="Screenshot showing ESP Web Tools dialog offering visting the device, adding it to Home Assistant, change Wi-Fi, show logs and console and reset data."
  274. />
  275. <i>Screenshot showing the ESP Web Tools interface</i>
  276. </p>
  277. <h3 id="logs">Viewing logs & sending commands</h3>
  278. <p>
  279. ESP Web Tools allows users to open a serial console to see the logs and
  280. send commands.
  281. </p>
  282. <p class="screenshot">
  283. <img
  284. src="./static/screenshots/logs.png"
  285. alt="Screenshot showing ESP Web Tools dialog with a console showing ESPHome logs and a terminal prompt to sent commands."
  286. />
  287. <i>Screenshot showing the ESP Web Tools logs & console</i>
  288. </p>
  289. <h2 id="add-website">Adding ESP Web Tools to your website</h2>
  290. <p>
  291. To add this to your own website, you need to include the ESP Web Tools
  292. JavaScript files on your website, create a manifest file and add the ESP
  293. Web Tools button HTML.
  294. </p>
  295. <p>
  296. <a href="https://github.com/balloob/squeezelite-esp32-install"
  297. >Click here to see a full example.</a
  298. >
  299. </p>
  300. <p>
  301. <b>Step 1:</b> Load ESP Web Tools JavaScript on your website by adding
  302. the following HTML snippet.
  303. </p>
  304. <pre>
  305. &lt;script
  306. type="module"
  307. src="https://unpkg.com/esp-web-tools@9.0.5/dist/web/install-button.js?module"
  308. >&lt;/script></pre
  309. >
  310. <p>
  311. (If you prefer to locally host the JavaScript,
  312. <a href="https://unpkg.com/browse/esp-web-tools/dist/web/"
  313. >download it here</a
  314. >)
  315. </p>
  316. <p>
  317. <b>Step 2:</b> Find a place on your page where you want the button to
  318. appear and include the following bit of HTML. Update the
  319. <code>manifest</code> attribute to point at your manifest file.
  320. </p>
  321. <pre>
  322. &lt;esp-web-install-button
  323. manifest="/static/firmware_build/manifest.json"
  324. >&lt;/esp-web-install-button></pre
  325. >
  326. <p>
  327. <b>Note:</b> ESP Web Tools requires that your website is served over
  328. <code>https://</code> to work. This is a Web Serial security
  329. requirement.
  330. </p>
  331. <p>
  332. If your manifest or the firmware files are hosted on another server,
  333. make sure you configure
  334. <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS"
  335. >the CORS-headers</a
  336. >
  337. such that your website is allowed to fetch those files by adding the
  338. header
  339. <code
  340. >Access-Control-Allow-Origin: https://domain-of-your-website.com</code
  341. >.
  342. </p>
  343. <p>
  344. ESP Web Tools can also be integrated in your projects by installing it
  345. <a href="https://www.npmjs.com/package/esp-web-tools">via NPM</a>.
  346. </p>
  347. <h3 id="manifest">Creating your manifest</h3>
  348. <p>
  349. Manifests describe the firmware that you want to offer the user to
  350. install. It allows specifying different builds for the different types
  351. of ESP devices. Current supported chip families are
  352. <code>ESP8266</code>, <code>ESP32</code>, <code>ESP32-C3</code>,
  353. <code>ESP32-S2</code> and <code>ESP32-S3</code>. The correct build will
  354. be automatically selected based on the type of the connected ESP device.
  355. </p>
  356. <pre>
  357. {
  358. "name": "ESPHome",
  359. "version": "2021.11.0",
  360. "home_assistant_domain": "esphome",
  361. "funding_url": "https://esphome.io/guides/supporters.html",
  362. "new_install_prompt_erase": false,
  363. "builds": [
  364. {
  365. "chipFamily": "ESP32",
  366. "parts": [
  367. { "path": "bootloader.bin", "offset": 4096 },
  368. { "path": "partitions.bin", "offset": 32768 },
  369. { "path": "ota.bin", "offset": 57344 },
  370. { "path": "firmware.bin", "offset": 65536 }
  371. ]
  372. },
  373. {
  374. "chipFamily": "ESP8266",
  375. "parts": [
  376. { "path": "esp8266.bin", "offset": 0 }
  377. ]
  378. }
  379. ]
  380. }</pre
  381. >
  382. <p>
  383. Each build contains a list of parts to be installed to the ESP device.
  384. Each part consists of a path to the file and an offset on the flash
  385. where it should be installed. Part paths are resolved relative to the
  386. path of the manifest, but can also be URLs to other hosts.
  387. </p>
  388. <p>
  389. If your firmware is supported by Home Assistant, you can add the
  390. optional key <code>home_assistant_domain</code>. If present, ESP Web
  391. Tools will link the user to add this device to Home Assistant.
  392. </p>
  393. <p>
  394. By default a new installation will erase all data before installation.
  395. If you want to leave this choice to the user, set the optional manifest
  396. key
  397. <code>new_install_prompt_erase</code> to <code>true</code>. ESP Web
  398. Tools offers users a new installation if it is unable to detect the
  399. current firmware of the device (via Improv Serial) or if the detected
  400. firmware does not match the name specififed in the manifest.
  401. </p>
  402. <p>
  403. When a firmware is first installed on a device, it might need to do some
  404. time consuming tasks like initializing the file system. By default ESP
  405. Web Tools will wait 10 seconds to receive an Improv Serial response to
  406. indicate that the boot is completed. You can increase this timeout by
  407. setting the optional manifest key
  408. <code>new_install_improv_wait_time</code> to the number of seconds to
  409. wait. Set to <code>0</code> to disable Improv Serial detection.
  410. </p>
  411. <p>
  412. If your product accepts donations you can add
  413. <code>funding_url</code> to your manifest. This allows you to link to
  414. your page explaining the user how they can fund development. This link
  415. is visible in the ESP Web Tools menu when connected to a device running
  416. your firmware (as detected via Improv).
  417. </p>
  418. <p>
  419. ESP Web Tools allows you to provide your own check if the device is
  420. running the same firmware as specified in the manifest. This check can
  421. be setting the <code>overrides</code> property on
  422. <code>&lt;esp-web-install-button&gt;</code>. The value is an object
  423. containing a
  424. <code>checkSameFirmware(manifest, improvInfo)</code> function. The
  425. <code>manifest</code> parameter is your manifest and
  426. <code>improvInfo</code> is the information returned from Improv:
  427. <code>{ name, firmware, version, chipFamily }</code>. This check is only
  428. called if the device firmware was detected via Improv.
  429. </p>
  430. <pre>
  431. const button = document.querySelector('esp-web-install-button');
  432. button.overrides = {
  433. checkSameFirmware(manifest, improvInfo) {
  434. const manifestFirmware = manifest.name.toLowerCase();
  435. const deviceFirmware = improvInfo.firmware.toLowerCase();
  436. return manifestFirmware.includes(deviceFirmware);
  437. }
  438. };</pre
  439. >
  440. <h3 id="customize">Customizing the look and feel</h3>
  441. <p>
  442. You can change the colors of the default UI elements with CSS custom
  443. properties (variables), the following variables are available:
  444. </p>
  445. <ul>
  446. <li><code>--esp-tools-button-color</code></li>
  447. <li><code>--esp-tools-button-text-color</code></li>
  448. </ul>
  449. <p>There are also some attributes that can be used for styling:</p>
  450. <table>
  451. <tr>
  452. <td><code>install-supported</code></td>
  453. <td>Added if installing firmware is supported</td>
  454. </tr>
  455. <tr>
  456. <td>
  457. <code>install-unsupported</code>
  458. </td>
  459. <td>Added if installing firmware is not supported</td>
  460. </tr>
  461. </table>
  462. <h4>Replace the button and message with a custom one</h4>
  463. <p>
  464. You can replace both the activation button and the message that is shown
  465. when the user uses an unsupported browser or non-secure context with
  466. your own elements. This can be done using the <code>activate</code>,
  467. <code>unsupported</code> and <code>not-allowed</code> slots:
  468. </p>
  469. <pre>
  470. &lt;esp-web-install-button
  471. manifest="/static/firmware_build/manifest.json"
  472. >
  473. &lt;button slot="activate">Custom install button&lt;/button>
  474. &lt;span slot="unsupported">Ah snap, your browser doesn't work!&lt;/span>
  475. &lt;span slot="not-allowed">Ah snap, you are not allowed to use this on HTTP!&lt;/span>
  476. &lt;/esp-web-install-button>
  477. </pre
  478. >
  479. <h2>Why we created ESP Web Tools</h2>
  480. <div class="videoWrapper">
  481. <lite-youtube
  482. videoid="6ZMXE5PXPqU"
  483. videotitle="Why we created ESP Web Tools"
  484. videoStartAt="1255"
  485. ></lite-youtube>
  486. </div>
  487. <div class="footer">
  488. <div class="initiative">
  489. ESP Web Tools is a project by
  490. <a href="https://esphome.io">ESPHome</a>.<br />
  491. Development is funded by
  492. <a href="https://www.nabucasa.com">Nabu Casa</a>.
  493. </div>
  494. <div>
  495. ESP Web Tools is
  496. <a href="https://github.com/esphome/esp-web-tools">open source</a>.
  497. </div>
  498. </div>
  499. </div>
  500. <script>
  501. if (/iPad|iPhone|iPod/.test(navigator.userAgent)) {
  502. document.querySelector(".not-supported-i").classList.remove("hidden");
  503. }
  504. </script>
  505. </body>
  506. </html>