This plugin was updated by @vosmont to run under openLuup (and possibly UI7.)

@DesT recently asked for a slight addition to its functionality, so I'm adding this thread to discuss the changes.

Hi!

In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan

Hello,
Trying to convert my Reactor scripts to MSR. Couldn't get the import to work so gave up on that. Anyway, curious on how to work with the following example.

Have a motion sensor on my back porch. Very simple logic:
7fbcd69e-9f85-4b7f-8138-1267d4e4ba1a-image.png The Reactor activities are as follows:
34e715fd-c2f1-4b92-99ea-e2838fc5d3dc-image.png.

In MSR, how do you tie activities to sub conditions like I have with the last action in activities.
In this case I was to trigger BlueIris to trigger regardless of the time of day, but only want the light to come on at night. Do I need multiple Rule Sets?

Thanks,
Roger

I am running MSR 1.0.0-21200-16a604f and am seeing the message:

HomeAssistant on "hass" may be an unsupported version. The reported version (2021.7.3) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available.

@akbooer

What's the "logic" behind zway plugin about renaming ? Are you always renaming when starting openLuup ?

"akbooer: Master Branch: 2021 Release 7.25
Long-overdue roll-up of the last year's development updates!"

ak - congratulations on some great improvements coming to fruition. I can only hope you aren't running out of ideas! It's not easy.

I'd still like to see an "App Store" plugin download count but the invisible hands still need to be invoked by someone - whoever that may be!!

A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:

...I want to work in a more open and stable [Vera] environment...

...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?

1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modification

What we wouldn’t need is UPnP.

What have we (nearly) got already?

We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.

Is it worth the effort? Probably not. Will I pursue this quest? Yes.

openLuup was the result.

DE2056BF-E548-4611-972B-40276F00BFEB.jpeg

Having some trouble getting the Fibaro TRV device working with the ZWay bridge. The device works in the ZWay (Zwave.Me) Smart Home GUI, and creates a number of devices in OpenLuup, some of which appear to have the right variables in it. Changing the XML and JSON files makes no difference.

