You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of a November update ESPHome's native qspi_dbi component should in theory be able to support the AXS15231 driver, however in testing myself and Clyde have been unable to replicate an init sequence that works on the T-Display Long.
The theory is that while the built-in axs15231 model may not work, we should be able to use the custom model if we can find a working init_sequence to add to the config.
Clyde suggested this config after looking at your component, but it does not work:
As of a November update ESPHome's native qspi_dbi component should in theory be able to support the AXS15231 driver, however in testing myself and Clyde have been unable to replicate an init sequence that works on the T-Display Long.
The theory is that while the built-in
axs15231
model may not work, we should be able to use thecustom
model if we can find a working init_sequence to add to the config.Clyde suggested this config after looking at your component, but it does not work:
If you could help figure out what
init_sequence
config we need here then your custom component should be no longer needed.The text was updated successfully, but these errors were encountered: