search

thorrak / tiltbridge

Tilt Hydrometer to WiFi Bridge
http://www.tiltbridge.com/
Other
61 stars 27 forks source link

WiFi Connection Lost Repeatedly #171

Closed SillyHats closed 1 year ago

SillyHats commented 3 years ago

Somewhere between every few hours to once per day the tilt bridge loses connection to the wifi (WPA2) for multiple hours. Other devices on the network do not seem to have the same issue. When I push the reboot button on the device it reconnects immediately upon reboot.

I have tried using the Arduio IDE serial port monitor, but it outputs gibberish characters. When I try to run the serial port monitor using Visual Studio Code with Platform IO installed I get the following error message.

Executing task: C:\Users\you.platformio\penv\Scripts\platformio.exe device monitor <

--- Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time --- More details at http://bit.ly/pio-monitor-filters --- forcing DTR active --- forcing RTS active Error: [WinError 2] The system cannot find the file specified The terminal process "C:\Users\you.platformio\penv\Scripts\platformio.exe 'device', 'monitor'" terminated with exit code: 1.

Is there a guide somewhere I can follow to get the serial port monitor in Visual Studio/Platform IO working or another, correct way to diagnose what is going on?

The Tilt Bridge has lost connection to your WiFi. Attempting to reconnect... wifilost

using TTGO USB-C with v1.0.2 from brewflasher (web interface about page says 1.0.1)

lbussy commented 3 years ago

Well, that didn't quite work as expected. This part though:

18:56:54.523 -> *wm:[2] setSTAConfig static ip not set, skipping 
18:56:54.523 -> *wm:[1] Connecting to SAVED AP: MeshAP
18:56:55.034 -> *wm:[1] connectTimeout not set, ESP waitForConnectResult... 
18:57:05.022 -> *wm:[2] Connection result: WL_DISCONNECTED
18:57:05.022 -> *wm:[1] AutoConnect: FAILED

Popping that portal was not what I expected - but then again it should just have connected and as you can see above it failed. I wonder if there's not a bigger thing in play here.

I briefly considered allowing the device to participate in the mesh ... but then sanity took hold.

SillyHats commented 3 years ago

When you say allowing the device to participate in the mesh, do you mean connecting to the node with the best signal?

lbussy commented 3 years ago

No, the ESP32 libs actually have the capability to participate as a mesh node. I'm officially whacking that one as scope creep. :)

thorrak commented 1 year ago

I’m fairly certain this has been resolved in the latest releases of TiltBridge with the updated platform packages. Closing the issue for now — we can reopen if needed.