!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

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

Load older messages


SenderMessageTime
26 Nov 2024
@hexa:lossy.network@hexa:lossy.network * and ipset is just a tool to manage data structures that holds ip addresses00:37:20
@hexa:lossy.network@hexa:lossy.networkit is used in combination with iptables for quick matches on large sets00:37:28
@hexa:lossy.network@hexa:lossy.networknftables has its own data structures, so ipset is probably as obsolete as iptables00:37:42
@spacekitteh:matrix.orgspacekittehi see i see02:06:04
@joerg:thalheim.ioMic92 hexa: any issues with harmonia? 07:12:01
@hexa:lossy.network@hexa:lossy.networknot really12:25:01
28 Nov 2024
@coelacanthus:mozilla.orgCoelacanthus 🆋 changed their profile picture.21:09:00
29 Nov 2024
@bl1nk:matrix.orgbl1nk changed their profile picture.01:11:45
@bl1nk:matrix.orgbl1nk changed their profile picture.01:12:00
1 Dec 2024
@mighty-heron:digitalprivacy.diymighty-heron joined the room.12:32:02
@freewalkr:fwkrr.rufreewalkr joined the room.15:30:21
@freewalkr:fwkrr.rufreewalkr hi everyone!
to = "on"; in my nix automation trigger config gets converted into to: on yaml config
home assistant interprets this as to: true and throws an error expected str for dictionary value @ data['to']
is this a known issue? has anyone solved it?
15:33:09
@freewalkr:fwkrr.rufreewalkr i see the same line in example config given in wiki page
should it even work?
15:35:05
@k900:0upti.meK900This is a YAML 1.2 thing I think?15:40:34
@k900:0upti.meK900 @hexa did that ever get fixed 15:40:38
@hexa:lossy.network@hexa:lossy.networkI rolled that back to 1.1 a while ago15:41:54
@hexa:lossy.network@hexa:lossy.networkzigbee2mqtt 2.0 is going to hit early january 2025 with breaking changes17:40:41
@hexa:lossy.network@hexa:lossy.networkhttps://github.com/Koenkk/zigbee2mqtt/discussions/2419817:40:43
@hexa:lossy.network@hexa:lossy.networkthere's stuff you can do to prepare today to not get hit hard 😄 17:40:52
@k900:0upti.meK900Honestly I still don't get how we ended up with MQTT as de facto standard RPC protocol for embedded things 17:45:54
@k900:0upti.meK900It's not even good at any of those things17:46:05
@hexa:lossy.network@hexa:lossy.networkeverything is a string 🥳17:48:10
@hexa:lossy.network@hexa:lossy.networkit is what was popular in early home automation tinkering setups17:48:40
@k900:0upti.meK900And everything is a queue 17:48:45
@k900:0upti.meK900Even though very few things actually are 17:48:55
@hexa:lossy.network@hexa:lossy.networkWhat would be the better alternative?17:49:17
@hexa:lossy.network@hexa:lossy.networke.g. CoAP is maybe 10 years old now17:49:49
@k900:0upti.meK900Some reasonable-ish RPC protocol, probably17:49:52
@k900:0upti.meK900I don't think there's anything out there that would be a good fit for all the use cases 17:50:14
@k900:0upti.meK900Which probably means there should be more than one protocol 17:50:35

Show newer messages


Back to Room ListRoom Version: 6