text
stringlengths
9
408
[36.34 --> 39.72] And there's a couple of interesting tidbits about the future in there as well.
[40.76 --> 50.84] Well, I don't know if you remember, but you and I chatted back in 2017 on a Linux Action Show special about Home Assistant, what feels like 100 years ago now.
[51.36 --> 52.28] Yeah, no, I do remember.
[52.34 --> 54.88] Well, I remember it was somebody from Jupyter Broadcasting.
[55.00 --> 55.94] I didn't realize it was you.
[55.94 --> 56.42] Yeah.
[57.20 --> 59.50] And man, have things come a long way.
[59.68 --> 62.52] So thank you for joining us to catch us up on stuff.
[63.18 --> 66.80] I am the happy owner of a Home Assistant Blue device.
[67.04 --> 67.68] Love it.
[67.96 --> 68.20] Awesome.
[68.62 --> 72.46] I put the order in during the live stream, so I got it fairly early.
[73.22 --> 77.42] And I got to say, you know, months into it, the performance holds up compared to the Raspberry Pi 4.
[77.54 --> 79.58] I think it is outperforming the Raspberry.
[79.92 --> 81.24] I mean, it's a beast.
[81.84 --> 83.68] The N2 is just like, it's amazing.
[83.68 --> 87.08] So are there any plans for more expansions in that direction?
[87.44 --> 89.74] Is that going to be a focus going forward?
[89.78 --> 92.00] Because it really seems like a pretty sweet integration.
[92.50 --> 92.68] Yeah.
[92.74 --> 94.26] So there are definitely plans.
[94.66 --> 96.36] Nothing to announce just yet.
[96.80 --> 101.42] We realized with the N2+, like we only made the case, right?
[101.46 --> 103.20] So it's just a board.
[103.52 --> 110.78] And when people think of home automation, they obviously think of like Zigbee or Z-Wave or Chip or Matter, whatever it's going to be called.
[110.78 --> 116.66] And so that's something that we want to, you know, if we want to address, we want to include that as well.
[116.74 --> 129.50] And I think the, you know, the Home Assistant Blue was really like, you know, the ultimate race car, but it was not very accessible in that the price was not, the price was pretty steep for like, you know, a device.
[129.60 --> 132.10] And also you needed to add like a Zigbee stick and these kind of things.
[132.10 --> 147.28] So I think we are definitely going to look into something as a successor, nothing to announce just yet, but it will also be hopefully lower priced and more capable out of the gate to be like, you know, used for smart home.
[147.80 --> 147.88] Yeah.
[148.06 --> 154.84] I can absolutely see how that would be way simpler for new users to get into the space as well.
[154.84 --> 155.24] Yeah.
[155.34 --> 162.56] And I think, you know, when we look at these things, it's not just like, we don't just want to create a box that competes with like Philips Hue or anything, right?
[162.56 --> 163.80] Like we're Home Assistant.
[164.00 --> 169.22] So it needs to be, you know, kind of hackable, playful, open.
[169.48 --> 173.22] Like it just needs, you know, just like the Odoid N2 Plus or the Home Assistant Blue.
[173.34 --> 175.70] I mean, you can flash anything on it that you want, right?
[175.76 --> 182.56] We wouldn't, we're not interested in like building a lockdown box that like will just keep the users out.
[182.56 --> 185.82] Well, that is completely understandable, especially now having used one.
[185.98 --> 191.56] But so what about guys like me who will always have a use case where I'm going to want to run it on a server?
[191.64 --> 194.32] Like here at the studio, we have a server that's doing like a hundred other things.
[194.42 --> 199.62] And so running Home Assistant in a container is perfect for the use cases of just controlling studio lights.
[199.62 --> 202.32] And we're not really using any integrations and stuff like that.
[202.62 --> 204.54] How do you see that user base being addressed in the future?
[204.92 --> 207.14] Right now we have four installation types.
[207.46 --> 211.08] We have the Home Assistant operating system.
[211.08 --> 217.88] We have the Home Assistant supervised, the Home Assistant container, and then Home Assistant core, which is just like running it in Python yourself.
[218.26 --> 223.10] And all the other three installation approaches all rely on containers.
[223.34 --> 224.80] And so they all use the same image.
[225.28 --> 227.60] So it's like the core technologies are all very similar.
[227.76 --> 229.22] Yeah, it's all the same thing, really.
[229.22 --> 236.92] The only one that's different is core because you maintain your own Python virtual environment.
[237.52 --> 238.92] The other three are all Docker based.
[239.02 --> 240.02] So it's all the same thing.
[240.54 --> 243.82] So those four installation types are pretty much set in stone right now.
[243.94 --> 252.28] I think that if you, in your studio, you can either run the container or you can run a virtual machine with Home Assistant operating system.
[252.28 --> 257.44] You know, the benefit, of course, of the virtual machine is that you have one-click updates of Home Assistant.
[257.96 --> 266.80] Well, with the container, it really depends on like your container management software, which can be Unraid or Portainer or Synology or whatever.
[267.28 --> 270.72] You know, that software then has to do the update of the container.
[271.14 --> 272.58] I think that's the only real difference.
[272.58 --> 276.38] In the end, all of these containers, they're all run Alpine.
[276.74 --> 278.50] They run Python.
[278.64 --> 279.80] And we maintain that, right?
[279.82 --> 282.54] So we have a big wheel server.
[282.76 --> 287.44] We make sure that all the dependencies work and compiled and are just up to date and running.
[287.90 --> 290.54] And that's just, you know, a big benefit as a user.
[290.66 --> 294.22] And I think that moving forward, you just want to run Home Assistant container?
[294.70 --> 295.74] That will be possible.
[296.26 --> 296.48] I see.
[296.56 --> 302.56] So it's not like it's ever going to go away, but you just feel like there's a lot of benefits to Home Assistant managing the entire system.
[302.58 --> 305.02] Because of all of the interdependencies.
[305.40 --> 305.52] Yeah.
[305.58 --> 307.20] I mean, there's just so many moving parts.
[307.38 --> 314.26] I think that if you look at our requirements.txt, which is where we define like the Python dependencies, it's like over a thousand.
[314.78 --> 314.92] Right?
[314.94 --> 319.62] Because each integration comes with its own Python library, which is a requirement we made ourselves.
[319.76 --> 322.78] So it's obviously like, you know, our own guidelines.
[322.96 --> 328.18] But, you know, the reason we always do this is that we want integrations to rely on like an SDK.
[328.28 --> 332.08] So an SDK is a Python package of the standalone that translates.
[332.58 --> 334.80] The protocol into like Python objects.
[335.08 --> 338.98] And that way, other Python projects, not just Home Assistant, can also use this package.
[339.14 --> 339.28] Right?
[339.34 --> 342.72] So we don't want protocol-specific information inside Home Assistant.
[343.22 --> 350.00] Because we want to make sure that other Python-based home automation systems or just one-off scripts can use these protocols as well.
[350.00 --> 350.44] Wow.
[350.44 --> 350.56] Wow.
[350.74 --> 355.56] So it kind of sounds like to me what you guys did as a team is you looked at the kind of, if you will, the whole problem.
[355.56 --> 367.00] And you said, quite frankly, it is easier for us as a team to just do a whole OS than say, you must have considered, well, bless Ubuntu LTS as the supported Home Assistant platform.
[367.00 --> 368.76] And anything else is DIY.
[369.08 --> 372.20] But if you want our official way or our official image, it's all Ubuntu-based.
[372.38 --> 372.58] Yeah.
[372.68 --> 380.96] But the problem with that is that your virtual environment that runs Python is going to be, has to be maintained as well.
[381.02 --> 383.12] So, I mean, this is, of course, how Home Assistant started.
[383.22 --> 386.08] It was just a Python application that we distributed through PyPI.
[386.50 --> 386.68] Sure.
[386.68 --> 390.00] And people would run into, like, they would do pip upgrades.
[390.30 --> 393.34] And then, of course, some people will upgrade from the last release.
[393.46 --> 395.84] Some people will update from, like, six releases ago.
[395.98 --> 398.32] And people got stuck all the time.
[398.42 --> 404.32] And the way it works with our Docker containers is that we install all the Python dependencies fresh in each container.