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.

@Crille

Brilliant good to know thanks

I'm confused I have 99 Alerts saying I have lots of devices and scenes that no longer exist on my Ezlo Plus controller.

However the devices and scenes are still on the controller.

I then wondered if some how all the device ID numbers had changed?

I just check four devices from the MSR Alerts list and using their ID numbers I used the Ezlo Online API Tool to give me a list of all devices.

In note pad I then search for these device ID numbers and they are still the same, meaning the number listed in the MSR Alerts, is still the same device ID number for the same correct device name from the Ezlo API Tool output.

What gives ?

Hi

Is there a way to copy text from an Alert or export them?

I wanted to copy a device ID number that MSR says no longer exists on my Ezlo Plus controller.

Thanks

OK just setup the rest of my MSR rule now with a Reset reaction, that gets the Vera Plus to run a LUA / os.execute shutdown command sent to the Windows 11 PC.

So now when I start my Logitech Harmony activity for the Windows Games PC, MSR triggers the rule and gets Vera to send a WOL packet to the PC to wake it up.

And when I end the Harmony activity the reset reaction in the MSR rule gets Vera to shutdown the PC.

I even managed to get my Harmony Elite remote to launch RetroArch or Steam via buttons on the LCD screen and I also added a ALT+F4 button to exit the Windows apps.

Next thing to figure out is how to split out the HDMI audio to a pair of PC speakers.

Thanks.

Its working now !

In Putty connected to my Vera Plus I ran a shutdown command to the Windows 11 PC it then said:

Host '192.168.1.47' is not in the trusted hosts file.

I hit Y to continue and Vera has just shutdown the Windows 11 Mini-PC via SSH.

Thanks.

OK let me try that then.

@toggledbits said in How to shutdown a Windows 10 PC ?:

If the Windows PC was previously known to the Vera before your upgrade, it's likely that the SSH key was regenerated on the Windows PC side when you did the upgrade, so the Vera SSH has the old host key. You can remove it from the known_hosts file on the Vera side.

The Mini-PC was not known to the Vera before. I updated to Windows 11 and then install OpenSSH on the Windows 11 PC.

Before that I did nothing with Vera and the Mini-PC running Windows.

Oh I think I see what might be happening now. Looking in the known_hosts I already have an entry for the static LAN IP address of the Mini-PC but that is for Linux Debian on the Mini-PC.

Before when I was messing about with Ezlo Softhub I setup a dual boot on the Mini-PC for Windows 10 and Debian Linux.

Guess I can't have two known hosts for the same IP address but different OS's.

@catmanv2

I always struggle with this type of stuff. Patrick helped me in the past on this Vera forum thread here.

On that old post I wanted my Vera Plus to be able to ssh into my Raspberry Pi with no password prompt.

I could then create MSR rules that instruct Vera to run a command like this to say reboot the Raspberry Pi etc.

os.execute("ssh pi@192.168.1.101 sudo reboot")

I updated this PC to Windows 11 and installed OpenSSH Server on it. I was then able to login to it directly via Putty on my other Windows 10 laptop, I was prompted for the username and password and I could then issue a shutdown /p command and it did then shutdown the Mini-PC.

I then tried to add my Vera Plus public key on to the Windows 11 PC so that Vera can ssh directly to it with no username and password prompt etc. However its not working I get this error every time.

ecdsa-sha2-nistp256 host key mismatch for 192.168.1.47 !

192.168.1.47 being the Windows 11 OpenSSH Server

I created an authorized_keys file on the Windows 11 PC in this location:

C:\Users\myusername\.ssh

And in the authorised_keys file I pasted in the Vera Plus pubic key.

I also followed the instructions on this article here to enable "Public key authentication" on the OpenSSH Server on the Windows 11 PC.

Then reading this Microsoft article it suggested if my windows user is in the administrators group I need to instead create a administrators_authorized_keys file in C:\ProgramData\ssh\

So I tried that but I still get the host key mismatch error when I connect to the Vera Plus via putty and then tried to ssh to the Windows 11 PC.

OK thanks I will take a read and report back.