Differences

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

--- infra:services:homeassistant [2024/03/25 19:26] – [Web] kfh
+++ infra:services:homeassistant [2025/03/08 15:13] (current) – [Hardware] marcusramberg
@@ Line 14: / Line 14: @@
 ==== Web ====
-. Get [[infra:services:hackerpass | Hackerpass]]
+  - Get [[infra:hackerpass | Hackerpass]] -
-. Go to [[http://hassio.local:8123|hassio.local:8123]] (or [[http://10.10.3.115:8123|10.10.3.115:8123]] if mDNS fails) in your favorite web browser
+  - Go to [[http://hassio.local:8123|hassio.local:8123]] (or [[http://10.10.3.115:8123| 10.10.3.115:8123]] if mDNS fails) in your favorite web browser
-. Log into web using the `hassio.local` Hackerpass credentials
+  - Log into web using the `hassio.local` Hackerpass credentials
 ==== Pi ====
@@ Line 24: / Line 24: @@
 ===== Hardware =====
-* Raspberry Pi 3B+ (32 bit ARM v7)
+  * Raspberry Pi 3B+ (32 bit ARM v7)
-* RasbBee (deRFmega256-23M12)
+  * RasbBee (deRFmega256-23M12)
 ===== Debug =====
@@ Line 33: / Line 33: @@
 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 four-lightbulb lights are named per numbers, 1 being on the short wall, away from the windows. Then each lightbulb is names A-D, a being closest to the corner.
+{{:infra:services:lights.png?400|}}
 ===== Files =====