RADAR fitbit connector version 0.3.0

Changes since 0.2.5

• Add version property to the user so it can be reset.
• Use HTTPS in repo URLs
• Adds support for adding users from the Firestore database.
• Adds support for pending updates from user repositories. This gives more control to user repositories on how the users are updated. Enables real-time updates from Firestore.

This introduces a security vulnerability through com.google.firebase:firebase-admin:6.12.2. This should be updated when a new version is released. #56 has been added to track this.

RADAR fitbit connector version 0.2.4

• Adds Fitbit intraday Calories and Activity

RADAR fitbit connector version 0.2.3

Changes since version 0.2.2:

• Reverts bug introduced in 0.2.2: replace findFirst to run request with an Iterator after which to run the request. By using calls with side-effects in streams, Java streams was preloading a lot of URLs without evaluating the findFirst and data was lost in that way.
• Fix security issues
• Make polling time per user route configurable

*Deprecated* RADAR-REST-Connector version 0.2.2

Deprecated Use version 0.2.3 instead.

Changes since version 0.2.1:

• Updated dependencies
• Added rest authoriser docker-compose.yml example
• Return any polled records immediately, instead of accumulating them.
• Fixed NPE when the user details in the user authorizer backend are not yet complete (fixes #39)

radar-rest-connector version 0.2.1

Changes since version 0.2.0:

• Added activity log topic (#12)
• Fixed backoff period (#14)
• Updated dependencies
• Using intraday data is configurable with fitbit.api.intraday
• Avoid using Instant.MIN and Instant.MAX to prevent int out of bounds errors when adding and subtracting
• If too many requests are made, do not try to make more requests for that user.

Release 0.2.0

Changes from Release 0.1.0

• Adds integration to a authorization webservice to get user information and access token. This can be used by adding

fitbit.user.repository.class=org.radarbase.connect.rest.fitbit.user.ServiceUserRepository
fitbit.user.repository.url=<url-to-authorization-service>

• Adds python-script to automatically authorize set of fitbit users and create files with user-properties to be used by the connector.

Release 0.1.0

A generalised REST source connector:

• Requests are generated by a request generator
• A request generator can have multiple request routes (e.g. URL's), that are themselves request generators
• A specialisation of a route is a polling route, that is expected to regularly poll a URL.
• Use OkHttp3 for HTTP handling

Made a generalised Fitbit source connector:

• Fitbit user registration is done outside of the connector, managed by a FitbitUserRepository.
  • Its default implementation just reads and writes data from a directory using YAML files. It also refreshes any OAuth2 tokens when necessary.
• With a FitbitRequestGenerator that has 4 routes:
  1. intraday heart rate
  2. intraday steps
  3. sleep
  4. time zone
• Each of the routes is a FitbitPollingRoute, with a separate polling counter per Fitbit user. It features a full historical pull for the first iteration, after which only the most recent history is polled. If data is added more recently than before-yesterday, no new data is expected for earlier than before-yesterday. If no data was added since 14 days, earlier days are also not reinspected.
• Data for each of the route is converted to Avro using RADAR Schemas.
• The connector backs off for a given user if the server indicates that too many requests are being made.
• Offsets are committed to the offset file, which is also read on startup.

Available under open source Apache License version 2.0