Niccolò Belli

> Ohhh, that's awesome, have you had problems ever since you started using the patches? I'm writing this from Chromium 101 on my Talos 2, it's been working very well...

@madscientist159 would it be possible to allow login using github/gitlab credentials like freedesktop does?  I think that would lower the contribution barrier while keeping a dedicated gitlab instance.

> unfortunately your driver log is not on loglevel "debug", so it doesn't tell much It was supposed to be on `debug`, but since I crosscompile from my laptop I...

Here are the logs with debug level: [zwavejs_2022-02-04.log](https://github.com/zwave-js/node-zwave-js/files/8002784/zwavejs_2022-02-04.log) [zwavejs2mqtt_2022-02-04.log](https://github.com/zwave-js/node-zwave-js/files/8002785/zwavejs2mqtt_2022-02-04.log) Initially I just did a network heal. Apart from a node being marked as dead just to be immediately back I...

> That must be this. IMO, this looks terribly like the 700 series issue isn't entirely solved for all commands I guess so, I'm not the first one who experienced...

I've updated Z-Pi 7 to fw v7.17.2 and zwavejs2mqtt to 6.7.1.2a08abd (zwave-js 9.0.2). I've done a full heal, but unfortunately it still looks like nodes are dying/reviving mid-heal: ``` 2022-04-15...

> Question is if the route between 2 and 83 is causing these or the one between controller and 2. Definitely between node 2 and 83 because the controller is...

Health check on node 28 seems to be fixed in git master thanks to https://github.com/zwave-js/node-zwave-js/pull/4494:  Unfortunately healing still picks terrible routes and we absolutely need a way to pick...

I (briefly) [did work](https://youtu.be/qBh6-Pd5Otw) on VSCode extensions, but I can't assure I will be able to tackle this because my experience is limited and I'm quite short on free time...

> Your title says can't heal any nodes, but as you describe it appears they all healed except the last one, correct? Nope, they **all** healed including the last one,...