| 26 Jul 2021 |
 @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 |
| @hexa:lossy.network | fair | 08:46:21 |
| CRTified | I mean, it's also possible to hack on the src for the ESP firmware in "normal usage" | 08:46:29 |
| CRTified | In the end, esphome boils down to a "code generation framework" | 08:46:59 |
| CRTified | * In the end, esphome boils down to a "code generation framework", and external_components allows you to declare third-party dependencies | 08:47:30 |
| CRTified | * In the end, esphome boils down to a "code generation framework", and external_components allows you to declare third-party dependencies for additional components | 08:47:35 |
| CRTified | * In the end, esphome boils down to a "code generation framework", and external_components allows you to declare third-party dependencies for additional components used in that generation process | 08:47:44 |
| @hexa:lossy.network | I packaged up some EV charging controller software and would hope for some quick review. https://github.com/NixOS/nixpkgs/pull/131475 | 13:19:09 |
| 28 Jul 2021 |
| @hexa:lossy.network | https://rc.home-assistant.io/blog/2021/07/28/release-20218/ | 20:45:05 |
| @hexa:lossy.network | 
Download image.png | 20:45:20 |
| @hexa:lossy.network | Redacted or Malformed Event | 20:45:35 |
| @hexa:lossy.network | https://media.discordapp.net/attachments/857346526527094814/869697914308554762/distribution.gif | 20:46:01 |
| 2 Aug 2021 |
| @hexa:lossy.network | zigbee2mqtt 1.21.0 … here we are. | 00:42:42 |
| @hexa:lossy.network | machine # [ 19.309961] zigbee2mqtt[882]: Building Zigbee2MQTT... (initial build), failed
machine # [ 19.322058] zigbee2mqtt[882]: (node:882) UnhandledPromiseRejectionWarning: Error: Command failed: npm run build
machine # [ 19.323645] zigbee2mqtt[882]: /bin/sh: npm: command not found
machine # [ 19.324600] zigbee2mqtt[882]: at ChildProcess.exithandler (child_process.js:308:12)
machine # [ 19.327325] zigbee2mqtt[882]: at ChildProcess.emit (events.js:314:20)
machine # [ 19.328799] zigbee2mqtt[882]: at maybeClose (internal/child_process.js:1022:16)
machine # [ 19.330959] zigbee2mqtt[882]: at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
machine # [ 19.333815] zigbee2mqtt[882]: (node:882) 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)
machine # [ 19.340992] zigbee2mqtt[882]: (node:882) [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.
machine # [ 19.372681] systemd[1]: zigbee2mqtt.service: Succeeded.
(3.29 seconds)
| 00:42:51 |
| @hexa:lossy.network |
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.
| 00:45:33 |
| CRTified | Yeah that looks like a horrible trend... | 00:46:23 |
