12-13-2021 05:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-13-2021 05:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello all,
I thought I'd have a go at making a basic "always on" clock for the Fitbit Versa 3. I've opened the SDK in the browser as instructed, then downloaded the simulator (Fitbit OS Simulator-latest-0.9.2.exe) as suggested.
There ends the progress.
I open the simulator and log in and set the studio.fitbit.com to look for the simulator, it says it is connected.
I've downloaded and built the sample project for clock face and it gives me errors:
1. This project is being built without a companion component. Create a file named companion/index.ts or companion/index.js to add a companion component to your project.
2. This project is being built without a settings component. Create a file named settings/index.tsx, settings/index.ts, settings/index.jsx or settings/index.js to add a settings component to your project.
I've read that these folders are optional so I assume the errors can be ignored BUT the run button is greyed out on the SDK so I cannot run anything.
What is wrong?
I'm a software engineer so I know my way about files and SDK's but this gives no hint as to what could be wrong. Grrr.

12-13-2021 06:08
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-13-2021 06:08
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I should also add that I have the simulator says The Device Bridge is disconnected and also that the Companion Bridge is connected to a debugger.
In the SDK web page whenever I hover over the Run icon it displays "Connect a device in order to run your app".
I can run the app on a real device but I don't want to yet, I'd like to get the simulator set up.

12-13-2021 06:17
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-13-2021 06:17
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Ignore all, it seems this is related to the Simulator SSL problem as already reported. I didn't think this was related.
Problem has gone.
12-13-2021 11:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


12-13-2021 11:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Glad to hear it.
Bear in mind that the 'always-on' API is only usable on real hardware by developers who have been specifically approved to do so by Fitbit. Even they can't install AOD products on their watches (eg, for testing) before they've been approved by Fitbit.
Gondwana Software
12-27-2021 18:08
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-27-2021 18:08
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Do you think you could run me through how you solved it? Im having troubles with this too

12-27-2021 18:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-27-2021 18:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Nevermind i was missing some code lol

