Advice reqeusted to migrate MSR from Bare Metal to Container

[LibraSun]

FEATURE REQUEST

Consider Including CallMeBot among the Notification classes, with the following parameters available for editing in notification.yaml:

base_url=http://api2.callmebot.com/start.php
source=vera
user=@<user_name>
text=<default_msg>
lang=en-US-Standard-C
rpt=2"

Of course, the text parameter can be overridden in Reactions and probably should not have a default setting come to think of it. IIRC, usernames correspond to the user's Telegram account nickname.

[LibraSun]

Just finished porting ALL of my Reactor recipes over to MSR Rules, and feel very accomplished for having done so. Only took me about a week, which included a TON of A/B testing.

With very few exceptions, my workflows are working swiftly and as expected. Any obvious glitches I've reported using Bug Tracker.
And the remaining one or two head scratchers (notably me pressing a button on my NodOn Soft Remote and Vera frustratingly ignoring me!) deserve deeper exploration before I submit a trouble ticket.

The MSR learning curve has been refreshingly low, and I suspect it will be even for staunch PLEG users as well.

[toggledbits]

The Nodons are among the "scene controllers" that use non-standard variables (well, according to the UPnP device and service definitions). It seems that half of the scene controllers Vera supports use LastSceneID, and the half use either sl_SceneActivated/Deactivated or sl_CentralScene, and I've scene (see what I did there?) one case recently where a device uses both (the former consistently and the latter inconsistently). Vera doing Vera things.

[LibraSun]

Delved deeper... turns out Vera had attempted to set a bogus Configuration Setting (device > details > Device Options)... Variable 1 = <empty>

Deleted that, did Save Changes, and voilà... not only did sl_CentralScene, sl_CentralSceneAttr and sl_SceneActivated spring back to life...
...so did the blinking LED in the center of the NodOn remote which, alas, had stopped working correctly last week. Guess how that's governed!? Yep, a Config Var (8, 1d, 3 IIRC).

Vera, Vera, Vera. Will your wonders never cease? Please? Pretty please?

[cw-kid]

Plus one for native CallMebot support. I am currently just sending a HTTP request.

Likewise for Telegram messenger push notifications, I am currently just sending a HTTP request.

Which is fine I guess, but anything that makes things easier for users is cool also.

[cw-kid]

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.

[toggledbits]

CallMeBot will be in today's build.

The Telegram plugin for Vera is supported through entity actions, no HTTP request needed.

[Matteburk]

@toggledbits Like Christmas for a kid the search entity function just popped up over night,when I woke up in a crispy Sunny Sweden it just was there.... Super great work P!

[cw-kid]

@toggledbits said in Preview of Multi-System Reactor:

Telegram plugin for Vera

I'm not using the Telegram plugin for Vera currently. Didn't see the point of installing another plugin, when I can just send a HTTP request directly to the Telegram API.

[cw-kid]

Just tested the new CallMeBot integration which is working for me.

In the notification.yaml file I just had to specify my username in the quotes:

user: "@user_name"

I also specified this language for proper English.

lang: "en-GB-Standard-A"

And the number of repeats I wanted:

rpt: "2"

When I press the Play button on the "Set Reaction" in my test rule, my phone receives a phone call saying "This is a test" twice.

My phone is Android Pie version 9. If anyone knows how to make this CallMeBot phone call ring out aloud even when my phone is in vibrate or silent mode I would really like to know how ?

[LibraSun]

@cw-kid said in Preview of Multi-System Reactor:

If anyone knows how to make this CallMeBot phone call ring out aloud even when my phone is in vibrate or silent mode I would really like to know how ?

Sounds like a job for Tasker. Best Android phone automation tool around. Basically Reactor for Android!

Among its many built-in variables is one for detecting the incoming phone number. That can become the basis for a "Profile" (trigger), which would run when CallMeBot phones you. And that profile can run a Task (reaction) which turns up your ringer volume and/or vibration.

Tasker even resets (some) changed States (attributes) automatically once the Profile goes inactive (false).

[cw-kid]

I am familiar with Tasker I do use it for some things already.

I was looking in all the various Android sound settings and notification settings etc, I thought I should be able to just exclude Telegram / CallMeBot so that when that particular app makes a notification sound or rings etc then it can do so, even if the phone is in silent or vibrate sound mode.

I spent ages looking around the settings but could not find anyway to do this.

[LibraSun]

Gotcha. And I concur that there is no such per-app setting in Android OS. Kinda boggles the mind that it doesn't exist, but c'est la vie.

[LibraSun]

@toggledbits I continue to receive email notifications from MSR (21081) containing ${{msgHead + msgBody + msgFoot}} rather than the substituted text. I know you demonstrated that it works fine on your end, so I don't want to file a PR on this, even though I'm on Synology NAS and your setup likely isn't.

Any adjustments you want me to try? Does spacing matter (e.g. ${{ msgHead + msgBody + msgFoot }} )?

[toggledbits]

Have you looked in the logs file to see if there are any errors logged with respect to the substitution? If you up the log level for Engine to 6, it will show you each substitution step as it makes it, as well.

[LibraSun]

I think I've got things sorted. (Every suggestion that there was an //error// condition among my Expressions in that particular Rule, which I ironed out.)

This begs the next question: "How best to introduce a linefeed or <CR> into one's text strings, for custom pagination/formatting?"

EXAMPLE:
The output of my SMTP message reads:
Vera says: \nMSR noticed that the Luup engine on Vera Plus just restarted.\n \nLuup engine restarted at 11:59:22 Tue 23 Mar 2021\non VeraPlus

where each instance of \n was intended to be a <br> as it behaved back in Reactor for Vera.

[toggledbits]

Coming soon. That's a change that gets done at the parser, and it implies some other issues with future localization that need to be done carefully.

[LibraSun]

On another note (please excuse the rapid-fire inquiries!):

Is there a hard-wired or practical limit to the size of objects that can be captured and stored by HTTP REQUEST GET/POST?

P.S. Really like how clicking the "Last value:" of a variable causes full contents to be selected for easy copying!

[toggledbits]

There is currently no limit on the response size, but it's probably going to get one in similar fashion to RFV.

I think it's time to close this thread and start encouraging new threads for new topics. I think this thread accomplished its mission and now seems to be meandering a bit.