**How to use Claude Code in Home Assistant — Transcript & Summary | SozAI** Source: https://sozai.app/transcript/use-claude-code-home-assistant/ Learn how to install and use Cloud Code AI within Home Assistant for automations and configuration management. ## Key Takeaways - Cloud Code can be integrated into Home Assistant via an add-on for OS or Supervised installs. - Backing up Home Assistant before using Cloud Code is highly recommended due to AI-driven changes. - Cloud Code can analyze and understand complex Home Assistant configurations and automations. - Users can interact with Cloud Code to query and modify automations using natural language. - Cloud Code supports advanced features like plan mode and automatic edit acceptance to streamline workflow. ## What the video covers - Introduction to using Cloud Code AI inside Home Assistant via an add-on. - Prerequisites include running Home Assistant OS or Supervised edition and backing up your system. - Step-by-step installation of the Cloud Terminal add-on from a custom repository. - Guided setup process including subscription authentication for Cloud Code. - Cloud Code reads and understands the Home Assistant configuration files to create a reference markdown file. - Demonstration of querying Cloud Code about existing automations for water valves. - Example modification of an automation to change watering schedule and duration using Cloud Code. - Explanation of Cloud Code’s ability to understand YAML and templating used in Home Assistant automations. - Use of different modes in Cloud Code such as plan mode and auto-accept edits. - Final recommendations to explore Cloud Code for enhanced Home Assistant automation management. ## Chapters 1. 00:00 Introduction to Cloud Code in Home Assistant 2. 01:13 Backing Up Home Assistant Before Setup 3. 02:42 Installing Cloud Terminal Add-on 4. 03:53 Setting Up Cloud Code and Authentication 5. 04:53 Initializing Cloud Code with Home Assistant Config 6. 06:25 Cloud Code Understanding Home Assistant Files 7. 08:25 Querying Automations with Cloud Code 8. 10:48 Modifying Watering Automation Using Cloud Code 9. 13:45 Advanced Cloud Code Features and Wrap-up Answers ## Questions about this video Can I use Cloud Code with any Home Assistant installation? Cloud Code via this add-on requires Home Assistant OS or Supervised edition because add-ons are only supported on these installations. Other setups like running on Mac or Windows may not support this method. Is it necessary to back up Home Assistant before using Cloud Code? Yes, it is strongly recommended to back up your Home Assistant configuration before using Cloud Code, especially if you are new to it, as AI-driven changes can sometimes produce unexpected results. What can Cloud Code do inside Home Assistant? Cloud Code can read and understand your Home Assistant configuration files, help you query existing automations, and modify them using natural language commands, supporting YAML and templating used in automations. ## Full Transcript — Download SRT & Markdown 00:01 Speaker A Hey, I want to show you how you can use Cloud Code inside of Home Assistant. 00:07 Speaker A If you're like me and you love using AI everywhere, or you know how to use Cloud Code and you want to see how you can use it in Home Assistant, this video is for you. I'm going to go through the installation process, and then I'm going to show you a couple examples of how I have found Cloud Code to be useful inside of Home Assistant. So, that's what we'll be doing. Two things as a way of preface. First is, this method of using Cloud Code happens through an add-on, and so you can only use add-ons if your Home Assistant installation is Home Assistant OS or Home Assistant Supervised edition. So, if you don't have that approach, and maybe you're just running on a Mac or on a Windows machine, you may still be able to use Cloud Code, but this video is not how to do it. So that's the first preface. The second is, if you have not already backed up your Home Assistant, I would recommend doing that before playing around with Cloud Code, especially if you haven't used Cloud Code before, because if you get yourself into a weird situation, Cloud Code is an AI and it may do some things that you may not want it to do if you're not used to using it. So, I would just, out of an abundance of caution, do a backup of your Home Assistant. You can do that in Settings, go down to System, and then Backups. So, without further ado, let's jump in. So, the first thing that we're going to do is we're going to go to Settings, scroll down to Add-ons, and here we're going to have to add an add-on store. So, click that in the bottom right, click the three dots up above, and then click on Repositories. Cool. I've already got this one added. If it wasn't added, you would go and get this: Hey, TCAST Home Assistant add-ons repository. Copy it, put it down in the bottom, and hit Add. And so that is what that looks like. I'll show you exactly what that process is. Paste, Add. It now adds this, and we can scroll down here in our add-on store and see Cloud Terminal. So once we've done that, we can click on Cloud Terminal. It will open this up. And then I can click Install. And we'll give that just a minute. Cool. So we are installed. And now we want to make sure that Start on Boot is here. And then we want Watchdog. This will restart the add-on if it crashes. And then Add to Sidebar as well. So that's there. Auto Update I'll leave off for now. And then I'm also going to hit Start. Cool. So this has started. Now we can go in and actually set up the rest of the way for Cloud Code. I can go over here on the sidebar and click Cloud Terminal. That opens this up and then it's going to guide us through a setup process. If you've set up Cloud Code before, it's going to be the same process that you use that you're used to. If you have not done this, I'll show you kind of what I might do. So here, I'll choose the style. You can use your arrow keys here. You're not going to be able to use your mouse to click. Use your arrow keys. And then I'll just keep it on dark mode, then hit Enter. To do this, you will need a Cloud Code subscription. There are a number of these that work. I'm going to do this first option where I have a subscription of Pro, Max, Team, or Enterprise. You can see here that there are a number of different options. I use the Pro version that gives me access to Cloud Code. So, I will flip back over here and then hit Enter. It's going to say it's going to open the browser to sign in for this add-on. That's not going to work. I'm going to have to click on this link to open up to do authentication. I'll hit Authorize. I'm going to copy this code. Come back here. Paste the code and hit Enter. Great. Login has been successful. I hit Enter. Cool. So, now that we have this all set up, Cloud gives a couple warning signs. Obviously, Cloud can make mistakes. That's what I mentioned earlier, so just be careful. I'll hit Enter. And then I'm going to, yes, trust the files in this folder. This is my Home Assistant instance. Yes, proceed. The first thing that we're going to want to do is run slash init. And that will create a claude.md file. That will be basically Claude's going to go out and I'm going to run it and now I'll talk while that's happening. What is going to happen here is Claude is going to go out and it's going to understand all the files that are in this repository because Cloud doesn't know that it's working in Home Assistant yet. And so it's going to go out and it's going to read all the files and try and understand what's going on here. And then what it's going to do is it's going to write that all into a markdown file that it will read every time on boot. So it will have a basis for the repository that it's in, in this case Home Assistant. So it will know that it is working inside of Home Assistant. So here it's just verifying with me that it wants to run this command to keep reading some things. Yes, I'm going to hit go ahead and continue. And then what I'm going to do is to prevent it from asking me to use any other questions, I'm going to hit Shift+Tab. You don't have to do this. And I've turned this mode on to accept edits automatically. So it shouldn't have to, it should not ask me again. So I'm going to let this churn for a minute and then I'll come back. Awesome. So Claude just finished here and I'm going to scroll back up to understand what we just saw here. So Claude was spelunking through this repository. It appears to be the Home Assistant configuration directory. Cool. Let me examine the key configuration files to understand the structure. So it read my configurations, it read my automations, it read my scripts, etc., etc. Continued on and then it wrote this Cloud file. Key sections, project overview, this describes this as a Home Assistant repo. Awesome. Config configuration structure explains a split YAML file organization, key integrations, Zigbee to MQTT, ESPHome, alarm, and other custom components. So, and so on and so forth. And so it has a quick understanding of this whole process of my Home Assistant setup and it's written that to a Cloud MD file. It will read that every time that it boots up. So this is where we're at. Cool. I'm glad that we've done this and now we can move on to a couple examples. So I have a couple examples that I want to walk through. The first is I want to add an automation. Actually, I want to modify an automation. I have some water valves outside that I have set to an automation. I'm going to ask Cloud Code about these. So I just asked Cloud Code what automations do I have for water valves. Cloud is going to look into this and get back to me. Obviously, I could just ask it to make a change to an automation, but I first want to understand what Cloud is understanding about my automations. Cool. Scheduled watering automations. So, there's daily garden watering. This happens at 9:00 a.m. and 4. And then daily front watering. This happens at 9:30 a.m. and 4:30 p.m. So, this is great, but we've moved to fall and I want to change this daily front watering from happening twice a day to happening just once a day for 15 minutes every other day. So, I'm going to see if Cloud can do that. For my daily front watering, can you change this to—had a typo there. I'm going to leave it because Cloud should understand. Can you change this to water every other day and only for 15 minutes? Cool. Now, a couple notes before I hit Enter here. I have, remember I got there by going Shift+Tab. So, if I do that again, it's going to move into plan mode, which is actually what I'm going to use here. If I do it one more time, it'll be in th— 00:16 Speaker A the installation process and then I'm going to show you a couple examples of how I have found Claude Code to be useful inside of Home Assistant. So, that's what we'll be doing. Um, uh, two things as way of preface. Uh first is uh 00:30 Speaker A this method uh of using cloud code happens through an add-on and so you can only use add-ons if your home assistant um installation is home assistant OS or home assistant supervised um edition. So uh if you don't uh have that approach um 00:45 Speaker A and maybe you're just running on a Mac or uh on a Windows machine, you may still be able to use cloud code, but this video is not how to do it. So that's the first preface. The second is 00:55 Speaker A uh if you have not already um backed up your home assistant, I would recommend doing that before playing around with cloud code, especially if you haven't used cloud code before um because um if you get yourself into a weird situation, 01:07 Speaker A cloud code, it's an AI and uh it may do some things that you may not want it to do um if you're not used to using it. 01:13 Speaker A So, I would just uh you know uh out of abundance of caution, do a backup of your home assistant. You can do that settings, go down to system, and then backups. 01:24 Speaker A So, without further ado, let's jump in. So, the first thing that we're going to do is we're going to go to settings, uh, scroll down, add-ons, and here we're going to have to add, uh, an add-on store. So, click that in the bottom 01:34 Speaker A right, click the three dots up above, and then click on repositories. Cool. I've already got this one added. Um, if it wasn't added, you would go uh, and get this. Hey, TCAST Home Assistant add-ons repository. copy it, put it down 01:53 Speaker A in the bottom, and hit add. And so that is what that looks like. And I'll show you exactly what that process is. Um, paste, add. It now adds this, and we can scroll down here in our add-on store and 02:05 Speaker A see cloud terminal. So once we've done that, we can click on cloud terminal. It will open this up. And then I can click install. And we'll give that just a minute. Cool. So we are installed. Um, and now uh we want to make sure that 02:18 Speaker A start on boot is here. And then we want um watchdog. This will restart the add-on if it crashes. And then add to sidebar as well. So that's there. Um auto update I'll leave off for now. And then I'm also going to hit start. Cool. 02:33 Speaker A So this has started. Now we can go in and actually set up uh the rest of the way for cloud code. Um I can go over here on the sidebar and click cloud terminal. 02:42 Speaker A That opens this up and then it's going to guide us through a setup process. Uh if you've set up cloud code before, it's going to be the same process that you use that you're used to. If you if you 02:50 Speaker A have not done this, um I'll show you kind of what I might do. So here, I'll choose uh the style. You can use your arrow keys here. You're not going to be able to use your your mouse to click um 02:59 Speaker A use your arrow keys. And then I'll just keep it on dark mode, then hit enter. Um to do this, you will need a cloud code subscription. There's a number of these that work. Um I'm going to do this first 03:09 Speaker A option where I have a subscription of Pro, Max, Team, or Enterprise. You can see here that there are a number of different options. Um, I use the pro version that gives me access to cloud code. So, I will flip back over here and 03:21 Speaker A then hit enter. It's going to say it's going to open the browser to sign in for this add-on. That's not going to work. 03:27 Speaker A I'm going to have to click on this link to open up um to do authentication. I'll hit authorize. I'm going to copy this code. 03:36 Speaker A Come back here. Paste the code and hit enter. Great. Login has been successful. I hit enter. Cool. So, uh, now that we have this, uh, all set up, Cloud gives it a couple warning signs. Obviously, Cloud can make mistakes. That's what I 03:53 Speaker A mentioned earlier, so just be careful. I'll hit enter. Um, and then I'm going to, uh, yes, trust the files in this folder. This is my home assistant instance. Yes, proceed. The first thing that we're want that we're going to want 04:06 Speaker A to do is run slashinit. And that will create a claude.md file. Uh that will be um basically it's claude's going to go out and I'm going to run it and now I'll talk while that's happening. What what is going to happen here is claude is 04:19 Speaker A going to go out and it's going to understand all the files um that are in this repository because cloud doesn't know that it's working in home assistant yet. And so it's going to go out and it's going to read all the files and try 04:29 Speaker A and understand what's going on here. And then uh what it's going to do is it's going to write that all into a a markdown file that it will read every time on boot. So it will have a um a 04:39 Speaker A basis for for um the repository that it's in in this case uh home assistant. 04:44 Speaker A So it will know that it is working inside of home assistant. So here it's just verifying um with me that it wants to run this command to keep reading some things. Yes, I'm going to hit uh go ahead and continue. And then what I'm 04:56 Speaker A going to do is uh to prevent it from asking me to use any other questions. 05:01 Speaker A I'm going to hit shift tab. You don't have to do this. And I've uh turned this mode on to accept edits automatically. 05:08 Speaker A So it shouldn't have to it should not ask me again. So I'm going to let this uh churn for a minute and then uh I'll come back. 05:16 Speaker A Awesome. So Claude just finished here and I'm going to scroll back up to understand uh what we just saw here. So Claude was, you know, spelunking through this uh this repository. Um it appears to be home assistant configuration 05:29 Speaker A directory. Cool. Let me examine the key configuration files to understand the structure. So it read my configurations, it read my automations, it read my scripts, etc., etc. Continued on and then it wrote uh this cloud file. Key sections, project overview, this 05:43 Speaker A describes this as a home assistant repo. Awesome. Config configuration structure um explains a split YAML file organization, key integrations, Ziggb to MQTT, ESP home, alarm, and other custom components. So um and so on and so forth. And so it it has a a quick 06:00 Speaker A understanding of this whole process of of um of my home assistant setup and it's written that to a cloud MD file. It will read that every time uh that it boots up. So this is where we're at. 06:12 Speaker A Cool. I'm glad that we've done this and then now we can move on to um a couple examples. So I have a couple examples that I want to walk through. The first is I want to add an automation. 06:25 Speaker A Um, actually I want to modify an automation. I have uh some out some some water valves outside uh that I have set to an automation. I'm going to ask Cloud Code about these. 06:38 Speaker A So I just asked Claude Code what automations do I have for water valves. Claude is going to look into this and get back to me. Uh obviously like I could just ask it to make a change to an 06:47 Speaker A automation, but I first want to understand what Claude uh is understanding about my automations. 06:52 Speaker A Cool. Scheduled watering automations. So, there's daily garden watering. This happens at 9:00 a.m. and 4. And then daily front watering. Um, this happens at 9:30 a.m. and 4:30 p.m. So, this is great, but we've moved to fall and uh I 07:07 Speaker A want to change this daily front watering um from happening twice a day to happening just once a day for 15 minutes uh every other day. So, I'm going to see if Claude can do that. for my daily front watering. 07:21 Speaker A Can you change this to had a typo there. I'm going to leave it because Cloud should understand. Um, can you change this to water every other day and only for 15 minutes? 07:35 Speaker A Cool. Now, a couple notes before I hit enter here. I have uh except at um remember I got there by going shift tab. So, if I do that again, it's going to move into plan mode, which is actually what I'm 07:48 Speaker A going to use here. If I do it one more time, it'll be in the default mode where it asks for uh verification before it uses before it modifies any files. Um, I'm going to move into plan mode. And 07:58 Speaker A then I'm uh so shift tab, then shift tab again, and then I'm going to hit enter. 08:02 Speaker A And what's going to happen is, uh, Claude Code is going to write up a plan for how it wants to solve this. So, we'll give this just a minute. 08:11 Speaker A Okay, cool. So Claude uh understands what I want. Before I create the plan, I need to clarify a few details. This is cool. And actually, this is the first time I've seen uh Claude do this uh sort of verification process. Odd days, even 08:24 Speaker A days, Monday, Wednesday, Friday, Sunday. So, I think what we're going to do is let's do odd days. Sure, that sounds good. And then the time uh keep this is this is really cool. I've never seen Claude uh confirm in this way. So, this is pretty 08:42 Speaker A neat. So, let's do I think 9:30 a.m. is fine. Going to hit enter and then submit answers. So, now Claude is going to take my answers and it is going to uh write up the plan that it wants to do. 08:57 Speaker A Cool. We've got the plan changes to automation daily front watering in automations. Update the triggers. Remove the 4:30 trigger. Keep the 9:30 trigger. 09:05 Speaker A Add condition to run only on odd days of the month. Cool. Update watering duration. Change from 30 minutes to 15 minutes. That sounds good. Change to reflect new schedule. Awesome. Preserve all safety mechanisms. Yep. Cool. So, I had like these other safety mechanisms 09:20 Speaker A in my automation. Um, if it didn't retry, it would if it didn't shut off the water, it would let me know um after three tries, etc., etc. 09:30 Speaker A Cool. Um, and then I can choose yes and auto accept edits or yes and manually approve edits. I'm going to do that one so we can see the change before um before uh Claude actually makes it. So I'll hit two and then we're going to let 09:43 Speaker A Claude do that. Cool. So here is the change that Claude wants to do. It updates the description and then the conditions. It uses this uh value template. Um it's a mathematical expression um uh to only only u make the 10:00 Speaker A automation happen on odd days. So that looks good. I'm going to hit yes. it's going to uh change that automation. 10:08 Speaker A Obviously, this is something we could have done in the automation u you know uh UI but uh it's this is just an example of a simple thing that cloud can do. Now also wants to uh change a message that it sends to me um whenever 10:22 Speaker A this happens. So that looks great. Yes, I'm going to allow that. Cool. And it wants to make one more change to a message that I have. The neat thing here is yes, this is a very simple change that we're making. Um but clot can get 10:35 Speaker A very complex and and uh it understands the templating and the YAML language uh that these automations are written in. 10:41 Speaker A So you can write some fairly complex things. Cool. Automation will next run on 930. So that's awesome. Um this is great. I think what I'm going to have to do is I'm actually going to have to uh reload my home assistant to make sure 10:55 Speaker A that this uh change is picked up. I think you have to do that whenever you make changes to um an automation file. 11:00 Speaker A So, I'm going to go to uh I believe settings, three dots up here, restart home assistant, and then I'm just going to do a quick reload. So, we'll give that just a minute, and then we're going to see if uh these changes have been 11:12 Speaker A reflected in our automations. So, in settings, we'll go to automations and scenes, uh automations, and then we have our daily front watering, which I have turned off. I'm going to click on that when the time is equal to 9:30. If the 11:26 Speaker A template the template renders um equal and so this is our uh every other day situation then perform this um delay for 15 minutes. Uh awesome. That all looks good. Cool. So now I'm going to turn this automation on and I will you know 11:45 Speaker A hope that works. Cool. I'm going to flip back to cloud terminal here. Uh, one interesting thing with cloud terminal when we do this is you will lose um your your last conversation, however you'd like to pick up where you left off. Um, 12:00 Speaker A because basically what happens is cloud it just starts back up. I think I don't know if that's a a situation with how the add-ons work or if the the add-on has not been, you know, updated. So, it it does this in a better way. Um, but 12:11 Speaker A you can do slash and then continue or I think you can do resume. Yeah, resume. And it will resume the last conversation. 12:25 Speaker A Okay, that's not working. Let me go back. Cloud terminal resume. Okay, well, apparently that's not working. So, it's an uh this this must be a bug in the new cloud code. So, uh maybe that's not working. But anyway, 12:44 Speaker A we'll keep going. Cool. So, let's go in the next example. Um, I want to update my dashboard. I'm going to flip over here to my main dashboard. This is my dashboard. I have I have some issues here. Some entity 12:57 Speaker A isn't found, but that's okay. I have this battery levels in the bottom right. Um, primary bath, north air conditioning. These are all most of these are moisture sensors. And then I have my um my water valves. These are 13:09 Speaker A all Ziggb um devices. Um, I have some new ones that are my uh my temperature uh sensors that I have in various refrigerators and freezers and I'd like for them to show up here. So, I'm going to see if Cloud can do that. So, let's 13:25 Speaker A go back to Cloud Terminal and then I'm going to write this out. Cool. I'd like for you to update my main dashboard so that my temp sensors, fridge and freezer, show up under battery levels. Let's see what happens 13:44 Speaker A here. I'm also going to put this in the plan mode. So, shift tab, shift, tab. 13:48 Speaker A Cool. We'll see what happens. Nice. So, I've read my dashboard. I'm going to check if there are battery sensors for the fridge and freezer. Now, it's going to look at uh it's going to run this command. Looks like that's 14:00 Speaker A fine. I'm going to go to two yes and don't ask again for ha stateless commands and config. That sounds good. 14:08 Speaker A Let me check the Ziggb configuration. So, it's going to check my ZigGB configuration file to see if there's Okay, look at that. Um, and one thing I want to note here is this HA state thing did not work. And so, Cloud was like, 14:21 Speaker A okay, let me try something else. And so, it decided to look in my Ziggb to MQ MQTT configuration. Read this, then it found my sensors. These are Aqua sensors. Awesome. Which are battery powered Sigb devices. Nice. Now, here's 14:33 Speaker A the plan. I'll update the battery levels section in UI main dashboard to include the three temperature um sensor battery levels. That looks good to me. Yes. And auto accept edits. 14:45 Speaker A Awesome. So, it looks like Claude is done here. Um simple change here. It just added these new entities here um that it found uh from looking at my uh Ziggb to MQTT configuration, which is pretty cool. Um I didn't have to go 14:57 Speaker A looking through all those files. The battery sensors for your fridge and freezer. Um nice. They should be here. 15:03 Speaker A These Aquar sensors will show their battery percentage and trigger low battery warning levels through existing automation. Cool. So, I already have an automation for low battery warning. Um, and it's just noting that that should still trigger for these. That's cool. 15:15 Speaker A Um, but let's go to the main dashboard and see what happened. So, I'm going to go up here. 15:20 Speaker A Battery levels. Look at that. Freezer and basement. So, it looks like I maybe should replace those batteries. They're in the freezer and so uh the the batteries don't work as well. So um uh these these may be a bit deceiving but 15:34 Speaker A we have these here and added. So that was super easy. Um one note here is I do have uh this this dashboard as a separate YAML file. Um and so uh I am able to have Claude change these and 15:46 Speaker A then I can just flip to the to the dashboard and see the changes immediately. Um so if you don't have your dashboards split out into separate YAML files, you may want to do that. Um cool. So, uh, that is that example. Um, 16:00 Speaker A a cool thing here is I actually had Claude build this entire dashboard, including all of these, um, temperature gauges, which is pretty cool. Um, I think they're they're they're more complex to set up, um, especially if you're just writing the YML for them. 16:14 Speaker A So, uh, yeah, those are the two examples that I wanted to run through. Um, so yeah, cool. A couple things as we wrap up. If you don't have cloud code, I would highly recommend uh, getting it and playing around with it. Um, I think 16:27 Speaker A AI is here to stay. Um, and uh, it's fun to play with. So, uh, I would recommend um, you know, if you can swing a subscription, go for that and play around with it. Um, and yeah, just see what it can do. Um, 16:44 Speaker A and then as exhibited by some of the examples I had today, uh, cloud code is not perfect. um and uh it may mess up, it may do things wrong, it may invoke wrong tools, uh but it can fumble around and figure things 16:58 Speaker A out. So, just like a human, um like anything else, uh cloud code and various AI things like cloud code, uh they're tools. Um and so, uh the tool isn't perfect. Um but, uh as you play around with it and use it, um you're more able 17:15 Speaker A to figure out the the ways that you can use it effectively. So, um I would highly recommend playing around with with things like cloud code uh in home assistant and things like that. So, I think that's all I have uh for you 17:28 Speaker A today. Thanks for watching. Topics: Home Assistant Cloud Code AI automation Home Assistant add-ons Cloud Terminal Home Assistant OS Home Assistant Supervised automation modification YAML smart home AI Study this video - [Flashcards from this video](https://sozai.app/tools/ai-flashcard-generator/?from=transcript&id=78248) - [Quiz on this video](https://sozai.app/tools/quiz-generator/?from=transcript&id=78248) Free, made by AI from this transcript. No signup. --- This is the markdown twin of https://sozai.app/transcript/use-claude-code-home-assistant/ — the same content, without the markup. Published by SozAI (https://sozai.app). Reuse and quotation are allowed with attribution and a link back. Machine-readable index: https://sozai.app/llms.txt · data API: https://sozai.app/api/