Not a real issue but rather asking if still interested in project -> want to port it to esphome

[p1ngb4ck]

Hi !

I am a great fan of your project, it is running "flawlessly" here - using a wemos d1 mini being the wifi serial proxy.
What I want to do:
As I have some experience in adding external components for esphome - I would like to add a component for the opendps.
This would allow for very easy "custom" configs (use the device you want by just creating a yaml and including my custom component) -> as I created usb-storage/sd_storage and nfs_client components for esphome as well, this would allow for some neat new features, like:

• ethernet support
• mqtt/ha-api
• data-logging to usb/sd/nfs
• any additions you basically like that esphome supports

Would you agree? Thx a bunch already

Edit says:
Me and Claude-AI did some initial work:
can be found @ https://github.com/p1ngb4ck/esphome/blob/dev/esphome/components/opendps
Readme is included there as well as example config yamls

[p1ngb4ck]

Okay - "good news" so far. I have been able to find some time and test this esphome component now.
I successfully tested everything provided by the component - except the fw update functionality.
Also wifi-signal-indicator doesnt yet work, if opendps is connected to esphome-device with my component (minor issue for now I think)
Next steps I am going to test:
Try to find my original fw file I had build and flashed - and use it to test fw-upgrade mechanism first
Then, change baud to 115200 for opendps fw and try to build and flash

Afterwards, I would create a separate repo for this external ("custom") esphome component, including Readme and infos.

[p1ngb4ck]

Okay
Everybody seeing this:

• I tested my esphome component linked above that shall be able to replace the bridge
• Added a serial proxy function on port 5005 in addition - so it should also now work together with dpsctl.py (in addition to providing sensors/switches etc itself)

ATTENTION:

• FW Update functionality does NOT work (bricked my device !!!!!!!!!!!!!!!!!!) - still not sure if I am going to fix or remove that (maybe just rely on dpsctl.py for that)

-> Restored my device more or less (had to do trace repairs, as my soldering skills back in the day were even worse than now, got stlink connected & flashed though) - but I dont have uart-connection to it now anymore, got to dig a little why -> its been multiple years since I flashed the previously working opendps version. I am pretty sure it was sth related to rx/tx definitions or similar - hope I will find out again soon.

[kanflo]

Hi! Glad to see this old sin of mine is still useful. I have actually been thinking of an ESPHome addition as I would like to be able to dim my patio lights from HASS using an old DPS5005 but time wise I am glad you beat me to it ;) . Strange that the device got bricked though. It was designed to be safe-ish where the DPS would drop into the boot loader if a FW upgrade failed.

[p1ngb4ck]

TY so much for coming back to me even on this old project still - yes it is still very useful - and can probably increase in usefulness bc:

• I have ethernet networking & sd/usb-storages / nfs-shares working in esphome as well
• dps5005 is exceptionally precise after proper calibration (at least my device was - I have to re-do calibration again now of course after unbricking etc)
• "serial-bridge" - feature (pauses normal esphome sensors etc while external client is connected) allows for dpsctl.py usage anyhow

The bricking of the device is absolutely my own fault. Definitely. It`s due to me not implementing the upgrade process correctly and repeatedly trying - at first the device came up in bootloader mode even after failed flash -> this was absolutely my own fault.

What I am currently missing (ToDos planned/working on right now) :

• Add ethernet connection & flash-in-progress symbols (cosmetic)
• fix fw upgrade (done !)
• I added display-brightness to query-response - works, but my esphome component acts strange regarding the display - some bug there left (Edit says: fixed - was a yaml issue, I was just missing a publish_state call to the template)
• I tested higher baud rates -> seems 57600 is the highest I can do with my cable-setup without dps getting out of sync after short while (update : sticking to 9600 / 19200 seems more stable - sticking to the latter for myself now)
• data-logger with fast psram buffers to support high update rates - to log fast bootsequences for examples in repairs (almost done, last bugs currently in progress)
• dpsctl.py now works fine with that serial-bridge, except for FW-upgrade.
• add custom card for HomeAssistant to create a beautiful overlay/panel dashboard - that could also be used in a separate no-frame-window for use with obs etc.

I know this is quite a lot to ask for, but if you still remember any close details regarding the actual "expected" procedure of the original fw-upgrade function of dpsctl.py (eg. "what I could be missing/whats important") -> that could really help me out, as this is the only major function not working (besides calibration actions missing in esphome component)
THX so much in advance - I will try my best to provide a neat PR as soon as everything is working and well tested

Edit says : please disregard - fw upgrade works now. Only cosmetics (symbols), add fw-upgrade enhancement for different bootloader speed (baud-rate), datalogger fixes, calibration assistant testing, ha-card + doc/readme updates to do

[p1ngb4ck]

For other readers that may not want to read all of this:
Current left ToDos are:-

• fix datalogger bugs // Edit says - done
• test calibration assistant & add calibration save&restore to/from sd (added - see calibration yaml example)
• fw-upgrade baudrate option additions // Edit says : fw upgrade now allows for changing to different baudrate for bootloader (& flash in bootloader then) - and back after successful flash - bugs here were solved now, works. make sure to reset preferences if they contain wrong bootloader baudrate (see factory-reset button of esphome)
• add symbols for ethernet & flash-in-progress // Edit says - ethernet-symbol done - flash upgrade progress would need changes in dpsboot bootloader
• bugs in tcp-serial-bridge addressed (currently testing)
• add HA-custom card to create a nice panel in HA - last major point on list thats open
• update Readme/Docs // Edit says - datalogger info added to Readme - Edit says: calibration yaml example added