| 27 Jul 2021 |
 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 |
| @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.
https://matrix.to/#/!QhvgabMQzwEQeWehhZ:lossy.network/$bu3ZzKHt4_oXlTZiga_CFvhyUjHyY8W27LFmmPGhCR4?via=lossy.network&via=matrix.org&via=nixos.dev
| 00:47:01 |
| @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.
https://matrix.to/#/!QhvgabMQzwEQeWehhZ:lossy.network/$bu3ZzKHt4_oXlTZiga_CFvhyUjHyY8W27LFmmPGhCR4?via=lossy.network&via=matrix.org&via=nixos.dev
| 00:47:09 |
 Church | Well that's horrific | 00:58:27 |
| Church | Guess we have to patch the package.json? | 00:58:45 |
| @hexa:lossy.network | I'm open to ideas | 01:03:14 |
| @hexa:lossy.network | do you have a specific patch in mind? | 01:04:17 |
| Church | Hmm, lemme see | 03:04:50 |
| Church | hexa https://github.com/Koenkk/zigbee2mqtt/blob/master/index.js Could comment out/remove line 69 | 03:07:15 |
| Church | That calls checkDist which calls the run build. | 03:07:34 |
 Zhaofeng Li | Can we send a patch upstream to add an option? It was just added 10 days ago and they don't look very frenck-y to me | 04:25:50 |
| Church | Definitely an option I think. | 05:59:25 |
| Church | We can see how open they are. | 05:59:34 |
 @andi:kack.it | https://github.com/Koenkk/zigbee2mqtt/issues/8145 | 08:45:28 |
| @andi:kack.it | That fix they provided is sufficient to fix it in my package. I could remove the hack I added last week when this first appeared. You should always have a dist/hash file in your output that contains unknown now. That is sufficient for the application to not do any of the weird stuff during startup. | 08:52:29 |
| @hexa:lossy.network | thanks | 09:18:01 |
| @hexa:lossy.network | odd, that is already in 1.21.0 | 09:20:15 |
