New here and this is my first post. I’m looking for a chime on which you can place your own sound files to queue from homey. Closest thing I could find is the Aeotec siren gen5. But that one is obsolete.
I know there are zwave chimes that come with a few or multiple sounds. But all seem tacky. I want to choose my own minimalistic sounds for when, for example, you arm your security system. And not be limited to one of 5 sounds and be forced to use an air-raid sound…
I don’t have wifi speakers in the house and I wish not to have to make custom speakers from example an rpi. I would love to be able to buy about 4 plug and play devices that can play custom sounds and work on 230v.
Not shure what you want/don’t want, but are a few Google Nest Mini’s (wifi speakers) an option?
They work very well with mp3’s of barking dogs and whatnot, (for me) loud enough.
Install 'em, add them to Homey per Chromecast app and cast away.
Thnx, @BAUWENS_Stephane , I feel like this might be out of my budget. I need a minimum of 4 devices. And would like to expand it to double it.
Sigh, I’ve promised myself an out-off-the-box solution This makes me want to make a few though!
Well, at around €35 a piece this might become an option. But I will have to dive into the privacy questions that raise when adding 4 to 8 listening devices to my home. (yes yes, “send from Android”) Maybe if I can verify the mute button is hardwired and make a IOT Google account and not use my personal account to setup the devices…
Thanks for the feedback, this gives me some creative ideas.
I think I’ll start with a base of hosting all the default sounds on the Homey Pro device. This makes swapping the sounds easy, instead of swapping 4/8 SD cards (when based on ESP32). And stream them to the Nest or ESP32.
Streaming the sounds (since we use WiFi instead of Zwave/Zigbee) will add the option to also use Text-To-Speech with Google Translate API (yes again that Google, I’ll start with it as a base. I’m sure there are TTS APIs that are open source).
Instead of a webbased/ url endpoint version I would swap to MQTT.
I think I’ll start with one Google Nest Mini, and see if we can get the base working from the Homey side. If this works I can choose to expand to multiple nests or build multiple ESP32 devices. Both can be wall mounted of be made in recessed ceilings.
Well shat, and here I thought I would find a plug and play solution, I feel like I’ll have my weekends filled. Well, let’s first wait until the Homey gets shipped
Thank you, @Peter_Kawa for sharing. I suggest setting the maximum volume change to 99% instead of 100% to avoid double dot feedback. This is because at 99%, only single dot feedback occurs. I know it may seem a bit OCD, haha.
Unfortunately, after replying to your message, I am experiencing issues with my Chromecast. Restarted the Chromecast application, all chromecast flow still won’t work It’s frustrating to see that one of Google’s cloud services is not reliable. I am not sure if I am the only one facing this problem.
I was not aware of that. What is the average response time for pressing the doorbell to hearing the sound on the nest? And would this be quicker if you would go to a ESP32 mp3 speaker?
Sjeesh, that’s too long indeed. What would be the bottleneck. Is it Homey, wifi or the Nest? And would a ESP32 approach be quicker, since it’s leaner or would switching to zwave instead of wifi be quicker. Also can the LAN/Wifi be a bottleneck? We have a serious Unifi network instead of the basic modem/router of the ISP.
