Hi,
I am having trouble with my device again. I received a replacement CM3 a few weeks ago and have installed that, and everything was fine for a few weeks.
However today I noticed my announcements are no longer working. I have a DIY doorbell which plays a chime from a local file server (over HTTPS) when the gate is opened.
Attached is the logs from my device (collected using Graylog) which shows 10s of activity prior/post/including the event.
Then I noticed my device had got into a bad state this evening. The app was working on my phone but I couldn’t add zones to a stream or unmute a zone. I rebooted the device and now it is working again, although I haven’t had chance to test the announcements, as the kids are all asleep!
Is there anything in these logs which show a problem?
Cheers,
Ben
PS - I wasn’t allowed to upload my CSV log files. Can you DM me and I will send them thru directly.
Hey Sumnerboy!
This sounds like something we’d like to poke at personally, could you open a support tunnel and email us the details of the tunnel and the logs at support@micro-nova.com?
You can open a support tunnel by going to Settings → Updater → Support Tunnel → Request Tunnel → copy+paste the security details and send them to us
Steven Engelbert
Support Coordinator
After getting into the support tunnel the initial thing we are seeing is a lot of announcements that haven’t been cleaned up. This is evidence that your system has had a lot of overlapping announcements. I don’t think you use the amplipi ui much but if you did you would have noticed 20 or so extra streams named “Announcement” in the stream drop down list (don’t worry we cleaned those up for ya).
Overlapping announcements definitely have the potential to cause some weird issues, since AmpliPi’s state can get corrupted when an announcement plays during another announcement. This is due to a bug in the design of announcements: Bug: Volume changing after multiple overlapping announcements · Issue #485 · micro-nova/AmpliPi · GitHub
The cause of overlapped announcements in your house is likely from doorbell events that are linked through an automation to an announcement. The doorbell events likely happen quicker than the announcement takes to finish. For the moment I would recommend trying to queue those events up to ensure the doorbell announcements happen one at a time.
Here’s a recent discussion on this that might shed more details.
Zone Specific Announce Misbehaving - #11 by linknum23
In the long run, doorbell automatons like this should just work. Our team will have some discussions about how to make this work better in the future. Stay tuned…
Yeah I have noticed those Announcement streams and have cleaned them up previously but they kept appearing so I left them. That does make some sense that it could be the cause of my issues.
I have use the AmpliPi for two types of announcements, one when the entry gate is opened (to play a doorbell chime) and the second when my DIY house alarm is arming/disarming (to play an alarm chirp).
I already have rate limiting on the doorbell chime, so it will only play an announcement at most every 5 mins. So the only issue I can see is if the alarm chirp is playing and the doorbell is triggered (the chirp can run for up to 60s or until the alarm is disarmed).
I will try adding some logic to disable the doorbell when the alarm is arming/disarming and see if this helps.
Thanks for diving into my machine and having a poke around!!