-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
device no response, serial monitor find 0 clients #181
Comments
I would like to try something. Can you try turn off modem and then turn on again please. I think it not work after that. So, I think it is problem of the issue. |
Same problem. It will lost control after a few days or weeks. Always clients:0. The only way is to turn off and turn on. unstable than son-off firmware. |
Problem solved. |
No, only erase this line
MDNS.close();
It’s under library file which i cant remember the name.
…Sent from my iPhone
On 3 Nov 2022, at 6:05 am, Jason Wang ***@***.***> wrote:
Sorry. I can't seem to find any code related to "mDNS restart" from the library. Do you mean this code block?
if (homekit_mdns_started) {
MDNS.close();
MDNS.begin(name->value.string_value, staIP);
INFO("MDNS restart: %s, IP: %s", name->value.string_value, staIP.toString().c_str());
MDNS.announce();
return;
}
and should the entire block be deleted?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.
|
thanks! works like a charm, at least for now. |
esp8266 works perfect once it connected in the beginning, but after several days, it will lost connections. just like those son-off devices i bought from TaoBao.
try to change modem settings such as , use certain channel, 2.4g only... the good news is: son-off devices never lose connections after i configure modem. but esp8266 still no response after a few weeks.
on esp8266 serial monitor, it saids: free heap: 42448, homekit clients:0
any suggestion what command i should use in serial monitor to figure our the problem?
The text was updated successfully, but these errors were encountered: