Missing Home Assistant building block (feedback) #2295
Unanswered
cornebistouille
asked this question in
I'm not sure
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Missing Home Assistant building block (feedback)
While building an AI intgegrartion, one limitation became very clear.
What would greatly simplify external API / AI integrations is a native long-text state variable:
Desired characteristics
Permanent (survives restarts)
Not historized
No length limit (or very high)
Readable directly from dashboard cards
Event-driven (trigger on change / duration)
Writable from automations
Modifiable from Python scripts / external APIs
In short:
A permanent, non-historized, long-text state, designed for communication
with external services (AI, diagnostics, summaries). a new value would simply erase the old one.
This would fully respect Home Assistant’s philosophy:
no polling
no database bloat
no filesystem hacks
It would make AI and external API integrations much cleaner and safer
than current workarounds (i.e. separate long responses from agent in several input text or using files...
Just sharing feedback from a real-world use case.
Why the uncertainty?
i don't know if this could be a core feature or an add on.
Use cases
i use an api to get answer from a local AI on my server, and i have to deal with a long string (> 255 char) to expose the answer in a dashboard. i tried via sensor attribute, input text files but all the solutions were not working or really non user friendly.
I describe my struggles here : https://discordapp.com/channels/330944238910963714/1456605148921991342
to exploit an AI exploited via API easily we shouls have a way to handle the result of a rest_command properly directly in HA. having this buffer thing (new entity type?) would really ease the way to do it.
What areas might this affect?
maybe tools and services,
,
,

a new type of entry
with those parameters :
eventualy dashboard (a new card type?)
(this card is the result of my efforts (be gentle :) ), all informations are the results of a prompt with HA sensor values, interrogating an API (served by a python script handling the AI part)
Anything else?
at first, Jorg told me about intégration files which coud do that. but i thing that creating a file is not the proper way to handle variables in HA.
Beta Was this translation helpful? Give feedback.
All reactions