Improve blind setup, calibration, and status tracking

[saiepour]

Summary

This PR improves the Schellenberg USB Home Assistant integration to make real-world blind setup more reliable and user-friendly.

The main focus is improving pairing, teach-in, calibration, status identity discovery, estimated position tracking, diagnostics, and Home Assistant entity handling.

What changed

• Added a more robust Pair and test setup flow.
• Added guided USB transmitter teach-in for motors.
• Added automatic calibration with measured open/close travel times.
• Added automatic status identity discovery during calibration.
• Added guided Discover status from original remote action.
• Separated command/transmit identity from receive/status identity.
• Added support for secondary/companion RF identities.
• Prevented unknown secondary frames from affecting position tracking.
• Improved estimated position tracking from:
  • Home Assistant commands
  • recognized remote/status frames
  • measured travel times
  • manual position sync actions
• Added manual position sync actions:
  • set fully open
  • set fully closed
  • set manual position 0–100%
• Added detailed Developer Tools diagnostics.
• Added stable Home Assistant unique IDs for cover entities.
• Added migration/backfill support for legacy blinds without stable IDs.
• Improved default naming to avoid repeated entity names.
• Rewrote the README to be more beginner-friendly.

Why this is needed

In real Schellenberg RF setups, the identity used by the USB stick to transmit commands is not always the same as the identity observed from the original remote or motor status frames.

Some setups also emit additional companion RF frames with unknown commands. Before this change, users often needed to inspect logs and manually guess which identity should be used for position tracking.

This PR makes setup more automatic and understandable by discovering usable status identities during calibration or guided remote discovery.

Tested

Tested live with:

• Schellenberg USB FunkStick
• Three installed Schellenberg RF shutter motors
• Home Assistant custom integration workflow
• Pairing / teach-in
• Short movement test
• Automatic calibration
• Status identity discovery
• Secondary RF identity handling
• Estimated position tracking
• Manual position sync
• Home Assistant restart and entity migration

Observed successful patterns included:

• Separate transmit and status identities
• Primary status streams using 00, 01, and 02
• Secondary companion streams with unknown commands
• Successful HA control
• Successful physical remote tracking
• Stable entity unique IDs after restart

Validation

• 217 tests passed
• Ruff clean
• formatting clean
• compilation clean
• JSON checks clean
• whitespace checks clean

Compatibility

Existing/legacy configurations are preserved. Blinds without stored stable IDs are backfilled once. Manual identity editing remains available for advanced users.

Notes

The integration still does not provide true physical position feedback. Position remains estimated from travel times and commands. USB stick ACKs confirm only that the stick transmitted; they do not confirm motor movement.

[GimpArm]

This is a lot of changes and I don't have time to review it properly. I also don't have time to address all the open issues. So I'm going to trust that you did not break everything for everyone else

[saiepour]

Thank you very much for the trust and approval. I agree this is a large change, so I tried to reduce the risk as much as possible: - Tested live with three installed Schellenberg RF motors - Verified pairing/teach-in, calibration, status discovery, manual sync, restart restore, and shutdown behavior - 224 tests pass - Ruff, mypy, formatting, compilation, JSON, and translation checks pass - Legacy configurations should be preserved and backfilled where needed That said, I understand that real Schellenberg setups can vary. I will monitor the PR/issues and help fix regressions if users report problems.

…

On Mon, 6 Jul 2026, 13:48 GimpArm, ***@***.***> wrote: Merged #27 <#27> into main. — Reply to this email directly, view it on GitHub <#27?email_source=notifications&email_token=ABOQ7GNDMJX2OFUTICYI4H35DOGXTA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZWGA2TMOJWG4YDHJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#event-27605696703>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOQ7GNYOY4QVLCBAZ7STTD5DOGXTAVCNFSNUABFKJSXA33TNF2G64TZHM4DENRSG43TSMRRHNEXG43VMU5TIOBRGAZTGOBXHAY2C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABOQ7GJFRXEQO7UNEJXDKYT5DOGXTA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZWGA2TMOJWG4YDHJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ABOQ7GNSPYIAMYCSOAF6IYT5DOGXTA5CNFSNUABQM5UWIORPF5TWS5BNNB2WEL2JONZXKZKFOZSW45CON52GSZTJMNQXI2LPNYXTENZWGA2TMOJWG4YDHJTSMVQXG33OUZQXK5DIN5ZKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>