Hi everyone. I completed a review video of the ZSE50 (link below) which includes a few use case demos, integration with Home Assistant, and the loading of sound files from the perspective of a Mac user.
I included the solution to getting rid of the metadata files (those that start with “._”) that you get when moving files from a Mac.
I’m sure most folks here on this forum already figured all this out, but if you are interested, the video is online.
I’m also working on a second video about the ZSE50 (hoping to have it out in a week or two) - where I think I’ve developed a way to make it useful as an additional siren for an IQ 4 alarm panel. [While not officially supported or really functional natively in the IQ, I think I have a workaround!? Stay tuned.]. And if anyone knows where I can get a sound file that is the exact IQ panel alarm siren sound, I’d love to get a copy of it!
Nice video, Darren! I’ve wondered about chaining announcements together. For example, “Power lost”…”on Freezer Outlet.” Have you tried anything like that yet?
Of course, one could put together individual .mp3 files to accomplish the same thing, but I noticed when playing a second announcement when the first one is still running causes the first message to be lost & only the second is played.
The ZSE50 is a great product & I am building a list of all the various announcements needed in our home.
Hi. Thanks for the kind words on the video.
Yes, I’ve noticed the same. When it receives a new command it stops playing. It is very useful when you have it set to play continuously (like a siren noise), because the next command can stop the siren. (And super duper handy if triggering the siren’s default sound with direct association!! So like ‘door open’ sounds the alarm continuously until ‘door closed’ happens, when directly associating from a Zooz open/close sensor for example.)
But when trying to stack as you said, it is cumbersome. The only solution I’ve done so far is to know the length of the prompt, and add the length of the first recording plus a few milliseconds of additional delay between announcement commands. So, send command to play first sound (say it is 3 secs long), then wait 3.5 seconds, then send next command to play next sound. Haven’t really spent much time on that as of yet… just thinking out loud…
