Oh, yeah. I noticed this, too. It seemed like a filename length issue. I don’t recall the exact length, but it is somewhere around 18, IIRC. To get around this, I shortened the names of the offending files and tried again until they all “fit” with usable filenames. Thanks for the reminder!
Family Appreciation Factor: it was brought to my attention (!) the voices sound “tinny.” Due to the speaker or transducer in the siren. You just can’t stuff a hi-fi speaker into such a small form factor.
In the latest version of files, I plugged an Echo Dot into my laptop & recorded Alexa making the announcements. It sounded a little better. Perhaps finding a “voice” that works best with the little device will improve the sound output.
Regardless, the ZSE50 is a great, versatile device and a good addition to our Smart Home.
Yes. I find the sounds I record in Audacity (with my own voice) or if I use Amazon Polly they sound rather good. My halloween sounds seem fine for my purposes but yes, tinny for sure at times.
Although the howling wolf is driving my dog crazy. He keeps looking for him lol.
Curious if you could solve this with a global variable - that way when the device id changes, you update the variable once? (I haven’t tried this myself, just probing)
Improved Tone File Management: Resolved the tone file ordering issue by introducing fixed, addressable locations for each tone. Adding or removing sound files will no longer alter the sequence of existing tones. This update ensures that scenes remain consistent and unchanged when new files are loaded.
Home.