search

HomeSeer / Plugin-SDK

Plugin development kit for the 4th major edition of the HomeSeer platform.
https://www.nuget.org/packages/HomeSeer-PluginSDK/
GNU Affero General Public License v3.0
20 stars 4 forks source link

ANDIF if being treated as Trigger and not as a Condition #338

Closed mcsSolutions closed 1 year ago

mcsSolutions commented 1 year ago

Reference Message Board https://forums.homeseer.com/forum/hs4-products/hs4-plugins/lighting-primary-technology-plug-ins-aa/hubitat-elevation-michael-mcsharry-aa/1444958-nuheat-thermostats/page2 post 25, 26

A Device Feature exists with control values of -1, -2, -3 and status values of 0, 1 and 2. An event is setup where this Feature is the subject of the ANDIF condition. The options to select the conditional state are the control values (-1, -2, or -3) and they should be the status values (0, 1 or 2).

In summary, an event that involves a Device Feature should present to the user Control Values for IF and Status Values for ANDIF.

spudwebb commented 1 year ago

Why would a trigger use Control values? I think both trigger (IF) and conditions (ANDIF) should use status values.

I saw in the forum thread that this user is using the legacy event page to edit this event, this is likely to be the problem, the legacy page does not handle very well HS4 devices. I just tested with the HS4 event page and it works as expected, but I see the problem in the legacy page.

mcsSolutions commented 1 year ago

I agree with you. It looks as if HS (Legacy) is only providing control values as part of the event setup. Feel free to respond to user in the thread as to what he should do.

From: spudwebb @.> Sent: Monday, February 6, 2023 1:25 PM To: HomeSeer/Plugin-SDK @.> Cc: mcsSolutions @.>; Author @.> Subject: Re: [HomeSeer/Plugin-SDK] ANDIF if being treated as Trigger and not as a Condition (Issue #338)

Why would a trigger use Control values? I think both trigger (IF) and conditions (ANDIF) should use status values.

I saw in the forum thread that this user is using the legacy event page to edit this event, this is likely to be the problem, the legacy page does not handle very well HS4 devices. I just tested with the HS4 event page and it works as expected, but I see the problem in the legacy page.

— Reply to this email directly, view it on GitHub https://github.com/HomeSeer/Plugin-SDK/issues/338#issuecomment-1419776915 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AALJP64PTJACAKZBIQKDWFTWWFTZ5ANCNFSM6AAAAAAUTBUZUA . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AALJP64GG6ZOUIY37YXO623WWFTZ5A5CNFSM6AAAAAAUTBUZUCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSUUAJZG.gif Message ID: @. @.> >