I'm having exactly the same issue and, in my case, I have indeed entered the correct IP address.
It's a non-secure HTTP connection and it works with a different http server I tried (Apache based). I just setup a default IIS service http server on Windows, and I get this failure.

E (49098) esp-tls ...

According to the ESP32-DEVKITC-V4 documentation , the onboard LED means that 5V is being applied to the module on pin 19. Is that not the case?

If the LED is fluctuating in intensity, that doesn't sound good. Did you say that HA is still recognizing the ESP32 so it seems to be functioning at least ...

Thanks nopnop2002 . What you describe explains what I'm seeing. I don't recall doing anything but a "default" procedure installing ESP-IDF on either platform, but on the virtual box, it must have gone down the "make" path. It's functioning properly, so I may leave it be ("let a sleeping dog lie ...

I don't know what caused it, but it's very interesting.
Is it possible that the versions of ninja installed on the two PCs are different?
$ ninja --version
1.11.1


Is it possible that my environment uses an alternative to ninja? It is not in one of my .espressif installations. This is the one ...

Is it possible that the versions of ESP-IDF installed on the two PCs are different?
You can check the ESP-IDF version with this command.

$ idf.py --version
ESP-IDF v5.5.3-dirty


Good question! They both show ESP-IDF v5.5.3.
It seems like there must be some kind of option or something that ...

Were you actually getting an error message for the deprecated function or was it a warning message? Usually when a function becomes deprecated, you're given a considerable amount of time to adapt the replacement function(s).

I have esp-idf 5.5.3 installed on two different machines. I might have installed them using the same procedure, I don't recall. But I did not set any special options or anything.

I've been through a lot of esp-idf upgrades and installs, and when I do an "idf.py build" it has always shown the ...

Some time ago, when I was running ESP IDF 4.3, I had an issue in which my device would automatically disconnect from the wifi router and I needed to reboot the unit for it to reconnect.

I then wrote my own wifi event handler and printed the failure code on the console, which was a MIC error ...

I noticed a setting of the value CONFIG_IDF_INIT_VERSION in my sdkconfig recently. It seems to indicate a prior version of ESP-IDF that I may have used. But I can't find any documentation on it or find any information about how it gets set.

What is the purpose of this configuration setting?

I think the idea of adding the same device as two different slaves may be the way to go, just treating the two different addresses as if they are for two different chips. That's what I would try anyway.