Rename the integration to CamperCan and add brand imagery #123
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/campercan-rename"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The integration is now CamperCan: domain
campercan, foldercustom_components/campercan, servicecampercan.shutdown, loggers, CI, release zip and package names. The updater follows: containercampercan-updater, in-container paths/var/lib/campercan-updater/..., hotspotcampercan-ota. Host bind sources underupdater-data/are unchanged, so no data moves. The icon and logo live incustom_components/campercan/brand/, which Home Assistant 2026.3 and later serves directly.Migration: an existing install must remove the old Campervan integration under Settings → Devices & services before installing CamperCan, then add it again. The config entry and entity registry are keyed by domain.
Hotspot: radio.py creates and deletes the profile by name, so a
campervan-otaprofile left up by an interrupted update would stay on the Pi; remove it withnmcli connection delete campervan-ota.Tested:
ruff check,ruff format --check,mypy, andpytest(1285 passed, 3 skipped).Re review:
brand/stays at the root on purpose. The brief was to prepare a home-assistant/brandscustom_integrations/campercansubmission and keep images out of the release zip. The icon is the opaque cream tile to match the touch icon; the transparent wordmark is the logo.The brand logo files have transparent backgrounds which will create problems with legibility on dark backgrounds. This needs fixed to have the cream background of the icons
Done in
fb9cbad: both logos are now opaque on the cream#FBF8F4background, same sizes and padding.