Skip to content

HS60C not identified as HS60C — stuck as type 0 (unrecognized), brightness/CCT don't work #110

Open

Description

@jonpikereally

Light: Neewer HS60C

Despite the HS60C profile being merged in #108, my light is not being identified/matched to it.

Steps taken:

  • Deleted local light database (Settings → Delete Local DB)
  • Re-synced database (Settings → Sync Database Now)
  • Removed the light from NeewerLite's device list ("forget")
  • Rescanned/reconnected via Bluetooth

Result: light still shows as name -307BF6 (its MAC suffix) with type: 0 in the Control View, both before and after the above steps.

Behavior:

  • Power on/off: works
  • Brightness / CCT: no effect on the physical light
  • Command pattern editor (gear icon → Update command patterns): empty for this light
  • The official Neewer app controls brightness/CCT on this same light correctly over Bluetooth, so the light and connection are fine.

NeewerLite version: v1.9.3 (33)

This looks like the BLE advertisement matching logic isn't recognizing this specific HS60C unit against the new database entry, even though the profile exists in Database/lights.json.

Activity

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