| 8 Jan 2025 |
 laurynasp | just doing a test run to check that ESPhome is happy with secrets.yaml being outside the config dir | 02:16:33 |
 @hexa:lossy.network | good luck 😄 | 02:18:18 |
| @hexa:lossy.network | if not you could probably file an issue upstream or submit a patch | 02:18:31 |
| laurynasp | Did you say you run dashboard from dev shell? is you config for that public?
P.s. I ended up using esphome service, because it worked, and I was not able to find any easy / detailed tutorial on how to flash esp32 devices.
The simplest alternative i found (but haven't tested) on https://nixos.wiki/wiki/ESP-IDF is
nix --experimental-features 'nix-command flakes' develop github:mirrexagon/nixpkgs-esp-dev#esp32-idf
Is your set up similar?
| 02:21:42 |
| laurynasp | * Did you say you run dashboard from dev shell? is your config for that public?
P.s. I ended up using esphome service, because it worked, and I was not able to find any other easy / detailed tutorial on how to flash esp32 devices on nixos / nix.
The simplest alternative i found (but haven't tested) on https://nixos.wiki/wiki/ESP-IDF is
nix --experimental-features 'nix-command flakes' develop github:mirrexagon/nixpkgs-esp-dev#esp32-idf
Is your set up similar?
| 02:22:57 |
| @hexa:lossy.network | no, there is plain secrets in there ;D | 02:23:23 |
| @hexa:lossy.network | * no, there is plain secrets in there 😄 | 02:23:24 |
| @hexa:lossy.network | although only for my iot wlan | 02:23:37 |
| @hexa:lossy.network | which probably isn't much use | 02:23:42 |
| @hexa:lossy.network | esphome is the most declarative and simple way to maintain a bunch of esp8266/32 devices | 02:24:25 |
| @hexa:lossy.network | ESP-IDF is the framework by espressif | 02:24:40 |
| @hexa:lossy.network | you'll need to be somewhat fluent in C with that | 02:25:09 |
| laurynasp | I am glad you saved me from a rabbit hole! | 02:25:15 |
| @hexa:lossy.network | https://git.darmstadt.ccc.de/cda/co2-sensor-workshop/-/blob/main/flake.nix?ref_type=heads | 02:26:04 |
| @hexa:lossy.network | this is a flake for an esphome project | 02:26:11 |
| @hexa:lossy.network | if that helps | 02:26:23 |
| laurynasp | Thanks - I will try it out tomorrow | 02:28:46 |
| @hexa:lossy.network | cuda cache? https://nix-community.org/cache/ | 14:08:27 |
 @qbit:tapenet.org | isn't there a buildPythonPackage like thing that's exposed from in buildHomeASsistantComponent (or some other HA .. entry point..)? | 20:53:55 |
| @qbit:tapenet.org | getting: ```
The Python derivation 'python3.13-firstof9/openevse-2.1.45' depends on a Python derivation
named 'python3.12-python-openevse-http-0.1.61', but the two derivations use different versions
of Python:
'python3.13-firstof9/openevse-2.1.45' uses /nix/store/acxvfb890g9jawlxsj7zs8marxxvzrrs-python3-3.13.1
'python3.12-python-openevse-http-0.1.61' uses /nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8
| 20:54:23 |
| @qbit:tapenet.org | * getting:
The Python derivation 'python3.13-firstof9/openevse-2.1.45' depends on a Python derivation
named 'python3.12-python-openevse-http-0.1.61', but the two derivations use different versions
of Python:
'python3.13-firstof9/openevse-2.1.45' uses /nix/store/acxvfb890g9jawlxsj7zs8marxxvzrrs-python3-3.13.1
'python3.12-python-openevse-http-0.1.61' uses /nix/store/c9m6yd8fg1flz2j5r4bif1ib5j20a0cy-python3-3.12.8
| 20:54:35 |
| @hexa:lossy.network | heh | 20:54:57 |
| @hexa:lossy.network | is that something you have downstream? | 20:55:27 |
| @hexa:lossy.network | use home-assistant.python | 20:55:39 |
| @qbit:tapenet.org | ya: https://github.com/qbit/xin/blob/main/pkgs/openevse.nix | 20:55:45 |
| @qbit:tapenet.org | swoot, ty | 20:59:52 |
| @qbit:tapenet.org | Jan 08 14:05:05 pwntie xin-ci-start[1947828]: error: future-1.0.0 not supported for interpreter python3.13 | 21:06:06 |
| * @qbit:tapenet.org cries python tears | 21:06:11 |
| @hexa:lossy.network | it is not 😄 | 21:07:09 |
| @hexa:lossy.network | man | 21:07:12 |
