Use of multiple VERSA3 watches to comunicate via Companion without phone

[Pepsy_SI]

Dear FitBit community and developers. We are developing app that communicates with local server over WiFi via WEB Socket IP.

Problem: WiFi on the watch is only used for updating firmware and side loading apps for development. This means in order for developed app to work is to send WebSocket API requests via Bluetooth (Companion) and telephone to WiFi and than our server. So every smart watch needs an phone or other Android device with WiFi, …

Is there any way to avoid using a phone with VERSA3 for FitBit app to internet communication:

Solution 1: Use of integrated Wi-FI – enable/unblock

• Are there physical reasons or other not to enable this type of direct communication.
• Can it be opened for Research reasons within Universities

Solution 2_A: Connection of multiple watches VERSA 3 via Bluetooth to single Android device – Single device with multiple Android Virtual Machines – to act as companion for all watches.

Solution 2_B: Connection of multiple VERSA 3 watches via Bluetooth to single device with single FitBit app but multiple accounts.

P.S.: What is the longest range of VERSA 3 Bluetooth.

Thank you very much for ANY suggestions or help!

[Rich_Laue]

Hi @Pepsy_SI I've moved your post to the developers board.

One issue I see is that WiFi is only turned on while the tracker is on its charger cable and charging.