| 24 Aug 2021 |
 @hexa:lossy.network | setting package like you are doing it probably means you run the tests when deploying? | 12:34:15 |
| @hexa:lossy.network | see https://github.com/NixOS/nixpkgs/blob/df2f45b347d57bdc99aaa96ee227a37f5201c9dc/nixos/modules/services/misc/home-assistant.nix#L187-L209 | 12:35:01 |
 Church | Yeah was out and about, ssh from the phone is annoying. :P | 12:40:15 |
| Church | Let me go see what it actually is in a few | 12:40:25 |
| Church | Yep owners are root:dialout | 12:54:18 |
| Church | Tried with my HUBUSB stick and chown'ing to hass:hass worked | 12:54:34 |
| @hexa:lossy.network | that is one solution, though I wouldn't expect this to be necessary with https://github.com/NixOS/nixpkgs/pull/135540 | 12:57:02 |
| @hexa:lossy.network | it puts your hass into the dialout group already | 12:57:12 |
| 1 Sep 2021 |
| @hexa:lossy.network | thinking about how to handle the hass update with the python-unstable branch in mind | 18:37:00 |
| @hexa:lossy.network | there is a certain overlap, but python-unstable goes through staging | 18:37:18 |
| @hexa:lossy.network | basing on staging, due to the large overlap of updated packages | 20:00:08 |
| @hexa:lossy.network | means it will likely be delayed 10-14 days | 20:00:19 |
| 3 Sep 2021 |
 iclanzan | Where could I store assets such as images for use in HA’s UI (picture-glance) and how would I reference them? Been trying allowlist_external_dirs without success. | 21:54:23 |
 Zhaofeng Li | Never used picture glance, but something like "${./path/to/some.jpg}" should work | 22:33:26 |
| iclanzan | It doesn't unfortunately because the lovelace html can't just reference arbitrary stuff from the nix store | 22:37:13 |
| @hexa:lossy.network | add another location block to your reverse proxy that points whereever | 22:52:41 |
| 4 Sep 2021 |
| iclanzan | Thant worked, thank you for the idea! | 00:56:33 |
| iclanzan | * That worked, thank you for the idea! | 00:56:38 |
| 7 Sep 2021 |
 CRTified | Is it me or is aioesphomeapi broken on unstable?
2021-09-07 22:14:48 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform esphome.light: Platform not found (cannot import name 'LightColorMode' from 'aioesphomeapi' (/nix/store/yw40d736xvv7criyfffz88pcfnvvavx0-python3.9-aioesphomeapi-8.0.0/lib/python3.9/site-packages/aioesphomeapi/__init__.py)).
| 20:18:30 |
| @hexa:lossy.network | it is | 20:35:30 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/135669#issuecomment-912177954 | 20:35:50 |
| CRTified | Thanks, the github search works "flawless" when searching for aioesphomeapi... | 20:36:29 |
| @hexa:lossy.network | In reply to @hexa:lossy.network
thinking about how to handle the hass update with the python-unstable branch in mind this relates to home-assistant update being delayed due to ^ | 20:36:36 |
| @hexa:lossy.network | python-unstable is currently in staging-next | 20:36:55 |
| @hexa:lossy.network | I'd have to duplicate alot of updates that are currnetly in there to get home-assistant updated | 20:37:10 |
| @hexa:lossy.network | if you can, please submit an override to home-assistant | 20:37:20 |
| CRTified | In reply to @hexa:lossy.network
if you can, please submit an override to home-assistant Something like this? It fixed it for me at least
pkgs.home-assistant.override {
packageOverrides = self: super: {
aioesphomeapi = super.aioesphomeapi.overrideAttrs (o: rec {
version = "7.0.0";
src = pkgs.fetchFromGitHub {
owner = "esphome";
repo = o.pname;
rev = "v${version}";
hash = "sha256-ho/1fpq4yAgmYNERPqs51oqr08ncaN9+GRTUUuGU7ps=";
};
});
};
}
| 20:55:53 |
| @hexa:lossy.network | Yep and now integrate it into pkgs/server/home-assistant/default.nix and open a pull request 😊 | 20:57:32 |
| CRTified | In reply to @hexa:lossy.network
Yep and now integrate it into pkgs/server/home-assistant/default.nix and open a pull request 😊 https://github.com/NixOS/nixpkgs/pull/137030 | 21:09:08 |
| 15 Sep 2021 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/138025 | 16:12:14 |
