!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

505 Members
Declarative Home Automation and other Sidequests | https://wiki.nixos.org/wiki/Home_Assistant132 Servers

Load older messages


SenderMessageTime
24 Feb 2025
@k900:0upti.meK900The Prometheus metric for "entity available" returns 0 if the entity is in state unknonw17:04:01
@k900:0upti.meK900* The Prometheus metric for "entity available" returns 0 if the entity is in state unknown17:04:02
@k900:0upti.meK900Except like17:04:11
@k900:0upti.meK900Most buttons default to state unknown17:04:15
@k900:0upti.meK900And a bunch of integrations report their state as unknown17:04:47
@k900:0upti.meK900And there's literally no way on the Prometheus side to tell if it's unknown or unavailable17:04:57
@k900:0upti.meK900And here I was thinking that I should just set up an alert for when a device becomes unavailable HOW HARD COULD THAT BE17:05:12
@k900:0upti.meK900TURNS OUT VERY FUCKING HARD AND IT'S NOT EVEN MY FAULT17:05:23
@k900:0upti.meK900 @hexa what are my odds of getting this fixed 17:06:47
@k900:0upti.meK900If I make a nicely written bug report about it17:06:53
@hexa:lossy.network@hexa:lossy.networkfairly good if you file the issue first17:11:20
@hexa:lossy.network@hexa:lossy.networkand submit a fix to close that issue17:11:27
@k900:0upti.meK900Problem is, I can'17:11:38
@hexa:lossy.network@hexa:lossy.networkdon't mention using nixos 😛17:11:40
@k900:0upti.meK900* Problem is, I can't really think of an immediately obvious fix17:11:45
@k900:0upti.meK900But I will file an issue17:11:53
@hexa:lossy.network@hexa:lossy.networkthen mention the prometheus component maintainer17:12:12
@marie:marie.cologne@marie:marie.cologne do they still hate us for packaging home-assistant? 17:12:24
@hexa:lossy.network@hexa:lossy.networkno idea17:12:32
@hexa:lossy.network@hexa:lossy.networkand I'm not interested to find out in the context of getting a bug squashed 😄 17:12:49
@k900:0upti.meK900https://github.com/home-assistant/core/issues/13920117:16:16
@k900:0upti.meK900OK let's see where this goes17:16:19
@hexa:lossy.network@hexa:lossy.network @symphorien:xlumurb.eu zap-chip is using an eol electron version 17:42:51
@hexa:lossy.network@hexa:lossy.networkhttps://github.com/project-chip/zap/issues/1502 meh17:58:52
@symphorien:xlumurb.eusymphorienit doesn't impact home assistant does it?18:23:28
@symphorien:xlumurb.eusymphorienotherwise I can patch the requirements18:23:43
@hexa:lossy.network@hexa:lossy.networkI have a PR open to remove electron up to version 3019:17:22
@hexa:lossy.network@hexa:lossy.networkand stopped there because 31 affects home-assistant19:17:33
@symphorien:xlumurb.eusymphorienah ok20:07:07
@symphorien:xlumurb.eusymphorien

hexahttps://github.com/NixOS/nixpkgs/pull/384858 gui still starts up but I don't know how to use this thing

20:25:56

Show newer messages


Back to Room ListRoom Version: 6