Source: https://github.com/home-assistant/architecture/discussions
- Total Open Discussions: 144
- Entity Models: 109 (76%)
- General: 33 (23%)
- Documentation: 2 (1%)
Source: https://github.com/home-assistant/architecture/discussions
I have an ask for the AI community: can someone create a standard for interacting with LLMs.
There is a whole category of new apps and features ready to be made on top of LLMs. But to get these in the hands of users is hard. Apps will need to have subscriptions, ask the user to add their OpenAI API key or include and ship their own LLMs. It’s time to add a fourth option: create a standardized API that allows interacting with LLMs that cloud and local services can implement to put the user in control.
There are new LLM models and tuned variations popping up all the time, and most of these models end up implementing some part of the Chat Completions endpoint of the OpenAI Rest API. The recommendation is for users to use the OpenAI SDK and override the endpoint (even Google is doing this now!). The OpenAI API is tailored to the needs of OpenAI, which means it’s set up to interact with their cloud-based LLM mode
/* | |
Copy file to <config>/www/user-agent-card.js | |
Restart Home Assitant if www folder didn't exist. | |
In Home Assistant: | |
- Profile -> Enable advanced mode | |
- Config -> Dashboards -> Resources | |
- New resource. `/local/user-agent-card.js`. Type: JS Module |
/* | |
Battery strategy that shows your battery entities grouped by area. | |
To use: | |
- store this file in `<config>/www/balloob-battery-strategy.js` | |
- Add lovelace resource: `/local/balloob-battery-strategy.js`, type JavaScript Module | |
- Create a new Lovelace dashboard and set as content: | |
views: | |
- title: Batteries |
/* | |
Demo strategy that shows each area as a tab. Each tab shows the area entities. | |
To use: | |
- store this file in `<config>/www/demo-strategy.js` | |
- Add lovelace resource: `/local/demo-strategy.js`, type JavaScript Module | |
- Create a new Lovelace dashboard and set as content: | |
strategy: | |
name: 'custom:balloob-demo' |
/* | |
To use in Home Assistant, configure card: | |
type: 'custom:example-card' | |
entities: | |
- switch.wemo_insight | |
- light.bed_light | |
- light.ceiling_lights | |
- light.kitchen_lights |
/* | |
Created by @jh3yy | |
Adapted for Home Assistant by @balloob | |
Original: https://twitter.com/jh3yy/status/1327686213432717313 | |
Only works on localhost because of restrictions MorphSVGPlugin3 | |
Card config for usage in Home Assistant: |
/* | |
Example panel. | |
Put this file in <config>/www/example-panel.js | |
In configuration.yaml: | |
panel_custom: | |
- name: example-panel | |
# url_path needs to be unique for each panel_custom config |
diff --git a/src/layouts/home-assistant.ts b/src/layouts/home-assistant.ts | |
index 0dae29df..663d152f 100644 | |
--- a/src/layouts/home-assistant.ts | |
+++ b/src/layouts/home-assistant.ts | |
@@ -150,6 +150,7 @@ export class HomeAssistantAppEl extends HassElement { | |
protected _handleVisibilityChange() { | |
if (document.hidden) { | |
+ console.log("home-assistant handle tab hidden"); | |
// If the document is hidden, we will prevent reconnects until we are visible again |
/* | |
Add a link to the sidebar to any path in Home Assistant | |
Put this file in <config>/www/panel-redirect.js | |
In configuration.yaml: | |
panel_custom: | |
- name: panel-redirect | |
# url_path needs to be unique for each panel_custom config |