Announcement

Collapse
No announcement yet.

Alexa skill doesn't work. Tried everything

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • spud
    replied
    phillb, chuckk9032 your logs show "request=echocontrol" which is a request that was used by the original homeseer skill which is no longer available. The current skills are no longer supposed to use this request. A side effect of a change made in 4.1.17.0 broke this request, we are going to fix it so that it in the next version of HS4, it works as in 4.1.16.0. That being said, could you try to remove the skill you are currently using and add back the new skill? this should fix your issue without having to wait for the next version of HS4.

    nickgosling, your logs show the correct request i.e, "request=controldevicebycontroluse", so your issue is different and not linked to the 4.1.17.0 version. If you still have issues with Alexa, I would advise to create a service desk ticket.

    Leave a comment:


  • nickgosling
    replied
    Spoke too soon. I think it may be an issue with zwave devices in alexa as my other devices are ok.

    What I have found by doing some testing is that if I enable the Zwave Root device instead of the actual light alexa discovers it and I am also able to control it. However alexa says "there was a problem" under the device name. I can now control the device which is a step in the right direction.

    Leave a comment:


  • nickgosling
    replied
    Got it working. Slightly annoying however this is how I did it and it didn't take long.

    Displayed all my devices including all the hidden ones. Enabled bulk edit. Selected every device then selected "disable voice" on the bulk actions menu.
    After that I deleted all my devices on the web based alexa (alexa.amazon.co.uk) and then ran a discover to check nothing was discovered.
    Then I reselected all the devices that I wanted to control with Alexa and used the bulk actions option again to "enable voice'
    I then did another rediscovery in Alexa and not only were the devices discovered they are now controllable.

    I hope this makes sense and might help someone else. It not a very elegant solution but at least it now works. I have 15 devices and these were all sorted into rooms in the alexa app which I have now redone but it was a little tedious.

    I'm not sure what the Bug is but ideally I'd like not to have to do that again.
    Thanks for all the help

    Leave a comment:


  • spud
    replied
    Originally posted by phillb View Post
    Jun-23 22:35:52 DEBUG JSON Query: request=echocontrol&command=ON&ref=414&token=437410865628173 08661

    Spud I am using the homeseer skill

    above is the single line that come up in the log

    Could you tell me ow to turn this debug mode off some time please

    let me know if you want anything else
    Phill
    thanks
    To turn off json debugging, run the following script command
    hs.debugmode=0

    Leave a comment:


  • zakrzep
    replied
    I am also using the homeseer smarthome skill. Stopped working after 4.1.17.0. And to clarify, I am on Windows. That might be the difference between some users working on Linux?

    Leave a comment:


  • phillb
    replied
    Originally posted by spud View Post
    Could you do this:
    From Tools > Scripts commands, enter hs.debugmode=2048 then click run
    this will turn on json debugging
    then try the command that fails from Alexa, and post here what you get in the logs

    Also, please tell me which skill you are using
    thanks
    Jun-23 22:35:52 DEBUG JSON Query: request=echocontrol&command=ON&ref=414&token=437410865628173 08661

    Spud I am using the homeseer skill

    above is the single line that come up in the log

    Could you tell me ow to turn this debug mode off some time please

    let me know if you want anything else
    Phill

    Leave a comment:


  • SteveW
    replied
    I upgraded to 4.1.17.0 on Linux. I am using the "Homeseer" skill. All of my devices can still be controlled by Alexa, and I did not refresh or reconfigure anything on the Alexa side. It simply works.

    In related news, 4.1.17.0 fixes the long-standing bug with Google Home getting device status from HS. I didn't have to re-sync or otherwise mess with my Google Home/HS4 settings. Yay!

    Leave a comment:


  • nickgosling
    replied
    I am using the homeseer smarthome skill.

    Leave a comment:


  • chuckk9032
    replied
    Originally posted by spud View Post

    Thanks that is helpful
    Can you tell me which skill you are using?
    This error was using the Homeseer skill, not the Homeseer SmarHome skill. However, I haven't gotten the HomeSeer SmartHome skill working again either. It is currently disabled.

    Leave a comment:


  • nickgosling
    replied
    Originally posted by spud View Post

    Could you do this:
    From Tools > Scripts commands, enter hs.debugmode=2048 then click run
    this will turn on json debugging
    then try the command that fails from Alexa, and post here what you get in the logs
    thanks
    Hi Spud,

    Sorry for the late response. I haven't been at home. Attached is a screenshot of the result that I got. Thanks. Click image for larger version

Name:	Alexa commands.png
Views:	117
Size:	604.9 KB
ID:	1480855

    Leave a comment:


  • spud
    replied
    Originally posted by phillb View Post
    When I upgraded to V. 4.1.17 that’s when my problem started before that no issues at all.
    Could you do this:
    From Tools > Scripts commands, enter hs.debugmode=2048 then click run
    this will turn on json debugging
    then try the command that fails from Alexa, and post here what you get in the logs

    Also, please tell me which skill you are using
    thanks

    Leave a comment:


  • phillb
    replied
    When I upgraded to V. 4.1.17 that’s when my problem started before that no issues at all.

    Leave a comment:


  • spud
    replied
    Originally posted by chuckk9032 View Post

    This is what I get in the logs when running debug and issuing an Alexa command:

    6/23/2021 11:10:19 AM
    HomeSeer
    DEBUG JSON
    Query: request=echocontrol&command=ON&ref=258&token=117244771818771 77534

    Alexa response: "XXX isn't responding. Please check its network connections and power supply." XXX represents all HS devices that are shown in Alexa.
    Thanks that is helpful
    Can you tell me which skill you are using?

    Leave a comment:


  • chuckk9032
    replied
    Originally posted by spud View Post

    Could you do this:
    From Tools > Scripts commands, enter hs.debugmode=2048 then click run
    this will turn on json debugging
    then try the command that fails from Alexa, and post here what you get in the logs
    thanks
    This is what I get in the logs when running debug and issuing an Alexa command:

    6/23/2021 11:10:19 AM
    HomeSeer
    DEBUG JSON
    Query: request=echocontrol&command=ON&ref=258&token=117244771818771 77534

    Alexa response: "XXX isn't responding. Please check its network connections and power supply." XXX represents all HS devices that are shown in Alexa.

    Leave a comment:


  • spud
    replied
    I'm trying to investigate the Alexa issues that happen specifically with HS 4.1.17.0
    If you have some problems with Alexa with other versions please open new threads
    Jez,
    zakrzep
    ,
    can you tell me if you are using the HomeSeer Home Automation Skill (i.e tell HomeSeer) or the HomeSeer SmartHome Skill ?

    Leave a comment:

Working...
X