# Announce endpoint zone specific

**URL:** <https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304>\
**Category:** Troubleshooting\
**Created:** [April 16, 2024, 12:31am UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304 "2024-04-16T00:31:16Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 16, 2024, 12:31am UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/1 "2024-04-16T00:31:16Z")

</div>

Hey guys, I dove into the announce API once again playing with my HASS automations. I am testing the announce endpoint and I can’t seem to get a reliable way to play each individual zone.

Is it expected that I should be able to specify the zone and have it play only on that one zone?

```auto
{
  "media": "localFile.mp3",
  "zones" : [3]
}

```

If I do `zones:[4]` for some reason it works fine in that one zone, but if I do any other `zones:[0]`, `zones:[1]`, `zones:[2]`, `zones:[3]` I find that it is defaulting to playing in more than one location.

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [April 16, 2024, 2:26am UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/2 "2024-04-16T02:26:18Z")

</div>

This smells like a bug we had early in 0.3.x releases. What version of amplipi are you running?

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 16, 2024, 3:55pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/3 "2024-04-16T15:55:28Z")

</div>

I have been holding back from the 0.3.x releases and am still on the last 0.2 release. Would you advise moving over to 0.3.x at this point?

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [April 16, 2024, 5:25pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/4 "2024-04-16T17:25:04Z")

</div>

Yeah totally. At this point our 0.3.4 release is fairly robust. It also includes a wholly new UI that should be a fair amount more intuitive to use.

Also I looked back apparently that bug I was talking about was introduced in 0.2.0 by [Cleanup and small changes by linknum23 · Pull Request #445 · micro-nova/AmpliPi · GitHub](https://github.com/micro-nova/AmpliPi/pull/445/commits/1e7c0ad2bfcf3afd4ca545dbeba62586b4d3d63e) . It was fixed in 0.3.0 with: [b7cb4dd23c964848977faac2b5805588e81b9efe](https://github.com/micro-nova/AmpliPi/commit/b7cb4dd23c964848977faac2b5805588e81b9efe)

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 16, 2024, 6:19pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/5 "2024-04-16T18:19:59Z")

</div>

Okay great thanks. Will perhaps try upgrading tonight. I saw some worry and issues after upgrading on this forum and decided to hold back for a couple point releases.

I have some automation / scripts / home assistant TTS stuff that I think you guys would enjoy seeing in the near future.

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 17, 2024, 1:18am UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/6 "2024-04-17T01:18:28Z")

</div>

So I went ahead and upgraded to 0.3.4 this afternoon.

Went and tried the announce endpoint once again and am getting strange results.

If I do:

```auto
{
  "media": "/home/pi/Music/attention.mp3",
  "vol_f": "0.2",
  "zones": [4]
}

```

And am sitting in the Kitchen (Zone 4) the volume is modified and zone only plays in Zone 4 (as intended).

However, if I choose something like:

```auto
{
  "media": "/home/pi/Music/attention.mp3",
  "vol_f": "0.2",
  "zones": [0] or [1] or [2]
}

```

The mp3 still plays in the Kitchen (Zone 4) every-time but at an unmodified volume level. It ALSO plays in the intended zone it’s just always playing on Zone 4 too.

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [April 17, 2024, 1:38am UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/7 "2024-04-17T01:38:04Z")

</div>

I’m so sorry you are still having problems with this.

Can you try adding the source\_id field to the request? Changing that could rule out anything weird going on with the zone muxing. The source\_id in an announcement defaults to 3 but 0, 1, or 2 work as well.

```json
{
  "media": "/home/pi/Music/attention.mp3",
  "vol_f": "0.2",
  "zones": [0],
  "source_id": 1
}

```

Does that change anything?

---

<div class="post-metadata">

**Author:** ![matchmee](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@matchmee](https://amplipi.discourse.group/u/matchmee)\
**Post date:** [April 17, 2024, 2:30am UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/8 "2024-04-17T02:30:58Z")

</div>

I would totally love to see some of the stuff you built!

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 17, 2024, 2:12pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/9 "2024-04-17T14:12:27Z")

</div>

No worries. Yeah I just tried the following:

```auto
{
  "media": "/home/pi/Music/attention.mp3",
  "vol_f": "0.6",
  "zones": [0] or [1] or [2] or [3] or [4],
  "source_id": 1
}

```

and it worked individually when I specified the source\_id. No zone 4 playback during the other zones with an unmodified volume.

Is there a drawback to having to specify the source\_id here like this for now?

Also, I did notice that when I make an announcement with a `source_id` that has a “Radio station” paused/stopped (e.g. Groove Salad). When the announcement is done it seems to play the radio station if it’s paused/stopped.

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [April 17, 2024, 2:45pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/10 "2024-04-17T14:45:20Z")

</div>

> Is there a drawback to having to specify the source\_id here like this for now?

The only drawback is that it will temporarily take over whatever source you specify.

> When the announcement is done it seems to play the radio station if it’s paused/stopped.

That’s a bug in the internet radio interaction with announcements. I made an issue for it here: [Bug: Stopped internet radio station, starts playing after announcement · Issue #683 · micro-nova/AmpliPi · GitHub](https://github.com/micro-nova/AmpliPi/issues/683)

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 28, 2024, 4:12pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/11 "2024-04-28T16:12:16Z")

</div>

Hey sorry to bring this back. Am having trouble again with this endpoint. Not sure why it was fine the other day. I changed two inputs around (not zones) and renamed two things but it seems like something is up here once again.

Will post my findings below, just walked around the house a bunch testing all these situations. Not sure what to do here since the source\_id isn’t working like it had that other time.

> Zone 0 - Family Room  
> Zone 1 - Ryan’s Office  
> Zone 2 - Master Bedroom  
> Zone 3 - Rear Porch  
> Zone 4 - Kitchen

> Input 1 - RCA 1 (Zone 0)  
> Input 2 - RCA 2 (Zone 3 and Zone 4)  
> Input 3 - Airplay Source (Zone 2)  
> Input 4 - Spotify Source (Zone 1)

Testing _without the source ID_ set:

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [0]
}

Result -> Plays on Zone 0 and Zone 2

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [1]
}

Result -> Plays on Zone 1

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [2]
}

Result -> Plays on Zone 2 and Zone 1

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [3]
}

Result -> Plays on Zone 3 (And overrides mute) and Zone 1

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [4]
}

Result -> Plays on Zone 4 and Zone 1

```

Testing _with the source ID_ set:

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [0],
  "source_id": 1
}

Result -> Plays on Zone 4 (Unmodified loud volume)

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [1],
  "source_id": 1
}

Result -> Plays on Zone 4 (Unmodified loud volume) and Zone 1

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [2],
  "source_id": 1
}

Result -> Plays on Zone 4 (Unmodified loud volume) and Zone 2

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [3],
  "source_id": 1
}

Result -> Plays on Zone 4 (Unmodified loud volume) and Zone 3 (And overrides mute)

```

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [4],
  "source_id": 1
}

Result -> Plays on Zone 4 (No unmodified loud volume, expected volume)

```

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 28, 2024, 4:44pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/12 "2024-04-28T16:44:30Z")

</div>

Okay, I just rebooted in the Configuration → HW Reboot and tried the following again:

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [0] or [1] or [2] or [3] or [4],
  "source_id": 1
}

```

And it all works fine at first, because every source is muted.

Once I unmute all the sources, it once again reverts to the previous issues I have with source\_id. I will also note, in the main homepage it shows during the announcement:

- It mutes the first source in the list
- Second source shows “First Floor” which is a custom group
- Does nothing to the third and fourth source

Then reverts back to all the settings I had prior to the announcement.

For now I reverted back to using but still have the extra zones called:

```auto
{
  "media": "/home/pi/Music/dryer-done.mp3",
  "vol_f": "0.5",
  "zones": [0] or [1] or [2] or [3] or [4]
}

```

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [April 29, 2024, 9:09pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/13 "2024-04-29T21:09:17Z")

</div>

I replicated your setup and was able to completely reproduce your issues here except for this report:

```auto
{
 "media": "/home/pi/Music/dryer-done.mp3",
 "vol_f": "0.5",
 "zones": [0]
}

Result -> Plays on Zone 0 and Zone 2

```

I’m assuming that you meant `Result -> Plays on Zone 0 and Zone 1`.

Thanks to your careful reporting I was able to find a bug that has existed in announcements from when they were introduced 3+ years ago.

See: [Bug: Zones playing audio on source used for annoncement are not muted while the announcement is playing · Issue #699 · micro-nova/AmpliPi · GitHub](https://github.com/micro-nova/AmpliPi/issues/699)

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [April 29, 2024, 9:13pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/14 "2024-04-29T21:13:02Z")

</div>

Thanks Lincoln! Appreciate you replicating and investigating. I was hoping this thorough report would be helpful in tracking it down. This would be great to get it all sorted!

Let me double check on that one section you were asking about and get back here. I could have messed up writing it down. Just read your bug report over on GitHub, looking forward to the fix.

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [May 1, 2024, 5:50pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/15 "2024-05-01T17:50:34Z")

</div>

> I’m assuming that you meant `Result -> Plays on Zone 0 and Zone 1` .

This is correct, I just had the chance to try this out again. My mistake.

Just saw the PR got merged for the next release. Looking forward to trying it out again, thanks for the quick turnaround!

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [June 14, 2024, 4:28pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/16 "2024-06-14T16:28:54Z")

</div>

Hey @linknum23 I was just curious when you think this change would be pushed for release? I know you prob got a lot of other things going on but didn’t know when you think you’d be doing the next 0.3.X release.

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [June 14, 2024, 5:43pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/17 "2024-06-14T17:43:16Z")

</div>

Very soon! Either today or very early next week. We have a lot of improvements to push out 🙂

---

<div class="post-metadata">

**Author:** ![linknum23](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/linknum23/32/6_2.png) [@linknum23](https://amplipi.discourse.group/u/linknum23)\
**Post date:** [June 18, 2024, 7:29pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/18 "2024-06-18T19:29:31Z")

</div>

Our latest release just got pushed out: [Release 0.3.6 · micro-nova/AmpliPi · GitHub](https://github.com/micro-nova/AmpliPi/releases/tag/0.3.6)

Check it out when you get a chance! It should fix your announcement issues.

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [June 20, 2024, 9:03pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/19 "2024-06-20T21:03:33Z")

</div>

Excellent! Will upgrade soon and report back! Thanks Lincoln

---

<div class="post-metadata">

**Author:** ![rwarner](https://yyz2.discourse-cdn.com/free1/user_avatar/amplipi.discourse.group/rwarner/32/84_2.png) [@rwarner](https://amplipi.discourse.group/u/rwarner)\
**Post date:** [June 23, 2024, 4:41pm UTC](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304/20 "2024-06-23T16:41:55Z")

</div>

Just reporting back to say I ran through my same test I listed out a few posts ago and everything seems to be working as expected. No need for `source_id` either 👍

[Next page](https://amplipi.discourse.group/t/announce-endpoint-zone-specific/304.md?page=2)