Claim your device automatically¶
IMPORTANT: It is assumed that the Raspberry Pi is connected to an internet-facing network via the Ethernet port. It is also assumed that your computer is in the same local network as your board.
This section describes how to automatically claim your device using pvr. If you want to do it manually, see how to do it in the claim your device manually guide.
On first boot Pantavisor will start the Alpine platform and wait for it to configure the network devices until Pantahub.com is reachable. Once this happens, Pantavisor will proceed to register the newly seen device with Pantahub.com and issue a challenge for the device to be claimed by a registered user account.
In order to claim your device you will need a Pantahub account, so make sure you have created one and have had it approved before the following. We are mostly interested now in the following command:
$ pvr scan
TROUBLESHOOTING: If no devices are detected, check both your Raspberry Pi and your computer are connected to the same network. Check also mDNS packets are allowed in your router and port 5353 is open in your computer firewall. Finally, access to your router admin settings and see if DHCP has served an IP to the board and that you can ping it. If none of this brings any result, check our Raspberry Pi 3 troubleshooting page.
$ pvr scan command, we will be able to discover devices in our network, both claimed and unclaimed, if they have no owner. We must begin by discovering and claiming our device:
pvr finds a device on the local network it will present this metadata for you to claim it via the command quoted in the output. Just run that command as-is and your user should now own your device.
It can take a minute or two, depending on your connection, for a device to fully show up on Pantahub's device list the first time it boots. Wait a few if it hasn't showed up, it eventually will. Once your device shows up as claimed and under your ownership, you can interact with it via
post commands. For example, if you
clone a device you will get a checkout of the different container assets that make up this firmware revision.