[ESPHome] Beta release

Beowolf

Ich bekomme den Adapter nicht installiert.

Hier die Meldungen:

$ iobroker add esphome --host ioBroker-Master

NPM version: 6.14.16

Installing iobroker.esphome@0.2.4... (System call)

> iobroker.esphome@0.2.4 install /opt/iobroker/node_modules/iobroker.esphome> npip install

No python_modules directory; installing pip locally if needed.

Successfully completed pip check.

Collecting esphome>=2021.8

Using cached esphome-2022.2.6-py2.py3-none-any.whl (2.1 MB)

Collecting tornado>=3.2

Using cached tornado-6.1.tar.gz (497 kB)

Preparing metadata (setup.py): started

Preparing metadata (setup.py): finished with status 'done'

Collecting tzdata>=2021.1

Using cached tzdata-2022.1-py2.py3-none-any.whl (339 kB)

Collecting esphome-dashboard==20220209.0

Using cached esphome_dashboard-20220209.0-py3-none-any.whl (592 kB)

Collecting click==8.0.3

Using cached click-8.0.3-py3-none-any.whl (97 kB)

Collecting PyYAML==6.0

Using cached PyYAML-6.0.tar.gz (124 kB)

Installing build dependencies: started

Installing build dependencies: finished with status 'done'

Getting requirements to build wheel: started

Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started

Preparing metadata (pyproject.toml): finished with status 'done'

Collecting aioesphomeapi==10.8.2

Using cached aioesphomeapi-10.8.2-py2.py3-none-any.whl (49 kB)

Collecting zeroconf==0.38.3

Using cached zeroconf-0.38.3-py3-none-any.whl (106 kB)

Collecting kconfiglib==13.7.1

Using cached kconfiglib-13.7.1-py2.py3-none-any.whl (145 kB)

Collecting esptool==3.2

Using cached esptool-3.2.tar.gz (206 kB)

Preparing metadata (setup.py): started

Preparing metadata (setup.py): finished with status 'done'

Collecting colorama==0.4.4

Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)

Collecting pyserial==3.5 Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)

Collecting tzlocal==4.1

Using cached tzlocal-4.1-py3-none-any.whl (19 kB)

Collecting platformio==5.2.5

Using cached platformio-5.2.5.tar.gz (218 kB)

Preparing metadata (setup.py): started

Preparing metadata (setup.py): finished with status 'done'

Collecting voluptuous==0.12.2

Using cached voluptuous-0.12.2.tar.gz (48 kB)

Preparing metadata (setup.py): started

Preparing metadata (setup.py): finished with status 'done'

Collecting paho-mqtt==1.6.1

Using cached paho-mqtt-1.6.1.tar.gz (99 kB)

Preparing metadata (setup.py): started

Preparing metadata (setup.py): finished with status 'done'

Collecting protobuf<4.0,>=3.12.2

Using cached protobuf-3.19.4-py2.py3-none-any.whl (162 kB)

Collecting noiseprotocol<1.0,>=0.3.1

Using cached noiseprotocol-0.3.1-py3-none-any.whl (20 kB)

Collecting importlib-metadata

Using cached importlib_metadata-4.11.3-py3-none-any.whl (18 kB)

Collecting bitstring>=3.1.6

Using cached bitstring-3.1.9-py3-none-any.whl (38 kB)

Collecting cryptography>=2.1.4

Using cached cryptography-36.0.2.tar.gz (572 kB)

Installing build dependencies: started

Installing build dependencies: finished with status 'error'

host.ioBroker-Master Cannot install iobroker.esphome@0.2.4: 1

ERROR: Process exited with code 25

Wo habe ich da einen Fehler?

maxpd

@beowolf welche python version ist drauf?

Beowolf

@maxpd
pi@ioBroker-Master:~ $ python --version
Python 2.7.16
pi@ioBroker-Master:~ $ python3 --version
Python 3.7.3
pi@ioBroker-Master:~ $

maxpd

@beowolf

Ich würde dir ein Update empfehlen:

https://forum.iobroker.net/topic/47213/upgrade-von-debian-10-buster-auf-11-bullseye

