Skip to content

Conversation

@p1ngb4ck
Copy link

@p1ngb4ck p1ngb4ck commented Feb 3, 2026

As the title says - my esphome component allows for ethernet connectivity as well, therefore I propose the following rework.
Mostly just renaming from wifi to network and add ethernet logic & symbol.
Also, display backlight value was added to response-content and I changed default baud to 19200 after intensive changes (please just deny that change of course if you dont agree)
Removed the status code change and rather changed my esphome component to be fully backwards compatible, no need to reflash if someone doesnt need display backlight in query response etc.

Esphome component finished now as well, last remaining point is to create a nice HA custom card
ESPHome component features:

  • handle sensors for VIN/VOUT/CUR_OUT
  • handle inputs for voltage, current, output switch (enable/disable), lock, display
  • provides functionalits for data logging to sd
  • provides calibration value request & save to sd storage + auto-restore after flashing fw
  • fw upgrade function capable of handling different bootloader speeds (if bootloaders uart baud rate setting is different from "main" opendps one) and capable of using esphome-devices "local" storage (sd/usb/internal flash data/extra spi flash attached)
    to read fw bin file from
  • provides tcp bridge on configurable port, auto-pausing and resuming when/after external tcp client connects - use in dpsctly.py with param "-d tcp:"

As esphome can deal with ethernet/wifi + mqtt + api connections (ha & custom) -> these features are automatically available as well when replacing the esp8266 wifi-serial- proxy with an esphome based device using my opendps component

Hope this helps =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants