4.2.18.3: Action conditional not working for following conditions:

[phsubscribenl]

I've been testing action conditions.

Conditions that consistently work:
-------------------------------------------
-Device
-Date
-Moon Phase
-Group

Here is a list of conditions I've found do not work. The Easy Trigger failures result in the events window crashing, all others simply will not save.
-------------------------------------------
-Time
-Counter
-Timer
-Easy Trigger Conditions

I just noticed my "System Profile" shows "In Virtual Machine=Yes". I have HS running as a service on a laptop.
Why does it show in Virtual Machine?

[John245]

phsubscribenlI suggest to remove the sensitive info from your message and post the message board system profile.

[claude]

...

I just noticed my "System Profile" shows "In Virtual Machine=Yes". I have HS running as a service on a laptop.
Why does it show in Virtual Machine?

I have Windows 10 Hyper-V activated but my profile still shows VM = No. Do you have by any chance some virtualization activated at the BIOS level ?

[pseudocode]

EasyTrigger "any device in group" works OK for action conditions.

[macromark]

phsubscribenl Suggest you post a little more detail about what you're trying to do... For example, you're saying that these conditions do not work:

-Time
-Counter
-Timer

Can you post a screen shot of the events that are using these so we can see how you're setting them up?

Also... I removed your system profile as it includes your admin email address and WAN / LAN IP addresses. Those should be posted to a public forum for security reasons.

[andyf]

macromark


spud has pretty much confirmed this new version has crippled a lot of EZTrigger.

https://forums.homeseer.com/forum/ul...ng#post1598046

[spud]

macromark


spud has pretty much confirmed this new version has crippled a lot of EZTrigger.

https://forums.homeseer.com/forum/ul...ng#post1598046

I wouldn't say "a lot", it's only 8 specific conditions and only if used in conditional actions. They still work fine if you use them as main conditions as before, and the equivalent triggers still work fine too.

[andyf]

I apologize if there was too much drama in that post. But really, aren't we all converting to mostly conditional actions now. I have an awful lot of "device was changed or set" triggers now. 😁😁. A lot of group triggers too, so invaluable.

[phsubscribenl]

Macromark, thanks for cleaning up my post, what a newbie mistake!

As mentioned in my original post, my earlier testing with "Easy Trigger" Condition cause the GUI to close. However as went to create these screen shots, it accepted the EasyTrigger edits. See 2nd screen shot.

The Time condition shown here are as follows in that any custom changes (edit hours) returns to default value and no saving occurs. Counter and Timer conditions behave the same.

[phsubscribenl]

claude,

I do have VT Emulation enabled in BIOS as I sometimes run VMWare Workstation on the computer. But HS is running native from the host.

[ecetron]

I vaguely remember seeing something like this in the first version that came out -- I re-tried it and it took just fine and saved the values. I just chalked to up to operator error with the new conditionals. Maybe it wasn't...

[macromark]

Macromark, thanks for cleaning up my post, what a newbie mistake!

As mentioned in my original post, my earlier testing with "Easy Trigger" Condition cause the GUI to close. However as went to create these screen shots, it accepted the EasyTrigger edits. See 2nd screen shot.

The Time condition shown here are as follows in that any custom changes (edit hours) returns to default value and no saving occurs. Counter and Timer conditions behave the same.

OK, tried the same condition as you:



When I save it, I get this:



So, this appears to be working OK. I'm not using Easy Trigger so not sure if that might be creating the issue? If your issues all involve Easy Trigger, post a note to the Easy Trigger forum to see if Chris ("Spud") can help you there.

[phsubscribenl]

I tried again this morning to "save" the conditional action using "Time" and failed. I restarted HS and was then able to save. HS had been up for slightly longer than 3 days. Note: I'm running HS as a service.

The Easy Trigger failure is recognized as a separate failure unrelated to the Time, Counter,Timer issues.

[macromark]

... I restarted HS and was then able to save...

So it's working now?

[randy]

So it's working now?

The only thing I have found is the specific Easy Trigger Conditions Spud pointed out. I have not seen any problems with native Conditions.