4 May 2025 |
@hexa:lossy.network | esphome dashboard --open-ui . | 13:30:46 |
@hexa:lossy.network | esphome run device.yaml | 13:31:17 |
dotlambda | In reply to @hexa:lossy.network esphome dashboard --open-ui . But that still uses platformio under the hood. And you don't run into problems? | 13:32:25 |
@hexa:lossy.network | I have never seen that error | 13:32:40 |
@hexa:lossy.network | might be related to what esphome components you use though | 13:32:52 |
dotlambda | I guess I should try a more basic YAML file first | 13:33:55 |
dotlambda | I tried the default YAML file that is created for a new ESP8266 and got the same error message | 13:45:33 |
@hexa:lossy.network | huh | 13:47:16 |
@hexa:lossy.network | I let it create an esp8266 from the wizard and that compiled just fine with esphome 2025.4.0 | 13:49:33 |
@hexa:lossy.network | can you give me something to repro? | 13:49:43 |
dotlambda | In reply to @hexa:lossy.network I let it create an esp8266 from the wizard and that compiled just fine with esphome 2025.4.0 That would have been exactly my instructions for reproducing | 20:14:21 |
dotlambda | I can send you the YAML but I don't think that matters much | 20:14:37 |
dotlambda | Maybe it only appears with a fresh install of esphome or at least a fresh download of the platformio compilers | 20:15:14 |
@hexa:lossy.network | yeah, maybe I should nuke my .platformio cache | 20:39:38 |
@hexa:lossy.network | 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:lossy.network | https://github.com/skylord123/pebble-home-assistant-ws | 18:02:17 |
| @knoopx:matrix.org left the room. | 22:27:05 |
6 May 2025 |
@hexa:lossy.network | wiped the ~/.platformio cache and still builds fine | 03:51:43 |
@hexa:lossy.network | 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:lossy.network | the same for an esp32-c3 board | 04:06:57 |
@hexa:lossy.network | 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:lossy.network | * 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:matrix.org | is anyone using duckdb? how does it compare to postgresql? | 15:11:45 |
@hexa:lossy.network | how does that relate to home automation? | 15:13:18 |
@kranzes:matrix.org | I saw people using duckdb for home assistant | 16:17:41 |