text stringlengths 7 369 |
|---|
[2341.70 --> 2347.36] And then you go to the web address, like it's a 192.168.0.1 kind of a thing. |
[2347.36 --> 2350.64] And you configure it to join your actual Wi-Fi network. |
[2351.26 --> 2358.26] And then pretty much shortly after that, Home Assistant detects it and says, hey, would you like to use the Shelly integration? |
[2358.62 --> 2362.44] Now this, my friends, this is where a choice will be made. |
[2362.44 --> 2366.40] This is where early into the process, you will reach a fork in the road. |
[2366.62 --> 2371.88] You must choose if you want to go with native Shelly integration or if you want to use MQTT. |
[2372.14 --> 2378.34] Because, of course, everything in Home Assistant is just three steps away from using MQTT. |
[2378.70 --> 2380.72] And the Shelly flood is no different. |
[2380.72 --> 2387.90] Now I, because I had really no time to mess around, just decided to use the native integration. |
[2388.28 --> 2393.08] I had heard that in the past there was some issues, but those issues had been resolved. |
[2393.08 --> 2396.56] So I thought, okay, self, we'll use the native Shelly integration. |
[2397.62 --> 2398.86] So I went ahead and did that. |
[2398.94 --> 2404.68] And now as we're looking right here at it during the show, I have what everybody has. |
[2404.68 --> 2408.68] And that is that now the Shelly temperature sensor is completely offline. |
[2409.84 --> 2411.80] Home Assistant can no longer talk to it. |
[2412.28 --> 2418.76] Because the way the system is supposed to work is that when the temperature drops or when it detects a leak, |
[2419.22 --> 2423.86] the device is supposed to wake up, join your Wi-Fi, and report back to Home Assistant. |
[2424.86 --> 2428.62] And you can kind of configure that threshold of, is it 1%? |
[2429.10 --> 2430.92] Is it, you know, 1 degree in temperature? |
[2431.12 --> 2432.12] Is it 0.5 degrees? |
[2432.16 --> 2433.14] Is it 2 degrees in temperature? |
[2433.14 --> 2436.58] What's the threshold to wake up the device and then report back? |
[2437.40 --> 2439.54] However, that doesn't seem to be working for me. |
[2439.86 --> 2443.74] Clearly, I should have gone the MQTT route, which the rest of the internet would tell you as well. |
[2444.06 --> 2448.44] I'm not particularly interested in doing that for reasons, but I may eventually. |
[2449.24 --> 2453.52] However, my overall experience with the Shelly was pretty good. |
[2454.16 --> 2460.26] And I am kind of in the process of looking at getting rid of some of my Z-Wave devices. |
[2460.26 --> 2470.40] I am considering when I get back from my September West Coast tour, thinking about doing a nuke and pave and redoing my Home Assistant setup. |
[2470.68 --> 2473.24] You have been threatening that for a number of months now. |
[2473.94 --> 2475.04] I'm so annoyed, dude. |
[2476.20 --> 2477.44] I'm so annoyed. |
[2477.44 --> 2482.68] I really just don't want to, I have, you know, 60 Z-Wave devices or something stupid like that. |
[2482.70 --> 2484.40] And I just don't want to go through and reset them up. |
[2484.48 --> 2486.58] So I'm going to eliminate some of them. |
[2486.90 --> 2489.36] And I'm also going to eliminate some of my HomeKit devices. |
[2490.10 --> 2496.52] And I think I'm going to look at different Shelly devices that are Wi-Fi capable to see what I can replace with. |
[2496.52 --> 2501.88] And so I kind of wanted to get some experience with these Shelly devices to see if I liked them, to see if they'd be a candidate. |
[2502.28 --> 2506.10] And I had some new plumbing in Jupes that I want to put a leak sensor on anyways. |
[2506.84 --> 2509.16] And so this just seemed like a great opportunity to try it. |
[2509.32 --> 2511.84] And I also kind of would like to know what the temperature is in that area. |
[2511.94 --> 2512.32] So great. |
[2512.38 --> 2513.42] This device does both. |
[2513.90 --> 2515.44] And I like that it uses Wi-Fi. |
[2515.58 --> 2517.48] It's not Z-Wave or Zigbee. |
[2518.26 --> 2521.62] They claim you can get 12 to 18 months of battery life. |
[2521.70 --> 2528.02] It uses one of those 3-volt lithium CR123A, little batteries, little Duracells or whatever from wherever. |
[2528.54 --> 2538.20] And the fact that Homeless doesn't just detects it within seconds and offers up an integration, in theory if that integration worked the way I wanted, is a really nice experience. |
[2538.20 --> 2541.80] And there is a ton of documentation to actually make this thing work the way I want. |
[2542.68 --> 2547.20] But you know what I thought, Alex, is when I was using this, one of the things that struck me was, |
[2547.48 --> 2555.88] is there are areas where the Home Assistant developers could be closing the gap to make this a better user experience. |
[2556.34 --> 2565.98] Like when you connect something like a flood sensor, you've got to figure there's a pretty, like a 95% chance that if you get a flood connect, |
[2565.98 --> 2575.80] if Home Assistant sees a flood sensor connect to the system and start receiving data, you probably want an alert when the flood sensor detects a flood. |
[2575.80 --> 2583.68] Right? Like you can almost, probably some people that don't, but probably like 90-95% of the use cases, they want to know when the flood detector detects a flood. |
[2583.68 --> 2587.06] And there are lots of ways you can do this, man. |
[2587.10 --> 2589.26] I could get a notification in Matrix and Telegram. |
[2589.36 --> 2590.90] I could rig up some push notifications. |
[2591.80 --> 2597.00] I mean, there's a lot of ways, a lot of really great ways you can solve push notifications in Home Assistant. |
[2597.00 --> 2600.72] But A, nothing tells you you need to do it. |
[2600.82 --> 2601.98] B, nothing helps you do it. |
[2602.06 --> 2608.38] And C, nothing's like I push a button and now I'm getting push notifications from this integration. |
[2608.60 --> 2613.98] And to me, this just seems like a no-brainer Nebukasa integration. |
[2614.14 --> 2617.98] Like if you're paying for the monthly Nebukasa Home Assistant service, |
[2617.98 --> 2622.92] it seems like a no-brainer that they could be routing push services through that to the app |
[2622.92 --> 2625.88] that I already also have connected to the Nebukasa cloud service. |
[2626.16 --> 2630.16] And the Nebukasa servers offer push notification capabilities for developers. |
[2630.54 --> 2632.48] So like the infrastructure is there. |
[2632.60 --> 2634.06] Like everything's there. |
[2634.26 --> 2637.94] I just need a button that says get push notifications about this. |
[2637.94 --> 2642.46] And oh, by the way, if you're a Home Assistant member, you get those push notifications automatically. |
[2642.46 --> 2645.64] Like that just seems like a no-brainer value add that they could do. |
[2645.92 --> 2652.50] And you would need something in particular that would work with iOS's time-sensitive notifications |
[2652.50 --> 2654.10] and whatever the equivalent is on Android. |
[2654.16 --> 2656.54] Because you need something that'll break through like do not disturb. |
[2656.62 --> 2661.78] Because for a flood sensor, like I'm in a recording focus mode right now. |
[2661.88 --> 2664.74] Nothing but my wife and maybe a kid can get through this. |
[2665.46 --> 2667.16] But a leak sensor, I'd also like to get through. |
[2667.62 --> 2671.06] So you need something that could actually support time-sensitive notifications on iOS. |
[2671.06 --> 2675.90] And I've conveniently linked the documentation for that from Apple's developer portal in the show notes. |
[2677.58 --> 2681.22] You know, I'd like to see things like that as part of the Works with Home Assistant program |
[2681.22 --> 2682.88] that we covered last week on the show. |
[2684.10 --> 2686.98] You know, just imagine if Shelley were on that program. |
[2687.60 --> 2695.32] And as part of that program, there was a bunch of magic that became available to those developers, |
[2695.66 --> 2697.76] such as exactly what you just articulated. |
[2698.52 --> 2699.80] Yeah, that'd be so great. |
[2699.80 --> 2705.96] However, I gotta say, all that aside, really impressed with the Shelley setup. |
[2706.68 --> 2709.16] You know, the fact that it was super quick to connect to, |
[2710.10 --> 2713.06] had a really easy-to-use admin interface built into it. |
[2713.08 --> 2715.74] Anybody that's probably used a Shelley has seen this before. |
[2716.64 --> 2720.36] That even though this device isn't functioning with Home Assistant the way I want, |
[2720.36 --> 2726.82] I've decided to go ahead and pick up a couple of other products from them because I was overall very impressed. |
[2726.82 --> 2734.82] And so I'm getting the Shelley Plus H&T, which is their e-ink humidity and temperature sensor that has a little display. |
[2735.30 --> 2738.64] And then, of course, reports back to Home Assistant over Wi-Fi. |
[2738.64 --> 2740.32] We'll see how this works. |
[2740.40 --> 2742.58] I'm assuming probably going to be the same thing. |
[2742.86 --> 2745.10] MQTT would be probably a better route to go. |
[2745.68 --> 2746.60] But I'm going to give it a shot. |
[2746.60 --> 2751.36] That looks remarkably similar to the Xiaomi sensors that I have, which are BLE. |
[2751.80 --> 2753.10] Is this a Wi-Fi thing? |
[2753.46 --> 2754.28] It is, yeah. |
[2754.66 --> 2761.42] Because those BLE ones I have are about 90% reliable, which is just about enough. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.