Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. [ESPHome] Beta release

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.2k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.2k

[ESPHome] Beta release

Geplant Angeheftet Gesperrt Verschoben Tester
591 Beiträge 48 Kommentatoren 156.0k Aufrufe 39 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • B bernd33-1

    @sborg Hi, ok... wie finde ich denn raus, welche Version aktuell bei mir installiert ist? Wenn ich das ESPHome Dashboard im IOBroker auf mach, steht da rechts unten v2021.8.2 . ISt das dann die Version, die ich aktuell habe?

    Und die Folgefrage wäre dann: Wie upgrade ich den ESPHome Adapter? Aktuell bietet der IOB kein Adapterupdate an und über "Beta" kommt auch kein Update?

    Danke schon mal und Grüße, Bernd

    SBorgS Offline
    SBorgS Offline
    SBorg
    Forum Testing Most Active
    schrieb am zuletzt editiert von
    #577

    @bernd33-1 sagte in [ESPHome] Beta release:

    ISt das dann die Version, die ich aktuell habe?

    Genau :)

    @bernd33-1 sagte in [ESPHome] Beta release:

    Wie upgrade ich den ESPHome Adapter?

    Adapter --> Expertenmodus einschalten --> Oktocat ("Katze" / "aus eigener URL installieren") --> "von GitHub" wählen --> bei der Adapterauswahl nun "ESPHome" auswählen --> freuen ;)

    LG SBorg ( SBorg auf GitHub)
    Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation

    B 1 Antwort Letzte Antwort
    0
    • SBorgS SBorg

      @bernd33-1 sagte in [ESPHome] Beta release:

      ISt das dann die Version, die ich aktuell habe?

      Genau :)

      @bernd33-1 sagte in [ESPHome] Beta release:

      Wie upgrade ich den ESPHome Adapter?

      Adapter --> Expertenmodus einschalten --> Oktocat ("Katze" / "aus eigener URL installieren") --> "von GitHub" wählen --> bei der Adapterauswahl nun "ESPHome" auswählen --> freuen ;)

      B Offline
      B Offline
      bernd33-1
      schrieb am zuletzt editiert von
      #578

      @sborg perfekt :-) ich musste aber vorher noch auf die Beta-Repositories umschalten. Sonst wurde mir der ESPHome Adapter nicht angezeigt. Dann einfach "drüber installieren" und nun seh ich 2022.2.6 im ESP-Dashboard.

      Dank dir und Grüße, Bernd

      1 Antwort Letzte Antwort
      0
      • W Offline
        W Offline
        wusa
        schrieb am zuletzt editiert von
        #579

        Ich versuche gerade auch den ESPHome Adapter zu installieren.
        Leider schaffe ich es nicht.
        Ich habe auf Beta umgeschaltet und der Adapter taucht auch auf.
        Aber bei der Installation bricht er mit folgenden Fehlern ab:

        host.iobroker
        2022-06-29 13:43:45.708	info	iobroker exit 25
        host.iobroker
        2022-06-29 13:43:44.612	error	iobroker host.iobroker Cannot install iobroker.esphome@0.2.4: 126
        host.iobroker
        2022-06-29 13:42:45.537	info	iobroker Installing iobroker.esphome@0.2.4... (System call)
        host.iobroker
        2022-06-29 13:42:45.527	info	iobroker NPM version: 8.11.0
        host.iobroker
        2022-06-29 13:42:27.858	info	iobroker add esphome auto --host iobroker
        

        Kann mir hier jemand helfen?

        Danke

        1 Antwort Letzte Antwort
        0
        • B Offline
          B Offline
          bernd33-1
          schrieb am zuletzt editiert von
          #580

          Hi zusammen,

          wenn ich mit ESPHome auf meinem ESP8266 eine PWM ausgebe, dann hat das PWM-Signal nur eine Auflösung von 8 Bit (0-255). Weis jemand wie man das auf die vollen 10 Bit umstellen kann?

          Thx und Grüße, Bernd

          draexlerD 1 Antwort Letzte Antwort
          0
          • B bernd33-1

            Hi zusammen,

            wenn ich mit ESPHome auf meinem ESP8266 eine PWM ausgebe, dann hat das PWM-Signal nur eine Auflösung von 8 Bit (0-255). Weis jemand wie man das auf die vollen 10 Bit umstellen kann?

            Thx und Grüße, Bernd

            draexlerD Nicht stören
            draexlerD Nicht stören
            draexler
            schrieb am zuletzt editiert von draexler
            #581

            Hi Zusammen,

            an die E Paper Spezialisten oder die welche sich mich den GPIO auskennen ;-)
            Ich will ein Waveshare 7.5 V2 ePaper mit einen Firebeetle ESP32 verbinden.
            Ich bekomme keine Anzeige hin. Denke aber das ich an den GPIO/PIN Einstellungen scheitere....

            Das ist die YAML Einstellung:

            spi:
              clk_pin: GPIO18
              mosi_pin: GPIO23
             
            display:
              - platform: waveshare_epaper
                cs_pin: GPIO09
                dc_pin: GPIO22
                busy_pin: GPIO27
                reset_pin: GPIO21
                model: 7.50inv2
                update_interval
            

            Das ist das PIN Shema vom Firebird:
            https://wiki.dfrobot.com/FireBeetle_ESP32_IOT_Microcontroller(V3.0)__Supports_Wi-Fi_&_Bluetooth__SKU__DFR0478#target_7
            Bildschirmfoto 2022-07-08 um 13.55.36.png

            und das die von Waveshare ePaper HAT: (Hier gilt nur die Linke Spalte wegen der Bezeichnungen)
            Bildschirmfoto 2022-07-08 um 13.56.38.png

            Was muss ich jetzt in der YAML eintragen? Ich kriege es nicht gebacken....

            Zusammengesteckt sieht es so aus:
            Bildschirmfoto 2022-07-08 um 18.44.57.png

            Danke euch :-)

            EDIT: Was ich anschließen kann, ist das das ePaper defekt ist. Habe es gerade mit einen anderen ESP getestet.

            draexlerD 1 Antwort Letzte Antwort
            0
            • draexlerD draexler

              Hi Zusammen,

              an die E Paper Spezialisten oder die welche sich mich den GPIO auskennen ;-)
              Ich will ein Waveshare 7.5 V2 ePaper mit einen Firebeetle ESP32 verbinden.
              Ich bekomme keine Anzeige hin. Denke aber das ich an den GPIO/PIN Einstellungen scheitere....

              Das ist die YAML Einstellung:

              spi:
                clk_pin: GPIO18
                mosi_pin: GPIO23
               
              display:
                - platform: waveshare_epaper
                  cs_pin: GPIO09
                  dc_pin: GPIO22
                  busy_pin: GPIO27
                  reset_pin: GPIO21
                  model: 7.50inv2
                  update_interval
              

              Das ist das PIN Shema vom Firebird:
              https://wiki.dfrobot.com/FireBeetle_ESP32_IOT_Microcontroller(V3.0)__Supports_Wi-Fi_&_Bluetooth__SKU__DFR0478#target_7
              Bildschirmfoto 2022-07-08 um 13.55.36.png

              und das die von Waveshare ePaper HAT: (Hier gilt nur die Linke Spalte wegen der Bezeichnungen)
              Bildschirmfoto 2022-07-08 um 13.56.38.png

              Was muss ich jetzt in der YAML eintragen? Ich kriege es nicht gebacken....

              Zusammengesteckt sieht es so aus:
              Bildschirmfoto 2022-07-08 um 18.44.57.png

              Danke euch :-)

              EDIT: Was ich anschließen kann, ist das das ePaper defekt ist. Habe es gerade mit einen anderen ESP getestet.

              draexlerD Nicht stören
              draexlerD Nicht stören
              draexler
              schrieb am zuletzt editiert von
              #582

              Das wäre jetzt mal das "very verbose" Log.

              ich lese zuminestet mal raus das das epaper nicht antwortet?!?

              [12:00:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=139796 (now=149803)
              [12:00:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:00:35][V][component:200]: Components should block for at most 20-30ms.
              [12:00:36][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:00:36][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:00:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=96428 (now=156428)
              [12:00:41][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:00:41][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:00:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=149796 (now=159796)
              [12:00:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:00:45][V][component:200]: Components should block for at most 20-30ms.
              [12:00:46][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:00:46][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:00:51][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:00:51][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:00:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=159796 (now=169796)
              [12:00:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:00:55][V][component:200]: Components should block for at most 20-30ms.
              [12:00:56][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:00:56][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:01][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:01][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=169796 (now=179796)
              [12:01:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:01:05][V][component:200]: Components should block for at most 20-30ms.
              [12:01:07][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:07][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:11][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:11][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=179796 (now=189796)
              [12:01:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:01:15][V][component:200]: Components should block for at most 20-30ms.
              [12:01:16][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:16][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:22][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:22][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=189796 (now=199796)
              [12:01:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:01:25][V][component:200]: Components should block for at most 20-30ms.
              [12:01:27][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:27][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:32][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:32][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=199796 (now=209800)
              [12:01:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:01:35][V][component:200]: Components should block for at most 20-30ms.
              [12:01:37][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:37][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=156428 (now=216432)
              [12:01:42][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:42][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=209796 (now=219796)
              [12:01:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:01:45][V][component:200]: Components should block for at most 20-30ms.
              [12:01:47][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:47][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:52][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:52][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:01:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=219796 (now=229800)
              [12:01:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:01:55][V][component:200]: Components should block for at most 20-30ms.
              [12:01:57][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:01:57][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:02][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:02][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=229796 (now=239796)
              [12:02:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:02:05][V][component:200]: Components should block for at most 20-30ms.
              [12:02:07][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:07][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:12][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:12][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=239796 (now=249796)
              [12:02:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:02:15][V][component:200]: Components should block for at most 20-30ms.
              [12:02:17][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:17][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:22][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:22][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=249796 (now=259796)
              [12:02:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:02:25][V][component:200]: Components should block for at most 20-30ms.
              [12:02:27][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:27][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:32][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:32][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=259796 (now=269796)
              [12:02:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:02:35][V][component:200]: Components should block for at most 20-30ms.
              [12:02:37][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:37][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=216428 (now=276432)
              [12:02:42][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:42][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=269796 (now=279796)
              [12:02:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:02:45][V][component:200]: Components should block for at most 20-30ms.
              [12:02:47][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:47][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:52][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:52][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:02:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=279796 (now=289798)
              [12:02:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:02:55][V][component:200]: Components should block for at most 20-30ms.
              [12:02:57][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:02:57][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:03][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:03][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=289796 (now=299797)
              [12:03:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:03:05][V][component:200]: Components should block for at most 20-30ms.
              [12:03:05][I][ota:105]: Boot seems successful, resetting boot loop counter.
              [12:03:05][D][esp32.preferences:114]: Saving preferences to flash...
              [12:03:07][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:07][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:12][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:12][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=299796 (now=309804)
              [12:03:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:03:15][V][component:200]: Components should block for at most 20-30ms.
              [12:03:18][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:18][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:23][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:23][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=309796 (now=319797)
              [12:03:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:03:25][V][component:200]: Components should block for at most 20-30ms.
              [12:03:27][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:27][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:33][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:33][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=319796 (now=329801)
              [12:03:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:03:35][V][component:200]: Components should block for at most 20-30ms.
              [12:03:38][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:38][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=276428 (now=336431)
              [12:03:42][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:42][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=329796 (now=339804)
              [12:03:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:03:45][V][component:200]: Components should block for at most 20-30ms.
              [12:03:48][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:48][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:53][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:53][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:03:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=339796 (now=349803)
              [12:03:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:03:55][V][component:200]: Components should block for at most 20-30ms.
              [12:03:58][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:03:58][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:03][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:03][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=349796 (now=359796)
              [12:04:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:04:05][V][component:200]: Components should block for at most 20-30ms.
              [12:04:08][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:08][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:13][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:13][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=359796 (now=369796)
              [12:04:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:04:15][V][component:200]: Components should block for at most 20-30ms.
              [12:04:18][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:18][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:23][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:23][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=369796 (now=379796)
              [12:04:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:04:25][V][component:200]: Components should block for at most 20-30ms.
              [12:04:28][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:28][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:33][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:33][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=379796 (now=389796)
              [12:04:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:04:35][V][component:200]: Components should block for at most 20-30ms.
              [12:04:38][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:38][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=336428 (now=396429)
              [12:04:43][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:43][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=389796 (now=399801)
              [12:04:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:04:45][V][component:200]: Components should block for at most 20-30ms.
              [12:04:48][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:48][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:54][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:54][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:04:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=399796 (now=409796)
              [12:04:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:04:55][V][component:200]: Components should block for at most 20-30ms.
              [12:04:58][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:04:58][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=409796 (now=419803)
              [12:05:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:05:05][V][component:200]: Components should block for at most 20-30ms.
              [12:05:05][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:05][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:09][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:09][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:13][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:13][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=419796 (now=429796)
              [12:05:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:05:15][V][component:200]: Components should block for at most 20-30ms.
              [12:05:20][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:20][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=429796 (now=439796)
              [12:05:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:05:25][V][component:200]: Components should block for at most 20-30ms.
              [12:05:25][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:25][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:28][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:29][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=439796 (now=449803)
              [12:05:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:05:35][V][component:200]: Components should block for at most 20-30ms.
              [12:05:35][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:35][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=396428 (now=456428)
              [12:05:40][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:40][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=449796 (now=459799)
              [12:05:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:05:45][V][component:200]: Components should block for at most 20-30ms.
              [12:05:45][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:45][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:51][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:51][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:05:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=459796 (now=469796)
              [12:05:55][V][text_sensor:016]: 'WindRichtungAussen': Received new state SSW
              [12:05:55][D][text_sensor:067]: 'WindRichtungAussen': Sending state 'SSW'
              [12:05:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:05:55][V][component:200]: Components should block for at most 20-30ms.
              [12:05:55][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:05:55][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:00][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:00][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:01][VV][scheduler:186]: Running interval 'update' with interval=900000 last_execution=4294544578 (now=477282)
              [12:06:01][D][sntp:075]: Synchronized time: 2022-07-09 12:06:01
              [12:06:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=469796 (now=479796)
              [12:06:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:06:05][V][component:200]: Components should block for at most 20-30ms.
              [12:06:06][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:06][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:11][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:11][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=479796 (now=489796)
              [12:06:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:06:15][V][component:200]: Components should block for at most 20-30ms.
              [12:06:15][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:15][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:21][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:21][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=489796 (now=499799)
              [12:06:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:06:25][V][component:200]: Components should block for at most 20-30ms.
              [12:06:26][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:26][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:31][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:31][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=499796 (now=509799)
              [12:06:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:06:35][V][component:200]: Components should block for at most 20-30ms.
              [12:06:36][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:36][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:40][V][text_sensor:016]: 'TemperaturAussen': Received new state 21.2° C
              [12:06:40][D][text_sensor:067]: 'TemperaturAussen': Sending state '21.2° C'
              [12:06:40][V][text_sensor:016]: 'LuftfeuchtigkeitAussen': Received new state 58%
              [12:06:40][D][text_sensor:067]: 'LuftfeuchtigkeitAussen': Sending state '58%'
              [12:06:40][V][text_sensor:016]: 'MaxTemperaturAussen': Received new state 21.2°
              [12:06:40][D][text_sensor:067]: 'MaxTemperaturAussen': Sending state '21.2°'
              [12:06:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=456428 (now=516432)
              [12:06:41][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:41][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=509796 (now=519796)
              [12:06:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:06:45][V][component:200]: Components should block for at most 20-30ms.
              [12:06:46][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:46][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:51][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:51][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:06:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=519796 (now=529802)
              [12:06:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:06:55][V][component:200]: Components should block for at most 20-30ms.
              [12:06:56][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:06:56][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:01][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:01][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=529796 (now=539801)
              [12:07:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:07:05][V][component:200]: Components should block for at most 20-30ms.
              [12:07:06][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:06][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:11][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:11][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=539796 (now=549803)
              [12:07:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:07:15][V][component:200]: Components should block for at most 20-30ms.
              [12:07:16][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:16][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:21][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:21][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=549796 (now=559796)
              [12:07:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:07:25][V][component:200]: Components should block for at most 20-30ms.
              [12:07:26][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:26][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:31][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:31][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=559796 (now=569796)
              [12:07:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:07:35][V][component:200]: Components should block for at most 20-30ms.
              [12:07:37][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:37][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=516428 (now=576428)
              [12:07:41][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:41][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=569796 (now=579803)
              [12:07:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:07:45][V][component:200]: Components should block for at most 20-30ms.
              [12:07:46][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:46][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:52][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:52][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:07:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=579796 (now=589803)
              [12:07:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:07:55][V][component:200]: Components should block for at most 20-30ms.
              [12:07:57][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:07:57][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:01][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:01][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=589796 (now=599796)
              [12:08:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:08:05][V][component:200]: Components should block for at most 20-30ms.
              [12:08:07][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:07][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:12][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:12][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=599796 (now=609800)
              [12:08:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:08:15][V][component:200]: Components should block for at most 20-30ms.
              [12:08:16][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:16][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:22][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:22][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=609796 (now=619796)
              [12:08:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:08:25][V][component:200]: Components should block for at most 20-30ms.
              [12:08:27][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:27][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:31][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:31][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=619796 (now=629796)
              [12:08:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:08:35][V][component:200]: Components should block for at most 20-30ms.
              [12:08:37][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:37][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=576428 (now=636428)
              [12:08:42][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:42][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=629796 (now=639798)
              [12:08:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:08:45][V][component:200]: Components should block for at most 20-30ms.
              [12:08:47][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:47][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:52][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:52][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:08:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=639796 (now=649798)
              [12:08:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:08:55][V][component:200]: Components should block for at most 20-30ms.
              [12:08:57][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:08:57][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:02][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:02][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=649796 (now=659796)
              [12:09:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:09:05][V][component:200]: Components should block for at most 20-30ms.
              [12:09:07][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:07][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:12][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:12][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=659796 (now=669796)
              [12:09:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:09:15][V][component:200]: Components should block for at most 20-30ms.
              [12:09:17][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:17][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:22][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:22][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:24][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=669796 (now=679796)
              [12:09:25][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:09:25][V][component:200]: Components should block for at most 20-30ms.
              [12:09:27][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:27][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:32][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:32][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:34][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=679796 (now=689799)
              [12:09:35][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:09:35][V][component:200]: Components should block for at most 20-30ms.
              [12:09:37][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:37][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:40][VV][scheduler:186]: Running interval '' with interval=60000 last_execution=636428 (now=696428)
              [12:09:42][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:43][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:44][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=689796 (now=699799)
              [12:09:45][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:09:45][V][component:200]: Components should block for at most 20-30ms.
              [12:09:47][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:47][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:53][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:53][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:09:54][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=699796 (now=709797)
              [12:09:55][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:09:55][V][component:200]: Components should block for at most 20-30ms.
              [12:09:58][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:09:58][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:10:00][V][text_sensor:016]: 'MaxTempMorgen': Received new state 20°
              [12:10:00][D][text_sensor:067]: 'MaxTempMorgen': Sending state '20°'
              [12:10:00][V][text_sensor:016]: 'MinTempMorgen': Received new state 14°
              [12:10:00][D][text_sensor:067]: 'MinTempMorgen': Sending state '14°'
              [12:10:00][V][text_sensor:016]: 'MinTempUEbermorgen': Received new state 13°
              [12:10:00][D][text_sensor:067]: 'MinTempUEbermorgen': Sending state '13°'
              [12:10:00][V][text_sensor:016]: 'MaxTempUEberUebermorgen': Received new state 24°
              [12:10:00][D][text_sensor:067]: 'MaxTempUEberUebermorgen': Sending state '24°'
              [12:10:00][V][text_sensor:016]: 'WettersymbolUEberUebermorgen': Received new state 2
              [12:10:00][D][text_sensor:067]: 'WettersymbolUEberUebermorgen': Sending state '2'
              [12:10:02][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:10:02][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:10:04][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=709796 (now=719800)
              [12:10:05][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:10:05][V][component:200]: Components should block for at most 20-30ms.
              [12:10:08][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:10:08][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:10:13][VV][api.service:355]: on_ping_request: PingRequest {}
              [12:10:13][VV][api.service:043]: send_ping_response: PingResponse {}
              [12:10:14][VV][scheduler:186]: Running interval 'update' with interval=10000 last_execution=719796 (now=729804)
              [12:10:15][V][component:199]: Component waveshare_epaper.display took a long time for an operation (1.60 s).
              [12:10:15][V][component:200]: Components should block for at most 20-30ms.
              
              1 Antwort Letzte Antwort
              0
              • Y Offline
                Y Offline
                Yoshi
                schrieb am zuletzt editiert von Yoshi
                #583
                INFO Reading configuration /opt/iobroker/iobroker-data/esphome.0/test.yaml...
                Failed config
                
                web_server: [source /opt/iobroker/iobroker-data/esphome.0/test.yaml:31]
                  port: 80
                  
                  [version] is an invalid option for [web_server]. Please check the indentation.
                  version: 2 [source /opt/iobroker/iobroker-data/esphome.0/test.yaml:32]
                  include_internal: True
                
                

                So langsam dreh ich durch :-)
                Ich bekomme den ESP nicht angebunden. Ich bin ratlos.
                Auf dem MAc bekomme ich das irgendwie hin...aber ich bekomme ihn nicht im iobroker angebunden

                1 Antwort Letzte Antwort
                0
                • F Offline
                  F Offline
                  Fox1985
                  schrieb am zuletzt editiert von
                  #584

                  Guten Morgen,
                  ich wollte nun auch den Adapter installieren.
                  Leider bekomme ich aber immder die folgende Fehlermeldung. Kann mir jemand da helfen?
                  Viele Grüße
                  Stefan

                  $ iobroker url DrozmotiX/ioBroker.esphome --host iobroker-pi --debug
                  
                  NPM version: 8.19.2Installing DrozmotiX/ioBroker.esphome... (System call)
                  
                  npm ERR! code 1
                  
                  npm ERR! Installing build dependencies: startednpm ERR! Installing build dependencies: finished with status 'done'npm ERR! Getting requirements to build wheel: startednpm ERR! Getting requirements to build wheel: finished with status 'done'npm ERR! Preparing metadata (pyproject.toml): startednpm ERR! Preparing metadata (pyproject.toml): finished with status 'done'npm ERR! Collecting esphome-dashboard==20220209.0npm ERR! Using cached esphome_dashboard-20220209.0-py3-none-any.whl (592 kB)npm ERR! Collecting esptool==3.2npm ERR! Using cached esptool-3.2.tar.gz (206 kB)npm ERR! Preparing metadata (setup.py): startednpm ERR! Preparing metadata (setup.py): finished with status 'done'npm ERR! Collecting kconfiglib==13.7.1npm ERR! Using cached kconfiglib-13.7.1-py2.py3-none-any.whl (145 kB)npm ERR! Collecting paho-mqtt==1.6.1npm ERR! Using cached paho-mqtt-1.6.1.tar.gz (99 kB)npm ERR! Preparing metadata (setup.py): startednpm ERR! Preparing metadata (setup.py): finished with status 'done'npm ERR! Collecting platformio==5.2.5npm ERR! Using cached platformio-5.2.5.tar.gz (218 kB)npm ERR! Preparing metadata (setup.py): startednpm ERR! Preparing metadata (setup.py): finished with status 'done'npm ERR! Collecting zeroconf==0.38.3npm ERR! Using cached zeroconf-0.38.3-py3-none-any.whl (106 kB)npm ERR! Collecting tzdata>=2021.1npm ERR! Using cached tzdata-2022.7-py2.py3-none-any.whl (340 kB)npm ERR! Collecting PyYAML==6.0npm ERR! Using cached PyYAML-6.0.tar.gz (124 kB)npm ERR! Installing build dependencies: startednpm ERR! Installing build dependencies: finished with status 'done'npm ERR! Getting requirements to build wheel: startednpm ERR! Getting requirements to build wheel: finished with status 'done'npm ERR! Preparing metadata (pyproject.toml): startednpm ERR! Preparing metadata (pyproject.toml): finished with status 'done'npm ERR! Collecting colorama==0.4.4npm ERR! Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)npm ERR! Collecting tornado>=3.2npm ERR! Using cached tornado-6.1.tar.gz (497 kB)npm ERR! Preparing metadata (setup.py): startednpm ERR! Preparing metadata (setup.py): finished with status 'done'npm ERR! Collecting aioesphomeapi==10.8.2npm ERR! Using cached aioesphomeapi-10.8.2-py2.py3-none-any.whl (49 kB)npm ERR! Collecting tzlocal==4.1npm ERR! Using cached tzlocal-4.1-py3-none-any.whl (19 kB)npm ERR! Collecting voluptuous==0.12.2npm ERR! Using cached voluptuous-0.12.2.tar.gz (48 kB)npm ERR! Preparing metadata (setup.py): startednpm ERR! Preparing metadata (setup.py): finished with status 'done'npm ERR! Collecting pyserial==3.5npm ERR! Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)npm ERR! Collecting click==8.0.3npm ERR! Using cached click-8.0.3-py3-none-any.whl (97 kB)npm ERR! Collecting protobuf<4.0,>=3.12.2npm ERR! Using cached protobuf-3.20.3-py2.py3-none-any.whl (162 kB)npm ERR! Collecting noiseprotocol<1.0,>=0.3.1npm ERR! Using cached noiseprotocol-0.3.1-py3-none-any.whl (20 kB)npm ERR! Collecting importlib-metadatanpm ERR! Using cached importlib_metadata-6.0.0-py3-none-any.whl (21 kB)npm ERR! Collecting bitstring>=3.1.6npm ERR! Using cached bitstring-4.0.1-py3-none-any.whl (45 kB)npm ERR! Collecting cryptography>=2.1.4npm ERR! Using cached cryptography-39.0.2.tar.gz (604 kB)npm ERR! Installing build dependencies: startednpm ERR! Installing build dependencies: finished with status 'error'npm ERR! npm WARN using --force Recommended protections disabled.npm ERR! npm WARN old lockfile npm ERR! npm WARN old lockfile The package-lock.json file was created with an old version of npm,npm ERR! npm WARN old lockfile so supplemental metadata must be fetched from the registry.npm ERR! npm WARN old lockfile npm ERR! npm WARN old lockfile This is a one-time fix-up, please be patient...npm ERR! npm WARN old lockfile npm ERR! npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecatednpm ERR! npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecatednpm ERR! npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecatednpm ERR! npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecatednpm ERR! npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependenciesnpm ERR! Cache entry deserialization failed, entry ignorednpm ERR! Cache entry deserialization failed, entry ignored
                  
                  host.iobroker-pi Cannot install DrozmotiX/ioBroker.esphome: 1
                  
                  ERROR: Process exited with code 25
                  
                  1 Antwort Letzte Antwort
                  0
                  • J Offline
                    J Offline
                    Jacke
                    schrieb am zuletzt editiert von
                    #585

                    Hallo ich bin nach Tasmota auf ESP Home gestoßen und finde es super sensoren auslesen klappt Problemlos.
                    Leider bekomme ich immer diesen Fehler

                    ESPHome client 192.168.1.121 TypeError: Cannot read properties of undefined (reading 'deserializeBinary')
                    

                    Meine grund yaml funktioniert ohne Probleme erst wenn ich diese abschnitte hinzufüge kommt der Fehler

                    globals:
                      - id: bbq_desired_temp
                        type: int
                        initial_value: "0"
                    
                      - id: bbq_tol
                        type: int
                        initial_value: "0"
                    
                    number:
                      - platform: template
                        name: "BBQ_Toleranz"
                        id: "bbq_tol_slider"
                        optimistic: true
                        min_value: 0
                        initial_value: 0
                        max_value: 10
                        step: 1
                        set_action:
                          then:
                            - lambda: id(bbq_tol) = x;
                    
                      - platform: template
                        name: "BBQ Desired Temp"
                        id: "bbq_temp_slider"
                        step: 1
                        min_value: 0
                        max_value: 250
                        mode: slider
                        optimistic: true
                        unit_of_measurement: "°C"
                        set_action:
                          then:
                            - lambda: id(bbq_desired_temp) = x;
                            #((x/5)-20)+100
                    
                    binary_sensor:
                      - platform: template
                        name: "Grill Temperatur"
                        lambda: |-
                          if ((id(grill_temp).state > id(bbq_desired_temp)-id(bbq_tol)) && (id(grill_temp).state < id(bbq_desired_temp)+ id(bbq_tol)) ) {
                            // Temperatur erreicht
                            return true;
                          } else {
                            // Temperatur ausserhalb des Bereichs
                            return false;
                          }
                    

                    Hier soll ein Temperatur Bereich erfasst werden welcher über einen SLider einstellbar ist.
                    Das funktioniert auch in der weboberfläche.
                    Aber er verbindet sich nicht mit dem IoBroker.
                    Hier ist der komplette code

                    globals:
                      - id: bbq_desired_temp
                        type: int
                        initial_value: "0"
                    
                      - id: bbq_tol
                        type: int
                        initial_value: "0"
                    
                    number:
                      - platform: template
                        name: "BBQ_Toleranz"
                        id: "bbq_tol_slider"
                        optimistic: true
                        min_value: 0
                        initial_value: 0
                        max_value: 10
                        step: 1
                        set_action:
                          then:
                            - lambda: id(bbq_tol) = x;
                    
                      - platform: template
                        name: "BBQ Desired Temp"
                        id: "bbq_temp_slider"
                        step: 1
                        min_value: 0
                        max_value: 250
                        mode: slider
                        optimistic: true
                        unit_of_measurement: "°C"
                        set_action:
                          then:
                            - lambda: id(bbq_desired_temp) = x;
                            #((x/5)-20)+100
                    
                    binary_sensor:
                      - platform: template
                        name: "Grill Temperatur"
                        lambda: |-
                          if ((id(grill_temp).state > id(bbq_desired_temp)-id(bbq_tol)) && (id(grill_temp).state < id(bbq_desired_temp)+ id(bbq_tol)) ) {
                            // Temperatur erreicht
                            return true;
                          } else {
                            // Temperatur ausserhalb des Bereichs
                            return false;
                          }
                    
                    
                    spi:
                      miso_pin: GPIO12
                      clk_pin: GPIO14
                    
                    sensor:
                      - platform: max6675
                        name: "Grill Temp"
                        id: grill_temp
                        cs_pin: GPIO15
                        update_interval: 30s
                      
                      - platform: ntc
                        sensor: resistance_sensor
                        calibration:
                         # b_constant: 3893.80906
                         # reference_temperature: 23.5°C
                         # reference_resistance: 105.1kOhm
                          - 104.500kOhm -> 23.7°C
                          - 48.600kOhm -> 41.5°C
                          - 9.500kOhm -> 88°C
                        name: NTC Temperature
                    
                      # Example source sensors:
                      - platform: resistance
                        id: resistance_sensor
                        sensor: source_sensor
                        configuration: UPSTREAM
                        resistor: 98.0kOhm
                        reference_voltage:  3.3V
                        name: Resistance Sensor
                      - platform: adc
                        id: source_sensor
                        filters:
                          #-  offset:  0.035
                          -  multiply: 3.3
                        pin: A0
                        update_interval: never
                    
                    switch:
                      - platform: gpio
                        pin: 16
                        name: NTC Spannung
                        id: ntc_vcc
                    
                    interval:
                      - interval: 10s
                        then:
                          - switch.turn_on: ntc_vcc
                          - component.update: source_sensor
                          - switch.turn_off: ntc_vcc
                    
                    

                    Hat jemand eine Idee?

                    ZarelloZ 1 Antwort Letzte Antwort
                    1
                    • J Jacke

                      Hallo ich bin nach Tasmota auf ESP Home gestoßen und finde es super sensoren auslesen klappt Problemlos.
                      Leider bekomme ich immer diesen Fehler

                      ESPHome client 192.168.1.121 TypeError: Cannot read properties of undefined (reading 'deserializeBinary')
                      

                      Meine grund yaml funktioniert ohne Probleme erst wenn ich diese abschnitte hinzufüge kommt der Fehler

                      globals:
                        - id: bbq_desired_temp
                          type: int
                          initial_value: "0"
                      
                        - id: bbq_tol
                          type: int
                          initial_value: "0"
                      
                      number:
                        - platform: template
                          name: "BBQ_Toleranz"
                          id: "bbq_tol_slider"
                          optimistic: true
                          min_value: 0
                          initial_value: 0
                          max_value: 10
                          step: 1
                          set_action:
                            then:
                              - lambda: id(bbq_tol) = x;
                      
                        - platform: template
                          name: "BBQ Desired Temp"
                          id: "bbq_temp_slider"
                          step: 1
                          min_value: 0
                          max_value: 250
                          mode: slider
                          optimistic: true
                          unit_of_measurement: "°C"
                          set_action:
                            then:
                              - lambda: id(bbq_desired_temp) = x;
                              #((x/5)-20)+100
                      
                      binary_sensor:
                        - platform: template
                          name: "Grill Temperatur"
                          lambda: |-
                            if ((id(grill_temp).state > id(bbq_desired_temp)-id(bbq_tol)) && (id(grill_temp).state < id(bbq_desired_temp)+ id(bbq_tol)) ) {
                              // Temperatur erreicht
                              return true;
                            } else {
                              // Temperatur ausserhalb des Bereichs
                              return false;
                            }
                      

                      Hier soll ein Temperatur Bereich erfasst werden welcher über einen SLider einstellbar ist.
                      Das funktioniert auch in der weboberfläche.
                      Aber er verbindet sich nicht mit dem IoBroker.
                      Hier ist der komplette code

                      globals:
                        - id: bbq_desired_temp
                          type: int
                          initial_value: "0"
                      
                        - id: bbq_tol
                          type: int
                          initial_value: "0"
                      
                      number:
                        - platform: template
                          name: "BBQ_Toleranz"
                          id: "bbq_tol_slider"
                          optimistic: true
                          min_value: 0
                          initial_value: 0
                          max_value: 10
                          step: 1
                          set_action:
                            then:
                              - lambda: id(bbq_tol) = x;
                      
                        - platform: template
                          name: "BBQ Desired Temp"
                          id: "bbq_temp_slider"
                          step: 1
                          min_value: 0
                          max_value: 250
                          mode: slider
                          optimistic: true
                          unit_of_measurement: "°C"
                          set_action:
                            then:
                              - lambda: id(bbq_desired_temp) = x;
                              #((x/5)-20)+100
                      
                      binary_sensor:
                        - platform: template
                          name: "Grill Temperatur"
                          lambda: |-
                            if ((id(grill_temp).state > id(bbq_desired_temp)-id(bbq_tol)) && (id(grill_temp).state < id(bbq_desired_temp)+ id(bbq_tol)) ) {
                              // Temperatur erreicht
                              return true;
                            } else {
                              // Temperatur ausserhalb des Bereichs
                              return false;
                            }
                      
                      
                      spi:
                        miso_pin: GPIO12
                        clk_pin: GPIO14
                      
                      sensor:
                        - platform: max6675
                          name: "Grill Temp"
                          id: grill_temp
                          cs_pin: GPIO15
                          update_interval: 30s
                        
                        - platform: ntc
                          sensor: resistance_sensor
                          calibration:
                           # b_constant: 3893.80906
                           # reference_temperature: 23.5°C
                           # reference_resistance: 105.1kOhm
                            - 104.500kOhm -> 23.7°C
                            - 48.600kOhm -> 41.5°C
                            - 9.500kOhm -> 88°C
                          name: NTC Temperature
                      
                        # Example source sensors:
                        - platform: resistance
                          id: resistance_sensor
                          sensor: source_sensor
                          configuration: UPSTREAM
                          resistor: 98.0kOhm
                          reference_voltage:  3.3V
                          name: Resistance Sensor
                        - platform: adc
                          id: source_sensor
                          filters:
                            #-  offset:  0.035
                            -  multiply: 3.3
                          pin: A0
                          update_interval: never
                      
                      switch:
                        - platform: gpio
                          pin: 16
                          name: NTC Spannung
                          id: ntc_vcc
                      
                      interval:
                        - interval: 10s
                          then:
                            - switch.turn_on: ntc_vcc
                            - component.update: source_sensor
                            - switch.turn_off: ntc_vcc
                      
                      

                      Hat jemand eine Idee?

                      ZarelloZ Offline
                      ZarelloZ Offline
                      Zarello
                      schrieb am zuletzt editiert von
                      #586

                      @jacke Siehe die unterstützen Sensoren im ersten Post.
                      Leider wird number zur Zeit noch nicht unterstützt. Möchte man das verwenden geht das leider nur über MQTT.

                      1 Antwort Letzte Antwort
                      0
                      • C Offline
                        C Offline
                        ChrisXY
                        schrieb am zuletzt editiert von
                        #587

                        Hey ich habe mein OTA passwort wohl im esphome Admin adapter hinterlegt.. die config ist aber weg. Wie komme ich an das passwort also die Sternchen ? Gibt es da eine möglichkeit @Dutchman Danke

                        1 Antwort Letzte Antwort
                        0
                        • X Offline
                          X Offline
                          x-traxion
                          schrieb am zuletzt editiert von x-traxion
                          #588

                          ich stehe gerade etwas auf dem Schlauch.
                          Ich habe hier ein Node mit einem Display. Das funktioniert auch wunderbar.

                          Jetzt würde ich mir nur gerne Werte bzw. Text von einem anderen Node bzw. Texte/Werte aus dem iobroker raus anzeigen lassen.

                          zB will ich die Temps von einem anderen Node auf das Display bringen, die Windgeschwindigkeit die ich über KNX im ioBroker habe oder welche Person von meinem AI Server auf den Kameras erkannt wurde.
                          Heißt ich benötige diverse (Text)Sensoren die ich auch beschreiben kann.
                          Ich hab die Dokumentation schon rauf und runter gelesen, bekomme es aber nicht hin. text sensor, sensor, platform: homeassistant usw. alles von versucht. Entweder wird mir der Sensor erst gar nicht im iobroker angezeigt, oder er ist nicht schreibbar. Selbst wenn ich write händisch auf true setze.

                          Hat mir hier wer n Tip mit welchem Sensortyp ich das hin bekomme und hätte mir beispielzeilen?

                          EDIT: mit MQTT geht es wie gewünscht mit folgenden Zeilen:

                          • platform: mqtt_subscribe
                            name: "Status KameraServer"
                            id: Blueiris
                            topic: BlueIris/status

                          würde das aber gerne über die API machen :/

                          ZarelloZ 1 Antwort Letzte Antwort
                          0
                          • X x-traxion

                            ich stehe gerade etwas auf dem Schlauch.
                            Ich habe hier ein Node mit einem Display. Das funktioniert auch wunderbar.

                            Jetzt würde ich mir nur gerne Werte bzw. Text von einem anderen Node bzw. Texte/Werte aus dem iobroker raus anzeigen lassen.

                            zB will ich die Temps von einem anderen Node auf das Display bringen, die Windgeschwindigkeit die ich über KNX im ioBroker habe oder welche Person von meinem AI Server auf den Kameras erkannt wurde.
                            Heißt ich benötige diverse (Text)Sensoren die ich auch beschreiben kann.
                            Ich hab die Dokumentation schon rauf und runter gelesen, bekomme es aber nicht hin. text sensor, sensor, platform: homeassistant usw. alles von versucht. Entweder wird mir der Sensor erst gar nicht im iobroker angezeigt, oder er ist nicht schreibbar. Selbst wenn ich write händisch auf true setze.

                            Hat mir hier wer n Tip mit welchem Sensortyp ich das hin bekomme und hätte mir beispielzeilen?

                            EDIT: mit MQTT geht es wie gewünscht mit folgenden Zeilen:

                            • platform: mqtt_subscribe
                              name: "Status KameraServer"
                              id: Blueiris
                              topic: BlueIris/status

                            würde das aber gerne über die API machen :/

                            ZarelloZ Offline
                            ZarelloZ Offline
                            Zarello
                            schrieb am zuletzt editiert von Zarello
                            #589

                            @x-traxion sagte in [ESPHome] Beta release:

                            würde das aber gerne über die API machen :/

                            Auch Dich kann ich leider nur auf die unterstützen Elemente im ersten Post hinweisen.
                            Ich bin am Anfang selber auch in diese Falle getappt.
                            Es ist ein Open-Source-Projekt. Wenn sich jemand findet, der das einbaut, gibt es sicherlich einige, die sich darüber freuen würden (mich eingeschlossen).
                            Ich hatte mir den Adapter kurz angeguckt und beschlossen, es ist für mich leider viel einfacher MQTT zu verwenden als meine benötigten Funktionen im Adapter nachzuziehen, da meine Fähigkeiten in JavaScript sehr begrenzt sind.

                            PS.: Wenn Du MQTT verwendest, solltest Du die API übrigens deaktivieren, ansonsten startet Dein Gerät alle viertel Stunde neu, da es keinen Kontakt über die API hat.

                            1 Antwort Letzte Antwort
                            0
                            • J Offline
                              J Offline
                              Jacke
                              schrieb am zuletzt editiert von Jacke
                              #590

                              Ich bin mittlerweile auch bei MQTT gelandet, leider bekomme ich es nicht hin die Werte zu ändern.
                              es geht um folgendes

                              number:
                                  - platform: modbus_controller
                                    name: "${devicename} Max Output Active Power"
                                    address: 3
                                    value_type: U_WORD
                                    min_value: 0
                                    max_value: 100
                                    entity_category: config
                                    step: 1
                              

                              Hier kann ich die Leistung meines Growatt regeln leider weis ich nicht wie ich das machen kann.
                              Mir würde auch erstmal ein SLider in der Weboberfläche reichen.
                              Hier habe ich einen Slider bekomme aber den Wert mittels IoBroker nicht geändert

                              number:
                                - platform: template
                                  name: "BBQ_Toleranz"
                                  id: "bbq_tol_slider"
                                  optimistic: true
                                  min_value: 0
                                  initial_value: 5
                                  max_value: 10
                                  step: 1
                                  set_action:
                                    then:
                                      - lambda: id(bbq_tol) = x;
                              

                              wenn ich den Wert mittels Node Red ändere sehe ich es im Mqtt explorer aber er übernimmt es nicht in der Weboberfläche

                              1 Antwort Letzte Antwort
                              0
                              • DutchmanD Offline
                                DutchmanD Offline
                                Dutchman
                                Developer Most Active Administrators
                                schrieb am zuletzt editiert von
                                #591

                                Gruesse euch ! Nach viel redesign wurde soeben ESPHome 0.5.0-beta.0 released, feedback zu testen etc bitte hier: https://forum.iobroker.net/topic/70134/esphome-beta-release-0-5-0-beta-0-ist-bereits-zum-testen

                                damit schliesse ich dieses ältere topic

                                1 Antwort Letzte Antwort
                                2
                                Antworten
                                • In einem neuen Thema antworten
                                Anmelden zum Antworten
                                • Älteste zuerst
                                • Neuste zuerst
                                • Meiste Stimmen


                                Support us

                                ioBroker
                                Community Adapters
                                Donate

                                765

                                Online

                                32.4k

                                Benutzer

                                81.4k

                                Themen

                                1.3m

                                Beiträge
                                Community
                                Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                ioBroker Community 2014-2025
                                logo
                                • Anmelden

                                • Du hast noch kein Konto? Registrieren

                                • Anmelden oder registrieren, um zu suchen
                                • Erster Beitrag
                                  Letzter Beitrag
                                0
                                • Home
                                • Aktuell
                                • Tags
                                • Ungelesen 0
                                • Kategorien
                                • Unreplied
                                • Beliebt
                                • GitHub
                                • Docu
                                • Hilfe