| 12 Jan 2025 |
 @hexa:lossy.network | * yeah, much more introspection into the zigbee network was the reason I chose z2m | 00:37:46 |
 teto | started with zha since that was the default ?! but quickly switched to z2m as it supported more of my devices (and in general it supports more from what I read). Has been pretty good so far. It took hours to draw a map of my 10 devices network but that must be an issue with the network rather than z2m, which is why I was tempted to test version 2 before reporting some feature requests | 01:29:11 |
| teto | hexa: please share your nabu case device "voice" experience onceyou've tried. I ponder getting one. | 01:29:56 |
| @hexa:lossy.network | teto: did you read this article yet? | 01:30:33 |
| @hexa:lossy.network | tinker isn't entirely clear on what his processing pipeline is, but the general picture is there | 01:35:26 |
| @hexa:lossy.network | the local sentence patterns preform really well, but you need to know them | 01:36:00 |
| @hexa:lossy.network | piping stuff into an LLM allows you to send off wild queries, that it will execute perfectly fine | 01:37:00 |
| @hexa:lossy.network | it also holds context between multiple triggers | 01:37:20 |
| @hexa:lossy.network | but it sometimes messes up simple things | 01:37:55 |
| @hexa:lossy.network | earlier today I asked it to make a light brighter, and it did that, but also did that for a light in the room that was off | 01:38:18 |
| @hexa:lossy.network | which was unexpected | 01:38:20 |
| @hexa:lossy.network | * earlier today I asked it to make a light brighter, and it did that, but also did that for another light in the room that was off | 01:38:31 |
| @hexa:lossy.network | the packaging was cute and no plastics at all | 01:39:08 |
| @hexa:lossy.network | the device feels very light, it has rubber feet in the corners, but since it is so lightweight the cable sometimes dominates its positioning here 😄 | 01:39:54 |
| 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 |