Danach gehts.

Dutchman

@beowolf sagte in [ESPHome] Beta release:

@maxpd
pi@ioBroker-Master:~ $ python --version
Python 2.7.16
pi@ioBroker-Master:~ $ python3 --version
Python 3.7.3
pi@ioBroker-Master:~ $

python muss nach 3.7 verweisen , da dies für jedes System anders ist kan ich die Python Installation selber leider nicht Supporten

OpenSourceNomad

@beowolf said in [ESPHome] Beta release:

Python 2.7.16

Python 2 ist übrigens schon seit über 2 Jahren EOL. Wahrscheinlich gibt es so ziemliche keine (aktuelle) Software die nicht mit Python 3 kompatibel ist

Thomas Braun

@beowolf
Debian? Bullseye?

Dann würde ich empfehlen:

sudo apt update
sudo apt install python-is-python3
sudo apt autoremove

Beowolf

@thomas-braun

Hm.
Ich habe jetzt alles neu aufgesetzt. Backup eingespielt usw.

Es kommt immer noch diese Meldungen:


pi@raspberrypi:~ $ cd /opt/iobroker
pi@raspberrypi:/opt/iobroker $ npm i iobroker.esphome@latest

> iobroker.esphome@0.2.4 install /opt/iobroker/node_modules/iobroker.esphome
> npip install

No python_modules directory; installing pip locally if needed.
  Cache entry deserialization failed, entry ignored
  Cache entry deserialization failed, entry ignored
Successfully completed pip check.
Collecting esphome>=2021.8
  Using cached esphome-2022.3.0-py2.py3-none-any.whl (2.2 MB)
Collecting tornado>=3.2
  Using cached tornado-6.1.tar.gz (497 kB)
  Preparing metadata (setup.py) ... done
Collecting tzdata>=2021.1
  Using cached tzdata-2022.1-py2.py3-none-any.whl (339 kB)
Collecting kconfiglib==13.7.1
  Using cached kconfiglib-13.7.1-py2.py3-none-any.whl (145 kB)
Collecting esptool==3.2
  Using cached esptool-3.2.tar.gz (206 kB)
  Preparing metadata (setup.py) ... done
