You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have up to 8 servers and 1 client. All are running on ESP32. The servers are identical using esp-nimble-cpp. The client uses Nimble-arduino.
The client runs a task that wakes every second to find any unknown servers that it should have. It also connects any known servers that have disconnected.
If the server is not connected, it advertises. When connected, it sends a data every 2 seconds with notify(), with a light sleep in between.
This works, except when I restart the client. It remembered the clients, so it connects with each, get the service and characteristic so that it can listen for the notify. Sometimes it fails to get the service. It connects to the server quickly, then waits many seconds and finally fails to return the service. The server behaves for a short while as if it is connected, sending the notify, then concludes it has no connection and advertises.
I could use some clues as to what might be going on. It feels like there might be some state information in the server that needs to be reset.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have up to 8 servers and 1 client. All are running on ESP32. The servers are identical using esp-nimble-cpp. The client uses Nimble-arduino.
The client runs a task that wakes every second to find any unknown servers that it should have. It also connects any known servers that have disconnected.
If the server is not connected, it advertises. When connected, it sends a data every 2 seconds with notify(), with a light sleep in between.
This works, except when I restart the client. It remembered the clients, so it connects with each, get the service and characteristic so that it can listen for the notify. Sometimes it fails to get the service. It connects to the server quickly, then waits many seconds and finally fails to return the service. The server behaves for a short while as if it is connected, sending the notify, then concludes it has no connection and advertises.
I could use some clues as to what might be going on. It feels like there might be some state information in the server that needs to be reset.
Beta Was this translation helpful? Give feedback.
All reactions