Closed robudus closed 3 months ago
Yes, it's a bug! It works with 2024.4.0.
I will investigate
Just got the same error when copying the 2024.3.0 files to my local environment and validating the config. When restoring the files from the previous release the validation works as expected.
Using EspHome 2024.4.2. Do you mean the problem could be fixed by downgrading it to 2024.4.0, at least as a workaround until the real issue is solved?
I just found out: There is no EspHoMaTriXv2 version tagged 2024.5.0! So, as fallback the default branch is used (see https://esphome.io/components/external_components#external-components), which is very old. Please use "latest" or an available version number as ref, e,g, latest or 2024.3.0,
So this is not a bug in EspHoMaTriX!
Where exactly do you mean should this "latest" be adjusted?
In my case I just have a source of type local in the yaml
You have to specify a valid branch under the ref tag in your yaml.
external_components:
- source:
type: git
url: https://github.com/lubeda/EspHoMaTriXv2
ref: latest
refresh: 60s
components: [ ehmtxv2 ]
I got that when using a git resource, but how to handle the error when using a local source with the files copied to a local folder?
external_components:
- source:
path: /copied_components
files copied to a local folder
Copy files from latest
branch...
Ok my fault, shame on me 😀 now I got the point, thanks
Question
Hi i would like to compile the latest version to my esp32 but get the Error: I use EspHome in HomeAssistant 2024.4.2
see logs for the error.
I use this yaml https://github.com/lubeda/EspHoMaTriXv2/blob/latest/install/ulanzi-easy.yaml
Can you please help me.
Thanks
ROBudus
Additional information
used Hardware:
ESP32
EspHoMaTriXv2 version: 2024.5.0
Logs