Kay Ohtie (@KayOhtie@blimps.xyz)
blimps.xyz
Attached: 3 images My kingdom for @homeassistant@fosstodon.org to have a means of forcing Whisper to transcribe a spoken number as numeric digits instead of a word. Because of that, and not realizing I could do a Z2M command to start watering on a timer explicitly, I didn't notice my water was running all night and a fitting blew, causing me to water nearly 4000 liters before I caught it this morning. Fuck. Solution: default to 5 minutes. Don't think I can get this removed from my water bill. An expensive personal mistake.

Basically, I was super tired getting home from an event last night and didn’t even notice the water hadn’t stopped flowing normally. It’s quiet so I don’t normally hear it.

Apparently at some point a couple hours in a fitting in my drip setup blew, flooding my peppers planter entirely and in the process burning through nearly 4000 liters of water before I caught it on my way out the door to work this morning.

I’ve since learned there’s a Z2M command to start watering on a timer, but I didn’t know that before and trusted Whisper to not fuck this up. My fault.

Don’t think my water bill company will be amenable to it. I’ll call and ask but, fuck.

    • Kay Ohtie@pawb.socialOPEnglish
      7·
      2 days ago

      I set it up as just a sentence automation, not as a separate script being fired where that’d have caused an error. I’ve not found a means of forcing validation like that in sentence automations, only in custom sentences/intents (never quite gotten a handle on those)

      • just_another_person@lemmy.worldEnglish
        6·
        2 days ago

        Template Conditions in that case. Ensure it falls between a specific range when ingested as an intent, and reject if not within that range. Should help you avoid future issues like this.

        • Kay Ohtie@pawb.socialOPEnglish
          1·
          2 days ago

          Yep. In the fix I linked I set it up to default to a word if it fails the template instead, so it’ll then check for a match to that word (“fail”) and if so it just falls back to 5 minutes and will tell me as much.

          Going to be a hell of a lot better about that in the future though. Was definitely a rookie mistake on my part to assume that just because it’d worked every time I’d tested it, used it, and with timers and all thus far that it would always work 100% of the time. Why assume when you can validate? I do in code I write… Guess I don’t think about it in the same way with HA as much, oops.