| 26 Jul 2021 |
 @hexa:lossy.network | * if the config uses json or toml you can use pkgs.formats.json to render that | 17:28:42 |
| @hexa:lossy.network | and I agree that node-red is more about tying workflows together, creating automations | 17:30:45 |
| @hexa:lossy.network | while home assistant has alot more integrations into $everything | 17:31:02 |
| @hexa:lossy.network | and offers a dashboard and a working automation system | 17:31:35 |
 CRTified | In reply to @hexa:lossy.network
if the config uses json or toml you can use pkgs.formats.json to render that Note that json is a subset of YAML, so that format is also covered by that function | 17:32:38 |
| @hexa:lossy.network | to /some/ degree. only that which can be represented within nix. | 17:33:07 |
| @hexa:lossy.network | nothing like raw values used for type casting or custom functions | 17:33:55 |
| @hexa:lossy.network | * to /some/ degree. only that which can be represented within nix (the language). | 17:34:31 |
| @hexa:lossy.network | jhillyerd: https://github.com/NixOS/nixpkgs/pull/116578 | 18:58:11 |
 jhillyerd | I was just reading through a long thread by him in the main NixOS room. Sounds like node-red expects to be able to install npms on the fly at run time, so it's not likely to be as easy as I'd hoped. | 19:06:07 |
| jhillyerd | Thanks for linking that though, will keep an eye on it. | 19:08:06 |
| @hexa:lossy.network | rough | 19:12:12 |
| @hexa:lossy.network | can always use a container | 19:12:23 |
| @hexa:lossy.network | * can always use a container, if you really want to 🥸 | 19:12:45 |
| jhillyerd | Yeah, that's likely what I'll end up doing. It's not like I want/need to declaratively configure a drag & drop programming language. 🙂 As long as I can back up my flows after I've made them. | 19:35:07 |
 @andi:kack.it | All of these home automation tools are just shitting into their own workspace all the time.. I'm tracking zigbee2mqtt myself an packaging it with npmlock2nix and recently that piece of excellent software started running npm run build on startup... If computers haven't killed us all in 10y we surely have lost control of how to actually run software offline by then. | 21:54:56 |
| CRTified | Oh no, zigbee2mqtt is also starting with that behavior? 😓 | 21:56:35 |
| @andi:kack.it | Looks lke touch dist/.hash is enough but really... I think the target audience of home automation is just demanding "make it work" too much.. | 21:57:32 |
| @andi:kack.it | Oh no, they are actually hashing and comparing something.... | 21:58:22 |
| @hexa:lossy.network | huh, using zigbee2mqtt via node2nix, didn't notice any breakage | 22:26:08 |
| @hexa:lossy.network | also it's mostly that they just don't know any better | 22:28:31 |
| @hexa:lossy.network | they are mostly scratching their own itch and don't want to be burdened by our strange limitations | 22:28:59 |
| @hexa:lossy.network | not really surprising, is it? | 22:29:17 |
| @andi:kack.it | You are probably not following the develop branch then? They recently switched to typescript | 22:57:06 |
| @hexa:lossy.network | releases only | 23:04:56 |
| @hexa:lossy.network | https://github.com/esphome/esphome/pull/2055/files | 23:04:57 |
| @hexa:lossy.network | so yeah, esphome does it, too? | 23:05:21 |
| @hexa:lossy.network | well, for external components, whatever they are | 23:06:32 |
|  ashkitten (it/its) 🏳️⚧️ left the room. | 23:14:49 |
| 27 Jul 2021 |
| CRTified | In reply to @hexa:lossy.network
well, for external components, whatever they are I think that's only changing the behavior when using esphome, not when packaging it. So it's possible to put esphome into nixpkgs, but you can't use nix to build an esphome configuration that relies on external_components, which are basically third-party addons that weren't included into esphome | 08:45:58 |
