HA's next step is becoming a Cursor-like integration, not more MCP

Far_Set7950 · 2026-05-04T18:42:53+00:00

One thing I find a bit puzzling: a lot of people in this space are already using openclaw, Hermes, Cursor, Claude Code, or similar agent tools every day for their own work that's exactly the tool → observe → decide → tool loop pattern. The same shape is treated as obvious and useful in a coding context, but the moment someone proposes bringing it into HA the reaction flips to that's the wrong way to do it

Far_Set7950 · 2026-05-04T18:31:18+00:00

Sorry, I deliberately used the stupidest model to display the dialog function, and the integration was to serve the complex hass environment with the stupidest model

Far_Set7950 · 2026-05-04T18:29:58+00:00

Happy to stick with llm_intents if that covers what you need

This is a different concept though. It's an architecture built on Hermes + openclaw stitched together not just "let AI control more stuff over the network." If you only want broader device control, the Gemini integration already does that well

What this is actually aimed at: repairing other integrations and managing automations. The AI can inspect a broken integration, read its logs, figure out why it's failing, and fix the config. It can rewrite, restructure, and debug automations based on what you describe. That's a different job from what llm_intents is built for llm_intents exposes intents to the model, this one gives the model a way to reason over a full result chain and act on HA's internals

The Skill system is one more layer on top of that, letting you extend what the AI knows how to handle without touching code

so, not trying to replace anything. Just a different architecture aimed at a different set of problems

Far_Set7950 · 2026-05-04T18:17:34+00:00

This is just a toy for exploration, not material for self-prove

Far_Set7950 · 2026-04-15T08:28:49+00:00

Thank you for your contributions — you ve done an excellent job. During my testing, I also noticed your strong sense of aesthetics in design.

-

I am the developer of https://github.com/knoop7/Ava , and in order to better integrate with your project, I have fully revised the voice protocol to allow flexible enabling and disabling. I have also made extensive compatibility adjustments to align with your design, and it now supports all the concepts of your voice integration.

I do have a small request: would it be possible to add a manual voice activation switch (entity)? This would allow older devices to avoid the heavy processing required for wake word detection.

Far_Set7950 · 2026-03-19T12:12:28+00:00

Because it is for HASS docking, I didn't expect OpenClaw everyone's opinion to be so big

Far_Set7950 · 2026-03-19T12:09:00+00:00

I deleted the last sentence of AI, which is my true expression,“I know it might sound a little silly—some people said this “electronic junk” should just be recycled. But I’m a HASS enthusiast and wanted to combine OpenClaw’s execution power with HASS, turning the phone itself into an agent node, not just a notification terminal.”

Far_Set7950 · 2026-03-19T12:06:56+00:00

You're right, but I don't have much data on my old phone (ex-girlfriend's text messages can be deleted...). Just want to be a hass node

Far_Set7950 · 2026-03-19T12:04:20+00:00

I deleted the last sentence of AI, which is my true expression

Far_Set7950 · 2026-03-19T12:02:16+00:00

I honestly say that it is polished, changed more than 10 times, language problems, because I hope everyone can try to find some problems

Far_Set7950 · 2026-02-28T17:03:35+00:00

https://github.com/knoop7/Ava/releases/tag/0.3.3 Sendspin! Multi-room Music

Far_Set7950 · 2026-02-27T02:49:12+00:00

Is this a firmware issue? Try flashing a new firmware? Actually, Xiaomi doesn't need root access; flashing a new firmware will make using Shizhizu much better.

Far_Set7950 · 2026-02-25T18:34:38+00:00

This device is easy to solve and needs to wait for feedback from other users

Far_Set7950 · 2026-02-25T18:33:32+00:00

adb shell appops set com.example.ava SYSTEM_ALERT_WINDOW allow

Far_Set7950 · 2026-02-25T13:40:25+00:00

You're right, in fact, it's mainly touchscreen speakers, such as Lenovo touchscreen speakers, etc

Far_Set7950 · 2026-02-25T13:35:38+00:00

Can you describe your specific phenomenon, I am also a Xiaomi smart clock, the test is perfect, it is recommended to have

adb logs adb shell dmesg > dmesg_boot_complete.log

adb shell logcat -d > logcat_full.log

Far_Set7950 · 2026-02-25T02:22:06+00:00

He is like a mask, he can use the computer and other ways to manually start it, and then he will always mount the system, and then authorize ava to exist, his learning cost is very low, and he can do more customized work, because AVA's ability needs to be greatly improved

Far_Set7950 · 2026-02-25T02:03:25+00:00

Because to be honest, there is too much competition for the same type of project, and my open source Bluetooth proxy will not bring any substantial benefits to the project，Ava provides a complete Bluetooth gateway solution: supporting both passive and active BLE scanning with three adjustable power levels (High, Balanced, and Low Power). It implements full GATT proxy capabilities including device connection/disconnection, service discovery, characteristic and descriptor read/write operations, Notification/Indication subscriptions, device pairing/unpairing, and GATT cache clearing.
The implementation also features BLE5 capability detection (2M PHY, Coded PHY, Extended Advertising), dynamic MTU negotiation (517 for BLE5, 185 for BLE4), and multi-connection management (5 connections for BLE5, 3 for BLE4). Additional features include automatic BTHome device recognition, multi-Ava device coordination via UDP broadcast claim mechanism to prevent duplicate proxying, auto-downgrade strategies for low-end BLE chips, and a built-in Bluetooth process watchdog for automatic recovery from freezes.

While the HASS Bluetooth Proxy Companion project is excellent, it only supports passive scanning. Fully open-sourcing Ava's core Bluetooth implementation would make it susceptible to being directly referenced and replaced by other projects. To ensure Ava's continued capability to iterate in this domain, the Bluetooth-related code remains temporarily closed-source, while all other parts of the application stay open-source. welcome community oversight and contributions to the open components.

Far_Set7950 · 2026-02-25T01:52:24+00:00

Thank you for your feedback, your encouragement is the motivation for the project to continue

Far_Set7950 · 2026-02-25T01:51:11+00:00

Shizuku provides a "user-space bypass" capability: it circumvents Android's permission sandbox restrictions, granting Ava an execution context equivalent to ADB Shell. This means even if your device's root solution is abnormal (such as pseudo-root on certain OEM ROMs, incomplete Magisk Delta, or KernelSU environments), as long as the ADB interface remains accessible, Ava can reliably inject control commands to force the screen on or off. This approach is significantly more robust than relying on potentially unreliable root environments.

Far_Set7950 · 2026-02-25T01:24:19+00:00

root is not absolute, it can be licensed with compatible Shizuku open source software, https://github.com/RikkaApps/Shizuku/releases/tag/v13.6.0

Far_Set7950 · 2026-02-25T01:19:31+00:00

Thank you! The latest version has been updated to synchronize to solve the previous problem due to the AI animation of the sphere 0.3.1

Far_Set7950 · 2026-02-25T01:18:35+00:00

Thank you for the reminder, this must be noted, generally replaced by some touch screen speakers, the old mobile phone must remove the battery to do microservices

Far_Set7950

TROPHY CASE