2021-SelfHosted-Transcripts / 55: Home Assistant Turns Amber _transcript.txt
willtheorangeguy's picture
add all 2021 transcripts
c844cb3 verified
[0.00 --> 6.10] Alex, I'm checking my email every single day right now because my Starlink kit is on its way.
[6.22 --> 7.70] This is going to be a game changer for me.
[8.52 --> 9.48] I think so, yeah.
[9.74 --> 14.88] You've unlocked a level, you've one-upped life if you've got Starlink.
[15.04 --> 19.64] You know what's funny is I started thinking, now I need to get serious about a home PC setup.
[20.06 --> 24.10] I'm always like, my work laptop will do or an iPad will do.
[24.10 --> 29.66] But if I'm going to have real internet at home now, I got to have a real PC to connect to that.
[30.00 --> 30.88] So how's it going to work?
[30.92 --> 33.90] Because my understanding of Starlink is reasonably limited.
[34.30 --> 35.86] I watched a couple of Jeff Geerling videos.
[36.12 --> 37.70] I think that's about as far as it goes.
[38.64 --> 44.80] Don't you have to tie it to a specific grid reference so that they have enough satellite bandwidth for you to talk to?
[44.88 --> 47.88] Like it won't work if you drive 50 miles west or something, right?
[47.88 --> 54.58] Yeah, I think it mostly turns out to be like a 30-mile area around your service address that you've put on your account is where it's functional.
[55.14 --> 56.10] I don't know yet.
[56.20 --> 59.46] This is something I'm going to play with, but it sounds like it's pretty straightforward.
[60.00 --> 63.40] In most cases, to just update your service address.
[63.70 --> 68.72] And then like it takes effect in like 15 minutes and then you can start setting up in your new location.
[69.10 --> 72.70] I imagine that's actually not as smooth as it's going to go.
[72.98 --> 75.96] Like I'll try to do it and be like too many users in this area.
[75.96 --> 85.74] Yeah, I recall I was watching a guy on YouTube who was an RVer and was proclaiming that he had hacked the Starlink algorithm to let him use it anywhere.
[86.18 --> 93.22] In actual fact, what he was doing was he was pre-staging his location in the Starlink app before he got there.
[93.28 --> 99.16] So the systems had time to catch up or if where he got to didn't have connection to update his service address.
[99.16 --> 103.38] I mean, I could see that because I generally know where I'm going to end up parking at, you know, before I go there.
[103.42 --> 104.86] So I could plug that in before I arrive.
[105.34 --> 112.48] The other tricky thing is, is I think the little dishy takes like 150 watts pretty much consistently once it's up and running.
[112.60 --> 114.32] That's a significant amount of power.
[114.38 --> 116.04] In fact, it's like running a whole PC.
[116.36 --> 117.16] It is pretty much, isn't it?
[117.16 --> 118.16] And they're not cheap either.
[118.16 --> 122.46] So there was the $99 deposit, which I felt was fair.
[122.70 --> 123.02] Okay.
[123.22 --> 123.78] All right, fine.
[124.42 --> 130.22] And then there's like a separate $485 fee to get the kit.
[130.30 --> 131.66] And the kit is everything you need.
[131.72 --> 136.02] It's like the router, Ethernet, the POE injector, the dish, all of it.
[136.72 --> 138.32] But every time I check, it just says pending.
[138.98 --> 141.20] So you're $600 in the hole for this thing then?
[141.56 --> 143.40] And then the monthly service, of course, as well.
[143.66 --> 144.86] Oh, what does that cost?
[144.86 --> 147.20] I think it's going to be in the $100 range.
[147.20 --> 154.58] When you don't have good, solid bandwidth, almost any price that you can conceivably afford to pay is worth it.
[155.02 --> 155.10] Yeah.
[155.28 --> 156.94] Slow internet is worse than no internet.
[157.58 --> 158.54] That's what they say.
[159.02 --> 161.44] And then once you get that good internet, head over to a Cloud Guru.
[161.56 --> 164.44] They are the leader in learning for the cloud, Linux, and other modern tech skills.
[165.38 --> 171.96] Thousands of hands-on labs, hundreds of certifications and courses, and free cloud sandboxes on their credit card, not yours.
[172.06 --> 173.62] Go to cloudguru.com.
[174.04 --> 175.80] Get certified, get hired, get learning.
[175.80 --> 180.92] So I can only imagine how having decent, low ping internet.
[181.04 --> 185.38] Do you have any sense of the Starlink kind of ping times yet?
[185.54 --> 188.02] I have done a little bit of meta-analysis of the reviews.
[188.44 --> 193.80] And also, to their credit, the Starlink folks kind of give you that information in the sign-up process when they're like,
[193.86 --> 194.62] hey, this is a beta.
[195.10 --> 196.66] It's going to go down sometime.
[196.66 --> 202.12] You're probably going to get ping somewhere in the 40 millisecond range is what they kind of warn you for.
[202.22 --> 204.82] And that's kind of what I've seen from the meta-analysis of the reviews.
[205.24 --> 207.76] I have seen some reviewers get it as low as 20.
[207.76 --> 217.24] Something in the 20 to 40 would be great because 40 is about the best case I'm ever going to get ever on LTE is about 40 milliseconds.
[217.24 --> 230.04] And I know from having done these shows with you now for a long time, an LTE connection is workable, but we end up stepping on each other quite often and makes life for our editor more difficult.
[230.22 --> 232.32] So lower the ping time for us, certainly the better.
[232.32 --> 249.38] And also, I would imagine, although we'll see, I'll get a sense of this, is it would hopefully, I know it drifts, but hopefully it drifts either less or more consistently than LTE, where LTE is kind of all over the board depending on all the other users that are in that area.
[250.04 --> 253.94] Are there any constraints around the amount of bandwidth you can consume?
[254.04 --> 255.70] Because with LTE, that's a big concern.
[256.02 --> 256.22] Right.
[256.28 --> 257.88] And as far as I know, there's no limits either.
[257.88 --> 262.38] I don't know if eventually when they go public, if they'll have tiered plans, but that's a huge deal.
[263.02 --> 265.10] No, no, no, no, no, no.
[265.16 --> 265.54] I know.
[265.80 --> 266.18] I know.
[267.22 --> 274.02] Even with my quote unquote unlimited LTE plans, I'm really kind of in the doghouse after 300 gigs.
[274.02 --> 276.96] And around 400 gigs, they're looking at what I'm doing.
[277.26 --> 280.52] And, you know, I get deprioritized and all that kind of stuff.
[280.52 --> 283.14] And that is like on the extremely high end.
[283.14 --> 288.20] Like these are elite rare plans where I can even get that far along before they start getting mad at me.
[288.44 --> 288.92] That's crazy.
[289.16 --> 299.94] Where I was staying last week at my mother-in-law's in rural Norfolk, the only decent internet that she can get is through 4G LTE from EE in the UK.
[299.94 --> 305.00] And she gets 200 gigabytes a month bandwidth for her home internet.
[305.00 --> 311.60] And for me, that was a real adjustment, you know, dealing with that ping time, dealing with that lack of bandwidth availability.
[312.02 --> 312.64] Welcome to my world.
[312.92 --> 315.58] I honestly don't know how you cope with it full time.
[315.92 --> 316.62] I know.
[316.92 --> 317.28] I know.
[317.32 --> 324.30] That's why I'm really excited about Starlink, even though there's the downside of putting more junk up in space, which is a serious problem.
[324.30 --> 330.86] And these may actually be visible from the ground and maybe, you know, there's, we're not going to be happy about that long term.
[331.18 --> 342.76] But it's so obvious that at least here in the States, we need a solution to this because my other options are duopoly cell providers or a monopoly cable provider.
[342.94 --> 345.36] Those are my options here.
[345.36 --> 356.54] And it just isn't, it is not long-term sustainable or tenable for something as important as our connectivity, which is how I organize, manage, and run my entire business.
[356.54 --> 359.46] And most of my personal life is all online now.
[359.48 --> 362.12] And that's true for probably nearly everyone listening to this show.
[362.24 --> 369.50] And so access to the internet just is so critical that I think it's kind of necessary that we have something like Starlink as an option.
[369.50 --> 381.08] And if they can get these prices down to below what I'm paying for these ridiculous LTE plans, I mean, that's going to make it more available to more people and, you know, eventually to folks like Alex's mom.
[381.72 --> 384.56] It's going to be a game changer for a lot of people.
[384.88 --> 389.70] There are remote mountain properties that you look at these days on Zillow or Rightmove or whatever.
[390.06 --> 394.24] And you think, oh, I'd love to, no, it's going to have two meg ADSL.
[394.50 --> 397.14] I can't, I just can't even consider it, you know?
[397.14 --> 415.46] Yeah, and I think ultimately, Alex, it's going to make something like my end dream, building some off-grid property a lot more feasible because all of the areas I've looked at in the Pacific Northwest that I could even begin to remotely afford that have water or something like that, they're all outside of cellular range.
[415.54 --> 416.48] There's nothing around.
[416.56 --> 417.74] There's no services.
[417.74 --> 428.30] And the idea that I could go out there with my solar-powered RV and set up a little Dishy and get a connection to the internet from space, it's just amazing.
[428.66 --> 429.18] I mean, it's huge.
[429.86 --> 430.18] Dishy.
[430.34 --> 431.50] What an adorable little name.
[432.10 --> 434.24] Did you see that Home Assistant had a release this week?
[434.44 --> 435.28] It seems like a big one.
[435.38 --> 441.92] You know, it's hard to tell from the outside, like, which ones are kind of just the minor updates and which ones are the big ones.
[441.92 --> 447.88] And the one that came out as we're recording is the October release that came out on October 6th.
[448.46 --> 450.12] There's a big thing in here, Alex.
[450.20 --> 454.48] They got official Tuya integration from the folks at Tuya.
[454.88 --> 462.60] The people that organize all the Tuya devices and run the Tuya infrastructure have now created an official integration for Home Assistant.
[463.34 --> 464.38] So here's the thing about this.
[464.50 --> 470.86] I mean, I think it's awesome that we're starting to get actual vendors looking at Home Assistant and going, yes, I want to support that.
[470.86 --> 478.96] But also, you know, we've got stuff like cloudfree.shop and mylocalbytes.com and that kind of thing.
[479.08 --> 486.80] And there's other things coming along with pre-Tasmodo Flash devices that this becomes less important to me.
[487.56 --> 490.78] Well, even more so because this is the cloud integration.
[491.38 --> 495.24] They worked with the cloud API team, not with, like, the firmware team.
[495.54 --> 498.26] And so this doesn't work for local integration.
[498.26 --> 500.16] This uses the cloud connectivity.
[500.54 --> 502.28] It looks like it's doing a really good job.
[502.36 --> 504.82] In fact, it's much better than before, much quicker, all of that.
[505.42 --> 506.40] It's what you'd want.
[506.46 --> 507.12] And it's official.
[507.58 --> 514.66] But it does require their cloud API, which means it requires an internet connection, which means it's a disqualifier for me.
[514.86 --> 517.50] Just like you said, I'd rather get a device I could control locally.
[517.84 --> 520.60] In fact, I'd rather get a device that's not on Wi-Fi.
[521.10 --> 522.46] What's your preferred poison these days?
[522.54 --> 524.38] Are you a Z-Wave or a Zigbee type of chat?
[524.38 --> 528.22] If you go by the number of devices I have, it'd be Z-Wave.
[528.44 --> 534.48] But if you go by where I plan to go to, it'd be Zigbee and Matter because that's going to be one and the same, I think, eventually.
[535.04 --> 542.24] Matter, I think, is really kind of exciting because if a vendor adopts the Matter protocol, then there is a local API.
[542.58 --> 545.20] If you use Matter, then you've got a local API.
[545.44 --> 547.40] And that, to me, is like, well, that's a no-brainer.
[547.40 --> 553.36] But right now, I invested pretty early in Z-Wave, and I've been very happy with my Z-Wave devices.
[553.50 --> 555.34] In fact, I'll talk about that in a little bit more.
[555.60 --> 562.10] But for me, Wi-Fi, it's just I like to be able to reboot my access points and maintain control of my devices.
[562.60 --> 565.76] I don't like putting that load on my Wi-Fi network.
[565.76 --> 571.50] And if it works with Z-Wave or Zigbee, I almost am guaranteed I can make it work somehow with Home Assistant.
[571.86 --> 572.56] That's very true.
[573.04 --> 579.36] The stuff I talked about in the last episode at my dad's house, the Zigbee buttons I put in here, he's been delighted with them.
[579.60 --> 583.10] The little IKEA Trad Free buttons, I think is what they're called.
[584.00 --> 585.04] They're working great.
[585.28 --> 588.80] So you get a plus one on Zigbee from me anyway.
[589.16 --> 591.56] I'm going to hold out with my Z-Wave devices for now.
[592.04 --> 594.74] And then when the Matter stuff settles, I may make a transition.
[594.74 --> 599.50] But Alex, with the release, they had a live stream, kind of like a release party with the developers.
[599.50 --> 602.46] And they brought on some of the developers from Tuya.
[602.76 --> 609.66] And they talked about some stats, the opt-in stats that people can get into and then send their information off anonymously.
[609.86 --> 615.38] They said that for the people that have opted in, they now show 90,000 active Home Assistant users.
[615.82 --> 621.80] That's just since April when they launched this statistics package and the people who have opted into it.
[621.80 --> 626.04] Also, the data shows that a lot of people have not updated since that April release.
[628.82 --> 630.36] Oh boy, that's a lot.
[630.64 --> 632.68] That's a lot of updates since they're doing a monthly now.
[633.12 --> 637.32] Also, their analytics show that 40% of Home Assistant users have a Chromecast.
[637.32 --> 641.52] 40% is a huge, huge number for that kind of thing.
[642.40 --> 644.54] HomeKit also shows as quite popular.
[644.80 --> 654.06] And the most popular hardware was the Raspberry Pi, followed closely by running Home Assistant in a VM like you do.
[654.58 --> 657.78] Now, do they take statistics on how many of those Raspberry Pi users are you?
[657.78 --> 661.72] Very fair, very fair.
[662.20 --> 668.54] All those stats are public at analytics.home-assistant.io, or we'll put a link in the show notes.
[669.04 --> 675.46] This is also the release for us Z-Wave users where it's time to migrate to Z-Wave.js.
[676.02 --> 680.66] As of this release, it now supports S2, which is the improved security model.
[681.16 --> 682.78] And it's short for security too.
[682.96 --> 683.54] Surprise, surprise.
[683.54 --> 687.44] Besides improved security, devices are also more reliable.
[687.68 --> 693.86] They provide greater battery life and less latency compared to the original security mode that was supported by Z-Wave.js.
[694.70 --> 699.24] The integration will now automatically pick the best and optimal security method available.
[699.42 --> 702.66] They have a whole new wizard for adding new devices, and it looks sharp.
[703.06 --> 711.00] Oh, and speaking of wizards, there is now a migration wizard to migrate you from your old Z-Wave setup to the new Z-Wave.js, which is what I was waiting for.
[711.00 --> 717.44] However, when I go in my home assistant, it actually is still asking me to migrate to OpenZW or whatever it was.
[717.50 --> 720.46] I don't know why, but I'm still getting a migration offer to OpenZW.
[720.62 --> 725.50] And I don't know if I'm supposed to install Z-Wave.js first or what.
[725.60 --> 726.98] Like, they don't give you any information on that.
[727.10 --> 731.92] But if your system isn't wonky like mine, they're saying go ahead and make the migration now.
[732.00 --> 733.16] It's been pretty refined.
[733.44 --> 736.12] It'll walk you through what it's going to do and what's going to change.
[736.12 --> 741.24] And then, Alex, the developers in the stream kind of doubled down, which made me feel good about using Z-Wave.
[741.36 --> 745.44] They said this Z-Wave.js integration is well-written.
[745.98 --> 750.00] It's well-built, and it is well-maintained, and they think it's good code.
[750.64 --> 751.48] And so it's solid.
[751.74 --> 752.90] It's a good...
[752.90 --> 754.26] In fact, they're going to go for...
[754.26 --> 754.68] They're thinking.
[755.20 --> 763.08] They haven't said they're going to do this, but they're thinking seriously about going for official Z-Wave certification from the Z-Wave group because they're so proud of how this has turned out.
[763.08 --> 765.82] Oh, really? That'd be a huge success.
[766.06 --> 776.22] I bought a Z-Wave smart door lock on some kind of sale on Black Friday, and it's been sat in a box ever since because I couldn't ever get it to pair.
[776.84 --> 779.64] So maybe now is the time I can...
[779.64 --> 783.44] With that new S2 security support that's in there, maybe I should give that another go.
[783.80 --> 790.34] Yeah, and it gives you a little more information, and it's a little more clear about when you should go hit the pair button on the device.
[790.34 --> 793.60] Like, all of that whole process is a little smoother now.
[793.96 --> 795.26] It looks with Z-Wave.js.
[795.50 --> 798.22] They did a little live demonstration of a migration on the stream.
[798.48 --> 802.08] I just remember it being frustrating as anything, you know, when I tried it.
[802.94 --> 805.14] Yeah, it feels a bit like a black box, doesn't it?
[805.38 --> 808.44] But no, I think they're doing good things.
[808.62 --> 814.00] So if you are a Z-Wave device user, which, you know, I probably have somewhere near...
[814.00 --> 815.82] I think I have like a dozen Z-Wave devices.
[815.82 --> 821.78] It's not like an unbelievable number that I can eventually migrate off of, but I'll be using them still for a while.
[822.52 --> 828.60] All right, I've got a low-key, genuinely awesome feature that's come to GitHub, I think, in the last two or three months.
[829.24 --> 831.50] Load up a GitHub repository right now.
[832.20 --> 833.10] You can do this live.
[833.68 --> 836.24] And open a repository.
[836.62 --> 837.58] You just need to be logged in.
[837.62 --> 838.46] That's the important thing.
[839.06 --> 844.14] When you have that page open, press full stop, the period key on your keyboard, and watch what happens.
[844.14 --> 847.00] Oh, that's pretty nice.
[847.18 --> 848.32] Oh, look at them.
[848.46 --> 849.06] Yeah, right?
[849.48 --> 851.20] Straight into VS Code Web.
[851.38 --> 854.04] Suddenly, Electron doesn't look so bad now, huh, does it?
[854.24 --> 856.98] It's that repository opened up in VS Code, isn't it?
[857.04 --> 857.24] Right?
[857.30 --> 857.84] It better be.
[857.90 --> 858.14] Yep.
[858.26 --> 859.42] Oh, that's slick.
[859.56 --> 860.64] Okay, impressive.
[860.98 --> 872.22] And then you open a file, you make an edit, you press save, and it then is because it's part of Git, the Git plugin in VS Code, you just commit it directly in there, and boom, you're done.
[872.54 --> 873.38] Oh my gosh.
[873.38 --> 886.44] If you're opening a third-party repository, though, and you make a change and you save it, it asks you then if you want to fork it, and then automatically helps you with the pull merge request model that GitHub has.
[886.84 --> 887.20] Wow.
[887.30 --> 889.92] It is so cool in the browser.
[890.42 --> 892.12] When did they sneak this in?
[892.24 --> 892.68] I don't know.
[892.76 --> 896.74] I mean, I first found it, someone on our Discord told me a couple of months ago about it, I think.
[896.84 --> 897.36] Of course.
[897.36 --> 901.02] But I've been using it a lot for my notes in the last few weeks, actually.
[901.10 --> 909.82] I've got a private repository on GitHub I use for notes, and I've actually just ended up using VS Code in the browser on github.com.
[909.96 --> 911.38] It's not very self-hosted, is it?
[911.44 --> 913.10] But it works very well.
[913.10 --> 918.32] And I want to mention our friends at A Cloud Guru have a course on the Linux kernel.
[918.44 --> 923.00] It's a standalone course, but it's also part of a learning path to prepare you for the LPIC 201 exam.
[923.70 --> 927.56] You'll learn how the Linux kernel provides an interface between hardware and software.
[927.78 --> 929.84] You'll compile a kernel from start to finish.
[930.20 --> 937.22] And of course, you'll cover kernel runtime management, troubleshooting, adding and removing modules, and modifying the modules on boot.
[937.22 --> 941.40] We'll have a link in our show notes where you can go to a Cloud Guru and search for the Linux kernel.
[943.70 --> 946.90] So we were just talking about ZigBee and Z-Wave and all that kind of stuff.
[947.04 --> 951.18] And I was really excited to see that the Home Assistant has a new hardware project out.
[951.54 --> 952.36] Yeah, and it's been funded.
[952.96 --> 958.06] The Home Assistant Amber, which is based around the Compute Module 4, with their own board.
[958.14 --> 959.36] It's got an SSD connector.
[959.52 --> 961.14] It has ZigBee built in.
[961.58 --> 963.22] In fact, the devs on the stream said,
[963.38 --> 964.68] no SD cards.
[964.82 --> 966.28] We hate SD cards.
[966.28 --> 969.90] So you can either use an SSD or it'll come with eMMC built into it.
[970.42 --> 973.04] They're going to ship it with a transparent case.
[973.66 --> 975.78] I think maybe in part for radio.
[976.12 --> 977.56] It's plastic for radio transparency.
[977.68 --> 980.24] And then they have a whole post on why they chose transparent.
[980.68 --> 983.38] Some models will come with a POE hat as well.
[984.34 --> 985.32] It's pretty nice looking.
[985.74 --> 989.42] Although I don't know if it's going to be as fast as the Home Assistant Blue.
[989.90 --> 992.32] Well, no, I mean, my only concern about this box,
[992.32 --> 996.40] and let me just preface everything I'm about to say with the fact,
[996.46 --> 1001.08] I think that these kind of projects from Home Assistant themselves are wonderful.
[1001.08 --> 1003.24] And I'm so happy to see that they're doing it.
[1003.70 --> 1011.62] My only concern is that putting the Compute Module 4 into a product at this stage in the Raspberry Pi 4's lifecycle
[1011.62 --> 1017.66] feels like we're getting towards the end of the Pi 4 cycle, maybe.
[1018.40 --> 1022.32] Are we going to be able to upgrade this to a CM5 one day?
[1022.42 --> 1023.10] Probably not.
[1023.24 --> 1027.06] Will there be a Home Assistant burnt Sienna instead or something?
[1027.14 --> 1027.52] I don't know.
[1027.60 --> 1029.46] But that's my only reservation.
[1029.64 --> 1030.78] Everything else looks great.
[1030.78 --> 1033.36] Yeah, perhaps that could be an issue.
[1033.78 --> 1036.90] I don't know if we know for sure if there will be a Compute Module 5.
[1037.10 --> 1039.32] This may be a, you know, once every few years.
[1039.64 --> 1040.62] That's a good point, Christopher.
[1041.04 --> 1048.30] The other thing that holds the Raspberry Pi 4 back right now is absolutely the I.O. situation.
[1048.68 --> 1052.74] And they solve that with EMMC or an SSD.
[1053.24 --> 1053.44] Yeah.
[1053.44 --> 1055.64] I mean, it's no x86 box, right?
[1055.64 --> 1062.88] Like, I've got jobs where I need more powerful systems, but I am doing more than ever with my Pi 4.
[1063.08 --> 1068.28] I mean, now it's doing MQTT and it's doing energy metric collection and graphing.
[1068.64 --> 1071.88] And it's still just chugging right along.
[1072.32 --> 1076.52] Like, it's just, oh, and also for a short period of time, I even ran the Wise Bridge on it.
[1076.78 --> 1077.18] Really?
[1077.18 --> 1078.60] It was still doing just, yeah.
[1079.00 --> 1080.54] Oh, that thing chomps the CPU.
[1080.90 --> 1082.34] Only with two camera feeds, let me be clear.
[1082.42 --> 1083.22] And I turned it off.
[1083.30 --> 1083.88] I did turn it off.
[1083.88 --> 1086.08] But Home Assist and everything was still working.
[1086.26 --> 1089.00] Like, it still has a little bit of oomph to spare.
[1089.80 --> 1099.56] And I could see the Compute 4 module being enough machine for most people until you get into more advanced logging and graphing and stuff like that.
[1099.74 --> 1102.84] So what does this mean for the blue then, moving forward?
[1103.10 --> 1106.38] Well, it seems like the blue is kind of going to phase out over time.
[1107.06 --> 1112.66] I think the words used were, we're going to take the lessons learned and we're applying that to the amber.
[1112.66 --> 1121.48] One thing about the blue that was noted by the developers is that it's a board that they took that already existed.
[1122.18 --> 1125.10] And then, you know, they flashed Home Assistant onto it.
[1125.20 --> 1129.72] But if you want Zigbee or Z-Wave or Matter Support, you got to add a dongle.
[1129.72 --> 1138.54] And it's not really flexible in that regard where this is a device that they kind of control the board that the compute module is going to sit in.
[1138.84 --> 1140.82] They can integrate things like Zigbee.
[1141.08 --> 1142.96] They can do things like PoE.
[1142.96 --> 1152.66] And it seems like when you look at also their hardware stats we talked about earlier and you see so many, so many users are using the Raspberry Pi.
[1153.04 --> 1162.94] It probably makes sense from like a software end user reliability stability standpoint to base your core product on that same platform if you can.
[1163.30 --> 1170.24] Because then improvements you make there are going to benefit everybody else also using the Raspberry Pi that isn't running on an amber.
[1170.34 --> 1171.06] They're just on a pi.
[1171.06 --> 1172.84] Yeah, I hadn't considered that angle.
[1173.00 --> 1173.88] That's an interesting one.
[1174.46 --> 1181.50] And Alex, if you'll allow me, there's one small update in this October Home Assistant release that I wanted to talk about.
[1182.10 --> 1184.34] It wasn't initially going to cover it, so I feel kind of embarrassed.
[1184.50 --> 1185.48] But it's icons.
[1185.74 --> 1189.14] They updated the material design icons to version 6.
[1189.50 --> 1191.30] They've added 400 new icons.
[1191.30 --> 1207.60] And if you haven't done this yet to your Home Assistant update, I know all this has been very Home Assistant specific, but I tell you what, it made me love my dashboard a little bit more when I went in there and just tweaked the icons for all the different entities.
[1207.60 --> 1210.42] So they all have unique individual icons that represent what they are.
[1210.42 --> 1223.04] And rumor has it, based on what the devs accidentally said on the live stream, they're going to include in the Lovelace wizard a new icon picker soon that lets you easily pick from these icons.
[1223.20 --> 1224.28] Oh, good.
[1224.34 --> 1233.70] Because the MDI website that you pick the icons from is the slowest damn web page to load on the entire freaking internet, I swear.
[1233.76 --> 1234.20] So slow.
[1234.42 --> 1234.78] So bad.
[1234.98 --> 1235.02] Yeah.
[1235.02 --> 1237.74] I'm glad they have it, but it's so slow.
[1238.38 --> 1238.52] Yeah.
[1238.58 --> 1239.88] So they're going to have an icon picker.
[1239.98 --> 1240.80] It'll be built in.
[1241.06 --> 1243.88] And these material design icons are in Home Assistant.
[1244.04 --> 1249.24] And there's so many for your different devices that just kind of give you a nice visual indicator what it do.
[1249.70 --> 1249.98] Mm-hmm.
[1250.58 --> 1251.84] You've got to know what it do.
[1253.66 --> 1255.70] Leno.com slash SSH.
[1255.76 --> 1257.82] Talk about people who know what they are doing.
[1258.00 --> 1260.66] They've been doing this since 2003.
[1260.66 --> 1262.88] One of the very first companies in cloud computing.
[1262.88 --> 1265.30] I mean, that's knowing what you're doing.
[1265.42 --> 1273.38] And 18 years later, Linode is the largest independent open cloud provider in the world with 11 different data centers around the world.
[1273.52 --> 1275.88] So it's linode.com slash SSH.
[1275.96 --> 1279.78] You go there to get $100 in 60-day credit on a new account.
[1280.16 --> 1281.76] And, of course, you support the show.
[1281.90 --> 1285.22] This show is made possible by you taking advantage of our sponsor offers.
[1285.40 --> 1286.88] We're an independent operation.
[1286.88 --> 1288.66] A couple of guys doing our thing here.
[1288.78 --> 1292.30] And you taking advantage of something great like this linode.com slash SSH.
[1292.30 --> 1294.28] Man, that's the circle of life for us.
[1294.58 --> 1297.04] Plus, you can go in there and just see how great it is.
[1297.26 --> 1299.96] It really is a fantastic service with great performance.
[1299.96 --> 1306.40] And they've really invested in the dashboard and the hardware and the networking and, well, the whole stack, really.
[1306.70 --> 1311.16] Like, if you want to switch over from Zoom to Jitsi, they've got a one-click deployment for that.
[1311.66 --> 1315.06] And it's like a great opportunity to take advantage of our $100 credit.
[1315.06 --> 1320.58] They really have the best-in-class experience because they've been focusing on making this great for the last 18 years.
[1320.88 --> 1322.54] Their mission has remained unchanged.
[1323.24 --> 1326.94] Making cloud computing accessible, affordable for all.
[1327.44 --> 1330.72] And once you get in, you'll see that they have things like S3-compatible object storage.
[1330.84 --> 1332.58] There's so much you can do with that.
[1332.96 --> 1335.88] They have bare metal servers if your application load requires that.
[1336.00 --> 1336.92] DDoS protection.
[1337.30 --> 1338.14] VLAN support.
[1338.44 --> 1339.98] A powerful DNS manager.
[1339.98 --> 1348.30] And if you like to do your infrastructure by code, they've got Terraform and Kubernetes support to help you, well, integrate with everything else you're doing.
[1348.46 --> 1353.10] And with pricing 30% to 50% cheaper, maybe it's a great opportunity to go multi-cloud.
[1353.36 --> 1354.76] Why get locked into a single vendor?
[1355.88 --> 1359.96] Linode can help you spread that out so you're not just dependent on one hyperscaler.
[1360.24 --> 1364.84] And as we've seen just the week that we're recording, sometimes, sometimes they go down.
[1365.12 --> 1369.16] And if you ever get stuck, Linode has the best customer support in the industry.
[1369.16 --> 1373.52] They really have amazing 24-7 customer support by phone, ticket, or social.
[1373.94 --> 1378.20] And then they back all that up with hundreds of guides and thousands of tutorials.
[1379.02 --> 1382.06] Linode is dedicated to offering the best in virtualized cloud computing.
[1382.30 --> 1385.00] If it runs on Linux, it runs on Linode.
[1385.52 --> 1388.14] Sign up today at linode.com slash SSH.
[1388.22 --> 1392.08] Get $100 in 60-day credit on your new account and you support the show.
[1392.96 --> 1395.52] Linode.com slash SSH.
[1395.52 --> 1399.26] Now, what were you doing earlier in the week?
[1399.38 --> 1402.44] You weren't, you know, messing about with BGP routes, were you?
[1403.76 --> 1406.74] No, no, I'm not pushing out changes to remove DNS entries.
[1407.38 --> 1411.62] Just, you know, of course, listeners are probably picking up on the fact that this is the week that Facebook went down.
[1411.88 --> 1414.30] And Alex and I are watching this with popcorn going,
[1414.30 --> 1418.68] oh, could you imagine what it's like to be on site right now where they can't even badge in,
[1418.78 --> 1421.24] let alone figure out why everything's down?
[1421.70 --> 1422.50] What a nightmare.
[1422.50 --> 1423.92] Or send each other an email.
[1424.16 --> 1424.66] That's the thing.
[1424.80 --> 1427.96] Like, you know, bob at facebook.com would no longer work, would it?
[1428.54 --> 1428.94] Man.
[1429.30 --> 1433.48] If I didn't know any better, I'd think somebody probably lost their job.
[1433.86 --> 1436.74] Well, I mean, this conspiracy theorist in me wonders,
[1437.08 --> 1443.98] it's all a little fishy that it happened on the exact same week as the testimony whistleblower thing.
[1444.80 --> 1449.36] You know, is it a deflection tactic or is it just genuinely a screw up?
[1449.36 --> 1452.50] I don't know, but you got to wonder sometimes.
[1453.12 --> 1454.46] I don't think it was a deflection tactic.
[1454.60 --> 1458.34] I mean, it was, if it was, that was a very significant self-inflicted wound.
[1459.00 --> 1459.56] Yeah, true.
[1459.92 --> 1463.04] I actually saw one of my neighbors sharing on Facebook today,
[1463.64 --> 1466.08] 10 Facebook alternatives for 2021.
[1466.58 --> 1467.88] I just thought that was so funny.
[1468.30 --> 1468.48] Yeah.
[1468.52 --> 1471.00] And Telegram saw a massive rush of new users.
[1471.14 --> 1476.44] You know, I'd buy an insider job before I'd buy an intentional screw up,
[1476.44 --> 1478.74] you know, like a rage quit kind of thing.
[1479.36 --> 1479.72] Yeah, maybe.
[1480.40 --> 1483.60] Maybe the Zuck didn't give somebody the smoked meats they were after.
[1484.58 --> 1487.24] I've been a little too distracted to really pay attention, though.
[1487.34 --> 1490.60] I got sucked into the rabbit hole of energy monitoring.
[1490.84 --> 1492.42] Right, yeah, because you're back home now,
[1492.48 --> 1495.40] so you've actually got some free time instead of just driving all day.
[1495.98 --> 1498.16] And Home Assistant, while I was on the roads,
[1498.20 --> 1499.76] I didn't have a chance to really look at it,
[1499.94 --> 1501.86] added energy monitoring support,
[1501.86 --> 1506.24] where you can actually, like, get some good stats and whatnot in Home Assistant
[1506.24 --> 1509.96] and identify batteries and utility sources
[1509.96 --> 1512.80] and even, like, you know, fuel consumption costs
[1512.80 --> 1514.56] if you want to monitor that.
[1515.58 --> 1517.50] So I thought, okay, I got to try this.
[1517.94 --> 1521.30] And I have a couple of Z-Wave smart plugs that do energy monitoring.
[1521.60 --> 1523.20] I've never really used that.
[1523.56 --> 1527.52] So that is sort of the route that I looked at this like,
[1527.58 --> 1531.82] well, why don't I try to see if I can get my existing smart plugs to work?
[1532.30 --> 1535.32] And for listeners that don't remember, I have two setups.
[1535.50 --> 1539.70] I have a home automation setup in my RV, which is pretty extensive.
[1540.10 --> 1542.84] And then I have, like, a mini version at the studio.
[1543.66 --> 1548.22] It's like a smaller instance of Home Assistant.
[1548.48 --> 1550.12] It runs on the Home Assistant Blue.
[1550.46 --> 1553.62] And in a way, it's often kind of like a good testing ground
[1553.62 --> 1554.90] because it's so much simpler.
[1555.10 --> 1557.40] There's just, there's less entities to go through
[1557.40 --> 1558.42] and all that kind of stuff.
[1558.52 --> 1561.18] And I noticed after the update,
[1561.86 --> 1563.98] to the Home Assistant Blues version of Home Assistant,
[1564.08 --> 1566.22] which comes out at the same time everybody else does,
[1567.12 --> 1569.50] that I just had energy monitoring.
[1569.66 --> 1572.48] Like my Belkin Wemo plugs that I happen to have
[1572.48 --> 1573.68] that I only use here in the studio
[1573.68 --> 1576.34] were just reporting their energy usage.
[1576.88 --> 1579.32] And Home Assistant had like a little diagram
[1579.32 --> 1580.92] of where power was going
[1580.92 --> 1582.94] and how much power had been used that day.
[1583.08 --> 1586.32] And I thought, wow, that looks great.
[1586.32 --> 1589.60] I'd love to have that at home where I actually care about my power
[1589.60 --> 1591.42] and all of that kind of stuff, I thought to myself.
[1591.84 --> 1594.22] So I go home and I don't have any of that.
[1595.04 --> 1597.74] My plugs are monitoring their draw.
[1598.08 --> 1600.26] They're seeing how many watts are being used.
[1600.76 --> 1602.30] But Home Assistant couldn't care less.
[1602.38 --> 1603.54] Like if I bring up the sensor,
[1603.66 --> 1606.10] yeah, it knows how many watts are being used.
[1606.52 --> 1608.68] But when I go to configure an energy device,
[1608.74 --> 1610.56] it's just whatever, bro.
[1610.80 --> 1612.36] There's no device that's giving you any stats.
[1612.36 --> 1615.74] For some reason, I've just got this picture of Home Assistant
[1615.74 --> 1620.36] being like this beavis and butthead style character
[1620.36 --> 1623.14] sat on a couch in the corner with a backwards baseball cap
[1623.14 --> 1624.52] and a cigarette in the other hand going,
[1624.94 --> 1626.94] whatever, bro, I don't care.
[1627.14 --> 1627.88] Yeah, you can't have that.
[1628.30 --> 1628.94] I don't care.
[1629.54 --> 1631.56] And so to me, it's like, okay, there's something wrong.
[1631.64 --> 1634.18] Obviously, these devices are like not giving Home Assistant
[1634.18 --> 1635.72] the information you need.
[1635.76 --> 1637.12] But when you go into the developer tools
[1637.12 --> 1639.10] and you look at the state attributes
[1639.10 --> 1640.36] and the states it's sending back,
[1640.36 --> 1644.64] it's clearly saying this is the amount of power being consumed.
[1644.96 --> 1648.42] It's in the watts format and it is this many watts.
[1648.56 --> 1650.98] Like it's easily readable by the human eye.
[1651.06 --> 1653.46] And I'm thinking to myself, what's going on here?
[1653.50 --> 1655.18] Why can't I see this power draw?
[1655.50 --> 1658.42] And I want to not only get an overview of my power draw,
[1658.48 --> 1660.66] but I want to start building automations that say,
[1660.78 --> 1663.62] hey, when two appliances, when these two smart plugs,
[1663.70 --> 1665.64] because I can just say these two together,
[1666.34 --> 1667.20] they're on one circuit.
[1667.20 --> 1667.80] I know that.
[1667.80 --> 1671.36] So when these two smart plugs both have a draw over 500 watts,
[1671.92 --> 1673.46] turn off the heater smart plug.
[1673.56 --> 1674.26] Always turn it off.
[1674.32 --> 1675.70] So that way the wife can turn on the toaster.
[1675.98 --> 1677.96] And when it starts drawing a thousand watts,
[1678.08 --> 1680.20] it turns off the heater that's drawing 800 watts.
[1680.52 --> 1682.56] And that's essentially what I want.
[1682.62 --> 1684.82] And if anybody has a blueprint or a good advice
[1684.82 --> 1686.48] on how to set that up, please let me know.
[1686.98 --> 1688.58] Ultimately, that's what I'm trying to get to.
[1688.70 --> 1689.74] I haven't gotten there yet.
[1689.74 --> 1693.92] But what I did do is I managed to get my damn energy monitored.
[1693.92 --> 1696.52] And it took quite a journey, I have to say,
[1696.58 --> 1701.14] because ultimately you have to get the data in the format
[1701.14 --> 1702.42] that Home Assistant wants.
[1702.84 --> 1706.96] So first, you got to have Home Assistant 2021.8 or newer,
[1707.20 --> 1711.52] and you need a smart plug or an energy monitoring device,
[1711.52 --> 1713.42] like one of those clamp devices or a Shelly
[1713.42 --> 1716.54] that reports in kilowatt hours.
[1716.54 --> 1720.14] All my plugs report in watts,
[1720.94 --> 1724.22] as in watts currently being consumed.
[1724.98 --> 1727.00] Home Assistant wants kilowatt hours,
[1727.22 --> 1729.42] and then it'll do all the math for you from there.
[1729.78 --> 1733.24] So what you have to do is you have to get an integration
[1733.24 --> 1735.54] called integration.
[1735.96 --> 1737.44] It's a math integration,
[1737.44 --> 1739.94] which will take the watts
[1739.94 --> 1742.34] and convert them into kilowatt hours for you,
[1742.34 --> 1744.84] and then produce a new sensor
[1744.84 --> 1748.06] that shows that energy information in kilowatt hours.
[1748.56 --> 1752.00] I have a configuration.yaml entry example in the show notes.
[1752.70 --> 1754.12] Then once you have that,
[1754.70 --> 1757.72] the new energy utilities that are built into Home Assistant
[1757.72 --> 1760.22] will see this device as something it can pull stats from
[1760.22 --> 1762.32] and will start giving you your usage.
[1762.80 --> 1764.98] So I have to go through for each one of my smart plugs,
[1765.24 --> 1766.70] and I have to do this.
[1766.76 --> 1770.56] I have to create this template sensor
[1770.56 --> 1775.12] that takes information from the state of my smart plug
[1775.12 --> 1778.16] and formats it in a way that Home Assistant wants.
[1778.20 --> 1779.56] And I have the examples in the show notes,
[1779.66 --> 1780.76] but I had to go deep
[1780.76 --> 1782.92] because I had to learn a little bit of how templating works.
[1783.00 --> 1786.14] I had to learn about creating new kinds of sensors.
[1787.32 --> 1789.06] It was really quite the journey.
[1789.06 --> 1792.82] I naively expected to just do the update,
[1792.92 --> 1793.74] get energy monitoring,
[1793.98 --> 1795.74] and see my smart plugs report in there.
[1796.14 --> 1797.70] Boy, was I wrong.
[1797.98 --> 1800.34] Sometimes we get a bit spoiled with Home Assistant,
[1800.34 --> 1800.74] don't we?
[1800.76 --> 1801.70] It picks up so much.
[1801.76 --> 1802.42] It does so much.
[1802.60 --> 1804.10] And then occasionally,
[1804.10 --> 1807.24] we actually have to break out some DaVinci code
[1807.24 --> 1808.80] to find out what we actually wanted.
[1809.24 --> 1810.44] I think this is one of those examples.
[1810.94 --> 1812.68] And I felt like there was so much out there
[1812.68 --> 1815.80] that didn't apply since the new energy monitoring
[1815.80 --> 1816.74] was introduced.
[1816.84 --> 1819.50] So like a lot of the help was old
[1819.50 --> 1821.06] and no longer relevant.
[1821.06 --> 1823.68] And because my smart plugs,
[1823.74 --> 1824.02] I guess,
[1824.06 --> 1824.74] aren't as common,
[1825.28 --> 1827.10] there's not as many people
[1827.10 --> 1828.70] that have solved this problem.
[1829.32 --> 1829.74] So I just,
[1830.20 --> 1830.42] yeah,
[1830.54 --> 1830.80] it was,
[1831.02 --> 1833.52] I felt like I was searching niche resources
[1833.52 --> 1835.04] and it took me a while
[1835.04 --> 1836.32] to even just try to figure out
[1836.32 --> 1837.40] the language I need
[1837.40 --> 1838.92] and figure out what the requirements were
[1838.92 --> 1839.56] of Home Assistant
[1839.56 --> 1840.30] and all of that.
[1840.30 --> 1841.52] That is a real problem
[1841.52 --> 1842.94] with projects like Home Assistant
[1842.94 --> 1843.96] that move so fast.
[1844.04 --> 1845.98] I see it a lot with Kubernetes at work as well
[1845.98 --> 1851.64] is that kind of Google entropy of stuff.
[1852.04 --> 1853.38] Like a post,
[1853.60 --> 1853.74] you know,
[1853.84 --> 1856.12] Google will think a year old post
[1856.12 --> 1859.10] isn't too old to surface as the top result
[1859.10 --> 1861.02] when in actual fact in Home Assistant
[1861.02 --> 1862.66] that may as well be 10 years ago.
[1863.24 --> 1863.64] Yeah,
[1863.74 --> 1864.72] that's exactly right.
[1865.34 --> 1865.96] And then,
[1866.10 --> 1866.40] you know,
[1866.46 --> 1866.68] Alex,
[1866.74 --> 1867.78] when I got it all kind of done,
[1868.30 --> 1870.60] I realized it's okay.
[1870.84 --> 1872.34] It's pretty basic at this point
[1872.34 --> 1873.38] because I don't have
[1873.38 --> 1874.94] all of my battery
[1874.94 --> 1876.30] and solar information in there.
[1876.60 --> 1878.56] It really wasn't worth the journey.
[1878.76 --> 1880.72] I actually like the dashboards
[1880.72 --> 1883.38] I created myself better.
[1883.80 --> 1885.34] And I'll have a few links in the show notes.
[1885.34 --> 1887.76] It involved setting up
[1887.76 --> 1889.18] a history stats integration
[1889.18 --> 1891.52] so I could collect historical information
[1891.52 --> 1892.58] about my power usage.
[1893.20 --> 1894.02] And then I used
[1894.02 --> 1895.50] a utility meter integration
[1895.50 --> 1897.86] and that let my
[1897.86 --> 1899.78] virtual energy monitors
[1899.78 --> 1900.32] I'd set up
[1900.32 --> 1901.38] that produce kilowatt hours
[1901.38 --> 1902.66] show up as a utility source.
[1902.78 --> 1902.90] Now,
[1903.58 --> 1905.66] that lets me do all kinds of things
[1905.66 --> 1907.48] like now I have a dashboard
[1907.48 --> 1909.38] that shows me
[1909.38 --> 1910.98] if today
[1910.98 --> 1913.86] my heaters are using more power
[1913.86 --> 1914.84] than they were,
[1914.84 --> 1915.04] say,
[1915.10 --> 1915.68] three days ago.
[1915.72 --> 1916.70] I have a three-day window
[1916.70 --> 1919.18] on my power usage of my heaters
[1919.18 --> 1921.06] and I can kind of tell
[1921.06 --> 1923.98] when I'm kind of using more power
[1923.98 --> 1925.70] and maybe I can make adjustments
[1925.70 --> 1926.54] based on that if I want.
[1926.58 --> 1927.38] I actually haven't decided
[1927.38 --> 1928.40] to take any action on that.
[1928.46 --> 1929.18] Right now I'm just collecting
[1929.18 --> 1929.72] the information
[1929.72 --> 1931.34] and collecting historical information.
[1932.20 --> 1933.72] And so when summer comes around,
[1933.78 --> 1934.36] I'll have a totally,
[1934.58 --> 1934.82] you know,
[1934.98 --> 1935.78] different set of data
[1935.78 --> 1936.76] and then when the whole year
[1936.76 --> 1937.20] is completed,
[1937.30 --> 1938.30] I think the information
[1938.30 --> 1939.38] is going to be pretty fascinating
[1939.38 --> 1941.10] and I'll probably be able
[1941.10 --> 1941.70] to overlay it
[1941.70 --> 1942.66] with temperature information
[1942.66 --> 1943.52] and all kinds of stuff.
[1943.88 --> 1945.22] So I brought together
[1945.22 --> 1947.78] the history stats integration
[1947.78 --> 1950.00] with the utility meter integration
[1950.00 --> 1951.10] and I have,
[1951.36 --> 1951.62] again,
[1951.74 --> 1953.46] an example of what that looks like
[1953.46 --> 1954.90] in your configuration.yaml
[1954.90 --> 1955.96] linked in the show notes.
[1956.44 --> 1957.30] So now what that's done
[1957.30 --> 1957.78] is it's created
[1957.78 --> 1958.82] these virtual sensors
[1958.82 --> 1960.16] that I've built dashboards around
[1960.16 --> 1960.98] in Home Assistant
[1960.98 --> 1962.60] that give me all this information
[1962.60 --> 1963.86] that I think
[1963.86 --> 1964.80] that's where they're going
[1964.80 --> 1966.32] with the built-in energy support,
[1966.48 --> 1967.78] but I like my version better
[1967.78 --> 1968.70] than I built myself.
[1969.40 --> 1970.22] It's not too bad, actually.
[1970.30 --> 1971.52] 17 lines of code
[1971.52 --> 1973.30] to do all that history stat stuff.
[1973.40 --> 1974.70] It's not unreasonable.
[1975.26 --> 1976.18] And it's very readable.
[1976.30 --> 1977.12] Like it all makes sense
[1977.12 --> 1977.64] when you read it.
[1977.66 --> 1978.52] You can see what I'm doing.
[1978.66 --> 1980.00] There's nothing tricky about it.
[1980.30 --> 1981.08] Yeah, that's very true.
[1981.24 --> 1981.42] Now,
[1981.58 --> 1982.68] something else we've talked about
[1982.68 --> 1983.58] on the show previously
[1983.58 --> 1985.48] is de-Google-ifying.
[1986.22 --> 1986.96] I'll be honest,
[1987.16 --> 1988.06] whilst I've been in England,
[1988.16 --> 1989.06] I haven't been paying
[1989.06 --> 1990.72] much attention to that.
[1990.80 --> 1991.94] I've just been getting on
[1991.94 --> 1993.04] with the business of traveling.
[1993.58 --> 1993.98] However,
[1994.44 --> 1996.30] you mentioned in LUP this week,
[1996.68 --> 1997.86] linuxonplugged.com
[1997.86 --> 1998.88] slash 426,
[1999.42 --> 2001.46] a tool called TubeSync.
[2001.68 --> 2001.98] Yeah,
[2002.04 --> 2002.68] think of TubeSync
[2002.68 --> 2004.20] as a PVR for YouTube.
[2004.42 --> 2006.22] You give it channels
[2006.22 --> 2006.94] and playlists,
[2007.06 --> 2007.88] or if you're familiar
[2007.88 --> 2008.56] with Sonar,
[2008.64 --> 2009.82] it's like Sonar for YouTube.
[2010.06 --> 2011.54] And then it goes out
[2011.54 --> 2012.84] and pulls down the videos
[2012.84 --> 2013.32] and it gives you
[2013.32 --> 2014.46] a dashboard to tell you
[2014.46 --> 2015.76] how many video sources
[2015.76 --> 2016.70] you're pulling from,
[2016.96 --> 2018.28] what's coming up next,
[2018.66 --> 2019.78] exactly like you might expect
[2019.78 --> 2021.00] from something like Sonar.
[2021.00 --> 2023.14] It's a pretty advanced UI
[2023.14 --> 2024.84] and there's a Docker Compose
[2024.84 --> 2026.04] that gets most of it
[2026.04 --> 2026.88] set up for you too, Alex,
[2026.94 --> 2028.14] including the Elasticsearch
[2028.14 --> 2028.86] stuff you might need.
[2029.16 --> 2030.24] The reason I brought this up
[2030.24 --> 2030.92] on this show
[2030.92 --> 2033.28] is this isn't Linux
[2033.28 --> 2034.30] unplugged extras,
[2034.60 --> 2036.72] but I actually found
[2036.72 --> 2037.44] something called
[2037.44 --> 2039.36] MediaCMS.io
[2039.36 --> 2040.94] and this is essentially
[2040.94 --> 2043.72] a YouTube front-end clone.
[2044.40 --> 2045.24] So what I was thinking
[2045.24 --> 2046.68] about doing was,
[2046.90 --> 2047.84] originally anyway,
[2047.84 --> 2049.38] I was going to use TubeSync
[2049.38 --> 2050.44] to download the videos
[2050.44 --> 2051.14] from YouTube
[2051.14 --> 2052.90] just as an archiving
[2052.90 --> 2055.16] type utility.
[2055.56 --> 2057.06] Bring them into Plex maybe
[2057.06 --> 2058.36] because there are some people
[2058.36 --> 2059.70] on the Plex forums
[2059.70 --> 2062.16] that have YouTube metadata agents
[2062.16 --> 2063.02] and that kind of thing.
[2063.48 --> 2065.28] But I think what I might end up doing
[2065.28 --> 2067.78] is using this MediaCMS.io
[2067.78 --> 2069.44] to self-host my own
[2069.44 --> 2071.82] kind of pseudo YouTube
[2071.82 --> 2073.18] instance thing.
[2073.34 --> 2074.02] Have you seen this?
[2074.48 --> 2075.96] Oh, this is neat, yes.
[2076.08 --> 2077.64] And it is obviously
[2077.64 --> 2079.42] inspired by the YouTube UI,
[2079.66 --> 2080.20] but good on them.
[2080.44 --> 2081.80] They've taken the best elements
[2081.80 --> 2082.26] in this
[2082.26 --> 2084.26] and I think it looks
[2084.26 --> 2084.78] really solid.
[2084.94 --> 2086.38] They got dark mode,
[2086.52 --> 2087.46] they got light mode
[2087.46 --> 2090.10] and it could really end up
[2090.10 --> 2091.94] making a perfect curated YouTube.
[2092.36 --> 2094.02] And while I could see it
[2094.02 --> 2094.54] being a lot of work
[2094.54 --> 2095.52] for what you want to do,
[2096.18 --> 2096.86] man, this could be
[2096.86 --> 2098.68] a slam dunk for parents.
[2099.20 --> 2100.70] This could be a great way.
[2101.10 --> 2102.26] You could take TubeSync
[2102.26 --> 2104.18] and pull in the approved channels
[2104.18 --> 2104.88] that you're comfortable
[2104.88 --> 2105.84] with your kids watching,
[2105.84 --> 2107.30] have TubeSync pull it
[2107.30 --> 2108.22] down to the file system
[2108.22 --> 2110.38] and then point MediaCMS
[2110.38 --> 2111.26] right at that
[2111.26 --> 2112.50] and it's a curated YouTube.
[2112.86 --> 2114.40] I wonder how they handle
[2114.40 --> 2115.72] video transcoding
[2115.72 --> 2116.48] because obviously YouTube
[2116.48 --> 2118.60] has a whole bunch of stuff
[2118.60 --> 2119.96] when you upload video to it,
[2119.96 --> 2120.78] it transcodes
[2120.78 --> 2121.94] to all the different formats
[2121.94 --> 2123.08] and then you just switch
[2123.08 --> 2124.18] on the fly
[2124.18 --> 2125.64] the quality that you're streaming.
[2125.90 --> 2128.40] Does this have any function for that?
[2128.46 --> 2129.96] I don't see any quality options
[2129.96 --> 2130.62] in the playback.
[2131.18 --> 2131.60] Oh yeah, no,
[2131.68 --> 2132.50] it's under the settings.
[2132.50 --> 2133.12] It's right there.
[2133.54 --> 2134.30] And it says it has
[2134.30 --> 2135.94] multiple transcoding profiles.
[2136.14 --> 2137.14] Same defaults, it says,
[2137.18 --> 2138.10] for multiple dimensions
[2138.10 --> 2141.52] from 240p up to 1080p.
[2142.22 --> 2143.04] Experimental support
[2143.04 --> 2144.04] for remote workers.
[2144.18 --> 2145.70] So I guess there's a bunch of stuff
[2145.70 --> 2146.68] we could figure out there.
[2147.00 --> 2148.50] This could be a fun project.
[2148.84 --> 2150.30] That's something to put on our list
[2150.30 --> 2151.86] after I get done solving energy.
[2153.12 --> 2154.44] Yeah, and then world hunger
[2154.44 --> 2155.42] and world peace
[2155.42 --> 2157.20] and COVID
[2157.20 --> 2158.38] is where you've got to solve
[2158.38 --> 2158.96] that one too.
[2159.06 --> 2160.76] And then we'll get on
[2160.76 --> 2161.92] redoingjb.com.
[2161.92 --> 2163.40] But we do have one thing
[2163.40 --> 2164.46] we can solve for people
[2164.46 --> 2166.36] if they are an iCloud
[2166.36 --> 2168.16] slash iPhone user
[2168.16 --> 2169.70] and you got your pictures up there.
[2169.80 --> 2170.72] You came across
[2170.72 --> 2172.04] a really handy tool
[2172.04 --> 2174.06] to help pull all of your
[2174.06 --> 2175.20] iCloud photos down
[2175.20 --> 2176.42] locally to your machine.
[2176.98 --> 2178.02] Yeah, we were talking about this.
[2178.08 --> 2178.48] Where was it?
[2178.52 --> 2180.16] In the Jupyter Broadcasting
[2180.16 --> 2181.60] Telegram chat, actually.
[2182.36 --> 2183.38] Someone was asking,
[2183.84 --> 2184.06] you know,
[2184.10 --> 2185.34] how do you back up your iPhone
[2185.34 --> 2187.22] pictures and stuff like that?
[2187.56 --> 2188.72] Because of the way that iOS
[2188.72 --> 2190.26] has very restrictive
[2190.26 --> 2191.56] background API,
[2191.96 --> 2192.38] kind of,
[2192.54 --> 2193.98] it kills anything
[2193.98 --> 2194.68] in the background
[2194.68 --> 2197.18] that's going to drain battery,
[2197.32 --> 2198.04] unlike Android
[2198.04 --> 2199.26] that's a lot more permissive.
[2199.60 --> 2201.16] It means you can't run
[2201.16 --> 2202.08] stuff like
[2202.08 --> 2203.50] Resilio Sync
[2203.50 --> 2204.46] or Sync thing
[2204.46 --> 2205.48] very effectively,
[2205.74 --> 2206.46] or there's another one
[2206.46 --> 2206.84] on Android
[2206.84 --> 2207.90] called Folder Sync.
[2207.90 --> 2209.46] And so,
[2209.92 --> 2211.54] this neat app
[2211.54 --> 2212.30] is actually called
[2212.30 --> 2214.34] Gimme-iPhotos,
[2214.42 --> 2215.64] which is kind of a funny name.
[2216.20 --> 2217.44] And this sidesteps
[2217.44 --> 2219.02] all of iOS's problems
[2219.02 --> 2221.26] with backgrounding APIs
[2221.26 --> 2222.08] and on-device,
[2222.42 --> 2222.76] you know,
[2223.36 --> 2224.10] image management
[2224.10 --> 2224.98] and stuff like that,
[2225.10 --> 2226.56] because it hooks
[2226.56 --> 2228.46] directly into iCloud.
[2229.02 --> 2229.74] The only caveat being
[2229.74 --> 2230.40] is you've got to be okay
[2230.40 --> 2231.20] with putting your photos
[2231.20 --> 2232.24] up in iCloud.
[2232.38 --> 2233.06] But I think what Alex
[2233.06 --> 2233.74] is driving at there,
[2233.80 --> 2233.98] it's like,
[2234.04 --> 2234.74] that's the only one
[2234.74 --> 2235.68] that's really going to work
[2235.68 --> 2236.66] reliably with the way
[2236.66 --> 2238.04] the iPhone backgrounding works.
[2238.36 --> 2239.02] If you want them
[2239.02 --> 2239.94] off the phone reliably,
[2240.24 --> 2240.68] automatically,
[2240.94 --> 2241.64] it's going to have to be
[2241.64 --> 2242.82] iCloud Photo on an iPhone.
[2243.18 --> 2244.42] So that's why this is so great.
[2244.70 --> 2245.76] And because it's Python,
[2246.34 --> 2247.62] you don't have to be on a Mac.
[2247.82 --> 2249.24] You could run it on a Linux box
[2249.24 --> 2250.26] or a Windows box too.
[2250.82 --> 2251.34] Yeah, I ran this
[2251.34 --> 2253.02] just on a normal Linux server.
[2253.14 --> 2254.42] I think I ran it out of a container
[2254.42 --> 2257.22] because that's just who I am.
[2257.82 --> 2259.30] The really nice thing about it,
[2259.34 --> 2260.62] and I didn't expect this at all,
[2260.72 --> 2262.32] I didn't even think about this
[2262.32 --> 2263.38] until I tried it,
[2263.78 --> 2266.12] it uses a Python library underneath,
[2266.12 --> 2267.82] which actually supports
[2267.82 --> 2269.54] the iCloud two-factor
[2269.54 --> 2271.42] authentication mechanisms.
[2271.96 --> 2273.24] So when I brought this up
[2273.24 --> 2274.16] for the first time,
[2274.58 --> 2275.62] a little pop-up appeared
[2275.62 --> 2276.60] on my Mac to say,
[2276.94 --> 2278.14] hey, someone's trying to log in
[2278.14 --> 2279.50] as you back in Raleigh.
[2279.56 --> 2280.08] Is this you?
[2280.16 --> 2281.34] And here's your two-factor code.
[2281.40 --> 2281.90] And I was like,
[2282.30 --> 2283.94] huh, did not expect that.
[2284.40 --> 2284.96] Yeah, that made me feel
[2284.96 --> 2285.62] a little bit better
[2285.62 --> 2286.80] that it was kind of legit
[2286.80 --> 2288.10] about how it's authorizing
[2288.10 --> 2289.20] against the iCloud servers.
[2289.28 --> 2289.96] It seems to be using
[2289.96 --> 2291.96] like an official Apple API for that.
[2292.40 --> 2293.46] And I think it's great
[2293.46 --> 2294.74] for running on your NAS.
[2294.74 --> 2295.88] If you've got a NAS box
[2295.88 --> 2297.14] that you can shell into,
[2297.70 --> 2299.28] you could go into your directory
[2299.28 --> 2300.22] of choice on your NAS
[2300.22 --> 2301.28] and execute this thing,
[2301.32 --> 2302.14] and it's just going to sit there
[2302.14 --> 2303.34] and download photos all day long.
[2304.00 --> 2304.70] And I think for me,
[2304.78 --> 2307.34] the absolute killer use case
[2307.34 --> 2309.34] are like my parents' phones.
[2309.76 --> 2310.92] You know, a couple of parents
[2310.92 --> 2311.40] use Android,
[2311.52 --> 2313.14] a couple use iOS.
[2313.88 --> 2315.12] And the iOS ones,
[2315.18 --> 2315.86] I've really struggled
[2315.86 --> 2316.78] to get the photos
[2316.78 --> 2317.64] out of iCloud
[2317.64 --> 2319.66] into anything meaningful,
[2319.82 --> 2320.46] off their phones,
[2320.56 --> 2321.40] into anything meaningful,
[2321.52 --> 2322.58] like NextCloud even
[2322.58 --> 2324.30] is a bit of a crapshoot on iOS.
[2325.06 --> 2326.26] And this just solves
[2326.26 --> 2327.86] that problem altogether.
[2328.26 --> 2328.72] I'm not,
[2328.86 --> 2329.68] the only thing I'm not
[2329.68 --> 2330.76] totally certain on
[2330.76 --> 2331.96] is how long
[2331.96 --> 2333.30] that two-factor authentication
[2333.30 --> 2334.72] token lasts for.
[2335.18 --> 2336.42] And I guess time will tell,
[2336.54 --> 2338.30] but I'm going to set this up
[2338.30 --> 2339.46] for my parents this week
[2339.46 --> 2340.10] whilst I'm here
[2340.10 --> 2341.82] and then report back
[2341.82 --> 2342.22] when it,
[2343.22 --> 2343.42] you know,
[2343.44 --> 2343.94] in six months
[2343.94 --> 2344.64] and let you know
[2344.64 --> 2345.46] how it's gone.
[2345.98 --> 2346.36] And are you thinking
[2346.36 --> 2347.16] just chron it
[2347.16 --> 2348.34] so it just runs automatically
[2348.34 --> 2349.76] every night or something?
[2349.76 --> 2351.16] Yeah, exactly.
[2351.32 --> 2352.28] Put it on a timer
[2352.28 --> 2353.12] and then let it download
[2353.12 --> 2354.24] every day,
[2354.34 --> 2354.84] every week,
[2354.92 --> 2355.42] whatever, yeah.
[2355.74 --> 2356.60] Yeah, that will be interesting
[2356.60 --> 2357.08] to see how long
[2357.08 --> 2358.28] that two-factor authentication,
[2358.60 --> 2358.92] if it is,
[2359.10 --> 2360.14] I bet you it must have
[2360.14 --> 2361.30] some time expiration.
[2361.76 --> 2362.76] So you'll have to check back in
[2362.76 --> 2363.94] and see if either
[2363.94 --> 2365.40] A, it generates a new prompt
[2365.40 --> 2366.76] or B, just breaks quietly.
[2370.44 --> 2372.30] Backblaze.com slash SSH.
[2372.56 --> 2373.62] Go there to get a free trial,
[2373.76 --> 2375.12] no credit card required.
[2375.24 --> 2376.28] Just get peace of mind
[2376.28 --> 2377.14] knowing your files
[2377.14 --> 2378.06] are backed up securely
[2378.06 --> 2378.74] in the cloud
[2378.74 --> 2379.94] with Backblaze.
[2380.24 --> 2381.36] It's $7 a month,
[2381.48 --> 2382.16] no gimmicks.
[2382.42 --> 2383.66] You get unlimited backup
[2383.66 --> 2384.80] for your Mac or your PC,
[2385.14 --> 2385.62] your movies,
[2385.76 --> 2386.14] your music,
[2386.26 --> 2386.76] your photos,
[2386.98 --> 2387.44] your videos,
[2387.54 --> 2388.06] your projects,
[2388.40 --> 2389.22] all the data.
[2389.58 --> 2390.80] And Backblaze now has
[2390.80 --> 2391.90] over an exabyte
[2391.90 --> 2392.90] of customer data
[2392.90 --> 2393.86] backed up and counting
[2393.86 --> 2395.44] with 50 billion files
[2395.44 --> 2396.48] restored for their customers.
[2396.96 --> 2398.04] You can do web restores
[2398.04 --> 2399.64] if that's how you like to roll.
[2400.00 --> 2401.02] You can restore files
[2401.02 --> 2401.68] by the app
[2401.68 --> 2402.60] if that's how you want
[2402.60 --> 2403.98] to get to files on the go.
[2404.14 --> 2404.82] I don't know how you do.
[2405.08 --> 2406.16] And they also offer
[2406.16 --> 2407.36] restore by mail.
[2407.62 --> 2408.44] Check this out.
[2408.68 --> 2409.40] A flash key
[2409.40 --> 2410.16] or a hard drive
[2410.16 --> 2410.92] that you can grab
[2410.92 --> 2411.58] from them.
[2412.12 --> 2412.96] Ship to your door
[2412.96 --> 2414.14] overnight with your data
[2414.14 --> 2414.86] restored to it.
[2415.06 --> 2416.22] But here's the best part.
[2416.68 --> 2417.76] If you send the hard drive
[2417.76 --> 2419.04] back within 30 days,
[2419.40 --> 2420.42] you get a full refund.
[2420.82 --> 2422.14] Now that's some peace of mind.
[2422.22 --> 2423.02] If you lose your data
[2423.02 --> 2424.28] and you've got a lot of things
[2424.28 --> 2425.16] you're going to need to recover,
[2425.68 --> 2426.54] it's nice having
[2426.54 --> 2427.68] a physical hard drive
[2427.68 --> 2428.88] mailed to you overnight
[2428.88 --> 2429.98] by FedEx.
[2430.44 --> 2431.06] And if you're worried
[2431.06 --> 2432.72] about accidentally deleting files
[2432.72 --> 2434.06] for an extra $2 a month,
[2434.14 --> 2434.72] you can increase
[2434.72 --> 2435.68] your retention history
[2435.68 --> 2436.78] to one year.
[2437.22 --> 2437.82] Their mobile apps
[2437.82 --> 2438.62] mean you can get access
[2438.62 --> 2439.54] to those same files
[2439.54 --> 2440.36] when you're out and about
[2440.36 --> 2441.00] on the go.
[2441.56 --> 2441.90] And of course,
[2442.00 --> 2443.16] Backblaze has been recommended
[2443.16 --> 2444.38] by New York Times,
[2444.64 --> 2445.24] by Macworld,
[2445.34 --> 2446.06] by Tom's Guide,
[2446.52 --> 2447.20] 9to5Mac,
[2447.42 --> 2448.04] and many more.
[2448.50 --> 2449.34] But why not go see it
[2449.34 --> 2449.82] for yourself?
[2450.18 --> 2451.72] Get a free 15-day trial
[2451.72 --> 2453.36] at backblaze.com
[2453.36 --> 2454.96] slash SSH.
[2455.28 --> 2456.26] 15 days means
[2456.26 --> 2457.32] plenty of time
[2457.32 --> 2458.10] to upload
[2458.10 --> 2459.26] and download some files
[2459.26 --> 2460.14] and get a real feel
[2460.14 --> 2460.86] for the service.
[2461.18 --> 2461.90] And you know,
[2462.06 --> 2462.86] Backblaze has been around
[2462.86 --> 2463.38] for a while.
[2463.64 --> 2465.16] They started 14 years ago
[2465.16 --> 2466.02] to create a business
[2466.02 --> 2467.12] that's equally fair
[2467.12 --> 2468.06] and good for its customers,
[2468.56 --> 2468.84] partners,
[2469.32 --> 2469.72] employees,
[2470.20 --> 2470.58] investors,
[2470.78 --> 2472.20] and the greater community.
[2472.20 --> 2473.86] And since 2013,
[2474.36 --> 2475.34] they've been publishing
[2475.34 --> 2476.60] their hard drive reports.
[2477.12 --> 2477.56] That's a report
[2477.56 --> 2478.10] we make sure
[2478.10 --> 2479.02] to never miss.
[2479.10 --> 2480.20] And it's a real value
[2480.20 --> 2481.54] to the entire industry too
[2481.54 --> 2482.44] because of the amount
[2482.44 --> 2482.94] of disks,
[2483.36 --> 2484.20] the real scale
[2484.20 --> 2484.84] that Backblaze
[2484.84 --> 2485.50] is working with.
[2485.70 --> 2486.22] They can get
[2486.22 --> 2487.44] some genuine insights.
[2488.16 --> 2488.62] And now,
[2489.00 --> 2490.12] after 14 years,
[2490.12 --> 2491.50] they have over
[2491.50 --> 2492.94] 500,000 customers
[2492.94 --> 2495.72] in 175 countries.
[2496.24 --> 2497.10] Backblaze.com
[2497.10 --> 2498.22] slash SSH.
[2498.34 --> 2499.38] No credit card required.
[2499.70 --> 2500.10] Get started
[2500.10 --> 2501.34] on a free 15-day trial
[2501.34 --> 2503.00] and start backing up
[2503.00 --> 2503.42] your data.
[2503.88 --> 2504.28] Start getting
[2504.28 --> 2505.16] some peace of mind.
[2505.66 --> 2506.58] Backblaze.com
[2506.58 --> 2508.02] slash SSH.
[2510.22 --> 2510.70] Now,
[2510.76 --> 2511.74] I mentioned Tailscale
[2511.74 --> 2513.00] in the last episode,
[2513.16 --> 2514.68] which was a brand new
[2514.68 --> 2515.36] project to me,
[2515.42 --> 2516.12] but it turns out
[2516.12 --> 2516.96] a lot of you guys
[2516.96 --> 2517.66] had already figured
[2517.66 --> 2518.26] this one out
[2518.26 --> 2519.22] well ahead of me.
[2519.86 --> 2521.00] And Zahid writes in,
[2521.12 --> 2521.28] Hello,
[2521.46 --> 2522.32] I was just listening
[2522.32 --> 2523.32] to your latest episode
[2523.32 --> 2524.10] and heard about
[2524.10 --> 2525.34] your love for Tailscale.
[2525.86 --> 2527.04] Not sure if you're aware,
[2527.16 --> 2527.64] but there are
[2527.64 --> 2528.52] Synology packages
[2528.52 --> 2529.78] available for it as well.
[2530.34 --> 2531.24] Keep up the great work.
[2531.54 --> 2532.70] Cheers, Zahid.
[2532.94 --> 2533.82] Hey, that's handy.
[2534.24 --> 2535.06] Yeah, it really is.
[2535.10 --> 2535.24] I mean,
[2535.28 --> 2535.70] that was actually
[2535.70 --> 2536.26] the only reason
[2536.26 --> 2536.96] I ended up looking
[2536.96 --> 2538.10] at Tailscale
[2538.10 --> 2539.00] in the first place
[2539.00 --> 2540.34] was I was futzing
[2540.34 --> 2541.00] about with that
[2541.00 --> 2541.80] Synology Naz,
[2542.16 --> 2542.74] ready to put it
[2542.74 --> 2543.52] at my mom's house,
[2543.82 --> 2544.92] and I was like,
[2545.46 --> 2546.94] what's this Tailscale thing?
[2546.98 --> 2547.38] I'm pretty sure
[2547.38 --> 2547.98] I've heard of it.
[2548.06 --> 2548.46] And then I did
[2548.46 --> 2549.32] a bit of research,
[2549.50 --> 2550.16] figured out it was
[2550.16 --> 2550.80] WireGuard,
[2550.88 --> 2551.40] and was like,
[2552.12 --> 2553.56] I'll just give this a go.
[2554.10 --> 2555.20] And then within 10 minutes,
[2555.24 --> 2556.16] I'd built out everything
[2556.16 --> 2557.30] I was trying to achieve
[2557.30 --> 2557.98] with WireGuard
[2557.98 --> 2559.44] for several days prior.
[2559.90 --> 2560.78] No kidding.
[2560.94 --> 2561.96] Huge fan of Tailscale.
[2562.24 --> 2562.38] And it,
[2562.74 --> 2562.98] you know,
[2563.12 --> 2564.40] real success story.
[2564.92 --> 2565.96] My mom took it back
[2565.96 --> 2567.22] from my mother-in-law's house
[2567.22 --> 2567.70] where she,
[2567.82 --> 2568.04] you know,
[2568.10 --> 2569.58] came to meet my daughter
[2569.58 --> 2570.50] and stuff like that.
[2571.10 --> 2572.02] Took it back
[2572.02 --> 2573.00] to her house,
[2573.18 --> 2574.62] plugged in one Ethernet cable,
[2574.78 --> 2575.36] a power cable,
[2575.52 --> 2576.46] pressed the on button
[2576.46 --> 2577.06] on the Synology.
[2577.72 --> 2579.24] And within a couple of minutes,
[2579.32 --> 2580.04] it had booted,
[2580.44 --> 2581.88] and Tailscale had registered it.
[2582.04 --> 2582.66] It didn't have to do
[2582.66 --> 2583.54] any dynamic DNS,
[2584.44 --> 2585.74] no firewall changes.
[2585.74 --> 2587.42] It was just magic.
[2587.66 --> 2589.20] I swear it was awesome.
[2589.88 --> 2591.12] That's why we've been seeing
[2591.12 --> 2592.70] so much love this week.
[2592.88 --> 2593.72] Erno writes in,
[2593.90 --> 2594.84] I'm beyond ecstatic.
[2595.24 --> 2596.52] I listened to episode 54
[2596.52 --> 2597.24] of Self-Hosted
[2597.24 --> 2598.38] on my way to my morning
[2598.38 --> 2599.02] mountain biking,
[2599.44 --> 2600.58] and as soon as I came home,
[2600.66 --> 2601.96] I had to try Tailscale.
[2602.70 --> 2603.40] It was pretty cool
[2603.40 --> 2604.62] based on Alex's explanation,
[2604.84 --> 2605.94] but now that I tried it,
[2606.22 --> 2607.20] it's even cooler.
[2607.58 --> 2609.04] They make it super easy
[2609.04 --> 2609.54] to set up.
[2609.62 --> 2610.62] I think I've been setting up
[2610.62 --> 2611.86] WireGuard for weeks,
[2612.18 --> 2612.50] but this,
[2612.94 --> 2613.04] well,
[2613.08 --> 2613.70] this just takes care
[2613.70 --> 2614.60] of all of it for me.
[2615.12 --> 2615.80] I have it installed
[2615.80 --> 2616.34] on my phone,
[2616.72 --> 2617.38] Kubuntu desktop,
[2617.56 --> 2618.48] and my Linode server.
[2618.48 --> 2619.72] I plan on installing it
[2619.72 --> 2620.48] on my Odroid,
[2620.64 --> 2621.74] running an Armbian,
[2621.88 --> 2622.92] and I'm planning on setting up
[2622.92 --> 2624.04] some kind of sync thing.
[2624.78 --> 2625.44] We'll see.
[2625.76 --> 2626.40] But so far,
[2626.66 --> 2627.70] I am super ecstatic.
[2627.84 --> 2628.50] Thank you so much
[2628.50 --> 2629.44] for your mention of Tailscale.
[2630.28 --> 2630.74] And Chris,
[2631.08 --> 2631.72] glad you made it back
[2631.72 --> 2632.26] to Washington.
[2632.68 --> 2632.94] Alex,
[2633.06 --> 2633.66] I hope you're enjoying
[2633.66 --> 2634.18] the motherland.
[2634.46 --> 2634.82] Sincerely,
[2635.26 --> 2636.12] Erno from Virginia.
[2636.58 --> 2637.34] I think I weigh
[2637.34 --> 2638.84] at least 90%
[2638.84 --> 2639.78] of fish and chips now.
[2639.86 --> 2640.42] Good for you.
[2640.48 --> 2641.18] Having been back here
[2641.18 --> 2641.82] for a month.
[2642.12 --> 2643.14] That's what I'd do too.
[2643.28 --> 2643.84] I'd have to.
[2644.06 --> 2645.00] Fish and chips and curry.
[2645.68 --> 2646.50] So Taylor writes in,
[2646.90 --> 2647.48] thanks so much
[2647.48 --> 2648.20] for the amazing show
[2648.20 --> 2649.18] that is self-hosted.
[2649.28 --> 2650.06] Every two weeks,
[2650.14 --> 2651.46] I'm refreshing my podcatcher
[2651.46 --> 2652.30] like a madman.
[2652.86 --> 2653.72] I was just catching up
[2653.72 --> 2654.70] on episode 54
[2654.70 --> 2655.70] and could relate
[2655.70 --> 2657.54] to Alex's remote access woes.
[2658.06 --> 2659.00] Tailscale's a solution
[2659.00 --> 2659.98] that seems to be popular
[2659.98 --> 2661.40] on Reddit and IRC,
[2661.66 --> 2662.84] but I wanted to mention
[2662.84 --> 2663.74] something that has been
[2663.74 --> 2665.24] working really well for me,
[2665.44 --> 2666.82] and that is ZeroTier.
[2667.32 --> 2667.52] Now,
[2667.58 --> 2669.04] ZeroTier is a distributed
[2669.04 --> 2669.92] WAN solution
[2669.92 --> 2671.20] that essentially creates
[2671.20 --> 2672.96] a global overlay network,
[2672.96 --> 2674.86] kind of like Nebula does.
[2675.38 --> 2676.50] It's open source
[2676.50 --> 2677.40] and self-hostable
[2677.40 --> 2678.98] with NAS packages,
[2679.30 --> 2680.50] third-party web management
[2680.50 --> 2681.00] GUIs,
[2681.10 --> 2681.66] and so on.
[2682.16 --> 2682.96] They just released
[2682.96 --> 2684.50] a DNS solution as well,
[2684.70 --> 2686.24] which sounds very similar
[2686.24 --> 2687.16] to the Tailscale
[2687.16 --> 2688.40] Magic DNS offering,
[2688.82 --> 2690.24] and I just wanted to give you guys
[2690.24 --> 2691.54] another self-hosted option.
[2691.90 --> 2692.46] Thanks for the show.
[2692.46 --> 2693.88] I definitely want to give
[2693.88 --> 2694.88] Headscale a try.
[2694.98 --> 2696.72] That's why I'm kind of waiting
[2696.72 --> 2697.84] to replace Nebula
[2697.84 --> 2698.78] with Tailscale,
[2699.02 --> 2699.82] is I want to see
[2699.82 --> 2701.26] how viable it is
[2701.26 --> 2702.54] to use Headscale
[2702.54 --> 2704.18] and self-host
[2704.18 --> 2705.06] the server component
[2705.06 --> 2705.64] of Tailscale,
[2705.76 --> 2706.42] but that also looks
[2706.42 --> 2706.84] really great.
[2706.90 --> 2707.24] It does.
[2707.46 --> 2708.60] There's so many options.
[2708.72 --> 2709.74] I just had to give a plug
[2709.74 --> 2710.46] for Nebula, too.
[2711.12 --> 2711.30] Now,
[2711.34 --> 2713.22] the only thing about ZeroTier
[2713.22 --> 2715.26] that kind of gives me,
[2715.50 --> 2718.44] it's just a 1% or 2% pause,
[2719.04 --> 2720.26] is that the protocol
[2720.26 --> 2721.08] is custom,
[2721.08 --> 2723.16] whereas the Tailscale protocol
[2723.16 --> 2725.14] is based around WireGuard.
[2725.36 --> 2725.48] So,
[2726.50 --> 2726.88] I mean,
[2726.92 --> 2727.62] who's to say one
[2727.62 --> 2728.48] is better than the other,
[2728.66 --> 2730.76] but I love me some WireGuard.
[2731.14 --> 2732.10] If I were betting,
[2732.22 --> 2732.70] man, Alex,
[2732.80 --> 2733.46] I know which one
[2733.46 --> 2734.04] I would bet on.
[2734.46 --> 2736.16] It's not one
[2736.16 --> 2736.90] that's been made up.
[2737.72 --> 2738.56] I really,
[2738.70 --> 2739.94] I respect the WireGuard
[2739.94 --> 2741.06] project immensely,
[2741.40 --> 2742.68] so it's just clearly
[2742.68 --> 2743.16] like the one
[2743.16 --> 2744.00] I would put my trust in
[2744.00 --> 2744.74] if my data was
[2744.74 --> 2745.90] truly critical.
[2746.30 --> 2746.98] I want to mention,
[2747.20 --> 2747.88] thank you everybody
[2747.88 --> 2748.40] who went to
[2748.40 --> 2749.16] self-hosted.show
[2749.16 --> 2749.78] slash contact
[2749.78 --> 2751.02] and sent in their question
[2751.02 --> 2751.62] we also have
[2751.62 --> 2752.64] the Discord community,
[2752.78 --> 2753.44] self-hosted.show
[2753.44 --> 2754.06] slash Discord,
[2754.22 --> 2755.28] which is always popping off.
[2755.72 --> 2757.26] And our Matrix community
[2757.26 --> 2758.24] is also growing.
[2758.60 --> 2759.78] There's a good conversation
[2759.78 --> 2761.06] of self-hosters going on.
[2761.36 --> 2762.34] You can find our Matrix server.
[2762.46 --> 2762.66] We have a
[2762.66 --> 2764.08] jupiterbroadcasting.com
[2764.08 --> 2764.66] Matrix server.
[2764.94 --> 2766.80] And probably the easiest way
[2766.80 --> 2768.26] to just get like a quick guide
[2768.26 --> 2769.48] is to actually go to
[2769.48 --> 2770.56] linuxunplugged.com
[2770.56 --> 2771.10] slash Matrix.
[2771.24 --> 2771.90] I haven't put that up
[2771.90 --> 2772.56] anywhere else yet.
[2773.06 --> 2774.20] But there is a community
[2774.20 --> 2775.08] growing out there
[2775.08 --> 2776.00] in Matrix land
[2776.00 --> 2776.60] of self-hosters.
[2777.18 --> 2777.60] Oh, Chris,
[2777.64 --> 2778.26] what have you done?
[2778.26 --> 2778.88] You've invited
[2778.88 --> 2780.02] another set of notifications
[2780.02 --> 2781.14] into my life.
[2781.24 --> 2782.12] Thank you so much.
[2782.58 --> 2784.38] Oh, oh, I know, Alex.
[2784.46 --> 2785.60] I know so well.
[2786.52 --> 2787.18] But you know,
[2787.24 --> 2788.64] I'm trying to assemble
[2788.64 --> 2789.10] the troops
[2789.10 --> 2790.48] because I'm so close
[2790.48 --> 2791.36] to getting
[2791.36 --> 2793.18] this automation bliss
[2793.18 --> 2794.48] where, you know,
[2794.54 --> 2795.90] my goal is to
[2795.90 --> 2796.90] make it so my wife
[2796.90 --> 2798.06] no longer has to worry
[2798.06 --> 2799.26] about blowing
[2799.26 --> 2801.22] a 15 amp circuit.
[2801.22 --> 2802.22] If we have a heater going
[2802.22 --> 2802.68] and she wants
[2802.68 --> 2803.46] to run the toaster,
[2803.96 --> 2804.82] I want Home Assistant
[2804.82 --> 2805.60] to figure it out.
[2806.06 --> 2806.52] And I know,
[2806.66 --> 2807.70] like our guest Matt
[2807.70 --> 2808.46] and others out there
[2808.46 --> 2809.04] have done this,
[2809.10 --> 2809.74] but I could use
[2809.74 --> 2810.28] some wisdom.
[2810.84 --> 2811.86] So the Matrix server
[2811.86 --> 2812.52] is a great spot
[2812.52 --> 2813.30] to let me know
[2813.30 --> 2814.64] because I'm trying
[2814.64 --> 2815.36] to drop in
[2815.36 --> 2815.84] on the Matrix
[2815.84 --> 2816.46] from time to time.
[2816.54 --> 2817.30] The Discord's also
[2817.30 --> 2817.86] really great.
[2818.14 --> 2818.94] Or Telegram.
[2819.34 --> 2820.12] How have you solved
[2820.12 --> 2821.08] this particular problem?
[2821.28 --> 2822.00] What should I do?
[2822.10 --> 2823.40] And will my Z-Wave devices
[2823.40 --> 2824.56] update fast enough?
[2825.20 --> 2825.90] Because it seems like
[2825.90 --> 2826.40] there's sometimes
[2826.40 --> 2827.60] like a 20-second lag.
[2828.10 --> 2828.66] All these things.
[2828.72 --> 2829.32] Share your wisdom.
[2829.32 --> 2830.16] Let's get this energy
[2830.16 --> 2830.94] monitoring figured out
[2830.94 --> 2831.60] because I think this is
[2831.60 --> 2832.14] going to be big
[2832.14 --> 2833.28] in the self-hosting community.
[2833.90 --> 2834.38] And as always,
[2834.54 --> 2835.36] I want to give a big
[2835.36 --> 2837.14] thank you to our SRE subscribers.
[2837.38 --> 2838.56] You make this show possible.
[2839.16 --> 2839.62] You can go to
[2839.62 --> 2840.76] selfhosted.show
[2840.76 --> 2841.78] slash SRE
[2841.78 --> 2842.90] to support the show.
[2843.56 --> 2844.40] And you can find us
[2844.40 --> 2844.96] on Twitter.
[2845.10 --> 2845.84] Alex is over there
[2845.84 --> 2846.82] at Ironic Badger.
[2846.94 --> 2847.96] I'm at Chris LAS
[2847.96 --> 2848.58] and the show
[2848.58 --> 2849.94] at Self Hosted Show.
[2850.30 --> 2851.18] And as usual,
[2851.30 --> 2851.86] thanks for listening,
[2851.98 --> 2852.28] everybody.
[2852.50 --> 2852.78] That was
[2852.78 --> 2853.82] selfhosted.show
[2853.82 --> 2854.96] slash 55.
[2854.96 --> 2860.36] was
[2860.36 --> 2861.26] thanks for listening.
[2861.74 --> 2862.68] And I
[2862.68 --> 2871.42] Operation
[2871.42 --> 2873.22] might
[2873.22 --> 2873.24] have