10-18-2022 03:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-18-2022 03:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Considering that the companion app is not always available to users especially during battery optimizations or sometimes just not running in the background or foreground.
Is there a way we can communicate through the fitbit App using it's wiFi capabilities to external APIs.
or via it's notifications channel?

10-18-2022 12:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-18-2022 12:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
No, That is not possible. What I use is filetransfers. If the companion app starts again, the files are sent. Make sure your companion doesnt close be adding the following lines.
import { me } from "companion"
me.appTimeoutEnabled = false; // Disable timeout

10-18-2022 12:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


10-18-2022 12:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Are you sure appTimeoutEnabled is for the companion? My understanding is that it prevents apps (as opposed to clockfaces) being closed after 2 minutes on the watch.
You can use wake interval to get the companion to run periodically, although it should be woken automatically when it receives a file from the watch.
Gondwana Software

10-18-2022 12:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-18-2022 12:30
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I am actualy not sure. That code is my app for 4 years now, havent looked at it. My app performs like it should and files are sent always. Looking at the Docs, I think you are right.
