#project #WakeOnLANManager
DESCRIPTION
If you have any device at home that is compatible with the Wake On LAN (WOL) protocol, this project will help you allowing them to be turned on or turned off from your phone.

This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet, or when the dev considers it is needed even not imported from TaskerNet.

Project Setup...
Previous Steps:
- Import project.
- Install AutoRemote and AutoTools (Android), and EventGhost + AutoRemote Plugin (Windows).
- Configure your devices to allow them to receive WOL Magick Packet.

* When registering device's names on AutoRemote as well as EventGhost, use the same exact names to configure them, as these names will be used within 'Setup' task inside the project.
* If you have problems receiving the ping response back from your devices, it's probably of its firewalls. To solve it, go here.
* As every device is a world, I won't cover how to enable Wake On LAN on this guide. You can search for your device's (or component's) manufacturer website for instructions on how to do that.

AutoRemote Steps:
1. On first time opened...
-- Allow AutoRemote to access device's storage (Android permission popup).
-- Give your device a name.
2. Once your new AutoRemote URL ID is on the screen...
-- Go to: Preferences (bottom icons) > EventGhost (Other Settings), and enable 'Skip Public IP' option.
-- Go to: Registered Devices (bottom icons), and authenticate the session with your Google account.
3. Done.

EventGhost Steps:
1. To setup EventGhost and its plugin...
-- Go here to learn how to configure EventGhost. (After step 13 is optional)
2. After checking that AutoRemote (Android) and EventGhost are communicated each other you can delete test actions. (Keep the plugin)
3. To add the project folder to your EventGhost tree...
-- Download it from here, and open it.
-- Select all the content of the TXT file and copy it to the clipboard.
-- Inside EventGhost, select 'Autostart' just above the AutoRemote plugin, right click on it and select 'Paste'. (It should looks like this)
-- Save settings and minimize EventGhost.

* When having to add the Key for the device we are going to register in AutoRemote plugin (EventGhost), you can get it by copying the AutoRemote (Android) generated URL and paste it on your browser. The key you need to add for your device will appear after 'http://autoremotejoaomgcd.appspot.com/?key=' at the top of the browser's URL address bar.
* Enable the 'Try to contact via local ip if available' option at the end of the plugin window (without adding any IP address). This will allow AutoRemote (Android) and EventGhost to still being in contact when no internet connection is available by whatever reason.

Notes:
- AutoRemote, AutoTools and EventGhost are needed for the project to work.
- All the devices will need to have a static IP address in the network. (Configure it from your router)

CREDITS
@SmartPhoneLover

VERSION
v1.0

#project #WakeOnLANManager
DESCRIPTION
If you have any device at home that is compatible with the Wake On LAN (WOL) protocol, this project will help you allowing them to be turned on or turned off from your phone.

This project includes an Initial Setup task that needs to be executed when it is imported from TaskerNet, or when the dev considers it is needed even not imported from TaskerNet.

Project Setup...
Previous Steps:
- Import project.
- Install AutoRemote and AutoTools (Android), and EventGhost + AutoRemote Plugin (Windows).
- Configure your devices to allow them to receive WOL Magick Packet.

* When registering device's names on AutoRemote as well as EventGhost, use the same exact names to configure them, as these names will be used within 'Setup' task inside the project.
* If you have problems receiving the ping response back from your devices, it's probably of its firewalls. To solve it, go here.
* As every device is a world, I won't cover how to enable Wake On LAN on this guide. You can search for your device's (or component's) manufacturer website for instructions on how to do that.
* To get rid of AutoRemote and AutoTools notifications when sending/receiving cmds, go to the device's Android App Settings and disable notifications for both apps.

AutoRemote Steps:
1. On first time opened...
-- Allow AutoRemote to access device's storage (Android permission popup).
-- Give your device a name.
2. Once your new AutoRemote URL ID is on the screen...
-- Go to: Preferences (bottom icons) > EventGhost (Other Settings), and enable 'Skip Public IP' option.
-- Go to: Registered Devices (bottom icons), and authenticate the session with your Google account.
3. Done.

EventGhost Steps:
1. To setup EventGhost and its plugin...
-- Go here to learn how to configure EventGhost. (After step 13 is optional)
2. After checking that AutoRemote (Android) and EventGhost are communicated each other you can delete test actions. (Keep the plugin)
3. To add the project folder to your EventGhost tree...
-- Download it from here, and open it.
-- Select all the content of the TXT file and copy it to the clipboard.
-- Inside EventGhost, select 'Autostart' just above the AutoRemote plugin, right click on it and select 'Paste'. (It should looks like this)
-- Save settings and minimize EventGhost.

* When having to add the Key for the device we are going to register in AutoRemote plugin (EventGhost), you can get it by copying the AutoRemote (Android) generated URL and paste it on your browser. The key you need to add for your device will appear after 'http://autoremotejoaomgcd.appspot.com/?key=' at the top of the browser's URL address bar.
* Enable the 'Try to contact via local ip if available' option at the end of the plugin window (without adding any IP address). This will allow AutoRemote (Android) and EventGhost to still being in contact when no internet connection is available by whatever reason.

Notes:
- AutoRemote, AutoTools and EventGhost are needed for the project to work.
- All the devices will need to have a static IP address in the network. (Configure it from your router)

CREDITS
@SmartPhoneLover

CHANGELOG
- New: Icons (Arduino, Raspberry Pi, Google Home)
- New: 'WOL WiFi (on)' and 'WOL Auto (on/off)' options to automate the Wake On LAN. (See 'Setup' task to configure and learn what they do)
- New: 'Ping Test' and 'WOL Test' separate tasks to help you to know if the device you're going to add is configured properly.
- New: Statusbar notification to stop sending turning on/off signals manually.
- Fix: 'Initial Setup' task was failing to download resources.
- Other: Reworked 'Initial Setup' task. (Will be applicable for future projects)
- Other: Deleted unnecessary actions from task linked to 'Turn On' button.

VERSION
v1.1

#warning #TaskerDev
[DEV] Avast/AVG saying Tasker is a virus. Hint: it's not! :P
Hi everyone. Since people have been complaining about this I thought it was better to create a post about it.

Seems like a recent update to Avast/AVG triggered it, suddenly saying that Tasker is a virus for some reason.

The part where the update was on Avast/AVG's part is very important and just shows that there's no problem with Tasker. If you scan the old first Tasker 5.9.3 beta it also says it has the same virus as shown here: https://www.virustotal.com/gui/file/bf079521cde70e02379eec8acc343158055fe0952f060222077664dc22e5444b/detection

Since I don't have a time machine and can't retroactively put viruses in apps, I think that's proof enough that Tasker didn't introduce a virus in the latest beta but that this was some kind of update on their part. :)

Also, I installed the Avast and AVG apps on my phone to try them out and it didn't detect viruses for Tasker in my case. Also, seems super sketchy (and against Google Play's TOS) that Avast and AVG are the exact same apps except for the color scheme.

Finally, I have no interest at all in putting viruses in Tasker. Why would I destroy an app I've worked for indirectly for so many years and successfully purchased about 2 years ago and can now develop for?

Also, if anyone has any info on the APK:RepSandbox [Trj] trojan that is mentioned by Avast/AVG it would be great. Maybe I can find out why they are seeing a false positive here.

I have no interest at all in anyone's data. Tasker's safe.

Please let me know if there are any questions about this issue.

Source: Go!

#task #ConvertDateTimeFormatIntoEpoch
DESCRIPTION
This task will help you to convert any type of date/time string format into Epoch time.

Notes:
- To know more about how to use SimpleDateFormat class, you can go here.

CREDITS
@SmartPhoneLover

VERSION
v1.0