Describe the bug
Sleep below 3 hours is not recognized

To Reproduce
Sleep less than 3 hours and FitBit will not show Deep, Light, REM, and Wake times. But FitBit will show sleep times!

Expected behavior
Sleep times should be shown anywhere

Screenshots & Logfiles

Versions:

• Adapter version: 0.4.8
• JS-Controller version: 4.0.23
• Node version: 16.18.1
• Operating system: Docker Container

Think about update stable version to 0.4.11

Version: stable=0.4.10 (236 days old) => latest=0.4.11 (15 days old)
Installs: stable=124 (79.49%), latest=21 (13.46%), total=156

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

This adapter seems to be incompatible with js-controller 5

See https://forum.iobroker.net/topic/68328/fitbit-app-l%C3%A4uft-mit-js-controller-5-0-12-nicht-mehr

Any adapter listed at latest or stable repository MUST use the standard github based tests provides by test-and-release worklow. And of course those tests must pass (green mark at github main page)

This adapter still tries to use node 12 and 14 which are no longer supported.

see PR #15 for a fix

Think about update stable version to 0.4.13

Version: stable=0.4.10 (271 days old) => latest=0.4.13 (15 days old)
Installs: stable=122 (78.71%), latest=21 (13.55%), total=155

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Hallo, was ist genau damit gemeint?
Muss ich dem Entwickler mein Account freigeben?

Why i did not see the heartbeat?

Think about update stable version to 0.4.7

Version: stable=0.4.6 (87 days old) => latest=0.4.7 (78 days old)
Installs: stable=52 (70.27%), latest=16 (21.62%), total=74
Click to edit

Beta ist 0.4.9
und latest ist 0.4.10 !?

hier festgestellt :
https://forum.iobroker.net/topic/63087/fitbit-adapter-l%C3%A4sst-sich-nicht-updaten

bei BETA : http://repo.iobroker.live/sources-dist-latest.json

bei STABLE: http://repo.iobroker.live/sources-dist.json

Hi .. thanks for this adapter .. from the old adapter the only object I used was the battery object .. would it be possible to add this here too?

Best regards

Beim versuchen den Token updaten bekomme ich diese Fehler Version 0.4.9
und Adapter bleibt Rot

Screenshots & Logfiles

Versions:

• Adapter version: v0.4.6
• JS-Controller version: 4.0.23
• Node version: v14.21.1
• Operating system: Raspbian GNU/Linux 10 (buster)

Additional context
The adapter doesn't sync any body or food data.

Is this a known behavior?

Thanks

Hello,

you can see my problem already in the screenshot. Some values are not retrieved. The token is up to date. Do you have any idea what else I can try?

• Adapter version: v0.4.6
• JS-Controller version: 4.0.23
• Node version: v16.17.0
• Operating system: Docker (unraid)

with actual js-controller 5.x Alpha this issue appears, the adapter crashed:

