index.html 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404
  1. <html>
  2. <head>
  3. <meta charset="utf-8" />
  4. <title>ESP Web Tools</title>
  5. <meta
  6. name="description"
  7. content="Easily allow users to flash new firmware for their ESP-devices on the web."
  8. />
  9. <meta name="viewport" content="width=device-width" />
  10. <meta property="og:title" content="ESP Web Tools" />
  11. <meta property="og:site_name" content="ESP Web Tools" />
  12. <meta
  13. property="og:url"
  14. content="https://esphome.github.io/esp-web-tools/"
  15. />
  16. <meta property="og:type" content="website" />
  17. <meta
  18. property="og:description"
  19. content="Easily allow users to flash new firmware for their ESP-devices on the web."
  20. />
  21. <meta
  22. property="og:image"
  23. content="https://esphome.github.io/esp-web-tools/static/social.png"
  24. />
  25. <meta name="twitter:card" content="summary_large_image" />
  26. <meta name="twitter:title" content="ESP Web Tools" />
  27. <meta
  28. name="twitter:description"
  29. content="Easily allow users to flash new firmware for their ESP-devices on the web."
  30. />
  31. <meta
  32. name="twitter:image"
  33. content="https://esphome.github.io/esp-web-tools/static/social.png"
  34. />
  35. <style>
  36. body {
  37. font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI",
  38. Roboto, Ubuntu, sans-serif;
  39. padding: 0;
  40. margin: 0;
  41. line-height: 1.4;
  42. }
  43. .content {
  44. max-width: 600px;
  45. margin: 0 auto;
  46. padding: 12px;
  47. }
  48. .project .logo {
  49. float: right;
  50. }
  51. .project .logo img {
  52. height: 50px;
  53. }
  54. a {
  55. color: #03a9f4;
  56. }
  57. .videoWrapper {
  58. position: relative;
  59. padding-bottom: 56.25%; /* 16:9 */
  60. height: 0;
  61. margin-bottom: 25px;
  62. background: #000;
  63. }
  64. .videoWrapper iframe {
  65. position: absolute;
  66. top: 0;
  67. left: 0;
  68. width: 100%;
  69. height: 100%;
  70. }
  71. .content pre {
  72. max-width: 100%;
  73. overflow-y: scroll;
  74. }
  75. .footer {
  76. margin-top: 24px;
  77. border-top: 1px solid #ccc;
  78. padding-top: 24px;
  79. text-align: center;
  80. }
  81. .footer .initiative {
  82. font-style: italic;
  83. margin-top: 16px;
  84. }
  85. table {
  86. border-spacing: 0;
  87. }
  88. td {
  89. padding: 8px;
  90. border-bottom: 1px solid #ccc;
  91. }
  92. @media (prefers-color-scheme: dark) {
  93. body {
  94. background-color: #333;
  95. color: #fff;
  96. }
  97. a {
  98. color: #58a6ff;
  99. }
  100. }
  101. </style>
  102. <script module>
  103. import(
  104. // In development we import locally.
  105. window.location.hostname === "localhost"
  106. ? "/dist/web/install-button.js"
  107. : "https://unpkg.com/esp-web-tools@4.0.2/dist/web/install-button.js?module"
  108. );
  109. </script>
  110. </head>
  111. <body>
  112. <div class="content">
  113. <h1>ESP Web Tools</h1>
  114. <p>
  115. ESP Web Tools is a set of open source tools to allow working with ESP
  116. devices in the browser.
  117. <a href="https://github.com/esphome/esp-web-tools"
  118. >The code is available on GitHub.</a
  119. >
  120. </p>
  121. <p>
  122. To try it out and install
  123. <a href="https://esphome.io">ESPHome</a> on an ESP, connect it to your
  124. computer and hit the button:
  125. </p>
  126. <esp-web-install-button
  127. manifest="static/firmware_build/manifest.json"
  128. ></esp-web-install-button>
  129. <p>
  130. <i>
  131. Note, this only works in desktop Chrome and Edge. Android support
  132. should be possible but has not been implemented yet. If you don't see
  133. your ESP device, you might miss <a href="#drivers">drivers</a>.
  134. </i>
  135. </p>
  136. <p>
  137. This works by combining
  138. <a
  139. href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_API"
  140. >Web Serial</a
  141. >
  142. with a manifest which describes the firmware. It will automatically
  143. detect the type of the connected ESP device and find the right firmware
  144. files in the manifest.
  145. </p>
  146. <div class="videoWrapper">
  147. <iframe
  148. width="560"
  149. height="315"
  150. src="https://www.youtube-nocookie.com/embed/k88BS8zgWq0"
  151. title="YouTube video player"
  152. frameborder="0"
  153. allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
  154. allowfullscreen
  155. ></iframe>
  156. </div>
  157. <h2 id="used-by">Products using ESP Web Tools</h2>
  158. <div class="project">
  159. <a href="https://wled.me" class="logo"
  160. ><img src="static/logos/wled.png" alt="WLED logo"
  161. /></a>
  162. <h3>WLED</h3>
  163. <p>
  164. Fast and feature-rich firmware to control NeoPixel (WS2812B, WS2811,
  165. SK6812) LEDs and SPI based chipsets like the WS2801 and APA102.
  166. </p>
  167. <p>
  168. <a href="https://install.wled.me" target="_blank"
  169. >Installation Website</a
  170. >
  171. </p>
  172. </div>
  173. <div class="project">
  174. <a href="https://tasmota.github.io" class="logo"
  175. ><img src="static/logos/tasmota.svg" alt="Tasmota logo"
  176. /></a>
  177. <h3>Tasmota</h3>
  178. <p>
  179. Firmware with easy configuration using webUI, OTA updates, automation
  180. using timers or rules, expandability and entirely local control over
  181. MQTT, HTTP, Serial or KNX.
  182. </p>
  183. <p>
  184. <a href="https://arendst.github.io/Tasmota-firmware/" target="_blank"
  185. >Installation Website</a
  186. >
  187. </p>
  188. </div>
  189. <div class="project">
  190. <a href="http://www.espeasy.com/" class="logo"
  191. ><img src="static/logos/espeasy.png" alt="ESPEasy logo"
  192. /></a>
  193. <h3>ESPEasy</h3>
  194. <p>Easy MultiSensor device based on ESP8266/ESP32.</p>
  195. <p>
  196. <a href="https://td-er.nl/ESPEasy/" target="_blank"
  197. >Installation Website</a
  198. >
  199. </p>
  200. </div>
  201. <div class="project">
  202. <a href="https://esphome.io" class="logo"
  203. ><img src="static/logos/esphome.svg" alt="ESPHome logo"
  204. /></a>
  205. <h3>ESPHome</h3>
  206. <p>
  207. No-code platform for ESP devices. Uses ESP Web Tools in their
  208. dashboard to install ESPHome on devices.
  209. </p>
  210. <p>
  211. <a href="https://esphome.io" target="_blank">Website</a>
  212. </p>
  213. </div>
  214. <h2 id="add-website">Adding ESP Web Tools to your website</h2>
  215. <p>
  216. To add this to your own website, create a manifest and add the button to
  217. your website. Make sure you update the manifest attribute to point at
  218. your manifest.
  219. </p>
  220. <p>
  221. You can import ESP Web Tools directly from the unpkg CDN or
  222. <a href="https://unpkg.com/browse/esp-web-tools/dist/web/"
  223. >download the files</a
  224. >
  225. and put them on your website.
  226. </p>
  227. <pre>
  228. &lt;script
  229. type="module"
  230. src="https://unpkg.com/esp-web-tools@4.0.2/dist/web/install-button.js?module"
  231. >&lt;/script>
  232. &lt;esp-web-install-button
  233. manifest="static/firmware_build/manifest.json"
  234. >&lt;/esp-web-install-button></pre
  235. >
  236. <p>
  237. Your website needs to be served over <code>https://</code>. If your
  238. manifest is hosted on another server, make sure you configure
  239. <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS"
  240. >the CORS-headers</a
  241. >
  242. for your manifest and firmware files such that your website is allowed
  243. to fetch those files by adding the header
  244. <code
  245. >Access-Control-Allow-Origin: https://domain-of-your-website.com</code
  246. >.
  247. </p>
  248. <p>
  249. ESP Web Tools can also be integrated in your projects by installing it
  250. via NPM:<br />
  251. <code>npm install --save esp-web-tools</code>
  252. </p>
  253. <h3 id="manifest">Creating your manifest</h3>
  254. <p>
  255. ESP Web Tools manifest describe the firmware that you want to install.
  256. It allows specifying different builds for the different types of ESP
  257. devices. Current supported chip families are <code>ESP8266</code>,
  258. <code>ESP32</code>, <code>ESP32C3</code> and <code>ESP32S2</code>. The
  259. correct build will be automatically selected based on the type of the
  260. ESP device we detect via the serial port.
  261. </p>
  262. <pre>
  263. {
  264. "name": "ESPHome",
  265. "version": "2021.11.0",
  266. "home_assistant_domain": "esphome",
  267. "new_install_skip_erase": false,
  268. "builds": [
  269. {
  270. "chipFamily": "ESP32",
  271. "parts": [
  272. { "path": "bootloader.bin", "offset": 4096 },
  273. { "path": "partitions.bin", "offset": 32768 },
  274. { "path": "ota.bin", "offset": 57344 },
  275. { "path": "firmware.bin", "offset": 65536 }
  276. ]
  277. },
  278. {
  279. "chipFamily": "ESP8266",
  280. "parts": [
  281. { "path": "esp8266.bin", "offset": 0 }
  282. ]
  283. }
  284. ]
  285. }</pre
  286. >
  287. <p>
  288. Each build contains a list of parts to be flashed to the ESP device.
  289. Each part consists of a path to the file and an offset on the flash
  290. where it should be installed. Part paths are resolved relative to the
  291. path of the manifest, but can also be URLs to other hosts.
  292. </p>
  293. <p>
  294. If your firmware is supported by Home Assistant, you can add the
  295. optional key <code>home_assistant_domain</code>. If present, ESP Web
  296. Tools will link the user to add this device to Home Assistant.
  297. </p>
  298. <p>
  299. By default a new installation will erase the entire flash. If you want
  300. to skip this step, set the optional key
  301. <code>new_install_skip_erase</code> to <code>true</code>. ESP Web Tools
  302. considers it a new installation if it is unable to detect the current
  303. firmware of the device (via Improv Serial) or if the detected firmware
  304. does not match the name specififed in the manifest.
  305. </p>
  306. <h3 id="improv">Wi-Fi provisioning</h3>
  307. <p>
  308. ESP Web Tools has support for the
  309. <a href="https://www.improv-wifi.com/serial"
  310. >Improv Wi-Fi serial standard</a
  311. >. This is an open standard to allow configuring Wi-Fi via the serial
  312. port.
  313. </p>
  314. <p>
  315. If Improv is supported, a user will be guided to connect the device to
  316. the network after installation. It also allows the user to connect
  317. already installed devices and re-configure the wireless network
  318. settings.
  319. </p>
  320. <h3 id="customize">Customizing the look and feel</h3>
  321. <p>
  322. There are multiple options to change the look and feel of the button and
  323. other elements.
  324. </p>
  325. <h4>Change colors</h4>
  326. <p>
  327. You can change the colors of the default UI elements with CSS custom
  328. properties (variables), the following variables are available:
  329. </p>
  330. <ul>
  331. <li><code>--esp-tools-button-color</code></li>
  332. <li><code>--esp-tools-button-text-color</code></li>
  333. </ul>
  334. <p>There are also some attributes that can be used for styling:</p>
  335. <table>
  336. <tr>
  337. <td><code>install-supported</code></td>
  338. <td>Added if installing firmware is supported</td>
  339. </tr>
  340. <tr>
  341. <td>
  342. <code>install-unsupported</code>
  343. </td>
  344. <td>Added if installing firmware is not supported</td>
  345. </tr>
  346. </table>
  347. <h4>Replace the button and message with a custom one</h4>
  348. <p>
  349. You can replace both the activation button and the message that is shown
  350. when the user uses an unsupported browser or non-secure context with
  351. your own elements. This can be done using the <code>activate</code>,
  352. <code>unsupported</code> and <code>not-allowed</code> slots:
  353. </p>
  354. <pre>
  355. &lt;esp-web-install-button
  356. manifest="static/firmware_build/manifest.json"
  357. >
  358. &lt;button slot="activate">Custom install button&lt;/button>
  359. &lt;span slot="unsupported">Ah snap, your browser doesn't work!&lt;/span>
  360. &lt;span slot="not-allowed">Ah snap, you are not allowed to use this on HTTP!&lt;/span>
  361. &lt;/esp-web-install-button>
  362. </pre
  363. >
  364. <h3 id="drivers">USB Serial Drivers</h3>
  365. <p>
  366. If the serial port is not showing up, your computer might be missing the
  367. drivers for the USB serial chip used in your ESP device. These drivers
  368. work for most ESP devices:
  369. </p>
  370. <ul>
  371. <li>
  372. CP2102 (square chip):
  373. <a
  374. href="https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers"
  375. >driver</a
  376. >
  377. </li>
  378. <li>
  379. CH341:
  380. <a
  381. href="https://github.com/nodemcu/nodemcu-devkit/tree/master/Drivers"
  382. >driver</a
  383. >
  384. </li>
  385. </ul>
  386. <div class="footer">
  387. <div>
  388. ESP Web Tools –
  389. <a href="https://github.com/esphome/esp-web-tools">GitHub</a>
  390. </div>
  391. <div class="initiative">
  392. ESP Web Tools is a project by
  393. <a href="https://esphome.io">ESPHome</a>.<br />
  394. Development is funded by
  395. <a href="https://www.nabucasa.com">Nabu Casa</a>.
  396. </div>
  397. </div>
  398. </div>
  399. </body>
  400. </html>