You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that there is not already an issue with the same problem
This is really a bug of current code, not an enhancement request (f.e. adding support for a new device type). There is a dedicated template for feature-requests.
Describe the bug
Local external component is not found during compilation
To Reproduce
Steps to reproduce the behavior:
Create a new device with given yaml.
Copy external components "dps" to folder /opt/iobroker/iobroker-data/esphome.1/components
Expected behavior
Local components should work. If the remote github component is used, compilation is successful.
Logs (as screenshot and in text-form)
INFO ESPHome 2024.10.2
INFO Reading configuration /opt/iobroker/iobroker-data/esphome.1/dps.yaml...
INFO Unable to import component dps: No module named 'esphome.components.dps'
Failed config
Component not found: dps.
id: dps0
modbus_id: modbus0
update_interval: 5s
current_resolution: AUTO
Versions:
*** BASE SYSTEM ***
Static hostname: raspberrypi
Icon name: computer
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.6.51+rpt-rpi-v8
Architecture: arm64
OS is similar to:
Additional context
Basically I need this ESPHome project: https://github.com/syssi/esphome-dps
But the problem is that I need to change some cpp files of the components. So I cannot use the remote components.
The text was updated successfully, but these errors were encountered:
points to the root directory, not the components folder. Think of it like esphome is just cloning the repo, when you specify a git repo. The path is still "github://syssi/esphome-dps@main" not something like "github://syssi/esphome-dps@main/components"
So tldr:
change:
external_components:
- source:
type: local
path: ./components
to
external_components:
- source:
type: local
path: .
!!! Before you start !!!
Describe the bug
Local external component is not found during compilation
To Reproduce
Steps to reproduce the behavior:
Minimal! Yaml config to reproduce.
Expected behavior
Local components should work. If the remote github component is used, compilation is successful.
Logs (as screenshot and in text-form)
INFO ESPHome 2024.10.2
INFO Reading configuration /opt/iobroker/iobroker-data/esphome.1/dps.yaml...
INFO Unable to import component dps: No module named 'esphome.components.dps'
Failed config
dps: [source /opt/iobroker/iobroker-data/esphome.1/dps.yaml:53]
Component not found: dps.
id: dps0
modbus_id: modbus0
update_interval: 5s
current_resolution: AUTO
Versions:
*** BASE SYSTEM ***
Static hostname: raspberrypi
Icon name: computer
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.6.51+rpt-rpi-v8
Architecture: arm64
OS is similar to:
Model : Raspberry Pi 4 Model B Rev 1.5
Docker : false
Virtualization : none
Kernel : aarch64
Userland : 64 bit
*** NodeJS-Installation ***
/usr/bin/nodejs v20.18.0
/usr/bin/node v20.18.0
/usr/bin/npm 10.8.2
/usr/bin/npx 10.8.2
/usr/bin/corepack 0.29.3
Core adapters versions
js-controller: 7.0.1
admin: 7.2.6
javascript: 7.8.0
Installed ioBroker-Instances
Used repository: beta
Adapter "admin" : 7.2.6 , installed 7.2.6
Adapter "backitup" : 3.0.26 , installed 3.0.26
Adapter "cul" : 2.2.0 , installed 2.2.0
Adapter "discovery" : 5.0.0 , installed 5.0.0
Adapter "esphome" : 0.5.0-beta.8, installed 0.5.0-beta.8
Adapter "go-e" : 1.0.41 , installed 1.0.40 [Updatable]
Adapter "history" : 3.0.1 , installed 3.0.1
Adapter "javascript" : 8.8.3 , installed 7.8.0 [Updatable]
Controller "js-controller": 7.0.2 , installed 7.0.1 [Updatable]
Adapter "lovelace" : 4.1.10 , installed 4.1.10
Adapter "mqtt" : 6.1.2 , installed 5.2.0 [Updatable]
Adapter "shelly" : 8.4.0 , installed 8.4.0
Additional context
Basically I need this ESPHome project: https://github.com/syssi/esphome-dps
But the problem is that I need to change some cpp files of the components. So I cannot use the remote components.
The text was updated successfully, but these errors were encountered: