Migrate to ESP-IDF 5.x and Arduino 3.x

[mairas]

The Espressif and PlatformIO are in an unfortunate staring contest wrt. supporting Arduino Core 3 and ESP-IDF 5.x in PlatformIO. As a result, the ESP32 Arduino Core in PlatformIO isn't getting updates or bugfixes which I would like to use in SensESP. Given that a new pioarduino project has emerged to bridge this gap, SensESP should probably adopt it. Using the updated platform requires only a one-liner change in plaformio.ini for the end user, but the changes in the framework itself require some trivial fixes in SensESP itself.

I don't yet know whether it is feasible to try to support both Arduino core versions simultaneously.

[mefenlon]

I think this is related to a problem I reported over at SensESP/SensESP-project-template#6 (comment)

A few days ago, I started getting a build error

fatal error: esp_websocket_client.h: No such file or directory

It looks like some issues have come up for platformio
platformio/platform-espressif32#1225 (comment)

[CaptIgmu]

With migration to pioarduino to circumvent PlatformIO troubles, there is now a compile problem:
fatal error: esp_websocket_client.h: No such file or directory

That is because in ESP-IDF 5.x, esp_websocket_client.h has moved to espressif/esp-protocols/components/esp_websocket_client/include

Trying to "point at it" with include directories or adding the necessary files to a project src folder didn't work for me. There will have to be a fundamental SensESP change.

Mairas, Thanks for all your work!

[mefenlon]

@CaptIgmu you can use this workaround.
Use this for your project as a template: https://github.com/SignalK/SensESP/blob/main/examples/platformio.ini

Chgange lib_deps to use the git repository rather than the release

lib_deps =
  https://github.com/SignalK/SensESP.git

[CaptIgmu]

Wow! That worked!
Looks like major changes in the platformio.ini file for SensESP.

I was still getting compile errors in my program using SensESP/OneWire, had to update my program based on the latest example:
using namespace reactesp;
using namespace sensesp;
using namespace sensesp::onewire;

Thanks for your help, I can now explore my Halmet, but now I'm intrigued about the Halser . . .

[ErikDLundberg]

@mefenlon I am using a FireBeetle 2 ESP32-E, and have been battling the esp_websocket_client.h problem. Up-front, I will say that I am pretty much a novice with PlatformIO. I tried the work around you suggested in this thread on Mar 10...

• As a template, I used: https://github.com/SignalK/SensESP/blob/main/examples/platformio.ini
• Then I set: default_envs = espidf_esp32
• And used the github repository, rather than the release: lib_deps = https://github.com/SignalK/SensESP.git

And I get this error when PlatformIO tries to resolve the dependencies: "Detected a whitespace character in project paths."

I then tried pegging the espressif platform to an earlier version, as you had suggested in Issue #6 , but still no joy: platform = espressif32@5.1.0

And with regard to that last point (and I admit that I am sort of blundering around here, because I don't fully understand the platform!), there are two spots where I pegged the espressif32 platform... in the [arduino] platform configuration and in the [espidf] platform configuration, just for good measure.

Any thoughts here?
Thanks in advance!

[mefenlon]

@ErikDLundberg sorry for the late reply. I am no expert on this, but I have some thoughts on your issue.

Version 3.1.0 was released so my workaround to set lib_deps is no longer necessary.

I would suggest getting a fresh copy of the current platform.ini file from the current repo https://github.com/SignalK/SensESP/blob/main/platformio.ini

The only change you should have to make in the platform.io file is setting the environment at the top of the file

; Change the default environment to match your board. Valid options are:
; - arduino_esp32
; - pioarduino_esp32
; - espidf_esp32
; - pioarduino_esp32c3
; - espidf_esp32c3
; - shesp32
; - halmet
; - halser

default_envs = pioarduino_esp32

I don't have any experience with the FireBeetle 2. I think you could get away at leaving it at the default value unless you know for sure which env the firebeatle is.

I use a halmet so as an example I would change that one line to

; Change the default environment to match your board. Valid options are:
; - arduino_esp32
; - pioarduino_esp32
; - espidf_esp32
; - pioarduino_esp32c3
; - espidf_esp32c3
; - shesp32
; - halmet
; - halser

default_envs = halmet

It sounds like you might have some dependency/package issues, so start from an empty directory and a new project just to make sure you are starting clean.

It might be worth looking at the troubleshooting steps for platformio
https://docs.platformio.org/en/latest/faq/troubleshooting.html#package-manager