| 28 Jan 2025 |
 @qbit:tapenet.org | ya, logs show it using the wrong address for the tts response | 15:07:56 |
 @hexa:lossy.network | settings > system > network | 15:09:06 |
| @hexa:lossy.network | does your home-assistant discover the correct ip address? | 15:09:14 |
| @qbit:tapenet.org | it's correct, but the port seems closed, despite having the fw open | 15:13:09 |
| @qbit:tapenet.org | tcp 0 0 127.0.0.1:8123 0.0.0.0:* LISTEN 2184/python3.13 | 15:13:52 |
| @qbit:tapenet.org | nixos-fw-accept tcp -- anywhere anywhere tcp dpt:8123 | 15:13:53 |
| @qbit:tapenet.org | anyway - thanks for all the help, i'll try beating my head against it some more :D | 15:14:15 |
| @hexa:lossy.network | can you dump your firewall rules? | 15:15:08 |
| @hexa:lossy.network | nft list ruleset | 15:15:21 |
| @qbit:tapenet.org | it's iptables, but ya: http://okturing.com/src/22945/body | 15:16:24 |
| @hexa:lossy.network | everything passes through the tailscale tables first 🫣 | 15:17:51 |
| @qbit:tapenet.org | root@box[0]:~# nixos-firewall-tool open tcp 8125
ip6tables v1.8.11 (nf_tables): Chain 'nixos-fw-accept' does not exist
Try `ip6tables -h' or 'ip6tables --help' for more information.
root@box[2]:~#
that doesn't seem right..
| 15:23:02 |
| * @qbit:tapenet.org throws all the computers into the trash | 15:23:50 |
| @qbit:tapenet.org | i don't think it's tailscale, i can poke a hole in the fw and stand up nc (nc -l 8125 and connect fine externally | 15:33:11 |
 laurynasp | I use tailscale too, but I started with local ips to reduce moving parts
I.e. I added voice-pe using esphome integration from ha UI using 192.xxx ip address, which I took from fresh avahi-browse output. Not sure i that's of any help.
| 15:37:01 |
| @qbit:tapenet.org | ah, i think it's because I had config.http.server_host set to 127.0.0.1, added the 10. ip | 15:39:31 |
| @qbit:tapenet.org | firewalls.. all the way down.. | 15:39:42 |
| laurynasp | I am not sure what your set up is exactly, I run ha on raspberry pi, and then I have voice-pe. I did run tts (piper) on the same pi as ha, so that simplifies issues with firewall for PoC config. | 15:39:45 |
| @qbit:tapenet.org | aww yis, that was it | 15:41:50 |
| 29 Jan 2025 |
 dotlambda | Is there an established way to add blueprints from the NixOS config? | 00:00:35 |
| @hexa:lossy.network | hm, apparently we could just drop them into /var/lib/hass/{automation,script/{owner}/{name}.yaml | 00:04:20 |
| dotlambda | I guess I should rather use Nix functions to create similar automations but I want my family to be able to use the blueprint | 00:04:21 |
| dotlambda | In reply to @hexa:lossy.network
hm, apparently we could just drop them into /var/lib/hass/{automation,script/{owner}/{name}.yaml You're missing blueprint, and owner isn't actually required afaict | 00:05:00 |
| @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 |
