openwrt_hass_devicetracker - GitLite

KO | EN

gitlite — search

#javascript #python #llm #machine-learning #deep-learning #linux #windows #kubernetes #awesome-list #pytorch #security #mcp #ios #open-source

openwrt_hass_devicetracker

(★ 95)

Simple OpenWRT package which forwards device connection changes to a HomeAssistant instance for presence detection

파일 탐색기

최종 버전 다운로드 (.zip)

- - build.yml
- - .gitignore
- .config
- build.sh
- Dockerfile
.gitignore
docker-compose.yml
LICENSE
README.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/mueslo/openwrt_hass_devicetracker

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd openwrt_hass_devicetracker

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Docker

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Docker Desktop 컨테이너를 빌드하고 실행하려면 필요합니다. 설치 후 실행해서 백그라운드에 켜두세요.

docker compose run pkgbuild # x86_64 build

compose 설정 파일에 정의된 서비스들을 대상으로 명령을 실행합니다.

docker compose run pkgbuild-arm # aarch64 build

compose 설정 파일에 정의된 서비스들을 대상으로 명령을 실행합니다.

✅ 터미널에 docker compose ps 를 입력해 컨테이너들이 Up 상태인지 확인하세요. README에 포트 번호가 적혀있다면 브라우저에서 http://localhost:포트번호 로 접속해보세요.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

3. Make

보통

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Make Linux/macOS는 보통 기본 설치되어 있습니다. Windows는 별도 설치(예: MSYS2, WSL)가 필요합니다.

⚠️ 이 프로젝트는 규모가 큰 저장소라, 이 방법이 실제 핵심 제품이 아니라 내부 하위 패키지를 가리키는 것일 수 있습니다. README 전체를 함께 확인해보세요.

cd packages/net/hass-tracker

이 프로젝트의 관련 파일이 하위 폴더 안에 있어서, 먼저 그 폴더로 이동합니다.

make

생성된 빌드 설정을 바탕으로 실제 컴파일을 진행해 실행 파일을 만듭니다.

✅ 에러 없이 끝나면 성공입니다. 생성된 실행 파일을 직접 실행해보세요.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# openwrt_hass_devicetracker

Package for a completely event-driven device/user presence tracker for [Home Assistant](https://www.home-assistant.io/components/openwrt/) on an OpenWrt access point.

## Description

Listens on hostapd wifi association events and then initiates appropriate service calls to the configured Home Assistant instance. On `AP-STA-CONNECTED` or `AP-STA-POLL-OK` the device is marked as seen with a timeout set by the `timeout_conn` config option. If an `AP-STA-DISCONNECTED` event is received, it is marked as seen with a timeout of `timeout_disc`.

Since restarting your access points removes any scripts connected via `hostapd_cli -a`, this package includes a daemon which monitors ubus for added APs so restarting/reconfiguring your radios doesn't kill the service.

## Building

The package is built using the official [`openwrt/sdk`](https://hub.docker.com/r/openwrt/sdk) Docker image and produces `.apk` packages for the apk-based OpenWrt package manager (25.12+). Since hass-tracker is `PKGARCH=all` (pure shell scripts), the same `.apk` works on any OpenWrt target.

### Using build script (Linux — requires Docker)

```bash
./build/build.sh
```

Uses the `openwrt/sdk:x86_64-main` image to build. The resulting `.apk` lands in `build/bin/`.

| Variable       | Default                  | Description                           |
|----------------|--------------------------|---------------------------------------|
| SDK_IMAGE_TAG  | x86_64-main              | openwrt/sdk image tag                 |
| OUTPUT_DIR     | build/bin                | Output directory for the .apk         |
| PACKAGE_DIR    | packages/net/hass-tracker | Package source directory             |

### Using Docker Compose

```bash
docker compose run pkgbuild       # x86_64 build
docker compose run pkgbuild-arm   # aarch64 build
```

The resulting `.apk` will be in `build/bin/`.

### Using GitHub Actions

Push a tag matching `v*` to automatically build and create a release with the `.apk` artifact. The CI runs against both `x86_64-main` and `aarch64_cortex-a72-main` as a sanity check. See `.github/workflows/build.yml`.

## Installation

On an OpenWrt system with apk as package manager (25.12+):

```bash
apk add hass-tracker_*.apk
```

### Configuration

Once the package is installed, you can modify `/etc/config/hass-tracker` to your liking and start/enable the service via `service hass-tracker start` and `service hass-tracker enable`. If you would like to use HTTPS, simply start your host string with the `https://` protocol specifier.

Authentication is done via a [long-lived access token](https://developers.home-assistant.io/docs/en/auth_api.html#long-lived-access-token) that can be generated from the web UI. This token needs to be set in the configuration file in the field `token`.

## Note on missed events

If Home Assistant or the OpenWrt access point is restarted frequently or unreliable in other ways, you should reduce the very long default timeout for connected devices, since a disconnect event may be missed. However, since association events for connected devices can happen as infrequently as every 2-4 hours, you might want to then add a cronjob which synchronizes the state to Home Assistant at least twice as often as your timeout for connected devices `timeout_conn`. A good value for this might be a timeout of 1 hour and a sync every 30 minutes. The cronjob should look like:

```
#!/bin/sh

source /lib/functions.sh
config_load hass-tracker

source /usr/lib/hass-tracker/functions.sh
sync_state
```

This ensures that missed disconnect events do not spuriously keep the device present for more than an hour.