Have "for" in the current-state node work for <=, >=, ...

[Hadatko]

Describe the bug

It looks like for half of IF conditions for current state node cannot be set FOR value for following value in timeout

To Reproduce

Edit any current state node. Try is, is not, in, not in and compare with <=, >=, ...

Expected behavior

FOR option should be available for all options or none of them.

Screenshots

Example Flow

No response

Environment Information

Version: latest one

Home Assistant version: latest one
Companion version:

Node-RED version: latest one
Docker: yes
Add-on: no

Node.js version:
OS:

Additional context

No response

[zachowj]

Because it gets how long it's been in a given state based on the last changed timestamp. With <, >, ... the state value could be true on multiple states but the last timestamp would keep changing and the beginning time is unknown.

Could this be changed to work with <, >, yes.

[Hadatko]

Oh i see. But you closed it to early :D Are you willing to implement support for this?

[Hadatko]

For example node event-state supports all cases.

[zachowj]

Sure it could be implemented. It currently isn't on my list but it would be a welcomed addition.

Moving this to feature requests.

[Hadatko]

Thank you very much. Also for such quick response.

[ciotorcristian]

Any updates on this? It would be a welcomed feature to have this option.