Reactor-Editor / Reactor-ui-Status Errors

[rafale77]

Opening a thread here for suggestions and discussions on future integrations to MSR.

I'll jump in and give my wish list:

Homekit
Z-way through weksocket
openLuup specific MQTT

[therealdb]

I think something like ha-bridge but native could be huge as well. I could definitely help here.

[LibraSun]

Well, if we're all piling on the BUILD-IT-ONCE-SO-ALL-MAY-PROFIT bandwagon, then allow me to toss another API into the ring:

ecobee thermostats

And if this ship has any fuel left in it after the first orbit, why not:

IFTTT (or at least APILIO) integration (LOL!)

[CatmanV2]

HA bridge works wonderfully, but yes a native implementation would be brill

C

[toggledbits]

These are all great ideas. What I'm working on at the moment changes the entity model a bit conceptually, not in implementation, and I want to get that in your collective hands and stabilized first, in case it breeds any necessary changes in the API. But, I'm happy to say, the implementation was pretty quick on my end -- while it has taken me most of the last two days, yesterday was really a short day (family events, hence no build last night) and I knocked out the changes for Hubitat and Hass, and today (about three hours so far) I've completed the Vera changes.

The gist is this: the updated controllers will be exposing every attribute and every action they can in a standard, stable interface at the rule and reaction level. The "lingua Franca" capabilities (power_switch, etc.) will still and always be present for use, and will represent their own stable interface across platforms, but it will no longer be strictly necessary for new and unrecognized devices to be mapped before use.

This is going to "fluff up" the list of attributes and actions in the UI, particularly on Vera. It's actually pretty tidy and nice on Hass and Hubitat. All of this will be in today's build, hopefully, if I can get through my testing. If there's no build today, this is why, as it's pretty much the only thing I've worked on since yesterday (and I have more family events this afternoon).

So, who's volunteering to build what? JavaScript required...

[LibraSun]

I volunteer to:

1. Hammer on all things msr/vera as released.
2. Proofread any and all documentation.
3. Continue filing bug reports with full data.
4. Periodically send Patrick some beer money! ◄– as should everyone who respects his time and energy

[CatmanV2]

In addition to 4 can I volunteer to stand around, sucking my teeth?

C

[Matohl]

@librasun said in System integration roadmap:

Periodically send Patrick some beer money! ◄– as should everyone who respects his time and energy

Done

[rafale77]

From what I recall he likes Scotch better...

[therealdb]

@toggledbits I’m more than happy to do mqtt and ha-bridge, to start. I’ve some open source time to invest (because I love to give back) and I’ll be more than happy to help.

[PerH]

I'd like to try a Domoticz integration, but spring usually brings more outdoor projects.. some day!

[cokeman]

I'd love to see a docker addon for HA...

[cw-kid]

I'd like for the Home Remote dashboard app to support the MSR API. So I could add an MSR device object in to the Home Remote Designer and then see all my Global Reactions (Scenes) that are in MSR etc. I could then easily create dashboard "Scene" tiles to run these MSR Global Reactions from my dashboard interface.

But obviously that would be down to the Home Remote developer to add native support for it.

I was able to add a "HTTP Switch" in to the Home Remote Designer and send one HTTP command to MSR when the switch was turned ON in the dashboard app and send another HTTP command when the switch was turned OFF etc.

Using commands like:

http://MSR-IP:8111/api/v1/reaction/re-klkn8rxw/run

It worked but I can see it being very time consuming creating these types of HTTP switches in the Home Remote dashboard, as its basically a plugin script in Home Remote and not the easiest thing to scale up and just create a load of new switches that can run various MSR Global Reactions.

[cw-kid]

@toggledbits said in System integration roadmap:

The gist is this: the updated controllers will be exposing every attribute and every action they can in a standard, stable interface at the rule and reaction level. The "lingua Franca" capabilities (power_switch, etc.) will still and always be present for use, and will represent their own stable interface across platforms, but it will no longer be strictly necessary for new and unrecognized devices to be mapped before use.
This is going to "fluff up" the list of attributes and actions in the UI, particularly on Vera

Please can you explain this in more simple terms for us dummies.

Does this mean in MSR everything that Vera can see about a device, will now be seen and accessible in the MSR rules also?

All that devices various ServiceID's and variables ?

Thanks

[toggledbits]

@cw-kid said in System integration roadmap:

Does this mean in MSR everything that Vera can see about a device, will now be seen and accessible in the MSR rules also?

Yes. In that respect, same as Reactor for Vera. Not user-friendly, but complete. The system-defined capabilities will still be there, like power_switch and dimming. You will able to use either.

[cw-kid]

OK well that's a good thing then. Will make it like PLEG also in that respect, where you can see and choose all ServiceID's and variables.

[LibraSun]

I'd love to see native Google Calendar integration (in much the same way that GCal 3 plug-in currently offers I/O to a designated Google Calendar).

Fun way to track past events and preset future triggers dynamically.

[Matteburk]

Reolink Cameras with NVR ... would be lovely to trigger stuff with....

[LibraSun]

Heck, if we're heading in that direction, then I toss RING Cameras and Doorbells into the hat. I realize that's a tall order from every perspective.

[cw-kid]

Do those camera systems not have their own HTTP API ?

I have Hikvision cameras and they have a HTTP API for controlling aspects of the cameras. So Vera and MSR or anything else can control them via HTTP requests.

Turning on / off motion detection for example or starting a manual recording.