I 100%+ plus agree. I myself will not take this path.
If your current controller is a Modbus (is this ESP32 DIY or something else?) it will be reletively easy to add a Mode Button press simulation and use a feedback from Mode State LEDs.
You may need just only 2 status signals from whichever Modes are used.
For modbus, I'm using waveshare esp32-s3-relay-1ch with esphome.
I've actually just gotten the mode register read working, so now I know what the mode is after a button press. But there is some polling delay.
Which modbus commands can do mode button press simulation and mode state LED feedback? I only know the commands from AutoSlide-ATM2-Modbus-Protocols.pdf.
Thounds good!
So, feedback for current Mode Status is there. There is no need to messup with checking LED States. Polling delay should not be a problem.My ggod gess, Mode Change will be used only few timea s day.
Unfortunately there is no shuch thing. You will need to add wires across Mode Select Button and use an Optocoupler (my primary choice) or Relay for simulating Button Press. How to control this Optocouple or Relay is a different story. I have no idea what is "waveshare esp32-s3-relay-1ch" and what its capability. If you want to, I can share my Hubduino Modbus Controller sketch for the ESP32 (any ESP32 development board should be OK and you will need a RS485 Tranceiver module). You will need to add a "Mode Status" read function and a control for Optocoupler/Relay (basically the same thing, simple On/Off Switch). This has a direct integration with HE.
Thank you for the advice. esp32-s3-relay-1ch has an rs485 interface, and a relay. I've just soldered the relay to the mode switch button, and configured esphome to read the mode register value and press the button the needed number of times for certain modes.
1 Like
I am happy to hear you got a solid reliable solution.
