Видео

Next week!! Just testing the last pieces with Patreons!!! 😊

Fishnets for fishermen?? 😂😂😂

Very true, I should edit to say 'save hours of banging your head, to give you hours more to headbang...'... 😂

🤘🤘😁

😂😂 I know the feeling, it's tough to narrow down - I had even more on the long list, I suspect the 84 wonders of the world might not have been as concise..... 😂

Link is in the description!! 😊

This is a great example! Love it! It's also a common thing I hear about that fridges temperature management is a bit ropey, so it'd be quite interesting to see how a temp sensor measures up to the fridge's perceived temperature! Plus how long it takes to re-chill the fridge every time you open it! Endless fun!

Glad it helped!

Yes, that's a nice idea - I've done this (and also solar panels) - one for future!

Also I enjoy your tips on home automation

POINTS TO YOU!!!! 💯💯💯 I thought no one was going to point that out (I'd thought of doing a death ray and an ice beam to be really obvious!)

I appreciated it, it was subtle enough that if you know you know but not hit you over the head obvious.

Just to share, my most recent home automation is to flash a light in my living room when the washer is done and ready to be changed.

You can join my Evil League of Evil any day.... 😉

Hey, think this is the one? amzn.to/45TvOx8

@@handsonkatie Thak you very much

Hey, thanks!

Hey, great point - in later videos I touch on the air quality sensors that I'm looking to install, these track pm1-10, VOCs and more, so I'm going to use these as a proxy to then automatically vacuum the room, alert to dust levels. I'm not sure how cigarette smoke would be tracked, but it'd be an interesting test!

Not for a beginner tour of esphome/esp chips, it has it's place, but wrong stage....!

Genius idea!!! 😈

If you really want to freak somebody out go. To developer tools then services and type in "TTS" and choose the text to speech option. A list of speakers will show up if you have any Chromecast or other smart speakers. Then type in whatever you want it to say, unfiltered. The best part is it works on soundbars so it's fun having it say something while watching TV with my friend and his wife because they have no idea what's happening. I pretend like I didn't hear a thing.

Great solution - pico's are excellent little chips too!

It doesn't take me more than 15 minutes to update roughly 25 devices. Now, I am using a mini PC with a roughly 3 year old AMD chip and DDR5 RAM with an m.. 2 SSD so not what you would get on a raspberry pi but if you have 80 devices you should be running it on x86 if you aren't already. It takes me 2 minutes to do a full backup over the network and my backups are over 2GB because I really need some cleanup. I do agree though, if you watch an update through the CLI it looks like it's doing a new install, almost like it cleans the existing build files. It should at least be able to tell revisions because it doesn't have to download and completely recompile for some minor changes. At the same time most are doing this in their free time so it's hard to complain.

@@JoshFisher567that’s waaaay more horsepower than a proper “home automation” / embedded system engineering design should need to accomplish the updating of sensor and switch devices that have teeny tiny flash storage. What’s really happening is two-fold, main ESPHome doesn’t lend itself well to building generic binaries nor have any good way for the build system to look at a config and only build/rebuild the portions needed. Secondarily, you are correct kinda… the integration is tracking and entire build tree per device and sharing none is the compiled objects between them, even identical hardware. Having done commercial embedded system work professionally for a while long ago, this isn’t how you design an embedded device build system. You also don’t build binaries on the control boxes. Heh. It’s an interesting problem they have. Both upstream and the integration. Example: Why throw a warning just because a dot release came out for the overall project upstream, that likely doesn’t even affect your hardware/use case. But the current way it’s architected - the integration has no way to know that. Because upstream has not provided a way to look at the config file and only rebuild needed objects. It’s seriously goofy. Nabu Casa is trying to make a more professional automation platform it seems, but paired up with ESPHome and integrated it the most “build your binaries multiple times monthly” release model possible. BTW they do pay at least one ESP dev, I think they announced two some time ago? The integration seems to be mainly maintained by one of those devs. But it’s pretty clear they haven’t worked in pro embedded (microcontroller) systems. Well until now I guess. But no mentor to guide them in the ways of tiny fast updating binary releases. Fun to chat about. I don’t see it getting better without at least 3 devs having it as a full time goal in a pro shop. BTDT. It also would have to be a goal, and I don’t see the willpower from above at Nabu wanting to move ESPHome away from the nerd/hacker mentality toward a packaged product. Shrug… dunno. It’s fun to play with but if I want fast updates and embedded design architecture - that’s still Tasmota. ESPHome is the Wild West compared to the goals of the lead Tas devs. Not sure what Nabu Casa really wants to do with ESPHome but it’s not a fully baked solution for “home automation” device code. HA overall kinda needs an “LTS” release cycle for those who want to set and forget it. Far too many updates with breaking changes not caught in regression nor documented. The ESPHome devs seem to be caught up in the release cycle designed for the UI. Embedded devices simply shouldn’t need that fast of a cycle. And sure, users can learn to ignore the warning in the UI but that’s bad from a “training the user to avoid important things” standpoint. Even monthly UI releases with major changes are kinda “too much” for any non-tinkering folk to take it serious as a product. Again… shrug. Fun to discuss as an old embedded product guy. Unique. I’d say. In the embedded world.

@@NatesRandomVideo I see what you're saying and you obviously have the background to recognize this and yes, Nabu Casa does have full time payed devs, there just isn't a lot of them. The guy who wrote microwakeword for voice assistants was a contributed and saw it as a challenge because he heard the main voice guy on a podcast saying that was their ultimate goal and took it as a challenge. That's not a knock on the main voice guy as he had written Rhasspy before moving to Nabu. On the flip side, having worked for a software development company that makes extremely niche complicated software, there have been times where you start something new like ESPHome, make some poor decisions from the start and have to either live with them, which seems what they are doing, or rewrite stuff from scratch, possibly changing things in a way that would require removing and adding all devices back. I'm. Not saying that's the issue but I have seen it before and once it's in a final release and in customers hands, it's a much harder problem to fix for that reason. Sometimes you just can't please everyone. I work at a company that makes software for state DOTa and there were always complaints about performance. The devs started storing stuff in Redis cache (memory) which made it way faster but now DBA's are mad because their custom triggers or updates don't work or aren't because if they do an update via the DB directly, when a user saves in the UI it writes what's in the Redis cache to the DB, overwriting the DBA's update. In the end we ended up giving them the option to choose what tables to use Redis so now are application can be slow in some areas and faster in others on a per agent by basis because they have different needs and cache different tables which is over 800 tables. The more complicated software gets the harder it is to make everyone happy.

@@JoshFisher567 yup, BTDT type of thing, too. I think ESPHome could rewrite the build process "relatively" easily without touching how devices are actually working at the end product -- but like you said, limited resources, so live with it. I see they announced they donated the entire project to their Foundation -- for better or worse, going forward... will be interesting to see where it goes. Software so easily becomes a mess without an up-front plan, and us old guys who know the gotchas usually aren't appreciated much (and cost too much) for small companies to bother. Then they get big, and go thru a lot of unnecessary pain re-writing the avoidable stuff! Ha... circle of life, and all that! Cheers! Fun chat!

@@NateDuehr last thing I wanted to add. It's also probably the 2nd best example of the power of Open source with Linux obviously being the best. It's hard to think that it was created by one guy back in 2012, or that's when he uploaded his first version to GitHub, at the time it wasn't an OS or supervisor, below was a post by the guy who started it. Before HA, as you know, to get that level of customizability you had to pay for it and it's out of reach for the majority of people but there will always be those willing to pay for a professional company because they got the money to and the obvious advantages like having the company set everything up, add devices and fix issues. I started using it right after Nabu Casa was foed and you got an external secure domain for 6.dollars a month. People would complain even though when you pointed out stuff like it's free if you generate your own self signed ASL cert and want toanage all the network stuff for external use. Then they would say it's to technical because setting up an SSL certificate using let's encrypt isn't a click next, next type of thing. Neither is port forwarding and the other network stuff. So while they became big in a sense they never really milked their users and could have easily taken the money and run as I'm sure they have had lots of offers over the years and I give them props for sticking to their original vision. Most would take the money. Nvidia recently approached them to build a local LLM just for HA because they all use HA. Now, I'm not sure where AI will go or if it's something I would ever use but the fact that Nvidia has been doing most of the work with HA devs is them asking questions while they port everything to GPU based as they want to use their Jetson lineup as both the HA server and LLM or separate with the Jetson only being the local LLM. That and they already said their next hardware device is going to be a Z-Wave adapter. I thought that was an odd choice but didn't know how amazing the range is. They said when using "old" Z-Wave with a "new" Z-Wave adapter (I'm assuming new means better range and other stuff) they were able to communicate outside at 0.7 miles. They were at a Z-Wave conference they tested and they're was no place in the hotel where they couldnt connect directly to one another. That could have some use cases as I never used Z-Wave before. Not as good as LORA but way cheaper. Not toention they currently support 2812 integrations (without HACs) so while I agree they could fix quite a few things in ESPHome, that's a lot to maintain outside just ESPHome. Pretty amazing that MS Visual Studio is the only open source project larger than HA. That and I believe there are more installs out there then people think. The numbers they release are only from people who manually opted into analytics. I don't believe you are prted during the setup, you have to manually go into System and turn it on. <-- It’s 2012 and I was a visiting scholar at the University of California, San Diego working on finishing my Master thesis. It’s back then when the first Philips Hue product hit the market: a hub and 3 light bulbs for around $200. The hub had something that would change my life: it had a local API that allowed local control. I’ve always been really into programming and so I immediately started toying with the Hue API in Python, my language of choice. There is something very satisfying about making things change in the real world from your code. On September 17, 2013 I decided that this playground had evolved into something that others could use too, and pushed the first version of Home Assistant to GitHub. The original audience of Home Assistant was die-hard tech nerds. You had to install Python, Home Assistant and all of its dependencies manually. When Pascal Vizeli introduced the Home Assistant Operating System 1 (then called hass.io) the first step was made to bring Home Assistant to non-technical users. Now users could install Home Assistant on an SD card, put it into a Raspberry Pi and have a fully working home automation hub that can update via the user interface. Users could fully focus on automating their home. That and that Nabu Casa was started by 10 people. When Home Assistant turned five, we launched Nabu Casa 5. The goal of Nabu Casa is to make the development of Home Assistant sustainable. Nabu Casa came just in time, as it gave our developers some time to breathe. We had to grow to around 10 people before both Pascal and I felt like all our day-to-day tasks could be shared. There are no investors and development of Home Assistant is sustainable. Home Assistant is the 2nd most active open source project on GitHub (source 30). Running a project this large requires a lot of administration, processes, structure and maintenance. This is provided by full-time Nabu Casa employees so that contributors can focus on the fun part: building Home Assistant.

Well I admit it's quicker with several printers.... ;) I just printed over a few weeks basically - print costs were pretty low (saw a great deal on filament for £7 a kg) - so buy bulk and just take your time I'd say! All the way through I was sense-checking and significantly cheaper than the usual commercial boxes and solutions!

So true!

Love it! Really creative idea - don't know mosquitoes well enough, but sounds very possible - indeed I'd imagine they've got a distinct sound pitch of their irritating whine! Having separate sensors would also let you locate as you say!! You'd just need to research/test different mics to make sure you got the right sensitivity - but could be a neat idea to have it alert you when one is detected!

@@handsonkatie Not just sound an alert... but ⚡ *zap* ⚡ the mosquito by activating a _(relatively low-power)_ *Tesla coil* ?! 🤓

Check the description - link there! 😉

You are so welcome!

Thank you honestgoat! Great comment and yes you're completely right, I was trying to not get too deep into the detail on this to keep it accessible, but there are various challenges and as you say you need to pick your ESP32/battery pack carefully, plus there's usually workarounds but these naturally depend on your use case (eg if outside then a solar panel as a boost charger works great), but probably a video in its own right!