| 23 Jul 2021 |
etu | It's not great to depend on it anymore | 08:45:02 |
@hexa:lossy.network | follow #dev:nixos.org for recent hass developments | 11:05:02 |
| 24 Jul 2021 |
Zhaofeng Li | In reply to @etu:semi.social It's not great to depend on it anymore The thing is that there are few alternatives. OpenHAB is moving forward at an extremely slow pace, and others (Gladys?) lack feature and polish. | 00:44:55 |
Zhaofeng Li | People can make that argument that we can roll our own solution from scratch that works with Nix, but that isn't really the most productive use of time and it's silly to tie things like this to the distro, no matter how unique our concept may be | 00:48:00 |
etu | In reply to @zhaofeng:zhaofeng.li The thing is that there are few alternatives. OpenHAB is moving forward at an extremely slow pace, and others (Gladys?) lack feature and polish. I've heard good things about nodered | 03:48:37 |
treed | I got excited about the webthings gateway or whatever but it looks just as Product as hass | 08:08:49 |
treed | https://webthings.io/gateway/ | 08:09:05 |
treed | I guess it does technically have a "Linux" download option | 08:09:28 |
@hexa:lossy.network | pretty sure mozilla discontinued that … or migrated it it to a community project | 08:33:44 |
@hexa:lossy.network |
WebThings is sponsored by Krellian Ltd. and is no longer affiliated with the Mozilla Corporation.
| 08:34:09 |
treed | Yeah, it's separate but still around? | 09:21:21 |
treed | Although they released 1.0 last year and no releases since | 09:21:28 |
| 25 Jul 2021 |
| p3psi joined the room. | 04:43:43 |
| 26 Jul 2021 |
jhillyerd | In reply to @etu:semi.social I've heard good things about nodered I don't think nodered can really replace something like home assistant, it's more of a compliment to it. But I came here to ask, is anyone running nodered on Nix? I see we have an npm build for it in nixpkgs, but it looks like I'd have to do my own systemd configuration, and whatever it uses for data storage. | 16:59:24 |
@hexa:lossy.network | tl;dr: someone dropped it into the node package set et voila | 17:20:29 |
@hexa:lossy.network | yes, you'd need to write your own systemd unit | 17:23:28 |
@hexa:lossy.network | not sure if you'd actually need a database setup | 17:24:30 |
@hexa:lossy.network | I'd first assume that it drops it into its HOME | 17:24:41 |
@hexa:lossy.network | systemd.services.node-red = {
after = [ "network-online.target" ];
wantedBy = [ "multi-user.target" ];
serviceConfig = {
DynamicUser = true;
User = "node-red";
};
| 17:25:38 |
@hexa:lossy.network | * systemd.services.node-red = {
after = [ "network-online.target" ];
wantedBy = [ "multi-user.target" ];
serviceConfig = {
DynamicUser = true;
User = "node-red";
ExecStart = "${pkgs.nodePackages.node-red}/bin/node-red";
};
| 17:25:54 |
@hexa:lossy.network | * systemd.services.node-red = {
after = [ "network-online.target" ];
wantedBy = [ "multi-user.target" ];
serviceConfig = {
DynamicUser = true;
User = "node-red";
ExecStart = "${pkgs.nodePackages.node-red}/bin/node-red";
StateDirectory = "node-red";
};
}
| 17:26:06 |
@hexa:lossy.network | that could be a minimal systemd unit | 17:26:16 |
@hexa:lossy.network | it likely want's a config file | 17:28:10 |
@hexa:lossy.network | if the config uses json or toml you can use pkgs.formats.json | 17:28:37 |
@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 |