msgreenf Posted March 31 Share Posted March 31 Kasa is 100% supported by amazon still Quote Link to comment Share on other sites More sharing options...
msgreenf Posted March 31 Share Posted March 31 https://www.amazon.com/TP-LINK-Kasa/dp/B01EIQX6Y8 Quote Link to comment Share on other sites More sharing options...
msgreenf Posted March 31 Share Posted March 31 https://www.tp-link.com/us/support/faq/944/ Quote Link to comment Share on other sites More sharing options...
Benoît van Osch Posted March 31 Share Posted March 31 1 hour ago, msgreenf said: Kasa is 100% supported by amazon still The Kasa plug is still fully controllable by Alexa but Alexa does not allow its dimming value to be used as a routine trigger event. I am looking for a way to trigger Alexa speech by using an input from Control4. It would take home automation to the next level. Quote Link to comment Share on other sites More sharing options...
SpencerT Posted March 31 Share Posted March 31 20 minutes ago, Benoît van Osch said: The Kasa plug is still fully controllable by Alexa but Alexa does not allow its dimming value to be used as a routine trigger event. I am looking for a way to trigger Alexa speech by using an input from Control4. It would take home automation to the next level. Try voicemonkey. You can call it from the tcp driver. https://voicemonkey.io/help Quote Link to comment Share on other sites More sharing options...
Benoît van Osch Posted March 31 Share Posted March 31 1 hour ago, SpencerT said: Try voicemonkey. You can call it from the tcp driver. https://voicemonkey.io/help Thank you for the recommendation. What do you mean with calling it from the TCP driver? Please could you explain a bit more on how to set this up with Alexa and Control4 for it to show as trigger events in Alexa. Quote Link to comment Share on other sites More sharing options...
SpencerT Posted March 31 Share Posted March 31 3 hours ago, Benoît van Osch said: Thank you for the recommendation. What do you mean with calling it from the TCP driver? Please could you explain a bit more on how to set this up with Alexa and Control4 for it to show as trigger events in Alexa. Take a look at the documentation. In short, you create a trigger in voicemonkey which appears as a doorbell in Alexa. Create a routine in Alexa for when your voicemonkey routine triggers. Call it via the API (or webhook) they provide using the chowmain generic tcp driver. Quote Link to comment Share on other sites More sharing options...
Benoît van Osch Posted April 1 Share Posted April 1 15 hours ago, SpencerT said: Take a look at the documentation. In short, you create a trigger in voicemonkey which appears as a doorbell in Alexa. Create a routine in Alexa for when your voicemonkey routine triggers. Call it via the API (or webhook) they provide using the chowmain generic tcp driver. Thanks, I’ve been reading through the documentation but wasn’t sure if I had to use HA or IFTTT as a bridge between VM and C4. Are you saying that the TCP driver can communicate directly with VM and get its full capability? Quote Link to comment Share on other sites More sharing options...
RAV Posted April 1 Share Posted April 1 Other options: Shelly - haven't tried it myself, but the theory is all there. They allow 3 virtual triggers free, or sign up for Premium (~$40 yearly) and have up to a 100 You setup Shelly as the go between to send the trigger to Amazon as a virtual doorbell. Set pretty much anything in Shelly based on it's state. When light at 10% Notify Amazon Trigger 10 for example. Alexa Shelly Skill & Control4 Shelly driver How do you feel about a third party having access to some of your Amazon information? These all have Sign in with Amazon requirements to set up linking. Webhook Routine Trigger Voice Monkey Virtualsmarthome.xyz Each operate similarly. Send a URL command to their website and it's passed to Amazon. So reliant on their web service and Amazon Partner shares from Amazon at least: name, email, account ID and access token. Amazon Account Linking and Control4 TCP driver Quote Link to comment Share on other sites More sharing options...
Benoît van Osch Posted April 2 Share Posted April 2 22 hours ago, RAV said: Other options: Shelly - haven't tried it myself, but the theory is all there. They allow 3 virtual triggers free, or sign up for Premium (~$40 yearly) and have up to a 100 You setup Shelly as the go between to send the trigger to Amazon as a virtual doorbell. Set pretty much anything in Shelly based on it's state. When light at 10% Notify Amazon Trigger 10 for example. Alexa Shelly Skill & Control4 Shelly driver How do you feel about a third party having access to some of your Amazon information? These all have Sign in with Amazon requirements to set up linking. Webhook Routine Trigger Voice Monkey Virtualsmarthome.xyz Each operate similarly. Send a URL command to their website and it's passed to Amazon. So reliant on their web service and Amazon Partner shares from Amazon at least: name, email, account ID and access token. Amazon Account Linking and Control4 TCP driver Thanks Rav for the overview, very much appreciate the effort. Shelly sounds like a good alternative for people that dont want to share account information with third parties so I will look into that. Separate question I have is around the possibility of knowing what Alexa device is spoken to in a multi-Alexa household. Do you know if there is a way to get this information to Control4 so that e.g. when I say 'good-night' in a certain bedroom, some logic can trigger different routines / logic dependent on the Alexa device spoken to n order to switch of lights, TV, etc in that room? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.