One trick that I use to isolate a problem is to temporarily rename the device to zebra or sesame and then see if it works. The word is unique enough, so if it is a naming issue, you at least know it is open zebra works, though open sesame sounds much cooler.
Announcement
Collapse
No announcement yet.
HomeSeer SmartHome Skill (Alexa Version 3 API)
Collapse
X
-
Originally posted by wkomorow View PostOne trick that I use to isolate a problem is to temporarily rename the device to zebra or sesame and then see if it works. The word is unique enough, so if it is a naming issue, you at least know it is open zebra works, though open sesame sounds much cooler.
Comment
-
Originally posted by Tomgru View PostI have a virtual device setup for my garage door.
If I try 'open garage door'... I get "more than one device was found with that name combination.
If I try "unlock"... alexa tells me she can't do that now "to be safe".
If I try "lock the garage door", this will work (e.g. close it)
If it try "close the large garage door".. I get the more than one device found message again.
I only have one device with this name. I've also gone through and made sure the voice command box is unchecked on anything else that's close (like garage door motion sensor)
I've tried forgetting all devices and starting over.
can you guys give me a few debugging ideas to run with? Would it be as easy as changing the parameters control use to on/off instead of lock/unlock so Alexa doesn't think it's a lock?
You mentioned "close the large garage door" as one of the things you tried. The picture says Small Garage Door, so possibly Alexa just isn't understanding you since you have more than one device with similar names. It's just hearing "something garage door" which might be why it says you have more than one device with that name.
Comment
-
I think my amazon account is messed up. I am able to get v3 HS skill working on my wifes profile. But when I switch back to my profile I cannot discover any devices.
I have a ticket open wit AWS but if anyone else has had similar issues and knows how to fix, LMK.
Thanks.
NET-NET, HSv3 skill is working just fine. Looks like a AWS issue or some DB corruption on my account profile (just a guess). But I do recall when the issue happened, I "forgot" all my devices and got an error on the forget even though it worked. But since then have not been able to discover anything (until today when I logged in with my wifes profile and added the HS skill)
thanks.
Comment
-
Hi,Rjh
Can you send the skill to amazon.fr
I have installed it from amazon.uk and my system is linked.
I can turn on and off some light in my house in "French", but we are in the Beta Test for France.
all my device are offline but respond to vocal command
I can't see my event in Scenes
Thanks
The link is : https://alexa.amazon.fr
Jean-francois.
Comment
-
Add my discover log:
mars-04 20:59:18
DEBUG JSON
Query: request=getevents&voiceonly=True&token=70525612708613451256& source=EchoSH
mars-04 20:59:18
DEBUG JSON
Query: request=getsetting&setting=gGlobalTempScaleF&token=705256127 08613451256&source=EchoSH
mars-04 20:59:18
DEBUG JSON
Query: request=getstatus&devref=3782&voiceonly=False&token=70525612 708613451256&source=EchoSH
mars-04 20:59:18
DEBUG JSON
Query: request=getsetting&setting=gGlobalTempScaleF&token=705256127 08613451256&source=EchoSH
mars-04 20:59:18
DEBUG JSON
Query: request=getstatus&devref=3765&voiceonly=False&token=70525612 708613451256&source=EchoSH
mars-04 20:59:17
DEBUG JSON
Query: request=getsetting&setting=gGlobalTempScaleF&token=705256127 08613451256&source=EchoSH
mars-04 20:59:17
DEBUG JSON
Query: request=getstatus&devref=3258&voiceonly=False&token=70525612 708613451256&source=EchoSH
mars-04 20:59:17
DEBUG JSON
Query: request=getcontrol&ref=3859,3861,3860,3868,3820,3857,3863,38 62,3866,3864,3865,3766,3770,3768,3769,3767,3766,3770,3768,37 69,3767,3765,3259,3263,3261,3262,3260,3259,3263,3261,3262,32 60,3258,3858,3783,3787,3785,3786,3784,3783,3787,3785,3786,37 84,3782,2820,3882,3879,3883,3888,3892,3889,3891,3887,3890,38 70,3874,3871,3873,3872,3592,3877,3875,3876,3885&token=705256 12708613451256&source=EchoSH
mars-04 20:59:17
DEBUG JSON
Query: request=getstatus&devref=3783,3784,3785,3786,3787&voiceonly= False&token=70525612708613451256&source=EchoSH
mars-04 20:59:16
DEBUG JSON
Query: request=getstatus&devref=3259,3260,3261,3262,3263&voiceonly= False&token=70525612708613451256&source=EchoSH
mars-04 20:59:16
DEBUG JSON
Query: request=getstatus&devref=3766,3767,3768,3769,3770&voiceonly= False&token=70525612708613451256&source=EchoSH
mars-04 20:59:16
DEBUG JSON
Query: request=getstatus&devref=all&voiceonly=True&token=7052561270 8613451256&source=EchoSH
mars-04 20:59:15
DEBUG JSON
Query: request=getsetting&setting=bLocationFirst&token=705256127086 13451256&source=EchoSH
Comment
-
I thought I'd document something here that I haven't seen others discuss, just in case anyone else runs into this issue.
I use the "User Access" function in devices, mainly to simplify the device list for my wife. To that end, many of the root devices are set to only allow user access to the user "admin".
My thermostat wasn't working with the echo, and in troubleshooting I changed the thermostat root device back to "any" user access.
Viola, now the thermostat is discovered and working by alexa.
This nuance should probably be documented in the skill setup documentation.
Comment
Comment