Woli² control your android tablet

---

Hey,
some time ago I read here in the forum that some of you use wallmounted android tablets for controling homeautomation stuff. This is smart and I also wanted these advantages of the central control unit. So I installed one in my kitchen. But how to serve this tab automatically for example turn on display when pir-kitchen is present or open a website in kiosk mode or let it say something? Maybe tasker can do that?
A coworker point me to the android app woli²
awesome app!

Install the app. Turn off screenlock if active. Set the display off timer to 15 seconds. Install googel text to speech (sounds much better as the default robotic one.)

setting up the app…

• 1 push the star
• 2 turn on autostart
• 3 turn on use IP
• 4 turn on function you want to use
• 5 configure IP settings
• 6 activate UDP
• 7 set portnumber
• 8 set triggerword to whatever you want
• 9 set triggerwords for each used function to whatever you want
• 10 start woli

Now the woli app listens on the defined port for udp messeges like: “wolido:wake:1”

How to send UDP package?
Well you can use NodeRed for that…

or via commandline
echo -n wolido:wake:1 | nc -4u -w1 192.168.1.234 6666

A pimatic rule like following will let the tablet say something with includet variables, activate the screen and start a website in kiosk mode.

execute "echo -n wolido:speak:Die Aussentemperatur beträgt derzeit $weather.temperature Grad Celsius. Die Luftfeuchtigkeit liegt bei $weather.humidity Prozent. Heute wird es vorraussichtlich etwa $regen_heute.regen_heute milimeter pro quadrat meter regnen. Hier die Nachrichten für Dich | nc -4u -w1 192.168.1.234 6666" and after 1 seconds "echo -n wolido:wake:1 | nc -4u -w1 192.168.1.234 6666" and after 2 second execute execute "echo -n wolido:web:www.tagesschau.de | nc -4u -w1 192.168.1.234 6666" 

more samples…
wolido:wake:1turns screen on
wolido:wake:0screen turns off after 15 seconds
wolido:speak:hello world let the tablet say “hello world”
wolido:web:www.google.de opens website in kiosk mode (turn on “use WOLi-Browser” in URLs settings)
wolido:startapp:1 starts app witht ID1 (must be defined in App Launcher settings)
wolido:sound:1plays sound with ID1 (must be defined in Sound settings)
wolido:alert:1 popup alarm massege with ID1 (alerttext, sound and icon must be defined in AlertDialog settings)
wolido:toast:hello world toast message
wolido:notify:hello world notify message
… it is also possible to set brightness und volume

Now the tablet can talk with alexa

have fun
magic-tune

wahoo!! nice!! thanks a lot for your howto!

@magic-tune said

Now the tablet can talk with alexa

that surely would be an interesting conversation

@magic-tune

ooh my god… that app was great…
you got me now out of bed to implement them immediatly in my walltab!

thanx for this great tutorial…

Great! I tried it out and it works fine. Would be nice if some developer could write a plugin for this so that the ‘send’ command could be extended for this. Rule text would then be shorter and easier to handle.

In config.json:

{
  "plugin": "wolido",
  "terminal": "myTerm1"
  "ip": "192.168.1.234",
  "port": "6666"
}

And then in rule action e.g.

send wolido to: "myTerm1" action:"speak" msg:"Hello world!"

You can stop an ongoing speak by sending another speak command with an empty string.

Did anyone try Notify or Alert. With Notify the message is truncated on my Android Nexus tablet. Alert does show nothing.

@Heizelmann
Corrected my first post. It works as follow:
wolido:alert:1 popup alarm massege with ID1 (alerttext, sound and icon must be defined in AlertDialog settings)

@magic-tune Thanks for helping. It works, but it’s a pitty that the alert text can not be set as variable and that a new alert overwrites an old unread one.

Anyway wolido is agreat tool and I use it many times in my pimatic installation.

@Heizelmann said in Woli² control your android tablet:

You can stop an ongoing speak by sending another speak command with an empty string.

Disadvantage of this behaviour is that if multiple speak commands are sent e.g. from different rules at nearly the same time are not stacked but interrupts the currently ongoing speech output.

Meanwhile I use Woli² intensively within rules. To avoid over and over again the relativ lengthy and complex statement in the rule action string which I always can not remember I use the following workaround.

Instead of using this in rules

execute \"echo -n wolido:volume:12 |  nc -4u -w1 192.168.1.234 6666\" and execute \"echo -n wolido:speak:Pimatic is great. | nc -4u -w1 192.168.1.234 6666\"

I did this:

Firstly I defined I variable (used as constant) for my Woli and a variable for the actual speech output

{
      "name": "woli1",
      "value": "nc -4u -w1 192.168.1.234 6666"
}
{
      "name": "woli1-speech",
      "value": ""
}

With this on hand I defined the following general purpose rule

{
      "id": "woli1-speak-variable",
      "name": "woli1 speak variable",
      "rule": "when $woli-speech changes and $woli-speech != \"\" then execute \"echo -n wolido:volume:12 | $woli1\" and execute \"echo -n wolido:speak:$woli-speech . | $woli1\" and after 1 second set $woli-speech to \"\"",
      "active": true,
      "logging": true
    },

Now the rule action looks like this

set $woli-speech to \"Pimatic is great\"

Much simpler and shorter as the original aproach.

the developer has publish a new beta version (0.38.2) on his webpage, which includes some new features like batterylevel and setting export/import . see changelog.

Now its possible to get the batterylevel

echo -n wolido:batterylevel: | nc -4u -w1 192.168.1.234 6666 | nc -u -w1 -l 6666
BatteryLevel:67%

and only the value for pimatic shellsensor

echo wolido:batterylevel: | nc -4u -w1 192.168.1.34 6666 | nc -u -w1 -l 6666 | sed 's/BatteryLevel://g' |sed 's/%//g'
67