Collecting PyYAML==6.0
  Using cached PyYAML-6.0.tar.gz (124 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting aioesphomeapi==10.8.2
  Using cached aioesphomeapi-10.8.2-py2.py3-none-any.whl (49 kB)
Collecting paho-mqtt==1.6.1
  Using cached paho-mqtt-1.6.1.tar.gz (99 kB)
  Preparing metadata (setup.py) ... done
Collecting pyserial==3.5
  Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
Collecting voluptuous==0.12.2
  Using cached voluptuous-0.12.2.tar.gz (48 kB)
  Preparing metadata (setup.py) ... done
Collecting tzlocal==4.1
  Using cached tzlocal-4.1-py3-none-any.whl (19 kB)
Collecting platformio==5.2.5
  Using cached platformio-5.2.5.tar.gz (218 kB)
  Preparing metadata (setup.py) ... done
Collecting zeroconf==0.38.3
  Using cached zeroconf-0.38.3-py3-none-any.whl (106 kB)
Collecting click==8.0.3
  Using cached click-8.0.3-py3-none-any.whl (97 kB)
Collecting colorama==0.4.4
  Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
Collecting esphome-dashboard==20220309.0
  Using cached esphome_dashboard-20220309.0-py3-none-any.whl (593 kB)
Collecting noiseprotocol<1.0,>=0.3.1
  Using cached noiseprotocol-0.3.1-py3-none-any.whl (20 kB)
Collecting protobuf<4.0,>=3.12.2
  Using cached protobuf-3.19.4-py2.py3-none-any.whl (162 kB)
Collecting bitstring>=3.1.6
  Using cached bitstring-3.1.9-py3-none-any.whl (38 kB)
Collecting cryptography>=2.1.4
  Using cached cryptography-36.0.2.tar.gz (572 kB)
  Installing build dependencies ... error
  error: subprocess-exited-with-error

  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [122 lines of output]
      Collecting setuptools>=40.6.0
        Using cached setuptools-60.10.0-py3-none-any.whl (1.1 MB)
      Collecting wheel
        Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
      Collecting cffi>=1.12
        Using cached cffi-1.15.0.tar.gz (484 kB)
        Preparing metadata (setup.py): started
        Preparing metadata (setup.py): finished with status 'done'
      Collecting setuptools-rust>=0.11.4
        Using cached setuptools_rust-1.1.2-py3-none-any.whl (21 kB)
      Collecting pycparser
        Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
      Collecting typing-extensions>=3.7.4.3
        Using cached typing_extensions-4.1.1-py3-none-any.whl (26 kB)
      Collecting semantic-version<3,>=2.8.2
        Using cached semantic_version-2.9.0-py2.py3-none-any.whl (15 kB)
      Building wheels for collected packages: cffi
        Building wheel for cffi (setup.py): started
        Building wheel for cffi (setup.py): finished with status 'error'
        error: subprocess-exited-with-error

        × python setup.py bdist_wheel did not run successfully.
        │ exit code: 1
        ╰─> [36 lines of output]
            running bdist_wheel
            running build
            running build_py
            creating build
            creating build/lib.linux-armv7l-3.9
            creating build/lib.linux-armv7l-3.9/cffi
            copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/lock.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/error.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/model.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/__init__.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/api.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/cparser.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/commontypes.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/verifier.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/recompiler.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/_embedding.h -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.9/cffi
            running build_ext
            building '_cffi_backend' extension
            creating build/temp.linux-armv7l-3.9
            creating build/temp.linux-armv7l-3.9/c
            arm-linux-gnueabihf-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -ffile-prefix-map=/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/python3.9 -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.9/c/_cffi_backend.o
            c/_cffi_backend.c:2:10: fatal error: Python.h: Datei oder Verzeichnis nicht gefunden
                2 | #include <Python.h>
                  |          ^~~~~~~~~~
            compilation terminated.
            error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for cffi
        Running setup.py clean for cffi
      Failed to build cffi
      Installing collected packages: wheel, typing-extensions, setuptools, semantic-version, pycparser, setuptools-rust, cffi
        Running setup.py install for cffi: started
        Running setup.py install for cffi: finished with status 'error'
        error: subprocess-exited-with-error

        × Running setup.py install for cffi did not run successfully.
        │ exit code: 1
        ╰─> [38 lines of output]
            running install
            /opt/iobroker/node_modules/iobroker.esphome/python_modules/lib/python3.9/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
              warnings.warn(
            running build
            running build_py
            creating build
            creating build/lib.linux-armv7l-3.9
            creating build/lib.linux-armv7l-3.9/cffi
            copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/lock.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/vengine_gen.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/error.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/model.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/__init__.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/ffiplatform.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/api.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/cparser.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/commontypes.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/verifier.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/pkgconfig.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/recompiler.py -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/_cffi_include.h -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/parse_c_type.h -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/_embedding.h -> build/lib.linux-armv7l-3.9/cffi
            copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-3.9/cffi
            running build_ext
            building '_cffi_backend' extension
            creating build/temp.linux-armv7l-3.9
            creating build/temp.linux-armv7l-3.9/c
            arm-linux-gnueabihf-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -ffile-prefix-map=/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/python3.9 -c c/_cffi_backend.c -o build/temp.linux-armv7l-3.9/c/_cffi_backend.o
            c/_cffi_backend.c:2:10: fatal error: Python.h: Datei oder Verzeichnis nicht gefunden
                2 | #include <Python.h>
                  |          ^~~~~~~~~~
            compilation terminated.
            error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
      error: legacy-install-failure

      × Encountered error while trying to install package.
      ╰─> cffi

      note: This is an issue with the package mentioned above, not pip.
      hint: See above for output from the failure.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.esphome@0.2.4 install: `npip install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.esphome@0.2.4 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-03-21T16_38_52_555Z-debug.log
pi@raspberrypi:/opt/iobroker $

Wo mache ich etwas falsch?

Thomas Braun

@beowolf sagte in [ESPHome] Beta release:

Wo mache ich etwas falsch?

Wie ist denn python jetzt installiert?

python --version
python3 --version
apt policy python3-pip
apt policy python3-cffi

Beowolf

@thomas-braun


pi@raspberrypi:/opt/iobroker $ python --version
Python 3.9.2
pi@raspberrypi:/opt/iobroker $ python3 --version
Python 3.9.2
pi@raspberrypi:/opt/iobroker $ apt policy python3-pip
python3-pip:
  Installiert:           (keine)
  Installationskandidat: 20.3.4-4+rpt1
  Versionstabelle:
     20.3.4-4+rpt1 500
        500 http://archive.raspberrypi.org/debian bullseye/main armhf Packages
     20.3.4-4 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
pi@raspberrypi:/opt/iobroker $ apt policy python3-cffi
python3-cffi:
  Installiert:           (keine)
  Installationskandidat: 1.14.5-1
  Versionstabelle:
     1.14.5-1 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
pi@raspberrypi:/opt/iobroker $

Thomas Braun

@beowolf

Ich vermute python3-pip sollte mindestens installiert sein.

Beowolf

@thomas-braun

Ich habe es hier mit versucht.

sudo apt-get --reinstall install python3-pip

Kein Erfolg

pi@raspberrypi:/ $ python3 -V
Python 3.9.2
pi@raspberrypi:/ $ pip3 -V
pip 20.3.4 from /usr/lib/python3/dist-packages/pip (python 3.9)

Thomas Braun

@beowolf

sudo apt update
sudo apt install python3-pip

Beowolf

@thomas-braun

Asche auf mein Haupt - Hin und wieder ein reboot und alles geht.

maxpd

@Dutchman

Wenn ich lediglich ein Script über 1 oder 2 Template Buttons

https://esphome.io/components/button/template.html

starten möchte und die gesamte restliche Logik und Variablen etc direkt auf dem ESP platziere, was benötigst du dann an Informationen?

Dutchman

@maxpd sagte in [ESPHome] Beta release:

starten möchte und die gesamte restliche Logik und Variablen etc direkt auf dem ESP platziere, was benötigst du dann an Informationen?

ich glaube nix die frage ist ob ein template Button Exposed wird.
Mal mal bitte einen in der yaml (kan ich später erst probieren) und schaue was passiert.

We der wert Pere Opi uebertragen wird koennen 2 Sachen passieren:

die daten passen in die jetzigen Adapter code
es ist eine neue, unbekannte entity
Beim zweiten fall wuerde eine fehler/warnung in ioBroker log sichtbar sein und die infos brauche ich dan

maxpd

@dutchman Ich glaube dir hat die Spracheingabe den Text ein bissl versämmelt

Aber ich hab die yaml hier gebaut

esphome:
  name: little_wemos
  platform: ESP8266
  board: d1_mini
 
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
 
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Little Wemos Fallback Hotspot"
    password: "************"
 
captive_portal:
 
# Enable logging
logger:
 
api:
  services:
    - service: control_servo
      variables:
        level: float
      then:
        - servo.write:
            id: my_servo
            level: !lambda 'return level / 100.0;'
          
 
ota:
 
output:
  - platform: esp8266_pwm
    id: pwm_output
    pin: D3
    frequency: 50 Hz
 
 
servo:
  - id: my_servo
    output: pwm_output
    
button:
  - platform: template
    name: "Template Button"
    on_press:
      - logger.log: Button Pressed
      - cover.open: flying
      - delay: 8s
      - cover.close: flying
      - delay: 9s    
          
cover:
  - platform: time_based
    id: flying
    open_action:
#      then:
      - servo.write:
          id: my_servo
          level: 10.0%
    open_duration: 5s

    close_action:
#      then:
      - servo.write:
          id: my_servo
          level: -10.0%
    close_duration: 6s
    
    stop_action:
#      then:
      - servo.write:
          id: my_servo
          level: 0%
      - servo.detach: my_servo

und bekomme die Ausgabe. Wobei mein wemos plötzlich immer disconnected. Liegt eventuell am Update auf die 2022.03?


esphome.0
2022-03-22 20:14:42.592	debug	192.168.178.53 client data 4 little_wemos (esphome v2022.3.0)"little_wemos

esphome.0
2022-03-22 20:14:42.575	error	ESPHome client 192.168.178.53 TypeError: Cannot read property 'deserializeBinary' of undefined

esphome.0
2022-03-22 20:14:42.574	debug	192.168.178.53 client data 

esphome.0
2022-03-22 20:14:13.912	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:13,912 INFO 304 GET /devices (192.168.178.146) 1.62ms

esphome.0
2022-03-22 20:14:12.535	warn	Client 192.168.178.53 Timeout, connection Lost, will reconnect automatically when device is available!

esphome.0
2022-03-22 20:14:09.061	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:09,061 INFO Running command 'esphome --dashboard -q vscode --ace /opt/iobroker/iobroker-data/esphome.0'

esphome.0
2022-03-22 20:14:08.989	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,989 INFO 101 GET /ace (192.168.178.146) 1.17ms

esphome.0
2022-03-22 20:14:08.971	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,970 INFO 200 GET /static/fonts/material-icons/MaterialIcons-Regular.woff2 (192.168.178.146) 1.87ms

esphome.0
2022-03-22 20:14:08.913	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,913 INFO 304 GET /devices (192.168.178.146) 1.58ms

esphome.0
2022-03-22 20:14:08.877	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,876 INFO 200 GET /static/js/vendor/ace/mode-yaml.js (192.168.178.146) 2.07ms

esphome.0
2022-03-22 20:14:08.874	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,873 INFO 200 GET /static/js/vendor/ace/theme-dreamweaver.js (192.168.178.146) 1.69ms

esphome.0
2022-03-22 20:14:08.696	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,696 INFO 200 GET /static/js/vendor/jquery-ui/jquery-ui.min.js?hash=cab3392d (192.168.178.146) 189.47ms

esphome.0
2022-03-22 20:14:08.666	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,666 INFO 200 GET /static/js/vendor/materialize/materialize.min.js?hash=4be20daf (192.168.178.146) 158.14ms

esphome.0
2022-03-22 20:14:08.636	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,635 INFO 200 GET /static/js/esphome/index-92d154f2.js (192.168.178.146) 114.09ms

esphome.0
2022-03-22 20:14:08.633	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,633 INFO 200 GET /static/js/vendor/ace/ace.js?hash=65322f49 (192.168.178.146) 124.26ms

esphome.0
2022-03-22 20:14:08.516	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,515 INFO 200 GET /static/js/vendor/jquery-validate/jquery.validate.min.js?hash=aad785d4 (192.168.178.146) 8.16ms

esphome.0
2022-03-22 20:14:08.511	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,511 INFO 200 GET /static/js/vendor/jquery/jquery.min.js?hash=12108007 (192.168.178.146) 5.14ms

esphome.0
2022-03-22 20:14:08.462	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,461 INFO 200 GET /static/css/esphome-2.css?hash=b79b4733 (192.168.178.146) 7.20ms

esphome.0
2022-03-22 20:14:08.459	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,459 INFO 200 GET /static/css/vendor/materialize/materialize.min.css?hash=ec1df3ba (192.168.178.146) 5.40ms

esphome.0
2022-03-22 20:14:08.452	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,450 INFO 200 GET /static/fonts/material-icons/material-icons.css?hash=ead4c276 (192.168.178.146) 3.75ms

esphome.0
2022-03-22 20:14:08.449	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,449 INFO 200 GET /static/fonts/material-icons/MaterialIcons-Regular.woff2?hash=570eb838 (192.168.178.146) 2.71ms

esphome.0
2022-03-22 20:14:08.412	debug	esphome.0 (13292) [ESPHome - Console] 2022-03-22 20:14:08,411 INFO 304 GET /?instance=0&newReact=true&0&react=colored (192.168.178.146) 2.16ms

esphome.0
2022-03-22 20:14:07.562	error	ESPHome client 192.168.178.53 TypeError: Cannot read property 'deserializeBinary' of undefined

esphome.0
2022-03-22 20:14:07.561	debug	192.168.178.53 client data 4 little_wemos (esphome v2022.3.0)"little_wemos

esphome.0
2022-03-22 20:14:07.543	error	ESPHome client 192.168.178.53 TypeError: Cannot read property 'deserializeBinary' of undefined

esphome.0
2022-03-22 20:14:07.542	debug	192.168.178.53 client data 

esphome.0
2022-03-22 20:13:37.521	warn	Client 192.168.178.53 Timeout, connection Lost, will reconnect automatically when device is available!

klassisch

Kurze Zwischenfrage: Hat schon jemand Erfahrungen mit dem MCP23016 oder PCF8575 mit ESPHome?
Ich möchte > 8 Eingänge abfragen. Nicht zeitkritsch, Abfrageintervall von einigen Sekunden wäre kein Problem.
Die Eingänge werden mit open collector auf GND gezogen. Wenn man einen internen pull up nutzen könnte, wäre das einfacher. Beim MCP23ß16 scheint das nicht zu gehen.

OpenSourceNomad

@klassisch said in [ESPHome] Beta release:

Erfahrungen mit dem MCP23016 oder PCF8575 mit ESPHome?
Ich möchte > 8 Eingänge abfragen.

Ich glaube (wenn ich mich recht erinnere) hat der PCF8575 die blöde Eigenschaft direkt nach dem starte/nbestromen alle GPIO auf Output und high zu setzen. Erst wenn esphome die init routine durchlaufen hat sind die GPIO's vom PCF8575 auf input gesetzt.

Die MCP230xx haben diese Eigenheit soweit ich mich erinnere nicht.

Wenn man einen internen pull up nutzen könnte, wäre das einfacher. Beim MCP23ß16 scheint das nicht zu gehen.

Dafür der MCP23008 und MCP23017 wenn ich die docs passend interpretiere

klassisch

Vielen Dank!

@opensourcenomad sagte in [ESPHome] Beta release:

@klassisch said in [ESPHome] Beta release:
Ich glaube (wenn ich mich recht erinnere) hat der PCF8575 die blöde Eigenschaft direkt nach dem starte/nbestromen alle GPIO auf Output und high zu setzen. Erst wenn esphome die init routine durchlaufen hat sind die GPIO's vom PCF8575 auf input gesetzt.

ugly! Dann zerschießt er u.U. die oc Ausgänge meiner Sensoren. Müßte man also jeweils noch einen Serienwiderstand einfügen, 330 Ohm

Die MCP230xx haben diese Eigenheit soweit ich mich erinnere nicht.

Das wäre gut!

Wenn man einen internen pull up nutzen könnte, wäre das einfacher. Beim MCP23ß16 scheint das nicht zu gehen.

Ja steht in der ESPHome Doku so beim MCP23016

Dafür der MCP23008 und MCP23017 wenn ich die docs passend interpretiere

Zumindest die bei ESPHome angegebenen Beispiele zeigen mein 08 und beim 17 die Komentarzeile

# One of INPUT or OUTPUT

bzw.

      mode:
        input: true
        pullup: true
      inverted: false

die Komentarzeile

# One of INPUT or OUTPUT

steht auch im Beispielprogramm des PCF8574 / 5.

So richtig eindeutig ist die Doku leider nicht.

und der MCP23017 kostet ein Vemögen!
Und den MCP23008 gibt es derzeit nicht als brakout Modul.
Bleibt wohl nur PCF8575 mit Reihenwiderstand und hoffen, dass der pull up funktioniert.

NEWS

[ESPHome] Beta release

Support us

871
Online

31.8k
Users

80.0k
Topics

1.3m
Posts

NEWS

[ESPHome] Beta release

Support us

871Online

31.8kUsers

80.0kTopics

1.3mPosts

871
Online

31.8k
Users

80.0k
Topics

1.3m
Posts