| 14 Jun 2021 |
 @hexa:lossy.network | yeah, it's difficult to find the proper spot(s) to make the community well aware | 21:17:38 |
| @hexa:lossy.network | header of the wiki page probably | 21:17:44 |
 vika (she/her) 🏳️⚧️ | It's just... My train of thought goes "of course it's unsupported, NixOS is doing a lot of things its own way" | 21:19:01 |
| vika (she/her) 🏳️⚧️ | And additionally I like reading upstream documentation and it usually lists supported installation methods | 21:19:23 |
| vika (she/her) 🏳️⚧️ | So by the time I get to distribution-specific documentation I'm usually well aware of support status for certain more esoteric setups | 21:19:59 |
| @hexa:lossy.network | right | 21:20:13 |
| vika (she/her) 🏳️⚧️ | I just hope it won't be the "toxic" kind of unsupported where issues get closed without letting you speak if you go so far as mentioning an unsupported configuration somewhere | 21:20:47 |
| @hexa:lossy.network | - enable = mkEnableOption "Home Assistant";
+ enable = mkEnableOption "Home Assistant. Please note that this installation method is unsupported upstream";
| 21:20:46 |
| @hexa:lossy.network | I've submitted reasonable issues to the upstream before | 21:21:02 |
| vika (she/her) 🏳️⚧️ | In reply to @hexa:lossy.network
- enable = mkEnableOption "Home Assistant";
+ enable = mkEnableOption "Home Assistant. Please note that this installation method is unsupported upstream";
I like this one more! | 21:21:33 |
| @hexa:lossy.network | You just need to make sure that the issue really belongs there | 21:21:20 |
| @hexa:lossy.network | If you can't tell better to report to us. | 21:21:30 |
| vika (she/her) 🏳️⚧️ | In reply to @hexa:lossy.network
You just need to make sure that the issue really belongs there That's what I consider reasonable actually | 21:22:08 |
| @hexa:lossy.network | Yup, don't need to mention hass or nixos again that way, and it relates to upstreams wording | 21:21:58 |
| vika (she/her) 🏳️⚧️ | If I'd go my way about making home automation, I'd make a lot of HTTP gateway/webhook daemons to certain protocols for devices I have on my smart home, not depend on state at all - rather describe everything as, e.g. systemd units depending on each other, and then make a dashboard+event handler service that talks to these gateways and/or receives webhooks with events. I don't think smart homes should have any sort of state at all - most of the devices in my home only have transient state stored in them that disappears as soon as they're unplugged and plugged back in (or power goes out).
Maybe HTTP is not the best protocol for that but it'll do the job which is the important thing. Then one could wrangle it under nginx, create a nice HTML+CSS+a little bit of JS dashboard (TODO: generate it with Nix?) to send manual commands to things and enjoy a fully declarative configuration | 21:27:23 |
| vika (she/her) 🏳️⚧️ | I think that's similar enough to how home assistant functions | 21:27:43 |
| vika (she/her) 🏳️⚧️ | But more distributed and with a lot less stateful knobs and "fake plug-and-play" state-inducing install wizards | 21:28:41 |
| vika (she/her) 🏳️⚧️ | One could probably also host, e.g. a gateway for bulbs in a certain room on a Raspberry Pi in that exact room to make the systems semi-independent | 21:29:58 |
| vika (she/her) 🏳️⚧️ | If only I had smart bulbs that didn't require a cloud connection with a proprietary protocol | 21:30:24 |
 colemickens 🏳️🌈 | seems like there should at least be an informal project started to collect people. I see the same criticisms of HA from NixOS-y folks and it seems like our goals would be well-aligned. | 21:30:29 |
| vika (she/her) 🏳️⚧️ | Actually I think Yeelight makes bulbs that can be controlled locally, don't they? | 21:30:47 |
| colemickens 🏳️🌈 | cc: etu | 21:30:37 |
| vika (she/her) 🏳️⚧️ | And I've seen an official manual for their protocol so they care about DIY segment somewhat | 21:31:15 |
| colemickens 🏳️🌈 | I have also been disappointed to see HA seem to embrace "productization" and point-and-click statefulness over what I perceived to be a simpler declarative static model when I first adopted it. | 21:31:11 |
| @hexa:lossy.network | smart home to me also means metrics, and automation based on these metrics | 21:31:24 |
| @hexa:lossy.network | and a common interface to same-in-class devices of different vendors | 21:31:52 |
| @hexa:lossy.network | the move to statefullness of home-assistant also has me slightly worried, I started using home-assistant way back with v0.21, and back then yaml was king | 21:33:05 |
 @etu:semi.social | In reply to @colemickens:matrix.org
cc: etu I would really like to move away from Hass really, I don't use super many integrations really... I could probably build something similar buy depending on the same libraries... | 21:39:05 |
| @etu:semi.social | But currently I'm very preoccupied with family things | 21:39:29 |
| vika (she/her) 🏳️⚧️ | In reply to @hexa:lossy.network
smart home to me also means metrics, and automation based on these metrics metrics could probably be collected with a separate component, I don't think it's impossible to fit in the model I described | 21:40:02 |
