| 23 Feb 2025 |
 @hexa:lossy.network | same package, different metadata | 00:55:51 |
| @hexa:lossy.network | wild | 00:55:51 |
 oddlama | I'm also not sure. I think the main issue is that they hardcode the directory to /data in the first place, otherwise we could just skip the bind mount which seems to cause the problems. I've seen the same CHIP:DL: Failed to create temp file /data/chip_factory.ini-gR0axc: Permission denied error on a friends HA instance, but never on mine. The difference being that they use a nixos container and I am running on bare metal. Maybe the added file system namespace interferes with the bind mount in some way. | 12:22:30 |
|  noah_andrews changed their display name from noah_andrews to harperrr. | 23:22:46 |
| 24 Feb 2025 |
|  Leon joined the room. | 00:30:38 |
 mattleon | I tested this nixpkgs PR on my system, and it appears to fix the permissions issue. Still not sure exactly why it happens for v7 but not prior versions, though. In further testing, it seems like the issue was the matter SDK update, which has this PR: https://github.com/project-chip/connectedhomeip/pull/35428 | 01:33:26 |
|  @lynatic:catgirl.cloud joined the room. | 03:41:48 |
 K900 | Are you fucking kidding me | 17:02:43 |
| K900 | The Prometheus metric for "entity available" returns 0 if the entity is in state unknonw | 17:04:01 |
| K900 | * The Prometheus metric for "entity available" returns 0 if the entity is in state unknown | 17:04:02 |
| K900 | Except like | 17:04:11 |
| K900 | Most buttons default to state unknown | 17:04:15 |
| K900 | And a bunch of integrations report their state as unknown | 17:04:47 |
| K900 | And there's literally no way on the Prometheus side to tell if it's unknown or unavailable | 17:04:57 |
| K900 | And here I was thinking that I should just set up an alert for when a device becomes unavailable HOW HARD COULD THAT BE | 17:05:12 |
| K900 | TURNS OUT VERY FUCKING HARD AND IT'S NOT EVEN MY FAULT | 17:05:23 |
| K900 | @hexa what are my odds of getting this fixed | 17:06:47 |
| K900 | If I make a nicely written bug report about it | 17:06:53 |
| @hexa:lossy.network | fairly good if you file the issue first | 17:11:20 |
| @hexa:lossy.network | and submit a fix to close that issue | 17:11:27 |
| K900 | Problem is, I can' | 17:11:38 |
| @hexa:lossy.network | don't mention using nixos 😛 | 17:11:40 |
| K900 | * Problem is, I can't really think of an immediately obvious fix | 17:11:45 |
| K900 | But I will file an issue | 17:11:53 |
| @hexa:lossy.network | then mention the prometheus component maintainer | 17:12:12 |
 @marie:marie.cologne | do they still hate us for packaging home-assistant? | 17:12:24 |
| @hexa:lossy.network | no idea | 17:12:32 |
| @hexa:lossy.network | and I'm not interested to find out in the context of getting a bug squashed 😄 | 17:12:49 |
| K900 | https://github.com/home-assistant/core/issues/139201 | 17:16:16 |
| K900 | OK let's see where this goes | 17:16:19 |
