Announcement

Collapse
No announcement yet.

Alexa suddenly stopped working

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

    Alexa suddenly stopped working

    Hi

    I hope you can help before I throw Alexa through window.

    Since mid july I have not been able to get Alexa to communicate in any ways with my Homeseer. Until mid july I have been running a UK Amazon dot (in Denmark) on an US Amazon developer account with a custom invocation name ("the house"), and again. It worked perfectly. https://forums.homeseer.com/showthread.php?t=184368

    Nothing appears in the HS log and Alexa just responds with "I'm sorry, that command was not recognized". But the skill links without any problems.

    I have tried the original "Homeseer" skill, but that cannot find any devices. Links to Homeseer without any problems.

    I have also tried "Homeseer Home Automation Skill" with same bad result.

    My HS3 connects gracefully to MyHS, and I can connect to my Homeseer through MyHS. And again. All skills links to MyHS without any problem.

    Also tried recreating skill, factory reset of Dot, disable/enable MyHS.

    Im running 3.0.0.318, and using jon00 Alexa helper (latest version, which i also have tried disabling).

    I hope some of you can provide some input on how to fix this before Alexa will meet her new destiny.


    Best regards
    Jonas

    #2
    The command not being recognized is an issue on the Amazon side

    You should check the log in your echo account. (this is different from HomeSeer)

    This will give you the exact message that the echo is hearing from you.

    Maybe Amazon has changed something, but nothing has changed on the HomeSeer side in that time frame.
    Wade

    "I know nothing... nothing!"

    Comment


      #3
      I have absolutely no clue what has happened.

      There was absolutely no response when i wrote original message, but when I decided to test again today the exact same phrases works.

      Generally im missing debugging options with Alexa, and to see what really hits MyHS. I dont think the logging under Settings -> History is sufficient.

      But ill better leave Alexa alone now that she responds.

      Comment


        #4
        Originally posted by levring View Post
        I have absolutely no clue what has happened.

        There was absolutely no response when i wrote original message, but when I decided to test again today the exact same phrases works.
        As posted earlier, Alexa doesn't alert you to the fact that she can't "phone home" to Amazon, she just doesn't work. At that point, it is all on Amazon and they have to fix their end, your end is fine.

        My experience in trying to troubleshoot this particular problem is a lot like trying to see if the light went off in the refrigerator, when you closed the door...
        HomeSeer Version: HS4 Pro Edition 4.2.19.0 (Windows - Running as a Service)
        Home Assistant 2024.3
        Operating System: Microsoft Windows 11 Pro - Desktop
        Z-Wave Devices via two Z-Net G3s
        Zigbee Devices via RaspBee on RPi 3b+
        WiFi Devices via Internal Router.

        Enabled Plug-Ins
        AK GoogleCalendar 4.0.4.16,AK HomeAssistant 4.0.1.18,AK SmartDevice 4.0.5.1,AK Weather 4.0.5.177,AmbientWeather 3.0.1.9,Big6 3.44.0.0,BLBackup 2.0.64.0,BLGData 3.0.55.0,BLLock 3.0.39.0,BLUPS 2.0.26.0,Device History 4.5.1.1,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,HSBuddy 4.50.128.5,JowiHue 4.1.3.0,LG ThinQ 4.0.25.1,ONVIF Events 1.0.0.5,SDJ-Health 3.1.1.9,TPLinkSmartHome4 2022.12.30.0,UltraCID3 3.0.6681.34300,Z-Wave 4.1.0.3

        Comment

        Working...
        X