Been using PLEG for about 8 or 9 years, I had 100 Conditions / Actions in PLEG, these are now all disabled and I've recreated them on MSR.

Still learning MSR and how to do somethings but everything I was doing in PLEG was fairly easy to convert over to MSR once I found my feet a bit and got going.

Thanks to everyone who answered any of my questions along the way when I got stuck.

I have some Vera scenes I'd like to also convert to MSR, so not quite done yet.

@toggledbits said in How to auto start on Rpi reboot ?:

rpi-install.sh

This is the reactor.service file it created:

# This file allows you to run your Reactor installation under systemd,
# so it can be started at boot. Copy this file (as root or under sudo)
# to /etc/systemd/system, and then run "systemctl daemon-reload". You
# can then able Reactor to start at boot "systemctl enable reactor".
# The usual systemctl subcommands can also be used to start, stop, and
# restart reactor at will (e.g. "systemctl restart reactor").

[Unit]
Description=Multi System Reactor
After=network.target

[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi/Documents/reactor
ExecStart=/usr/bin/node app -p
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

I followed the rest of the instructions and I could see a reactor.pid file had been created and reactor was running again.

I then rebooted my Pi and after it rebooted MSR is running again.

So everything appears to have worked OK.

Thanks

P.S. I really like the new Entity Attribute picker and search dialogue box.

Would of saved me a lot of time if we had it earlier but its definitely a big improvement.

I've tried the Vera Multi-String plugin, it looks just like the type of plugin I was needing and looking for.

You can have up to five variables on a device.

You can then have your rule in MSR send the data to each variable etc.

The Multi-String plugin devices data is also outputted in the Vera SDATA stream so these device will also work with the Home Remote dashboard app.

{ "name": "Covid-19 Stats", "altid": "", "id": 133, "category": 0, "subcategory": -1, "room": 0, "parent": 0, "variablename1": "Confirmed", "variable1": "4329180", "variablename2": "Recovered", "variable2": "3787312", "variablename3": "Critical", "variable3": "615", "variablename4": "Deaths", "variable4": "126573", "variablename5": "", "variable5": "", "options": "", "configured": "0" },

So I recommend using the Multi-String plugin rather than trying to create your own modified Generic IO devices as I was doing.

Gees, I know a lot of those names, didn't know Pabla and Crille were banned and I certainly didn't know ElCid was banned.

Well I always speak my mind and if something doesn't work I'll say it doesn't.

AltHue Plugin for Vera:

CONFIRMED AS WORKING - HUE SCENES

The ServiceID's are now exposed in an Entity Action in an MSR rule or Global Reaction.

You need to select the main AltHue device in your Entity Action, then select hue_scene from this list.

Go in to the AltHue main device in Vera UI7 web GUI and go in to the "Hue Scenes" area and find the scene in the list that you want to start in your MSR rule or Global Reaction.

Copy its ID number.

Back in MSR edit the Entity Action and paste in the ID number.

When I ran my MSR Global Reaction, my hue scene is started and my lights are now in Arctic Aurora.

CONFIRMED AS WORKING - EFFECT COLORLOOP

Next I created another Global Reaction and tried starting the Effect ColorLoop

Choose the set_effect from the drop down list.

The child ID is the AltHue child device aka the light that you want the colorloop to be on.

and enter "colorloop" in the Effect field.

When you run the Reaction, If the light is already turned ON the colorloop will start.

However if the light is turned off nothing will happen, so I added an action to turn on the light first then run the colorloop effect, which is working.

@catmanv2 said in Need help backing up Raspberry Pi:

Have you got another SD card? Restore to that

No I haven't. Not the same size anyway.

I think I will buy another SanDisk 64GB SD card and make sure I can actually restore to a new card etc.

HARMONY POWER AND ACTIVITY STATUS - WORKING

If I use this HTTP command it lists all the Activities on my Lounge Harmony Hub.

http://VERA-IP/port_3480/data_request?id=lr_Harmony184&cmd=list_activities

{ "status": "OK", "msg": "OK", "data": { "activities": [ { "ID": "27585584", "Activity": "ChromeCast Video" }, { "ID": "23834935", "Activity": "Media Center" }, { "ID": "23834936", "Activity": "XBOX" }, { "ID": "23864128", "Activity": "Wii-U" }, { "ID": "43190809", "Activity": "Nintendo Switch" }, { "ID": "23834933", "Activity": "Freeview" }, { "ID": "-1", "Activity": "PowerOff" }, { "ID": "42772934", "Activity": "Fire TV" }, { "ID": "36455394", "Activity": "ChromeCast Audio" }, { "ID": "42766865", "Activity": "BT TV" } ] }, "code": 200 }

In MSR I can see x_vera_plugin_harmony.activity_status ServiceID

When there are no activities running e.g. OFF the status returned is 0

And when I am in my Watch TV "BT TV" activity, the status is 2, so you should be able to work out which activity is what status number ?

Activities OFF - Status = 0

Watch TV Activity - Status = 2

So I created a rule that when my Harmony hub is OFF then turn off some LED strip lights.

Alternatively there is a ServiceID called x_vera_plugin_harmony.power_status

It is FALSE when all my Harmony Activities are turned OFF, so we can potentially use this instead.

And finally I looked at x_vera_plugin_harmony.current_activity this will return the activity ID numbers.

I know -1 = Powered OFF so I could have used this also.

When my Harmony is in Watch TV activity "BT TV" its showing a number ID of 42766865 which is correct. If you look at my output at the start listing all the activities and their ID numbers.

So I could now create an MSR rule that does something only when I am in the Watch TV Harmony activity etc.

@therealdb OK its working ! I just pasted the raw code in to the startup LUA area and the virtual motion sensor now follows the real devices tripped status.

I am writing a user guide for the Everspring EH403 Floodlight device, as it doesn't configure correctly after pairing with Vera.

I will credit you for your code in the guide when I publish it on the forum.

Thanks

I just edited the rule and ticked "ignore case" again and saved and the rule is still working and triggering, so that was a red herring as you say.

Home Remote does not support Ezlo hubs. and I am not sure if support for them will ever be added. I guess if somehow Home Remote integrated with MSR it might be possible to then import Ezlo devices into the Home Remote Designer / Dashboard app ?

@crille

Great thanks I will try it again.

I've not used Dynamic Groups before either, so you are giving me a good tutorial !

Alternatively doing it the "old" way without using a Dynamic Group these two expressions seem to work and are correctly returning the names of the two currently failed devices on my Ezlo Plus Controller:

FailedEzlo:

each id in matchEntities( { capability: 'x_ezlo_device' } ):
             ( getEntity(id)?.attributes.x_ezlo_device.reachable ) !=true ? id : null

FailedNamesEzlo:

join( each id in FailedEzlo: getEntity(id)?.name ?? id, ", " )

@crille

Thanks for the detailed information.

However after adding the group in to my reactor.yaml file MSR no longer starts or runs.

My controller is called Ezlo_Plus

I've tried both "Ezlo_Plus" and "ezlo_plus"

- id: groups
    name: Dynamic Group Controller
    enable: true
    implementation: DynamicGroupController
    config:
      groups:
        "UnreachableEzloDevices":
          name: Ezlo Devices Not Responding
          select:
            - include_controller: Ezlo_Plus
            - include_capability: x_ezlo_device
          filter_expression: entity.attributes.x_ezlo_device.reachable != true

Does it matter where abouts in the reactor.yaml file you add this code? I just added it in the Controllers section after my last "enabled" controller .

Thanks.

This is a currently failed device on my Ezlo Plus

battery_power.level=1
battery_power.since=1648664932056
humidity_sensor.units="%"
humidity_sensor.value=65.9700012207031
x_ezlo_device.battery_powered=true
x_ezlo_device.category="humidity"
x_ezlo_device.manufacturer="CentraLite"
x_ezlo_device.model="3310-G"
x_ezlo_device.parent=""
x_ezlo_device.reachable=false
x_ezlo_device.ready=true
x_ezlo_device.room="61f08bdc123e431284c13fbc"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory=""
x_ezlo_device.type_id="CentraLite_3310-G"
x_ezlo_item.battery=100
x_ezlo_item.humidity=65.9700012207031
x_ezlo_object.id="61f0bbbf123e4312a1900a18"
Capabilities: battery_power, humidity_sensor, x_ezlo_device, x_ezlo_item, x_ezlo_object
Actions: x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check

x_ezlo_device.reachable=false

Its a Zigbee device if that makes any difference.

Hi

Does anyone have an expression to detect failed devices on an Ezlo hub?

This is how we did it for a Vera hub here.

Thanks

Patrick would it be possible for the system to detect if any state files have 0kb values and just delete them automatically ?

Ok thanks I will read that tomorrow

Also have to figure out why my Raspberry Pi has gone tits up, that's still totally down, but only InfluxDB and Grafana on there so not the end of the world.

In Entities under Reactor System I have all this information

reactor_system.alert_count=0
reactor_system.alert_last=1647657325518
reactor_system.alert_severity=null
reactor_system.alerts=[]
reactor_system.arch="x64"
reactor_system.hostname="HP-Thin01"
reactor_system.internet_ok=null
reactor_system.platform="linux"
reactor_system.reactor_memory_used=138702848
reactor_system.reactor_uptime=1082
reactor_system.system_load=[0.13,0.15,0.11]
reactor_system.system_memory_free=2020356096
reactor_system.system_memory_size=3537993728
reactor_system.system_uptime=17002.98
reactor_system.volume_critical_reactor_base=false
reactor_system.volume_critical_reactor_data=false
reactor_system.volume_critical_reactor_logs=false
reactor_system.volume_reactor_base=[5390756,13825496,0.389,"/home/stuart/reactor"]
reactor_system.volume_reactor_data=[5390756,13825496,0.389,"/home/stuart/reactor/storage"]
reactor_system.volume_reactor_logs=[5390756,13825496,0.389,"/home/stuart/reactor/logs"]
sys_system.state=true
Capabilities: reactor_system, sys_system
Actions: reactor_system.clear_alert, reactor_system.clear_alerts, sys_system.restart

Memory free is that disk or RAM ?

I am assuming I have had a lucky escape here then, all my rules look to be present still, I am assuming "States" is just that as the name suggests the current state of the rules and that they will rebuild and repopulate themselves.

I didn't have any auto backup in place as not really sure how to do that in Linux command line, so I was just now and again manually copying the entire contents of the /reactor folder down on to my PC.