I’m trying to write an Alexas routine that sense wnen my motion detector “senses motion”
When I go into the Alexas app to select the motion sensor…it is there…BUT when I select it I get a “not supported message”
Trying to sense when the mail has arrived…any ideas??
In your Alexa app, go to Skills, then find and disable the Wyze skill. As soon as it is disabled re-enable it (log back in using your Wyze credentials) and you should then be able to create a routine that uses the sensor.
Well I tried it…no luck
Same error message “not supported”…yet it shows up in Alexa…
May be too far away…
Tomorrow I’ll try some distant testing…
Where in the routine process does it say not supported? You said you were able to select the motion sensor, so I wonder if it’s another function that isn’t supported.
Edit 30 mins later/. I made a routine earlier to test this to try and replicate, well I forgot to delete it and it just triggered and my Alexa device was full volume and it scares the crapola out of me. It works!
Steps to create routine
Select: when this happens
Select: Smart home
Select : Motion device
BINGO…DEVICE NOT SUPPORTED
Step 5 in previous
Mail should say: “mail senser”,
It’s really a motion senser that’s in the mail box
Thanks for the info. I know you said your relogged into the Wyze skill in Alexa, but have you deleted and readded the motion sensor device in Alexa? If you choose a different Wyze device do you also get the not supported? Or is that just the motion sensor that does this?
Check that the sensor is showing up correctly in the Wyze app. Trigger it and see if the Wyze app sees the event?
I brought the motion sensor into the house…deleted it and re-installed it
…the previous error message is now gone and I can not set up a routine in Alexa…HOWEVER
When I pass my hand across the sensor it detects motion and then sort of locks up with “motion in progress” and just sits there…
It either ignores the routine or it is looking for the camera???
If routine worked it would turn OFF a nearby lamp…
I will now move closer
To the camera and run a test
Success…I had an error in the routine…
Now operating as it should, however there seems to be a delay after it executes a routine…
Not sure if that’s adjustable but I can with that.
Next step…test the “range” of the device…
I have 10 Blink cameras and 3 Arlos…but I’m starting to really like this Waze potential…photos are beautiful
I’ll keep you posted on the range…Thankyou for your expertise…
Well once it executes the routine
It “locks” up on me saying motion in progress…it’s been over 3 min…
I’ll have to delete and reinstall
Ok…seems to be operating normally with a 2 min delay between opations…
Tested ok with 3 tests in a row…
Now for range testingi
Fails the range test…
.works ok if the sensor in “near”
The camera is in the garage…
If I move the sensor toward the fron door and then trigger the device…
It goes into a lock up condition looking for the camera and doesn’t 't even talk to Alexa…
Unfortunately it’s too difficult to move the camera right now but I may order another camera and install it near the front door to see if that helps…
The normal communication pathway would be sensor to bridge, bridge to camera, camera to router, router to app/Wyze etc and then reverse. In practice the camera with the bridge seems to work up to about 30 feet from sensor with no intervening walls etc, when you add obstructions or walls or large masses of metal etc the range drops quickly.
I have 3 motion sensors, the farthest gap from sensor to bridge is about 10 feet.
Yes, you’ve hit it right on the head…
I suppose the small “door” sensors suffer the same delema…it’s one of the major trade offs for miniaturization