# hassock v0.3.0 - Table of Contents

> Home Assistant WebSocket client for Elixir.

## Pages

- [Hassock](readme.md)
- [Changelog](changelog.md)

## Modules

- [Hassock](Hassock.md): Home Assistant WebSocket client for Elixir.
- [Hassock.Area](Hassock.Area.md): An area from Home Assistant's area registry (`config/area_registry/list`).

- [Hassock.Cache](Hassock.Cache.md): Optional ETS-backed cache of all Home Assistant entity states.
- [Hassock.Config](Hassock.Config.md): Configuration for connecting to a Home Assistant instance.
- [Hassock.Connection](Hassock.Connection.md): WebSocket client for Home Assistant.
- [Hassock.Connection.Backoff](Hassock.Connection.Backoff.md): Reconnect delays: exponential backoff with "equal jitter".
- [Hassock.Device](Hassock.Device.md): A device from Home Assistant's device registry (`config/device_registry/list`).
- [Hassock.EntityEntry](Hassock.EntityEntry.md): An entry from Home Assistant's entity registry (`config/entity_registry/list`).
- [Hassock.EntityState](Hassock.EntityState.md): A snapshot of a Home Assistant entity's state.

- [Hassock.Floor](Hassock.Floor.md): A floor from Home Assistant's floor registry (`config/floor_registry/list`).
`level` orders floors (it may be `nil`).

- [Hassock.Label](Hassock.Label.md): A label from Home Assistant's label registry (`config/label_registry/list`).

- [Hassock.Protocol](Hassock.Protocol.md): Pure functions for parsing and encoding Home Assistant WebSocket frames.
- [Hassock.Registries](Hassock.Registries.md): Fetch Home Assistant's floor, area, device, entity and label registries.
- [Hassock.RegistryCache](Hassock.RegistryCache.md): Optional ETS-backed cache of Home Assistant's floor, area, device, entity
and label registries.
- [Hassock.ServiceCall](Hassock.ServiceCall.md): A request to call a Home Assistant service.
- [Hassock.Supervisor](Hassock.Supervisor.md): Optional convenience supervisor that wires a `Hassock.Connection`,
(optionally) a `Hassock.Cache` and (optionally) a `Hassock.RegistryCache`
together under a `one_for_all` strategy — if any crashes, all restart from
a clean slate.