Claus Broch

Do you have the Generic BLE module installed? If that'st the case then you need to ensure it's updated to v4.0.1 (or later). Otherwise it will interfere with the bluetooth...

Could you try running the following command from the ~/.node-red directory and attach the result: `npm list`

@phellarv the last line in your log shows that the state changes to "poweredOn" which is OK. @jukkaTheFinn are you also seeing this change to poweredOn, or does it stay...

@phellarv It appears from your log that you had a version of Generic BLE older than v4.0.1 installed, as it starts scanning for nodes even though it isn't part of...

@phellarv did you restart the Raspberry Pi? I have sometimes seen the bluetooth getting into an undefined state where it appears to be working, but it doesn't connect to any...

@phellarv metal cases and wireless are seldom a good combination. This could be the reason it starts scanning, but doesn't detect any devices. I also noticed you are running Linux...

@phellarv good to hear that it can connect now.

@jukkaTheFinn just out of curiosity, did you install node-red-contrib-noble-bluetooth from the Node-RED palette manager, or from the command line?

@jukkaTheFinn Ok. I’m not sure it will solve your problem, but could you try installing it from the command line as described in https://www.norgesvej12a.dk/husbryg/gf-connect-v0-9-2-released/ Hopefully it will provide some indication...

@jukkaTheFinn Even though there are a lot of intermediate errors the last few lines appears to indicate successful installation of several packages. What is the verdict after restarting Node-Red?