Sensors
Telegram client
lufton/ha_telegram_client · v1.0.2
HACSCloud polling
HACS telegram client component
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 |
|---|---|---|
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) |
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 100 (0.01%) |
|---|---|
| GitHub stars | 17 |
| Latest version | 1.0.2 (2025-06-25) |
| Set up in the UI | Yes |
| Maintainers | @lufton |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| dyamirana/ha_telegram_client Newer code | ★ 0 | 2026-06-26 | HACS telegram client component |
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.
Sources
- Documentation: https://github.com/lufton/ha_telegram_client/
- Source code: https://github.com/lufton/ha_telegram_client
- Issues: https://github.com/lufton/ha_telegram_client/issues
- HACS: https://hacs.xyz
