Local HTTP API for Linktap
sh00t2kill/linktap_local_http_component · vv0.8.9
A Custom Component that uses the linktap local HTTP API
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
valve | Valve |
1 report below say how a device from this integration behaves in the Home app.
What people report
Local HTTP API for LinkTap watering gateways; works unless the gateway's local API stops responding. One user confirmed entities reach Apple Home via HomeKit Bridge.
- Works1
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| LinkTap G2S gateway | Works Local | Entity naming and lookup fixes tested on live G2SSaved copySummary This PR improves LinkTap compatibility with current Home Assistant and fixes several issues identified and tested on a live LinkTap G2S installation. The main functional fix removes LinkTap's dependency on constructing sibling `entity_id` strings from tap names. Internal relationships now resolve entities through Home Assistant's Entity Registry using their existing stable `unique_id` values. This means renamed or recreated entity IDs, including Home Assistant's newer Entity ID formats with device/area components, no longer break watering duration, watering volume, pause duration, or … Excerpt saved from GitHub on 2026-10-23. | PR #93 · 2026-08 | |
| LinkTap gateway and taps | Partly works Local | Works in Home Entities exposed to Apple Home via HomeKit Bridge without problems | Local API sometimes stops responding; toggling an app schedule can restore itSaved copycan you try this curl command ? assuming the IP in your logs is the correct gateway IP address. [code] It should return something like this, but with your specific gateway ID `{"cmd":3,"gw_id":"BB54B60C004B12BB","ret":3}` Excerpt saved from GitHub on 2026-10-23. | Issue #102 · 2026-09 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Details
| Installs (analytics) | 449 (0.06%) |
|---|---|
| GitHub stars | 55 |
| Latest version | v0.8.9 (2026-09-20) |
| Set up in the UI | Yes |
| Maintainers | @sh00t2kill |
| License | MIT |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
