Håll den här filen uppdaterad — alltid. Varje gång något läggs till, ändras eller tas bort i setupen (integrationer, enheter, USB-passthrough, entiteter, automationer, addons, gotchas som upptäckts under felsökning) ska CLAUDE.md uppdateras i samma arbetspass och committas tillsammans med ändringen. En ändring är inte klar förrän den finns dokumenterad här.
Family home (4-6 rooms). Lights, blinds, sensors. Full energy monitoring.
- Owner: Petter (primary phone:
notify.mobile_app_petter_iphone) - Kids' rooms: Ida, Moa
| Service | Host | Notes |
|---|---|---|
| Home Assistant | 192.168.1.60 | Proxmox VM |
| MariaDB | 192.168.1.61:3306 | Recorder, 10-day retention |
| InfluxDB | 192.168.1.62:8086 | Long-term → Grafana |
| MQTT | 192.168.1.63:1883 | Mosquitto |
| Zigbee | ConBee II | Z2M channel 11, frontend :8099, addon ID: 45df7312_zigbee2mqtt |
| Reverse proxy | 192.168.1.70 (LXC 200) | Plain nginx. One site-file per service under /etc/nginx/sites-enabled/, own certbot cert per subdomain. HTTPS on per-service port (home:8123, maffia+grocy share 8443 via SNI). External access = https://<svc>.sandholdt.se:<port> (WAN:port→.70:port; WAN:443 = gateway UI). SSH alias nginx-proxy |
| Docker host | 192.168.1.66 (LXC 105 "docker") | Ubuntu 24.04, Docker/Compose. Runs maffia-game (Caddy owns :80/443) + Grocy container + MeshCore proxy/mux (/opt/meshcore, Wio Tracker via dev0) + Mesh-Citadel BBS (/opt/mesh-citadel). SSH alias docker (maffia kept as alias). Renamed from "maffia" 2026-07-19 |
| Docker-loggar (LXC 105) | /etc/docker/daemon.json |
Global log-rotation json-file 10m×3 sedan 2026-11-07. Gäller bara containrar som skapas efter det (log-opts sätts vid create) — meshcore-proxy/meshcore-mux/grocy har fortfarande obegränsade loggar tills de återskapas (docker compose up -d --force-recreate). Bakgrund: disken blev 100 % full 2026-11-07 av discis-bot-1 (24 GB) + nodesis-mongo-1 (20 GB) json-loggar → maffia-backend unhealthy, ENOTFOUND mongo, Caddy kunde inte skriva. Fix: truncate -s 0 på /var/lib/docker/containers/<id>/<id>-json.log, sedan --force-recreate. Kolla df -h / på docker-hosten vid review |
| Grocy | Container on docker host .66:9283 |
Inventory/stock mgmt (lscr.io/linuxserver/grocy, compose in /opt/grocy). HTTPS via reverse proxy → https://grocy.sandholdt.se:8443. Upgrade: docker compose pull && up -d |
| Home Connect | Cloud | Neff oven & hob (no energy data) |
| UniFi Protect | 192.168.1.1 (Zeus) | Cameras: ringklocka, uppfart, garage |
| Synology NAS | 192.168.1.9 (Atlas) | 8-bay NAS, backup storage, Plex media, Frigate NFS storage |
| Music Assistant | HA Addon | Multi-room Sonos via Plex |
| JupyterLab | 172.30.33.4:8099 | HA Addon, nginx patched for Claude access |
| Frigate | HA Addon (ccab4aaf_frigate) |
NVR for birdhouse camera, motion recording (repo blakeblackshear/frigate-hass-addons) |
| MeshCore | Wio Tracker L1 via USB → LXC 105 → proxy+mux (192.168.1.66:5002) |
LoRa-mesh basnod SE-Ullstamma-Base, delas mellan flera klienter via meshcore-mux. HA ansluter över TCP. Rapporterar till meshat.se:s MQTT. Se MeshCore |
| USB-passthrough | Proxmox ares, VM 102 |
usb0=ConBee II 1cf1:0030 (ttyACM0), usb1=RFXtrx433 0403:6001 (ttyUSB0, integration rfxtrx — se RFXtrx), Passthrough per vendor:device-id. Wio Tracker L1 2886:1667 är inte längre på VM 102 (usb2 borttagen 2026-10-07) — den sitter på LXC 105 via dev0. Proxmox-token är read-only; SSH-alias ares (root, addonens nyckel) för ändringar |
Dryckesbeståndet i källarens vinhylla, läst ur Grocy. Inmatning sker i dryck-appen
(dryck.sandholdt.se:8443), inte i HA.
| Entitet | Syfte |
|---|---|
sensor.kallaren_grocy |
Hela beståndet. State = antal flaskor, attribut items/groups/by_country/by_vintage/n_*/error. Exkluderad från recorder & InfluxDB |
sensor.kallaren_flaskor |
Bara antalet, recordat → trendgraf |
script.kallaren_drick_upp |
Konsumerar valda flaskan i Grocy |
script.kallaren_satt_betyg |
Skriver rating/tasting_notes på senast druckna |
automation.kallaren_fyll_flaskvaljaren |
Håller input_select.kallaren_flaska i synk |
- Data hämtas av
scripts/grocy_kallaren.py(joinar/api/stock,/api/objects/products,/api/objects/product_groups,/api/objects/locations) var 5:e minut. Grocy-integrationen används inte för lagret — den exponerar inte userfields (årgång, druva, land, betyg). - Enhetstester:
cd /config/scripts && python3 -m unittest discover -s . -p "test_grocy_*.py" - Testdata för att verifiera vyerna:
python3 scripts/grocy_testdata.py --add|--list|--remove(produkter med prefixZZ Test). Kör alltid--removeefteråt. - Grocy-schemat (grupper, userfields, enheter, locations) ägs av dryck-appens bootstrap — ändra det aldrig härifrån.
groups-attributet listar alla grupper som förekommer i beståndet — de fem riktiga Grocy-grupperna plus en sensor-egen bucketÖvrigtsomgrocy_kallaren.pylägger till för produkter utan produktgrupp (t.ex. produkt 3).Övrigtfinns inte i Grocy och har inget filterchip, men beståndsvyn itererargroupsså inget lager blir osynligt.PUT /api/userfields/products/{id}merge:ar;rating/vintagereturneras som strängar.- Automationens entity_id blev
kallaren_fyll_flaskvaljaren(inte-vare) eftersom HA slugifierar den svenska aliasen "Källaren - Fyll flaskväljaren" — bestämd form ger ett extra n. Kontrollera alltid faktiskt entity_id, lita inte på id-fältet i automations.yaml.
| Component | Purpose |
|---|---|
| nordpool | Electricity spot prices (SE3) |
| smartthinq_sensors | LG appliances (torktumlare, 2x refrigerators) |
| icloud3 | Device tracking |
| solcast_solar | Solar production forecasts (Solcast PV) |
| unifi | UniFi network devices |
| unifiprotect | UniFi Protect cameras |
| synology_dsm | Synology NAS monitoring |
| music_assistant | Multi-room audio management |
| xiaomi_home | Xiaomi/Roborock devices (vacuum) |
| frigate | Frigate NVR integration (HACS) — birdhouse camera + motion recording |
| meshcore | MeshCore LoRa-mesh (HACS custom repo meshcore-dev/meshcore-ha) — basnod över USB + MQTT till meshat.se |
| File | Purpose |
|---|---|
configuration.yaml |
Main config, includes, recorder, influxdb |
automations.yaml |
All automations |
template_sensors.yaml |
Template sensors (electricity pricing) |
sql_sensors.yaml |
SQL sensor (peak power) |
statistics_sensors.yaml |
Statistics sensors (24h energy) |
zigbee2mqtt/configuration.yaml |
Z2M devices |
secrets.yaml |
Credentials (not in git) |
scripts/ |
Utility scripts |
scripts/ha |
HA CLI wrapper (use for config validation, restarts) |
scripts/generate_claude_snapshot.py |
Generates codebase snapshot |
scripts/ha_screenshot.py |
Take dashboard screenshots |
scripts/robonect.py |
Robonect (Gordon-mowern) API-klient/CLI — läs/styr/inställningar |
esphome/ |
ESPHome device configs (water meter, BT proxy) |
dashboards/ |
YAML Lovelace dashboards |
www/meshcore-node-card.js |
Eget Lovelace-kort custom:meshcore-node-card (MeshCore-dashboarden) |
themes/ |
Teman (!include_dir_merge_named): icloud3_theme, meshcore/ (MeshCore Dark) |
| Dashboard | Path | Purpose |
|---|---|---|
| Hem | /lovelace-hem |
Room-based control (13 views: Översikt + rooms + dammsugare) |
| Elektricitet | /lovelace-elektricitet |
Energy monitoring (6 views) |
| Klimat | /lovelace-klimat |
Temperature, humidity, CO2 (2 views) |
| Batteri | /lovelace-batteri |
Device battery status (2 views) |
| Vatten | /lovelace-vatten |
Water consumption & leak detection (2 views) |
| System | /lovelace-system |
Git status, automations, NAS health (1 view) |
| Källaren | /lovelace-kallaren |
Grocy drinks inventory (4 views: Bestånd, Hantera, Statistik, Grocy) |
| MeshCore | /lovelace-meshcore |
LoRa-mesh: basnod, repeater, skicka meddelande, kontakter, meddelandelogg, automationer, 7-dagarsgraf (1 view, tema MeshCore Dark) |
Dashboard cards use: Mushroom cards, ApexCharts, layout-card (grid-layout), decluttering-card templates.
Areas are configured for room-based entity grouping:
idas_rum, moas_rum, gastrum, vardagsrum, kok, garage, partyrummet, tvattstuga, sovrum, entre, groventre, garageuppfart, utomhus, system, grillen
Query entities by area:
curl -s -X POST "http://supervisor/core/api/template" \
-H "Authorization: Bearer $SUPERVISOR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"template": "{{ area_entities(\"kok\") | join(\"\n\") }}"}'- Zigbee friendly names: Swedish ("Ida tryckknapp", "Moas rullgardin")
- Entity IDs: snake_case with room prefix (
cover.idas_rullgardin,cover.moas_rullgardin) - Automation IDs: snake_case (
ida_knapp_rullgardin_ner) - Automation aliases: Swedish, "Room/subject - Action" format ("Ida knapp - Rullgardin ner")
- Notifications: Swedish text
| Entity | Purpose |
|---|---|
sensor.smart_meter_ts_65a_3_aktiv_effekt |
Real-time grid power (W) |
sensor.solarnet_effekt_solceller |
Current solar production (W) |
sensor.peak_power_5th_highest |
5th highest power peak (kW) |
sensor.peak_power_top_5_average |
Average of top 5 peaks (kW) |
sensor.nordpool_kwh_se3_sek_3_10_025 |
Current electricity price (SEK/kWh) |
sensor.solcast_pv_forecast_forecast_today |
Forecasted solar production today (kWh) |
sensor.water_meter_t_display_total_water_consumption |
Total water consumption (m³) |
binary_sensor.vatten_rinner |
Water flow detected (leak detection) |
- Solar & Grid: Fronius inverter with Smart Meter TS 65A-3 (all energy data from single source)
- Solar Forecast: Solcast PV integration for production predictions (
sensor.solcast_pv_forecast_forecast_today,sensor.solcast_pv_forecast_forecast_tomorrow) - Per-device: Smart plugs with power metering (FTX, CASA, Frys, Network)
- Appliances:
- Neff oven/hob via Home Connect (status only, no energy)
- LG torktumlare via SmartThinQ (has energy data)
- Peak power pricing: Summer (Apr-Oct) 22 kr/kW, Winter (Nov-Mar) 43 kr/kW
- 24h energy tracking: Statistics sensors in
statistics_sensors.yaml(FTX, CASA, Frys, Network, Torktumlare)
Export control via SunSpec registers:
| Register | Name | Description |
|---|---|---|
| 40236 | WMaxLimPct_SF | Export power limit % (0=none, 100=full) |
| 40246 | WMaxLim_Ena | Limit enable (0=off, 1=on) |
To limit: Set 40236=0, then 40246=1. To restore: Set 40246=0.
Total capacity: 11.89 kWp DC / 10 kW AC Inverter: Fronius Symo GEN24 10.0 Plus Panel model: JA Solar JAM54S30 410/MR (410 Wp per panel) Total panels: 29
Site 1: Southern roof (Södra taket)
- Panels: 17
- DC Capacity: 6.97 kWp
- Tilt: 30°
- Azimuth: 155° (south-southeast, 25° east of due south)
Site 2: Southwest roofs (Sydvästra taken)
- Panels: 12 (4 + 8 from two segments)
- DC Capacity: 4.92 kWp
- Tilt: 30°
- Azimuth: -115° (west-southwest, 90° west of Site 1)
Two rooftop sites configured:
| Setting | Site 1 (South) | Site 2 (Southwest) |
|---|---|---|
| DC Capacity | 6.97 kWp | 4.92 kWp |
| AC Capacity | 5.9 kW | 4.1 kW |
| Tilt | 30° | 30° |
| Azimuth | 155° | -115° |
| Efficiency factor | 0.85 | 0.85 |
Note: Azimuth uses scale where 0° = north, ±180° = south, 90° = east, -90° = west.
- Solcast PV Forecast integration installed via HACS
- Forecast updates are handled by the integration's own auto-update (
auto_update: 1= spread evenly between sunrise and sunset within the quota) — there is no HA automation for it. Free tier: 10 calls/day, and each poll uses 2 (one per site) → ~5 polls/day. 429 / Try again laterwith "API used is 2/10" = Solcast throttling hobbyist accounts while their servers are busy, not our quota. The integration retries 10× and then waits for the next auto-update; the forecast from the last successful poll stays valid. Seen 2026-10-12–13 (only the first poll of the day succeeded). Nothing to fix on our side.- Data feeds into Home Assistant energy dashboard
| Room | Devices |
|---|---|
| Idas rum | Tryckknapp, rullgardin, repeater |
| Moas rum | Tryckknapp, rullgardin, repeater |
| Gästrum | Tryckknapp, 2x gardin, repeater |
| Tvättstuga | FTX, CASA, vattensensor fjärrvärme |
| Partyrummet | Frys, vattensensor frys |
| Network | Network smartplug (power monitoring only) |
Button control: All buttons have direct Zigbee bindings to their covers (cluster 258 windowCovering) AND HA automations (blueprint custom/blind_button_control.yaml) as backup. Gästrum button is bound to both Gästrum höger gardin and Gästrum vänster gardin. HA automations target cover.gastrum_gardiner_ha (HA cover group containing both).
Water leak sensors: binary_sensor.vattensensor_frys_water_leak, binary_sensor.vattensensor_fjarrvarme_water_leak
The blinds may lose calibration after battery replacement or power loss. When this happens, they report incorrect positions (e.g., 46% when fully closed).
Symptoms: Cover shows "open" at ~46% when physically closed.
To recalibrate:
- Move blind to desired closed position:
cover.set_cover_positionwithposition: 0(or use HA UI) - Double-press the down button on the physical blind hardware
- The blind will register this as the new 0% (closed) position
Automations to update after recalibration:
automations.yaml: Updatedown_positionin button blueprints (Ida, Moa, Gästrum)
Current calibrated positions:
| Cover | Closed | Open |
|---|---|---|
| Idas rullgardin | 0% | 100% |
| Moas rullgardin | 0% | 100% |
| Gästrum gardiner | 0% | 100% |
Sleepy device configure failures:
IKEA battery devices (buttons, blinds) sleep aggressively. Z2M configure/bind operations time out if the device is asleep. Error: Bind ... genOnOff ... failed (waiting for response TIMEOUT).
Fix: Run ha z2m reconfigure <friendly_name> and press the device button repeatedly for ~30s to keep it awake until the bind completes.
NwkRouteDiscoveryFailed (0xd0): The coordinator cannot find a route to the device. Usually caused by a nearby repeater/router being offline.
Fix:
- Check router status:
ha z2m devices- look for STALE/OFFLINE routers - Power-cycle the relevant repeater
- Once router is back, enable permit join:
ha z2m permit-join - Wake the device (press button / move blind) to force a rejoin
- Reconfigure:
ha z2m reconfigure <friendly_name>while pressing the button
Device offline (last seen >24h): Battery devices that lose their route may not recover on their own. Check the nearest repeater first, then wake the device after the repeater is back online.
Plejd mesh lighting system (custom integration plejd). Lights are named by location:
- Köket:
light.kok_taklampa,light.koksspottar_1,light.koksspottar_2,light.lampa_over_kokso,light.bordslampa_tak_kok,light.fonsterlampor - Vardagsrum:
light.lampa_over_matbord - Gästrum:
light.takspottar_3,light.fonsterlampor_2 - Garage:
light.takbelysning,light.kallare - Partyrummet:
light.takspottar,light.taklampa - Utomhus:
light.belysning_staket,light.takfot,light.takfotbelysning_baksida,light.gangbelysning,light.belysning_grasmatta_baksida,light.ledlist_garageport,light.garge_yttervagg
Plejd ≥ 0.22.0 (installerat 2026-10-06, thomasloven/hass_plejd) gör huvudutgången på DIM-02/REL-02
till primär enhet (bär Bluetooth-adressen) och den andra utgången till via_device. Gamla registerposter
från < 0.22.0 kan ha adressen på fel utgång, eller båda utgångarnas identifiers hopslagna på en enhet.
Då faller hela config-entryn (setup_error) och alla Plejd-entiteter blir unavailable — tyst, utan
notis. Hände 2026-10-06 → 2026-10-22 (upptäckt vid review; upstream-issue #177, öppen).
- Symptom i loggen:
plejd: Not adding entity … connections [('bluetooth', …)] are already registered for device <id> of the same config entry(adressen på fel enhet) ellerHomeAssistantError: A device can not be its own via device(hopslagna identifiers), båda frånplejd_entity.pyregister_unknown_device. - Diagnos: gruppera Plejd-enheterna i
.storage/core.device_registryper BLE-adress (första delen av identifierMAC:objectId). Friskt = exakt en enhet per adress harconnections, och den har ingetvia_device_id; ingen enhet har > 1 identifier. - Fix: ta bort den felaktiga enheten via websocket
config/device_registry/remove_config_entry(device_id + Plejds entry-id01KF8M8SGFQ74FJJXTMV1M38B3), sedanha core restart— enbartentry reloadger "has already been setup". HA återskapar enheten (samma device-id) och entity_id:n behålls (light.bordslampa_tak_kok,light.takspottar_3,light.fonsterlampor_2,light.takbelysningverifierat). Diagnostik-entiteterna (switch.may_be_gateway_N,sensor.rssi_N) skapas bara för primära enheter, så de försvinner för sekundärutgången — refereras inte någonstans. - Lokal patch mot
*-splitten (se Bermuda-minnet) finns inte längre i 0.22.0 — behövs inte heller.
| Device | Purpose |
|---|---|
t-display (water meter) |
Kamstrup Multical 21 water meter reader via wM-Bus |
bt-proxy-1 |
Bluetooth proxy with iGrill thermometer support |
Water meter: LilyGo T-Display with CC1101 radio module, receives encrypted wM-Bus transmissions.
| Camera | Location |
|---|---|
camera.ringklocka_* |
Front door (doorbell with AI detection) |
camera.uppfart_* |
Driveway |
camera.garage_* |
Garage |
All cameras support: motion, person, vehicle, animal, smoke/CO detection.
NVR Storage: sensor.zeus_anvandning_av_lagringsutrymme shows ~99% - this is normal! The NVR continuously records and rolls over old footage, so storage is always near capacity.
Separate DIY camera, not UniFi Protect. A Raspberry Pi 3B (192.168.4.152, hostname birdhouse, IoT VLAN) runs v4l2rtspserver exposing rtsp://192.168.4.152:8554/unicast (H264 1024×768, bitrate capped to 2 Mbit/s).
camera.birdhouseis owned by the Frigate integration (HACS) — the oldgenericRTSP camera was removed so Frigate could take the entity_id.- Motion-only recording, 2-day retention (no 24/7). Clips: Media → Frigate → birdhouse. Motion:
binary_sensor.birdhouse_motion. - Object detection (person) is OFF (
detect.enabled: false+switch.birdhouse_detectoff) — pointless on a top-down IR nest cam. Motion detection + the customholkclassification run independently (verified:detection_fps: 0,process_fps: 5). NOTE: Frigate 0.17 has a runtime-override store that wins overconfig.ymlon restart, so toggling the switch is what actually takes effect — set both to keep it off. - Motion clips (MotionEye-style): automation
Fågelholk - Spela in klipp vid rörelseopens a Frigate manual event on motion (rest_command.birdhouse_clip_start→POST /api/events/birdhouse/motion/create) and ends it 5 s after motion stops (birdhouse_clip_end→PUT /api/events/<id>/end). Clip = actual motion duration; pulled from recordings, stored on NAS, shows in Media → Frigate → birdhouse. Orphan-safe: an un-ended open event auto-closes at ~30 s.rest_commandresponse shape:start.content.event_id. - Frigate config lives in
/addon_configs/ccab4aaf_frigate/config.yml(not reachable from the Claude addon — edit via the Frigate API on the internal container:curl http://ccab4aaf-frigate:5000/api/config/save?save_option=saverestart -H "Content-Type: text/plain" --data-binary @file). - Recordings store on the Atlas NAS via an HA network-storage NFS mount named
frigate→192.168.1.9:/volume2/homeassistant/frigate(mounted at/media/frigate, where the Frigate addon writes). The SQLite DB stays local in addon-configs (/config/frigate.db) — never on NFS. Frigate auto-prunes oldest at the disk threshold. SSH to the Pi only works from the HA host (IoT VLAN; a corp-VPN laptop can't reach it). - To move/restore the NFS mount: use the Supervisor mounts API (
curl -X POST http://supervisor/mounts ... '{"name":"frigate","usage":"media","type":"nfs","server":"192.168.1.9","path":"..."}'). The mount NAME must befrigateso it lands at/media/frigate. Claude addon cannot reach/media— local-disk cleanup needs the Advanced SSH addon (a0d7b954_ssh). - ÅTERKOMMANDE FEL — "holk-klasserna är borta" (2026-07-17, 2026-08-04): dataset-API:t
(
/api/classification/holk/dataset) returnerar{}fast konfigen är oförändrad. Grundorsaken är INTE att NFS-monteringen tappats —GET /mountsvisarstate: activeoch NAS:en är nåbar hela tiden. Supervisor gör två steg: (1) NFS-montering mot Atlas, som lyckas, och (2) en bind-montering av den in i/media/frigate. Steg 2 vägrar medMountTargetNotEmptyError: Cannot mount bind_frigate because there is existing data at /data/media/frigateså fort det ligger lokal data i katalogen. Frigate (boot: auto) startar då ändå och skriver på HA:s lokala disk — vilket lägger dit mer data och gör felet självförstärkande vid varje omstart. Datasetet ligger kvar orört på NAS:en.- Diagnos (ingen SSH behövs):
GET /api/stats→service.storage["/media/frigate/clips"].mount_type.ext4+ total ≈ 125 GB (=GET /host/infodisk_total) betyder lokal disk = trasigt. Friskt ärnfs4+ total ≈ 32,9 TB. Grundorsaken syns ordagrant iGET /supervisor/logs. - Fix: stoppa Frigate → flytta undan
/media/frigatevia SSH-addonen →POST /mounts/frigate/reload→ starta Frigate → verifieramount_type: nfs4och att datasetet har 3 klasser. Enbart addon-omstart hjälper INTE (bekräftat) — katalogen måste tömmas först. - SSH-addonen: port 22222, user
hassio(uid 1000, inte root), lösenord i addonens options viaGET /addons/a0d7b954_ssh/info. Lösenordsfrisudofungerar och behövs —/mediaär root-ägd 755. Ingensshpass/paramikoi Claude-addonen som standard (pip install paramiko). Addonen ser/media, men inte värdens/mnt/data/supervisor.
- Diagnos (ingen SSH behövs):
Basnod SE-Ullstamma-Base = Seeed Wio Tracker L1 Pro med MeshCore Companion USB-firmware
(v1.17.1-d929643, protokoll 13, bygd 14-Aug-2026), ansluten med USB till Proxmox-värden och
släppt in i docker-hosten (LXC 105) där proxy + mux delar den mellan flera klienter (sedan 2026-10-07,
se Companion-delning). HA:s enhetsregister visar firmware "Unknown" —
integrationen läser inte ut den för basnoden; det är inte transportlagret.
Integration meshcore v2.10.0 via HACS (custom repo meshcore-dev/meshcore-ha), installerad 2026-09-25.
| Inställning | Värde |
|---|---|
| Anslutning (HA) | TCP 192.168.1.66:5002 (dedikerad mux-port för MeshCore-HA). Bytt från USB via integrationens Reconfigure 2026-10-07 — config entryn (repeater, broker, tracked clients) behölls |
| Serieport (i LXC 105) | /dev/serial/by-id/usb-Seeed_Studio_Seeed_Wio_Tracker_L1_5D83C909DFE7FBE5-if00 (by-id, aldrig ttyACMx), 115200 baud — ägs av meshcore-proxy |
| Radio | 869.618 MHz, 62.5 kHz, SF8, CR 8, 22 dBm — ändra inte radioinställningarna |
| Kontaktläge | Manual contact mode (integrationen slår på det) — noden lägger inte till kontakter själv, HA håller upptäckta. Rekommenderat, låt vara |
| MQTT Broker 1 | meshcore-mqtt.meshat.se:443, websockets, TLS + verify, inget user/lösen, Auth Token på (audience meshcore-mqtt.meshat.se), Payload Mode packet (LetsMesh), IATA LPI. Topics meshcore/{IATA}/{PUBLIC_KEY}/packets + /status |
| Övervakad repeater | SE0580-Ullstamma (1cb817f5567d, ~20 m bort) — status, telemetri & grannar var 7200 s (lösenord i config entry) |
| Kontakter på noden | SE-SM5XBV (4242d01aa7a1) och SE-SM5XBC-2 (a57e8a604f5c, med C — Petter kallar den "SE-SM5XBV-2") = Petters bärbara companions. Båda kontakter + tracked clients (telemetriförfrågan var 7200 s, flood tills väg är känd → basnoden sänder). DM/status-kommandot gäller bara SE-SM5XBV |
| Basnodens publika nyckel | 505500c8885f10f604aad6889b6c9715e1c1cb6cf2598f0929cb3117be3b9a93 (inte hemlig; behövs när en annan nod ska lägga till basnoden utan att basnoden advertar) |
| Entitet | Syfte |
|---|---|
sensor.meshcore_505500_node_status_se_ullstamma_base |
HA:s anslutning till basnoden (via mux) (online/offline) |
binary_sensor.meshcore_505500_mqtt_broker_1_connection |
MQTT-anslutningen till meshat.se |
binary_sensor.meshcore_1cb817f556_online_se0580_ullstamma |
Repeatern svarar (off först efter 2,5 × pollintervallet = 5 h vid 2 h) |
sensor.meshcore_1cb817f556_bat_se0580_ullstamma |
Repeaterns batterispänning (V) |
sensor.meshcore_1cb817f556_uptime_se0580_ullstamma |
Repeaterns uptime (dygn) |
automation.meshcore_larm_repeater_se0580_ullstamma |
Notis: repeater offline/tillbaka, batteri < 3,6 V, basnod offline 10 min |
automation.meshcore_internet_nere_tillbaka |
DM till SE-SM5XBV när binary_sensor.internet går off/on (push fungerar inte utan internet) |
automation.meshcore_svara_pa_status_fran_se_sm5xbv |
DM status från SE-SM5XBV → svarar med statusrapport (~100 byte: tid, internet, nät/sol kW, läcka, olåsta lås, hemma, repeater-V) |
automation.meshcore_las_kontaktlistan_efter_omstart |
Workaround: kör lokalt get_contacts när nodantal-sensorn är unknown (efter start/omladdning) |
sensor.meshcore_se_sm5xbv_rssi / _snr (+ se_sm5xbc_2) |
Trigger-template (template_sensors.yaml): RSSI/SNR på senaste paket companion → basnod, mätt hos basnoden (companionens egen mottagning finns inte i telemetrin). Behåller värdet mellan paket, attribut senast/pakettyp |
binary_sensor.internet |
Template (template_sensors.yaml): on om binary_sensor.internet_ping_cloudflare (1.1.1.1) eller binary_sensor.internet_ping_google (8.8.8.8) svarar. delay_off 3 min, delay_on 1 min |
- Privat nyckel: auth token-läget läser ut nodens privata nyckel (
export_private_key) vid varje start/omladdning. Den hålls bara i minnet — aldrig i config entry eller loggar. Skriv aldrig ut den.meshcore-decodersaknas → integrationen signerar token i Python (varning "meshcore-decoder not found" är förväntad och ofarlig). - Sänd inget från noden utan att fråga (meddelanden, adverts). Repeaterövervakningen skickar statusförfrågningar över radio (och login vid upprepade fel, max 1/h) — det är godkänt.
- Repeaterns online-sensor returnerar
offdirekt om basnoden tappar USB — därför kräver larm-automationen att basnoden äronline. - Loggar: integrationen loggar på INFO (anslutning,
[MQTT1] Connected) — meddefault: warningsyns inget. Tillfälligt:ha call logger.set_level '{"custom_components.meshcore":"info"}'(inte persistent). Paketpubliceringar loggas bara på DEBUG. Återställ tillwarningefteråt. - Skicka DM från HA:
meshcore.send_messagemednode_id: SE-SM5XBV(ellerpubkey_prefix) ochmessage(~140 tecken max). Mottagaren måste finnas i basnodens kontaktlista, och mottagaren måste ha basnoden som kontakt (DM krypteras med nycklar från båda noderna; paketet bär bara en avsändar-hash). Leverans syns isensor.meshcore_505500_last_message_delivery_se_ullstamma_base. - Agera på inkommande DM: event
meshcore_messagemedmessage_type: direct,message,sender_name,pubkey_prefix,hop_count. Utgående DM skickar samma event medoutgoing: trueochpubkey_prefix= mottagarens → filtrera alltid bortoutgoing(annars loop). Filtrera påpubkey_prefix, inte namn — namn kan spoofas, DM kan bara dekrypteras från rätt nyckel. MeshCore-text max ~160 byte (å/ä/ö = 2 byte). Nya kommandon läggs somchoose-grenar/villkor i stil medmeshcore_status_kommando. - Internet-detektering: UniFi-integrationen exponerar inte WAN-status för Zeus (bara
state/uptime/CPU/minne). Därför Ping-integrationen (2 config entries, entity_ids omdöpta från
binary_sensor.1_1_1_1/8_8_8_8). Dual-WAN-failover ger inget larm eftersom pingen fortsätter. - Lägga till en kontakt (lokalt över USB, ingen radio): låt noden skicka advert → den dyker upp i
select.meshcore_discovered_contact→select.select_option+meshcore.add_selected_contact(köradd_contact <pubkey>). Kontrolleraadded_to_node: truepå kontaktens binary_sensor. - Adverts (bara på Petters begäran): basnoden flood-advert =
meshcore.execute_command{"command":"send_advert true"}. Få repeatern att flood-adverta via fjärr-CLI:{"command":"send_cmd 1cb817f5567d advert"}→ repeatern svarar "OK - Advert sent" (syns i logbooken). Fjärr-CLI kräver admin-login (integrationen är inloggad via repeater-lösenordet). Resultat avexecute_commandloggas bara på INFO ("Command result"). - Varje ändring av config entry (options-flödet: repeater, tracked client, broker …) laddar om hela integrationen → USB-återanslutning, MQTT-återanslutning och ny export av privata nyckeln. Alla MeshCore-entiteter byter tillstånd i logbooken samtidigt — det är normalt.
- Dashboard
/lovelace-meshcore(dashboards/meshcore.yaml). Nodkorten är ett eget kortcustom:meshcore-node-card(www/meshcore-node-card.js, vanilla JS, inga beroenden) medkind: base|repeater; config-nycklarna är entity_ids (online,battery,voltage,rssi,snr,noise,sent,received,tx_air,rx_air,uptime,temperature,path_len,neighbor_prefix, för companion ävenlast_seen(kontaktens binary_sensor) ochrequests_ok/fail).kind: companionräknar batteri-% frånch1_voltagemed en LiPo-kurva och visar "Ladda!" < 20 %. Trendlinjerna hämtas viahistory/history_during_period(24 h). Advert- knapparna på baskortet sänder (bekräftelsedialog). Resursen är registrerad i Lovelace-resurserna (storage) som/local/meshcore-node-card.js?v=N— höjvvid varje ändring av JS-filen (lovelace/resources/updatevia websocket), annars cachar webbläsarna gammal kod. Layouten anpassar sig efter kortets bredd (CSS container queries,@container≤470/≤380 px): mindre märken/typsnitt, temperatur flyttas till namnraden och nyckel-id döljs i smala kort. Vyn tvingar tematMeshCore Dark(themes/meshcore/meshcore.yaml) så standardkort matchar.ha-selectignorerar temats fyllnadsfärger → användmushroom-select-cardför selects. Förhandsgranska utan omstart: skapa en tillfällig storage-dashboard (lovelace/dashboards/createlovelace/config/savemed samma config), screenshot, ta bort den.
- Integrationsbugg —
sensor.meshcore_505500_node_count_se_ullstamma_base=unknownefter varje omstart/omladdning: sensorn sätts bara vidCONTACTS/NEW_CONTACT-event, men kontakterna läses in innan den prenumererar. Workaround-automationen ovan körexecute_command get_contacts(lokalt över USB, ingen radio) ~1 min 45 s efter. Värdet = tillagda kontakter + basnoden själv. - Companion-telemetri kräver att companion-appen tillåter telemetri för SE-Ullstamma-Base
(telemetriinställning i appen: tillåt alla / favoriter). Annars 0 lyckade förfrågningar
(SE-SM5XBV hade 0/16 2026-09-27; fungerar efter att telemetri tillåtits i appen). Svaret (LPP)
ger för companions
sensor.meshcore_<pfx>_ch1_battery_voltage_<namn>(V),_ch1_battery_(%, integrationens egen omräkning),_ch1_temperature_,_ch1_illuminance_och GPS →device_tracker.meshcore_<pfx>_gps_<namn>(nodens position syns i HA). Sensorerna skapas först vid första lyckade svaret — dashboarden refererar dem i förväg. Manuell förfrågan (sänder!):execute_command {"command":"send_telemetry_req <pubkey12>"}. - Råpaket-tolkning (
meshcore_raw_event,event_type: EventType.RX_LOG_DATA):payload.payload= paketet i hex:[header][path_len][path…][dest-hash][src-hash]…(+4 byte transport-kod för route_type 0/3). header: route = bits 0-1 (1 FLOOD, 2 DIRECT), payload_type = bits 2-5 (0 REQ, 1 RESPONSE, 2 TXT, 3 ACK, 4 ADVERT, 8 PATH). path_len: bits 0-5 antal hopp, 6-7 hashstorlek-1. Basnoden =50, SE-SM5XBV =42, SE-SM5XBC-2 =a5(1-byte-hash, kan kollidera). Flood med hopp > 0 har repeaterns RSSI, inte avsändarens.raw_hex=[snr*4][rssi]+ paketet. - Gotcha: variabeln
off(ävenon/yes/no) som YAML-nyckel blir boolesk →Invalid config … expected str 'variables->False'.ha core checkfångar det INTE, bara core-loggen vidtemplate.reload. Trigger-templates:variablesfungerade inte iconditionshär — lägg logiken inline i villkorsmallen. - Felsök "hörs inte": lyssna på
meshcore_raw_eventvia websocket (subscribe_events) — visar varjeRX_LOG_DATA(SNR/RSSI),CONTACT_MSG_RECV,TELEMETRY_RESPONSE,ACK. Obs: kontaktenslast_advertuppdaterades INTE av companionens adverts 2026-09-27 fast DM gick fram direkt (SNR 12,75) — använd DM/telemetri, intelast_advert, för att avgöra om en nod nås. Räknarnarequest_successes/failuresnollställs vid omladdning (bara i minnet). - Repeatern tillagd via Configure → Add Repeater Station. Första login i config-flödet kan timea ut ("Login to repeater failed or timed out") — lyckas efter omladdning.
custom_components/är gitignorerad och konfigurationen ligger i.storage→ ominstallation kräver HACS + config-flödet igen (TCP →192.168.1.66:5002, sedan Manage MQTT Brokers → Add Broker).
Companion-firmware tar bara EN anslutning och protokollet saknar request-ID:n (OK/ERR går inte att
knyta till en klient, SYNC_NEXT_MESSAGE tömmer enhetens enda inbox). Därför en protokollmedveten
mux framför noden. Allt i /opt/meshcore på docker-hosten (ssh -F ~/.ssh/config docker):
Wio (USB) ─ares dev0→ LXC 105 ─→ meshcore-proxy :5000 ─(nät "upstream", internal)→ meshcore-mux
(serial→TCP, ej publicerad) ├ 127.0.0.1:5001 multi-client (engångs-CLI)
├ 192.168.1.66:5002 MeshCore-HA
├ 5003 mesh-citadel (bara via Docker-nätet meshcore_default, EJ publicerad)
└ 5005 reserv (i mux-configen, EJ publicerad)
| Del | Detalj |
|---|---|
| Proxy | ghcr.io/rgregg/meshcore-proxy:v0.5.0 — --serial <by-id> --host 0.0.0.0 --port 5000 --log-level info. README:ns --log-events/--tcp finns INTE i CLI:t |
| Mux | ghcr.io/fdyfox/meshcore-mux:0.5.1 (Go-port av compumike/meshcore-tcp-mux), config.yaml bredvid compose. Persistence på (volym meshcore_mux-state), dedup på, allow_private_key_export: true (krävs — meshcore-ha signerar MQTT-token mot meshat.se; godkänt av Petter 2026-10-06), import/factory reset av |
| Brandvägg | meshcore-fw.service → /usr/local/sbin/meshcore-fw.sh: DOCKER-USER-regel som släpper 5002 bara från 192.168.1.60. Proxmox-brandväggen är avstängd i klustret och UniFi ser inte trafik mellan VM/LXC på samma vmbr0 — därför ligger skyddet här |
| CLI | docker run --rm --network host meshcore-cli:1.6.5 -t 127.0.0.1 -p 5001 <kmd> (lokalt byggd image). Direkt mot proxyn: --network meshcore_upstream ... -t meshcore-proxy -p 5000 — bara när mux:en är stoppad |
| Proxmox | dev0: /dev/serial/by-id/usb-Seeed…-if00,gid=20,mode=0660 på LXC 105 (hotplug fungerade, ingen omstart). Proxmox 9.2.21 |
- Regler: mux:en ska vara nodens ENDA klient — ingen direkt TCP/USB mot noden när den kör. En
dedikerad port = en app, delas aldrig. Lyssnarna saknar auth/kryptering: vem som når 5001/5002 kan
exportera privata nyckeln → exponera aldrig mot internet; nya portar (5003, 5005) kräver både
ports:i compose och en brandväggsregel. - Gotcha Docker i unprivileged LXC:
--devicefungerar bara med samma sökväg i containern (A:B-omdöpning → runc "error creating device nodes … no such file or directory").-v-bindning fungerar också. - Gotcha
DOCKER-USER: filtrera på-m conntrack --ctdir ORIGINAL --ctorigdst … --ctorigdstport …. Utan--ctdir ORIGINALmatchar även containerns svarspaket (källa 172.x) och droppas → inte ens den tillåtna källan når fram. - Uppgradera: ändra image-taggen i
compose.yaml→docker compose pull && docker compose up -d. Ändradconfig.yaml→docker compose up -d --force-recreate meshcore-mux. - Rollback till USB i HA:
docker compose down→pct set 105 --delete dev0(på ares) →qm set 102 --usb2 host=2886:1667→ meshcore Reconfigure → USB, by-id-sökvägen ovan. - Inkommande DM kopieras till ALLA klienter (HA och BBS:en ser samma DM). Därför har BBS:en
ignore_commandsför HA:s DM-kommandon — se Mesh-Citadel BBS. - Kända begränsningar (mux:ens LIMITATIONS.md): utgående meddelanden speglas inte till andra klienter;
bara en remote-request (login/status/telemetri) åt gången — samtidiga får
BAD_STATE; Go-porten var otestad mot riktig hårdvara före oss (fungerade 2026-10-07: HA, MQTT-token, repeaterpollning via radio).
Citadel-BBS på basnoden (samma identitet SE-Ullstamma-Base), installerad 2026-10-07. Kör vår fork
petterl/mesh-citadel (av taedryn/mesh-citadel) — upstream
kan bara USB. Forken lägger till: TCP-anslutning (connection: tcp), configure_node, advert_interval: 0
= inga adverts, ignore_commands, Dockerfile, samt melidosian-forkens buggfixar (CANCEL, lagad testsvit + CI).
Lokal klon för utveckling: /data/home/src/mesh-citadel (tester: python -m pytest -q).
| Del | Detalj |
|---|---|
| Container | mesh-citadel i /opt/mesh-citadel (compose; build: ./src = klon av forken, image mesh-citadel:local). Read-only, cap_drop ALL, uid 10001 |
| Anslutning | tcp://meshcore-mux:5003 över externt nät meshcore_default — 5003 publiceras inte på värden → ingen brandväggsregel |
| Config | /opt/mesh-citadel/data/config.yaml. configure_node: false (rör aldrig radio/namn/TX), advert_interval: 0, ignore_commands: ["status"], tz Europe/Stockholm |
| Data | /opt/mesh-citadel/data/citadel.db (SQLite på disk, use_memory: false). Loggar bara via docker logs (log_file_path: /dev/null, json-file 3×10 MB) |
| Sysop | petter (SYSOP, skapad direkt i DB:n före första start så ingen på meshen blir förste-sysop). Lösenord root-only i /root/mesh-citadel-sysop.txt på docker-hosten |
- Svarar på alla DM till basnoden (inloggningsprompt) — sänder över radio. Lägg varje nytt
HA-DM-kommando (
meshcore_status_kommando-stilen) även iignore_commands, annars svarar båda. Matchar hela meddelandet, skiftlägesokänsligt. Ändrad config →docker compose restart. - Kontakter: BBS:en lägger till varje companion den hör advert från på noden (lokalt, ingen radio) och raderar
den äldsta vid
max_device_contacts(300) — kan på sikt radera HA:s kontakter (SE-SM5XBV, repeatern). Ej åtgärdat. - Vid start: synkar nodens klocka +
set_manual_add_contacts(true)(samma som HA) — inget sänds. - Upgrade:
cd /opt/mesh-citadel && git -C src pull && docker compose up -d --build. Hämta upstream/melidosian-ändringar i den lokala klonen (git fetch upstream), testa, pusha till forken först. - Lokal konsol:
docker exec -it mesh-citadel python cli_client.py(CLI-socket/tmp/mesh-citadel-cli.sock).
RFXCOM RFXtrx433 via USB (usb1), core-integrationen rfxtrx tillagd 2026-09-25.
- Port:
/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A118TRAH-if00-port0(by-id, intettyUSB0). - Status vid start: 433.92 MHz, firmware 43, output power 31.
- Protokoll satta i integrationens alternativ 2026-09-26 (HA skickar dem vid varje anslutning,
inte sparat i pinnens flash):
ac,arc,lighting4,oregon,x10,fineoffset,lacrosse,rubicson,hideki,homeeasy,byronsx. Med bara de fem första (pinnens default) hördes noll paket på 10 min. automatic_add: false, inga enheter tillagda än. Hörda sändare (11 min lyssning 2026-09-26): Viking 02035/02038 temp+fukt,id 87:00, var ~60 s, utomhus (15,1 °C = utegivaren). Oklart om den är vår eller grannens.- Gotcha: en traceback
TypeError: 'NoneType' object cannot be interpreted as an integer(serialposix.py read) betyder att mottagartråden dog när porten stängdes vid omladdning. Integrationen visar ändåloadedmen tar inte emot något. Fix: ladda om config entryn. - Paket från okända enheter syns bara på DEBUG (
logger.set_level '{"homeassistant.components.rfxtrx":"debug","RFXtrx":"debug"}', radRecv:), inte somrfxtrx_eventnärautomatic_addär av. Återställ tillwarningefteråt.
Addon ID: d5369777_music_assistant
Music library manager with multi-room audio. Uses native Sonos provider (not HA Sonos integration).
| Provider | Source |
|---|---|
| Plex | Music library on Atlas NAS |
| Squeezebox | Logitech Squeezebox devices (squeezelite) |
| Chromecast | Google Cast devices |
| Entity | Room | Device | Provider |
|---|---|---|---|
media_player.koket |
Köket | Sonos One | Sonos |
media_player.vardagsrum_ljud |
Vardagsrum | Sonos Playbar | Sonos |
media_player.garage |
Garage | Sonos One | Sonos |
media_player.partyrummet |
Partyrummet | Sonos system (sub + surrounds) | Sonos |
media_player.sonos_move |
Portabel | Sonos Move | Sonos |
media_player.idas_rum_clock |
Idas rum | Logitech Squeezebox | Squeezebox |
media_player.alla_inne |
Group | All indoor speakers | MA Group |
Other speakers (not in MA):
media_player.ringklocka_hogtalare- UniFi Protect doorbell speaker
Each player has a button.*_favorite_current_song entity to save current track.
# Play via MA service
service: mass.play_media
data:
media_id: "Artist or Album Name"
media_type: artist # or album, track, playlist, radio
target:
entity_id: media_player.koket
# Or standard HA service
service: media_player.play_media
target:
entity_id: media_player.koket
data:
media_content_type: playlist
media_content_id: "Playlist Name"MA supports announcements that pause music and resume after:
service: tts.speak
target:
entity_id: media_player.koket
data:
message: "Någon vid dörren"| Appliance | Entities |
|---|---|
| Torktumlare | sensor.torktumlare_* - status, energy, job state |
| Höger kyl | climate.hoger_kyl_*, sensor.hoger_kyl_* |
| Vänster kyl | climate.vanster_kyl_*, sensor.vanster_kyl_* |
Refrigerators have climate controls for fridge and freezer compartments.
| Entity | Purpose |
|---|---|
vacuum.roborock_de_118057288_s5 |
Roborock S5 "Gun Gun" - main control |
sensor.roborock_de_118057288_s5_battery_level_p_3_1 |
Battery level |
sensor.roborock_de_118057288_s5_charging_state_p_3_2 |
Charging state |
select.roborock_de_118057288_s5_mode_p_2_2 |
Suction mode (Silent/Basic/Strong/Full Speed) |
States: docked, cleaning, returning, paused, idle, error
Automations:
dammsugare_schema_vardagar- Cleans weekdays at 10:00 when nobody homedammsugare_klar_notis- Notifies when cleaning completedammsugare_fel_notis- Notifies on error or stuckdammsugare_lagt_batteri_notis- Notifies on low battery
Room cleaning: Use Roborock app to set up room IDs, then call vacuum.send_command with room IDs.
| Switch | Purpose |
|---|---|
switch.uttag_brevlada |
Outdoor outlet at mailbox |
switch.uttag_dammbelysning |
Pond lighting outlet (Plejd) |
Automations auto-pull from GitHub on webhook, startup, and every 6h. Smart reload: only restarts services whose files changed (automations, scripts, scenes, Z2M).
- Always ask user before pushing - Never push without explicit permission
- Smart commit messages - Use descriptive messages based on what changed (not generic timestamps)
- Handle untracked files first - New files must be added to git or .gitignore before pushing
- Stage specific files - Use
git add <specific-files>, nevergit add -Aorgit add .
When asked to commit and push changes:
- Check for untracked files first:
git ls-files --others --exclude-standard - If untracked files exist, ask user: add to git or .gitignore?
- Update CLAUDE.md so it describes the change (see the rule at the top) and stage it in the same commit
- Stage specific files:
git add <files> - Commit with descriptive message:
git commit -m "Update automations and template sensors" - Push using PAT from secrets.yaml:
Read
git push https://<github_pat>@github.com/<github_repo>.git master
secrets.yamlforgithub_patandgithub_repovalues.
Update automations- when automations.yaml changedUpdate configuration- when configuration.yaml changedUpdate ESPHome: device-name- when esphome/ changedUpdate dashboards- when dashboards/ changedfeat: Description- new featuresfix: Description- bug fixes
- Proxmox Backup Server (PBS) - Primary backup for all VMs/LXCs (HA, MariaDB, InfluxDB)
- HA built-in snapshots (3 copies, local)
- Git (this repo) for config - public repo at github.com/petterl/Home-Assistant-Configuration
- Database performance & stability
- Expanding Zigbee mesh
- Building automations (lights, blinds, sensors)
- Lovelace & Grafana dashboards
- Google Home/Alexa integration
- Water leak detection automations
- Always validate YAML before restart:
/config/scripts/ha core check - Test automations in Developer Tools → Services first
- Commit working config to git before major changes
- Use
secrets.yamlfor all credentials:!secret key_name
- Exclude noisy entities from recorder (updates, system sensors)
- InfluxDB: only store what you'll graph
- Monitor MariaDB size, should stay stable with 10-day purge
- Mains-powered devices act as routers → better mesh
- Pair new devices close to coordinator, then relocate
- Swedish friendly names for consistency
- Check device health regularly:
ha z2m devices(STALE >6h, OFFLINE >24h) - Repeater outage cascades: if a repeater goes offline, all battery devices routing through it lose connectivity and may not recover until the repeater is back + devices are woken up
- Buttons/blinds have both direct Zigbee bindings AND HA automations for redundancy
- Fronius Smart Meter: provides all solar and grid data via Solarnet integration
- Exclude high-frequency energy sensors from recorder if causing bloat
- Keep it simple, one trigger/action to start
- Use scripts for reusable logic
- Blueprints for common patterns (motion lights, etc.)
- NEVER use
!secretin automations.yaml - prevents UI editing. Use hardcoded values or move secret-dependent automations to configuration.yaml
The addon requires these persistent packages (set in addon Configuration tab):
"persistent_apk_packages": ["chromium", "chromium-chromedriver"],
"persistent_pip_packages": ["selenium", "websocket-client", "pyyaml"]chromium+chromium-chromedriver: Headless browser for dashboard screenshots (ha_screenshot.py)selenium: Python Selenium bindings for screenshot automationwebsocket-client: WebSocket client for Jupyter kernel code execution (jupyter.py)pyyaml: YAML parsing forha_screenshot.py(missing this broke the screenshot script until installed persistently)
Also enable tmux_mouse_mode: true for scroll wheel support in the web terminal.
The ha command is available via /config/scripts/ha.
IMPORTANT: Always prefer scripts/ha over raw curl commands for HA operations. If a needed command is missing from the script, add it to scripts/ha rather than using one-off curl calls. This keeps operations consistent and reusable.
WARNING: NEVER run ha core stop - Claude runs in a HA addon, so stopping HA will kill the addon and you won't be able to restart it.
Grepping logs: ha core logs output contains ANSI colour codes and bytes that make grep treat it as binary and silently print nothing. Always use grep -a (and strip colours with sed 's/\x1b\[[0-9;]*m//g').
/config/scripts/ha core check # validate config - RUN AFTER EVERY YAML CHANGE
/config/scripts/ha core restart # apply changes (restarts HA)
/config/scripts/ha core logs # show recent logs (default 100 lines)
/config/scripts/ha core logs 2000 # show last 2000 lines
/config/scripts/ha core logs -f # follow logs
/config/scripts/ha core logs -f 200 # follow last 200 lines
/config/scripts/ha core info # show HA version and status
/config/scripts/ha addons # list all addons
/config/scripts/ha addons info <slug> # show addon info
/config/scripts/ha addons logs <slug> # show addon logs (default 100 lines)
/config/scripts/ha addons logs <slug> 30 # show last 30 lines
/config/scripts/ha addons logs <slug> -f # follow addon logs
/config/scripts/ha addons restart <slug> # restart addon
/config/scripts/ha addons start <slug> # start addon
/config/scripts/ha addons stop <slug> # stop addon
# Entity & service commands
/config/scripts/ha state <entity_id> # get state, attributes, last_changed
/config/scripts/ha search <pattern> # find entities matching regex pattern
/config/scripts/ha template "<jinja2>" # render any Jinja2 template
/config/scripts/ha call <domain.service> '<json>' # call a service with JSON data
# Config entries (websocket API)
/config/scripts/ha entry list [domain] # id, domain, state, disabled_by, title
/config/scripts/ha entry disable|enable <entry_id> # disable/enable an integration entry
/config/scripts/ha entry reload <entry_id> # reload an entry
# Zigbee2MQTT commands
/config/scripts/ha z2m devices # list all Z2M devices with last-seen status
/config/scripts/ha z2m permit-join [sec] # allow new devices to join (default 120s)
/config/scripts/ha z2m reconfigure <name> # reconfigure device (press button to keep awake!)
/config/scripts/ha z2m logs [N] # show Z2M logs (default 100 lines)
/config/scripts/ha z2m logs -f # follow Z2M logsEntity examples:
/config/scripts/ha state cover.moas_rullgardin
/config/scripts/ha search "moa.*rullgardin"
/config/scripts/ha template "{{ area_entities('kok') | join('\n') }}"
/config/scripts/ha call cover.set_cover_position '{"entity_id":"cover.moas_rullgardin","position":50}'Workflow for config changes:
- Edit YAML files
- Run
/config/scripts/ha core checkto validate - If valid, either let auto-reload pick up changes or run
ha core restart
Take screenshots of HA dashboards for visual verification. Dependencies installed at boot.
# Take screenshot
python3 /config/scripts/ha_screenshot.py "/lovelace-elektricitet/oversikt" "/config/www/screenshots/screenshot.png" 15
# View screenshot (Claude can read images)
# Read /config/www/screenshots/screenshot.pngCredentials stored in secrets.yaml:
ha_username: screenshot_botha_password: (stored in secrets)
Claude Code can access JupyterLab's API directly (nginx patched via addon init_commands).
Connection:
- Base URL:
http://172.30.33.4:8099 - WebSocket:
ws://172.30.33.4:8099 - XSRF: use
-H "X-XSRFToken: dummy" -b "_xsrf=dummy"for POST/DELETE/PUT - Notebooks root:
/config/notebooks/(shared filesystem) - Addon slug:
a0d7b954_jupyterlablite
Helper script: /config/scripts/jupyter.py - wraps all Jupyter API operations.
# Execute code on a Jupyter kernel
python3 /config/scripts/jupyter.py execute "print('hello')"
# Start a persistent kernel (returns kernel ID)
python3 /config/scripts/jupyter.py kernel-start
# Execute on existing kernel
python3 /config/scripts/jupyter.py execute --kernel-id <ID> "import pandas as pd; print(pd.__version__)"
# Stop a kernel
python3 /config/scripts/jupyter.py kernel-stop <ID>
# List running kernels
python3 /config/scripts/jupyter.py kernel-list
# List notebooks
python3 /config/scripts/jupyter.py list
# Create a notebook
python3 /config/scripts/jupyter.py create "my_analysis.ipynb" "print('hello')" "# Markdown cell"Nginx patch mechanism: The addon's init_commands patches nginx to allow the addon subnet (172.30.33.0/24). This runs on every addon restart. If JupyterLab addon is updated and access breaks, restart the addon to re-apply the patch.
IMPORTANT: Always validate dashboards after any edit. Run all three checks:
- YAML syntax validation
ha core check- Entity reference verification (check all referenced entities exist and have valid states)
YAML dashboards are in dashboards/. Validate with:
# Validate apexcharts-card configurations (checks for common issues)
python3 /config/scripts/validate_apexcharts.py /config/dashboards/DASHBOARD.yamlTo make cards span multiple columns, use layout-card (installed via HACS):
views:
- title: My View
type: custom:grid-layout # Required on the view
cards:
- type: custom:apexcharts-card
view_layout:
grid-column: span 2 # Span 2 columns
# ... rest of card config# 1. Validate YAML syntax
python3 -c "import yaml; yaml.safe_load(open('/config/dashboards/DASHBOARD.yaml')); print('Valid')"
# 2. Run HA config check
/config/scripts/ha core check
# 3. Extract and verify all entity references exist
python3 << 'EOF'
import yaml, json, urllib.request, os
with open('/config/dashboards/DASHBOARD.yaml') as f:
dashboard = yaml.safe_load(f)
entities = set()
def find_entities(obj):
if isinstance(obj, dict):
for k, v in obj.items():
if k == 'entity' and isinstance(v, str) and '.' in v:
entities.add(v)
elif k == 'entities' and isinstance(v, list):
for item in v:
if isinstance(item, str) and '.' in item:
entities.add(item)
elif isinstance(item, dict) and 'entity' in item:
entities.add(item['entity'])
else:
find_entities(v)
elif isinstance(obj, list):
for item in obj:
find_entities(item)
find_entities(dashboard)
token = os.environ['SUPERVISOR_TOKEN']
for entity in sorted(entities):
data = json.dumps({"template": f"{{{{ states('{entity}') }}}}"}).encode()
req = urllib.request.Request('http://supervisor/core/api/template', data=data,
headers={'Authorization': f'Bearer {token}', 'Content-Type': 'application/json'})
state = urllib.request.urlopen(req).read().decode().strip()
status = '✗' if state in ['unavailable', 'unknown'] else '✓'
print(f"{status} {entity}: {state[:40]}")
EOF# List measurements
curl -s "http://192.168.1.62:8086/query?db=homeassistant&q=SHOW+MEASUREMENTS" | python3 -c "import sys,json; print('\n'.join([m[0] for m in json.load(sys.stdin)['results'][0]['series'][0]['values']]))"
# Query data
curl -s "http://192.168.1.62:8086/query?db=homeassistant" --data-urlencode "q=SELECT mean(value) FROM \"W\" WHERE entity_id='smart_meter_ts_65a_3_aktiv_effekt' AND time > now() - 1h GROUP BY time(5m)"
# Check entity data exists
curl -s "http://192.168.1.62:8086/query?db=homeassistant" --data-urlencode "q=SELECT count(value) FROM \"W\" WHERE entity_id='ENTITY_ID'"Dashboards stored in /config/grafana/. After editing:
- Validate JSON:
python3 -c "import json; json.load(open('/config/grafana/FILE.json')); print('Valid')" - Re-import in Grafana UI (Dashboards → Import → Upload JSON)
- Datasource UID must match:
influxdb(lowercase)
A bare "review" / "gör en review" means a setup health review → use the ha-review skill
(.claude/skills/ha-review/, data collector collect.sh), not code-review on the diff.
IMPORTANT: All reviews MUST include checking logs:
- Core logs:
/config/scripts/ha core logs- filter for errors/warnings - Addon status:
/config/scripts/ha addons- check all addons are running - Addon info:
/config/scripts/ha addons info <slug>- check for updates - Addon logs:
/config/scripts/ha addons logs <slug>- check for addon-specific errors
Run periodically to analyze configuration and suggest improvements:
Review the current HA setup: automations, template sensors, dashboards, and Zigbee config.
Check core logs and addon status for errors. Identify duplication, anti-patterns, and suggest best practices.
Look for opportunities to use blueprints, consolidate sensors, or improve efficiency.
Fast check for errors and issues:
Check HA core logs for errors/warnings (exclude custom integration warnings).
Check all addons are running and look for available updates.
Verify all automations are enabled and confirm key sensors are working.
Review energy monitoring setup:
Review the energy monitoring setup: Nordpool integration, peak power tracking,
solar production, and consumption sensors. Check logs for energy-related errors.
Suggest improvements for cost optimization.
Check Zigbee mesh health:
Review Zigbee2MQTT configuration, device bindings, and mesh topology.
Check Z2M addon status and logs for pairing/communication errors.
Check for devices with poor link quality or missing router coverage.
HA entity states cannot exceed 255 characters. SQL sensors returning JSON must:
- Return the primary value as state (short)
- Put detailed data in attributes
- Example:
sensor.peak_power_datareturns2.235as state, peaks array inpeaks_jsonattribute
Proxmox-värdens NIC nic0 (Intel I219-V, 0000:00:1f.6, drivrutin e1000e, switchport 21 på
USW 24 PoE) kan låsa sig: e1000e ... nic0: Detected Hardware Unit Hang. Värden och alla VM/LXC
fortsätter gå men ingen trafik når ut — ser ut som att "HA är nere". Hände 2026-10-03 22:45 →
2026-10-06 (3,5 dygn, Petter bortrest); löstes först av omstart av värden (skärmen var en slump).
- Kännetecken: HA-journalen visar
enp6s18 ... ip-config-unavailable(ingen DHCP) i loop,nfs: server 192.168.1.9 not responding; logbooken: UniFi/Sonos/Atlas → unavailable samtidigt men Zigbee, MariaDB (.61) och Proxmox-API fortsätter (intern brygga). vzdump → PBS timeout. Switch/Zeus-uptime opåverkad. - Bekräfta på värden:
journalctl -b -N | grep -iE "e1000e|hang"(Proxmox-token saknarSys.Syslog). - Fix införd 2026-10-06:
post-up /usr/sbin/ethtool -K nic0 tso off gso off gro offunderiface nic0i/etc/network/interfacespå ares (+ körd direkt). Verifiera:ethtool -k nic0 | grep -E "tcp-segmentation|generic-(segmentation|receive)"→ allaoff. Ingen ping-vakt ännu. Om hänget återkommer trots detta: lägg en cron-vakt som startar omnic0.
The following entities exist but devices are not paired to Zigbee2MQTT:
binary_sensor.ida_smartplug_aktiv- referenced in button descriptions but no Z2M devicebinary_sensor.moa_smartplug_aktiv- same issue Action: Either re-pair physical devices or remove orphaned entities via HA UI
Enabled with 0 SEK/kWh threshold (only limits when price goes negative).
input_boolean.export_begransning_aktiv: ONinput_number.export_begransning_pris: 0- Uses Fronius Modbus registers 40236/40246
~70% of energy consumption is untracked ("Okänd"). Tracked devices:
- FTX, CASA, Frys, Network (Zigbee smart plugs)
- Torktumlare (SmartThinQ) Missing: Refrigerators, oven/hob, water heater, lighting
- Use
level: INFOfor logging (not DEBUG) - Always set OTA password via
!secret ota_password - Water meter (t-display) cannot run Bluetooth proxy due to hardware conflicts
- HTTP-inställningarna bor i GUI:t, inte i YAML. HA har migrerat
http:till Inställningar → System → Nätverk (/config/.storage/http,yaml_migration_done: true).http-blocket iconfiguration.yamlär medvetet borttaget (commit0ebfda6) — lägg inte tillbaka det. Aktiva värden:ip_ban_enabled: true,login_attempts_threshold: 10,use_x_forwarded_for: true, trusted proxies = 192.168.1.70/32 + 172.30.32.0/23 + 172.30.33.0/24 + 127.0.0.1/32. Verifiera medcat /config/.storage/http. - GitHub repo is public - webhook ID in automations.yaml is visible but low risk (only triggers git pull)
- Secrets.yaml properly excluded from git