| 8 Jul 2021 |
 @andi:kack.it | Perhaps start by stating which channel that is on? :) | 08:04:39 |
 @hexa:lossy.network | and whether you are using zwave or zwave_js | 11:24:56 |
| @hexa:lossy.network | for the serial access for zwave I'll provide the fix with tdoays update | 11:35:05 |
| @hexa:lossy.network | * for the serial access for zwave I'll provide the fix with todays update | 11:35:13 |
| @hexa:lossy.network | the latest update of home-assistant has tied multicast membership requests into a central fixture ._. | 12:19:42 |
| @hexa:lossy.network | basically the hass fixture (a toy home-assistant instance) tries to to ssdp | 12:21:47 |
 @etu:semi.social | ugh, zwave_js, I don't feel like migrating my zwave 😀 | 12:23:13 |
| @etu:semi.social | And why mix in js? | 12:23:25 |
| @etu:semi.social | It's already messy enough | 12:23:32 |
| @hexa:lossy.network | I kinda wish we had a dummy netdev in the stdenv, so tests could find interfaces, subscribe to multicast groups | 12:23:40 |
| @hexa:lossy.network | and have that interface lead nowhere | 12:23:43 |
| @hexa:lossy.network | etu: it is a reimplementation of zwave-js in pure python | 12:23:53 |
| @etu:semi.social | ah | 12:24:00 |
| @etu:semi.social | I still have hopes for another future than hass 😀 | 12:24:14 |
| @hexa:lossy.network | invest now :p | 12:24:22 |
| @etu:semi.social | That was previously discussed here | 12:24:26 |
| @etu:semi.social | How? 😀 | 12:24:30 |
| @hexa:lossy.network | get the people together, shape a vision, flesh out a prototype | 12:24:59 |
| @hexa:lossy.network | meh, I want a home-assistant staging branch 😫 | 12:44:30 |
 CRTified | In reply to @etu:semi.social
That was previously discussed here I think instantepiphany was the one who wanted to start such a project and wrote a feature list for a MVP here. Maybe some dedicated channel or GH project or something might make sense sooner than expected, just to have a location to keep track of this - even if it's only thinking about ideas and concepts | 12:32:00 |
 Mic92 (Old) | hexa: I don't think anything is stopping you from it. | 12:49:14 |
| @hexa:lossy.network | yup, true | 12:49:53 |
| @hexa:lossy.network | Fabian Affolter, dotlambda: there is now a home-assistat branch you can target | 12:54:27 |
| @hexa:lossy.network | or … well. push to. | 12:54:37 |
 iclanzan | In reply to @hexa:lossy.network
for the serial access for zwave I'll provide the fix with todays update I am using the original zwave integration. Let me know when the fix lands. | 13:56:25 |
| @hexa:lossy.network | iclanzan: this is the fix fwiw: https://github.com/NixOS/nixpkgs/pull/129644/commits/d57f643a434f3cd3a65f89268a40075845bea04c | 13:57:04 |
| iclanzan | Thanks! Do you have any ideas of what I could prod at next regarding the file permission issue? | 13:59:07 |
| @hexa:lossy.network | I'm not sure what your setup is trying to do honestly | 14:00:11 |
| @hexa:lossy.network | but yeah, allowlist_external_dirs is required for ReadWritePaths | 14:02:15 |
| @hexa:lossy.network | maybe you can check the resulting systemd unit, whether it includes that path? systemctl cat home-assistant.service | 14:02:34 |
