| 28 Jan 2025 |
 @qbit:tapenet.org | has anyone managed to overlay esphome? | 00:26:23 |
| @qbit:tapenet.org | got the preview edition of hte home assistant voice device | 00:26:41 |
 @hexa:lossy.network | overridePythonAttrs | 00:27:01 |
| @qbit:tapenet.org | but it want's the latest esphome that 374675 added | 00:27:02 |
| @hexa:lossy.network | 374675? | 00:27:14 |
| @hexa:lossy.network | oh, pr | 00:27:40 |
| @qbit:tapenet.org | pr you made | 00:27:41 |
| @hexa:lossy.network | same as home-assistant then | 00:27:49 |
| @qbit:tapenet.org | (_: super: {
esphome = super.esphome.overridePythonAttrs (oldAttrs: rec {
version = "2024.12.4";
src = super.fetchFromGitHub {
owner = "esphome";
repo = "esphome";
tag = version;
hash = "sha256-Ff3NuLHKRLoBbjqb92vvDcSbSJnjCwm5FmSDwnEI0p4=";
};
});
});
| 00:27:48 |
| @hexa:lossy.network | just reference the package from the unstable channel | 00:28:03 |
| @qbit:tapenet.org | is what I have, and it seems to build .. except the service doesn't snag it | 00:28:10 |
| @hexa:lossy.network | sigh | 00:28:19 |
| @hexa:lossy.network | I don't maintain the service, but let me look what it does | 00:28:25 |
| @hexa:lossy.network | it consumes pkgs.esphome, so overlaying it should work | 00:28:57 |
| @qbit:tapenet.org | hm | 00:30:36 |
| @qbit:tapenet.org | wesphome --version shows the expected version | 00:32:53 |
| @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 |
| @qbit:tapenet.org | And the m5stack epaper thing.. Which has potential for something neat | 12:23:47 |
| laurynasp | I see - I've just checked out m5stack - that's intriguing
| 12:39:25 |
| laurynasp | how esphome and Voice PE relate in your setup? are you connecting Vocie PE to esp32 bluetooth gateway? or you using esphome to fiddle with Voice PE firmware?
P.s. I got my Voice PE last week, and I've been playing with it too. I have had it connected directly to hass via esphome integration, but I would be keen to find a more automated way to configure it | 12:42:39 |
