Видео

Do you mean C++ component or in YAML? Both are in the pipeline, I currently have a 54 tutorials pipeline, the YAML one is coming soon, the C++ one is a beast of its own and will come much later

@@homeautomatorza Great, it's yaml.

I changed that see the newer videos

Hi Lars, I think I know why you say it's differant, I may not have explained it as deeply as in the tutorial. It's the same function, both use packages. This is also why I wanted to do this series by the way, to clarify the methodology and the code. I hope this clears up any confusion. -- Pascal

@@homeautomatorza Almost sounds as if this is built by humans ;-) Thanks for the explanation.

Working on it 😄

Glad you found it useful.

Thank you Philip. I hope it’s all clear enough, we will go into samples from the next tutorial in this series.

That is quite a rant sir. You have the right to your opinion, however, calling it “clickbait” is maybe a bit much. My channel is an ESPHome channel, I introduce it as such, I do not see where the problem is. And for your information, clickbait is to create money, this channel costs me money. Have a great day, Pascal.

@homeautomatorza Just said that to hopefully help You and others not waste time. As I said in the comment, there's not enough context in the title which is the first thing you see when you are choosing videos to watch, and I hope the comment helps you form better titles, especially for a new audience. Neither the title nor the channel name is directly linked to what you're trying to say. I thought I was going to see general coding tips and trics, as the title says. Not specifially for ESPs, which I have little interest in now, hence it wasted more of my time than I would have liked, hence the comment. Content itself was useful for what it was. Hope you have a wonderful day too!

Thanks Lars, the next one is going to interest you I think.

Thanks, that would be great. I've done the configuration into Home Assistant for the Home Assitant plugin but ESPHome is another beast. Anyways, part 2 is comming soon and it's going to answer a lot of your questions I did not have answers to in the live stream.

Thanks for sharing the link. The modular part is only one part of what I am doing by the way.

Hi Dan, Most people would probably want to dedicate a [physical] machine to run docker, this is why I took this approach for the tutorial. I have a lot of docker containers running inside of LXC containers, but this is a bit more advanced. If you want to play around this guy tteck.github.io/Proxmox/ has a bunch of scripts that will install virtual machines or LXCs for you. As for the off grid, I can't help you much.

@@homeautomatorza Thanks for your answer, I have been using those scripts already, they work great. I say he had one for installing Docker onto Proxmox. The only factor with being off grid is power consumption. I have a huge lithium/solar system, but still would like to limit the servers to just one for my homelab...if possible.

Thanks Manu I’ve only been around for a few months though. There is much more coming and the next series is an extension of this one, but we will be going into more advanced techniques and additional properties, I hope you will enjoy it as much as I do preparing and recording them. And don’t hesitate to ask questions. Love and respect from South Africa

I think I only use the Advanced SSH and Web Terminal. I cannot remember why though

@@homeautomatorza yea, will have to dig into the logs someday, when i get some energy..heh

Forgot to mention, but I'm still using ha api connection check on esphome device boot, because I have plenty of LCD-screens and it will turn of the backlight on my code when connection is ok. I can see immediately, if connection fails-> esphome: name: ${esphome_name} platform: ESP8266 board: d1_mini on_boot: priority: -10 then: - wait_until: api.connected: - logger.log: API is connected!

Thanks Marko, I am currently working on a more advanced and modular version of this tutorial, it will include a lot of tips too. Now I need my voice back so I can record them.

Correct, the fix is explained here ruclips.net/video/wcUDYzLFjQ0/видео.html

@@homeautomatorza Thank you!

Thank you for the great suggestion. It’s been on my list for sometime now, but being that it is an advanced project it will take time to get there.

Thank you

Glad I could help

Steve and I were working on the new code during the live stream, which wasn’t intended as a tutorial. My streams tend to be a bit chaotic-I don’t script them extensively because I enjoy the spontaneity and unpredictability. However, we did discuss code reusability with Steve during the livestream. I’m excited to announce that I’m preparing a comprehensive tutorial series. It’ll delve deeper into the topics we touched on during the live stream. I’ve planned at least seven tutorials, ranging from quarter-hour to half-hour per video. Two of them are already scripted-I just need to find time to record them. Also, stay tuned for the ESPHome Weather Station project! It’ll incorporate the new techniques we discussed in the live stream and more. This content will be labeled as intermediate and I’ve already scripted one episode. If you’re starting from scratch, check out my existing playlist: Creating a Room Sensor from Scratch. It’s designed specifically for those entering the ESPHome space (ruclips.net/p/PLJ3MNJX_MOUkHnK4C65lJr4klT58Yi1_W), the next tutorial in this series is recorded-I’ll be busy editing it, so keep an eye out for it. Thank you for the feedback-I’ll definitely consider structuring my livestreams better in the future.

