Home Assistant on Ulis Notes https://wolf-u.li/en/tag/home-assistant/ Recent content in Home Assistant on Ulis Notes Hugo en Copyright 2006-CURRENTYEAR Uli Wolf - All rights reserved Sun, 23 Jun 2024 12:01:45 +2300 ESPHome 'ota' requires a 'platform' key but it was not specified. https://wolf-u.li/esphome-ota-requires-a-platform-key-but-it-was-not-specified/ Sun, 23 Jun 2024 12:01:45 +2300 https://wolf-u.li/esphome-ota-requires-a-platform-key-but-it-was-not-specified/ <p>With the update to ESPHome greater 2024.06, some of my devices couldn&rsquo;t be updated as they showed the following error:</p> <div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code><span class="lnt">1 </span></code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-plaintext" data-lang="plaintext"><span class="line"><span class="cl">&#39;ota&#39; requires a &#39;platform&#39; key but it was not specified. </span></span></code></pre></td></tr></table> </div> </div><p><ins class="adsbygoogle" style="display:block; text-align:center;" data-ad-layout="in-article" data-ad-format="fluid" data-ad-client="ca-pub-2322978122735420" data-ad-slot="3161252284"></ins> The solution was to edit the config file where i originally had a section like this:</p> <div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code><span class="lnt">1 </span><span class="lnt">2 </span></code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">ota</span><span class="p">:</span><span class="w"> </span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">password</span><span class="p">:</span><span class="w"> </span>!<span class="l">secret esphome_ota_password</span><span class="w"> </span></span></span></code></pre></td></tr></table> </div> </div><p>Which, since the merge of a <link rel=dns-prefetch href=//github.com /> <a href="https://github.com/esphome/esphome/pull/6459" title="specific PR" target="_blank" rel="nofollow noopener noreferrer" > specific PR&nbsp;<svg xmlns="http://www.w3.org/2000/svg" class="icon" aria-hidden="true" focusable="false" viewBox="0 -128 512 640"> <path d="M384 320c-17.67 0-32 14.33-32 32v96H64V160h96c17.67 0 32-14.32 32-32s-14.33-32-32-32L64 96c-35.35 0-64 28.65-64 64V448c0 35.34 28.65 64 64 64h288c35.35 0 64-28.66 64-64v-96C416 334.3 401.7 320 384 320zM488 0H352c-12.94 0-24.62 7.797-29.56 19.75c-4.969 11.97-2.219 25.72 6.938 34.88L370.8 96L169.4 297.4c-12.5 12.5-12.5 32.75 0 45.25C175.6 348.9 183.8 352 192 352s16.38-3.125 22.62-9.375L416 141.3l41.38 41.38c9.156 9.141 22.88 11.84 34.88 6.938C504.2 184.6 512 172.9 512 160V24C512 10.74 501.3 0 488 0z"/> </svg></a> into 2024.06 has to look like that (also described <link rel=dns-prefetch href=//esphome.io /> <a href="https://esphome.io/components/ota/esphome.html" title="here" target="_blank" rel="nofollow noopener noreferrer" > here&nbsp;<svg xmlns="http://www.w3.org/2000/svg" class="icon" aria-hidden="true" focusable="false" viewBox="0 -128 512 640"> <path d="M384 320c-17.67 0-32 14.33-32 32v96H64V160h96c17.67 0 32-14.32 32-32s-14.33-32-32-32L64 96c-35.35 0-64 28.65-64 64V448c0 35.34 28.65 64 64 64h288c35.35 0 64-28.66 64-64v-96C416 334.3 401.7 320 384 320zM488 0H352c-12.94 0-24.62 7.797-29.56 19.75c-4.969 11.97-2.219 25.72 6.938 34.88L370.8 96L169.4 297.4c-12.5 12.5-12.5 32.75 0 45.25C175.6 348.9 183.8 352 192 352s16.38-3.125 22.62-9.375L416 141.3l41.38 41.38c9.156 9.141 22.88 11.84 34.88 6.938C504.2 184.6 512 172.9 512 160V24C512 10.74 501.3 0 488 0z"/> </svg></a>):</p> With the update to ESPHome greater 2024.06, some of my devices couldn’t be updated as they showed the following error:

1

'ota' requires a 'platform' key but it was not specified.

The solution was to edit the config file where i originally had a section like this:

1
2

ota:
  password: !secret esphome_ota_password

Which, since the merge of a specific PR  into 2024.06 has to look like that (also described here ):

1
2
3

ota:
  - platform: esphome
    password: !secret esphome_ota_password

And now it all worked again ;-)

]]> Home Assistant: Change file without core running https://wolf-u.li/homeassistant-change-file-without-core-running/ Tue, 23 Jan 2024 21:25:21 +2300 https://wolf-u.li/homeassistant-change-file-without-core-running/ <p>Recently i managed to change a file in the Home Assistant configuration and then i forgot about that change&hellip; a bit later i started the upgrade to the latest version of Home Assistant which doesn&rsquo;t check if Home Assitant could be started with the current configuration &hellip; of course i had managed to break it and so home assistant &ldquo;core&rdquo; didn&rsquo;t start. <ins class="adsbygoogle" style="display:block; text-align:center;" data-ad-layout="in-article" data-ad-format="fluid" data-ad-client="ca-pub-2322978122735420" data-ad-slot="3161252284"></ins> The solution was to logon either via SSH (if you have the addon installed and configured) or to have access to the console of the Home Assistant OS. Once you are logged on, follow these steps:</p> Recently i managed to change a file in the Home Assistant configuration and then i forgot about that change… a bit later i started the upgrade to the latest version of Home Assistant which doesn’t check if Home Assitant could be started with the current configuration … of course i had managed to break it and so home assistant “core” didn’t start. The solution was to logon either via SSH (if you have the addon installed and configured) or to have access to the console of the Home Assistant OS. Once you are logged on, follow these steps:

  • Enter login to switch from the ha tool to the commandline
  • Change to the home assistant directory via cd /mnt/data/supervisor/homeassistant
  • Edit the corresponding file via vi <filename>
  • Enter exit to go back to the ha tool.
  • Enter core restart to restart home assistant

Hopefully it should be able to start again :)

]]>