Announcement

Collapse
No announcement yet.

Feature Requests

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by logman View Post
    the plugin took ownership of a virtual device that had not been associated to your plugin by me. The "My Devices" under the plugin config tab does not show any devices associated with the plugin
    Attached is an app which will remove the SmartDevice plugin interface from the devices. Unzip the files in a folder and run, first time it shows the list of your devices with the interface. Second time you run it - just to verify - the interface should be removed.

    Attached Files

    Comment


    • #17
      Originally posted by logman View Post
      If a device is "interfaced" with the plugin, JSON API calls to the device no longer work, whether the plugin is enabled or not
      Can you please give me some example how to test it, so I can debug the problem. Again, should be really a separate thread....

      Comment


      • #18
        Originally posted by logman View Post
        The device is effectively orphaned unless I can figure out how to force release the AK interface
        If the device doesn't have any timer/trigger/linked device enabled - it should release interface. You can enable logging (for the particular device) - then when you disable/enable plugin (or restart HomeSeer) - you can see in the log what's going on. If you want - send me the log, I can check.

        Comment


        • #19
          I'm working on the new version. Many fixes and improvements...

          Major change - Creating configuration matrix for Countdown Timer for different "Linked Device" States:

          Click image for larger version  Name:	CntdwnMatrix.PNG Views:	1 Size:	49.5 KB ID:	1300681

          Comment


          • #20
            Possibility to add more than one trigger state of each added device within the trigger.

            for example

            If I have add the trigger state “Nighttime” of the virtual device “Home”, I can’t add also the trigger state “Away” for that device.
            (of course with the group Logic set to “Any”)
            I must now add a complete new trigger

            Comment


            • #21
              Originally posted by Paul vdK View Post
              Possibility to add more than one trigger state of each added device within the trigger.

              for example

              If I have add the trigger state “Nighttime” of the virtual device “Home”, I can’t add also the trigger state “Away” for that device.
              (of course with the group Logic set to “Any”)
              I must now add a complete new trigger
              Sure. I'm working on ver.2 - will add.

              Comment


              • #22
                Hi,

                I'm trying to use your plug-in to set a status for a group of lights, i.e. if any bedroom light is on, turn ON virtual device, likewise, if ALL bedroom light are OFF, turn OFF the virtual device. Additionally, I'm using that virtual device so that you can actually turn ON or turn OFF all lights in that particular area.

                The problem is I need to differentiate between your plug-in changing the status of the virtual device, versus someone actually clicking the virtual device. I know there are all sorts of things I could do outside of your plug-in to be able to do this with additional variables and adding more complex HS events. I'm actually already doing this, but simplicity is what I'm after...and I'm almost there with your plug-in.

                By using the 'Add to Status' flag, I can tell if the status changed via your plug-in because the device string is also changed. This works great for the ON triggering event, i.e. if ANY device in the group turns ON, as the device string will also contains ' (trigger device)'. This way I know it was triggered because an individual light was turned on. But for the OFF event, I tests for ALL lights OFF. And your 'Add to Status' logic is different. The device status is properly triggered, but it also triggers my event as if the virtual device was clicked OFF.

                I was trying to figure out if I could use your 'Add to Status' logic for ALL events in some way, but what I discovered is that I can't figure out how to make it work at all. Meaning if something was preventing the trigger, it was not updating the virtual device string. In any case, I would prefer the functionality more similar to the 'ANY' trigger. Meaning, the device string will contain the name of last device that caused the event to trigger. If that's not possible, and you would still like to use the original functionality, can you add something like '(Null)' to show that no devices that were not satisfying the conditions, i.e. the event was triggered.

                In any case, really do like your plug-in. Really fantastic work.

                Thanks

                Richard

                Comment


                • #23
                  Originally posted by ruderthanyou View Post
                  I was trying to figure out if I could use your 'Add to Status' logic for ALL events in some way, but what I discovered is that I can't figure out how to make it work at all. Meaning if something was preventing the trigger, it was not updating the virtual device string. In any case, I would prefer the functionality more similar to the 'ANY' trigger. Meaning, the device string will contain the name of last device that caused the event to trigger. If that's not possible, and you would still like to use the original functionality, can you add something like '(Null)' to show that no devices that were not satisfying the conditions, i.e. the event was triggered.
                  Hi Richard, I had same problem myself - how to use 'Add to Status' to "ALL" logic - because it kind of doesn't make sense. One (probably the one) option I consider - adding names of devices which prevent from trigger.

                  Any input is welcome.

                  As I'm working on Ver 2 - which is a big change (internally, to make it more flexible) - it's good time for requests!

                  Comment


                  • #24
                    Originally posted by ruderthanyou View Post
                    the device string will contain the name of last device that caused the event to trigger
                    Probably it's a best idea

                    Comment

                    Working...
                    X