Announcement

Collapse
No announcement yet.

Alexa Smarthome down but Alexa Skill is still up

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

  • Alexa Smarthome down but Alexa Skill is still up

    Over the weekend I've Alexa responds that a device is not responding when using the Smarthome functions but works fine when using the standard skill. I have found that if I reboot the Smarthome skill comes back but then stops a few hours later. When I check the logs nothing shows up when using Smarthome commands but I see normal log information when using Skill commands. Since both of these go through HS servers I suspect that the HS to Alexa interface is having troubles and not my system.

    Is anyone else having this issue? I've not rebooted this time incase HS wants to check anything.
    HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
    Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

    Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
    mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

    Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

  • #2
    I had a similar issue that started yesterday. I only use the standard Alexa HomeSeer skill but everything became unresponsive through Alexa but worked fine through the HS interface. I've learned to tread lightly when this happens as it's usually an HS cloud issue. If you start deleting skills and devices it typically ends up a mess. I waited until this morning to see if anything changed but it hadn't. I disabled the skill, enabled the skill which forced me to redo the account linking, and for now everything seems to work and didn't hose up my devices or groups.

    Comment


    • #3
      Still down as of 10AM PDT. I still haven’t rebooted yet.
      HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
      Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
      IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

      Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
      mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

      Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

      Comment


      • #4
        I needed to relink mine and then it worked fine.

        Comment


        • #5
          It seems to be back and I didn't relink. Still need to watch it. Now if there was an issue on HS side I wish they would tell us so we wouldn't keep worrying about it.
          HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
          Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
          IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

          Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
          mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

          Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

          Comment


          • #6
            It’s almost like we all need to create a watchdog for Alexa and HomeSeer. Thinking about this, it actually wouldn’t be all that difficult. Every minute or 5 minutes have HS speak to Alexa some command that would trigger or turn on/off something within HS. If it doesn’t work or doesn’t work within a specified time, then send out an email.

            Now, if support would accept these automated emails and do something constructive with them, then we could actually have a self-healing automation system. Rather than an automation system where it needs humans to babysit.

            it works pretty well. The challenge is that when the Alexa integration doesn’t work then people will stop using it. I have had a few customers bail on HS or smart home implementations because it wasn’t reliable.

            it would be interesting to know how many Alexa invoked commands do come through HS. Maybe in reality the failed ones are so small that it appears to be a bigger problem than it really is.

            welcome to technology.... And they want cars to drive themselves.....
            HomeSeer 2, HomeSeer 3, Allonis myServer, Amazon Alexa Dots, ELK M1G, ISY 994i, HomeKit, BlueIris, and 6 "4k" Cameras using NVR, and integration between all of these systems. Home Automation since 1980.

            Comment


            • #7
              I just want the Alexa Smart Home Interface fixed. It’s like no one is seriously working on it. It used to be fairly solid at least for basic commands but currently it’s crappy.

              One thing that’s never work reliable is getting device stats back to Alexa. If you use their interface it almost always reads that a light or switch is off even when it’s on. This is the case when you change a life from Alexa, manually or from HS3.

              although this isn’t an Alexa interface issue I really wish that HS would press Amazon to allow for a direct WiFi connection to the Echo so audio messages to it. That combined with Amazon Polly Speech services would allow for a fully off line TTS when combined with a caching front end like PollyC that’s currently available.
              HomeSeer Version: HS3 Standard Edition 3.0.0.531 | Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
              Linux version: Linux auto 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
              IP Address: 10.0.2.16 | Number of Devices: 417 | Number of Events: 667 | Available Threads: 399 | HSTouch Enabled: True

              Enabled Plug-Ins: AirplaySpeak: 3.0.0.13 | BLBackup: 2.0.61.0 | EasyTrigger: 3.0.0.65 | LiftMaster MyQ: 1.3.7006.42100
              mcsMQTT: 4.0.2.2 | PHLocation2: 3.0.0.53 | Pushover 3P: 0.0.0.45 | Z-Wave: 3.0.1.262

              Z-Net version: 1.0.23 using a HomeSeer SmartStick+: 6.04 (ZDK 6.81.3)

              Comment

              Working...
              X