2023-04-06 10:52:54.815 - info: host.iobrokerS2 instance system.adapter.fitbit-fitness.0 started with pid 13160 2023-04-06 10:52:54.815 - info: host.iobrokerS2 instance system.adapter.fitbit-fitness.0 started with pid 13160 2023-04-06 10:52:55.535 - debug: fitbit-fitness.0 (13160) Redis Objects: Use Redis connection: 10.1.1.1:6379 2023-04-06 10:52:55.555 - debug: fitbit-fitness.0 (13160) Objects client ready ... initialize now 2023-04-06 10:52:55.556 - debug: fitbit-fitness.0 (13160) Objects create System PubSub Client 2023-04-06 10:52:55.557 - debug: fitbit-fitness.0 (13160) Objects create User PubSub Client 2023-04-06 10:52:56.062 - debug: fitbit-fitness.0 (13160) Objects client initialize lua scripts 2023-04-06 10:52:56.066 - debug: fitbit-fitness.0 (13160) Objects connected to redis: 10.1.1.1:6379 2023-04-06 10:52:56.089 - debug: fitbit-fitness.0 (13160) Redis States: Use Redis connection: 10.1.1.1:6379 2023-04-06 10:52:56.096 - debug: fitbit-fitness.0 (13160) States create System PubSub Client 2023-04-06 10:52:56.097 - debug: fitbit-fitness.0 (13160) States create User PubSub Client 2023-04-06 10:52:56.103 - debug: fitbit-fitness.0 (13160) States connected to redis: 10.1.1.1:6379 2023-04-06 10:52:55.535 - debug: fitbit-fitness.0 (13160) Redis Objects: Use Redis connection: 10.1.1.1:6379 2023-04-06 10:52:55.555 - debug: fitbit-fitness.0 (13160) Objects client ready ... initialize now 2023-04-06 10:52:55.556 - debug: fitbit-fitness.0 (13160) Objects create System PubSub Client 2023-04-06 10:52:55.557 - debug: fitbit-fitness.0 (13160) Objects create User PubSub Client 2023-04-06 10:52:56.062 - debug: fitbit-fitness.0 (13160) Objects client initialize lua scripts 2023-04-06 10:52:56.066 - debug: fitbit-fitness.0 (13160) Objects connected to redis: 10.1.1.1:6379 2023-04-06 10:52:56.089 - debug: fitbit-fitness.0 (13160) Redis States: Use Redis connection: 10.1.1.1:6379 2023-04-06 10:52:56.096 - debug: fitbit-fitness.0 (13160) States create System PubSub Client 2023-04-06 10:52:56.097 - debug: fitbit-fitness.0 (13160) States create User PubSub Client 2023-04-06 10:52:56.103 - debug: fitbit-fitness.0 (13160) States connected to redis: 10.1.1.1:6379 2023-04-06 10:52:58.489 - info: fitbit-fitness.0 (13160) starting. Version 0.4.10 (non-npm: Chris-656/ioBroker.fitbit-fitness) in /opt/iobroker/node_modules/iobroker.fitbit-fitness, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230406-4552d569 2023-04-06 10:52:58.550 - debug: fitbit-fitness.0 (13160) Getting refresh Token: c817bd62dd39ec8ed529fc0d16396a1xxxxxxxx 2023-04-06 10:52:58.803 - info: fitbit-fitness.0 (13160) User logged in B...l id:xxxx8 2023-04-06 10:52:58.808 - debug: fitbit-fitness.0 (13160) Tokens checked 2023-04-06 10:52:59.041 - info: fitbit-fitness.0 (13160) Activity Records: Steps:0 Floors:undefined Calories:1884 2023-04-06 10:52:59.047 - error: fitbit-fitness.0 (13160) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2023-04-06 10:52:59.047 - error: fitbit-fitness.0 (13160) unhandled promise rejection: undefined is not a valid state value 2023-04-06 10:52:59.049 - error: fitbit-fitness.0 (13160) Error: undefined is not a valid state value at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/maybeCallback.js:35:17) at FitBit._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5332:49) at FitBit.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5293:21) at FitBit.setActivityStates (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:321:9) at FitBit.getActivityRecords (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:305:15) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async FitBit.getFitbitRecords (/opt/iobroker/node_modules/iobroker.fitbit-fitness/main.js:87:5) 2023-04-06 10:52:59.049 - error: fitbit-fitness.0 (13160) undefined is not a valid state value 2023-04-06 10:52:59.057 - info: fitbit-fitness.0 (13160) terminating 2023-04-06 10:52:59.058 - warn: fitbit-fitness.0 (13160) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-04-06 10:52:59.277 - info: fitbit-fitness.0 (13160) Body records: Weight:10.5 Fat:11.342750549316406 BMI:20.1 2023-04-06 10:52:59.559 - info: fitbit-fitness.0 (13160) terminating 2023-04-06 10:52:59.612 - error: host.iobrokerS2 instance system.adapter.fitbit-fitness.0 terminated with code 6 (UNCAUGHT_EXCEPTION)