index.html 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572
  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.4.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/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://sle118.github.io/squeezelite-esp32-installer/"
  224. target="_blank"
  225. class="project"
  226. >
  227. <div class="logo">
  228. <img
  229. src="static/logos/squeezelite-esp32.png"
  230. alt="Squeezelite-ESP32 logo"
  231. />
  232. </div>
  233. <div class="name">Squeezelite-ESP32</div>
  234. </a>
  235. <a
  236. href="https://2smart.com/docs-resources/platform-updates/platform-updates-13-07-2022"
  237. target="_blank"
  238. class="project"
  239. >
  240. <div class="logo">
  241. <img src="static/logos/2smart.png" alt="2Smart logo" />
  242. </div>
  243. <div class="name">2Smart</div>
  244. </a>
  245. <a
  246. href="https://clockwise.page"
  247. target="_blank"
  248. class="project">
  249. <div class="logo">
  250. <img src="static/logos/clockwise.png" alt="Clockwise logo" />
  251. </div>
  252. <div class="name">Clockwise</div>
  253. </a>
  254. </div>
  255. <h2>How it works</h2>
  256. <p>
  257. ESP Web Tools works by combining
  258. <a
  259. href="https://developer.mozilla.org/docs/Web/API/Web_Serial_API"
  260. >Web Serial</a
  261. >, <a href="https://www.improv-wifi.com/">Improv Wi-Fi</a> (optional),
  262. and a manifest which describes the firmware. ESP Web Tools detects the
  263. chipset of the connected ESP device and automatically selects the right
  264. firmware variant from the manifest.
  265. </p>
  266. <p>
  267. Web Serial is available in Google Chrome and Microsoft Edge
  268. browsers<span class="not-supported-i hidden">
  269. (but not on your iOS device)</span
  270. >. Android support should be possible but has not been implemented yet.
  271. </p>
  272. <h3 id="improv">Configuring Wi-Fi</h3>
  273. <p>
  274. ESP Web Tools supports the
  275. <a href="https://www.improv-wifi.com/serial"
  276. >Improv Wi-Fi serial standard</a
  277. >. This is an open standard to allow configuring Wi-Fi via the serial
  278. port.
  279. </p>
  280. <p>
  281. If the firmware supports Improv, a user will be asked to connect the
  282. device to the network after installing the firmware. Once connected, the
  283. device can send the user to a URL to finish configuration. For example,
  284. this can be a link to the device's IP address where it serves a local
  285. UI.
  286. </p>
  287. <p>
  288. At any time in the future a user can use ESP Web Tools to find the
  289. device link or to reconfigure the Wi-Fi settings without doing a
  290. reinstall.
  291. </p>
  292. <p class="screenshot">
  293. <img
  294. src="./static/screenshots/dashboard.png"
  295. 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."
  296. />
  297. <i>Screenshot showing the ESP Web Tools interface</i>
  298. </p>
  299. <h3 id="logs">Viewing logs & sending commands</h3>
  300. <p>
  301. ESP Web Tools allows users to open a serial console to see the logs and
  302. send commands.
  303. </p>
  304. <p class="screenshot">
  305. <img
  306. src="./static/screenshots/logs.png"
  307. alt="Screenshot showing ESP Web Tools dialog with a console showing ESPHome logs and a terminal prompt to sent commands."
  308. />
  309. <i>Screenshot showing the ESP Web Tools logs & console</i>
  310. </p>
  311. <h2 id="add-website">Adding ESP Web Tools to your website</h2>
  312. <p>
  313. To add this to your own website, you need to include the ESP Web Tools
  314. JavaScript files on your website, create a manifest file and add the ESP
  315. Web Tools button HTML.
  316. </p>
  317. <p>
  318. <a href="https://github.com/balloob/squeezelite-esp32-install"
  319. >Click here to see a full example.</a
  320. >
  321. </p>
  322. <p>
  323. <b>Step 1:</b> Load ESP Web Tools JavaScript on your website by adding
  324. the following HTML snippet.
  325. </p>
  326. <pre>
  327. &lt;script
  328. type="module"
  329. src="https://unpkg.com/esp-web-tools@9/dist/web/install-button.js?module"
  330. >&lt;/script></pre
  331. >
  332. <p>
  333. (If you prefer to locally host the JavaScript,
  334. <a href="https://unpkg.com/browse/esp-web-tools/dist/web/"
  335. >download it here</a
  336. >)
  337. </p>
  338. <p>
  339. <b>Step 2:</b> Find a place on your page where you want the button to
  340. appear and include the following bit of HTML. Update the
  341. <code>manifest</code> attribute to point at your manifest file.
  342. </p>
  343. <pre>
  344. &lt;esp-web-install-button
  345. manifest="/static/firmware_build/manifest.json"
  346. >&lt;/esp-web-install-button></pre
  347. >
  348. <p>
  349. <b>Note:</b> ESP Web Tools requires that your website is served over
  350. <code>https://</code> to work. This is a Web Serial security
  351. requirement.
  352. </p>
  353. <p>
  354. If your manifest or the firmware files are hosted on another server,
  355. make sure you configure
  356. <a href="https://developer.mozilla.org/docs/Web/HTTP/CORS"
  357. >the CORS-headers</a
  358. >
  359. such that your website is allowed to fetch those files by adding the
  360. header
  361. <code
  362. >Access-Control-Allow-Origin: https://domain-of-your-website.com</code
  363. >.
  364. </p>
  365. <p>
  366. ESP Web Tools can also be integrated in your projects by installing it
  367. <a href="https://www.npmjs.com/package/esp-web-tools">via NPM</a>.
  368. </p>
  369. <h3 id="preparing-firmware">Preparing your firmware</h3>
  370. <p>
  371. If you have ESP32 firmware and are using ESP-IDF framework v4 or later,
  372. you will need to create a merged version of your firmware before being
  373. able to use it with ESP Web Tools. If you use ESP8266 or ESP32 with
  374. ESP-IDF v3 or earlier, you can skip this section.
  375. </p>
  376. <p>
  377. ESP32 firmware is split into 4 different files. When these files are
  378. installed using the command-line tool <code>esptool</code>, it will
  379. patch flash frequency, flash size and flash mode to match the target
  380. device. ESP Web Tools is not able to do this on the fly, so you will
  381. need to use <code>esptool</code> to create the single binary file and
  382. use that with ESP Web Tools.
  383. </p>
  384. <p>
  385. Create a single binary using <code>esptool</code> with the following
  386. command:
  387. </p>
  388. <pre>
  389. esptool --chip esp32 merge_bin \
  390. -o merged-firmware.bin \
  391. --flash_mode dio \
  392. --flash_freq 40m \
  393. --flash_size 4MB \
  394. 0x1000 bootloader.bin \
  395. 0x8000 partitions.bin \
  396. 0xe000 boot.bin \
  397. 0x10000 your_app.bin</pre
  398. >
  399. <p>
  400. If your memory type is <code>opi_opi</code> or <code>opi_qspi</code>,
  401. set your flash mode to be <code>dout</code>. Else, if your flash mode is
  402. <code>qio</code> or <code>qout</code>, override your flash mode to be
  403. <code>dio</code>.
  404. </p>
  405. <h3 id="manifest">Creating your manifest</h3>
  406. <p>
  407. Manifests describe the firmware that you want to offer the user to
  408. install. It allows specifying different builds for the different types
  409. of ESP devices. Current supported chip families are
  410. <code>ESP8266</code>, <code>ESP32</code>, <code>ESP32-C3</code>,
  411. <code>ESP32-S2</code> and <code>ESP32-S3</code>. The correct build will
  412. be automatically selected based on the type of the connected ESP device.
  413. </p>
  414. <pre>
  415. {
  416. "name": "ESPHome",
  417. "version": "2021.11.0",
  418. "home_assistant_domain": "esphome",
  419. "funding_url": "https://esphome.io/guides/supporters.html",
  420. "new_install_prompt_erase": false,
  421. "builds": [
  422. {
  423. "chipFamily": "ESP32",
  424. "parts": [
  425. { "path": "merged-firmware.bin", "offset": 0 },
  426. ]
  427. },
  428. {
  429. "chipFamily": "ESP8266",
  430. "parts": [
  431. { "path": "esp8266.bin", "offset": 0 }
  432. ]
  433. }
  434. ]
  435. }</pre
  436. >
  437. <p>
  438. Each build contains a list of parts to be installed to the ESP device.
  439. Each part consists of a path to the file and an offset on the flash
  440. where it should be installed. Part paths are resolved relative to the
  441. path of the manifest, but can also be URLs to other hosts.
  442. </p>
  443. <p>
  444. If your firmware is supported by Home Assistant, you can add the
  445. optional key <code>home_assistant_domain</code>. If present, ESP Web
  446. Tools will link the user to add this device to Home Assistant.
  447. </p>
  448. <p>
  449. By default a new installation will erase all data before installation.
  450. If you want to leave this choice to the user, set the optional manifest
  451. key
  452. <code>new_install_prompt_erase</code> to <code>true</code>. ESP Web
  453. Tools offers users a new installation if it is unable to detect the
  454. current firmware of the device (via Improv Serial) or if the detected
  455. firmware does not match the name specififed in the manifest.
  456. </p>
  457. <p>
  458. When a firmware is first installed on a device, it might need to do some
  459. time consuming tasks like initializing the file system. By default ESP
  460. Web Tools will wait 10 seconds to receive an Improv Serial response to
  461. indicate that the boot is completed. You can increase this timeout by
  462. setting the optional manifest key
  463. <code>new_install_improv_wait_time</code> to the number of seconds to
  464. wait. Set to <code>0</code> to disable Improv Serial detection.
  465. </p>
  466. <p>
  467. If your product accepts donations you can add
  468. <code>funding_url</code> to your manifest. This allows you to link to
  469. your page explaining the user how they can fund development. This link
  470. is visible in the ESP Web Tools menu when connected to a device running
  471. your firmware (as detected via Improv).
  472. </p>
  473. <p>
  474. ESP Web Tools allows you to provide your own check if the device is
  475. running the same firmware as specified in the manifest. This check can
  476. be setting the <code>overrides</code> property on
  477. <code>&lt;esp-web-install-button&gt;</code>. The value is an object
  478. containing a
  479. <code>checkSameFirmware(manifest, improvInfo)</code> function. The
  480. <code>manifest</code> parameter is your manifest and
  481. <code>improvInfo</code> is the information returned from Improv:
  482. <code>{ name, firmware, version, chipFamily }</code>. This check is only
  483. called if the device firmware was detected via Improv.
  484. </p>
  485. <pre>
  486. const button = document.querySelector('esp-web-install-button');
  487. button.overrides = {
  488. checkSameFirmware(manifest, improvInfo) {
  489. const manifestFirmware = manifest.name.toLowerCase();
  490. const deviceFirmware = improvInfo.firmware.toLowerCase();
  491. return manifestFirmware.includes(deviceFirmware);
  492. }
  493. };</pre
  494. >
  495. <h3 id="customize">Customizing the look and feel</h3>
  496. <p>
  497. You can change the colors of the default UI elements with CSS custom
  498. properties (variables), the following variables are available:
  499. </p>
  500. <ul>
  501. <li><code>--esp-tools-button-color</code></li>
  502. <li><code>--esp-tools-button-text-color</code></li>
  503. </ul>
  504. <p>There are also some attributes that can be used for styling:</p>
  505. <table>
  506. <tr>
  507. <td><code>install-supported</code></td>
  508. <td>Added if installing firmware is supported</td>
  509. </tr>
  510. <tr>
  511. <td>
  512. <code>install-unsupported</code>
  513. </td>
  514. <td>Added if installing firmware is not supported</td>
  515. </tr>
  516. </table>
  517. <h4>Replace the button and message with a custom one</h4>
  518. <p>
  519. You can replace both the activation button and the message that is shown
  520. when the user uses an unsupported browser or non-secure context with
  521. your own elements. This can be done using the <code>activate</code>,
  522. <code>unsupported</code> and <code>not-allowed</code> slots:
  523. </p>
  524. <pre>
  525. &lt;esp-web-install-button
  526. manifest="/static/firmware_build/manifest.json"
  527. >
  528. &lt;button slot="activate">Custom install button&lt;/button>
  529. &lt;span slot="unsupported">Ah snap, your browser doesn't work!&lt;/span>
  530. &lt;span slot="not-allowed">Ah snap, you are not allowed to use this on HTTP!&lt;/span>
  531. &lt;/esp-web-install-button>
  532. </pre
  533. >
  534. <h2>Why we created ESP Web Tools</h2>
  535. <div class="videoWrapper">
  536. <lite-youtube
  537. videoid="6ZMXE5PXPqU"
  538. videotitle="Why we created ESP Web Tools"
  539. videoStartAt="1255"
  540. ></lite-youtube>
  541. </div>
  542. <div class="footer">
  543. <div class="initiative">
  544. ESP Web Tools is a project by
  545. <a href="https://esphome.io">ESPHome</a>.<br />
  546. Development is funded by
  547. <a href="https://www.nabucasa.com">Nabu Casa</a>.
  548. </div>
  549. <div>
  550. ESP Web Tools is
  551. <a href="https://github.com/esphome/esp-web-tools">open source</a>.
  552. </div>
  553. </div>
  554. </div>
  555. <script>
  556. if (/iPad|iPhone|iPod/.test(navigator.userAgent)) {
  557. document.querySelector(".not-supported-i").classList.remove("hidden");
  558. }
  559. </script>
  560. </body>
  561. </html>