Alexa App For Windows 10 Free Download

0 views
Skip to first unread message
Message has been deleted

Alfonzo Liebenstein

unread,
Jul 14, 2024, 6:44:46 PM7/14/24
to geopersancde

Just to be clear the camera I have is " [Wyze Cam 1080p HD Indoor WiFi Smart Home Camera with Night Vision, 2-Way Audio, Works with Alexa & the Google Assistant]" if it works on Amazon Echo show with is running of the alexa app then I think it should also run on the Alexa app (dispite the app is on a PC)

alexa app for windows 10 free download


Descargar Zip https://tinurll.com/2yOKgE



Couple of things going on here. Your description could apply to the V1, V2, or V3 but is most likely a WyzeCam V2. The new beta web view should work with a V2 or V3 if you are paying for CamPlus on that camera. The Alexa support is separate, and free when it works.

The following guide provides step-by-step instructions to set up the Alexa Voice Service (AVS) Device SDK on Windows 10 64 bit. This includes installing, building, authorizing, and using the Alexa Voice Service (AVS) Device SDK. When finished, you have a working sample app to test interactions with Alexa.

Before you install the AVS Device SDK, you must Register an AVS Product and Create a Security Profile. After you register your device, you download a config.json file that contains your client ID and client secret. The client ID and client secret authorize your device, so you can retrieve access tokens from AVS. Your config.json file facilitates the authorization calls between your device and AVS.

Download and run the MSYS2 (64-bit) installer. This installs three different shells: MSYS2, MinGW32, and MinGW64. After the installation finishes, open the MinGW64 shell. You should be in the home directory.

Open the MinGW64 shell and run these three commands in a single block statement. This downloads three AVS Device SDK configuration scripts into your MinGW64 home directory. These scripts are later used to download and authorize the AVS Device SDK and sample app.

Make sure you update the path parameters to point to the same locations that you downloaded the WebVTT files to in step one and two of these instructions. For example, /home/alexa/webvtt/build/src/webvtt/libwebvtt.dll and /home/alexa/webvtt/include/.

You are now ready to talk to Alexa. The next time you start the sample app, you don't have to go through the authorization process again. If you close the sample app, start it again by rerunning the startsample.bat file.

Hi! I've built a custom smartblinds controller. My device driver implements the WindowShade capability. Works great in Hubitat dashboards and also Homebridge/HomeKit. However, if I expose my device to the Alexa skill, it does not show up in my Alexa app.

I found that it looks like the Alexa team has just added native support for this type of capability last month:
Developer Feature Requests Support for blinds (or shades) in smart home with open/close/stop/move to %...Hi Alexa,1. There is not BLIND or SHADES as Display Category availabe -apis/alexa-discovery.html#display-categories, so please can you add support for this ?2. Blinds (or shades) can be opened, closed,...

Update: I'm sure Hubitat will get to adding this support to their own Alexa skill eventually, but in the meantime, I created my own Alexa skill that talks to the Hubitat Maker API to control window shades.

It's not a published skill. It's code you can use to host your own skill. I haven't written much instructions, because if you know how to host and install your own skill, you won't need my instructions.

Finally got around to writing my own skill. After I finally got my head around how lambda ties into the skill and everything works I finally got it setup so it discovers my devices. I've written my own lambda function in python to interact with my own "maker api" to control and discover devices. It now imports contact, motion, switch, dimmer, temperature and I will add others after once I figure the next part out.

One note, if you have an issue where it says "device is not responding" but it still works, there is a timeout setting for the lambda code. Where you posted the lambda code, scroll down and you should see basic settings that you can edit.

By default it is set to 3 seconds. But I found 3s to be too short and would timeout before my hub could respond. By default, alexa waits 8 seconds for a response which could be extended by the app responding will a DeferResponse message if needed. Just change this to 8 and you should be good to go.

I've worked out the hard parts here: GitHub - joelwetzel/Alexa-Skill-For-Hubitat-Shades-And-Blinds: An Alexa skill to interact with a Hubitat smarthome hub, and expose shades and blinds to Alexa. (Because the native Hubitat Alexa skill does not yet support shades and blinds.)

Just needs to be integrated into the existing skill. My code there is under a Creative Commons CC0 license, so it's public domain and Hubitat is free to use/remix/include any part of it with zero obligation or rights reserved to me.

I should mention.. There is a small bug in fans at the moment that I'm tracking down.. Specifically with drivers that use both fan control and level capabilities. She gets a little confused with both capabilities reporting at the same time using the same directive response.. I'm hunting that down.. It works.. she just complains that it's not responding.

@bcopelandI've got a similar thing - I have a load of blinds using the Qubino Shutter module. On the latest Hubitat release they come up in Alexa as a switch and a thermostat... but not a blind. Even after removing and re-adding.... any help?

I used this solution for all of my window contacts and have now also the possibility to ask Alexa if any window in my house is closed or opened.
Makes it easy to know if any window in the attic is open when it begins raining, without looking into the App or walking up the stairs.

Hint: After searching for new devices in Alexa, the window contact (aka window lock) item in the Alexa App sometimes seems to be unresponsive. In this case you can simply open and close the corresponding window one time and the status will be updated.

I noticed that the String item is not logged when my door opens. I think that is the problem. I tried the Sensor direct or via a Heating-Group. Both are not showing up in my logs files exept I reboot my Raspberry. Than the sensor get a state once.

What would currently be the best solution if I want to be able to ask Alexa something like:
Sind die Schlafzimmer Fenster geschlossen? and then get an answer back if one of the windows is open (lets say the left one) which is something like: Schlafzimmer Fenster Links ist offen.

It has never been easier to connect your motorized blinds and shades to your Amazon Echo, Echo Dot, and Echo Show devices. All you'll need is a compatible smart home hub and an internet connection. If you have a Google Home device, we have solutions for you, too.

shop alexa compatible

When customizing your motorized blinds or shades, be sure to include a home automation option while selecting your lift. These smart home hubs are small devices that use your homes Internet to send signals to your compatible motorized window coverings. It will give you the ability to control your motorized shades from a phone, tablet, or remote. This hub will also give you the ability to pair your shades to an Amazon Alexa device. Different window treatments may require different types of smart home hubs. Find your compatible device by searching through the list below.

shop compatible products

After setting up your smart home hub and installing your compatible motorized window treatments, you will have to pair your hub to an Amazon Alexa device. Typically, this will require a home internet connection. This connection is usually wireless, but some smart hubs can also use a wired ethernet connection.

This automation checks if a window sensor has been open for 30 seconds or more, then sends me a push notification to my phone. I dont have alexa, but I imagine with the alexa integration you can send a notify to that device in a similar way.

The script referenced at the end is what I actually do when the open window has been detected (in this case pause the heating), but you dont have to have it in a separate script, you could just perform the action in the actions section of the automation:

It can send you a notification when the window has been open for X minutes, repeat that reminder at a given interval (you could set that to 24 hours), and then send you a notification when the window is closed.

d3342ee215
Reply all
Reply to author
Forward
0 new messages