Thank you, a revised version of that is coming soon.

Hi there, To answer your question, most of my tutorials are for beginners, and until now, I did not see the use of introducing Studio Code server or desktop. If you watched the last live stream, that is all I used to do the YAML. The compilation and upload are done in ESPHome though. The ESPHome studio plugin is a bit dated and throws errors where there are none. Most of my future tutorials will be using a modular technique, making studio code a must, so you will see plenty of it. Ps, the live stream was a lot of fun and the input from Deliberate Geek as well as all that were there was great, I think it’s a great watch but it’s over 2 hours long. So I am preparing a series of tutorials around the discussion we had, all using advanced methods and Studio Code. On a personal note, I did not code for many years either when I went down the IoT path in C++, which I had used in my professional life. Then I discovered the world of ESPHome and YAML, it’s really not that complicated, if you have dealt with JSON or XML, you’ll get it quickly. It’s a configuration file standard, that’s it. If your tabs are correct and you config properties are right, you’ll have no issues. Thanks for watching and many good things are coming.

@@homeautomatorza Thanks for the quick response. My coding ended about 15 yrs ago when I developed a huge database with MS Visual Basic for the fronted to run a SQL Database for BHP Billiton Mining here in Canada. So this is all "new" but still familiar. PS...I have a ton of friends in SA from my mining days and even got to spend about a month in Pretoria back in my Military days flying CC130 Hercs all over SA. I'm currently binge watching your videos, so 1. your watch time will go up a ton and 2. I'm looking forward to the Visual Studio Code stuff. Hopefully I can join a live stream at some point. My challenge to myself for learning all this stuff is to build out our RV to a "Smart Home" using as many DIY devices as possible.

Firstly, thank you for your binge-watching! 🙌 The reason I haven’t posted anything new lately is that I’ve been continuously refining the modular code. As of today, I believe I’ve nailed it. Now, about the next room sensor tutorial: It’s already recorded, but here’s the catch-I’ve made numerous references to the new code without providing context. That’s where my hesitation comes in. I’m considering re-recording the coding section to align it with the current monolithic approach. Then, I’ll introduce the modular method in a fresh tutorial series titled ‘Coding Practices, Tips, and Tricks.’ I’ve got seven tutorials planned for that series, and one of them is already written. As for the intermediate-level ESPHome Weather Station tutorials, I’m seriously contemplating a delay. I want to ensure that the ‘Coding Practices, Tips, and Tricks’ series has progressed far enough for us to confidently dive into those advanced techniques. Thanks for your patience, and stay tuned for more exciting content!

@@homeautomatorza Thanks for the quick response. You should consider doing a Studio Code Server video with how to switch back and forth between it and ESPHome to compile. Some folks may not understand how to move the files back and forth or why. During the live stream you had multiple Tabs open and it cold get confusing with what software you were doing what. Probably could be one of your Quickie Videos. You touched some of the details on your install video but was missing the whole concept of compiling in ESPHome instead of Studio Code.

A full series of tutorials is coming for the modular techniques in which I explain what you’ve pointed out. It’s difficult to plan a live stream as you never know what will happen and truthfully I like it that way. The next live stream is some times away but I’ll structure it better. I am still very new at this. Now I need my voice back so I can record 😟

Thank you

I am not too sure what you getting at.

Thanks

Hi Lars, I thought I'd give you the long answer from my computer, here it is: There is no cheating, there are cases where this methodology and framework may not fit the requirements, any methodologies has it's exceptions. I am currently scripting the methodology in multiple tutorials for an easier learning experience and with more information from the livestream questions and Steve's additions. I highlight that this is the way I do it, but it may not be for everyone, it's a framework to adapt to your need and your way of thinking. Remember, you need to adapt it to what works for you. Have a blast. -- Pascal

Thank you Larry, maybe one day you can pop into the channel and bring us some of your wisdom.

@@homeautomatorza ROFL, I don't know about wisdom, but i have some ideas ever once in a while. 😀

I thought of editing it but there is so much information I opted to leave it as is. And there is nothing wrong with going at 2x, I often do it. And yes, vars opens a different way to do things too.

Thank you for the feedback.

Wait until Saturday’s livestream where I’ll show more advanced ways to do the code and stream line it even more. I’ll check the link, thanks.

If you use OTA, yes.

I am not sure I understand, but here are 2 things you can try 1. Is device_internal_name defined? 2. Are you typing as follows: id: ${device_internal_name}_status Lastly, are you doing this in ESPHome or Home Assistant ? The code that I have on GitHub is fully tested, except for the ota change there is nothing else that should break it. Can you maybe paste the full error, so I can help?

