Sensors
Culiplan
culiplan/home-assistant-culiplan · vv0.15.2
HACSCloud push
Culiplan meal planning integration for Home Assistant
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 push
Goes through the maker’s cloud, which sends updates as they happen. Needs the internet and an account.
Details
| Installs (analytics) | 8 |
|---|---|
| GitHub stars | 29 |
| Latest version | v0.15.2 (2026-09-21) |
| Set up in the UI | Yes |
| Maintainers | @culiplan |
| License | Apache-2.0 |
Limitations from the README
- HA Core catalog listing, Phase 4. We're aiming for HACS first; HA Core submission depends on the upstream pytesthomeassistantcustomcomponent test-fixture fix (the only Silver rule still todo in qualityscale.yaml).
- Brands logo in HA integration picker, assets are prepared; the PR to home-assistant/brands ships at the same time as HACS submission.
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.
