[–] 2 points 1 month ago (1 child)

@batmaniam the reason its not as easy as just including a library is that the two projects are not designed that way.ESPHome and WLED are not libraries, they are complete projects in their own right.Sure, you can bodge an air filter for one car into a different one, but you can’t (easily!) bodge a whole car into a different one! #StupidCarAnalogiesESPectre is also a project in its own right, but additionally has been made available as an ESPHome external component- ie ESPHome has a feature to copy the relevant ESPectre code and ESPHome adapter/integration code into the ESPHome tree while doing its codegen/compilation step.

  • source
  • parent
  • context
  • [–] 3 points 1 month ago (3 children)

    @batmaniam #esphome uses python to read a yaml file and generate C++, and then compiles the result. In general, you can’t just trivially combine two esp32 projects into a single firmware. However, esphome has a component that accepts the #wled udp broadcast protocol from software running elsewhere on your network. This may or may not end up being a simplification - there are a small number of existing “senders”, mostly designed for coordinating large lighting installations such as Christmas light displays across multiple ESP32s.Additionally, esphome has a number of built-in lighting effects (fewer than wled, and less flexible), which may be enough for your purposes. If so, you should be able to consolidate two esp32s into one.Then again, the positioning of the esp32 probably plays a role in its ability to detect motion using the espectre component, so there may still be tradeoffs involved. Ie the led controller may be positioned near the ceiling where it is less able to detect movement.

  • source