Home / Productivity Apps / Tasker Network Event Server on Windows Pc

Tasker Network Event Server on Windows Pc

Developed By: TActHab

License: Free

Rating: 4,2/5 - 42 votes

Last Updated: September 04, 2019

Download App

Compatible with Windows 7/8/10 Pc & Laptop

See older versions

App Details

Version1.0.22
Size1.1 MB
Release DateJune 09, 16
CategoryProductivity Apps

App Permissions:
Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming. [see more (4)]

What's New:
Correct the problem with the HTTP server shuting down after a while. Service is now in foreground. [see more]

Changelog:
[see all]

Description from Developer:
TNES is a plugin that enables Tasker to trigger events when receiving messages over network. There are two ways to send messages to the plugin :1) Sending an... [read more]

App preview ([see all 7 screenshots])

App preview

About this app

On this page you can download Tasker Network Event Server and install on Windows PC. Tasker Network Event Server is free Productivity app, developed by TActHab. Latest version of Tasker Network Event Server is 1.0.22, was released on 2016-06-09 (updated on 2019-09-04). Estimated number of the downloads is more than 1000. Overall rating of Tasker Network Event Server is 4,2. Generally most of the top apps on Android Store have rating of 4+. This app had been rated by 42 users, 29 users had rated it 5*, 6 users had rated it 1*. Older versions of Tasker Network Event Server are also available with us 1.0.22 1.0.21 1.0.20 1.0.13 1.0.11

How to install Tasker Network Event Server on Windows?

Instruction on how to install Tasker Network Event Server on Windows XP/7/8/10 Pc & Laptop

In this post, I am going to show you how to install Tasker Network Event Server on Windows PC by using Android App Player such as BlueStacks, Nox, KOPlayer, ...

Before you start, you will need to download the apk installer file, you can find download button on top of this page. Save it to easy-to-find location.

[Note]: You can also download older versions of this app on bottom of this page.

Below you will find a detailed step-by-step guide, but I want to give you a fast overview how it works. All you need is an emulator that will emulate an Android device on your Windows PC and then you can install applications and use it - you see you're actually playing it on Android, but this runs not on a smartphone or tablet, it runs on a PC.

If this doesn't work on your PC, or you cannot install, comment here and we will help you!

Step By Step Guide To Install Tasker Network Event Server using BlueStacks

  1. Download & Install BlueStacks at: http://bluestacks.com
  2. Open the apk file: Double-click the apk file to launch BlueStacks and install the application. If your apk file doesn't automatically open BlueStacks, right-click on it and select Open with... Browse to the BlueStacks. You can also drag-and-drop the apk file onto the BlueStacks home screen
  3. After install, just click Run to open, it works like a charm :D.

How to install Tasker Network Event Server on Windows PC using NoxPlayer

  1. Download & Install NoxPlayer at: http://bignox.com. The installation is easy to carry out.
  2. Drag the apk file to Nox and drop it. The File Manager will show up. Click the Open XXX Folder button under the file sign that turns blue.
  3. Then you will be able to install the apk you just download from your computer to Nox or move/copy the file to other locations in Nox.
Powered by Google

Discussion

(*) is required

Correct the problem with the HTTP server shuting down after a while. Service is now in foreground.

June 11, 2016

Correct the problem with the HTTP server shuting down after a while. Service is now in foreground.

Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming.
Allows applications to access information about Wi-Fi networks.
Allows applications to access information about networks.
Allows applications to open network sockets.
TNES is a plugin that enables Tasker to trigger events when receiving messages over network. There are two ways to send messages to the plugin :
1) Sending an HTTP GET or POST to it : There is an HTTP server that can handle GET and POST requests on ressource "/" on port 8765. Variables of the POST can be filtered and transmited to Tasker as explains below.
2) Over then remote server http://thacthab.herokuapp.com : Go to this adress and register a free account. Then configure the plugin with both the login and the password you used for that account. You can send message via the website or by sending a GET or POST request to http://thacthab.herokuapp.com/broadcast . The GET or POST request MUST contains following variables :
- login : the login you used for the account
- pass : the password you used for your acount
- title : a title, actually just some text describing the message
- message : a message, can be simple text or a serialized JSON.
In this case, the plugin will consider following variables :
- senderName : its value will be equal to the login used to send the request.
- title : the title of the message
- message : the message.
- if message can be parsed as a JSON, then every attribute of it will be processed as variables.

The plugin will trigger the event if the variables contains in the message are not filtered. If at least one filter is evaluated as false, then the event is not triggered. Filters can be expressed when configuring an instance like this (one filter per line) :
variable
variable == value
variable != value

The filter "variable" means that variable should be present in the message, whatever its value.
The filter "variable == value" means that variable should be present in the message and that its value must be equal to "value".
The filter "variable == value" means that variable should be present in the message and that its value must be different from "value".

Every variable transmited via the network call will be translated into Tasker variable if the event is fired. The variable are named like this: %tpe_VARNAME, where VARNAME is the name of the variable in the network call, VARNAME is ALWAYS lower case so that the variable is local to the rule from the Tasker point of view.