Skip to content

Calibration never finishes; received messages show “no corresponding entity found” #26

Description

@saiepour

Hello,

I am trying to use the Schellenberg USB integration with a Schellenberg USB Funk-Stick 21009 / ENAS on Home Assistant.

System information:

Home Assistant OS: 18.1
Home Assistant Core: 2026.7.0
Architecture: aarch64 Raspberry Pi
HACS: 2.0.5
Schellenberg USB integration: v1.0.1 from HACS
USB stick: Schellenberg ENAS / 21009
Serial path: /dev/serial/by-id/usb-schellenberg_ENAS_000000000000-if00

The USB stick itself seems to work:

  • Home Assistant recognizes the stick.
  • The Schellenberg USB integration loads.
  • The LED entity of the USB stick can be controlled.
  • The integration receives Schellenberg radio messages.

The problem is with adding/calibrating blinds.

Pairing starts and the integration seems to detect the shutter, but during the range calibration step the process never finishes. Because calibration does not complete, no blind/cover entity is saved in Home Assistant.

I attached schellenberg_logs.txt.

The important repeated warnings are like:

Received message for device 3720B8 (enum=08, cmd=02) but no corresponding entity found. The device may need to be added to Home Assistant.

Received message for device 3720B8 (enum=08, cmd=01) but no corresponding entity found. The device may need to be added to Home Assistant.

Received message for device 3720B8 (enum=08, cmd=00) but no corresponding entity found. The device may need to be added to Home Assistant.

Other devices/enums also appear in the log, for example:

F2B8D5 enum=23
F2B8D5 enum=13
06C5C0 enum=0D
3720B8 enum=08

So the USB stick is clearly receiving radio traffic, but the integration does not create or match the corresponding Home Assistant cover entity.

My questions:

  1. Is there a way to manually add a blind entity using device ID and enum, for example 3720B8 and enum=08, without completing the calibration wizard?

  2. Is the calibration step expected to create the entity only after successful range detection?

  3. Could this be a compatibility issue with Home Assistant Core 2026.7.0, Python 3.14.6, or the Schellenberg Premium tube motors?

  4. Is there any additional debug logging I can enable to help diagnose why calibration never completes?

Thank you very much for this integration.

schellenberg_logs.txt

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