Skip to content

[Bug]: Diagnostic report #76

Closed
Closed

Description

@Tiwas

Problem summary

Diagnostic report

Steps to reproduce

Ran flow to turn on all lights

Expected behavior

For all lights to be turned on

Actual behavior

Only some lights were turned on

App version

1.10.35

Diagnostic report

Smart (Components) Toolkit diagnostic report

  • Generated: 2026-10-11T17:51:01.113Z
  • App version: 1.10.35
  • Node.js: v22.23.3
  • Current session started: 2026-10-11T01:33:26.649Z
  • Current session uptime: 16h 17m 34s
  • Debug mode: enabled
  • App state: running
  • Homey-reported crash count: 0
  • Process error handlers before app start: unhandledRejection 1, uncaughtException 1

Resource load

  • App process memory: RSS unavailable, heap used unavailable of unavailable
  • Memory samples this session (UTC time heap/RSS MB): 16:33 20.9/?, 16:48 21.2/?, 17:03 21.4/?, 17:18 20.9/?, 17:33 21.0/?, 17:48 21.4/?
  • Previous session: started 2026-10-10T02:01:06.438Z, last heartbeat 2026-10-11T01:16:12.841Z, clean shutdown no; heap/RSS MB 21:31 20.3/? -> 01:16 20.4/? (16 samples)
  • Homey-reported app memory: 106.7 MB
  • Homey-reported app CPU metric: 0.000000
  • Homey system load average (1 / 5 / 15 min): 0.28 / 0.33 / 0.32
  • Homey memory: 2597.4 MB used of 7870.6 MB (5273.2 MB free, 33.0% used)
  • Homey storage: 1981.6 MB used of 2534.7 MB (553.1 MB free, 78.2% used)

Device load

  • App devices: 11
  • Devices with configuration alarm: 3
  • Homey registry snapshot: 110 current / 113 known / 3 deleted
  • Driver circadian-light-group: 2
  • Driver circadian-light-group-collection: 1
  • Driver composite-device: 0
  • Driver logic-device: 3
  • Driver logic-unit: 2
  • Driver logic-unit-10: 1
  • Driver logic-unit-2: 1
  • Driver logic-unit-3: 1
  • Driver logic-unit-4: 0
  • Driver logic-unit-5: 0
  • Driver logic-unit-6: 0
  • Driver logic-unit-7: 0
  • Driver logic-unit-8: 0
  • Driver logic-unit-9: 0
  • Driver state-capture-device: 0
  • Driver state-device: 0

Circadian Light Group load

  • Group 1: 5/5 members enabled; update 120s; transition

Setup details shortened to preserve the newest diagnostics.

Recent warnings and errors

  • 2026-10-11T17:35:39.760Z [ERROR] [CircadianLightGroup] Circadian member update failed during timer.
at Remote Process
  • 2026-10-11T17:37:40.733Z [ERROR] [CircadianLightGroup] Circadian member update failed during timer.
at Remote Process
  • 2026-10-11T17:39:40.055Z [ERROR] [CircadianLightGroup] Circadian member update failed during timer.
at Remote Process
  • 2026-10-11T17:41:40.115Z [ERROR] [CircadianLightGroup] Circadian member update failed during timer.
at Remote Process
  • 2026-10-11T17:43:39.830Z [ERROR] [CircadianLightGroup] Circadian member update failed during timer.
at Remote Process
  • 2026-10-11T17:44:27.459Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified off after retries.
  • 2026-10-11T17:44:29.230Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified off after retries.
  • 2026-10-11T17:45:34.405Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified on and at target after retries.
  • 2026-10-11T17:47:02.735Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified on and at target after retries.
  • 2026-10-11T17:47:36.955Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified on and at target after retries.
  • 2026-10-11T17:48:47.582Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified on and at target after retries.
  • 2026-10-11T17:50:40.523Z [WARN] [CircadianLightGroup] 1 Circadian member(s) could not be verified on and at target after retries.

Privacy notice

Device names and IDs are intentionally omitted from the structured data. Common identifiers and secrets are redacted from captured log lines, but please review this report before submitting it.

Activity

  1. Tiwas commented on Oct 28, 2026

    @Tiwas
    OwnerAuthor

    Fixed in v1.10.36 and included in v1.10.38 on the test channel (#77).

    Root cause: the Circadian Light Group Collection's Is paused condition only read the Collection's own pause flag. While one of its member groups was paused, the "All on" Flow took the not paused branch and skipped Resume. The Collection turn-on then skipped every light in the paused group.

    Fix: Is paused on a Collection now returns yes when the Collection itself or at least one available member group is paused. Resume still resumes every member group. A live retest with the same Advanced Flow took the correct branch, resumed both groups and turned the skipped lights on.

    The remaining warnings in the report ("could not be verified on and at target after retries") come from individual lights that were unreachable or did not acknowledge commands. Those are device or mesh problems, not app bugs, and the Error occurred trigger still reports them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions