| 28 Jan 2025 |
 @qbit:tapenet.org | oh.. my god.. lol | 00:33:39 |
| @qbit:tapenet.org | bitten by the tailnet.. | 00:33:49 |
| @qbit:tapenet.org | i don't know where anything runs on my network anymore \o/ | 00:33:55 |
| @qbit:tapenet.org | thanks for the clue sticks! | 00:39:01 |
 @hexa:lossy.network | yw | 00:39:44 |
 laurynasp | qbit: out of curiosity, what do you use "services.esphome" for? | 12:11:18 |
| laurynasp | I am asking because I used it, but found it impractical for my use case, which was automating setup/updates of my esp32 devices, This was mostly because (i) nixos service does not have many options exposed (e.g. preExec systemd services) and (ii) esphome itself does not like symlinks. Both things together made it difficult to use "auto-generated" config files for my devices
| 12:11:28 |
| laurynasp | hexa pointed me towards flake/nix shell to run esphome, which seems to be better alternative for me, although I haven't finalised that workflow yet.
| 12:11:41 |
| laurynasp | I am asking in case you found a smooth way to declaratively configure (esp32) devices using the service? or check what advantages you have discovered service vs on-demand launch from nix shell? | 12:12:40 |
| @qbit:tapenet.org | I am not using it declaratively, mostly just playing around with a few of the voice things for home assistant | 12:22:45 |
| @qbit:tapenet.org | M5stack and the new preview thing | 12:23:01 |
