[WIP] ESPHome firmware - #57
Conversation
|
@DSpeichert Please encapsulate any code changes in the firmware with "#ifdef ESPHOME" as is already done with MATTER and MQTT. |
There will be no changes to the firmware in |
|
Yeah, makes sense ... I should've gave it some thought first!! :P |
| - "\uE6C3" # on_hub_device | ||
|
|
||
| display: | ||
| - id: display1 |
There was a problem hiding this comment.
Need to include:
invert_colors: false
| 4. Clean configuration if you're having issues rebuilding (`esphome clean ...`) | ||
|
|
||
|
|
||
| You can achieve the above with the following snippet: |
There was a problem hiding this comment.
I tried this in a clean directory (ie, not a git cloned area) and it failed as the ../app/default_16mb.csv file was missing. After supplying that (and making the to the device yaml file mentioned below), it worked and reprogrammed the device.
|
So far, I can verify the display works (but not necessarily the touch screen) and the motion sensor. I do not see any way to exercise the other areas that are believed to be supported though (like the touch screen, status LED, light sensor, the piezo or the relays). |
The PCB can happily be operated via ESPHome firmware, which is native to Home Assistant (official ESPHome plugin is needed instead of MQTT server/bridge) thanks to its wide array of supported modules - in fact all of the ones used by this project.
This YAML currently includes support for:
What I tried that didn't work:
TODO before merging: