I got it working. Alexa has discovered the ZigBee devices I have. However, it can only turn on the lights. When I tell it to turn off, it says "the light is not responding and to check the power supply". Has anyone else had this happen?
Homey is out of the line expensive. There is new one ISG by linknlink. Has Home assistant and their own operating for simple management. Has a display tablet. Can use home assistant when ready or not.
Yolink is another freq. LoRa Only one that works at distance. Inexpensive . And have lots of different devices. Freezer alarms, contact sensor, outdoor motion for driveway, exterior plugs, inside plugs.
Thanks for the tutorial but I encountered an issue. Alexa found the devices I exposed, but when I wanted to turn on/off, it just says server unresponsive.
@SmartHomeTheory what about the Alexa Smart Home Skill? In my opinion my Alexa doesn't even try to search for new devices. When I ask to discover devices, Alexa replies right away saying it could not discover any new smart home devices and finally is giving the advice to enable Smart Home skill in the Alexa App. Looks like in order to enable SMART Home Skill an AWS account is needed which is free for the first 12 month only. Do I need Smart Home skill enabled or there is another way to do it? BTW I got the first Alexa edition (echo), don't know if matters or not.
so, it means that I can control any Wi-Fi device without need to Alexa compatible? and for example when i try to add a Wi-Fi switch to Alexa what should I do? like it can automatically recognize?
Great video. I have been using Emulated Hue to turn on and off lights/switches from Alexa. I have also incorporated input booleans to toggle scripts to run. While this has been ok, you still need to remember to say "turn on" or "turn off" to Alexa. I am interested in switching to node red but if I already have an entity setup in Emulated Hue, how to I switch it over to node red? Do I need to wipe out the emulated hue and clear the Alexa cache?
my HA (June2024 edition) is running on port 8123 - Docker... I tried both 80 and 8123 - rebooting HA every time after saving the yaml file - no difference... xxx.xxx.x.x:8123 or coures works but xxx.xxx.x.x:8123/api/v2/lights produces an error 404 in the browser.... i.e. nothing
Hi, great video. I got a problem qhen using additional commands. Everytime I invoke Alexa i get :"I seems that "device x" is not responding" but the order is executed. Can you help me? Thanks
This is an informative video. It filled in some blanks for me. I just ordered a Raspberry Pi 5 to be dedicated to Home Assistant. My interest in HA is the ESP32Home add-on.
Hi, handsome bro, I watched your video and think your video is very high quality and it can be a great reference for some people who are curious about smart home but don't know much about it.🥰 We have a similar product, but we are smarter and added temperature and humidity display, so our product can control devices such as air conditioner or humidifier by real time temperature and humidity change. Are you interested in experiencing it and taking videos? I believe your opinion can not only help customers, but also help us to improve and upgrade our products to make us better.😘
MicroSD is fine for getting started. Had mine nearly a year already with zero issues. Still going strong. Even if it did fail that’s what cloud backups are for. I’d be up and running again in 20 minutes tops. Sure there are better alternatives but there’s no need to complicate it in the beginning.
I'm currently utilizing Emulated Hue and am able to expose everything I want, especially if I need unique control by utilizing Input_booleans. However! One Issue I constantly run into with emulated hue is when I add new devices to the configuration.yaml file. Of the like 10+ times I've done it, every single time when I go to add a new device or add a new input boolean I expose to run different automations, Alexa wont discover the new device. I ended up unplugging echos, deleting the file, adding it again, tons of stuff, sometimes i Just wait a day or two and all sudden NOW Alexa will discover it. I DO HAVE ONE Question, I'm considering switch to Nabu Casa for the simplicity to avoid running into the constant issues with Emulated hue. Is the the control through Nabu Casa to Alexa CLOUD all the time? Like if I'm home, and I've got Z-wave devices that I use Nabu Casa to expose to Alexa, does it got to go out to the Cloud then back to turn the Zwave device on? Or is it local like when Utilizing Emulated Hue?
Please how do you manage alexa to turn on/off the tv. I have been trying everything but Alexa is not seeing the TV. When I ask alexa to turn on the TV, I get this message: "Sorry I cannot find a device or group name TV" I will appreciate your assistance on this. Thank you
Wow - this is very cool. I was actually thinking about building my own, but then figured someone might already have made the product. :-) Thanks for the guide.
Can these also be used in reverse? Like using a default IR remote to trigger automations/actions. IF yes this would be amazing if you need tons of buttons for your smarthome/remote
I use port forwarding to Caddy Server, which runs a reverse proxy. This needs only a few lines of config to get working. It gives HTTPS encryption via the free Let's Encrypt service. Using a reverse proxy removed the SSL termination function from HA, so this aspect is a bit more robust than when simply connecting directly to HA across the internet.
Didn't integrate Alexa like this yet but want to say thank you for a great video already. I understand all and I bet it works next week when I find time :)
I don't have any Zigbee devices (I don't think) but I'm using all types of smart home brands, from Tapo to TCP smart to WIZ etc. will these automatically be visible once I've set up home assistant as they're already on the network? great video and thanks for the help
One last thing to consider that i just discovered the hard way: because devices and scripts are exposed and seen as lights by alexa/google, it will turn the "all lights on/off" commands to be useless / dangerous, but its a necessary compromise
True. I never ran into this problem but then again I never say lights off but “goodnight” to turn everything off. If you really want to say “lights off” you could set up a routine called “lights off” and add all your actual lights to it. Should work.
Thats what i had to do after unwillingly setting off everything in what looked like the mr robot hacked home scene, safe guarded those key words by creating routines for them that override the default ones 😅
Thank you so much for your quick respond. I am surprised that I am not able to use Alexa to turn on/off the TV using the IRBlaster even though I can turn the TV on/off using an Entity card. Could you please let me know how you were able to use Alexa to turn the TV on/off. Do you have special yaml settings for emulated hue?. Thanks Kwame
Hi, I am looking to connect HA to Alexa, but the other way around. Instead of controlling my HA devices from the Alexa App, I like to control and automate Alexa with my HA. I am talking about the gazillion of devices which don't integrate locally with HA but connect via a proprietary cloud and are controllable with Alexa. So for these devices I like to get and modify their state with HA. Is this possible?
This simple setup won’t work. I cannot connect to homeassistant.local:8123 I’ve tried using the up and still says site cannot be reached. This is my first project using a Raspberry Pi and so far I’m not very impressed. Can’t even get the thing going. So frustrating.
@@mariondo00 try to install the app and don't do anything. Just ask alexa to discover the devices, after few mins it will get you many new devices, also esp32 ones and now I can do stuff I never thought