| 29 Jan 2025 |
 @hexa:lossy.network | * hm, apparently we could just drop them into /var/lib/hass/blueprint/{automation,script/{owner}/{name}.yaml | 00:05:45 |
| @hexa:lossy.network | blueprints/automation/
blueprints/automation/bnapalm/
blueprints/automation/homeassistant/
blueprints/automation/homeassistant/motion_light.yaml
blueprints/automation/homeassistant/notify_leaving_zone.yaml
blueprints/automation/mweinelt/
blueprints/automation/mweinelt/danfoss_trv_ext_temp_z2m.yaml
blueprints/automation/sbyx/
blueprints/automation/sbyx/low-battery-level-detection-notification-for-all-battery-sensors.yaml
blueprints/automation/sbyx/notify-or-do-something-when-an-appliance-like-a-dishwasher-or-washing-machine-finishes.yaml
blueprints/script/
blueprints/script/homeassistant/
blueprints/script/homeassistant/confirmable_notification.yaml
| 00:05:48 |
| @hexa:lossy.network | this is out it looks for me | 00:05:51 |
| @hexa:lossy.network | * this is how it looks for me | 00:07:41 |
 dotlambda | Should I add a blueprints option to the NixOS module or just let people use tmpfiles manually? | 00:11:06 |
| @hexa:lossy.network | tmpfiles is an ugly interface | 00:13:05 |
| @hexa:lossy.network | it deserves to be wrapped | 00:13:20 |
| dotlambda | Do we want to let people write blueprints in Nix? Or do they have to provide a path to a YAML file? | 00:21:31 |
| @hexa:lossy.network | people are probably going to want to consume blueprints most, no? | 00:24:33 |
| dotlambda | I would definitely give the option to do both | 00:30:09 |
|  colonelpanic joined the room. | 03:23:08 |
| colonelpanic | I've gotten pretty far with setting up matter/thread with homeassitant by using the open thread border router setup that is currently still a pr (https://github.com/NixOS/nixpkgs/pull/332296). For a long time, I was running into this very annoying issue (https://github.com/home-assistant/android/issues/4146), but the recommendations there ended up solving the problem. However, I'm now running in to a new issue where adding the device fails on my android device with "Can't reach device: Make sure your phone is connected to Wi-Fi". Has anyone else seen this issue? Has anyone here had success with a matter/thread setup using the nixos home assistant module? | 03:27:21 |
| colonelpanic | I guess it seems like spacekitteh is the one who has been working on this PR? Have you been able to actually pair a matter/thread device? | 03:31:48 |
 spacekitteh | sorry i'll have a look this evening | 03:32:03 |
| colonelpanic | are you aware that mrene had already set up a nixos module here https://github.com/NixOS/nixpkgs/pull/332296 | 03:33:43 |
| colonelpanic | Another possibly relevant detail is that I can never view the topology page in the web interface for the border router | 03:37:46 |
| colonelpanic | Also wonder if this warning message in the otbr agent could be relevant: "00:07:33.117 [W] Nat64---------: no mapping found for the IPv4 addres" | 03:45:55 |
| dotlambda | I've decided against blueprints written in Nix for now: https://github.com/NixOS/nixpkgs/pull/377688 | 04:07:16 |
 kdn | After playing with Tuya for a while I want to get started with Home Assistant: got myself HA dongle and a few zigbee-enabled devices.
Would you suggest running HA through NixOS or flash RPi4 4GB with their OS? | 13:11:27 |
| kdn | personally I'm more comfortable managing NixOS than whatever distro would be there | 13:11:56 |
 laurynasp | I guess you are asking for a cons vs pros between the two approaches - I am too new to provide such info
| 13:57:43 |
| laurynasp | What i can share is that my aim is to have as automated setup as i can, hence I am using nixos to run ha in declarative way, and for that reason i picked raspbery pi 4B because it is most compatible. (I am using 8GB rather than 4GB but that is an orthoganal matter).
However, for my journal of automated/scripted/decalrative setup of ha, I have been rather disappoitned, because I was not able to find an easy way to automated onboarding, but that is home-assitant's issue, not nixos modules issue. Still, ha module on nixos on pi 4B is the best i was able discover so far.
| 13:57:58 |
| laurynasp | * What i can share is that my aim is to have as automated setup as i can, hence I am using nixos to run ha in declarative way, and for that reason i picked raspbery pi 4B because it is most compatible with nixos. (I am using 8GB rather than 4GB but that is an orthoganal matter).
However, for my journal of automated/scripted/decalrative setup of ha, I have been rather disappoitned, because I was not able to find an easy way to automated onboarding, but that is home-assitant's issue, not nixos modules issue. Still, ha module on nixos on pi 4B is the best i was able discover so far.
| 13:58:28 |
| laurynasp | * What i can share is that my aim is to have as automated setup as i can, hence I am using nixos to run ha in declarative way, and for that reason i picked raspbery pi 4B because it is most compatible with nixos. (I am using 8GB rather than 4GB but that is an orthoganal matter).
However, for my aim of automated/scripted/declarative setup of ha, I have been rather disappoitned, because I was not able to find an easy way to automated onboarding, but that is home-assitant's issue, not nixos modules issue. Still, ha module on nixos on pi 4B is the best i was able discover so far.
| 13:58:49 |
| @hexa:lossy.network | 4 vs 8 GB does matter, if you want the rpi to evaluate and rebuild itself | 14:00:23 |
| laurynasp | * What i can share is that my aim is to have as automated setup as i can, hence I am using nixos to run ha in declarative way, and for that reason i picked raspbery pi 4B because it is most compatible with nixos. (I am using 8GB rather than 4GB but that is an orthoganal matter).
However, for my aim of automated/scripted/declarative setup of ha, I have been rather disappoitned, because I was not able to find an easy way to automated onboarding, but that is home-assitant's issue, not nixos modules issue. Still, ha module on nixos on pi 4B is the best i was able discover so far.
My guess is that most ppl workaround to "redeployment" of the configs state is via restoring backups
| 14:00:25 |
| @hexa:lossy.network | * 4 vs 8 GB does matter, if you want the rpi to evaluate and rebuild itself … aka do automatic upgrades | 14:00:42 |
| laurynasp | Good point! Hexa, if deploymetns are build remotely, i.e.g by running nixos-rebuild --target-host user@$NIXOS_INSTALL_TARGET_IP switch --flake .#ha-rpi --use-remote-sudo on my main machine, would 4GB still be an issue? | 14:03:08 |
| @hexa:lossy.network | probably not | 14:03:26 |
| @hexa:lossy.network | but remember that you need an arm64 builder for that, or do cross builds exclusively | 14:03:46 |
