When connecting with the Chorus Android app over wifi it always connects to the default gateway IP, assuming the wifi AP is the Chorus device. However, with Chorus32 in client mode, it can be any IP address. When whooping at home, the range of the ESP32's wifi is spotty back to my phone so the connection tends to drop off and go back to the other wifi network, which breaks the lap timer.
I think ideally it should do an mDNS query to find the lap timer on the network, but a good substitute would be to just let the user enter the IP or hostname of the timer device. I believe the hostname "chorus32" would just work for both AP and STA mode.
When connecting with the Chorus Android app over wifi it always connects to the default gateway IP, assuming the wifi AP is the Chorus device. However, with Chorus32 in client mode, it can be any IP address. When whooping at home, the range of the ESP32's wifi is spotty back to my phone so the connection tends to drop off and go back to the other wifi network, which breaks the lap timer.
I think ideally it should do an mDNS query to find the lap timer on the network, but a good substitute would be to just let the user enter the IP or hostname of the timer device. I believe the hostname "chorus32" would just work for both AP and STA mode.