Announcement

Collapse
No announcement yet.

Disable Voice checkbox by default

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

  • Disable Voice checkbox by default

    It seems that because Google & Alexa won't let you control security devices via their APIs, HS processing of available devices breaks down if presented with a security device that has "Enable Voice" checked.

    Since there's really no point in controlling my glass break sensors, doors, windows or motion sensors by voice would you consider making sure you turn off that bit when adding a new zone device? Probably makes sense for any of the devices created by a security plugin in general...

  • #2
    its really strange. some my devices have the Voice checkbox checked and some don't. i wonder if different versions of HS3 change that checkbox when the device is created

    i'll make a note to uncheck the box for these devices.
    Mark

    HS3 Pro 3.0.0.534
    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
    Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

    Comment


    • #3
      Yes the most recent releases of HS3 automatically check this as most users didn't know that it was required to be used with Amazon and Google devices.
      -Rupp
      sigpic

      Comment


      • #4
        Originally posted by shill View Post
        It seems that because Google & Alexa won't let you control security devices via their APIs, HS processing of available devices breaks down if presented with a security device that has "Enable Voice" checked.

        Since there's really no point in controlling my glass break sensors, doors, windows or motion sensors by voice would you consider making sure you turn off that bit when adding a new zone device? Probably makes sense for any of the devices created by a security plugin in general...
        While I stand by the idea of it being good for security devices to have this off by default, it seems perhaps there was another issue causing the hs/Google integration to break and it was a coincidence that a couple of us found that disabling this checkbox fixed it (when instead it was lucky timing).

        Comment

        Working...
        X