WEBVTT 00:00:00.005 --> 00:00:05.305 You know, I realized, you know, those cigars you got for the van success, 00:00:05.305 --> 00:00:07.485 we should have smoked those with Drew, just saying. 00:00:08.685 --> 00:00:09.825 Now we've got to go back to Denver. 00:00:11.985 --> 00:00:15.745 We keep putting off the success cigars. I think the key thing I was waiting 00:00:15.745 --> 00:00:19.425 for is, what really makes them special is you smoke them while you're going 00:00:19.425 --> 00:00:24.185 down the road, and you crack the windows, and you get like a half a day of cigar smell going. 00:00:24.725 --> 00:00:29.925 Oh. Oh, so you and I need to be on the same road trip and Wes can be there too 00:00:29.925 --> 00:00:31.905 in the backseat. And then I got another empty seat. 00:00:32.565 --> 00:00:35.205 We should play on something. Just smoke that place out. 00:00:35.385 --> 00:00:38.285 I mean, it'd probably make it smell better. It smells like the 90s in here. 00:00:38.345 --> 00:00:40.005 Hey, I like the 90s. 00:00:52.381 --> 00:00:57.121 Hello, friends, and welcome back to our weekly Linux talk show. My name is Chris. 00:00:57.281 --> 00:00:57.901 My name is Wes. 00:00:58.161 --> 00:00:59.021 And my name is Brent. 00:00:59.541 --> 00:01:02.481 Hello, gentlemen. It's really everyone's weekly talk show. It's kind of an open 00:01:02.481 --> 00:01:04.081 source weekly talk show. 00:01:04.121 --> 00:01:10.021 And today, I'm going to confess to my biggest smart home failure in probably seven years. 00:01:10.181 --> 00:01:13.401 And it happened the night right before our Texas trip. 00:01:13.661 --> 00:01:16.781 I'll tell you what broke, how I kind of pulled it all back together, 00:01:16.981 --> 00:01:20.661 how Wes would probably fix it right, and then my future build plans. 00:01:20.661 --> 00:01:23.161 They'll round out the show with some great picks, some boosts, 00:01:23.201 --> 00:01:24.541 some shout-outs, and more. 00:01:24.681 --> 00:01:28.541 So before we go any further, got to say time-appropriate greetings to that virtual lug. 00:01:29.221 --> 00:01:31.781 Hello, Mumble Room. There's one of you in the audience. 00:01:31.941 --> 00:01:32.121 Hello. 00:01:32.241 --> 00:01:32.481 Hello. 00:01:32.481 --> 00:01:34.621 Hello, hello, hello. I'll say it for everyone. Hello. 00:01:34.881 --> 00:01:38.041 Oh, I see Minimax up there staging. We have Autobrain inbound and a bunch of 00:01:38.041 --> 00:01:39.281 people up in quiet listening, too. 00:01:39.701 --> 00:01:43.581 Everybody's sneaking in right under the deadline, right as the intro music's going. 00:01:44.301 --> 00:01:48.881 Also, a big good morning to Define.net slash Unplugged. Go meet Defined Networking, 00:01:48.961 --> 00:01:53.301 and they have Manage Nebula, a decentralized VPN that's built on the open-source 00:01:53.301 --> 00:01:55.201 Nebula platform. It's really awesome. 00:01:55.641 --> 00:01:59.421 Talk about having full control of your infrastructure. And Nebula is optimized 00:01:59.421 --> 00:02:02.221 for speed, simplicity, and industry-leading security. 00:02:02.381 --> 00:02:05.701 You can fully self-host it, or you can take advantage of their managed product, 00:02:06.081 --> 00:02:11.221 100 devices for free, when you go to defined.net slash unplugged. 00:02:11.221 --> 00:02:17.641 Nebula got started really battle-tested in 2017 to secure Slack's global infrastructure. 00:02:18.021 --> 00:02:21.461 Now it's used by enterprises all over the world to connect their infrastructure. 00:02:21.681 --> 00:02:25.461 It's used by Homelabbers. It's even used by Rivian in their automobiles on the 00:02:25.461 --> 00:02:27.301 road to communicate back to Rivian HQ. 00:02:27.561 --> 00:02:31.521 It's super powerful. It's very flexible. You can go from managed to your own 00:02:31.521 --> 00:02:33.701 self-hosted. And I mean, you control everything. 00:02:33.981 --> 00:02:37.261 It's great. So go get started with up to 100 hosts, absolutely free, 00:02:37.381 --> 00:02:41.621 no credit card required. Go to defined.net slash unplugged. 00:02:44.768 --> 00:02:49.488 Now, we have just, I wanted to say thanks again. Not a lot in the housekeeping, 00:02:49.708 --> 00:02:52.388 but thank you again to everybody who made, I think, one of the best trips we've 00:02:52.388 --> 00:02:53.968 done in a while. I think it was my favorite trip of the year. 00:02:54.428 --> 00:02:55.428 What made it your favorite? 00:02:55.688 --> 00:02:58.808 Well, the race was a good part of it. That was a lot of fun, racing down. 00:02:58.968 --> 00:02:59.848 Only because you won. 00:03:00.268 --> 00:03:02.468 No, I think it would have been fun either way. I think that would have, 00:03:02.548 --> 00:03:03.468 because it was just a good challenge. 00:03:03.608 --> 00:03:07.408 Yeah, I mean, we got to see a bunch of the country. We ran into listeners and, 00:03:07.468 --> 00:03:09.368 like, various interesting things along the way. 00:03:09.368 --> 00:03:12.788 and right then the destination we got to see you and 00:03:12.788 --> 00:03:15.888 your cats and see the van again and see everybody at 00:03:15.888 --> 00:03:20.548 texas linux fest and visit austin which is always a good time plus we were able 00:03:20.548 --> 00:03:25.348 to swing by system 76 and drew which we hadn't planned for at all when we set 00:03:25.348 --> 00:03:30.188 out on the voyage so yeah i think in terms of like both achieving what we set 00:03:30.188 --> 00:03:34.748 out for and like you know the uh 00:03:35.148 --> 00:03:37.368 randomness of the road rolled in our favor. 00:03:37.368 --> 00:03:40.848 Yeah it was it was nice to have the flexibility and have 00:03:40.848 --> 00:03:44.068 the creative license that the audience trusted us with to go 00:03:44.068 --> 00:03:47.428 out there and do it and then having an event in october and it'll be november 00:03:47.428 --> 00:03:51.348 next year it's it's just it was the right amount of time after just event after 00:03:51.348 --> 00:03:54.968 event after event and we sort of had a breather so it was we were recharged 00:03:54.968 --> 00:03:58.868 and ready to go again um so i thought it was the best trip i guess you probably 00:03:58.868 --> 00:04:01.788 partied pretty hard at pretty hardy in nix vegas. 00:04:01.788 --> 00:04:06.028 That's true yeah that was a that was It was also a spectacular trip, 00:04:06.328 --> 00:04:09.708 but I didn't have you guys with me. So, you know, I can only hit so high. 00:04:09.928 --> 00:04:14.148 We also have some good news. After a lot of hard work by Mr. 00:04:14.308 --> 00:04:16.068 Westpain, our Matrix server is back online. 00:04:18.480 --> 00:04:23.420 Yeah, sorry about that, everyone. Thanks for your patience. Several billion 00:04:23.420 --> 00:04:26.120 state groups, state rows later, here we are. 00:04:26.380 --> 00:04:29.340 Many, yeah, multiple numbers of billions. Yeah, it was a lot. 00:04:29.540 --> 00:04:31.560 Yeah, and more than a terabyte of data gone. 00:04:31.720 --> 00:04:32.100 Yeah. 00:04:32.220 --> 00:04:32.680 In a good way. 00:04:32.800 --> 00:04:35.440 Yeah. So there's been some account cleanups. 00:04:36.040 --> 00:04:40.180 Yeah, main thing here is mostly just, well, let us know if you see stuff that's 00:04:40.180 --> 00:04:44.180 broken. And in particular, we suspended a bunch of stale accounts. 00:04:44.500 --> 00:04:47.480 But if we suspended anyone by mistake, do reach out. 00:04:47.620 --> 00:04:48.500 Let us know. Thank you. 00:04:51.109 --> 00:04:54.029 Okay, so, I mean, I've been doing the smart home thing for a while, 00:04:54.249 --> 00:04:57.909 tinkered with various different platforms, you know, the Amazon platform, 00:04:58.109 --> 00:05:03.289 the Google platform, the Apple platform, but inevitably would burn out on them 00:05:03.289 --> 00:05:04.449 or would have some sort of issue. 00:05:05.569 --> 00:05:08.609 about seven years ago I think I discovered Home Assistant, 00:05:09.989 --> 00:05:16.929 and it really started, kicked off the I'd say smart home lifestyle and it's been now, 00:05:17.149 --> 00:05:23.609 I only buy things that will integrate with Home Assistant and they integrate 00:05:23.609 --> 00:05:27.089 out of the box so I don't do the thing where I buy a smart product and see later 00:05:27.089 --> 00:05:29.309 on maybe I can make it work with Home Assistant It's. 00:05:29.309 --> 00:05:33.049 Kind of like the dance Linux users are used to, right? Yes You buy hardware 00:05:33.049 --> 00:05:36.509 with your software in mind. Although I think in both cases, right, it's gotten better. 00:05:36.949 --> 00:05:41.329 Yes, very much so. But just to underscore it, when the device goes in, 00:05:41.449 --> 00:05:47.109 whether it be a fan or a heater or a bug controller or lights for a barbecue 00:05:47.109 --> 00:05:50.469 area or a heater in a bathroom or whatever, 00:05:51.189 --> 00:05:55.229 it's integrated into Home Assistant first. And that's how it's always used initially. 00:05:55.249 --> 00:05:59.249 It's never used in the way it comes out of the box. So to say it's integrated 00:05:59.249 --> 00:06:03.729 into my home, my home is essentially a robot. I mean, it really is. 00:06:04.129 --> 00:06:07.409 And it has made our quality of life better because we live in a small space 00:06:07.409 --> 00:06:12.689 and having just climate control that is smart is really good. 00:06:12.809 --> 00:06:18.369 But also what I learned later on into my home assistant journey is something 00:06:18.369 --> 00:06:21.049 I don't think newbies out there that haven't gone down this path yet realize 00:06:21.049 --> 00:06:22.769 is it's very useful to have data. 00:06:24.436 --> 00:06:27.716 So if you have not deployed home assistant or you're a smart home skeptic, 00:06:27.896 --> 00:06:28.976 please listen to this next point. 00:06:29.556 --> 00:06:33.896 Having various bits of data about power usage in your home, water usage, 00:06:34.156 --> 00:06:41.796 if you have solar, your solar production, water leaks, motion and presence logs, even long-term things. 00:06:41.936 --> 00:06:45.456 Like I have sensors in my fridge and my freezer. 00:06:46.516 --> 00:06:51.336 And I can see if it's not performing as well over time. And so I can start to 00:06:51.336 --> 00:06:54.556 budget for a new fridge before my refrigerator fails. 00:06:55.596 --> 00:06:58.996 These are really powerful tools that I don't think people realize are available 00:06:58.996 --> 00:07:00.816 to them before they've gone down this journey. 00:07:00.936 --> 00:07:05.296 So it's extremely useful. Like I could just never go back, at least not while living in Jubes. 00:07:06.236 --> 00:07:09.856 But recently, I had one of the worst failures ever. 00:07:10.916 --> 00:07:13.696 And it was the worst kind of timing. I was telling the boys about it. 00:07:14.296 --> 00:07:19.336 It happened within a 24-hour window before we left for Austin. 00:07:19.976 --> 00:07:24.456 And I realized it literally the night I was packing because I went to hit a 00:07:24.456 --> 00:07:27.636 button and nothing happened. Oh, that's odd. 00:07:27.856 --> 00:07:31.276 Oh, I can imagine. I can almost feel the sinking feeling, right? 00:07:31.456 --> 00:07:34.536 At first, you're writing it off. Your brain's trying to explain it all away. 00:07:34.756 --> 00:07:36.356 Oh, it's probably a temporary failure. 00:07:36.756 --> 00:07:39.836 And then the evidence starts piling up. 00:07:40.136 --> 00:07:45.916 How bad, Wes? How bad could it be? The other thing I noticed is in my office 00:07:45.916 --> 00:07:49.696 slash the bathroom, because JOOPS is a small space after all. 00:07:49.876 --> 00:07:52.756 the automatic lighting and heating wasn't working. 00:07:53.496 --> 00:07:58.656 And so like when you enter the room, presence is detected and a WLED light strip 00:07:58.656 --> 00:08:03.376 that's in a diffuser that spans the length of the wall turns on and in the night, 00:08:03.436 --> 00:08:05.016 it's a real soft ambient glow. 00:08:05.156 --> 00:08:08.896 And during the day, it's a little brighter and it just wasn't triggering at all. 00:08:09.436 --> 00:08:13.336 And I noticed the heat wasn't triggering. So I start doing the math and I'm like, oh, 00:08:14.690 --> 00:08:19.210 These are all Zigbee devices. These are all Zigbee devices that are not working. 00:08:20.010 --> 00:08:26.930 So I sat down at Old Home Assistant, and the first thing I noticed is I had 00:08:26.930 --> 00:08:32.070 never seen this before, but there was an update pending for my Zigbee radio. 00:08:32.450 --> 00:08:37.290 And then just as a refresher here, you have smart devices of all kinds, right? 00:08:37.370 --> 00:08:41.170 Like Wi-Fi connected, Zigbee connected, and Z-Wave connected. 00:08:41.390 --> 00:08:43.330 And this is particularly a Zigbee issue. 00:08:43.490 --> 00:08:47.730 Yes. So not everything was broken. So it wasn't obvious at first because a lot 00:08:47.730 --> 00:08:49.090 of things are Z-Wave or Wi-Fi. 00:08:49.350 --> 00:08:55.330 But it's the really low power cheap stuff because Zigbee is 2.4 gigahertz based. 00:08:55.630 --> 00:08:56.490 You don't have to get it licensed. 00:08:56.790 --> 00:09:02.150 And so it brings the cost down. It's like a lot of little plugs and buttons and stuff are Zigbee. 00:09:03.450 --> 00:09:07.190 I won't be buying those anymore. But so I saw this firmware update, 00:09:07.310 --> 00:09:11.070 which I'd never seen before for my Home Assistant Yellow's built in Zigbee radio 00:09:11.070 --> 00:09:14.790 adapter. And I didn't apply it because I kind of wanted to figure out why things weren't working. 00:09:14.970 --> 00:09:17.030 I did later install it as a troubleshoot. And I was like, you know, 00:09:17.110 --> 00:09:19.750 when you're at the YOLO stage, you're like, all right, I'll try the firmware update. 00:09:19.850 --> 00:09:22.070 Right, at this point. Is it going to break worse? 00:09:22.150 --> 00:09:25.930 I don't know. Right, exactly. I did get to that point, but I wasn't there yet. 00:09:26.390 --> 00:09:31.050 So I popped into the Zigbee integration, and I noticed that it was in a failed-to-initialized 00:09:31.050 --> 00:09:33.030 state. And I noticed something was off. 00:09:33.770 --> 00:09:39.590 Home Assistant now listed two identical Zigbee radios that had the same duplicate 00:09:39.590 --> 00:09:44.290 devices. One was labeled like the Home Assistant Yellow Zigbee and one was labeled 00:09:44.290 --> 00:09:46.270 Hub Z Zigbee Comport Controller. 00:09:48.035 --> 00:09:52.195 did i maybe did i connect a second one right that's strange. 00:09:52.195 --> 00:09:54.435 You like we're halfway through a switch. 00:09:54.435 --> 00:09:54.895 Or playing. 00:09:54.895 --> 00:09:58.675 With something forgot about it never went back the thing rebooted now it sees it. 00:09:58.675 --> 00:10:00.195 Weren't you planning on buying an upgrade. 00:10:00.195 --> 00:10:03.895 Yeah i thought well maybe i wanted to right i was like maybe i was gonna set 00:10:03.895 --> 00:10:09.795 up an upgrade or something like that so you know i'm looking ls usb then i physically 00:10:09.795 --> 00:10:14.215 look at the device i'm like no i only have one radio on this thing what's going on here, 00:10:14.875 --> 00:10:17.555 Maybe there was something I had done wrong, but as far as I could tell, 00:10:17.795 --> 00:10:20.195 a second ghost adapter had just shown up. 00:10:20.935 --> 00:10:23.675 And I didn't really know what to do. I turned on the debug logs. 00:10:23.795 --> 00:10:26.055 They told me that the Zigbee service couldn't start. 00:10:26.235 --> 00:10:30.235 All of the online stuff says, well, maybe you have another integration that's conflicting. I did not. 00:10:30.775 --> 00:10:35.615 So I YOLO'd in and I decided I'm going to delete one of these adapters, 00:10:36.055 --> 00:10:37.975 but I don't know which one to delete. 00:10:38.175 --> 00:10:42.875 Do I delete the one that's named correctly or this new ghost one that shows up? 00:10:43.515 --> 00:10:47.875 I don't know, Brent, which one, in this case, which adapter rolling the dice would you delete? 00:10:48.275 --> 00:10:52.635 Well, and I feel like you didn't necessarily look, you haven't looked at this 00:10:52.635 --> 00:10:56.035 in the past because it's just like a thing you don't need to worry about. 00:10:56.155 --> 00:10:58.815 So you don't actually have a memory of what it's named. 00:10:58.975 --> 00:11:02.635 You didn't put a custom name on this adapter or anything. It's just like a 50-50? 00:11:03.235 --> 00:11:03.595 Yeah. 00:11:04.995 --> 00:11:06.615 Oh, gosh. I guess... 00:11:09.128 --> 00:11:14.168 I guess I would want to delete the one that didn't sound like Linux had named it. 00:11:14.688 --> 00:11:20.848 Okay, but in theory, Home Assistant was configured to work with the correctly named one. 00:11:20.968 --> 00:11:21.328 Yes. 00:11:21.408 --> 00:11:22.248 But was not working. 00:11:22.428 --> 00:11:24.408 Correct. That was my thinking. 00:11:24.568 --> 00:11:26.128 Yeah, okay. I can see the argument. 00:11:26.408 --> 00:11:30.108 So I went ahead and I deleted the one labeled Home Assistant yellow Zigbee adapter. 00:11:30.308 --> 00:11:32.988 Wow. That's risky. Wow. 00:11:33.268 --> 00:11:39.188 No, I didn't know. And I'm like, and it's like, do I just lose all my devices? and my oh right. 00:11:39.188 --> 00:11:41.088 Is this like a cascade delete that'll just. 00:11:41.088 --> 00:11:45.448 Right okay and I have to repair everything or something and then also I'm doing 00:11:45.448 --> 00:11:48.528 the math on like the cost could I could I just, 00:11:50.248 --> 00:11:55.708 replace them with Zigbee versions but it's like 30 ish devices so maybe even 00:11:55.708 --> 00:12:01.328 more it might be 60 I don't know it's a lot of devices it's between 60 and 30 this. 00:12:01.328 --> 00:12:02.308 Is an unbudgeted. 00:12:02.308 --> 00:12:04.008 Cost here exactly this. 00:12:04.008 --> 00:12:05.348 Is how you know you have a problem. 00:12:05.348 --> 00:12:09.108 Oh well you know there's a lot of sensors There's a lot of sensors and motion 00:12:09.108 --> 00:12:11.308 and open and close sensors. 00:12:12.548 --> 00:12:17.508 So I delete the one that's properly labeled, and I just hope that the generic 00:12:17.508 --> 00:12:20.488 Hub Z Zigbee Comport controller one is the correct one. 00:12:20.768 --> 00:12:27.048 I delete it, and I reboot the box because there isn't a built-in way to just restart Zigbee. 00:12:27.648 --> 00:12:30.988 You just got to restart Home Assistant and reboot the whole box. 00:12:31.128 --> 00:12:36.768 So I did that, and it came back up, and my Zigbee devices were just working. 00:12:36.828 --> 00:12:43.308 and the Zigbee integration started and apparently I randomly picked the right 00:12:43.308 --> 00:12:45.708 one to delete and everything resumed. 00:12:46.268 --> 00:12:49.488 So I've been trying to track down what kind of happened here. 00:12:49.968 --> 00:12:55.308 And my best guess is a firmware update, maybe I did apply it and I don't remember 00:12:55.308 --> 00:12:57.148 or it was partially applied automatically. 00:12:58.208 --> 00:13:03.608 It somehow changed the state of the radio and the Linux system underneath ended 00:13:03.608 --> 00:13:08.728 up exposing multiple serial endpoints or something. when this happened. And then... 00:13:09.652 --> 00:13:13.472 There was a conflict, the firmware update couldn't continue, 00:13:13.692 --> 00:13:15.392 and things ended in this sort of hung state. 00:13:15.952 --> 00:13:19.832 The Zigbee integration saw both endpoints trying to connect to it. 00:13:20.532 --> 00:13:24.392 And by deleting the non-functional entry, I forced the Zigbee integration to 00:13:24.392 --> 00:13:28.612 rebind to the working controller, even though maybe both were working, 00:13:28.712 --> 00:13:30.692 I don't know, and then restored the network. 00:13:31.112 --> 00:13:34.312 But I'm not sure. And the thing that sucks is the entire time I was in Texas, 00:13:34.632 --> 00:13:39.492 none of the Zigbee devices were working. So a lot of the presence detection stuff was just broken. 00:13:39.652 --> 00:13:41.312 And you couldn't do anything. You were on the road. 00:13:41.952 --> 00:13:44.932 Couldn't do anything. And I have no idea what caused it, really. 00:13:45.132 --> 00:13:48.112 And you hadn't, like, done some big update. Obviously, you hadn't done the firmware 00:13:48.112 --> 00:13:51.732 update. That would maybe make sense if the name changed post-firmware. 00:13:51.872 --> 00:13:52.412 I agree. 00:13:52.612 --> 00:13:53.452 I have a theory. 00:13:53.832 --> 00:13:54.652 Uh-huh. Please. 00:13:54.732 --> 00:13:58.792 Your dear, lovely wife has been listening to you gripe about that, 00:13:58.812 --> 00:14:00.832 you know, you need a new controller. 00:14:00.832 --> 00:14:06.952 so she got some advice from you know close friends and got a new one and tried to like in the night, 00:14:07.512 --> 00:14:12.172 plug it in and see if it just kind of worked and uh then all of a sudden everything 00:14:12.172 --> 00:14:16.132 went wrong and she just quietly hid it and returned it to amazon. 00:14:16.132 --> 00:14:21.072 I like this theory but wouldn't you be implicated in this story most likely i'm. 00:14:21.072 --> 00:14:22.332 Just trying to save her at this point. 00:14:22.332 --> 00:14:25.052 I did think it 00:14:25.052 --> 00:14:29.532 was funny the day after i solved all of this not related but the day after i 00:14:29.532 --> 00:14:33.652 solved all of this the home assistant team posted on x that they're ending production 00:14:33.652 --> 00:14:37.392 of the home assistant yellow they're going to continue to support it so it's 00:14:37.392 --> 00:14:42.812 still going to get patches and updates but that's no longer in production is. 00:14:42.812 --> 00:14:46.252 It possible like home assistant did some sort of auto updates that happen. 00:14:46.892 --> 00:14:50.272 I have to go in and turn them on it could have been it could have happened after 00:14:50.272 --> 00:14:53.612 the last os update and i didn't notice at first because so many things were still working, 00:14:55.285 --> 00:14:58.005 Um, because like Brent said, it's one of these things that you don't really 00:14:58.005 --> 00:15:00.985 think about. It has been so consistent and so reliable. 00:15:01.465 --> 00:15:05.485 And thankfully this turned out to be a pretty minor thing to correct. 00:15:05.765 --> 00:15:09.765 The implications and the risk were high, but it was pretty minor thing. 00:15:10.225 --> 00:15:14.445 Uh, but I, it has got me thinking about like what to do in the future. 00:15:15.285 --> 00:15:18.185 Right. Cause this was stuff that was just shipped on the device, 00:15:18.205 --> 00:15:21.785 right? You kind of just bought this one box to run home assistant with Zigbee built in. 00:15:21.865 --> 00:15:22.725 And now it's out of production. 00:15:23.425 --> 00:15:25.605 So you can't just hot swap into a new one. 00:15:25.605 --> 00:15:28.965 Can't just hot swap i mean it'll be supportive for a while but and 00:15:28.965 --> 00:15:31.905 also i think i'm outgrowing this even you know 00:15:31.905 --> 00:15:34.765 i noticed this especially when we built brent's new home assistant 00:15:34.765 --> 00:15:38.825 i just don't quite have enough horsepower but i also i kind of been rethinking 00:15:38.825 --> 00:15:43.405 the way to do my mobile home lab and change up the hardware in general and it 00:15:43.405 --> 00:15:47.605 seems like maybe this this home assistant yellow going out of you know going 00:15:47.605 --> 00:15:54.165 end of life and my I need to kind of rework my home lab hardware in my RV for my mobile home lab. 00:15:54.265 --> 00:15:58.225 The two things are kind of coming together, and I'm kind of starting to form a plan. 00:16:01.605 --> 00:16:05.525 1password.com slash unplugged. That's the number one password, 00:16:05.525 --> 00:16:07.685 and then it's unplugged. It's all lowercase. 00:16:07.865 --> 00:16:10.865 Go there to take the first steps for better security for your team, 00:16:11.085 --> 00:16:14.845 for your company, by securing credentials and protecting every application, 00:16:15.025 --> 00:16:20.225 even the unmanaged stuff you didn't know about. Learn more at 1password.com slash unplugged. 00:16:20.465 --> 00:16:24.065 If your employees are bypassing security to use unapproved apps, 00:16:24.145 --> 00:16:27.545 they might not even realize they're doing it, they probably feel they have to 00:16:27.545 --> 00:16:29.125 do it to just get their job done. 00:16:29.285 --> 00:16:35.285 And you can kind of connect with that viewpoint, but it's a very challenging position for IT. 00:16:35.505 --> 00:16:38.025 And if you're experiencing this, you're not alone. 00:16:38.425 --> 00:16:43.405 Fortunately, 1Password Extended Access Management will help you get your hands 00:16:43.405 --> 00:16:45.745 around this. You can be careful about security. 00:16:47.198 --> 00:16:49.878 You can't help it if users are going up and signing up for things and signing 00:16:49.878 --> 00:16:53.278 up for applications perhaps you're even already paying for, but they're doing 00:16:53.278 --> 00:16:54.278 it under their own credentials. 00:16:54.538 --> 00:16:56.298 This is where Trellica by 1Password 00:16:56.298 --> 00:16:59.558 really comes in. It inventories every app in use at your company. 00:16:59.778 --> 00:17:03.058 They have pre-populated app profiles that can assess the different risks, 00:17:03.178 --> 00:17:08.258 and they let you manage access, optimize your spend, and enforce best security 00:17:08.258 --> 00:17:12.938 practices across all the apps your employees are actually using. That's right. 00:17:13.298 --> 00:17:17.358 And for me, the thing that I was always struggling with and every client I always 00:17:17.358 --> 00:17:23.058 went to seemed to struggle with, they needed a process to securely onboard and off-board staff. 00:17:23.418 --> 00:17:25.598 Sometimes you'd have one that would last for a little while, 00:17:25.598 --> 00:17:28.958 but you really want something these days that will also help you meet compliance goals. 00:17:29.278 --> 00:17:31.998 Well, Trelica by 1Password provides a complete solution for that. 00:17:32.298 --> 00:17:36.258 Access governance is solved, and it's just one of the ways extended access management 00:17:36.258 --> 00:17:40.378 helps the team and you strengthen compliance and security. 00:17:40.638 --> 00:17:43.518 You know about 1Password and their award-winning password manager, 00:17:43.558 --> 00:17:45.058 of course, is trusted by millions of users. 00:17:45.578 --> 00:17:50.118 Take a second and ask yourself, how many SaaS applications are being used at your company right now? 00:17:50.838 --> 00:17:55.718 If you can't keep count, you're not alone. So go to 1password.com slash unplugged. 00:17:55.798 --> 00:17:58.938 Take the first steps to better security for your team by securing credentials 00:17:58.938 --> 00:18:02.218 and protecting every application, even the unmanaged stuff. 00:18:02.378 --> 00:18:05.258 It's really powerful. It's a great way to support the show, and you can learn 00:18:05.258 --> 00:18:08.058 more by going to 1password.com slash unplugged. 00:18:08.278 --> 00:18:12.758 That's all lowercase. It's the number 1password.com slash unplugged. 00:18:12.758 --> 00:18:16.618 Check compliance off your list with a system of record for your app inventory 00:18:16.618 --> 00:18:18.558 and employee lifecycle workflows. 00:18:18.878 --> 00:18:21.318 1password.com slash unplugged. 00:18:23.253 --> 00:18:27.573 Join crowdhealth.com slash unplugged. If you've followed me for a while, 00:18:27.713 --> 00:18:30.213 you know I have really struggled with trying to figure out healthcare. 00:18:30.473 --> 00:18:34.313 A small business that's a really small team, there's really no great options. 00:18:34.833 --> 00:18:39.473 My wife also is a type 1 diabetic, and so that makes things extra expensive 00:18:39.473 --> 00:18:41.973 for her, and she also runs her own small business. 00:18:42.253 --> 00:18:46.353 This has been something that has just really been a big stressor for us. 00:18:46.433 --> 00:18:49.693 But if you've noticed, I haven't really complained about it much recently. 00:18:49.693 --> 00:18:53.653 That's because just over three years ago, I joined CrowdHealth. 00:18:54.013 --> 00:18:57.253 And right now it's open enrollment, the season where the health insurance companies 00:18:57.253 --> 00:18:58.353 are going to hope you sign up. 00:18:58.913 --> 00:19:01.793 Even though things are getting overpriced, they're becoming a political football, 00:19:01.793 --> 00:19:04.273 and there's lots of confusing fine print. 00:19:04.633 --> 00:19:08.973 But don't take my word for it. Go over there. Check it out. Just see if it might 00:19:08.973 --> 00:19:10.453 make sense for you and your family. 00:19:11.273 --> 00:19:15.653 DrawingCrowdHealth.com slash unplugged. I wouldn't be talking about it if I 00:19:15.653 --> 00:19:19.553 hadn't tried this for myself and my wife for a long time. And it's something 00:19:19.553 --> 00:19:22.593 I'm very comfortable with. In fact, it's something that gives me peace of mind. 00:19:23.113 --> 00:19:27.713 I found the entire game of trying to pick insurance, pay the different prices all the time. 00:19:27.813 --> 00:19:31.693 And then, of course, you know, on the back end, they generally try to weasel 00:19:31.693 --> 00:19:32.973 out of actually helping you. 00:19:33.920 --> 00:19:36.800 CrowdHealth is different. It's a community of people funding each other's medical 00:19:36.800 --> 00:19:40.080 bills directly. No middlemen, no networks, no nonsense. 00:19:40.660 --> 00:19:44.580 Now, for me, when I signed up, I didn't really know what I'd be getting into 00:19:44.580 --> 00:19:48.320 because it's a new idea. But CrowdHealth is actually something that's been around for a while. 00:19:48.680 --> 00:19:52.360 The idea is just modernized with the ability to have apps and the Internet. 00:19:53.000 --> 00:19:58.380 And now, three years into it, I'm really glad we went this route and we have saved a ton of money. 00:19:58.620 --> 00:20:01.840 You've got to check out CrowdHealth, the health insurance alternative. 00:20:02.320 --> 00:20:06.720 Healthcare for under $100. You get access to a team of health bill negotiators, 00:20:07.160 --> 00:20:10.980 low-cost prescription and lab testing tools, as well as a database of low-cost, 00:20:11.060 --> 00:20:13.640 high-quality doctors that are vetted by CrowdHealth. 00:20:14.160 --> 00:20:17.920 They also have a fantastic app that they have improved on over the three years 00:20:17.920 --> 00:20:22.760 that I have been a member, and it just makes it so easy to get started with the process. 00:20:22.940 --> 00:20:25.520 From, oh, I think something's wrong to, hey, I have a bill. 00:20:26.060 --> 00:20:28.700 It really is pretty powerful. And if something major happens, 00:20:28.920 --> 00:20:34.200 you pay the first $500, and then CrowdHealth steps in with the crowd to fund the rest. 00:20:34.740 --> 00:20:39.700 It feels like the options we used to have before Obamacare, in my opinion, messed everything up. 00:20:39.840 --> 00:20:43.160 As a small business owner, it has been disastrous since then, 00:20:43.740 --> 00:20:45.680 especially if you have two of us in the family. 00:20:46.480 --> 00:20:49.960 And, of course, you'll join the crowd, a group of members just like you that 00:20:49.960 --> 00:20:52.460 want to help pay for each other's unexpected medical events. 00:20:53.020 --> 00:20:54.220 The system is betting that you'll 00:20:54.220 --> 00:20:57.520 stay stuck. You'll just use the same overpriced, overcomplicated mess. 00:20:57.860 --> 00:21:02.300 And this year, it's even more complicated because most of the ACA subsidies 00:21:02.300 --> 00:21:05.960 are set to expire, which means your prices could go sky high. 00:21:06.260 --> 00:21:10.720 So far, CrowdHealth members have saved over $40 million in health care expenses 00:21:10.720 --> 00:21:13.240 because they refuse to overpay for health care. 00:21:13.840 --> 00:21:17.360 This is open enrollment. Take your power back. Join CrowdHealth to get started. 00:21:17.660 --> 00:21:20.640 Join the crowd with me for $99 for your first three months. 00:21:21.540 --> 00:21:26.580 $99. Just use the promo code unplugged at joincrowdhealth.com. 00:21:27.719 --> 00:21:32.899 Join crowdhealth.com promo code unplugged. Crowd health is not insurance. 00:21:33.179 --> 00:21:35.519 Opt out. Take your power back. This 00:21:35.519 --> 00:21:40.619 is how we win. Join me over at joincrowdhealth.com promo code unplugged. 00:21:43.680 --> 00:21:47.360 Now, Chris, you and I care quite a lot about power usage. And, 00:21:47.560 --> 00:21:50.120 well, you mentioned how stats is a game changer for you. 00:21:50.220 --> 00:21:55.620 So I would imagine that's top of mind for you in designing this potential new situation. 00:21:56.220 --> 00:21:59.480 The next-gen build. Can I call it that? I don't know. Is that too corny? 00:21:59.940 --> 00:22:02.320 But it feels really... I feel like it's going to be my next-gen build. 00:22:02.720 --> 00:22:07.460 Yeah, obviously Raspberry Pis could be one route. You get like a max of 10 watts there. 00:22:07.820 --> 00:22:10.340 Yeah, did you jump off at the 4? When did you make it? Okay. 00:22:10.540 --> 00:22:13.140 So there is at least a generation to change. 00:22:14.480 --> 00:22:21.800 Of course, the N100 or N150 Intel platform, pretty competitive, 8 to 12 watts when idle. 00:22:22.120 --> 00:22:22.880 Not bad. 00:22:23.120 --> 00:22:29.100 Not too bad. And then there's the optimized TMM mini PC chips, 7 to 12 watts when idle. 00:22:29.280 --> 00:22:31.160 And then, of course, a desktop PC is going to be like, what, 00:22:31.220 --> 00:22:33.760 45 watts, something like that when idle? That's not really an option. 00:22:33.900 --> 00:22:37.760 If you're running off of a lithium battery bank and solar, every little watt 00:22:37.760 --> 00:22:40.280 counts because it's always going, right? 00:22:40.320 --> 00:22:43.340 It's a cumulative thing. so I think oh. 00:22:43.340 --> 00:22:44.980 That's why you didn't include Xeon on the. 00:22:44.980 --> 00:22:54.020 Right I think my ideal would be like an N100 N150 low power x86 PC that runs 00:22:54.020 --> 00:22:58.060 everything so right now I have a pie hole and I have a, 00:22:58.720 --> 00:23:03.760 raspberry pi that does camera feeds when I turn it on and then I have an oDroid that runs my, 00:23:05.160 --> 00:23:09.340 entire self hosting home stack basically all the applications we talk about 00:23:09.340 --> 00:23:12.420 on this show it's You know, got to be damn near 30 apps running on that thing. 00:23:12.620 --> 00:23:16.620 And, you know, on the top of the list, Jellyfin and Nextcloud and ersatz TV 00:23:16.620 --> 00:23:19.720 and, you know, like really important stuff that I use every single day. 00:23:19.880 --> 00:23:21.300 So it's like a pretty critical box. 00:23:21.880 --> 00:23:25.240 And why not replace that? Oh, and then I have the Home Assistant Yellow. 00:23:25.500 --> 00:23:30.500 Why not replace all of those with one mini PC if possible? 00:23:30.740 --> 00:23:34.280 That would be the ideal, right? But Home Assistant, Jellyfin and all the R tools 00:23:34.280 --> 00:23:37.520 and Image and Nextcloud and ersatz, et cetera, et cetera, et cetera. 00:23:37.520 --> 00:23:41.020 put that all on one system using VMs, 00:23:42.683 --> 00:23:46.203 But I think I'm worried, and I would really like the audience's feedback here, 00:23:46.243 --> 00:23:48.203 because I'm kind of hoping to do this early 2026. 00:23:49.383 --> 00:23:52.103 I don't know if I can find a box powerful enough to host all that. 00:23:52.803 --> 00:23:58.243 Because I want a significant upgrade for Home Assistant, but then I want the 00:23:58.243 --> 00:24:01.743 headroom to run all of this stuff, and things like Image and ersatz TV that 00:24:01.743 --> 00:24:02.743 need hardware acceleration. 00:24:03.203 --> 00:24:08.663 And you're not really willing to cut things, at least to start, right? So, yeah. 00:24:08.963 --> 00:24:11.783 You want more, but your power budget isn't more. Right. 00:24:12.683 --> 00:24:16.963 But Chris, I remember your argument when you were orchestrating this current 00:24:16.963 --> 00:24:22.483 build was you wanted Home Assistant on its own device so that if the machine 00:24:22.483 --> 00:24:26.263 you keep adding more VMs to decides to, you know, 00:24:26.923 --> 00:24:34.343 not go so hot, then your home stays consistent and stays constant and you're 00:24:34.343 --> 00:24:36.383 never tinkering with that particular application. 00:24:36.383 --> 00:24:39.483 So why the move away from that philosophy? 00:24:39.743 --> 00:24:42.123 I think it's a great philosophy. I blame Wes. 00:24:42.123 --> 00:24:43.403 What did I do? 00:24:43.583 --> 00:24:46.563 Well, we were talking about it last night, and we'll get into it more. 00:24:46.923 --> 00:24:51.143 And it just sort of like it... When you're switching to the Intel platform and 00:24:51.143 --> 00:24:52.023 you're using more power... 00:24:53.163 --> 00:24:56.983 I can't have multiple boxes. Like that's where my power savings has to come 00:24:56.983 --> 00:24:58.723 from is I eliminate some of the boxes. 00:24:59.663 --> 00:25:02.763 Because it's not just, it's like I'm going to put as much storage into these 00:25:02.763 --> 00:25:06.303 things as possible. They're going to have external devices plugged into them. That draws power. 00:25:07.123 --> 00:25:12.303 So as a matter of compromise, I think I'm going to go to VM isolation for like 00:25:12.303 --> 00:25:15.363 things like Home Assistant or something and just do one box. 00:25:15.463 --> 00:25:18.203 It's not really my preference, but because I want to get more out of Home Assistant, 00:25:18.283 --> 00:25:20.463 I would like to increase the performance of Home Assistant. 00:25:20.803 --> 00:25:25.123 I think I'm at the limits of what I'm going to get from the ARM platforms right now. I could be wrong. 00:25:25.703 --> 00:25:28.963 But something that's like, I don't know if it's out there, an N150 that takes 00:25:28.963 --> 00:25:33.163 32 gigs of RAM and you could put up to 8 terabytes of storage in. 00:25:33.383 --> 00:25:34.783 Is such a thing out there? 00:25:35.623 --> 00:25:39.503 I'm not so sure. I was also looking at maybe some of the quote-unquote enterprise 00:25:39.503 --> 00:25:45.223 hardware, like a ThinkCenter M720Q or an Optiplex 3070. Have you looked at these? 00:25:45.643 --> 00:25:46.803 Yeah, only a little bit. 00:25:46.963 --> 00:25:50.183 They're really impressive little boxes for the size and the price. 00:25:50.183 --> 00:25:55.143 So even if, so I think for some people, they're probably exactly what you would need right now. 00:25:55.243 --> 00:26:00.343 Like the ThinkCenter M7020Q is $205. 00:26:00.603 --> 00:26:04.523 It has an i5-8400T, which means it's the lower power variant. 00:26:05.003 --> 00:26:08.743 And it has eight gigs of RAM, but I'm pretty sure it goes up to 32. 00:26:09.823 --> 00:26:11.563 Yeah, that's the key detail right there. 00:26:12.283 --> 00:26:13.443 And the Optiplex. 00:26:13.783 --> 00:26:14.903 They really are a great. 00:26:15.183 --> 00:26:22.843 Lean, mean, again, an i5-9500T. 256 gigabyte SSD in there but you can pop it 00:26:22.843 --> 00:26:28.003 up again I believe yeah it says right here up to 32 gigabytes of 266 megahertz DDR4, 00:26:29.675 --> 00:26:32.735 Now, if this could take the storage, I don't know. So these little enterprise, 00:26:32.875 --> 00:26:37.355 this one's, although, $550. So I don't know about that. 00:26:38.235 --> 00:26:44.455 What about heat management? Because I know your current boxes are sort of solid state, right? 00:26:44.555 --> 00:26:47.955 They don't have moving fans or anything like that, and you have them in a little cupboard. 00:26:48.175 --> 00:26:50.235 So have you thought about this aspect? 00:26:51.195 --> 00:26:55.915 Yeah, that's a good question. It does get hot in there. The Odroid H3 has survived, though. 00:26:57.455 --> 00:26:59.575 The H4 might be enough for all of this. 00:27:00.375 --> 00:27:09.475 Over in matrix uh swami comes in with a uh minis forum ms01 workstation uh what they're using. 00:27:11.655 --> 00:27:13.735 Okay to me it feels like. 00:27:13.735 --> 00:27:15.935 Up to 24 terabytes of ssd storage. 00:27:15.935 --> 00:27:19.855 Like there's like this trifecta problem you know you can have speed you can 00:27:19.855 --> 00:27:23.535 have power efficiency or you can have all the storage and gadgets and i'm trying 00:27:23.535 --> 00:27:28.815 to like have all three and maybe i'm not over asking but just my initial look 00:27:28.815 --> 00:27:30.095 here. Oh, this is really nice though. 00:27:30.335 --> 00:27:34.075 So this is $480 US greenbacks. 00:27:35.709 --> 00:27:43.729 And it has a 13th generation i9, 24 terabytes of SSD storage up to, PCI4. 00:27:44.009 --> 00:27:46.049 My question would be is what is its idle draw? 00:27:46.249 --> 00:27:47.509 Yeah, that was going to be my question. 00:27:47.609 --> 00:27:52.729 See, an i9-2900H. I don't know what the power draw is on that. 00:27:53.149 --> 00:27:55.229 It's really hard. I know this. 00:27:56.169 --> 00:28:00.969 I've really enjoyed the yellow. It's really been a nice sweet spot here on the 00:28:00.969 --> 00:28:02.269 power to performance ratio. 00:28:02.489 --> 00:28:04.969 Do they have any other first-party hardware that interests you? 00:28:05.929 --> 00:28:10.369 Not really. No, just the power isn't really there. They have a blue and I want 00:28:10.369 --> 00:28:12.509 something more robust. It's fine. 00:28:13.489 --> 00:28:18.129 But when you think about it, what I'm trying to get is I want the webpages to render faster. 00:28:18.369 --> 00:28:21.389 I want the dashboard to render faster because when you're trying to do something 00:28:21.389 --> 00:28:23.509 really quick, you want the best performance possible. 00:28:24.109 --> 00:28:27.409 So now I'm trying to get to like, okay, how do I get this? And I think I'm at 00:28:27.409 --> 00:28:30.849 the limits of what a CM4 can deliver me there. 00:28:31.729 --> 00:28:35.249 But also, okay, so I have not figured out the hardware, but that's sort of the 00:28:35.249 --> 00:28:41.589 direction I'm trending, if possible, is an N150 or a T-series chip that gets 00:28:41.589 --> 00:28:42.389 me the performance I want. 00:28:42.429 --> 00:28:45.509 I have no idea if there's anything in the Ryzen world that would do this. 00:28:45.589 --> 00:28:49.589 I would love to hear about that, if anybody could boost in or send us an email with that. 00:28:50.389 --> 00:28:57.729 or my other option is run multiple boxes get really crappy cheap N100s and run 00:28:57.729 --> 00:28:59.549 a couple of those but yeah do you. 00:28:59.549 --> 00:29:00.249 Have the budget for two? 00:29:02.047 --> 00:29:03.047 If the price is right. 00:29:03.487 --> 00:29:09.727 You know, just one home assistant and maybe a couple other related services that fit the domain. 00:29:09.887 --> 00:29:14.527 If the price was right and the power draw worked out, I really can't afford to spend any more power. 00:29:15.107 --> 00:29:17.627 That's the most expensive thing for me right now because the current system 00:29:17.627 --> 00:29:18.927 is drawing a little bit more than I'd like. 00:29:19.307 --> 00:29:21.127 I think the other thing I'm going to do is I'm going to phase out Zigbee. 00:29:21.187 --> 00:29:22.647 I'm just going to start replacing those devices. 00:29:22.887 --> 00:29:27.567 My next build is going to use that new fancy home assistant connect ZWA2 Z-Wave 00:29:27.567 --> 00:29:31.367 that is really, really good. So that'll be my future plan. 00:29:32.047 --> 00:29:36.147 I'm going to phase out Zigbee. I liked the idea behind it, but it just hasn't worked for me. 00:29:36.747 --> 00:29:40.927 But I have a sense, Wes, that me kind of YOLOing and deleting adapters and then 00:29:40.927 --> 00:29:45.147 replicating Home Assistant OS in a VM on a new box, I don't know. 00:29:45.207 --> 00:29:48.067 I just have a feeling maybe not how you would do it. 00:29:48.447 --> 00:29:50.627 So how would you fix it right, Dr. Wes? 00:29:51.147 --> 00:29:53.747 Oh, I don't know if you could really call it fixing it right, 00:29:53.767 --> 00:29:58.087 but have you ever considered your old pal NixOS? 00:29:59.487 --> 00:30:03.107 Oh, why am I not surprised? Brent, are you surprised? 00:30:03.507 --> 00:30:05.287 I saw this coming from a mile away. 00:30:06.267 --> 00:30:10.087 You know, actually, I might have a better time on the sales pitch too, 00:30:10.247 --> 00:30:11.607 Brent, because he started out new. 00:30:11.767 --> 00:30:11.887 Yeah. 00:30:12.127 --> 00:30:16.167 And I think probably the main difficulty for you is you just have a lot of functionality 00:30:16.167 --> 00:30:18.387 that you don't want to give up and you would need to port. 00:30:18.887 --> 00:30:19.967 A lot of add-ons. 00:30:20.267 --> 00:30:20.387 Right. 00:30:20.567 --> 00:30:25.627 Little silly things like UI tweaks and new cards and new ways to graph things 00:30:25.627 --> 00:30:27.887 that come into the add-on store and whatnot. 00:30:28.087 --> 00:30:31.187 Although maybe it's possible to add the add-on store through Nix. I have no idea. 00:30:31.367 --> 00:30:35.067 No, I don't think so. They don't explicitly support it, at least with the module. 00:30:35.207 --> 00:30:38.527 I mean, you could do it on your own, because I think the add-ons are mostly talker containers. 00:30:38.647 --> 00:30:39.107 Yes, exactly. 00:30:39.287 --> 00:30:44.387 So you could run those. Or, like, what I'm doing is a lot of them just have 00:30:44.387 --> 00:30:46.827 NixOS modules for what you're running, right? 00:30:46.887 --> 00:30:51.547 So, like, music assistant, instead of an add-on, it's just another service that I run at the NixOS. 00:30:51.547 --> 00:30:52.587 And it's just in a different tab, yeah. 00:30:52.627 --> 00:30:52.707 Yeah. 00:30:53.744 --> 00:30:56.724 So there are some changes that you have to get used to. We started looking into 00:30:56.724 --> 00:31:00.964 this a little bit because I am currently running it this way. 00:31:01.224 --> 00:31:04.284 And I thought it'd be interesting to kind of look and see some of the things 00:31:04.284 --> 00:31:07.244 like that, you know, does it have enough of the stuff that you might need? 00:31:07.744 --> 00:31:12.064 It is kind of great because they do support, I mean, I think they say they have 00:31:12.064 --> 00:31:18.004 something like, they support like 90 plus percent of like the built-in stuff. A lot of it's Python. 00:31:18.504 --> 00:31:22.104 So anything that has, you know, if they have the dependency package for that, 00:31:22.104 --> 00:31:24.984 it makes it very easy to get that added to your setup. 00:31:25.364 --> 00:31:28.704 And so you can add any of the sort of extra components that you might want, 00:31:28.744 --> 00:31:34.024 but also you can do custom components and they support the custom Lovelace modules as well. 00:31:34.484 --> 00:31:37.544 And so you just sort of add all of the ones that you want into your config, 00:31:37.724 --> 00:31:39.204 right? There's services.homeassistant. 00:31:39.564 --> 00:31:43.244 So like I added, checking out stuff, you were using Mushroom, 00:31:43.444 --> 00:31:47.004 ClockWeatherCard, MiniGraphCard, LG WebOS Remote Control. 00:31:47.104 --> 00:31:49.384 I mean, I'm not going to use like, because I don't have a WebOS TV at the moment, 00:31:49.464 --> 00:31:50.464 but just to see, you know. 00:31:50.464 --> 00:31:55.344 and then you rebuild and that's it i mean you still got to go in and you know 00:31:55.344 --> 00:31:58.644 customize it i think there's ways to do even more stuff declaratively but for 00:31:58.644 --> 00:32:02.664 the most part i've just used it to get like all the dependencies and the core 00:32:02.664 --> 00:32:05.564 stuff set up and running and then i can go from there. 00:32:05.564 --> 00:32:08.584 Have you gone through an update cycle or so with home assistant. 00:32:08.584 --> 00:32:12.324 Yeah it's been going for more than a couple of months yeah 00:32:12.324 --> 00:32:15.504 i think at one point with esp home i disabled it for one update 00:32:15.504 --> 00:32:18.344 cycle i wasn't doing anything with it at the moment anyway so 00:32:18.344 --> 00:32:21.064 it was it was pretty easy and i could have pinned it if i if i'd 00:32:21.064 --> 00:32:24.244 cared to but that hasn't been a problem since it is 00:32:24.244 --> 00:32:27.324 um the way i have it set up i am building like home 00:32:27.324 --> 00:32:30.144 assistant most of the updates so that does take you know 10 00:32:30.144 --> 00:32:33.644 minutes or so depending on the power of the box you're using this is not an 00:32:33.644 --> 00:32:37.884 especially powerful box but that has not had any issues at all so and i don't 00:32:37.884 --> 00:32:41.044 really mind that because this is another box that i kind of run things i don't 00:32:41.044 --> 00:32:44.404 need to update a ton and are more of the infrastructure layer it's also my router 00:32:44.404 --> 00:32:47.464 more occasional updates yeah i love that you run it on your router you maniac. 00:32:48.844 --> 00:32:50.604 Also, his router is an Xbox. Yes. 00:32:50.724 --> 00:32:50.804 Yeah. 00:32:51.732 --> 00:32:54.172 Which also doesn't need to do very much. And so I update it like, 00:32:54.212 --> 00:32:58.452 you know, once or twice a month, basically, unless there's like a serious security thing or something. 00:32:58.932 --> 00:33:01.552 So yeah, so in that domain, it's worked quite nicely. 00:33:01.772 --> 00:33:08.332 So the thing, what you're saying that I do like is I like the idea of a implicitly 00:33:08.332 --> 00:33:12.292 defined home assistant setup, because that feels a little more appliance-like, 00:33:12.612 --> 00:33:14.572 especially at the level of dependency that I have. 00:33:14.832 --> 00:33:19.172 Because what I have now is a bunch of Docker containers that are being orchestrated 00:33:19.172 --> 00:33:22.852 by the home assistant supervisor container. And while it's been fine, 00:33:23.252 --> 00:33:26.912 it's always been sort of like it seems like a potential area of issues. 00:33:27.606 --> 00:33:31.306 But they actually do a great job in practice. But I like the idea of a defined 00:33:31.306 --> 00:33:33.026 home assistant setup that's easy to replicate. 00:33:33.546 --> 00:33:36.766 Then, you know, that would be really nice for, and I wish I would, 00:33:36.866 --> 00:33:39.786 now thinking about this, I wish I would have done this years ago because I need 00:33:39.786 --> 00:33:42.206 to redo home assistant at the studio probably next year. 00:33:42.366 --> 00:33:45.066 I have home assistant that I'm going to redo for Hadiyah's office. 00:33:45.306 --> 00:33:46.906 I'm going to do a second implementation there. 00:33:47.286 --> 00:33:50.246 It'd be really nice to have all of that actually set and easy to replicate. 00:33:50.686 --> 00:33:55.386 You know, really this came up because you were detailing to us privately some 00:33:55.386 --> 00:33:56.446 of your struggles, right? 00:33:56.446 --> 00:33:59.646 and I mean at first I was just laughing because you wanted robust stuff and 00:33:59.646 --> 00:34:04.286 you mentioned Z-Wave JS but more realistically you mentioned that you had to 00:34:04.286 --> 00:34:09.366 install an SSH add-on to troubleshoot that's so true because. 00:34:09.366 --> 00:34:10.526 Everything's containers I. 00:34:10.526 --> 00:34:14.666 Was just laughing in Nixos but no realistically there's a lot of trade-offs 00:34:14.666 --> 00:34:17.346 and I don't know that this would really be right for you but I'd be curious 00:34:17.346 --> 00:34:20.906 you could try it incrementally that's what I'd be curious to see I think for 00:34:20.906 --> 00:34:25.786 me for minimal setups things where you can kind of adapt how you build it to 00:34:25.786 --> 00:34:27.726 the limitations and the strengths, 00:34:27.746 --> 00:34:31.426 that's a different domain than porting an existing maxed out, 00:34:32.846 --> 00:34:34.626 supes tech van lifestyle. 00:34:34.806 --> 00:34:36.806 Hundreds of devices. Yeah, totally. 00:34:37.326 --> 00:34:42.666 Chris, do you worry about moving away from the officially supported OS way of 00:34:42.666 --> 00:34:45.746 running Home Assistant and doing a build your own? 00:34:45.806 --> 00:34:50.706 Do you worry about this I don't know, stability or supportedness of that? 00:34:51.026 --> 00:34:54.046 No, I mean if you run it if you run Home Assistant OS in a VM, 00:34:54.206 --> 00:34:55.686 that would be a supported configuration. 00:34:56.086 --> 00:35:01.526 If you go out in the crazy way, the crazy, scary way that Wes is talking about, 00:35:01.706 --> 00:35:03.186 that wouldn't necessarily be supported. 00:35:04.244 --> 00:35:05.704 But that doesn't concern me either, I suppose. 00:35:06.164 --> 00:35:08.784 Yeah, right. That's another part of the trade-off is I'm kind of giving up that 00:35:08.784 --> 00:35:13.984 for the ability to do it the Nix way, the benefits that may or may not have for you. 00:35:15.344 --> 00:35:19.464 And it's easier for me to hack on it a little bit that way just because now I'm a Nix guy. 00:35:19.644 --> 00:35:19.844 All right. 00:35:20.124 --> 00:35:23.304 But to your point, just really quick, is, right, you can also definitely, 00:35:24.104 --> 00:35:26.744 you know, if you did want, if you already were trying to deploy it on NixOS 00:35:26.744 --> 00:35:29.244 infrastructure, you could definitely run it in a VM or a container. 00:35:29.384 --> 00:35:30.124 Yeah, right. 00:35:30.524 --> 00:35:31.704 Just as you could on any base OS. 00:35:31.704 --> 00:35:34.324 Before we get off this, How do you say your name in the moment? 00:35:34.424 --> 00:35:36.984 Was it Dydriel? Dydriel? How do I say it? 00:35:37.284 --> 00:35:37.684 Dydriel. 00:35:37.984 --> 00:35:44.204 So you have the yellow, but you've popped a CM5 in your yellow. How's that working? 00:35:44.824 --> 00:35:48.644 I've been running it for over a year. It's been solid. The only issue I have 00:35:48.644 --> 00:35:49.924 is some smart plugs I have. 00:35:50.024 --> 00:35:56.064 The integration is glitchy and known to have to restart it, but that's just 00:35:56.064 --> 00:35:58.684 the integration itself. Nothing to do with the yellow itself. 00:35:59.444 --> 00:36:00.544 Do you want to out the vendor? 00:36:00.884 --> 00:36:02.184 Some Chinese knockoff. 00:36:02.184 --> 00:36:06.504 Oh, okay. All right, so you're telling me, you're telling me I pop off the top, 00:36:06.644 --> 00:36:12.064 I pop the top on the yellow, and I can just take the CM4 out, 00:36:12.144 --> 00:36:16.044 and I can in a new CM5, and I'm going to get a better, faster... 00:36:17.621 --> 00:36:20.681 Oh, but isn't the EMMC built into the... 00:36:21.181 --> 00:36:26.901 Yeah, you back up your Home Assistant first, and then swap it out, 00:36:27.041 --> 00:36:30.561 and then you reinstall Home Assistant, reload your config, and boom, 00:36:30.681 --> 00:36:31.381 you're back up and running. 00:36:31.561 --> 00:36:33.401 Have you had any problems with your Zigbee radio? 00:36:34.241 --> 00:36:39.741 I'm just getting into it. My wife doesn't let me buy fun toys like that. 00:36:40.401 --> 00:36:43.281 Go Z-Wave. That's my advice. Go Z-Wave. 00:36:43.601 --> 00:36:48.061 Okay, well, okay. So that also could be a time buyer. And did you notice a performance 00:36:48.061 --> 00:36:49.801 differential when you went CM5? 00:36:49.961 --> 00:36:52.961 Because that's my other concern is I go through the effort, I pay the money, 00:36:53.341 --> 00:36:58.821 I pop it in there, I reload the OS, and it's like a 10%, 20% improvement, which would be okay. 00:37:00.381 --> 00:37:05.101 I was actually running it out of a Docker container before on a quite powerful 00:37:05.101 --> 00:37:08.221 host that shouldn't have had any issues running it. 00:37:08.581 --> 00:37:13.181 And by going to a standalone box, I did notice a performance improvement just 00:37:13.181 --> 00:37:15.241 by going to standalone, letting it be dedicated. 00:37:16.121 --> 00:37:16.761 And not. 00:37:16.761 --> 00:37:21.641 Running my r stack next to it granted that stack is idle most of the time but still. 00:37:21.641 --> 00:37:26.201 Right when it does run it's stealing from home assistant yeah okay see i got 00:37:26.201 --> 00:37:30.001 too many choices here guys i really i think this is an area where i could really 00:37:30.001 --> 00:37:33.581 appreciate some experience and input they're like that's a great option if that 00:37:33.581 --> 00:37:38.561 cm5 buys me some time i think maybe what the what i should do there is uh, 00:37:40.701 --> 00:37:44.981 regardless of what I do, put a CM5 in that thing and deploy it somewhere else, you know? 00:37:45.101 --> 00:37:45.981 It sounds fun to try. 00:37:46.141 --> 00:37:48.821 Yeah, it's still got some good life in it, I think. Huh, all right. 00:37:48.941 --> 00:37:50.561 Well, please do boost in or go 00:37:50.561 --> 00:37:53.761 to linuxunplugged.com slash contact and let me know how you would do it. 00:37:53.881 --> 00:37:57.121 You know, maybe we get a poll going and the audience decides your hardware. 00:37:57.501 --> 00:37:57.661 Oh, God. 00:37:58.901 --> 00:37:59.681 I don't just say it. 00:37:59.821 --> 00:38:03.201 I want to nail it right. Ideally, it's something that lasts me another seven 00:38:03.201 --> 00:38:08.341 years, five years, you know, something I can put in that is a nice long-term. and. 00:38:08.341 --> 00:38:10.541 You didn't have something to recommend to other folks. 00:38:10.541 --> 00:38:13.761 The one really nice thing about going the prescribed home assistant 00:38:13.761 --> 00:38:16.761 os path vm or be it on physical hardware 00:38:16.761 --> 00:38:19.741 is the backup and restore is really top notch 00:38:19.741 --> 00:38:22.801 and if you have a nebikasa account they also store 00:38:22.801 --> 00:38:25.621 a version of the backup encrypted in cloud 00:38:25.621 --> 00:38:29.321 storage so you can now you can just restore from 00:38:29.321 --> 00:38:33.961 the cloud like it's a freaking iphone or android or something and restore it 00:38:33.961 --> 00:38:38.641 right onto the hardware and get right back to where you're at so the going from 00:38:38.641 --> 00:38:42.921 failure i got to switch to a new box to fully recovered scenario is really strong 00:38:42.921 --> 00:38:48.561 if you go the blessed route if you'll call it that which is one thing to consider, 00:38:49.842 --> 00:38:53.922 I think if you went the Nix route, like Wes is suggesting, by its very nature, 00:38:54.022 --> 00:38:58.002 it's so replicable that if you could just restore the data, you're probably going to be fine. 00:38:58.722 --> 00:39:02.382 Yeah, you know, copy over varlib NixWes, or Home Assistant, I mean. 00:39:02.862 --> 00:39:09.162 You know, I mean, is it crazy to run it on the router? Because I could also, I, yes. 00:39:09.542 --> 00:39:12.542 That was just super convenient for me when I was rebuilding my home lab. 00:39:12.682 --> 00:39:14.502 I'm not trying to recommend that per se. 00:39:14.742 --> 00:39:17.722 The router just wasn't doing anything else, so it was dedicated hardware I could use. 00:39:18.042 --> 00:39:21.442 Well, I could see some advantages. It is one less piece of hardware. 00:39:21.802 --> 00:39:24.422 And by router, it's mostly some NF tables rules, really. 00:39:24.522 --> 00:39:28.782 And something about, I just love the ludicrous idea of your critical home assistant 00:39:28.782 --> 00:39:31.962 system being on a box connected to the public internet. Like, 00:39:32.002 --> 00:39:33.802 it's just so dumb. I love it. 00:39:34.402 --> 00:39:38.002 I also, you know, there's so many meshes these days. Like, I don't have to have 00:39:38.002 --> 00:39:39.162 any ported ports and stuff. 00:39:39.322 --> 00:39:40.502 That's exactly how you would do it. 00:39:40.502 --> 00:39:40.682 Uh-huh. 00:39:44.345 --> 00:39:48.785 Unraid.net slash unplugged. Unleash your hardware with Unraid, 00:39:49.425 --> 00:39:53.925 a powerful, easy-to-use NAS operating system for those of you that want control, 00:39:54.085 --> 00:39:56.845 flexibility, efficiency, and you want to just take advantage of some of the 00:39:56.845 --> 00:39:59.805 apps we talk about with what you have in the closet right now. 00:40:00.385 --> 00:40:04.885 Build your ultimate rig or take advantage of that laptop sitting in the corner. 00:40:05.065 --> 00:40:07.365 You can really unleash the hardware that you have right now. 00:40:07.505 --> 00:40:09.125 And Unraid is cooking, my friends. 00:40:09.785 --> 00:40:16.865 The new RC is out for version 7.20. 5,000 different Unraid members help test the RC. 00:40:17.505 --> 00:40:21.465 That's awesome. They have lots of nice fixes, polish across storage, 00:40:21.725 --> 00:40:25.485 VMs, the web GUI, and the stable is just around the corner. 00:40:25.985 --> 00:40:28.145 Unraid goes from win to win. And 00:40:28.145 --> 00:40:32.425 recently, they have been laser-focused on making that web UI even better. 00:40:32.705 --> 00:40:37.325 Their community app store is bonkers. You get access to support, to the community, 00:40:37.565 --> 00:40:41.445 to all of those apps, and the continuous improvements of Unraid built on top 00:40:41.445 --> 00:40:45.485 of a modern Linux kernel, which means you get the best in virtualization, 00:40:45.705 --> 00:40:48.925 the best in containers, and the best in file systems. 00:40:49.105 --> 00:40:52.445 So check out Unraid and support the show. You get a 30-day free trial, 00:40:52.465 --> 00:40:57.985 which lets you test out Unraid, no credit card required, when you go to unraid.net slash unplugged. 00:40:58.045 --> 00:41:00.265 It's pretty powerful, and it just keeps getting better. 00:41:00.405 --> 00:41:04.185 And they just recently crossed the 20-year mark. And it feels like they've got 00:41:04.185 --> 00:41:06.345 all the steam and energy from, like, a startup. 00:41:06.585 --> 00:41:09.105 It's really pretty impressive. Check it out. Support the show. 00:41:09.365 --> 00:41:11.545 Unraid.net slash unplugged. 00:41:14.108 --> 00:41:18.408 Well, we'd like to do a shout-out to new member Giovanni, who joined as a core 00:41:18.408 --> 00:41:20.428 contributor. Thank you, Giovanni. 00:41:21.848 --> 00:41:27.168 Thank you. Hope you're enjoying. I will say, last week's bootleg had some extra 00:41:27.168 --> 00:41:28.768 road trip clips and stuff like that. 00:41:28.988 --> 00:41:33.268 Great bootleg if you are just signing up or you haven't grabbed them yet. 00:41:33.648 --> 00:41:36.788 Go do it. And thank you for becoming a core contributor. 00:41:37.188 --> 00:41:41.268 Appreciate that very much. And gentlemen, we do have some boosts. 00:41:42.048 --> 00:41:49.348 And Derevishan Dingus is our baller booster this week with 72,222 sets. 00:41:52.915 --> 00:41:57.255 Oh, that's a nice one. Thank you, derivation. So sorry I missed sending my config. 00:41:57.875 --> 00:42:01.755 I've been behind on shows, but I had to boost in my vote for more of this content. 00:42:01.975 --> 00:42:05.015 I really enjoyed this episode and would love to participate in a second round. 00:42:05.275 --> 00:42:08.355 That said, guys, for the love of God, please give Home Manager a try. 00:42:08.595 --> 00:42:13.355 I've replaced the vast majority of my individual .files with Nix modules because of Home Manager. 00:42:13.675 --> 00:42:18.135 It's so nice to have everything in one spot and in one format. Highly recommend. 00:42:18.655 --> 00:42:19.795 We knew this day would come. 00:42:20.115 --> 00:42:22.575 We've been resisting this for almost as long as we resisted Nix. 00:42:24.155 --> 00:42:31.055 almost but uh i i just you know my my hesitation is i just feel like i'm really 00:42:31.055 --> 00:42:34.615 going all in at that point but i think i already have all right we got to try 00:42:34.615 --> 00:42:38.995 it we got to try it i need to know is there like recommended well especially. 00:42:38.995 --> 00:42:40.675 Because we can clean up your config. 00:42:40.675 --> 00:42:43.415 My goodness i know every time i'm 00:42:43.415 --> 00:42:46.135 working and i'm vibing on hypervibe well not 00:42:46.135 --> 00:42:49.295 every time but very frequently it's like okay now I 00:42:49.295 --> 00:42:52.395 can do this with an activation script but if we 00:42:52.395 --> 00:42:55.155 used home manager let's tell it to tell me 00:42:55.155 --> 00:42:59.075 that all the time I'm sure it is uh he goes on I've been using hyperland and 00:42:59.075 --> 00:43:03.915 nix os for years at this point and in my opinion it is a match made in heaven 00:43:03.915 --> 00:43:07.615 hyperland has really come a long way since the early days and it has first class 00:43:07.615 --> 00:43:11.255 nix os support the whole time I've been using it it really is cool to see some 00:43:11.255 --> 00:43:14.795 people appreciating all the work being done over there it really does deserve the attention. 00:43:15.035 --> 00:43:17.695 I feel like it made my computer fun and exciting again. 00:43:18.555 --> 00:43:26.175 I'll plus one then. It's just enough desktop. It really has been pretty great and the combination of, 00:43:27.595 --> 00:43:33.555 just the way I can configure it simply and the instant reloads and the way it does tile. 00:43:33.755 --> 00:43:37.315 It just tiles very intelligently plus you can do support for some floating windows 00:43:37.315 --> 00:43:39.115 if you want. I really like it. 00:43:39.735 --> 00:43:42.395 That's all I have to say about that. And I do think it is a match made in heaven 00:43:42.395 --> 00:43:45.815 i agree and thank you for that boost appreciate it. 00:43:45.815 --> 00:43:49.915 Show mascot the golden dragon boosts in with a row of ducks, 00:43:52.838 --> 00:43:58.398 Boosting in 636, love the episode, great road talk, and interview with John. 00:43:58.658 --> 00:44:02.118 Oh, thank you. We had a lot of fun. And it was really great of John to be able 00:44:02.118 --> 00:44:04.618 to join us live like that. We were really down to the wire. 00:44:04.798 --> 00:44:06.738 And we pushed through some technical difficulties. 00:44:07.538 --> 00:44:12.878 Pabby boosted in a row of ducks. Plus one for the config confessions. 00:44:13.218 --> 00:44:15.458 Have to get around to cleaning up my next config sometime. 00:44:15.998 --> 00:44:18.338 All right. I think that's a plus two so far for this. 00:44:18.598 --> 00:44:19.898 I don't know. Three or four at least. 00:44:19.998 --> 00:44:23.458 I think we're getting in the green light category, boys. that's 00:44:23.458 --> 00:44:26.798 exciting that's really cool i wasn't sure at first it was sort of a slow start 00:44:26.798 --> 00:44:30.738 but now we're hearing it we're hearing it um if you disagree now's the time 00:44:30.738 --> 00:44:36.978 you can let us know but uh things are cooking things are cooking all right kiwi 00:44:36.978 --> 00:44:41.158 bitcoin guide comes in with 5 432 sats, 00:44:42.458 --> 00:44:46.818 time traveler boost i'm going back over episodes about file systems who knew 00:44:46.818 --> 00:44:52.058 that you could customize the file system in your os wow i know things we take for granted now no. 00:44:52.058 --> 00:44:55.078 Kidding right If you're just coming from more traditional devices. 00:44:55.458 --> 00:44:59.058 Yeah, especially Windows and macOS. Like, not a lot of options there. 00:44:59.338 --> 00:45:02.238 No, that does mean you kind of, you know, sometimes have to choose and debate 00:45:02.238 --> 00:45:04.818 why to choose and which, but that's part of the fun. 00:45:05.318 --> 00:45:08.118 That's true. Could you explain the difference between corporate distros like 00:45:08.118 --> 00:45:12.238 Ubuntu and Pop! OS and community distros? Pros, cons, trade-offs, that kind of thing. 00:45:13.197 --> 00:45:14.637 Almost an episode topic there. 00:45:14.637 --> 00:45:16.837 Oh, yeah. It's a big thread to pull. 00:45:17.177 --> 00:45:21.997 Well, the corporate distros generally have paid staff to maintain and develop 00:45:21.997 --> 00:45:26.817 them and work on certain pain points, but they also have an overall corporate 00:45:26.817 --> 00:45:29.217 mission that they're trying to deliver via that desktop. 00:45:29.457 --> 00:45:32.357 Now, if you agree with that and align with that, that's probably just fine. 00:45:32.897 --> 00:45:35.977 Community distributions can be a little bit more chaotic in their structure 00:45:35.977 --> 00:45:41.017 and their organization, but don't necessarily have any particular enterprise 00:45:41.017 --> 00:45:43.497 end goal or KPI that they must meet, 00:45:44.257 --> 00:45:48.097 or a certain thing of value that they must return to the organization making it. 00:45:48.197 --> 00:45:52.297 So they can be useful in that way. And I think my experience has been over the 00:45:52.297 --> 00:45:56.857 years, just have naturally gravitated towards the community maintained distributions 00:45:56.857 --> 00:46:01.077 overall, not for any particular criticism against Ubuntu or PopOS. 00:46:01.217 --> 00:46:02.257 I think they're both really fantastic. 00:46:02.517 --> 00:46:05.957 And I think the people in charge of them really have their best interest in 00:46:05.957 --> 00:46:09.097 mind. But it just seems to be where I've naturally gravitated to over the years. 00:46:09.657 --> 00:46:12.397 Yeah, and you know, kind of depends on what you're doing if you if you do 00:46:12.397 --> 00:46:15.297 align well with what you know the corporate distros in 00:46:15.297 --> 00:46:18.317 particular are trying to do if you could be a potential customer even 00:46:18.317 --> 00:46:21.017 or you want support eventually things like that then you know this 00:46:21.017 --> 00:46:24.497 can be really nice yeah and right they do have an ability to sort of set the 00:46:24.497 --> 00:46:27.957 bar or you know pay people to work on certain things in certain areas so if 00:46:27.957 --> 00:46:30.897 those are areas that are important to you that might be something that you appreciate 00:46:30.897 --> 00:46:36.737 but the downside can be that you you know if you diverge from that they don't 00:46:36.737 --> 00:46:39.497 always necessarily bend over backwards to support. 00:46:39.657 --> 00:46:42.477 I mean, it's still open source often, right? And so there is a lot of community 00:46:42.477 --> 00:46:44.377 involvement around corporate distros as well. 00:46:44.737 --> 00:46:47.917 But you just kind of get a different experience in, you know, 00:46:48.057 --> 00:46:51.437 the support use cases and the diversity of what people are doing with some of the community ones. 00:46:52.263 --> 00:46:58.803 Maybe the best place to see this in action is the delta between Debian and Ubuntu 00:46:58.803 --> 00:47:04.743 and Fedora and CentOS Stream and RHEL, right, where you can really see the community side. 00:47:04.883 --> 00:47:07.843 Even though you could argue that Red Hat still is somewhat involved in Fedora, 00:47:08.003 --> 00:47:09.043 it's very much community-led. 00:47:09.223 --> 00:47:13.363 And you see, like, the differences is they have ButterFS on Workstation now 00:47:13.363 --> 00:47:15.503 for multiple releases. That's still not in RHEL. 00:47:15.723 --> 00:47:19.383 And so they can experiment a bit more in some cases as well. 00:47:19.583 --> 00:47:24.403 Great question. i feel like i could talk about that for an hour love it if you 00:47:24.403 --> 00:47:26.423 have any other questions like that kiwi please do send them in. 00:47:26.423 --> 00:47:33.703 Chris b boosted with 5 000 cents if you're reading this my very first crypto 00:47:33.703 --> 00:47:40.103 transaction was successful sent using self-hosted bitcoin lnt and boost cli 00:47:40.103 --> 00:47:46.203 keep up the great work what that's awesome very very impressive oh that is a lot as. 00:47:46.203 --> 00:47:47.083 A first uh. 00:47:50.250 --> 00:47:53.270 Wow, that is crazy as a first. 00:47:53.410 --> 00:47:54.750 That's zero to like 300. 00:47:55.310 --> 00:48:00.970 Crispy, very, very impressive. And even Boost CLI. It's been ages since we've had a Boost CLI boost. 00:48:01.470 --> 00:48:04.930 You'll find as you get into Bitcoin, some really don't like the association 00:48:04.930 --> 00:48:07.970 of crypto and Bitcoin. There's Bitcoin and then there's everything else. 00:48:08.910 --> 00:48:12.110 But we're here, we're much more friendly folk. And we really, 00:48:12.390 --> 00:48:15.450 I'm impressed. Well done. Well freaking done. 00:48:16.490 --> 00:48:18.670 That's eagle for you, sir. Eagle for you. 00:48:18.670 --> 00:48:24.470 Well Kaspilin boosted in three boosts for a total of 6,300 sats, 00:48:25.410 --> 00:48:29.690 now this is on episode 329 flat 00:48:29.690 --> 00:48:38.270 network truthers funny nowadays kernel 5.5 pi's on 32-bit mangero bivaldi 12 00:48:38.270 --> 00:48:42.870 cores all amazing i miss those times those deep dives i was looking for info 00:48:42.870 --> 00:48:45.970 about nebula so thanks for the work Thank you. 00:48:46.130 --> 00:48:46.630 I think, right? 00:48:46.910 --> 00:48:47.130 Yeah. 00:48:47.310 --> 00:48:51.550 Thank you for the support. And he's saying we should do more deep dives. And I agree on that. 00:48:51.770 --> 00:48:52.270 Just a wee bit. 00:48:52.430 --> 00:48:57.950 A wee bit of a deep dive. You know, or an in-depth look could be that too. A wee bit of a deep dive. 00:49:02.150 --> 00:49:02.510 Yeah. 00:49:02.690 --> 00:49:06.630 If you have deep dive, I don't know, curiosities, you send them right along 00:49:06.630 --> 00:49:07.910 and we'll see what we can do. 00:49:08.270 --> 00:49:10.190 I love nerding out on kernel releases. 00:49:10.750 --> 00:49:14.510 I do kind of like, you know, the callbacks. there have been various different 00:49:14.510 --> 00:49:18.570 eras too right if you've just been following the desktop linux world and yeah 00:49:18.570 --> 00:49:23.150 from kernel five five yeah yeah the different versions of the pi the browser 00:49:23.150 --> 00:49:25.210 war there's just been a lot there's a lot. 00:49:25.210 --> 00:49:28.690 And there still is wes there still is and some. 00:49:28.690 --> 00:49:30.490 Some of us haven't processed that sometimes. 00:49:30.490 --> 00:49:36.110 It's too much wes sometimes there's too much ed broughton's here with 12 345 00:49:36.110 --> 00:49:37.750 sets that's one two three four five, 00:49:42.085 --> 00:49:44.545 Oh, another request for a wee bit of a deep dive. 00:49:48.385 --> 00:49:52.185 I'd like to see a deep dive on AlbiHub, a peek under the hood and some explanations 00:49:52.185 --> 00:49:55.025 of what the user-friendly UI is actually hiding from a node operator. 00:49:55.245 --> 00:49:59.165 Maybe include some discussion on ongoing channels and the why behind the limited 00:49:59.165 --> 00:50:01.305 number of LSPs offered through AlbiHub UI. 00:50:01.505 --> 00:50:05.025 How does AlbiHub impact decentralization of the network? And discussions of 00:50:05.025 --> 00:50:07.345 cloud versus self-hosted AlbiHub instances. 00:50:07.565 --> 00:50:07.805 Great. 00:50:08.045 --> 00:50:09.365 Ed, that's a pretty solid suggestion. 00:50:09.545 --> 00:50:10.165 True, yeah. 00:50:10.165 --> 00:50:12.385 You and I should do a Twib special or something on that. 00:50:12.385 --> 00:50:12.765 That sounds fun. 00:50:13.525 --> 00:50:17.505 Because I think that's probably where that would, This Week in Bitcoin is probably the place for that. 00:50:18.025 --> 00:50:21.885 And that is a great series of questions. And there's a lot of great answers there. 00:50:22.825 --> 00:50:25.025 Very, very, very excited about the LB Hub project. 00:50:26.145 --> 00:50:28.745 But there is good questions. Like, why is there only so many LSPs in there? 00:50:29.025 --> 00:50:29.925 Why don't they have more? 00:50:30.485 --> 00:50:33.445 Those are great questions, Ed. And Wes and I will have a conversation about 00:50:33.445 --> 00:50:35.625 maybe doing a special on This Week in Bitcoin for that. 00:50:36.145 --> 00:50:38.965 Thank you for the boost. Thank you, everybody, who boosted in. 00:50:38.965 --> 00:50:42.605 We had a good amount of you stream them sats as you listen to the show. 00:50:42.685 --> 00:50:44.245 That's always just super cool. We'd love to see that. 00:50:44.765 --> 00:50:49.405 Collectively, you stacked 40,807 sats. Hey, not bad. 00:50:49.665 --> 00:50:52.545 Thank you very much, sat streamers. When you combine that with our boosters, 00:50:52.725 --> 00:50:56.125 it's a humble amount. But after last week, that's kind of to be expected. 00:50:56.485 --> 00:51:00.765 We stacked a collective 147,250 sats. 00:51:02.781 --> 00:51:06.561 Thank you everyone who supports the show with a boost. When you boost this show, 00:51:06.721 --> 00:51:10.901 it's split amongst the hosts and our editor Drew, as well as the podcast app 00:51:10.901 --> 00:51:12.321 creator and the podcast index. 00:51:12.641 --> 00:51:16.021 It's all right there in the RSS feed for anyone to see. 00:51:16.301 --> 00:51:19.441 The contract itself is open source. That's really powerful. 00:51:19.641 --> 00:51:23.921 Plus, it gives the app creator a way to monetize that doesn't require creepy 00:51:23.921 --> 00:51:25.801 ads and tracking and stuff like that. 00:51:25.921 --> 00:51:28.961 It's really a powerful system. So you can start with Fountain FM. 00:51:29.141 --> 00:51:32.901 They make it really easy. You hear us talk about AlbiHub. That's a self-hosted 00:51:32.901 --> 00:51:36.161 system that you can load up yourself and then connect to lots of different applications. 00:51:36.601 --> 00:51:40.261 It's all really fun, too. It's a very educational experience. 00:51:40.481 --> 00:51:44.341 And when you get on the boost, it really feels like you're at the next level 00:51:44.341 --> 00:51:46.281 of interaction. You know, we're responding to you. 00:51:46.541 --> 00:51:48.661 You're responding to us. It's really great. 00:51:48.941 --> 00:51:52.821 And, of course, thank you to our members who said it and forget it. 00:51:55.775 --> 00:52:01.255 We better watch. Appreciate the members as well. All right, we got two picks 00:52:01.255 --> 00:52:02.815 for you before we get out of here. 00:52:02.995 --> 00:52:09.175 And the first one is a launcher that lets you launch your apps by casting spells. 00:52:09.895 --> 00:52:13.255 Yeah, I know how you like launchers. You're a big launcher guy. 00:52:13.415 --> 00:52:14.015 Big launch guy. 00:52:14.035 --> 00:52:17.215 Have you ever thought about using gestures to launch things? 00:52:17.415 --> 00:52:22.235 You know, I've played with this for a hot moment in like Firefox, I think, and stuff. 00:52:22.235 --> 00:52:29.175 like every now and then and it is really useful it sounds cheesy but if you 00:52:29.175 --> 00:52:33.035 already have your hand on the mouse why not just do a squiggly to launch something 00:52:33.035 --> 00:52:37.635 like your terminal really quick i don't think it takes away from having a keyboard-based 00:52:37.635 --> 00:52:40.175 launching system like keybinds or a launcher. 00:52:40.175 --> 00:52:41.015 No have them both. 00:52:41.015 --> 00:52:42.015 Have them both. 00:52:42.015 --> 00:52:45.715 No okay so then you might like hexacute uh 00:52:45.715 --> 00:52:48.955 it's a go app it's a gesture based launcher for 00:52:48.955 --> 00:52:54.095 wayland and um yeah you run on the commit you can run the command line uh ask 00:52:54.095 --> 00:52:59.275 it to learn then you draw your gesture three times and then after that um you're 00:52:59.275 --> 00:53:02.335 good to go so they kind of recommend you bind it to a key binding maybe or something 00:53:02.335 --> 00:53:05.915 to when you want to trigger it then you can draw whatever gesture you want. 00:53:05.915 --> 00:53:07.175 You're missing the best part, 00:53:08.550 --> 00:53:12.930 It has a magic wand sort of almost comp is style. 00:53:13.370 --> 00:53:18.170 Oh, yeah, right. So it turns your cursor into like a sparkly trailing magic wand. 00:53:18.430 --> 00:53:23.130 Yeah. So that's there. But I don't know. It also does like a lighting effect. 00:53:23.510 --> 00:53:25.290 It's pretty solid, actually. 00:53:25.530 --> 00:53:29.910 Yeah, the UI makes it seem quite charming. And so I kind of want to start using it just for that. 00:53:30.070 --> 00:53:32.190 Yeah. All right. We'll put a link to. 00:53:32.190 --> 00:53:34.690 This might actually especially work well if you were using on something like 00:53:34.690 --> 00:53:35.670 a touchscreen. I don't know. 00:53:36.810 --> 00:53:40.850 Oh, of course. hexacute gpl3 okay 00:53:40.850 --> 00:53:43.690 then let's talk about lenspect this got some 00:53:43.690 --> 00:53:46.850 attention this week because no one's really made a 00:53:46.850 --> 00:53:51.770 malware vulnerability scanner for linux in a while and lenspect is a modern 00:53:51.770 --> 00:53:56.490 gtk based application that does just that if this is something you're concerned 00:53:56.490 --> 00:54:01.850 about it is a lightweight security threat scanner powered by virus total virus 00:54:01.850 --> 00:54:06.510 total is a free service for individuals. They have a paid program for businesses. 00:54:06.830 --> 00:54:10.650 They kind of aggregate a bunch of different virus database information and then 00:54:10.650 --> 00:54:13.730 give applications one place to sort of look at aggregate information. 00:54:14.010 --> 00:54:16.430 This ties in. You go over there, create an account, get an API key. 00:54:16.550 --> 00:54:19.770 This ties in with that. And now you can scan individual files and folders on 00:54:19.770 --> 00:54:21.590 your system for all known malware. 00:54:21.790 --> 00:54:26.110 And because it's using the virus total backend, it's all currently up to date, 00:54:26.170 --> 00:54:29.050 which is nice, right? You don't even have to go like update your database. 00:54:29.710 --> 00:54:34.750 So Lenspect. And it's interesting to see this project right this is something 00:54:34.750 --> 00:54:39.190 that's been in the works for a little bit not a topic we cover a lot on the show, 00:54:40.387 --> 00:54:46.547 But the group decided to release this as GPO-3 and use the most modern GTK elements and designs they could. 00:54:47.267 --> 00:54:50.607 Yeah, you kind of like to see that. I mean, whether or not you are a particular 00:54:50.607 --> 00:54:55.587 in need or a user of this kind of thing, want to get the API key and all that. 00:54:56.467 --> 00:55:01.267 Some people do, and they want to do it on Linux. So if this enables that kind 00:55:01.267 --> 00:55:02.727 of workflow to happen, great. 00:55:03.127 --> 00:55:06.607 And they're distributing it as a flat pack, so it's pretty easy to get going. 00:55:06.927 --> 00:55:10.007 That scanning file logo kind of looks like the Bitwarden logo, 00:55:10.007 --> 00:55:12.527 but it's okay. Maybe it's not. 00:55:13.107 --> 00:55:15.807 And it looks like a really nice clean app and it gives you great information 00:55:15.807 --> 00:55:17.407 and then you can export that scan summary. 00:55:18.387 --> 00:55:21.067 Could be a way to, you know, maybe say you're doing compliance. 00:55:21.067 --> 00:55:23.527 I don't know. Or if you download something weird. 00:55:23.727 --> 00:55:27.567 This actually- Maybe we use it every time like after Brent's at the studio and 00:55:27.567 --> 00:55:28.527 then he's left the studio. 00:55:28.807 --> 00:55:30.667 That's big brain. That's big brain. 00:55:30.927 --> 00:55:32.167 Gotta get rid of the bug field, right? 00:55:33.087 --> 00:55:36.667 You know where this would be useful is if your kids are downloading like Minecraft 00:55:36.667 --> 00:55:40.027 mods or whatever crap it is, you could check this first, make sure there's nothing 00:55:40.027 --> 00:55:46.567 weird in there and it is GPL 3 at least for the front end stuff so it's not too risky to get into it. 00:55:46.567 --> 00:55:48.287 Yeah set up a gesture to launch it. 00:55:49.353 --> 00:55:52.253 Set up a gesture, sure. Then you'd use Hexacute to start Lenspect. 00:55:52.413 --> 00:55:52.593 Uh-huh. 00:55:52.713 --> 00:55:52.973 Mm-hmm. 00:55:54.493 --> 00:55:55.113 You're welcome. 00:55:55.433 --> 00:55:59.513 Now, can you give them a pro tip on, you know, maybe some advanced features 00:55:59.513 --> 00:56:01.753 that we have here in this here podcast that they might not know about? 00:56:01.873 --> 00:56:08.453 Oh, yes, we do. Well, first up is the magic of cloud chapters. Yeah. Dynamic. 00:56:08.853 --> 00:56:12.233 You just pull them down from the cloud, and suddenly you can jump around in 00:56:12.233 --> 00:56:14.933 the episode. Jump right to the content you want, skip the stuff you don't. 00:56:15.013 --> 00:56:18.053 We do have baked-in chapters if you don't have a podcasting 2.0 client. 00:56:18.213 --> 00:56:18.613 Yeah, that's right. 00:56:18.613 --> 00:56:23.233 But the nice thing about the cloud chapters is we can make corrections after the fact and stuff. 00:56:23.353 --> 00:56:26.613 And then your client automatically gets the update. There's that. So that's the chapters. 00:56:27.033 --> 00:56:28.273 But if you want more detail. 00:56:28.433 --> 00:56:28.953 I might, Wes. 00:56:29.073 --> 00:56:31.533 You might. We have transcripts. 00:56:31.693 --> 00:56:32.433 Oh, really? 00:56:32.673 --> 00:56:36.153 And a lot of clients these days, you can even play it in sync, 00:56:36.333 --> 00:56:40.633 follow along, look at transcript as you're listening to OSIAC in your ears. 00:56:40.733 --> 00:56:43.773 That's right. And for the clients that support it, we even have diarization 00:56:43.773 --> 00:56:47.233 because we are just that fancy. And some of those, like the new podcasting apps, 00:56:47.293 --> 00:56:48.573 they also support live streams. 00:56:48.693 --> 00:56:51.693 So you can join us every Sunday at our regular bat time. 00:56:55.753 --> 00:56:59.793 Yeah, join us on a Tuesday that's actually a Sunday. Sunday at 10 a.m. 00:56:59.913 --> 00:57:02.593 Pacific, 1 p.m. Eastern over at jblive.tv. 00:57:02.853 --> 00:57:05.593 Or if you've got an IceCast streamer, plug it into jblive.fm. 00:57:05.693 --> 00:57:08.893 And we're generally sending out video streams to things like YouTube and whatnot 00:57:08.893 --> 00:57:10.233 for the live stream as well. 00:57:10.733 --> 00:57:14.513 Links to everything we talked about today are at linuxunplugged.com. 00:57:15.173 --> 00:57:20.593 unpludged.com, sorry, slash 637. And of course, you can send us a contact or 00:57:20.593 --> 00:57:23.953 a boost to support the show, and our membership link is over there as well. 00:57:24.153 --> 00:57:28.473 Thank you so much for joining us on this week's episode of Your Unplugged Program. 00:57:28.713 --> 00:57:32.253 We'll see you back here next Tuesday, as in Sunday!