• 18 Posts
  • 55 Comments
Joined 2 years ago
Cake day: July 31st, 2023
  • Mike Wooskey@lemmy.d.thewooskeys.comOPtohomeassistant@lemmy.world•Seeking assistance customizing a sentence/intent with templatingEnglish
    2·
    2 years ago

    Thanks for the references, but at least one example from https://www.home-assistant.io/integrations/intent_script/ seems to be wrong/outdated.

    From that page:

    Local lists

    Sometimes you don’t need a slot list available for all intents and sentences, so you can define one locally, making it usable only in the context of the intent data (like a collection of sentences) where it was defined. For example:

    language: en
intents:
  AddListItem:
    data:
      - sentences:
          - add {item} to [my] shopping list
        lists:
          item:
            wildcard: true

    This is the code in my conversations.yaml:

    intents:
  HowManyDaysUntil:
    data:
      - sentences:
          - how many days until {countdownname}
        lists:
          countdownname:
            - "this"
            - "that"

    Here are the only difference I see between my code and the example above:

    • I don’t have language: en (but when I add it, I get Invalid config for 'conversation' at conversations.yaml, line 1: 'language' is an invalid option for 'conversation', check: conversation->language)
    • The example uses a wildcard and I’m using strings (but I’m following their other examples to have a list of strings)

    However, this yaml gets Invalid config for 'conversation' at conversations.yaml, line 9: value should be a string 'conversation->intents->HowManyDaysUntil->0', got None

    Perhaps I can’t have intents in conversations.yaml? Or maybe not lists? I started this project by editing config/intents/sentences/en/_cmmon.yaml but that’s a bad idea because an update would wipe my customizations. What’s the appropriate place for me to add custom sentences/intents/responses/lists?

  • Mike Wooskey@lemmy.d.thewooskeys.comtohomeassistant@lemmy.world•Timer DurationEnglish
    4·
    2 years ago

    From what I understand, a timer’s duration is the amount of time the timer was set to run for when it was started - the total time, not the time remaining.

    If you’re wanting to determine the time remaining in an active timer, you need something like:

    {% set finish_time = state_attr('timer.timer_entity_id', 'finishes_at') %}
{{ '00:00' if finish_time == None else (as_datetime(finish_time) - now()).total_seconds() | timestamp_custom('%H:%M', false) }}

    Or this version, which breaks hours and minutes into speakable parts:

    {% set finish_time = state_attr('timer.timer_entity_id', 'finishes_at') %} 
{% set hours, minutes = ('00:00' if finish_time == None else (as_datetime(finish_time) - now()).total_seconds() | timestamp_custom('%H:%M', false)).split(':') | map('int') %} 
{{ '' if hours == 0 else hours ~ ' hour' if hours == 1 else hours ~ ' hours' }} {{ ' and ' if hours > 0 }} {{ minutes ~ ' minute' if minutes == 1 else minutes ~ ' minutes' }}
  • Mike Wooskey@lemmy.d.thewooskeys.comOPtohomeassistant@lemmy.world•Disabled automations continually become enabledEnglish
    1·
    2 years ago

    This is really confusing to me. The History list shows when this automation was turned on and turned off (turned on means enabled, turned off means disabled) but the Logbook list doesn’t show anything for this automation at the datetime it was enabled (it does show me manually disabling the automation, though).

    I searched for the automation’s name (e.g., automation.my_automation) in every file in HA’s confg directory and there are no occurrences. I also searched for the automation’s ID (e.g., 1623421375007) in every file in HA’s confg directory the only occurrence is in the Automations.yaml file where the automation is defined. I also searched for automation.turn_on and automation.turn_off in every file in HA’s confg directory and there are no occurrences.

    This seems strange: when I click on the “On” or “Off” bar in the History list for this automation and the details for the automation pop-up (screenshots below), and I then click “Related”, the section that says “Part of the following automations” lists about half of my automations, but none of them have anything to do with this automation.

  • Mike Wooskey@lemmy.d.thewooskeys.comOPtohomeassistant@lemmy.world•Disabled automations continually become enabledEnglish
    2·
    2 years ago

    Thanks for the explanation and example, @CondorWonder@lemmy.ca.

    I used Studio Code Server to search all files for “Automation: Turn Off” and “automation.turn_off” and “automation” - there were 100s (1000s?) of results. I scanned through them and didn’t see anything that looks like it was enabling these automations. And that’s the only record in my logbook around these automations being disabled.

    So now I’ve renamed some of my automations and re-disabled them. In a few days they’ll either become enabled or I’ll search my logs for errors including their previous names.

  • Mike Wooskey@lemmy.d.thewooskeys.comOPtohomeassistant@lemmy.world•How to configure Dreametech vacuum in Home Asisstant?English
    1·
    2 years ago

    I want to flash my vac with Valetudo - my goal is to run-only, no cloud. But I read through Valetudo’s instructions and it’s too scary for me. I don’t think I have the skills to solder a board together and I barely understand all the steps. I can follow instructions, but there’s one point where they say something like “do these few steps within 180 seconds or you may brick your vacuum” - that’s too much risk for a ~$1000 vacuum. I didn’t upgrade the firmware on my vac, so maybe someday the process will be slightly easier and I’ll take the risk.