Differences

This shows you the differences between two versions of the page.

--- infra:services:homeassistant [2024/03/23 19:23] – created kfh
+++ infra:services:homeassistant [2026/06/26 15:59] (current) – [Current State Notes] kfh
@@ Line 1: / Line 1: @@
-# Home assistant
+====== Home Assistant ======
+Home Assistant controls parts of the physical hackerspace, including ceiling lights, Zigbee devices, WLED installations, media/cast devices, and related automations.
+  * NetBox: https://ip.hackeriet.no/dcim/devices/72/
+===== Access =====
+==== Web ====
+  * Web UI: [[http://10.10.3.115:8123/|10.10.3.115:8123]]
+  * mDNS name, when working: [[http://hassio.local:8123|hassio.local:8123]]
+  * Login credentials: `hackerpass hassio.local`
+  * Hackerpass documentation: [[infra:hackerpass]]
+  * Hackerpass repository: https://github.com/hackeriet/pass
+==== Pi ====
+Talk to @kfh or @sjn who have SSH access, and they can add your key. The IP address is bound to a Docker container, so it won't help to just add the key to any OS user.
+The Pi takes a long time to boot up after a power cycle, around 5 minutes.
+===== NetBox =====
+  * Device: `hassio`
+  * Primary IP: `10.10.3.115/24`
+  * Location: `Audiocorner`
+  * Rack: `Audiorack`
+  * Switch port: `hackeriet-sw` `GigabitEthernet0/15`
+  * Device page: https://ip.hackeriet.no/dcim/devices/72/
+Known mismatch to verify physically:
+  * NetBox says `Raspberry Pi 3 Model B v1.2`
+  * This page has historically said Raspberry Pi 3B / 3B+
+===== Hardware =====
+Home Assistant runs on a Raspberry Pi in the rack with the audio gear.
+  * Raspberry Pi 3B+ (32 bit ARM v7)
+  * RaspBee (deRFmega256-23M12)
+Zigbee devices, like the IKEA lights and buttons, run through a Zigbee stick that's plugged directly into the Pi's GPIO headers. deCONZ, with the Phoscon interface, is used as bridge between Zigbee stick and the Home Assistant runtime.
+===== Software =====
+As of 2026-06-21:
+  * Home Assistant Core: `2025.11.3`
+  * Time zone: `Europe/Oslo`
+  * Location name: `Hackeriet`
+Important integrations and add-ons:
+  * deCONZ / Phoscon for Zigbee lights, switches, sensors, and groups
+  * WLED for LED/light installations
+  * Cast media players
+  * OctoPrint integration
+  * Backup integration
+  * Terminal & SSH add-on
+  * AirCast add-on
+  * Zigbee2mqtt and Zigbee2mqtt Assistant add-ons
+===== Areas =====
+Configured Home Assistant areas:
+  * Baren
+  * Projektor
+  * Sofakroken
+  * Arbeidsbord
+  * Scenen
+  * Hoveddøra
+  * Dør bakgård
+  * Hackeriet
+  * Pinball-veggen
+  * Kjøleskapet
+  * Brusskapet
+===== Operational Checks =====
+Basic checks:
+  * Ping `10.10.3.115`
+  * Open [[http://10.10.3.115:8123/|10.10.3.115:8123]]
+  * Check that the UI loads and login works
+  * Check power and cabling at the Raspberry Pi
+  * Check the switch port documented in NetBox
+Useful UI pages:
+  * Settings -> Repairs
+  * Settings -> System -> Updates
+  * Settings -> System -> Backups
+  * Settings -> Devices & services
+  * deCONZ / Phoscon status
+  * WLED device availability
+  * Zigbee sensor battery status
+===== Current State Notes =====
+**2026-06-26**
+KFH: Tried poking at the controller through the UI a bit, this seems to have been the fix for the plugs:
+- In Hassio: restart the DeConz plugin
+- Open up the DeConz dashboard
+- Disconnect and re-connect the plugs that were missing (the plug itself, not its load)
+- For the Matelight plug that didn't come back up: trigger pairing in DeConz and then disconnecting and re-connecting it
+All four plugs appear to be live now, and everything turns off and on with the button as is supposed to.
+As of 2026-06-21, Home Assistant had many unavailable entities. This does not necessarily mean Home Assistant itself is broken, but it is useful context when debugging devices or automations.
+Largest unavailable groups:
+  * WLED devices, especially `LED strips`, `Cold North heater`, `Prusalight`, `PAR (DMX)`, `WLED`, and `Sprinkler`
+  * deCONZ devices, including some door/window sensors, smart plugs, motion sensor, cube, and some lights/groups
+  * OctoPrint entities
+  * Cast media players
+Pending updates at that time:
+  * Terminal & SSH: `9.20.1` -> `10.3.0`
+  * deCONZ: `8.5.2` -> `8.7.0`
+  * AirCast: `4.2.4` -> `5.1.1`
+  * Some WLED firmware entities reported updates
+No pending Home Assistant Core, Supervisor, or Home Assistant OS update was observed at that time.
+===== Backups =====
+Home Assistant has backup entities configured.
+As of 2026-06-21:
+  * Backup manager state was `idle`
+  * Last automatic backup event was `2026-06-20T14:32:00.998+00:00`
+  * Some backup status sensors reported `unknown`
+Check backup configuration from the Home Assistant UI before relying on it for recovery.
+===== Debug =====
+==== Powercycle ====
+We've had issues with lights bouncing between modes and turning off randomly. The current theory is that new lights get stuck in a weird split-brain state when added through deCONZ. A reboot of the entire device seems to fix this.
+Update: Eirik and Deburd found that the reboot was just after OTA happens. So we tracked it to https://github.com/dresden-elektronik/deconz-ota-plugin/issues/37, where unfortunately this git issue had no solution when we checked.
+However, we turned off OTAU in the DeCONZ VNC app, and the power cycles stopped.
+We also turned off OTAU in the phoscon app settings, so that may also have fixed the problem.
+Anyhow, disabling OTAU in one of the places seems to have fixed the issue.
+==== Lightbulb naming convention ====
+Our six main ceiling lamps each have four bulbs. The lamps are numbered `1` through `6` in clockwise order around the room.
+Within each lamp, the bulbs are named `A` through `D`.
+{{:infra:services:lights.png?400|}}
+Use this naming when matching Home Assistant entities to physical bulbs, for example `1A`, `1B`, `1C`, `1D`, up to `6A`, `6B`, `6C`, `6D`.
+===== Maintenance Notes =====
+Before cleaning up devices or entities:
+  * Check whether unavailable devices are expected to still exist
+  * Check whether devices were renamed or moved
+  * Check whether WLED, OctoPrint, Cast, or Zigbee devices are powered and reachable
+  * Keep IP addresses, cabling, and placement in NetBox
+  * Keep service and recovery documentation here
+Likely cleanup areas:
+  * Stale WLED devices or renamed WLED entities
+  * OctoPrint integration if the printer/service no longer exists or has moved
+  * Cast devices no longer in use
+  * Duplicate or legacy Zigbee entities
+  * Raspberry Pi model mismatch between this page and NetBox
+===== Recovery =====
+If Home Assistant is down:
+  - Check power to the Raspberry Pi in the audio rack.
+  - Wait several minutes after power cycling before assuming boot failed.
+  - Check network reachability to `10.10.3.115`.
+  - Check the switch port documented in NetBox.
+  - Use `hackerpass hassio.local` for login credentials.
+  - If the UI is reachable, check Repairs, Updates, Backups, and Devices & services before making changes.
+===== Files =====
+  * {{ :infra:services:hassio:mega23m12.15-mega23m12-user-manual-2047839.pdf | deRFmega256-23M12 Manual (RaspBee radio) }}
+  * {{ :infra:services:hassio:derfmega128-22m00_22m10_22m12_23m00_23m10_23m12-bhb-en.pdf | deRFmega256-23M12 Datasheet (RaspBee radio) }}
+  * {{ :infra:services:hassio:raspbee-bhb-en.pdf | RaspBee manual }}
+===== Gallery =====
+{{gallery>:infra:services:hassio}}