| 4 May 2025 |
 hexa | yeah, maybe I should nuke my .platformio cache | 20:39:38 |
| hexa | can try later | 20:39:40 |
| 5 May 2025 |
|  @mur1chan:sakura.pm joined the room. | 00:57:35 |
| @mur1chan:sakura.pm left the room. | 00:59:08 |
| hexa | https://github.com/skylord123/pebble-home-assistant-ws | 18:02:17 |
|  @knoopx:matrix.org left the room. | 22:27:05 |
| 6 May 2025 |
| hexa | wiped the ~/.platformio cache and still builds fine | 03:51:43 |
| hexa | esphome:
name: test
esp8266:
board: d1_mini
# Enable logging
logger:
# Enable Home Assistant API
api:
password: "test"
ota:
- platform: esphome
password: "test"
wifi:
ssid: "test"
password: "testtest"
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Test Fallback Hotspot"
password: "M2KOWG36fKq5"
captive_portal:
⏎
| 03:52:10 |
| hexa | the same for an esp32-c3 board | 04:06:57 |
| hexa | esphome:
name: test2
esp32:
board: esp32-c3-devkitm-1
framework:
type: arduino
# Enable logging
logger:
# Enable Home Assistant API
api:
password: "test"
ota:
- platform: esphome
password: "test"
wifi:
ssid: "test"
password: "testtest"
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: " Fallback Hotspot"
password: "Ol9AvdeMyTd1"
captive_portal:
| 04:07:01 |
| hexa | * esphome:
name: test2
esp32:
board: esp32-c3-devkitm-1
framework:
type: arduino
# Enable logging
logger:
# Enable Home Assistant API
api:
password: "test"
ota:
- platform: esphome
password: "test"
wifi:
ssid: "test"
password: "testtest"
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: " Fallback Hotspot"
password: "Ol9AvdeMyTd1"
captive_portal:
| 04:07:05 |
 dotlambda | Weird. I nuked my .platformio again and now it also works for me 🤷 | 10:18:28 |
| dotlambda | * Weird. I nuked my
`.platformio` again and the error persists | 10:19:07 |
| dotlambda | I'll try it on a different machine next | 10:19:28 |
 kranzes | is anyone using duckdb? how does it compare to postgresql? | 15:11:45 |
| hexa | how does that relate to home automation? | 15:13:18 |
| kranzes | I saw people using duckdb for home assistant | 16:17:41 |
| kranzes | instead of postgresql or whatever other databases | 16:17:59 |
 K900 | Uhh what | 16:34:49 |
| K900 | I don't think it supports that | 16:35:11 |
| hexa | home-assistant relies on sqlalchemy | 16:36:11 |
| hexa | so in theory you can connect everything that it supports? | 16:36:41 |
| hexa | https://github.com/Mause/duckdb_engine | 16:37:00 |
| hexa | so maybe providing this dependency and configuring the correct dsn will just work | 16:37:18 |
 ethan | At that point I'd just use sqlite, not sure what benefit duckdb would give you in this space... | 16:51:27 |
| kranzes | noob question: why do we explictly disable proxy_buffering in the nginx config on the wiki? | 17:11:31 |
| kranzes | Is there a way to skip the entire onboarding process? | 18:53:32 |
| kranzes | and not import any of the default_config stuff, it's spamming me with google translate errors | 18:53:48 |
| kranzes | I have this config right now:
services.home-assistant = {
enable = true;
extraPackages = ps: with ps; [ psycopg2 ];
extraComponents = [
"isal"
"esphome"
];
customComponents = with pkgs.home-assistant-custom-components; [
auth_oidc
];
config = {
http = {
server_host = "127.0.0.1";
trusted_proxies = [ hassCfg.http.server_host ];
use_x_forwarded_for = true;
};
recorder.db_url = "postgresql://@/hass";
auth_oidc = {
client_id = "home-assistant";
discovery_url = "https://idm.ilanjoselevich.com/oauth2/openid/home-assistant/.well-known/openid-configuration";;
client_secret = "!secret auth_oidc_client_secret";
id_token_signing_alg = "ES256";
roles.admin = "home-assistant_admins@idm.ilanjoselevich.com";
};
};
};
| 18:54:18 |
| hexa | onboarding not that I know | 19:07:29 |
