text stringlengths 7 369 |
|---|
[1804.08 --> 1806.50] Where's my assurance that this is working? |
[1806.50 --> 1809.24] Can I have a button over Ethernet? |
[1809.84 --> 1813.64] But I suppose the other thing you've got to consider is, you know, with a little battery |
[1813.64 --> 1816.90] powered button or something like that, you can't be constantly pinging to say, are you |
[1816.90 --> 1817.30] okay? |
[1817.38 --> 1818.02] Are you okay? |
[1818.06 --> 1819.96] Because that would just, that's the problem. |
[1820.58 --> 1821.30] That is it. |
[1821.70 --> 1823.96] And the always powered stuff does do better. |
[1823.96 --> 1829.60] As a matter of the protocol though, when you hit the button, it should be a two-way thing. |
[1829.70 --> 1832.74] The button sends the thing and gets the acknowledgement back. |
[1832.78 --> 1833.26] I heard you. |
[1833.34 --> 1835.28] Otherwise the button just keeps buttoning. |
[1835.48 --> 1835.92] Yeah. |
[1836.32 --> 1836.72] Yeah. |
[1837.32 --> 1837.72] Yeah. |
[1837.72 --> 1839.42] And same with the sensors like temperature drop. |
[1839.54 --> 1844.62] I wake up and I send notification about temperature drop, but there's also an issue in Home Assistant |
[1844.62 --> 1849.20] where these devices are essentially offline until they wake up to do their job. |
[1849.20 --> 1854.52] And Home Assistant seems to be getting better about that, but it's not fantastic. |
[1854.86 --> 1860.82] And one of the things that can happen is it can say the temperature is 72 degrees Fahrenheit. |
[1861.16 --> 1863.96] And that's the last number that got into Home Assistant. |
[1864.16 --> 1868.54] And if it doesn't wake up and transmit another number for eight hours, Home Assistant just |
[1868.54 --> 1872.84] happily reports 72 degrees and here's your little bar graph and everything's just fine. |
[1873.00 --> 1876.12] And really the reality was the thing dropped off the network for eight hours. |
[1876.28 --> 1877.88] And I'm using mine to monitor my freezer. |
[1877.88 --> 1880.88] And in eight hours you can spoil a freezer, you know? |
[1881.10 --> 1881.54] Yes. |
[1882.02 --> 1889.46] See, it's funny because all of these are things that engineers solved in like the 1970s or 1980s |
[1889.46 --> 1890.98] with these alarm sensors. |
[1891.34 --> 1896.72] And the alarm sensors, like the ones that I'm using are encrypted, but the ones just before |
[1896.72 --> 1899.54] the ones that I'm using were not encrypted. |
[1899.92 --> 1904.34] And you can use software defined radio with those and you don't even have to have the alarm |
[1904.34 --> 1905.54] panel or anything like that. |
[1905.54 --> 1907.82] They actually do periodically check in. |
[1907.90 --> 1913.24] So like the batteries, like the little, the weird little, I don't even, I forget what their |
[1913.24 --> 1916.48] lithium cells, but they're tiny, but they're really thick. |
[1917.02 --> 1921.02] And those last like five years with these sensors. |
[1921.02 --> 1925.00] And it'll send a ping like every 15 minutes or so. |
[1925.80 --> 1932.10] And that the alarm panels will report, you know, a jam or RF interference. |
[1932.10 --> 1938.80] If the sensors don't check in every 15 minutes and same with the water sensors, like it'll set |
[1938.80 --> 1940.56] the, you'll get a trouble light on the panel. |
[1940.56 --> 1947.28] That's like, this is maybe alarm worthy, maybe not, but there is RF interference, or I haven't |
[1947.28 --> 1948.82] heard from this sensor in a while. |
[1949.36 --> 1955.92] And we were doing that when we had like 6502 levels of compute power for these kinds of |
[1955.92 --> 1959.40] things, which shows you how much garbage all of this stuff is. |
[1960.32 --> 1961.04] Yeah, you're right. |
[1961.30 --> 1965.98] Do we assume too much is going to work just because of how reliable TCP IP is? |
[1965.98 --> 1971.66] You know, we, uh, as a generation of engineers haven't grown up with just not working. |
[1972.60 --> 1980.28] We assume too much is, is, should work because TTL Motorola and the TTL, TTL logic was too |
[1980.28 --> 1981.08] damn good. |
[1981.60 --> 1983.68] Yeah, I can see it. |
[1984.42 --> 1985.94] TTL logic was so good. |
[1986.00 --> 1987.96] We could build an entire computer out of it. |
[1988.00 --> 1988.62] The Apple two. |
[1989.36 --> 1990.04] I'm sorry. |
[1990.10 --> 1990.84] The original Apple. |
[1991.04 --> 1994.30] The problem was that we wouldn't put everything on 2.4 gigahertz. |
[1994.30 --> 2001.06] So now everything has to communicate on the same exact channel on the same exact radio |
[2001.06 --> 2001.56] frequency. |
[2002.28 --> 2003.78] Oh, you know, it's crazy though. |
[2004.28 --> 2009.22] Like when you, cause I went down the rabbit hole in this whole IOT thing with radio frequencies |
[2009.22 --> 2012.48] and stuff, and I had no idea, but it really is the case. |
[2012.48 --> 2014.52] Like the physics of it with spread spectrum. |
[2015.16 --> 2021.34] If you have a really well implemented spread spectrum algorithm, the radio frequency bandwidth |
[2021.34 --> 2031.72] is, uh, very high shockingly high for these kinds of, of things, because it's, there's |
[2031.72 --> 2036.58] even a relatively small amount of frequency, the random, random hopping and rapidly random, |
[2036.86 --> 2042.30] randomly hopping at a relatively high frequency, doing those kinds of things on 2.4 gigahertz |
[2042.30 --> 2043.58] absent everything else. |
[2043.58 --> 2047.38] You could almost say that the FCC is getting to the point where it's obsolete. |
[2047.76 --> 2051.26] When our radio technology is a little bit more advanced, the whole spectrum allocation, |
[2051.66 --> 2052.18] blah, blah, blah. |
[2052.28 --> 2058.26] If everything, everything is, is implementing their radio circuit that way, it is a, it is, |
[2058.34 --> 2059.00] it's crazy. |
[2059.10 --> 2064.58] Nothing will interfere with anything else because it's, they're all using a different key to |
[2064.58 --> 2066.96] pick which thing is next for the thing that it's doing. |
[2066.96 --> 2068.18] Ah, I see. |
[2068.38 --> 2069.36] Boy, I hope that happens. |
[2069.50 --> 2076.18] In the meantime, I actually had to physically separate my wifi AP from my, my Zigbee stick |
[2076.18 --> 2078.50] because they were just colliding with each other too much. |
[2078.54 --> 2083.62] And so now I've physically separated the two and my Zigbee network has become more reliable. |
[2083.98 --> 2088.86] It's not solid, solid, not a hundred percent, but it's better now that I've just moved those |
[2088.86 --> 2089.64] two devices apart. |
[2089.92 --> 2090.02] Yeah. |
[2090.08 --> 2093.02] See, having to do that is just, we failed. |
[2093.22 --> 2095.94] Like whatever that technology is, has failed. |
[2095.94 --> 2097.26] That's what it felt like. |
[2097.34 --> 2099.28] It felt like I was doing a stupid, okay. |
[2099.36 --> 2099.64] All right. |
[2099.66 --> 2101.12] Well, all right. |
[2101.12 --> 2103.18] I'll do a layer one fix for this, I guess. |
[2103.78 --> 2107.70] That's like, well, you know, we've got running water, but in order for it to be potable, I |
[2107.70 --> 2108.46] have to boil it. |
[2108.54 --> 2110.40] And it's like, that's not a first world problem. |
[2114.34 --> 2116.64] Linode.com slash SSH. |
[2116.72 --> 2120.46] Go there to get a hundred dollars in 60 day credit on a new account and go there to support |
[2120.46 --> 2124.74] the show while you're checking out Linode, which I think is the best place to host your |
[2124.74 --> 2129.48] stuff, fast, reliable, great support data centers all over the world. |
[2129.60 --> 2130.56] It's what we use. |
[2130.62 --> 2131.78] It's the only thing I'll use there. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.