| 20 Jan 2025 |
spacekitteh | I'll try to have a look at it this evening | 02:34:36 |
ibizaman | What prompted you to add auth_oidc to home-assistant? Just for the sake of it or do you have plans of integrating oauth into the NixOS module? I'm curious because I planned to get to it (in the future, someday). | 22:24:20 |
ibizaman | * What prompted you to add auth_oidc to nixpkgs? Just for the sake of it or do you have plans of integrating oauth into the NixOS module? I'm curious because I planned to get to it (in the future, someday). | 22:24:31 |
@hexa:lossy.network | maybe I want to play with it | 22:26:31 |
| 22 Jan 2025 |
Ekleog | This is interesting; I'm hitting the same issue that custom components seem not to be loaded; but I don't actually have the fourth "manage resources" line when clicking this button (assuming it's in the top-right corner when editing the dashboard).
Did something change with 2025.01.2? | 02:21:40 |
| 21 Jan 2025 |
| oak 🏳️🌈♥️ changed their profile picture. | 22:36:02 |
| 22 Jan 2025 |
@hexa:lossy.network | @leo:gaspard.ninjaWhat is your Lovelace config in nix? | 07:04:02 |
| 21 Jan 2025 |
| oak 🏳️🌈♥️ changed their profile picture. | 22:37:29 |
| 22 Jan 2025 |
K900 | Works fine here FWIW | 07:06:23 |
K900 | The custom components that is | 07:06:27 |
K900 | At least on mobile though I really don't think it should matter | 07:07:04 |
uep | staging merge blew up whisper | 10:33:32 |
uep | trace: evaluation warning: getExe: Package "wyoming-faster-whisper-2.4.0" does not have the meta.mainProgram attribute. We'll assume that the main program has the same name for now, but this behavior is deprecated, because it leads to surprising errors when the assumption does not hold. If the package has a main program, please set `meta.mainProgram` in its definition to make this warning go away. Otherwise, if the package does not have a main program, or if you don't control its definition, use getExe' to specify the name to the program, such as lib.getExe' foo "bar".
error:
… while calling the 'head' builtin
at /nix/store/irknf7niks2djxz4csh7sr44wwrs082y-source/lib/attrsets.nix:1574:11:
1573| || pred here (elemAt values 1) (head values) then
1574| head values
| ^
1575| else
… while evaluating the attribute 'value'
at /nix/store/irknf7niks2djxz4csh7sr44wwrs082y-source/lib/modules.nix:846:9:
845| in warnDeprecation opt //
846| { value = addErrorContext "while evaluating the option `${showOption loc}':" value;
| ^
847| inherit (res.defsFinal') highestPrio;
(stack trace truncated; use '--show-trace' to show the full trace)
error: expected a list but found the partially applied built-in function 'concatMap': «partially applied primop concatMap»
| 10:34:14 |
@hexa:lossy.network | hrm | 11:42:21 |
@hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/375798 | 11:44:37 |
@hexa:lossy.network | morel likely to be a regression from the module changes I did recently | 11:45:01 |
Ekleog | Actually a friend explained to me that I needed to set a lovelace config from nix, and custom lovelace components don't work with the graphical UI setup. So now I have fixed it, thank you for your answer!
Out of curiosity, is there anyone using Valetudo with Home-Assistant here? I have the custom valetudo map card working fine on my android app, but the same card on my firefox shows everything but the actual map. Did this happen to anyone else? It does show up fine on Chromium | 17:14:14 |
@hexa:lossy.network | setting customLovelaceModules installs these in /var/lib/hass/www/nixos-lovelace-modules/ | 17:15:29 |
K900 | Works fine here | 17:15:32 |
@hexa:lossy.network | when the storage mode is yaml, aka nix controlled, we can automatically inject the .js entrypoints into that yaml lovelace config | 17:16:06 |
@hexa:lossy.network | if you want to edit it from the frontend then home-assistant will manage storing all that information and you'll have to add the resources yourself | 17:16:45 |
@hexa:lossy.network | if you want the latter, set lovelaceConfig = null | 17:17:14 |
Ekleog | Thank you for all your answers! It's pretty weird, but it seems that restarting firefox fixed the issue… weird 🤷
Thank you! :D | 17:22:40 |
@hexa:lossy.network | ok lol | 17:23:43 |
@hexa:lossy.network | sounds like a caching issue then | 17:23:48 |
| 24 Jan 2025 |
laurynasp | My Voice PE has just arrived, but I am having a bit of a trouble with step 7. I do not want to use cloud, and setup instructions say to use whisper and piper add-ons, which is where I get confused..
It seems that add-ons are availalabe only for HAOS and supervised, but on NixOS we have HA-core, is that correct?
I found Whisper integration, but I struggle to understand what it is for, and it page for it seems to refer to Wyoming protocol integration..
| 08:15:28 |
laurynasp | So I thought to check if anyone has their setup available to share or knows a blog post, before I start experimenting with those integrations | 08:15:53 |
uep | services.home-assistant = {
# ...
extraComponents = [
# ...
# voice assistant
"piper"
"whisper"
"wake_word"
"wyoming"
];
};
};
services.wyoming = {
faster-whisper.servers.whisper = {
enable = true;
uri = "tcp://127.0.0.1:10300";
device = "cpu";
language = "en";
model = "medium-int8";
};
openwakeword = {
enable = true;
uri = "tcp://127.0.0.1:10400";
};
piper.servers.piper = {
enable = true;
uri = "tcp://127.0.0.1:10200";
voice = "en_GB-semaine-medium";
};
};
| 10:57:38 |
uep | then you add those three ports via the wyoming integration in the HA UI | 10:58:48 |
uep | and you add the voice device via the esphome integration, which was where i got well confused | 10:59:50 |