New to the community ecosystem?

Start here.

Hubitat works on its own, but community apps and drivers can help it do more. This guide explains what you are looking at, where software comes from and which tool to use first.

Choose what you want to do Learn how to read results

The basic picture

Three parts of the ecosystem

Knowing who provides the software helps you choose the right tool and source.

  1. 1

    Hubitat platform and built-ins

    Hubitat supplies the hub platform plus built-in apps and drivers. Official device listings and release notes come from Hubitat.

  2. 2

    Community apps and drivers

    Community developers publish optional code. An app adds automation behaviour. A driver lets the hub communicate with a device or service.

  3. 3

    Hubitat Package Manager

    HPM installs and updates participating community projects.

Choose a path

What are you trying to do?

Start with your question. You can ignore the other tools until you need them.

Find

I want an app, driver or package

Search names, authors, namespaces, categories and tags across HPM and community catalogues.

Open Package Explorer Check

I want to research device support

Start with Hubitat's official device catalogue, then browse community driver listings.

Browse official devices Identify

I found code on my hub

Use its definition name, namespace or author to find the package that contains it.

Open General Search Discover

I want to know what Hubitat added

Search Hubitat release notes for new platform, app, driver, protocol and device features.

Open Update Tracker Recover

I am rebuilding a hub

Match app and driver identities to likely installation sources. Searches stay in your browser.

Open Recovery Inventory Publish

I develop community software

Check an HPM manifest, preview its catalogue record and prepare a public HPM submission.

Open Manifest Builder

Read with confidence

How to read the results

Labels show where each result came from and how closely it matches.

Exact

Identity confirmed

The identifying fields agree. When a result is only similar, it is labelled as a suggestion instead.

Source

Origin stays visible

Each result identifies whether it came from Hubitat, HPM, a community wiki or source code.

Snapshot

Dated catalogue update

Successful daily updates let the site show what changed over time.

Health

Latest source check

The date and result of the most recent source check.

No match

Try another identifier

Check the spelling or search by package, author, namespace or code name.

Privacy

Public data, local searches

Searches run in your browser and require no hub configuration.

A useful first visit

Try the ecosystem in five minutes

  1. 1

    Search for a product, protocol or author in Package Explorer.

  2. 2

    Open one result and compare the package, definition and source links.

  3. 3

    Check Package Feed or Update Tracker to see what has changed.

Keep nearby

Small glossary

These are the terms you will see most often.

App
Code that adds automation logic or a user-facing integration.
Driver
Code that represents and communicates with a device or service.
Package
A bundle of one or more apps and drivers that can be distributed together.
Manifest
A JSON file telling HPM what one package contains and where its files are located.
Repository
A separate JSON file an author hosts listing every package they publish. HPM reads it when you add a custom repository, and its public location is what gets listed in HPM's own catalogue.
Namespace
A developer-chosen identity used with a definition name to distinguish Hubitat code.
Snapshot
A dated copy of the public catalogue used to show changes over time.