ESPHome
[BUG] YAML-Parser-Inkompatibilität: Fehler "Shorthand only for strings" bei external_components (Version 2025.11.2) #3423
Replies: 9 comments 5 replies
-
|
I don't understand what you're asking. That repo doesn't even exist. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Das Versuche ich seit drei Tagen
Gesendet mit der Telekom Mail App
…-- Original-Nachricht --
Von: Samuel Sieb ***@***.***
***@***.***> >
Betreff: Re: [esphome/feature-requests] [BUG] YAML-Parser-Inkompatibilität:
Fehler "Shorthand only for strings" bei external_components (Version
2025.11.2) (Discussion #3423)
Datum: 03.12.2025, 09:31 Uhr
An: esphome/feature-requests ***@***.***
***@***.***> >
Cc: svenstoltebs38116-max ***@***.***
***@***.***> >, Author <
***@***.*** ***@***.***> >
I don't understand what you're asking. That repo doesn't even exist.
You can use external components directly from github. That's the most
common way to use them.
—
Reply to this email directly, view it on GitHub
<#3423 (comment)>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BX7K2AQDMXLEUAEFH3GSNAT372NXLAVCNFSM6AAAAACN4MJY2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJUGU3TCMI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
You're doing something wrong then. You need to point to the repo, not an archive zip file. But again, that repo doesn't even exist anyway. |
Beta Was this translation helpful? Give feedback.
-
|
Could you recommend a Modbus server that I can use to configure a Modbus
RTU slave device? That would be a great help. Thank you for your quick
reply and your time!
Gesendet mit der Telekom Mail App
…-- Original-Nachricht --
Von: Samuel Sieb ***@***.***
***@***.***> >
Betreff: Re: [esphome/feature-requests] [BUG] YAML-Parser-Inkompatibilität:
Fehler "Shorthand only for strings" bei external_components (Version
2025.11.2) (Discussion #3423)
Datum: 03.12.2025, 10:02 Uhr
An: esphome/feature-requests ***@***.***
***@***.***> >
Cc: svenstoltebs38116-max ***@***.***
***@***.***> >, Author <
***@***.*** ***@***.***> >
You're doing something wrong then. You need to point to the repo, not an
archive zip file. But again, that repo doesn't even exist anyway.
—
Reply to this email directly, view it on GitHub
<#3423 (reply in thread)>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BX7K2ATC6ZLYVGQ2N365OBD372RITAVCNFSM6AAAAACN4MJY2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJUGYYDCMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
https://esphome.io/components/modbus_controller/#example-server |
Beta Was this translation helpful? Give feedback.
-
|
If you need more help, come ask on the esphome discord server. |
Beta Was this translation helpful? Give feedback.
-
|
hallo ich bin es noch einmal wegen dem Modbus server ich bekomme es einfach
nicht ans laufen.
das direkte laden der Custon Component über die url funktioniert nicht also
habe ich es lokal gemacht.
jetzt habe ich ein weiterse Problem was ich nicht gelöst bekomme.
ich gebe ihnen jetzt mal meine Configuration und den fehler dazu da ich es
nicht so gut erklären kann.
esphome:
name: co2sensor-rs485
friendly_name: Co2sensor_rs485
includes:
- modbus_server_custom.h
esp32:
board: esp32-c3-devkitm-1
framework:
type: esp-idf
logger:
#api:
#ota:
#wifi:
# ssid: !secret wifi_ssid
# password: !secret wifi_password
# 💡 HINWEIS: Wir verwenden eine externe Komponente, um den Modbus-Server
sofort zu aktivieren.
external_components:
- source:
type: local
# PFAD WIE ZUVOR KORRIGIERT: Muss zur Ordnerstruktur passen
path: custom_components/modbus
components:
- modbus_server
i2c:
id: bus_i2c_scd40
sda: GPIO5
scl: GPIO4
frequency: 50kHz
uart:
# 2. UART Bus für RS485
id: intmodbus # ID wie im Beispiel
tx_pin: GPIO21
rx_pin: GPIO20
baud_rate: 9600
data_bits: 8
parity: NONE
stop_bits: 1
sensor:
# 3. SCD4x Sensoren
- platform: scd4x
i2c_id: bus_i2c_scd40
automatic_self_calibration: true
update_interval: 5s
co2:
name: "CO2 Konzentration"
id: scd40_co2
temperature:
name: "Temperatur"
id: scd40_temperature
humidity:
name: "Luftfeuchtigkeit"
id: scd40_humidity
# 4. Modbus Server (Slave) Konfiguration
modbus_server:
uart_id: intmodbus
address: 1
holding_registers:
- start_address: 0
type: UWORD
component: scd40_co2
property: state
- start_address: 1
type: FLOAT
component: scd40_temperature
property: state
- start_address: 3
type: FLOAT
component: scd40_humidity
property: state
INFO ESPHome 2025.11.3 INFO Reading configuration
/config/esphome/co2sensor-rs485.yaml... Failed config modbus_server:
[source /config/esphome/co2sensor-rs485.yaml:61] - uart_id: intmodbus
address: 1 holding_registers: - start_address: 0 [type] is an invalid
option for [holding_registers]. Please check the indentation. type: UWORD
[component] is an invalid option for [holding_registers]. Please check the
indentation. component: scd40_co2 [property] is an invalid option for
[holding_registers]. Please check the indentation. property: state -
start_address: 1 type: FLOAT
ich hoffe das sie mir dabei helfen können ich weiß nähmlich wirklich nicht
weiter, ich habe es sogar schon mit Google Gemini probiert aber der sagt
auch immer das meine esphome version alt und nicht stabil ist ich habe aber
heute ein update auf die neuste version gemacht.
Vielen dank schonmal im voraus
Mfg
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Why are you still using an external component? esphome has modbus server suppport built-in now. |
Beta Was this translation helpful? Give feedback.
-
|
Because I'm apparently too stupid 🤣🤣🤣
Gesendet mit der Telekom Mail App
…-- Original-Nachricht --
Von: Samuel Sieb ***@***.***
***@***.***> >
Betreff: Re: [esphome/feature-requests] [BUG] YAML-Parser-Inkompatibilität:
Fehler "Shorthand only for strings" bei external_components (Version
2025.11.2) (Discussion #3423)
Datum: 04.12.2025, 19:44 Uhr
An: esphome/feature-requests ***@***.***
***@***.***> >
Cc: svenstoltebs38116-max ***@***.***
***@***.***> >, Author <
***@***.*** ***@***.***> >
Why are you still using an external component? esphome has modbus server
suppport built-in now.
—
Reply to this email directly, view it on GitHub
<#3423 (reply in thread)>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BX7K2AQAB6L63FNGZVZ3GU34AB6JBAVCNFSM6AAAAACN4MJY2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJWGQZTONQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Does this also work with esphome version 2025 11.3 or only with version
2025 12.0 dev?
Gesendet mit der Telekom Mail App
…-- Original-Nachricht --
Von: Samuel Sieb ***@***.***
***@***.***> >
Betreff: Re: [esphome/feature-requests] [BUG] YAML-Parser-Inkompatibilität:
Fehler "Shorthand only for strings" bei external_components (Version
2025.11.2) (Discussion #3423)
Datum: 04.12.2025, 19:44 Uhr
An: esphome/feature-requests ***@***.***
***@***.***> >
Cc: svenstoltebs38116-max ***@***.***
***@***.***> >, Author <
***@***.*** ***@***.***> >
Why are you still using an external component? esphome has modbus server
suppport built-in now.
—
Reply to this email directly, view it on GitHub
<#3423 (reply in thread)>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BX7K2AQAB6L63FNGZVZ3GU34AB6JBAVCNFSM6AAAAACN4MJY2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJWGQZTONQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
It has been available for a while. I gave you a link to the docs earlier. |
Beta Was this translation helpful? Give feedback.
-
|
OK, thank you very much
Gesendet mit der Telekom Mail App
…-- Original-Nachricht --
Von: Samuel Sieb ***@***.***
***@***.***> >
Betreff: Re: [esphome/feature-requests] [BUG] YAML-Parser-Inkompatibilität:
Fehler "Shorthand only for strings" bei external_components (Version
2025.11.2) (Discussion #3423)
Datum: 05.12.2025, 00:26 Uhr
An: esphome/feature-requests ***@***.***
***@***.***> >
Cc: svenstoltebs38116-max ***@***.***
***@***.***> >, Author <
***@***.*** ***@***.***> >
It has been available for a while. I gave you a link to the docs earlier.
—
Reply to this email directly, view it on GitHub
<#3423 (reply in thread)>
, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BX7K2AVB3QW6DZ46DJGSCQL4AC7JRAVCNFSM6AAAAACN4MJY2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJWGYZDOOI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I finally managed to get it compiled and installed. The only thing that
doesn't work now is the Wi-Fi connection. Could it be that the Modbus
operation is blocking the Wi-Fi? I tried to add an update interval to give
the ESP enough time to establish the Wi-Fi connection, but unfortunately,
that didn't work.
I have attached my YAML in the attachment without the update interval;
maybe you have some improvement ideas.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Sorry, that was the bin file, here is the correct YAML
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe your core improvement
Kernverbesserung: Behebung eines Fehlers im YAML-Parser, der das Laden von Custom Components über die erweiterte URL-Source-Syntax blockiert.
Dies soll die Kompatibilität von ESPHome-Installationen mit älteren/spezifischen Versionen (wie z.B. 2025.11.2) mit modernen, über URL geladenen Custom Components sicherstellen.
Current limitations
Problem: Beim Versuch, eine Custom Component über die erweiterte external_components Syntax zu laden, schlägt die Kompilierung fehl, da der YAML-Parser die verschachtelte source-Definition nicht korrekt interpretieren kann.
Dies betrifft kritische Komponenten wie modbus_server, die oft als Custom Component installiert werden müssen, da die native Core-Komponente in diesen Versionen nicht stabil ist.
Betroffene Version: 2025.11.2
Genaue Fehlermeldung:
Failed config external_components: [source /config/esphome/...] - Shorthand only for strings.
Technical benefits
Erhöhte Abwärtskompatibilität: Ermöglicht Benutzern, kritische Custom Components (wie z.B. Modbus-Server) auch in älteren oder spezifischen Add-on-Versionen zu installieren, ohne ein Update durchführen oder die Dateien manuell in das lokale Verzeichnis kopieren zu müssen.
Verbesserte Stabilität des Modbus-Slaves: Ermöglicht die korrekte Verwendung der Custom Component, was die Stabilität für komplexe Protokolle wie Modbus RTU verbessert, wo die native Core-Komponente oft nicht ausreichend ist.
Additional context
Minimal-YAML-Code, der den Fehler auslöst:
external_components:
type: url
url: https://github.com/glmnet/esphome-modbus-server/archive/refs/heads/main.zip
components: [ modbus_server ]
refresh: 0s
Beta Was this translation helpful? Give feedback.
All reactions