Skip to main content

Fork Comparison: RiDDiX vs t0bst4r

This fork is the actively maintained successor of t0bst4r/home-assistant-matter-hub. The original author announced the end of development in January 2026; the upstream repository is archived, its last change dates to March 2026, and it was left with more than 160 open issues. This page compares the two projects factually so you can decide whether to switch. For the how-to, see the migration guide.

Project status

RiDDiX forkt0bst4r upstream
DevelopmentActive, stable and alpha release channelsArchived, read-only since March 2026
Issue trackerOpen, actively triagedClosed, more than 160 issues left open
matter.js0.17.90.16.7 (pinned, no further updates)
Home Assistant add-onhamh (stable), hamh-alpha, hamh-testingOriginal add-on, no longer updated

Features added in the fork

Everything the upstream project supported still works here; the storage format is compatible in both directions. The rows below are features that exist only in the fork.

FeatureStatus
Vacuum room selection (ServiceArea) with opt-in ascending room orderStable
Custom device names per entityStable
Composed multi-sensor devices (several HA sensors as one Matter device)Stable
Per-device battery mapping (batteryEntity)Stable
Server mode: standalone Matter accessories instead of a bridgeStable
Room Air Conditioner device type, incl. dry modeStable
EV charger (Energy EVSE)Stable
Electrical meter (power and energy measurement clusters)Stable
Battery storage (ESS)Stable
Water heater management (Matter 1.4, opt-in)Stable
Camera plugin (WebRTC live view)Experimental
Stable identity flag (keeps endpoint identity across renames)Stable
Wedge watchdog: rotates sessions gone silent (opt-in)Stable
Per-fabric health card with subscription scopeStable
Manual cleanup of orphaned identity and mapping recordsStable
Plugin system with a settings UI per bridgeStable
UI translations: 15 locales, including pt-BRStable
Doorbell device typeStable
Electrical utility meter device typeStable

New device types are opt-in overrides, never a changed default, so an upgrade does not re-compose devices that are already paired.

Compatibility with upstream

  • The Matter storage format is identical. Fabrics pair once and survive the switch in both directions, see migration and its rollback section.
  • Configuration options from upstream keep working; fork-only options are additive.

Sources

Feature claims are backed by the release notes and the supported device types list. Upstream status is visible on the archived repository.