| 2026-09-16 |
Document navi.service (Navi Proxy, port 8099) on ovpn_reserv
...
Verified via SSH on 2026-09-16: VM ovpn_reserv (192.168.1.226) runs navi.service (systemd, user ubuntu, WorkingDirectory /home/ubuntu/navi-1, ExecStart .venv/bin/navi-server) listening on 0.0.0.0:8099 with /health endpoint. Config at /home/ubuntu/navi-1/.env (OLLAMA_API_KEY, OLLAMA_HOST=https://ollama.com). No ollama_backends.json exists. SSH access as user ubuntu (root denied). No secrets stored.
|
Document VM tg_bots (192.168.1.254) navi melody instance and Ollama key rotation
...
New doc 10-systems/servers/tgbots-vm-navi-melody.md: VM tg_bots (192.168.1.254, hostname tgbots) runs mardisbot.service and navi.service (navi instance melody, port 8099, WorkingDirectory /home/ubuntu/navi-1). Ollama API key rotated 2026-09-16 in /home/ubuntu/navi-1/.env; ollama_backends.json not present on this instance; backup .env.bak-ollama-20260916 created; service restarted and verified active with /health HTTP 200.
|
Add service-host (192.168.1.176) doc and inventory: navi zoe instance + GHard panel
...
Rotated Ollama API key on navi zoe instance (192.168.1.176): updated OLLAMA_API_KEY in /home/ubuntu/navi-1/.env, restarted navi.service (active). No ollama_backends.json exists on the host. Documented host and service in gnexus-book (no secret values stored).
|
| 2026-09-04 |
Fix dead action aliases in API examples; add live-alias warning
...
Live recon 2026-09-04 confirmed the example aliases master_room_lamp_switcher and hallway2_lamp_switcher are dead (not registered by code, return null). Replaced with live aliases master_toggle and hall2_toggle; added a warning pointing to the verified live action list.
|
smart-home-server: add GAuth fix verification status (cross-context state validation confirmed)
...
Verification status appended to the GAuth OAuth State/PKCE Storage section: cross-context state validation confirmed via two-cookie-jar flow emulation on 2026-09-04.
|
Document file-based GAuth OAuth state/PKCE stores applied on 2026-09-04
...
Applied the file-based OAuth state/PKCE store fix on shome (2026-09-04); storage locations, wiring, and rollback backups are durable operational facts for future auth debugging.
|
smart-home-server: задокументирован SSH-пользователь shome, зафиксирован часовой пояс Europe/Kyiv после фикса
...
Live SSH diagnostics on 2026-09-04: host timezone was Etc/UTC (local time lagged 3h behind Kyiv), NTP was healthy. Fixed via timedatectl set-timezone Europe/Kyiv; /etc/timezone and /etc/localtime verified. SSH username shome discovered (was undocumented) and added to hosts inventory. Doc updated with Access & Time section.
|
| 2026-05-14 |
Add API usage instructions for triggering ControlScripts actions to smart-to-home-server.md with frontmatter.
...
Adding API usage instructions for triggering actions, as discovered during troubleshooting. I included the frontmatter to avoid validation errors.
|
| 2026-05-10 |
Document smart home server platform
Eugene Sukhodolskiy
committed
on 10 May
|
Seed smart home and 3D printer knowledge
Eugene Sukhodolskiy
committed
on 10 May
|
| 2026-05-09 |
Document home LAN topology and discovery observations
Eugene Sukhodolskiy
committed
on 9 May
|
Document public VPN and internal proxy route
Eugene Sukhodolskiy
committed
on 9 May
|