From 68f4e35bb4db166a244366fbd95fc74ee58ca029 Mon Sep 17 00:00:00 2001 From: Kasper Date: Fri, 21 Aug 2026 15:26:16 +0200 Subject: [PATCH] Update NAD M12 - Smart Power Follow --- NAD M12 - Smart Power Follow.-.md | 139 ++++++++++++++++++++++-------- 1 file changed, 104 insertions(+), 35 deletions(-) diff --git a/NAD M12 - Smart Power Follow.-.md b/NAD M12 - Smart Power Follow.-.md index 5b60d92..594c001 100644 --- a/NAD M12 - Smart Power Follow.-.md +++ b/NAD M12 - Smart Power Follow.-.md @@ -32,25 +32,25 @@ The logic is: Media Player State Change │ ▼ - Check all players + Check all players │ - ┌─────┴─────┐ - │ │ - Active All OFF - │ │ - ▼ ▼ - Wait ON Wait OFF - delay delay - │ │ - ▼ ▼ - NAD ON Re-check players - │ - ┌─────┴─────┐ - │ │ - Active All OFF - │ │ - ▼ ▼ - No action NAD OFF + ┌────┴────┐ + │ │ + Active All OFF + │ │ + ▼ ▼ + Wait ON Wait OFF + delay delay + │ │ + ▼ ▼ + NAD ON Re-check players + │ + ┌────┴────┐ + │ │ + Active All OFF + │ │ + ▼ ▼ + No action NAD OFF ## Active Media Players @@ -99,7 +99,7 @@ The sequence becomes: Wait 5 seconds │ ▼ - NAD M12 ON + NAD M12 ON ## Turning the NAD M12 Off @@ -202,22 +202,18 @@ For systems where media players need time to stabilize: Media Player: playing │ ▼ - NAD M12 ON + NAD M12 ON ### Switching between sources Apple TV: playing Spotify: off - │ ▼ - Apple TV: off Spotify: playing - │ ▼ - NAD M12 remains ON ### Stopping all playback @@ -225,7 +221,6 @@ For systems where media players need time to stabilize: Apple TV: off Spotify: off Chromecast: off - │ ▼ Wait 30 seconds @@ -242,12 +237,79 @@ For systems where media players need time to stabilize: - One or more `media_player` entities - A `media_player` entity representing the NAD M12 - The NAD M12 must support `media_player.turn_on` and `media_player.turn_off` -- The NAD M12 must be set to "Network standby" +- The NAD M12 must be set to **Network Standby** +## NAD M12 Home Assistant Configuration + +The NAD M12 is configured in Home Assistant using the NAD media player integration. + +Add the following configuration to your `configuration.yaml`: + + media_player: + - platform: nad + type: Telnet + host: 192.168.0.79 + port: 23 + name: NAD M12 + max_volume: -40 + sources: + 1: "TV" + +### Configuration + +| Setting | Value | Description | +|---|---|---| +| Platform | `nad` | Uses the NAD integration | +| Type | `Telnet` | Communication with the NAD M12 | +| Host | `192.168.0.79` | IP address of the NAD M12 | +| Port | `23` | Telnet communication port | +| Name | `NAD M12` | Name of the Home Assistant media player | +| Max Volume | `-40` | Maximum volume exposed to Home Assistant | +| Source 1 | `TV` | Configured input source | + +### Network Standby + +The NAD M12 must have **Network Standby** enabled. + +This is required so that Home Assistant can communicate with the amplifier and power it on when a selected media player becomes active. + +If Network Standby is disabled, the NAD M12 may not respond to the power-on command while it is in standby. + +### IP Address + +The IP address in the example is: + + 192.168.0.79 + +This must be changed if your NAD M12 uses a different IP address. + +If the NAD M12 receives its IP address through DHCP, it is recommended to create a DHCP reservation for the amplifier in your router so that the IP address does not change. + +### Restart Home Assistant + +After adding or changing the configuration, restart Home Assistant. + +Go to: + + Settings → System → Restart Home Assistant + +After restarting, the NAD M12 should be available as a `media_player` entity. + +### Verify the Entity + +The configured name is: + + NAD M12 + +Depending on the Home Assistant entity naming, the resulting entity will typically be: + + media_player.nad_m12 + +This entity should be selected as the **NAD M12** in the `NAD M12 - Smart Power Follow` Blueprint. ## Installation -The easiest way to install this Blueprint is to use the Import Blueprint button below. +The easiest way to install this Blueprint is to use the **Import Blueprint** button below. ### Automatic Installation @@ -255,10 +317,12 @@ The easiest way to install this Blueprint is to use the Import Blueprint button 2. Home Assistant will open the Blueprint import page. 3. Select **Import Blueprint**. 4. Once imported, the Blueprint will be available under: -`Settings → Automations & Scenes → Blueprints` + + Settings → Automations & Scenes → Blueprints + 5. Create a new automation from the Blueprint. 6. Select the media players that should control the NAD M12. -7. Select the NAD M12 media player entity. +7. Select the `NAD M12` media player entity. 8. Configure the desired power-on and power-off delays. 9. Save the automation. @@ -271,23 +335,28 @@ If the automatic import does not work, the Blueprint can also be installed manua 1. Open the Blueprint YAML file in the [repository](https://gitea.kskovmose.dk/Kasper/HAOS/src/branch/main/Blueprints/nad.yaml). 2. Copy the complete YAML content. 3. In Home Assistant, go to: -`Settings → Automations & Scenes → Blueprints` -4. Select Import Blueprint. + + Settings → Automations & Scenes → Blueprints + +4. Select **Import Blueprint**. 5. Paste the URL of the raw YAML file. 6. Confirm the import. 7. Create a new automation from the Blueprint. 8. Configure the media players, NAD M12 and delays. - ## Troubleshooting ### NAD M12 does not turn on -Check that the selected NAD entity is a `media_player`. +Check that: -Also verify that Home Assistant can control the amplifier using: +- The NAD M12 has **Network Standby** enabled. +- The selected NAD entity is a `media_player`. +- The IP address in `configuration.yaml` is correct. +- Home Assistant can communicate with the NAD M12. +- Home Assistant can execute: - media_player.turn_on + media_player.turn_on ### NAD M12 does not turn off