DynamicGroupController and attributes

[Pabla]

Hey Patrick, similar to R4V it would be nice if we could set the max amount of time a condition pulses. Currently in MSR you can only set it to pulse once or repeat continually until the condition goes false.

I currently have a rule that pings dead devices and occasionally the dead device needs a few pings for it to come back alive but I don't want it to keep pinging forever if the device is actually not functioning.

[gwp1]

@pabla I'm trying to find it in my rules but I'd swear there was either a count or time cap you could apply to pulse. In my case it was announcing the washing machine was done and clothes needed to be moved to the dryer and it gave up after 10x.

[toggledbits]

Yup, it was there. Somehow the edit fields didn't make the leap from Bootstrap 4 to Bootstrap 5, so that's now PR 0000331, and will be fixed in a build later today. The error only affects editing. Existing conditions with count limits will work, you just can't edit them.

[Pabla]

@toggledbits I felt the same way @gwp1 did too, I almost swore it existed at one point lol! Will keep an eye out for the new release

[gwp1]

@pabla You can always count on @toggledbits to TEST your sanity and then CONFIRM it

I sometimes wonder if he does these things on purpose to see what functionality we're REALLY using lol

[Pabla]

@gwp1 On the bright side it forces me to double check then triple check then check the manual before posting. Saves a lot of false alarms which I am guilty of doing a lot

[toggledbits]

@gwp1 said in Add Ability to Limit Amount of Time a Condition Pulses:

You can always count on @toggledbits to TEST your sanity and then CONFIRM it

At least you have it to test.

That's an embarrassing miss, but honestly, it's hard to test GUI stuff, because it defies automation, at least, without a lot of really complex (and expensive) software. Sometimes all you can do is bang away at it, and sometimes, you won't see something you should...

[Pabla]

@toggledbits Hmm unless I did something wrong, none of the new changes/features are showing up. My build shows as 22256 on the top right but still don't see the ability to limit the amount of times a condition can pulse. Neither can I see any metedata info for my entities either.

Retried the whole upgrade process and no change. Hard refreshed too.

[SweetGenius]

@pabla Did you get any warnings about newly created entities as listed in the release notes? I did not receive any alerts and I also can't see the ability to limit the amount of times a condition can pulse.
v latest-22256-65e94b36
Synology Docker

[Pabla]

@sweetgenius nope didn't get any alerts either

[toggledbits]

Sigh. Sorry guys, forgot to update the build tag. Pull the new package or docker image, same build number (22256).

[SweetGenius]

This post is deleted!

[toggledbits]

This post is deleted!

[Pabla]

Upgraded successfully and the limit for Pulse is back!