[MSR] Feature request: For Each action on arrays/groups

[Matteburk]

MSR is a bit different then the Reactor.

Trigger :
A changes
Constraints :
A is true
Reaction:
Close window shade

How do i " Else if A is false ! then Open shades
??

In old reactor it was easy but cant get it with msr....

/Mattias

[Matohl]

This post is deleted!

[LibraSun]

I honestly thought that's what the "Reset Reaction" section is for. Of course, I haven't actually used MSR yet because I'm waiting for a clear path of importing my old Reactors from Vera into the Docker-ized version of MSR that I've installed, and that process isn't officially viable yet.

But have you tried using "Reset Reaction" to accomplish what you're after in MSR?

[toggledbits]

Set and Reset are to MSR what the "is TRUE" and "is FALSE" activities are to Reactor for Vera root groups.

[Matohl]

@librasun I have actually moved most of my Reactor rules (3/4) by making new ones MSR were I could iron out some of the conceptual mistakes I made when I stated to use Reactor in Vera. MSR is rather stable now but I understand that you want to wait for how to import. My next step is to integrate it with InfluxdB.

[LibraSun]

It's really just me being lazy. Fact is, even my "simple" rules in Reactor tended to be quite involved (I love long Expressions, for example), so rather than risk a typo, I've been holding off waiting for the Backup/Restore process to work in the Docker environment. Fully acknowledging that this is at least a couple steps later in MSR's roadmap.

As for InfluxDB, which I presume you'll be using for variable persistence(?) among heterogeneous endpoints... isn't that something you could effectively achieve with MSR itself? I can't help wondering if MSR (as-is or with some extra, purpose-built feature added) could reasonable serve as a sort of IFTTT / Apilio / DB handler. After all, it's always-on and capable of managing variables already.

Or am I talking nonsense?

[Matohl]

I want my sensors to be stored in a database for further analysis/joy (Temp, Watts what ever). I guess you are right that it could be done with some additional functionality in MSR but I think @toggledbits bits in some post that it is not in the roadmap. Thinking ...

[LibraSun]

Patrick is wise not to reinvent the wheel when he doesn't have to.

[toggledbits]

@matohl said in How do I "else":

My next step is to integrate it with InfluxdB.

This is an area about which I know relatively little, but have a great deal of interest. MSR has both a WebSocket and HTTP API. It is very much on the roadmap to integrate with InfluxDB and Grafana, but I do not yet have in mind how I will do that. I need to pull those packages and start playing with them to get a feel for how they work, and then I'll understand better how to use them with MSR. I would, however, like it to be as simple as a basic configuration addition to say "these are here and this is what you need to know about them", and have them usable if present standalone (on either the local system or a remote), or as an add-on package that is integrated seamlessly within the UI.

But very much on the roadmap. The utility of this is not at all lost on me, and it's a high priority.

[Matohl]

Working on to get the values into, InfluxDB, not there yet. Will continue tomorrow.