diff --git a/README.md b/README.md
index 20369f2..a63515c 100644
--- a/README.md
+++ b/README.md
@@ -65,3 +65,11 @@ With the previous steps, you will provide the code grant and the plugin will do
 - It will generate the access and refresh tokens
 - It will store them in a file named `.homebridge-spotify-speaker` in the homebridge's persist directory. Thus, when your homebridge server restarts, it can fetch back the tokens.
 - It will automatically refresh the access token when needed
+
+## Finding a speaker device ID
+
+Once the spotify authentication flow is done, the plugin will display the list of available devices in your Homebridge logs. In Homebridge UI, keep an eye on the logs when the plugin restarts and you will see a message looking like the following:
+
+![Example Device Log](assets/example-device.png)
+
+You can then take the `id` from the Spotify device that you want to control and this is what you put in the plugin's configuration as the `spotifyDeviceId`.
diff --git a/assets/example-device.png b/assets/example-device.png
new file mode 100644
index 0000000..ffd7e90
Binary files /dev/null and b/assets/example-device.png differ
diff --git a/package.json b/package.json
index 3618807..750aa61 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "displayName": "Homebridge Spotify Speaker",
   "name": "@poblouin/homebridge-spotify-speaker",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "Homebridge plugin that creates a speaker that plays a specific Spotify playlist",
   "license": "MIT",
   "author": "Pierre-Olivier Blouin <poblouin@pm.me>",