Getting started with CLI on RaspberryPi

Did you also run this?

sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)

The single port that's being reported is a built-in physical serial port on the Raspberry Pi - it's not finding any Bluetooth devices - which could be because of the lack of the command above, or because bluetooth itself isn't working on the Pi

When it does work, --list should show some addresses of the form aa:bb:cc:dd:ee that you can use - and then you should be able to communicate with the Puck.

You can also run sudo hcitool lescan to see if the Bluetooth is able to see any of the Pucks.