AlCalzone

The intended way to leave a network would be to trigger exclusion on the primary, then using the `beginLeavingNetwork` API in Z-Wave JS (which behaves similar to pressing a button...

``` 2025-09-17 11:41:08.301 DRIVER « [Node 001] [REQ] [BridgeApplicationCommand] │ RSSI: -57 dBm └─[SecurityCCSchemeGet] ``` Looks like Vera tries to initiate the S0 bootstrapping, but Z-Wave JS does not react...

I'm pretty sure the stale nodes issue is related to https://github.com/zwave-js/zwave-js-ui/issues/4361 Seems that Z-UI needs to invalidate its nodes cache in a few more cases. The new log showed the...

This also happens when specifying an exact version. E.g. with ``` version: 1.3.0-beta.0 stableVersion: 1.2.3 ``` running `yarn version 1.3.0-beta.1` actually changes the version to `1.2.4-0` instead. **Edit:** It looks...

@arcanis there is a workaround for this and a good guess what causes the issue. I'm not sure how to reproduce this with sherlock though.

FWIW, deleting `stableVersion` from package.json before and after bumping the versions does result in the expected behavior. https://github.com/AlCalzone/release-script/pull/109/files

Any chance you have the Z-Wave logs prior to this aswell, so I can reproduce?

The file seems to be empty

Those are the wrong logs unfortunately. I need the driver logs which show the network traffic on loglevel debug: https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

Uhh, this is great! It seems that this fixes my issue https://github.com/microsoft/typescript-go/issues/1347 too. @chase could you include the compiler test case I posted in that issue?