1
posts
2
3
4
5
6
7
8
9
I'm running HAOS on a mini x86 PC with localai.io running on a local server with an Intel A750. The model I'm currently using is qwen3:4b-instruct-2507-q4_K_M which should support tool use.
I've tried other models and had similar results.
The debug spew for the above interaction is below. Of note, the data field of intent_output is empty.
Is this something I need to configure on the localai.io side? Something with the yaml file? Or is HA not catching the intents coming from localai?
stage: done
run:
pipeline: 01m4qn8aamt08pa8q3gprs8g9y
language: en
conversation_id: 01M4SQBP7364Q234NHBDAVQF4V
runner_data:
stt_binary_handler_id: null
timeout: 300
events:
- type: run-start
data:
pipeline: 01m4qn8aamt08pa8q3gprs8g9y
language: en
conversation_id: 01M4SQBP7364Q234NHBDAVQF4V
runner_data:
stt_binary_handler_id: null
timeout: 300
timestamp: '2026-10-13T04:12:03.684196+00:00'
- type: intent-start
data:
engine: conversation.ollama_conversation
language: en
intent_input: turn off the kitchen lights
conversation_id: 01M4SQBP7364Q234NHBDAVQF4V
device_id: null
satellite_id: null
prefer_local_intents: false
timestamp: '2026-10-13T04:12:03.684286+00:00'
- type: intent-progress
data:
chat_log_delta:
role: assistant
content: ''
timestamp: '2026-10-13T04:12:03.834864+00:00'
- type: intent-progress
data:
chat_log_delta:
content: intent
timestamp: '2026-10-13T04:12:03.835315+00:00'
- type: intent-progress
data:
chat_log_delta:
content: __
timestamp: '2026-10-13T04:12:03.888268+00:00'
- type: intent-progress
data:
chat_log_delta:
content: H
timestamp: '2026-10-13T04:12:03.941413+00:00'
- type: intent-progress
data:
chat_log_delta:
content: ass
timestamp: '2026-10-13T04:12:03.997781+00:00'
- type: intent-progress
data:
chat_log_delta:
content: Turn
timestamp: '2026-10-13T04:12:04.052061+00:00'
- type: intent-progress
data:
chat_log_delta:
content: 'Off'
timestamp: '2026-10-13T04:12:04.108197+00:00'
- type: intent-progress
data:
chat_log_delta:
content: ("
timestamp: '2026-10-13T04:12:04.160317+00:00'
- type: intent-progress
data:
chat_log_delta:
content: light
timestamp: '2026-10-13T04:12:04.214299+00:00'
- type: intent-progress
data:
chat_log_delta:
content: '",'
timestamp: '2026-10-13T04:12:04.267968+00:00'
- type: intent-progress
data:
chat_log_delta:
content: ' "'
timestamp: '2026-10-13T04:12:04.320906+00:00'
- type: intent-progress
data:
chat_log_delta:
content: Kitchen
timestamp: '2026-10-13T04:12:04.376033+00:00'
- type: intent-progress
data:
chat_log_delta:
content: '")'
timestamp: '2026-10-13T04:12:04.432053+00:00'
- type: intent-progress
data:
chat_log_delta:
content: ''
timestamp: '2026-10-13T04:12:04.485825+00:00'
- type: intent-progress
data:
chat_log_delta:
content: ''
timestamp: '2026-10-13T04:12:04.486312+00:00'
- type: intent-progress
data:
chat_log_delta:
content: ''
timestamp: '2026-10-13T04:12:04.486666+00:00'
- type: intent-end
data:
processed_locally: false
intent_output:
response:
speech:
plain:
speech: intent__HassTurnOff("light", "Kitchen")
extra_data: null
card: {}
language: en
response_type: action_done
data:
success: []
failed: []
conversation_id: 01M4SQBP7364Q234NHBDAVQF4V
continue_conversation: false
timestamp: '2026-10-13T04:12:04.488028+00:00'
- type: run-end
data: null
timestamp: '2026-10-13T04:12:04.488136+00:00'
started: 2026-10-13T04:12:03.684Z
intent:
engine: conversation.ollama_conversation
language: en
intent_input: turn off the kitchen lights
conversation_id: 01M4SQBP7364Q234NHBDAVQF4V
device_id: null
satellite_id: null
prefer_local_intents: false
done: true
processed_locally: false
intent_output:
response:
speech:
plain:
speech: intent__HassTurnOff("light", "Kitchen")
extra_data: null
card: {}
language: en
response_type: action_done
data:
success: []
failed: []
conversation_id: 01M4SQBP7364Q234NHBDAVQF4V
continue_conversation: false
finished: 2026-10-13T04:12:04.488Z
10
ha-iroh: p2p Android app for Home Assistant, garage door from the power menu, no port forward / VPN / cloud
(sh.itjust.works)
Background: I used Tailscale for remote access to HA. It mostly worked well, but in the driveway the phone is half on cellular, half on wifi. The HA app keeps an old connection and hangs most of the time when I just quickly want to open the garage door. Kill, reopen, wait. That was annoying enough that I wrote something that fixes that over the weekend.
ha-iroh is a small Android app plus a HACS integration, built on iroh (p2p QUIC). Every phone has a keypair with HA, traffic is end-to-end encrypted, NAT hole punching is done automatically where possible, otherwise a relay is used that only sees ciphertext. Setup (one-time, first connection) is done by scanning a QR-Code.
There is no persistent tunnel. The app dials HA when you tap something and disconnects afterwards, so network switches don't matter and my in-front-of-the-garage-door wait is gone.
Features
- Device Controls in the Android power menu / quick settings: lights, switches, fans, climate, covers, locks, scenes, scripts, buttons, with live state
- Assist via quick settings tile or launcher shortcut (text only for now)
- the normal HA dashboard in a WebView, login once, any auth provider incl. MFA
- several HA instances in one app
- pairing by QR code from the HA config flow. Delete the device in HA and the phone is out
Not included, on purpose Sensors, location, notifications, widgets, Wear OS, iOS. I still use the official app for all of that. ha-iroh only covers quick control when I'm not home.
Status
- v0.2.x. I've not received any major bug reports yet, but DO expect rough edges. For me at least it currently works reliably enough.
- Android 12+, arm64 APK via GitHub Releases or Obtainium. Not on Play.
- HA 2026.3+, HACS custom repo. The integration starts a small Rust bridge as a subprocess, x86_64 and aarch64 bundled, so HA OS / Container / Supervised work.
- Optional: forward one UDP port and iroh connects directly always instead of sometimes via relay. Not required.
- Two HA settings to check, both in the README:
ip_ban_enabled(the bridge connects from localhost, so wrong passwords from one phone can ban 127.0.0.1, i.e. all phones) and never put loopback intotrusted_networks.
Disclosure
Large parts of this were built with an LLM. If that's a dealbreaker for you, this project is not for you.
Links
- Repo + install guide: https://github.com/pzeinlinger/ha-iroh
- MIT
- https://buymeacoffee.com/pzeinlinger
Bug reports welcome, especially from people behind CGNAT or on Fritz!Box / MikroTik.
11
This morning (2026-10-11 07:10:00), I updated to Core 2026.10.1. After the update a few repairs showed up. One was for a Script that has been running for 3 years. Somehow an "Attribute" was inserted in the script, which was not there before the update. I fixed it by deleting the "Attribute". Then there are three devices which has been in my HA for more than 3 years and it is complaining on "... has area but no name on its own".
Edit: I think I know what these are: they are ghost devices which are now resurrected by the Update. The thing is there is no "delete" option when I go to their settings!
12
I hired an illustrator to draw my house. Now it's my Home Assistant dashboard.
(antonfrolov.substack.com)
13
14
15
16
17
18
19
20
21
22
23
What is your update policy? Are you on auto update, or do you manually go over stuff, do you pick a day to just flush it all though, or are you just on an old version?
Share why and how you run your updates? I would like to hear how you all manage them
24
25
view more:
next ›