text
stringlengths
7
369
[2156.08 --> 2159.44] For those of you listening on audio, it makes zero difference, of course.
[2159.44 --> 2163.08] But for the live stream, I mean, you can see how many gray hairs I have.
[2163.84 --> 2165.90] That's what brings the people to JupyterTube, Alex.
[2165.92 --> 2166.64] That's what it is.
[2166.82 --> 2167.52] Exactly, yeah.
[2168.38 --> 2172.86] But when I plugged in this Elgato light, it connected to my network via the app on my phone.
[2173.20 --> 2178.30] And then within a minute or two, Home Assistant picked it up and was like, there's an Elgato
[2178.30 --> 2178.86] integration.
[2179.02 --> 2179.78] Do you want to enable it?
[2179.80 --> 2180.54] And I was like, click.
[2180.66 --> 2181.28] Yes, I do.
[2181.44 --> 2182.16] Boom, boom, done.
[2182.62 --> 2185.70] Moments like that remind me that actually this stuff's super cool.
[2186.12 --> 2186.74] I love that.
[2186.74 --> 2191.00] I had the same experience, obviously, with the Shelly devices, you know, they just get
[2191.00 --> 2193.06] on the Wi-Fi network and boom.
[2193.82 --> 2195.74] Home Assistant just sees it.
[2195.88 --> 2196.80] You know, you click a button.
[2197.26 --> 2201.76] I just set up another Shelly smart plug on my test bench upstairs.
[2202.20 --> 2204.82] I have a super secret rig that I'm testing right now.
[2205.38 --> 2210.38] And so one of the things that I do in my test is I want to know what the power usage is in
[2210.38 --> 2211.18] various scenarios.
[2211.18 --> 2216.56] And I, you know, I used to what I used to do, Alex, is I used to get a kilowatt.
[2216.68 --> 2218.20] I don't know if you've seen these kilowatt devices.
[2218.60 --> 2221.78] And then I would just I would I would run a benchmark and I would walk over to the
[2221.78 --> 2224.02] kilowatt and I would write down what the power usage was.
[2224.08 --> 2224.22] Right.
[2224.26 --> 2228.02] And then when the benchmark and I'd walk over to the kilowatt, I'd write down what the power
[2228.02 --> 2228.82] usage was.
[2229.12 --> 2233.62] And now with the Shelly, I just pull it into Home Assistant and then I can just look back
[2233.62 --> 2238.16] over the entire, you know, review period and see what the power usage was.
[2238.48 --> 2241.96] And, you know, that's so freaking valuable for me.
[2242.02 --> 2244.26] So there's a lot of interesting ways you can use Home Assistant.
[2244.84 --> 2248.64] Are you exporting any of this stuff to Influx so you could do historical data?
[2248.80 --> 2249.48] That's a good idea.
[2249.66 --> 2253.52] There's a there's an exporter built into Home Assistant that you can enable, which will
[2253.52 --> 2257.68] ship out that data to InfluxDB, which is a time series database.
[2257.68 --> 2262.16] And then you could put if you if you wanted to a Grafana front end in front of that and
[2262.16 --> 2267.14] make pretty graphs or query it based on whatever, you know, query logic you want to use.
[2267.58 --> 2270.84] So I found that very useful for stuff like hard drive data where I want to know what the
[2270.84 --> 2272.82] temperatures were from season to season.
[2273.42 --> 2279.60] So I can actually look and see on average how warm or cool my my basement is just simply
[2279.60 --> 2283.58] based on the fact that my hard drives are 10 degrees warmer on average in the summer than
[2283.58 --> 2284.26] they are in the winter.
[2284.96 --> 2285.88] That's a great idea.
[2285.96 --> 2287.18] I'd love to know that data.
[2287.18 --> 2290.00] I don't care so much for the bench stuff, but boy, for jupes.
[2290.38 --> 2293.80] With Influx, you've got to be careful, though, because it's writing constantly.
[2294.62 --> 2295.98] Obviously not an SD card.
[2296.14 --> 2298.70] Otherwise, that will burn out pretty dang quickly.
[2299.62 --> 2300.02] Yeah.
[2300.26 --> 2301.08] So I don't know.
[2301.48 --> 2304.24] Just some kind of SSD or something is probably the way to go for that.
[2304.90 --> 2305.64] That's a good tip.
[2306.48 --> 2309.70] I have one other like Home Assistant related tip.
[2309.78 --> 2312.80] If you have hacks, do you still use hacks at all?
[2313.34 --> 2315.46] The HACS community store, right?
[2315.46 --> 2315.74] Yeah.
[2315.74 --> 2317.18] The Home Assistant community store.
[2317.66 --> 2321.08] I believe I don't remember if it's in there or if you have to go find the repo.
[2322.28 --> 2325.60] But there is a tail scale integration now.
[2325.98 --> 2327.72] So my Home Assistant Blue.
[2327.72 --> 2331.26] I has tail scale.
[2331.70 --> 2339.04] And I, you know, when you're on the Home Assistant OS, it's not like you can just SSH in and install the tail scale package and get it on your tail scale network.
[2339.04 --> 2345.06] And I already have one Home Assistant system that is subscribed to Nebukasa Cloud.
[2345.42 --> 2349.96] And I don't know how to have two different Home Assistant systems on one Nebukasa Cloud account.
[2350.18 --> 2357.92] So instead of getting two Nebukasa Cloud accounts with two different email addresses, I just put one Home Assistant on tail scale.
[2358.12 --> 2359.62] And it's working great.
[2359.62 --> 2361.10] It's better than that, darling.
[2361.30 --> 2363.00] It's an official add-on these days.
[2363.94 --> 2364.58] Is it?
[2365.76 --> 2366.76] Well, there you go.
[2366.90 --> 2369.60] I have to say it's been working really well for me.
[2369.82 --> 2373.48] And it's how I am doing remote control of one of my Home Assistant instances now.
[2373.54 --> 2374.86] And I give it a big thumbs up.
[2375.26 --> 2376.12] Not a sponsored thing.
[2376.18 --> 2376.74] Just telling you this.
[2376.80 --> 2377.96] One of the things I've done recently.
[2378.34 --> 2380.86] I still think it's worth paying for Nebukasa if you don't.
[2381.48 --> 2384.56] So I'm not saying avoid paying.
[2384.96 --> 2386.52] I just didn't want to have two accounts.
[2386.90 --> 2388.20] Although I did consider it, actually.
[2389.34 --> 2393.30] I did consider doing it, but I just didn't want to have to manage it with two different logins and all that kind of stuff.
[2393.80 --> 2399.38] So Lord Pandemic asks in the chat room, anyone know if you can use Nebukasa and tail scale at the same time?
[2400.16 --> 2401.86] And so I think the answer to that would be yes.
[2402.40 --> 2409.44] With tail scale, if you use the split DNS functionality, so let's say you have a specific subdomain you use just for your LAN stuff.
[2409.44 --> 2413.90] For me, I have a couple of letters which delineate the site that I'm at, for example.
[2414.10 --> 2418.28] So, you know, let's just say AB would be site one and CD would be site two.
[2418.78 --> 2422.18] So it'd be ab.domain.com and cd.domain.com.
[2422.76 --> 2427.88] And in tail scale, you can go into their magic DNS settings and do what's called split DNS.
[2428.64 --> 2435.20] And actually have tail scale route to the specific DNS server in that local subnet, in that location.
[2435.20 --> 2439.84] And look up the home assistant domain name in your LAN that way.
[2440.34 --> 2445.68] But if you're also paying for Nebukasa, you've pretty much got it open to the internet anyway.
[2446.18 --> 2452.72] I know it's obfuscated through a long series of letters and numbers, but it's security through obscurity, that one.
[2452.80 --> 2453.80] And it's open to anybody.
[2453.80 --> 2464.38] So if you're worried about people accessing your home assistant remotely, maybe the Nebukasa thing isn't the remote access portion of it anyway, isn't the way to do that.
[2464.54 --> 2467.68] Maybe tail scale is, but I'll leave that up to the listener.
[2468.14 --> 2475.14] And there is one key difference between the community tail scale version that I'm using and the official add-on.
[2475.14 --> 2487.18] So the official add-on is kind of like a control panel for your devices in tail scale, but it does not put your home assistant instance on the tail scale network.
[2487.42 --> 2492.26] So the community edition actually puts the machine on the network.