Announcement

Collapse
No announcement yet.

Problem with Events (Scenes)

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

    #16
    Here is how I have my Fan setup.

    For my Graphics Settings you'll want to notice something. If you don't want something to show then make sure you give it a row number and a column of "0" with a span of "0". This blocks the display.





    Here are the Graphics I use.



    And lastly this is the event I use to make sure that when you change a speed the speed will be set to the "standard" value for the device. That way if you manually advance the speed or tell Alexa the speed is say 20 it will be reset back to the correct speed setting so that Low, Med and High will be displayed. I also set it up so that when you say Alexa, set fan to on it goes to the last setting rather than High. To go to high you have to set the value to something over 66.

    I do make use of Easytrigger although you can do it without it, I think.

    HomeSeer Version: HS3 Standard Edition 3.0.0.548
    Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
    Number of Devices: 484 | Number of Events: 776

    Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
    3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
    4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
    3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

    Z-Net version: 1.0.23 for Inclusion Nodes
    SmartStick+: 6.04 (ZDK 6.81.3) on Server

    Comment


      #17
      I don't really think it is HS fault, but i wish you could just tell Alexa to set the fan to low/medium/high and have it work. Kind of frustrating to have to tell it to go to a value.

      Haven't played around with it much but I will try some of the suggestions.

      Comment


        #18
        Originally posted by sonypoolplr View Post
        I don't really think it is HS fault, but i wish you could just tell Alexa to set the fan to low/medium/high and have it work. Kind of frustrating to have to tell it to go to a value.

        Haven't played around with it much but I will try some of the suggestions.
        Until Alexa can handle setting fan speeds using the command "Alexa, Set fan to medium" I run both the Homeseer skill AND smart home processes. I've also got the fan on command set to issue "Last" and not "On" so when telling the fan to turn on it goes to the last speed used.

        So this way we use the native functions for on and off and the homeseer skill for speed changes. UPDATE!!!! Alexa does understand the words "Low" and "High" but it doesn't understand medium. It translates "low" to a value of 11 and high a value of 99. Since I have events that monitor the speed settings and reset them to the stand value of 33, 66 and 99 my displays always show the correct "Low", "Medium" and "High".

        Example:
        "Alexa, turn on fan"
        "Alexa, set fan to low" <== This does work
        "Alexa, {ask, tell} homeseer to set fan to low"
        "Alexa, {ask, tell} homeseer to set fan to medium"
        "Alexa, {ask, tell} homeseer to set fan to high"
        "Alexa, set fan to high" <== This does work kinda
        "Alexa, turn off fan"

        Sure it still take extra words but it more natural than giving a number.

        When HS releases their own fan controller there will be 4 speeds and I have no idea what the 4 speed will be called.

        As far as it bing an Alexa issue and not a HS issue I'm trying to figure that out. I though that I've seen other systems using Alexa being able to set fan speeds so I'm checking the Alexa documentation to see how they did it, however the documentation is not all that easy to follow.
        Last edited by Timon; May 20, 2018, 08:23 AM. Reason: Additional information
        HomeSeer Version: HS3 Standard Edition 3.0.0.548
        Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
        Number of Devices: 484 | Number of Events: 776

        Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
        3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
        4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
        3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

        Z-Net version: 1.0.23 for Inclusion Nodes
        SmartStick+: 6.04 (ZDK 6.81.3) on Server

        Comment


          #19
          I think I just found a bug in the handling of Alexa devices and scenes.

          It seems that even if you turn off "Voice Command" on a device Alexa can still control that device even after rescanning.

          I understand that Alexa doesn't delete devices or scenes, I consider that a serious bug which only Amazon can fix, but at least HS should honor the fact that the device is no longer available for voice control and error out voice requests for that device. The same thing is happening with scene so it's a common issue.

          I believe that the solutions for this may be to just to destroy the linkage token for the device or scene but I'll leave that for HS to figure out.
          HomeSeer Version: HS3 Standard Edition 3.0.0.548
          Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
          Number of Devices: 484 | Number of Events: 776

          Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
          3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
          4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
          3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

          Z-Net version: 1.0.23 for Inclusion Nodes
          SmartStick+: 6.04 (ZDK 6.81.3) on Server

          Comment

          Working...
          X