text stringlengths 9 408 |
|---|
[1724.96 --> 1726.62] We wanted to do a bunch for this episode. |
[1726.74 --> 1727.94] In fact, we were going to mention it earlier. |
[1728.04 --> 1728.86] It's episode 60. |
[1729.08 --> 1730.06] It's a feedback special. |
[1730.70 --> 1730.98] Indeed. |
[1731.30 --> 1732.18] 60 episodes. |
[1732.34 --> 1732.54] Wow. |
[1732.72 --> 1734.16] That's a, that's a lot of episodes. |
[1734.16 --> 1738.26] In fact, if we've been doing weekly, we'd be 120 by now. |
[1738.86 --> 1739.16] Whoa. |
[1739.88 --> 1743.16] You see my maths there was, it's, uh, pretty quick. |
[1743.58 --> 1749.02] Anyway, red asks, do you guys have any naming conventions for your home assistant automations? |
[1749.90 --> 1751.62] Oh, that's a great question. |
[1752.18 --> 1753.14] I should. |
[1753.80 --> 1758.58] I, if you were to look at my automations right now, I think I've, I think I've tried three |
[1758.58 --> 1762.40] different naming schemes, uh, you know, over the couple of years that I've been running |
[1762.40 --> 1763.28] home assistant now. |
[1763.98 --> 1764.98] It's kind of embarrassing. |
[1765.58 --> 1768.66] You are an XKCD comic personified, are you? |
[1769.12 --> 1769.40] Yeah. |
[1769.88 --> 1770.76] It's kind of embarrassing. |
[1771.06 --> 1775.78] I mean, I try and do something like, I try and group them, you know, button dash office |
[1775.78 --> 1780.34] lights, toggle button dash toggle music room lamps, whatever it is. |
[1780.34 --> 1787.38] Uh, climate dash up and downstairs set to 18 Celsius, that kind of thing at 8am. |
[1787.48 --> 1791.72] I try and make the titles as descriptive as possible, starting off with, you know, the |
[1791.72 --> 1795.38] type of events first, you know, or integration, I suppose first. |
[1796.30 --> 1799.96] Uh, and then if that doesn't work, I'll do things like notify dash. |
[1800.12 --> 1804.28] So I just have like a single word and then a hyphen and then an explanation of what it |
[1804.28 --> 1804.52] does. |
[1804.58 --> 1805.26] That seems to work. |
[1805.30 --> 1805.56] Okay. |
[1806.38 --> 1806.74] Yeah. |
[1806.78 --> 1808.86] It's pretty close to what I've, I've pretty much landed on. |
[1808.86 --> 1810.56] Mine's a little more rudimentary. |
[1810.62 --> 1815.38] It's just like if it's, if it's a heater and it's being turned on, it's heat on dash, name |
[1815.38 --> 1817.32] a heater, heat off dash, name a heater. |
[1817.74 --> 1822.10] But I've pretty much retired all of those now that I'm using the generic thermostat. |
[1823.50 --> 1828.18] I used to have a whole bunch that started turn on, turn off this, turn on that. |
[1828.68 --> 1831.42] And when you're looking through a whole group of stuff, you kind of want to group things |
[1831.42 --> 1832.14] together a little bit. |
[1832.14 --> 1834.24] Like you want all the bedroom automations to be together. |
[1834.34 --> 1835.96] You want all the kitchen things to be together. |
[1836.50 --> 1836.82] Yeah. |
[1836.82 --> 1840.08] And so, you know, you've just got to find a logical grouping that works for you and stick |
[1840.08 --> 1840.36] with it. |
[1840.78 --> 1841.76] That's how I would do it too. |
[1841.76 --> 1846.82] Do it so that way all the same areas look all in the same spot when you're looking at |
[1846.82 --> 1847.48] the damn list. |
[1848.06 --> 1852.02] All right, Alex, our next one comes in on how to approach a company about building a |
[1852.02 --> 1854.46] home assistant integration based on their API. |
[1854.96 --> 1858.24] So this is a tricky one a listener of ours ran into. |
[1858.78 --> 1865.92] And they have basically created an integration that they realize may actually get them in |
[1865.92 --> 1866.28] trouble. |
[1866.82 --> 1871.44] And so they're wanting our opinion on the best way to approach companies. |
[1871.44 --> 1873.00] It's a European company. |
[1873.88 --> 1875.46] They're big in this space. |
[1876.22 --> 1879.36] So should they open source the library and just hope for the best? |
[1879.42 --> 1881.80] Should they try to contact the company and get permissions? |
[1883.02 --> 1884.86] What are your thoughts on how they should approach them? |
[1885.82 --> 1887.24] Well, I think it depends on the company. |
[1887.94 --> 1892.20] So, I mean, in the question, which is linked to in the show notes, there's an awful lot more |
[1892.20 --> 1892.58] detail. |
[1892.58 --> 1896.86] But essentially, this one revolves around reverse engineering token generation. |
[1897.78 --> 1903.08] So, I mean, if you were to contact this company and say, hey, I have been able to achieve this |
[1903.08 --> 1903.56] result. |
[1903.56 --> 1906.14] You will end up in one of two situations. |
[1906.56 --> 1911.04] One, you'll end up in the Swedish school voting app situation. |
[1911.18 --> 1913.72] I don't know if you saw this in the news a little while ago. |
[1914.26 --> 1920.12] A couple of parents basically reverse engineered their school district's app to allow parents |
[1920.12 --> 1924.54] to talk to teachers and all that kind of thing so that they could access the API that was |
[1924.54 --> 1929.76] publicly available and then build another app on top of it that was better. |
[1930.38 --> 1934.38] So you might end up in a situation that they did where the government, the local government |
[1934.38 --> 1938.20] comes after you and starts issuing cease and desist letters and say, hey, stop that. |
[1938.28 --> 1938.92] You're hacking us. |
[1939.04 --> 1939.84] Blah, blah, blah, blah, blah. |
[1940.72 --> 1945.44] Because they don't understand that the publicly available API data is just that. |
[1945.50 --> 1946.10] It's not hacking. |
[1946.22 --> 1947.24] It's just it's available. |
[1947.38 --> 1948.76] That is how an API works. |
[1948.76 --> 1949.44] Yeah. |
[1949.62 --> 1953.74] Or you'll end up in a situation where the company is receptive and you might end up |
[1953.74 --> 1958.76] with a job out of it or some kind of situation where they're open to people willing to work |
[1958.76 --> 1961.44] with things like responsible disclosure and all that kind of thing. |
[1961.60 --> 1962.20] So, yeah. |
[1962.66 --> 1966.08] Don't go posting it all over Reddit and Twitter as your first port of call. |
[1966.34 --> 1969.34] Talk to the company first if you're worried it's going to get you in trouble and see what |
[1969.34 --> 1970.10] their response is. |
[1970.62 --> 1974.16] And then you can start going down the responsible disclosure routes and all the rest of it. |
[1974.54 --> 1977.22] Yeah, I think that's all probably pretty good advice. |
[1977.22 --> 1981.84] You could also try to, you know, maybe go a little LinkedIn spelunking, see if you can |
[1981.84 --> 1985.92] find some people that might be in the right areas of the company for you to reach out to. |
[1986.68 --> 1990.86] If the company has a forum that they run, sometimes some of the employees are active in there and |
[1990.86 --> 1994.16] you can kind of get a sense, start getting an idea who you're dealing with. |
[1995.20 --> 1997.02] This has got to be a wider problem. |
[1997.28 --> 2001.78] You know, even when you're not cracking tokens and whatnot, there's a lot of crap out there |
[2001.78 --> 2003.72] that could do with some home assistant integration. |
[2003.72 --> 2005.84] And they just need somebody to come knock on their door. |
[2006.48 --> 2014.10] Like it, it is a crime against humanity that the Victron folks that like do my inverter |
[2014.10 --> 2017.20] and my charge controller and manage all the power in my RV. |
[2017.94 --> 2022.46] It's a damn crime against humanity that they don't make a home assistant integration available. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.