text
stringlengths
9
408
[2022.86 --> 2029.30] Not only does the Victron system support MQTT, but it also supports Modbus over Ethernet and
[2029.30 --> 2029.58] TCP.
[2029.98 --> 2036.20] So there's like two really straightforward ways that they could build an integration to
[2036.20 --> 2040.04] get that data, which would be life-changing, life-changing.
[2040.32 --> 2043.42] And I've talked to people who've built all their own solutions for this stuff, but it's
[2043.42 --> 2047.00] just a great example of like, you can find people out there that are reverse engineering
[2047.00 --> 2048.66] it right now for these Victron systems.
[2049.16 --> 2052.52] But really what it needs is the company to either document this stuff or come out and do
[2052.52 --> 2055.58] it or, or enable a community to build something.
[2055.68 --> 2055.90] Right.
[2055.90 --> 2056.86] That's what we need.
[2056.94 --> 2060.82] And I don't know how we start changing that culture because when they're looking at how
[2060.82 --> 2066.30] they're going to spend their engineers time and resources, you know, it's a, it's a hard
[2066.30 --> 2067.24] thing to pro and con.
[2067.38 --> 2070.24] It looks, it just looks like a waste of time when you're doing it on a pro and con list.
[2071.00 --> 2076.06] I wonder how many more sales people like Victron might make if they advertise the home assistant
[2076.06 --> 2076.66] integration.
[2077.10 --> 2082.34] That's perhaps the angle that you have to approach is, is the business angle to get the product
[2082.34 --> 2087.74] phone as interested in spending those development tokens on what we want them to do.
[2088.06 --> 2089.08] I think it was Frank.
[2089.22 --> 2094.26] I think Frank on the live stream for home assistant said that Vans and, and mobile applications
[2094.26 --> 2098.02] are actually a very large use case for home assistant, which blew my mind.
[2098.04 --> 2099.86] I'm like, Hey, that's, that's me.
[2099.96 --> 2104.14] Like, but that's actually like something that is a big enough use case.
[2104.14 --> 2105.48] It was brought up on the live stream.
[2105.88 --> 2110.60] And yeah, when you're looking at the energy monitoring capabilities and logging and long-term
[2110.60 --> 2114.62] logging now available in home assistant, uh, yeah, that'd be powerful.
[2115.82 --> 2121.08] Well, James writes in, in defense of Portainer after last week's character assassination,
[2121.22 --> 2122.04] I think we gave it.
[2122.28 --> 2126.20] Hey guys, I just listened to 59 where y'all talk about Portainer.
[2126.30 --> 2130.30] Whilst I do love SSH and Docker CLI for most of my personal setup.
[2130.52 --> 2134.28] I think Portainer is great at two things at my company.
[2134.66 --> 2138.06] Number one, it provides discoverability for new users.
[2138.06 --> 2143.76] We're slowly dragging our company into the wonderful world of containers, but it is slow
[2143.76 --> 2145.12] getting everybody on board.
[2145.54 --> 2150.40] Having a nice GUI to show all the options for Docker run and to easily store things like
[2150.40 --> 2155.02] Docker compose stacks or private registry credentials where anyone can access them is
[2155.02 --> 2156.44] a huge benefit to us.
[2157.14 --> 2162.26] Number two, it also provides some level of access control, even in the free version remotely.
[2162.74 --> 2166.46] While we could just set up OS users for everyone on our big Docker test server.
[2166.46 --> 2171.72] It's much easier for me to just let Portainer handle it and somewhat lock it down, especially
[2171.72 --> 2176.58] when it comes to things like the QA team who don't really care about how things work under
[2176.58 --> 2176.90] the hood.
[2177.26 --> 2180.44] They just want to click a button, update a container and do their testing.
[2180.98 --> 2181.22] Thanks.
[2181.32 --> 2182.50] I love the show, James.
[2183.24 --> 2184.04] Fair enough.
[2184.86 --> 2185.26] Yeah.
[2185.26 --> 2190.68] After we recorded and I was chatting about it with Wes, it did kind of dawn on me.
[2190.92 --> 2191.94] Oh, right.
[2192.02 --> 2195.18] When you got a team of people that might need to poke in on these containers.
[2196.06 --> 2198.84] I start to appreciate a tool like this a little bit more.
[2198.90 --> 2204.78] Like we have more systems in the cloud on Linode than we probably should without some sort of
[2204.78 --> 2208.08] tool like this, because there's a lot of containers out there that we have running.
[2208.08 --> 2211.20] And, you know, you've got some and Wes and I have some running.
[2211.28 --> 2212.40] I've got some that only I've set up.
[2212.44 --> 2213.78] Wes has some that only he's set up.
[2214.02 --> 2217.10] We've got a lot of applications that are running in containers up there.
[2217.72 --> 2220.00] I could see how Portainer would be nice to manage all that.
[2220.14 --> 2223.36] I think we're probably pushing what you could do with the free version, though.
[2223.80 --> 2226.38] I mean, don't forget, I work on a daily basis with OpenShift.
[2226.48 --> 2230.32] And that really is the value add proposition of OpenShift.
[2230.62 --> 2233.88] I mean, there's a few more to it when you start getting down into the technical weeds.
[2233.88 --> 2241.04] But really, it's presenting a cohesive single pane of glass across different clouds.
[2241.48 --> 2244.70] That's really the value add of OpenShift, the hybrid cloud thing that you hear.
[2244.82 --> 2251.56] That's what it's doing, is it's giving people a standardized interface to access the underlying
[2251.56 --> 2253.56] abstractions, which in this case are containers.
[2254.26 --> 2259.10] You know, and James, who writes in, does make a valid point that, you know, you can use GUIs
[2259.10 --> 2259.98] to solve that problem.
[2259.98 --> 2266.38] I would argue that also you could use just simple bash aliases and some good documentation.
[2267.10 --> 2272.26] But, you know, I've worked with some QA teams in the past that really don't care how it works
[2272.26 --> 2272.70] under the hood.
[2272.80 --> 2276.44] They don't care if it's the perfect technical solution.
[2276.58 --> 2279.18] They just need to close their ticket and move on to the next one.
[2279.88 --> 2285.64] Well, and that's why often, especially internal projects, you'll go to a web page and there's
[2285.64 --> 2290.42] a button and that button, you know, it's just some hack script that's just doing something
[2290.42 --> 2293.96] to like, you know, check something and check something out and put them in the right spot
[2293.96 --> 2294.62] for the QA.
[2294.74 --> 2296.92] Like, it can get real hacky, but they don't care.
[2297.64 --> 2299.16] I'll tell you what I would like to see for JB.
[2299.52 --> 2302.76] And this is my own personal wish list that you don't know what I'm thinking yet.
[2302.86 --> 2305.18] So this is a voyage of discovery for you here, Chris.
[2306.12 --> 2310.50] You've been talking about this new server in LUP where you want to do tumbleweed or something
[2310.50 --> 2311.76] crazy with Sousa.
[2311.92 --> 2313.26] I don't know what you're smoking over there.
[2313.26 --> 2314.60] The audience voted.
[2315.84 --> 2320.22] I'm not convinced in the legitimacy of the results, but we're proceeding to maintain
[2320.22 --> 2320.62] faith.
[2321.04 --> 2325.26] Well, I was thinking, why don't we look at something like K3S, which is like a lightweight
[2325.26 --> 2330.56] Kubernetes from the Rancher team, an open source thing that is, you know, based around
[2330.56 --> 2336.14] Kubernetes, which is an industry standard deployment mechanism that we could adopt as
[2336.14 --> 2337.06] a network, you know?
[2337.82 --> 2340.38] For the on-premise and cloud systems.
[2341.84 --> 2342.68] Perhaps, yeah.
[2342.68 --> 2346.62] I mean, it's a lot of work for me, but I'm not afraid of a challenge.
[2347.86 --> 2348.14] Hmm.
[2348.32 --> 2348.56] Yeah.
[2348.60 --> 2348.86] Okay.
[2348.94 --> 2349.10] Yeah.
[2349.10 --> 2349.90] We should talk more about it.