- 10 Posts
- 917 Comments
Also, hard disagree.
smiletolerantly@awful.systemsto
Lemmy Shitpost@lemmy.world•I didn't realize it was so bad
30·1 month ago“average 50-59 year old weighs 5000 pounds” factoid actually just statistical error. Average person weighs 150 pounds. Pounds Georg, who lives in a cave and weighs over 50000000000000000000000000 pounds, is an outlier adn should not have been counted.
I don’t know. I had never seen another magical girl anime before, and it still stood out to me.
The Dvorak symphony or the Yusuke Kishi novel?
If the former, how dare you.
If the latter, … sorry I haven’t read it. おすすめですか。
Yeah, truly.
It’s a beautiful encapsulation of “what the fuck”.
“Madoka Magica” might as well be my trigger phase by now.
smiletolerantly@awful.systemsto
Lemmy Shitpost@lemmy.world•Working on my politics-free lemmy experience, what words should I add next?
17·1 month agoAdd “linux” and enjoy the empty feed
smiletolerantly@awful.systemsOPto
homeassistant@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
1·1 month agoAwesome!! And thanks for actually letting me know! :D
Edit: anything for the wishlist?
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
4·1 month agoThis started off as a single file in my private nix config, to see if I could get it working at all. In that initial part, some parts were indeed LLM generated (esp. testcases based on my existing intents and failures).
When I noticed that this might actually work and be useful not just for myself though, I moved everything out manually, refactored and cleaned it up, and everything since has just been myself. I guess you’re still right though. I’ll see about adding a disclaimer to the README until I’ve gotten the chance to properly rewrite everything.
smiletolerantly@awful.systemsOPto
homeassistant@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
2·1 month agoYes, you can! See the “threshold” value/slider. It’s at 0.7 by default, which seems to be a good tradeoff. 1 means exact match or failure, 0 will afaik match anything to everything.
Ah, I didn’t see the Edit, so we’re both in the same boat 😂
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
3·1 month agoHuh, interesting. Does that work with wildcards like “put x on my shopping list”? Also, what are you using for that, if I may ask?
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
2·1 month agoSorry, I don’t quite follow 😅
What’s the problematic response?
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
2·1 month agoYay, that’s fantastic to hear!
Also, how’s your experience been with the PE? Getting a readymade device in a nice shell is appealing for sure 😅
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
5·1 month agoOh, in the demo gif, that’s via a shortcut (holding power for half a second). Sorry, can’t help with wakeword there 😅
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
2·1 month agoVery cool. I’ll definitely look into that, and let you know back here :D
smiletolerantly@awful.systemsOPto
Selfhosted@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
8·1 month agoGlad to be of service… 😄
did you consider metaphone matching?
I did not even know about this. Sounds super interesting. Though it seems to be very language specific?
My original intent was to not rely on language specifics. But maybe we could just define additional steps in the pipeline for specific languages. Hm. I’ll have to think about this some more, but it might definitely be a great idea for a future version, so thanks for telling me about it!!
smiletolerantly@awful.systemsOPto
homeassistant@lemmy.world•hass-closest-intent: Fuzzy intent matcher for HomeAssistant. Garbled STT output in, actual intent out.English
3·1 month agoFinally got this through another comment below. No, this should not be able to happen, unless you yourself have created a custom intent + shell script action in home assistant that runs this. The integration itself does not execute actions/scripts or the like, it just finds the closest string in a list of strings, and then hands that to the official conversation agent/Hassil.







No
That’s not a physics statement btw. I just think that you, personally, are too slow to be able to do that. Offense intended.