Closed Nickduino closed 2 months ago
The mDNS for ESP32 is not great in that I don’t think it sends the appropriate packets for .local resolution when the network reserves the domain. There could be something I am missing with it but it is supposed to be a couple of lines of code.
Essentially the gateway loses the reference. Using the ip address bypasses the name resolution and adding an ip reservation on the router that includes the hostname also fixes it.
I get the same errors when I connect to it with the IP address.
I mentioned the mDNS only because the message changes slightly when the connection to the device is completely impossible.
I added some additional TCP publishing on the v2.4.2 pre-release. Let's see where that takes us.
@Nickduino have you seen an improvement with this issue after installing v2.4.2 pre-release?
I can't really say for the moment as it's a very sporadic issue (that happens once a week or something like that) and I installed it only two days ago
@Nickduino please make sure you update to the official v2.4.2 release. There have been many improvements on the final release.
Done.
I haven't had any issue with the pre-release, though.
Hardware
ESP32-C3
Firmware version
v2.4.1
Application version
v2.4.1
What happened? What did you expect to happen?
This is relatively common (something like once a week) but I don't know what triggers it. Are you aware of that issue?
How to reproduce it (step by step)
Logs
No response