I’ve got connectivity issues, what can I do?¶
Please follow the troubleshooting guide.
I’d like to connect my bridge to multiple assistants¶
Please follow the multi-fabric guide.
I’m running HAMH as a docker image and want to access it via a reverse proxy¶
Please follow the reverse proxy guide.
Changes on names and labels in Home Assistant have no effect in HAMH¶
When performing changes on entities, like adding or removing a label or renaming your entity, you need to reload the affected bridge for the changes to take effect. This happens automatically every 30 seconds, but you can enforce it by editing the bridge (even without making changes), or when restarting the whole addon.
I added a label to my entities, but HAMH won’t find any device¶
Labels and areas in Home Assistant are technically represented by their “slugs”.
Slugs are technical identifiers used in the background.
Slugs are always lowercase and only allow a-z and underscores, so everything else will be replaced with an underscore.
Even when renaming a label or area, the slug doesn’t change. Never. You can retrieve the slug using the following templates in Home Assistant:
{{ labels() }}- returns all labels{{ labels("light.my_entity") }}- returns the labels of a specific entity{{ areas() }}- returns all areas
If you just can’t get it working with your labels, try to delete your label and re-create it.
My Vacuum does not appear in the Apple Home App¶
Ensure that all home hubs in the Apple Home app are updated to iOS/tvOS/AudioOS 18.4 or later – if any home hub is below 18.4, the vacuum device will not show up. To resolve this:
Check for updates
iPhone / iPad:
Settings > General > Software UpdateHomePod:
Open the Home app → Home Settings → Software UpdateApple TV:
Settings > System > Software Updates
Install any pending updates, then restart each hub.
Relaunch the Home app and confirm the vacuum now appears under your accessories.
How do I access the Health Dashboard?¶
Click the heart icon (❤️) in the top navigation bar of the web UI, or navigate directly to /health.
My bridge keeps failing and restarting¶
The automatic recovery feature will restart failed bridges. If a bridge keeps failing:
Check the logs for specific error messages
Reduce the number of devices in the bridge
Verify all entities in the bridge are valid
Try factory resetting the bridge
How do I use the Bridge Wizard?¶
Go to the Bridges page
Click the Wizard button
Follow the guided steps to create bridges
Ports are automatically assigned starting from 5540
What sensors are supported?¶
Currently supported sensor types:
Temperature (with auto humidity and pressure mapping)
Humidity
Pressure
Flow
Illuminance (Light)
Air Quality (AQI, PM2.5, PM10, CO2, TVOC)
See Temperature & Humidity Sensor for details on combining temperature, humidity, pressure, and battery into a single device.
The app keeps crashing or restarting on my HA Yellow / Raspberry Pi¶
Low-resource devices (1–2 GB RAM) can run out of memory when running many bridges or devices. Since v2.0.17, HAMH limits the Node.js heap to 512 MB to prevent uncontrolled OOM kills. If crashes persist:
Reduce the number of devices per bridge
Split large bridges into smaller ones (e.g. per room)
Consider using a device with more RAM
See #141 for details.
Alexa loses connection after a few hours¶
This was caused by “dead sessions” — Alexa goes offline but the bridge keeps the old session alive, blocking new subscriptions. Since v2.0.17, the bridge detects and force-closes dead sessions automatically. If you still experience this:
Update to the latest version
Remove and re-pair the bridge in the Alexa app
Check your network for multicast/mDNS issues (see Connectivity Issues)
See #105 for details.
My cover / blinds open and close commands are inverted¶
Matter and Home Assistant use different conventions for cover position percentages. Use the bridge feature flags to fix this:
coverSwapOpenClose— Swaps open/close commands (fixes reversed Alexa commands)coverDoNotInvertPercentage— Skips percentage inversioncoverUseHomeAssistantPercentage— Uses HA percentages directly
Configure these in your Bridge Settings → Feature Flags. See #107, #109.
Battery shows as a separate device instead of being part of the sensor¶
HAMH has Auto Battery Mapping enabled by default. It automatically finds battery sensors on the same HA device and combines them with the primary sensor (temperature, climate, fan, vacuum). If it still shows separately:
Check that the battery entity belongs to the same HA device as the primary entity
Make sure
autoBatteryMappingis enabled in your Bridge Settings → Feature FlagsAlternatively, use Entity Mapping to manually set
batteryEntityon the primary sensor
See #99.
My thermostat doesn’t work correctly in auto mode¶
Matter’s “Auto” mode means the thermostat automatically switches between heating and cooling based on temperature. This maps to HA’s heat_cool mode, not auto. Since v2.0.17:
Heat-only thermostats (e.g. TRVs) are exposed with only the Heating feature
Cool-only thermostats (e.g. ACs) are exposed with only the Cooling feature
Full HVAC thermostats get Heating + Cooling + Auto features
This prevents Alexa from rejecting commands on single-capability thermostats. See #143, #136.
My water heater / kettle max temperature is capped at 50°C¶
Previously the default Matter thermostat limits capped water heaters at 50°C. Since v2.0.17, HAMH reads the actual min_temp and max_temp from your HA entity and passes them correctly. Update to the latest version to fix this.
Matter hub appears multiple times in Alexa / duplicate connections¶
This can happen when a bridge is factory-reset or re-created while still paired in Alexa. To fix:
Remove all duplicate entries from the Alexa app
Factory reset the bridge in HAMH (Bridge Settings → Factory Reset)
Re-pair the bridge in Alexa
See #152.
My binary sensor shows “Open/Closed” instead of “On/Off” (running, plug, power)¶
Binary sensors with device_class running, plug, power, battery_charging, or light are now mapped to OnOffSensor (On/Off) instead of ContactSensor (Open/Closed). This was fixed in v2.0.17.
If you’re on an older version, update to get the correct mapping. See #154.
My devices are not assigned to the correct rooms¶
HAMH sends your Home Assistant area names to Matter controllers using the FixedLabel cluster (label: "room", value: "<area name>"). However, no major controller (Google Home, Apple Home, Alexa) currently reads this label for automatic room assignment. You need to assign rooms manually in each controller app during or after pairing.
The FixedLabel data is kept in the bridge for future controller support. The room name is limited to 16 characters per the Matter spec — longer HA area names are truncated automatically.
How do I control Media Player playback?¶
Media players now support Play, Pause, Stop, Next Track, and Previous Track controls through Matter. However, not all controllers support these features yet. Volume control is also available.
What’s the difference between Stable and Alpha?¶
Stable: Production-ready, recommended for daily use
Alpha: New features for testing, may contain bugs
See the Alpha Features Guide for details on alpha features.
How do I report an Alpha bug?¶
When reporting Alpha issues, include:
Alpha version number (visible in Health Dashboard)
Full logs from the add-on/container
Steps to reproduce
Controller type (Google, Apple, Alexa)
My thermostat doesn’t turn on when I set the temperature¶
Since v2.1.0-alpha, thermostats support auto-resume — when off and you set a temperature (even the same one), it automatically turns on. This works with all voice assistants.
If not working:
Update to alpha v2.1.0-alpha.266+
Only works for single-temp mode (not range/auto)
Thermostat must be in “Off” state
Vacuum shows “Paused” instead of “Docked”¶
Fixed in v2.1.0-alpha. Previously some vacuums (Ecovacs, some Roborock) reported idle while docked, showing as “Paused”. Now correctly shows “Docked” when charging.
Too many “No battery entity found” log messages¶
Fixed in v2.1.0-alpha. Battery sensor auto-mapping now uses caching and reduced log levels (debug only). Previously every entity without battery logged a warning.
Bridge runs out of memory after several days¶
Fixed in v2.1.0-alpha. Endpoint disposal was improved in BridgeEndpointManager and ServerModeEndpointManager. Previously endpoints weren’t cleaned up during restarts, causing memory leaks.
How do I use the Dashboard landing page?¶
Since v2.1.0-alpha, the app opens with a Dashboard showing:
Bridge count, device count, fabric connections
Quick navigation to all pages
Bridge Wizard and Create Bridge buttons
Version and uptime
Refreshes every 15 seconds.
What is “Auto Composed Devices”?¶
Auto Composed Devices (autoComposedDevices feature flag, since v2.0.20) combines related entities from the same HA device into one Matter endpoint:
Temperature + Humidity + Pressure + Battery = one device
Switches/Lights with power/energy monitoring show consumption in one device
Uses real Matter Composed Devices with sub-endpoints for proper controller display
Enable in Bridge Settings → Feature Flags.