Sure will do, am using in esphome in home assistant. Will message you in the morning, many thanks, Michael

@@homeautomatorza I have a screen shot of the error code and the actions that have run before it. is there anyway i can forward this to you at all please ?

@@homeautomatorza INFO ESPHome 2024.6.6 INFO Reading configuration /config/esphome/foundation-device.yaml... WARNING Found '${device_internal_name}_status' (see binary_sensor->0->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_wifi_signal_sensor' (see sensor->0->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_uptime_sensor' (see sensor->1->name) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_uptime_human' (see sensor->1->on_raw_value->then->0->text_sensor.template.publish->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found 'int seconds = round(id(${device_internal_name}_uptime_sensor).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? to_string(days) + "d " : "") + (hours ? to_string(hours) + "h " : "") + (minutes ? to_string(minutes) + "m " : "") + to_string(seconds) + "s") ).c_str();' (see sensor->1->on_raw_value->then->0->text_sensor.template.publish->state) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_ip_address' (see text_sensor->0->ip_address->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_connected_ssid' (see text_sensor->0->ssid->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_mac_address' (see text_sensor->0->mac_address->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_uptime_human' (see text_sensor->2->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_status' (see binary_sensor->0->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_wifi_signal_sensor' (see sensor->0->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_uptime_sensor' (see sensor->1->name) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_uptime_human' (see sensor->1->on_raw_value->then->0->text_sensor.template.publish->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found 'int seconds = round(id(${device_internal_name}_uptime_sensor).raw_state); int days = seconds / (24 * 3600); seconds = seconds % (24 * 3600); int hours = seconds / 3600; seconds = seconds % 3600; int minutes = seconds / 60; seconds = seconds % 60; return ( (days ? to_string(days) + "d " : "") + (hours ? to_string(hours) + "h " : "") + (minutes ? to_string(minutes) + "m " : "") + to_string(seconds) + "s") ).c_str();' (see sensor->1->on_raw_value->then->0->text_sensor.template.publish->state) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_ip_address' (see text_sensor->0->ip_address->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_connected_ssid' (see text_sensor->0->ssid->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_mac_address' (see text_sensor->0->mac_address->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING Found '${device_internal_name}_uptime_human' (see text_sensor->2->id) which looks like a substitution, but 'device_internal_name' was not declared WARNING 'esphome_foundation_device': Using the '_' (underscore) character in the hostname is discouraged as it can cause problems with some DHCP and local name services. For more information, see esphome.io/guides/faq.html#why-shouldn-t-i-use-underscores-in-my-device-name WARNING GPIO2 is a strapping PIN and should only be used for I/O with care. Attaching external pullup/down resistors to strapping pins can cause unexpected failures. See esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins INFO Detected timezone 'Europe/London' Failed config binary_sensor.status: [source /config/esphome/foundation-device.yaml:111] platform: status name: Status IDs must only consist of upper/lowercase characters, the underscorecharacter and numbers. The character '$' cannot be used. id: ${device_internal_name}_status

@@homeautomatorza Hello Pascal, i have uploaded the error code for you to review if you would be so kind please ?

It’s coming as soon as I can and in 2 or 3 videos

@@homeautomatorza BUT its a LONG WAIT!! :)

Yeah, I lost my voice last week after being out for a week. It all ready to be recorded, I just need audio! Stupid I know.

Yeah! Live stream for a 1000?

Thank you.

Pleasure

My pleasure

I wanted to put this out so quickly I made a mistake and saw it when it was baked into the video and released, I left it

It surprised me, I should read the documentation more often. 😉

Hi Joe, Sorry I missed you, watch out for the next one. And thank you, as for the direction, I feel it's a team effort and I want to keep it that way. Here are the 2 links for the breadboards and the base Breadboard: www.printables.com/model/248418-gridfinity-breadboard-holders Baseplate: www.printables.com/model/368481-dovetail-gridfinity-anchor-magnet-cleatanchor-v2 (These are the ones I am moving to) Jumper: www.printables.com/model/428684-gridfinity-adjustable-jumper-wire-comb-higher-dens Part tray: www.printables.com/model/449317-v31-gridfinity-bigsmall-parts-project-tray-w-1x1-s Small tray: www.printables.com/model/449770-short-gridfinity-tray Maybe I should add a page with the on my git hub page. --Pascal

@@homeautomatorza Thank you Pascal, for the links. That would be a good addition to your Github page, I think.

Two more tutorials in this series and I'll start with the 16x2 LCD I showed and move from there. Those tutorials are going to be more advanced though, all in preparation for the Advenced series on building a usefull Weather Station, so you can expect to see that in our Spring latest.