| 12 Jan 2025 |
 teto | it matches what a youtuber I trust reported (with a preview unit). Guess I will wait a bit then since anyway it would probably add to the things I want to play with but can't find the time to fix all the flaws. I am interested in the v2 | 01:40:02 |
 @hexa:lossy.network | I require both hands to enable the mute button, because it needs a bit of force, which is surprising for the lightweight case | 01:40:54 |
| @hexa:lossy.network | the microphone and speaker work perfectly well though | 01:41:14 |
| @hexa:lossy.network | no issue there | 01:41:24 |
| @hexa:lossy.network | it is mostly about getting the pipeline right | 01:41:32 |
| @hexa:lossy.network | so I don't think it is a bad product per se | 01:41:46 |
|  Samsonite joined the room. | 03:55:43 |
| Samsonite | hey all, i'm a bit new to nixos. ive started playing with it in a lot of systemd-nspawn containers. my host OS is still debian. ive recently installed and configured frigate in a nspawn container and ive set up most everything to work, except i cannot get the coral to be detected | 04:05:27 |
| Samsonite | and i'm not sure if it's a nixos problem or a nspawn problem | 04:05:45 |
| Samsonite | host lsusb shows Bus 002 Device 002: ID 1a6e:089a Global Unichip Corp.
apparently from what ive read, once the coral is initialized, it changes and will say google coral
but something has to try to use it first i guess
inside my nixos container i just see:
Bus 002 Device 002: ID 1a6e:089a
my frigate.nspawn file on the host has: | 04:06:20 |
| Samsonite | [Files]
Bind=/dev/bus/usb:/dev/bus/usb
[Device]
DeviceAllow=/dev/bus/usb/* rwm
| 04:06:42 |
| Samsonite | i do have libedgetpu added as a system package in my configuration.nix file | 04:07:29 |
| Samsonite | services.frigate = {
enable = true;
hostname = "localhost";
settings = {
detectors = {
coral = {
type = "edgetpu";
device = "usb";
};
};
| 04:08:09 |
| Samsonite | any help would be very appreciated | 04:08:14 |
 uep | i got blocked at enabling esphome (see screenshot above) and then wandered off and got distracted with the rest of the weekend. tips welcome for whenever i get back to it again | 04:20:17 |
| @hexa:lossy.network | the host needs to be the hardware's ip address, not localhost 😄 | 04:21:40 |
| uep | er, that's for the esphome service that's running locally, not the voice device.. not up to that yet | 04:28:59 |
| @hexa:lossy.network | heh | 04:30:01 |
| @hexa:lossy.network | the service does not connect like that | 04:30:05 |
| @hexa:lossy.network | you can put it in an iframe, which will make it look like an addon | 04:30:15 |
| @hexa:lossy.network | https://www.home-assistant.io/dashboards/dashboards/#webpage-dashboard | 04:31:15 |
| uep | i have no idea. The install doc says the voice device will be magically auto detected, but that apparently assumes i have esphome integration set up, which it was not. So that's what i was trying to add | 04:31:29 |
| @hexa:lossy.network | if you have esphome in extraComponents that should be sufficient | 04:31:53 |
| uep | so i services.esphome.enabled = true; and tried to add the integration. | 04:32:20 |
| uep | yeah, i do. | 04:32:32 |
| uep | already did from day 1. | 04:32:46 |
| @hexa:lossy.network | not required | 04:33:09 |
| uep | ok | 04:33:16 |
| @hexa:lossy.network | that is for having the esphome dashboard to edit, upload, maintain your own esphome devices | 04:33:30 |
| @hexa:lossy.network | * that is for having the esphome dashboard to edit, upload firmware to, and maintain your own esphome devices | 04:33:53 |
