BeardedConti
This is excellent news, addition and contribution to Open source community!!! Thanks everyone for simplified setup process, new open standard and of course all of your work so far!!!
This is excellent news, addition and contribution to Open source community!!! Thanks everyone for simplified setup process, new open standard and of course all of your work so far!!!
Thank you very much for this report and your efforts in creating this project.
This is really slick! Here’s to hoping Firefox is able to get WebSerial and WebBluetooth running at some point, since I’m sure there’s a large overlap of people who use HomeAssistant and don’t trust Chrome and Chromium-based browsers.
I also assume that since iOS (i.e., Safari) doesn’t support WebSerial, then the Mac desktop app won’t support it, either.
Still, very impressive work, and the experience really looks like a massive step forward for usability.
Amazing news… 
It appears this is an official Nabu Casa project using a trademark of the Wi-Fi Alliance. Did anybody get clearance from them on the name “Improv Wi-Fi” ?
If not, there may be some trademark lawyers coming… 
Awesome! Now it’s time to make grow the esphome cookbook, this will show the people the power we have in our hands.
I am very impressed on the speed that this project has reached.
This. Is. Awesome! Congratulations for this amazing work!
I’m all new to the Home Assistant family, (I’ve received my Home Assistant Blue only last week), but I’m really impressed by everything that is possible with your tools and also really appreciative of the community around Home Assistant!
Keep up the good work and you will attract more and more new users to this community!
nothing about it being a nabu casa project, just initial funding
but then again lawyers be lawyers
From Our Brands | Wi-Fi Alliance
Brands for Public Use
Select brands and logos are offered license free and intended to be used widely throughout the
Wi-Fi ecosystem by Wi-Fi Alliance members, non-members, industry partners, media, and analysts to describe products, technology, network deployments, and operating system support.
Download the license-free logos.
|Wi-Fi®|Wi-Fi Multimedia™|
|Wi-Fi 4|Wi-Fi Optimized Connectivity™|
|Wi-Fi 5|Wi-Fi Protected Access®|
|Wi-Fi 6|Wi-Fi Protected Setup™|
|Wi-Fi 6E|Wi-Fi QoS Management™|
|Wi-Fi Agile Multiband™|Wi-Fi Vantage™|
|Wi-Fi Aware™|Wi-Fi ZONE™|
|Wi-Fi Data Elements™|WiGig|
|Wi-Fi Direct®|WMM®|
|Wi-Fi Easy Connect™|WPA™|
|Wi-Fi EasyMesh™|WPA2™|
|Wi-Fi Enhanced Open™|WPA3™|
|Wi-Fi HaLow™|Miracast®|
|Wi-Fi Home Design™|Passpoint®|
|Wi-Fi Location™|
This seems highly unlikely given their current position.
https://mozilla.github.io/standards-positions/#webserial
https://github.com/mozilla/standards-positions/issues/336
I can’t see the compile option in chrome. On the overflow menu I only see Clean MQTT, Clean compile files, and Delete.
I can though enter the docker container and compile from the commandline.
Indeed a step backwards.
Yeah it’s called “install” now 
Hitting “install” for a new board brings up a pop-up with choices for flash method.
Hitting “install” for a previously built board goes straight to OTA update even when the board is not available. No pop-up to allow downloading a .bin file. Have opened an issue.
2 replies
Yes. There is an issue open for that too:
Web Serial nor Web Bluetooth are web standards since both are only implemented by one browser engine, other browser engines consider them harmful due to the security issues they pose, and no standard is published, there is just a draft. See the text right in the specifications themselves:
It is not a W3C Standard nor is it on the W3C Standards Track.
The blog post talks about making ESPHome easier for non-technical users but those are the users more likely to be compromised by Web Serial/Bluetooth. It will be easy to trick people into flashing their ESP devices with malicious firmware which spies on their network/devices or exfiltrates data. Please remove the incorrect suggestion from the blog that these are a web standards.
It’s sad to see Home Assistant building on top of proprietary, insecure web APIs like these 
More than Web Serial, offering a mean for users who cannot understand “upload firmware” a way to, well, upload a random firmware from their browser on wifi-enabled ESP is a nice recipe for IoT bots
Great work by you guys! It is great to make this more accessible to more users. The more local control devices we create, the more of an alternative Home Assistant/ESPHome/‘wider local control ecosystem’ becomes to all the closed (but easy to use) systems out there.
Yes people can flash rogue firmwares to their ESP devices, as they can do already. It might be a bit easier now, but rogue firmware providers could provide the same options already, so eventually that would happen anyway.
1 reply
Trouble is, there is no accounting for stupidity.
Stupidity is a strong word, but definitely:
involves more control than clicking on a button on a webpage.
I doubt I’ll personally ever take the risk…
Let me guess. Chrome?? I find its caching getting in my way quite often.
Firefox.
This came at a perfect time for me! Recently got 3 WLED controllers die on me, new boards (QuinLED-ESP32 boards BTW ) arrived about an hour ago and they are already up and running, ‘installed’ straight from the WLED install page 
, I never imagined this would become so easy to do!
This is very cool for new adopters. Unfortunatly didnt’t work with my nodemcu (stuck on " Initializing…". Blue led start flashing, but actual firmware upload never gets past initialize). I can flash just ok with external tools
Yeah balloob mentioned on github they’re implementing a cache fix.
I find the emphasis on removing the term flashing very odd, when the page still refers to “erasing” and other technicalities (such as using Web Serial, etc.). Users are expected to still understand those things but not a fairly simple term such as flashing?
Flashing is a term very specifically used with firmware, and firmware is a class of code between hardware and software, and flashing is the process of writing the code to the kind of memory (family of memories) to such devices. How difficult is that to understand?
Nobody “erases” software from their PC (colloquially, people don’t speak like that). We uninstall software. So if you want to get rid of flashing, then also change erasing to uninstalling.
But these conventions have existed for decades. Why is it all of a sudden bothering people and is there this forcing move to change this part of the industry?
I’m not expecting an actual answer on any of this but wanted to voice my discontent. This is just weird.
PS: I’ll remain a massive supporter of ESPHome. I think it’s one of the most impressive projects I’ve ever seen. It’s brilliant.
Actually, I was confused and my screenshots are firefox 
But yeah, you have the same in Edge
Similar in Chrome for sure.
