No announcement yet.

Two ways to define EVL actions ?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Two ways to define EVL actions ?

    I just realized (sorry if I'm late to the party) that there are 2 ways to define an EVL action in an event:
    1- Control device / Select EnvisaLink element (ex: partition 1) / select State (ex: Arm away)
    2- EnvisaLink action / Action type (ex: Partition arm - away) / Select partition (ex: partition 1)

    I suspect that both ways will result in the same end result for the event.

    EXCEPT that if you select a plugin action, example 2 above, as opposed to Control device for an event and if you then copy the event, the event copy will not reproduce the parameters ('Partition arm - away' and 'partition 1').

    I found this behavior to be true for another plugin (Nathan's Insteon thermostat plugin)

    No big thing, but it shouldn't be. The fact that both plugins exhibit the same behavior makes me think this could be outside of the plugin's control, maybe an HS bug?

    Spud - any thoughts?

    P.S. I've left a duplicate post in Nathan's forum
    Attached Files

  • #2
    Claude asked me the same question and I believe I've fixed this with my Insteon Thermostat plugin - at least once is released for the updater. Brief description is here:
    HS (PRO)
    Hardware: Napco GEM-P9600 | VenstarT1800 w/Insteon 2441V adapter | Insteon PLM
    Plugins HS3: Napco Gemini (mine) | Insteon Thermostat (mine) | Insteon Plug-in (mnsandler) | HSTouch Server (HST)
    Platform: Windows 10 Pro 64bit, core2 duo 2.0Ghz, 4GB memory


    • #3
      I have fixed the problem with event Copy in version of the plugin