| 28 Jan 2025 |
 laurynasp | I had very similar symptom - it got fixed once voice-PE had a correctly configured access to tts service | 14:25:07 |
| laurynasp | for me that voice under Settings -> Voice assitnt -> tts, annd voice-PE had access to it | 14:25:41 |
| laurynasp | * for me that was under Settings -> Voice assitnt -> tts, annd voice-PE had access to it | 14:25:54 |
 @qbit:tapenet.org | i'll check that, did a factory reset (kinda fun :D) | 14:26:58 |
| laurynasp | * for me that was under Settings -> Voice assistants -> tts, annd voice-PE had access to it | 14:27:16 |
| @qbit:tapenet.org | bah, yeeted, but now I can't seem to re-add it | 14:37:18 |
| laurynasp | can you see if ip address is still the same of voice-pe (e.g. via avahi-browse ) | 14:39:28 |
| laurynasp | i.e. when I was resetting my voice-pe, i was caught out because once i forgot to remove it from from home-assitant (so obviously I wasn't able to add as it had been added already), on another occasion I was using wrong ip address | 14:45:39 |
| @qbit:tapenet.org | i did remove it from HA, it popped up for a second but errored with a json blob module error (didn't screen shot it unfortunately) | 14:48:12 |
| @qbit:tapenet.org | now it doesn't show up at all | 14:48:14 |
| @qbit:tapenet.org | since it was a factory reset, i assume it lost my wifi info | 14:48:29 |
 @hexa:lossy.network | so maybe it is available via improvble again? | 14:57:08 |
| @hexa:lossy.network | also, you can probably get its logs over the usb port | 14:57:42 |
| @qbit:tapenet.org | reflashed the fw and it popped back up | 15:02:39 |
| @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 |
