Announcement

Collapse
No announcement yet.

Alexa cannot find any devices

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

  • Alexa cannot find any devices

    Hi, This used to work but stopped so I removed all the devices one by one on my iPhone Alexa App and disabled the skill

    Then re-enabled the skill expecting Alexa to find all my devices...

    However, it finds nothing.

    What am I doing wrong (other than expecting it to work)?

  • #2


    Try disabling voice control for all devices, this can be done by using the check box and drop-down list directly under the words Device List, as seen in the screenshot.

    Once you use the check box to select all devices, you will want to use the drop down menu to select Disable Voice. Then, you will want to go through your device list and click the checkboxes for the devices you would like to control. There are two rules about enabling voice control:

    The device must have controls on the right hand side
    The device must be on/off, dimmable, or thermostat controls.


    For the device above, you would only want to enable voice control for the HomeSeer HS-WD100+ Switch Multilevel child device.

    Once all appropriate devices have been selected, you will want to select Enable Voice from the drop down menu, then unlink and relink Alexa with HomeSeer.
    -Rupp
    sigpic

    Comment


    • #3
      I will try tomorrow and let you know. Thanks!

      Comment


      • #4
        SOLVED
        Yes, this solved it for me
        In HomeSeer - turning off Voice for all devices
        In HomeSeer - turn on Voice only for control devices I choose
        In Alexa app - remove the HomeSeer skill
        In Alexa app - add the HomeSeer skill back in then scan.

        The previously voice enabled devices are now seen by Alexa and can be set up in the Alexa app.

        Rupp - Thanks!

        Comment


        • #5
          This is nuts! I just tried this and no joy. I’ll try it again but I’m not hopeful.

          This is what I think is happening. There has got to be some data that MyHS uses to know if it should send device data during an add. I think this data isn’t getting cleared out when a device has its voice enable cleared. We need a way for us to force MyHS to forgot all stored Alexa information and start over.

          PLEASE HOMESEER! Join these conversations and help us figure this out. Heck, you have my permission to check my database on MyHS to see what blocking the add devices.
          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
            I've been going back and forth with Matt on this issue. What was found is that once one gets into the state where is won't pickup devices you have to get forget all devices on Alexa and remove the voice flag on all devices you have to do the same thing for events. If forget just one event nothing will be found. I don't know if Matt agrees with me but I still say they have a bug in their code that needs to be found.

            They need to add something that will clear all of the flags that are used but allow the actual device voice flags on devices and events to be ignored so it's quicker to fix the issue.

            I told Matt that we need a way to easily find events that have the voice and other option flag that are set much the same way you can find what events are using a given device.

            My suggestion for everyone is to make a Event group that contains all of your voice triggered events. I'm not saying move the actual events there just a simple two line event that set to manual trigger and a run event which points to your original event that had a voice flag. This will make it MUCH easier to find and fix voice since you only have to look in one place.
            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


            • #7
              Many thanks for the info!

              Comment


              • #8
                Well, there is still an issue. I added to Events so they can be imported to Alexa. I entered the Voice string and checked the voice inside of the event. I did a device discovery and nothing got found. What I'm worried about now is when I get ready to add another WD200 dimmer it's not going to be found. There is still something wrong. We'll report back once I finish testing this.
                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


                • #9
                  Here is the latest update on adding events as devices too Alexa.

                  I turned off event voice checkbox and I can still add devices. However I 'm still not been able to add events as voice devices to Alexa. This used to be able to add them but no longer can.

                  One thing to note however Alexa/HomeSeer will NOT update device names as far as I can tell. I find the only safe way when making changing to existing devices is to forget the device you've changed than rename them then add them back in.

                  I'll report this to Matt tonight so he can check it out tomorrow.

                  In the meantime I'll keep looking after I watch todays NASCAR Cup Race
                  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


                  • #10
                    I have 72 devices and 30 events (scenes/Routines) discovered and working with echo for several months. Added 2 devices couple days ago... no problem. Created 3 new events yesterday (properly voice enabled) and cannot achieve discovery after multiple attempts. Reported to support today.

                    Comment


                    • #11
                      Originally posted by Jayhawk View Post
                      I have 72 devices and 30 events (scenes/Routines) discovered and working with echo for several months. Added 2 devices couple days ago... no problem. Created 3 new events yesterday (properly voice enabled) and cannot achieve discovery after multiple attempts. Reported to support today.
                      Yep, something has changed. As I said I had working events set with Alexa but was forced to remove them ignorer to get devices working again. Now Events won't connect again.

                      Anyway, back to playing with my system.
                      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


                      • #12
                        Same issues...tracking

                        Comment


                        • #13
                          My 4 additional events finally were discovered by Alexa yesterday; 12 days after adding them to HS3... I did not do discovery... they just appeared. I had reported the problem to HS support... there only response was to have me update my HS3 version which I did (10 days ago... no joy). I did go through all my devices and unchecked voice control for all that did not need it... probably 60 or so devices... 3 days ago. I had read in some posts that Amazon may have a limit on number of devices, events, or both(?). I did not remove/recreate any of my 30 routines from Alexa or change them in any way... they have always worked OK.

                          So I don't know if it was what I did, or if support did something, or if magic takes a lot of patience.

                          Comment


                          • #14
                            I have been trying for 2 weeks, about 73 devices........ yesterday they all showed up and are working perfectly

                            Comment


                            • #15
                              No bueno for me yet

                              Sent from my SM-T813 using Tapatalk

                              Comment

                              Working...
                              X