This is likely due to the MDNS problem that seems to plague different configurations in different ways. I assume you are using the Home Pod Mini as a HomeKit Hub? If so, when the device shows no response in the Home App, can you check to see if any sockets are connected to the device by typing 's' into the Serial Monitor. My guess is that it will show that none of the sockets are connected.

If that's true, can you try the following test: Add the following line to the setup() portion of your sketch:

new SpanUserCommand('D', " - disconnect WiFi", [](const char *buf){WiFi.disconnect();}); 

This allows you to force a WiFi disconnect by typing @D into the Serial Monitor. When you start receiving a no-response error from the Home App, type @D. HomeSpan will disconnect from WiFi, and then automatically re-connect after a second or two. What we want to test is whether forcing a WiFi re-connect cures the MDNS problem.

Thanks for the quick response and help, will try it out and revert one I complete this step

First of all, thank you for the great library — it’s been working very reliably in my project.

I noticed that when typing s in the Serial Monitor, HomeSpan prints the list of active sockets / connections, which is very helpful for debugging cases where the Home app shows “No Response” even though Wi-Fi and local logic are still running.

I’d like to ask a clarification question:

Is the socket / connection count that is shown by the s command accessible programmatically from user code?

Or is it intentionally exposed only via the Serial Monitor for manual debugging?

My goal is to implement a very conservative, non-intrusive recovery mechanism (e.g. forcing a Wi-Fi reconnect only after many hours with zero HomeKit connections), but I want to do this only using supported and stable APIs.

If there is a recommended HomeSpan-native way to observe HomeKit connectivity status (even indirectly), I’d appreciate any guidance.

Thanks again for maintaining HomeSpan and for your time.

There is currently no function call to return the number of active socket connections (i.e. the number in the 's' command), but I think this is a good idea. Let me give some thought into the best way add an API for some form set of global "status" flags that could be monitored by the user directly in a sketch (maybe include whether WiFi is connected, Ethernet is connected, number of sockets, whether device is paired, etc.). Could also add some logic to reboot directly if WiFi is on, pairing is on, and there has been no socket connectivity for a specified amount of time.

Thanks for the explanation.
In my real usage, I often see “No Response” in the Home app while the device is still connected to Wi-Fi and running normally. This makes it hard to detect the problem from sketch code, and it seems likely related to mDNS or HomeKit session issues, not Wi-Fi itself.
If HomeSpan could expose some read-only status flags (Wi-Fi/paired state, socket activity, etc.), it would make it much easier to implement safe and conservative recovery logic (e.g. a Wi-Fi reconnect instead of a reboot).
Thanks again for considering this and for maintaining HomeSpan.