Range Extender driver xdrv_58_range_extender does not compile with core 3.0.0

[Jason2866]

Details of failing can be seen in this GH Actions run https://github.com/Jason2866/Tasmota-build/actions/runs/8704050149/job/23871521878

@joba-1 @sillyfrog can you have a look and adopt to IDF5.1 / Arduino core 3.0.0?

[joba-1]

At first glance: tcpip_adapter API discontinued and replaced by ESP-NETIF :(
See https://docs.espressif.com/projects/esp-idf/en/release-v5.1/esp32/migration-guides/release-5.x/5.0/networking.html?highlight=tcp#tcp-ip-adapter

No idea how much changed. Maybe it is more or less search&replace ... and testing.

Could you please make it easy for me and post a platformio.ini or (a link to) instructions to compile locally with this new stuff? What I have working is VS Code on Linux with PlatformIO Extension and a cloned tasmota. I guess I just have to replace some platform or framework entries?

[Jason2866]

Do a fresh clone of Tasmota in a different folder. Don't use your existing setup it may conflicts since the platformio setup has changed. You can use this env

[env:tasmota32-rangeextender]
extends                     = env:tasmota32_base
build_flags                 = ${env:tasmota32_base.build_flags}
                              -DFIRMWARE_TASMOTA32
                              -DUSE_WIFI_RANGE_EXTENDER
                              -DUSE_WIFI_RANGE_EXTENDER_NAPT
lib_ignore                  =
                              TTGO TWatch Library
                              Micro-RTSP

best is to place in file platformio_tasmota_cenv.ini

[joba-1]

Thanks,, worked - seen the same errors last evening.
Changes are definitely not just cut&paste - will need time.
For now I did not even find a way to get the ip addresses of connected clients.
Another thing is, for some non-arduino api calls you need a net device. Not sure yet where this is buried in arduino, in case I need it.
The migration "guide" is far from complete :(

[github-actions]

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[sillyfrog]

I noticed this has been marked stale. I have this on my radar, but it'll be a little bit before I'll have time to look at it properly... Let me know if you get very far in the meantime. Thanks!

[joba-1]

sure, I‘ll let you know of any progress (or problems, in case you have an idea). Earliest next week, nothing new so far.

[github-actions]

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[sfromis]

Unstale, builds still failing

[github-actions]

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[sfromis]

Any hope of getting this feature refactored to match the API change?

[github-actions]

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[sfromis]

unstale

[github-actions]

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

[sfromis]

Tickle

[fdaubercy]

Hi.
I always have to run my rangeextender with a version older than the current one. Compiling with this option still doesn't work.
Frédéric

[Jason2866]

@fdaubercy Thats why this issue is open ;-)

[Jason2866]

Closing should be solved with #22205

[sillyfrog]

Thank you all (@Jason2866 @pharaocurt ) for helping get this sorted! (Sorry I never had a chance to get back into it).