Timberwolf Server Set value. Fitbit Daily activity summary.

Store yesterdays total steps counted by Fitbit to Timeseries for display via Grafana

Connect

Doing sport regularly is even more motivating when you can also see a graph with your results and recognise your personal improvements and best times with one click. Fitbit is a great way to count your steps. Even better if you can analyse them precisely in Grafana. The Timberwolf Server supports recording of values and graphical analysis with Grafana. This applet sends the values from the previous day to the server. So that you can outdo yourself every day.

Create your own Fitbit and Timberwolf Server workflow

Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.

30 triggers, queries, and actions

Daily activity summary

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time your Fitbit tracker syncs for the first time today and your previous day's stats are available.

Daily calorie burn goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when you achieve your daily calorie burn goal.

Daily distance goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily distance goal.

Daily floors climbed goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.

Daily goal not achieved by __:__

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you do not achieve a daily goal you choose at the time you specify. NOTE: Updated on the first Fitbit tracker sync after the time you specify.

Daily step goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily step goal.

Daily very active minutes goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily very active minutes goal.

New sleep logged

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time your Fitbit logs new sleep.

New weight logged

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you log your weight in the Fitbit app or with the Aria scale.

Object value has changed

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a Timberwolf Server object has changed.

Sleep duration above

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you log sleep above the target hours you specify.

Sleep duration below

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you log sleep below the target hours you specify.

History of achieved very active minutes goals

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of events when you achieved your very active minute goals.

History of Daily Activity Summaries

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of Daily Activity Summary events from your Fitbit.

History of daily calorie burn goal achieved

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily calorie burn goal.

History of daily floors climbed goal achieved

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.

History of daily goal not being achieved by __:__

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you did not achieve a daily goal you chose by the time you specified. NOTE: Updated on the first Fitbit tracker sync after the time you specified.

History of daily step goal achieved

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily step goal.

History of Sleep duration above threshold

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of events when you logged sleep above the target hours you specified. Note: this query will only return future events after this Applet is created.

History of sleep duration below

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you log sleep below the target hours you specify. Note: this query will only return future events after this Applet is created.

History of sleep logged

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when your Fitbit logs new sleep.

History of Timberwolf object value changes

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This returns a list of value changes recorded after this query is created.

History of weight logged

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you logged your weight in the Fitbit app or with the Aria scale.

History of when the daily distance goal was achieved

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you have achieved your daily distance goal.

Log your weight

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This Action will log a new weight measurement to Fitbit.

Set value

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
Set a Timberwolf Server object to a specified value. The selected Timberwolf Server will convert the textual value to the datatype of the target object. You can connect the target object to another subsystem like KNX, 1-Wire, Modbus, MQTT, HTTP or Timeseries

Switch off

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set a boolean Timberwolf object false.

Switch on

Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will set a boolean Timberwolf object true. You may connect the object on your Timberwolf Server to other services like KNX, 1Wire, Modbus oder MQTT.

Daily activity summary

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time your Fitbit tracker syncs for the first time today and your previous day's stats are available.

Daily calorie burn goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires when you achieve your daily calorie burn goal.

Daily distance goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily distance goal.

Daily floors climbed goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.

Daily goal not achieved by __:__

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you do not achieve a daily goal you choose at the time you specify. NOTE: Updated on the first Fitbit tracker sync after the time you specify.

Daily step goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily step goal.

Daily very active minutes goal achieved

Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This Trigger fires every time you achieve your daily very active minutes goal.

History of achieved very active minutes goals

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of events when you achieved your very active minute goals.

History of Daily Activity Summaries

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of Daily Activity Summary events from your Fitbit.

History of daily calorie burn goal achieved

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily calorie burn goal.

History of daily floors climbed goal achieved

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you achieve your daily floors climbed goal. NOTE: only available for Fitbit Ultra and One.

History of daily goal not being achieved by __:__

Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of when you did not achieve a daily goal you chose by the time you specified. NOTE: Updated on the first Fitbit tracker sync after the time you specified.

More on Fitbit and Timberwolf Server

About Fitbit

Fitbit designs products to track everyday health and fitness, empowering and inspiring people to lead healthier, more active lives. Turn on Applets to track your fitness and sleep goals, build healthier habits, and sync your fitness data to hundreds of other services.

Learn more

More integrations with Fitbit

About Timberwolf Server

The Timberwolf Server is a very powerful multi-protocol gateway with visualisation, logic, Influx time series database, graphical analysis with Grafana and extensible with Docker Containers.

The Timberwolf Server locally supports 10 protocols in parallel with tens of thousands of data points that can be linked and recorded at will with each other and with other IFTTT services.

Cloud based services meets local Smarthome installation.

Documentation about Timberwolf Server integration with IFTTT

Learn more

More integrations with Timberwolf Server