!QhvgabMQzwEQeWehhZ:lossy.network

NixOS Home Automation

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

Load older messages


SenderMessageTime
16 Nov 2021
@hexa:lossy.network@hexa:lossy.networkThank you!12:25:37
@hexa:lossy.network@hexa:lossy.networkAlright, that is very promising19:41:40
@hexa:lossy.network@hexa:lossy.network
❯ ./result/bin/zigbee2mqtt
Building Zigbee2MQTT... (initial build), failed
(node:2382814) UnhandledPromiseRejectionWarning: Error: Command failed: npm run build
/bin/sh: line 1: npm: command not found

    at ChildProcess.exithandler (child_process.js:383:12)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Socket.<anonymous> (internal/child_process.js:443:11)
    at Socket.emit (events.js:400:28)
    at Pipe.<anonymous> (net.js:686:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2382814) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:2382814) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
19:41:45
@hexa:lossy.network@hexa:lossy.networksure, why not execute npm run build at runtime19:41:57
@hexa:lossy.network@hexa:lossy.networkfeel right at home19:42:11
@hexa:lossy.network@hexa:lossy.networkjust puke into my filesystem please19:42:16
@schnecfk:ruhr-uni-bochum.deCRTifiedzigbee2mqtt too now?19:43:02
@hexa:lossy.network@hexa:lossy.networkI think that started around 1.20 IIRC19:43:15
@schnecfk:ruhr-uni-bochum.deCRTified:(19:43:19
@hexa:lossy.network@hexa:lossy.networkhttps://github.com/Koenkk/zigbee2mqtt/blob/0a1fccf6b3c7383ead8d5b6c77ac6063e70c31aa/index.js#L4719:44:18
@schnecfk:ruhr-uni-bochum.deCRTifiedI think it's getting to a point where I don't feel comfortable with relying on zigbee2mqtt (and home assistant)19:44:19
@hexa:lossy.network@hexa:lossy.networkwell they certainly don't plan to nixos, but with zigbee2mqtt it is probably not on purpose19:44:47
@hexa:lossy.network@hexa:lossy.networkand it's not the first package we've patched to behave19:44:54
@hexa:lossy.network@hexa:lossy.networkhttps://github.com/Koenkk/zigbee2mqtt/blob/0a1fccf6b3c7383ead8d5b6c77ac6063e70c31aa/index.js#L60-L6219:45:24
@hexa:lossy.network@hexa:lossy.networkthe build is conditional even19:45:26
@schnecfk:ruhr-uni-bochum.deCRTified
In reply to @hexa:lossy.network
https://github.com/Koenkk/zigbee2mqtt/blob/0a1fccf6b3c7383ead8d5b6c77ac6063e70c31aa/index.js#L47
Wow, but why? Don't they have everything at hand that they need to built it in the first place? Don't really know much about the internal structure of z2m, but I didn't see much that was plugin-based before
19:45:29
@jeroen:simonetti.nlJeroenhexa: are you trying to package zigbee2mqtt? If so, id be interested in your progress, just to see how you are doing it (asking for a friend) ;)19:48:01
@hexa:lossy.network@hexa:lossy.networkversion 1.16.0 is packaged, I'm trying to update it to 1.22.019:48:21
@jeroen:simonetti.nlJeroenI tried zwavejs2mqtt but failed badly19:48:33
@jeroen:simonetti.nlJeroenAh cool, ill check that out19:48:50
@hexa:lossy.network@hexa:lossy.network
In reply to @jeroen:simonetti.nl
I tried zwavejs2mqtt but failed badly
yeah, node/typescript/etc are a mess
20:03:29
@hexa:lossy.network@hexa:lossy.networkhttps://github.com/andir/infra/blob/64c46a0a4492ca8785ed2540fec76de9e94db78e/nix/packages/default.nix#L239-L27621:04:09
@hexa:lossy.network@hexa:lossy.networkzigbee2mqtt packaged using npmlock2nix21:04:24
17 Nov 2021
@maniacofmadness:matrix.orgManiac of Madness joined the room.06:36:35
@mic92:nixos.devMic92network integration seems to be broken on master: Setup failed for network: Unable to import component: No module named 'ifaddr' 12:40:35
@mic92:nixos.devMic92 This also breaks ios and zeroconf 12:41:44
@mic92:nixos.devMic92 transmission also seems to have an issue: Setup failed for transmission: Unable to import component: No module named 'transmissionrpc' 12:42:42
@mic92:nixos.devMic92interesting: we seem to have the right version: https://github.com/home-assistant/core/blob/b6dea3c6cb291c7df9282eb46e617a25e7d69c80/requirements.txt#L1512:44:12
@simisimis:matrix.orgseeMeecan I somehow add google calendar as an entity in HA?15:27:03
@schnecfk:ruhr-uni-bochum.deCRTified
In reply to @simisimis:matrix.org
can I somehow add google calendar as an entity in HA?
https://www.home-assistant.io/integrations/google/ should do the trick
15:28:01

Show newer messages


Back to Room ListRoom Version: 6