Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use component with ESP-IDF framework #23

Open
rschueler opened this issue Feb 3, 2023 · 7 comments · May be fixed by #33
Open

Use component with ESP-IDF framework #23

rschueler opened this issue Feb 3, 2023 · 7 comments · May be fixed by #33
Labels
enhancement New feature or request

Comments

@rschueler
Copy link

Hi, I am trying to utilize the bluetooth_proxy on my nsPanel, but the latest speed improvements are based on the ESP-IDF framework. When I configure my YAML file to use this framework, I encounter the following error during compilation: "This feature is only available with frameworks ['arduino']." Is there a solution to this problem?

Furthermore, I have run into some difficulties with the latest release of ESPhome and HA 2023.2. I have found that when using the 2022.12.8 firmware, the file size becomes excessively large when Bluetooth is enabled. The situation is becoming increasingly problematic as the API password is set to be deprecated and the recommended API encryption requires additional space.
@sairon
Copy link
Owner

sairon commented Feb 6, 2023

I already tried to port it, there are some parts of the code that would need to be rewritten, because they indeed use Arduino framework features, however the main blocker was that the ESP-IDF framework can not handle MQTT messages correctly. Today I created an issue reporting the misbehavior: esphome/issues#4133

Once the issue is resolved there is still some work to be done on my end, however I can not continue until the problem is resolved. There are some workarounds possible (e.g. introducing an artificial delay between the messages in the backend) but that is not the ideal way to proceed.

@sairon sairon added the enhancement New feature or request label Feb 6, 2023
@Scags104
Copy link

Following - same issues.

Thanks

@marek-vrana marek-vrana mentioned this issue Jul 25, 2023
Open
@PhiKapJames
Copy link

Looks like it was fixed last month. What work needs to be done that is left?

@sairon
Copy link
Owner

sairon commented Sep 19, 2023

@PhiKapJames The blocker is the display FW upload code, which uses HTTPClient library that is Arduino only. I did not have much time recently to invest into the rewrite effort - but maybe it could change in the following months. Also currently I can only presume it will address the issues with space constraints, because there is a chance that linking the HTTP APIs in ESP IDF (which are AFAIK not used in any other ESPHome component) will also cause the bloat.

@joBr99
Copy link

joBr99 commented Nov 20, 2023

@sairon Looks like the nextion upload code got ported to esp-idf

esphome/esphome#5667
https://github.com/esphome/esphome/tree/dev/esphome/components/nextion

@sairon
Copy link
Owner

sairon commented Nov 27, 2023

@joBr99 Nice, thanks for the heads-up! That should be fairly easy to port now, I will try to find a time slot for that soon.

@sairon sairon linked a pull request Dec 1, 2023 that will close this issue
Draft
@sairon
Copy link
Owner

sairon commented Dec 1, 2023

I have kicked off the ESP-IDF support in #33, I'll do some more testing and prepare a new release soon. Any other testers are welcome at this point 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add ESP-IDF support sairon/esphome-nspanel-lovelace-ui
5 participants
@sairon @rschueler @PhiKapJames @Scags104 @joBr99