I also tried creating a separate child device for Parameter 67 (using the gui for the ZWay bridge, see below), and setting the XML/JSON types for that device (like I've havd to do for a few other devices). This results in a device that correctly displays the TRV setpoint, but chaning the setpoint in the OpenLuup gui does not result in anything being transmitted to/by ZWay.

20490 49-0 D_ComboDevice1.xml zNode #49-0
49-0-113-8-12-A
49-0-113-8-13-A
49-0-113-8-14-A
49-0-113-8-15-A
49-0-113-9-3-A
49-0-64
49-0-67-1
20491 49-1 D_ComboDevice1.xml zNode #49-1
49-1-113-8-12-A
49-1-113-8-13-A
49-1-113-8-14-A
49-1-113-8-15-A
49-1-113-9-3-A
49-1-64
25031 49-1-67-1 D_Heater1.xml Radiator Bedroom
20492 49-2 D_ComboDevice1.xml multi #49-2
49-2-113-8-10-A
49-2-113-8-11-A
25030 49-2-49-1 D_TemperatureSensor1.xml Radiator Bedroom

Curious to know if anyone play with Z-Uno to create some "z-wave sensors"

All,

Due to changes in the push notification system by Apple, the plugin to send push notifications to HomeWave will have to be updated. Please use the link below. This plugin works on both Vera and OpenLuup platforms.

Push messages will continue to work with the old and the new plugin. Once the server and the HomeWave app are updated, the old plugin will stop working

http://www.intvelt.com/files/HomeWavePush.zip

Hi

I just tried to add a connection for my Ezlo Atom, its added the Atom system in to the MSR Entities, but it has a "false" state and hasn't found my devices that are paired to the Atom.

ff7f286a-e987-4b2b-a56e-0b7a067aff6e-image.png

Also note that on the Atom controller there is no settings for:

offlineAnonymousAccess: true or false

offlineInsecureAccess: true or false

So this line in the reactor.yaml file won't work for Atom's.

set_anonymous_access: true

This was what I added to my reactor.yaml file.

- id: ezlo-atom enabled: true implementation: EzloController name: Ezlo Atom config: source: "wss://192.168.0.101:17000" # change the IP address serial: "70060304" # put your hub's serial here username: "myusername" # put your username here between quotes password: "mypassword" # and password # set_anonymous_access: true

Thanks

I am seeing errors like these in the log file:

<VeraController:NOTICE> Controller VeraController#vera-edge is now online. 2021-07-22T15:41:29.586Z <default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_device": { "device_number": 139, "device_type": "urn:schemas-upnp-org:device:RGBController:1", "parent_device": 0, "failed": false, "configured": --null--, "mapped_class": "rgbcontroller_plugin", "mapped_by": "*;device_type=urn:schemas-upnp-org:device:RGBController:1" }, "x_vera_svc_upnp_org_RGBController1": { }, "x_vera_svc_upnp_org_SwitchPower1": { }, "x_vera_svc_micasaverde_com_HaDevice1": { }, "x_vera_rgbcontroller_plugin": { "device_type": "FGRGBWM-441", "configured": true, "color": "#0000000000", "message": "" } } 2021-07-22T15:41:29.587Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-07-22T15:41:29.588Z <VeraController:CRIT> Error: Entity#vera>device_139:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_139:setPrimaryAttribute() can't set power_switch.state, not defined for entity

and

<default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_device": { "device_number": 75, "device_type": "urn:schemas-micasaverde-com:device:WindowCovering:1", "parent_device": 1, "failed": false, "configured": false, "mapped_class": "fibaro_cover_scenecontrol", "mapped_by": "*;device_type=urn:schemas-micasaverde-com:device:WindowCovering:1;pnp=/^(3222)$/" }, "x_vera_svc_upnp_org_SwitchPower1": { }, "x_vera_svc_upnp_org_Dimming1": { }, "x_vera_svc_upnp_org_WindowCovering1": { }, "x_vera_svc_micasaverde_com_Protection1": { }, "x_vera_svc_micasaverde_com_EnergyMetering1": { }, "x_vera_svc_micasaverde_com_HaDevice1": { }, "x_vera_svc_micasaverde_com_ZWaveDevice1": { }, "x_vera_svc_micasaverde_com_ZWaveNetwork1": { }, "x_vera_svc_micasaverde_com_GenericSensor1": { }, "x_vera_svc_micasaverde_com_Color1": { }, "x_vera_svc_micasaverde_com_SceneController1": { }, "cover": { "state": false }, "position": { "value": 0 }, "zwave_scene_controller": { "scene_activated": "0", "key_attribute": --null--, "scene_deactivated": --null--, "central_scene": --null-- }, "x_vera_scene_controller": { "last_scene_id": "26", "last_scene_time": "1626714753" } } 2021-07-22T15:41:28.925Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-07-22T15:41:28.926Z <VeraController:CRIT> Error: Entity#vera>device_75:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_75:setPrimaryAttribute() can't set power_switch.state, not defined for entity

What does it mean?

One is an RGBW Plugin device the other is a real Z-Wave device, a Fibaro Roller Shutter 2.

Thanks

Well, it's July 19th, and as previously advertised, Reactor (Multi-System, aka MSR) has been published at release 1.0.0.

Docker images are on DockerHub, and download package for bare-metal installs is available at https://reactor.toggledbits.com/download/

Those of you with access to the Mantis Bug Tracker for the project, please continue to use it, particularly if you stick with the "latest" docker image tag (which will continue to be updated periodically, as will the bare-metal tarball). Feel free to open issues there on behalf of other users who do not have accounts if it seems appropriate.

Not sure which category to use, but it's about external access..

I'm using Dataplicity to connect from the web to openluup, and i'd like a similar connection for MSR. Thats not something i would use on a phone, but from a laptop situated elsewhere in the world (faulty logic always appears when i'm far away from home!)

I could offcourse do the same procedure (described in the lower part of this ) for MSR, but if I colud put a link somewhere in Openluup that would take me there (like the openluup console link?) that would be easier?

Don't know if it will work to connect to a different port?

Any ideas?

It's worth noting this recent (?) GitHub change:

GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories

Guidance for changing the default branch name for GitHub repositories - GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories

This will have an impact on the AltAppStore which has previously assumed the default repository name of master. So when specifying releases, you should ensure that any new plugins explicitly reference the main branch if that's the one you're expecting to use.

Hi,

Am I correct in assuming that MSR cannot be installed on a pi running HASS.OS?

Thanks.

Having gotten the Ezlo controller to connect I see these device items
x_ezlo_item.learn_ir_code=0
x_ezlo_item.learn_rf_code=0
x_ezlo_item.send_ir_code=""
x_ezlo_item.send_rf_code=""

But they are not listed in the capabilities. It would be nice if to send Ir and Rf codes direct from MSR.

If possible couild you add this feature.

In Entities area, I selected the Ezlo controller. However when using the Capabilities drop down list, I can also see capabilities from the Vera firmware hubs as well, is that expected behaviour?

Thanks

entities.png