Changelog

3.0.26b (Beta) (2014-07-02)

  • Calling out all developers. Added support for AutoRemote plugins! You can now create your own AutoRemote clients like the video shows!
  • In the near future I will be releasing the first implementation of this new framework called ‘AutoNode’. This will be the official Linux AutoRemote client when it’s released. AutoNode will be an extensible a cross-platform node.js client that will enable you to send and receive AutoRemote messages on any system.
  • I have created a small sample app that shows how to create your own AutoRemote client. This is written in C#, just for the sake of simplicity, but the purpose of it is to show you what’s needed to create the client. Let me know if you have any questions! Download the sample plugin app here (I’ll post it on GitHub later): https://drive.google.com/file/d/0B8G77eDgeMdwZWJSMEE1bWh1SmM/edit?usp=sharing
  • Several bugfixes

3.0.25b (Beta) (2014-07-01)

  • Made messages and notifications synchronous! What this means is, Tasker will wait until the message or notification is actually sent before continuing the task. If the message or notification isn’t sent, the task will stop in error. This is only applicable to newly created messages or notifications or if you set the timeout of these to something like 20 seconds.
  • Re-did the file transferring process so that it’s more reliable and doesn’t depend on having a Google Drive device in your device list. It should just work. Dropbox won’t be used to send files anymore.
  • Made Google Drive the place to backup and restore your URL. Local and Dropbox backups and restores are now available under Advanced->deprecated

3.0.18b (Beta) (2014-04-22)

  • Added “AutoRemote” Tasker event. Please use this instead of the plugin state as it is 2 times faster.
  • Changed the way messages are handled to better handle faster successive messages
  • Removed wake locks from the Wifi and BT Services. This is a beta feature to see if it keeps working as well as before.

3.0.16b (Beta) (2014-02-17)

  • Added new “AutoRemote Communication” Tasker event. This uses the new Tasker Event plugin condition which is available in the new Tasker beta (4.3)
  • several bugfixes

3.0.9

  • Added option to always try to send through Wifi even if not on the same network as the receiving device. Can be useful if using your phone as a mobile Access Point for your Tablet for example.
  • Fixed bug where sending “\n” in a message wouldn’t result in a new line

3.0.8

  • Added chrome popup actions on notifications. Allow you to send custom text back with the notification action: for example, you can reply to an SMS by writing the text directly in Chrome.
  • Fixed bug where actions could only be performed once.

3.0.7

  • Added option to send notification button icons to chrome extension

3.0.6

  • Added option in the Android app to always skip trying to send messages through BT and Wifi
  • Added option in the Chrome extension to redirect all received messages to EventGhost
  • Fixed bug where notification buttons wouldn’t show if the notification text was short
  • Fixed bug where linux messages wouldn’t receive a response if you have a password set in AutoRemote

3.0.5

  • Added lots and lots of notification status bar and button icons
  • Made EventGhost devices able to receive remote shares again
  • Fixed bug where notifications weren’t received via Bluetooth
  • Fixed bug where status bar and button icons weren’t set when sending notifications to yourself
  • Other smaller bugfixes

3.0.4

  • Fixed bug where Chrome Fallback could be done twice
  • Fixed bug with notifications on Android versions lower than 4.1

3.0.3

  • Added option to skip local ip for EventGhost so you can go straight to chrome fallback without trying any IP
  • Added new Tasker action “AutoRemote Settings” where you can change EG settings from Tasker. I can add more settings here by request.
  • Added support for Opening URLs remotely later to the EG plugin. You now have a new EG action to get these URLs. Place them where ever you like in the EG tree to get them. For instance, you could add this action on startup or when logging in to your PC.
  • You can now send messages to EG directly via URL again. This works just for messages. The url is something like http://localhost:1818/?message=MESSAGE_HERE . Replace “localhost” with your IP if not on the same PC.
  • Fixed bug where selected chrome fallback didn’t “stick” after AutoRemote was closed.

3.0.2

  • Fixed bug where files with redirections would have a bad filename
  • Fixed bug where Linux messages where always sent with the public IP if that IP existed
  • other smaller bug fixes

3.0.1

  • Added option to fallback to Chrome if sending message to EventGhost fails. This allows you to have a similar behaviour as the old “Fallback to Dropbox” option for the AutoRemote Desktop app.
  • The above allows you to send messages to EventGhost and be pretty sure that they will always arrive if you have EG and Chrome running on your PC
  • Added option to skip EG’s public IP address and go right to Chrome redirection if a local request fails
  • Fixed bug with some file browsers when selecting files to use in messages or notifications
  • Fixed bug that crashed the log screen sometimes
  • Fixed bug when you request all the devices from a device that has no devices in its list (a bit confusing I know :P)
  • Other minor bugfixes

3.0

  • Full release! AutoRemote is finally out of beta again.
  • a bunch of bug fixes.

2.2.17b (Beta)

  • When you change the ROM on your device, AutoRemote will detect that and automatically refresh your personal URL (it won’t change it)
  • Bugfixes

2.2.16b (Beta)

  • Fixed bug where AutoRemote Android couldn’t send messages through the web
  • Added option to refresh AutoRemote so you can easily get it back up and running after a ROM change, etc.
  • Fixed bug where messages with a “=” in them couldn’t be sent through wifi
  • Fixed bug where messages sometimes weren’t sent through bluetooth

2.2.15b (Beta)

  • EventGhost can now send files to devices even if not on the same network. Please accept the Google Drive permission request to use this feature. This request will appear when restarting EG after the update.
  • This means you can now also send notifications with local files and they will always arrive at your phone regardless of the network situation you’re in (unless you’re offline of course)
  • EventGhost plugin now also updates automatically via the web in addition to updating with the Android app
  • Added Tag button in text all fields so you can more easily use Tasker variables inside AutoRemote
  • Fixed Time To Live parameter on Android notifications
  • Fixed bug in EG where it wouldn’t detect your local IP if you didn’t have an internet connection

2.2.14b (Beta)

  • EventGhost plugin will add entry to the Windows Context Menu so you can send files to EventGhost. With this you can send files directly to your phone.
  • Redirect to Port was moved to the Chrome extension instead of it being in the Android App
  • Added test message field to AutoRemote Chrome Extension
  • Fixed bug with chrome redirection
  • Fixed bug when sending files from Android where some files could be sent with the wrong file name and the jpg extension
  • Time to Live added to register an notification

2.2.13b (Beta)

  • Needs you to update the EventGhost plugin manually. Please download it here and copy it over your current file that is usually in the following folder: C:\Program Files (x86)\EventGhost\plugins\AutoRemote\
  • Allows for file transfers between EventGhost and Android Devices. Send files from your PC to your phone easily!
  • Allows for file transfers between Android devices via local wifi network
  • This means you can now also create notifications with local files both from EventGhost and Android and they will automatically be pushed to the other Android device.
  • These are all the parameters you can put in an AutoRemote notification url:
    • title
    • text
    • url
    • channel
    • message
    • id
    • action
    • icon
    • led
    • ledOn
    • ledOff
    • picture
    • share
    • action1
    • action1name
    • action2
    • action2name
    • action3
    • action3name
    • sound
    • vibration
    • persistent
    • statusbaricon
    • action1icon
    • action2icon
    • action3icon
    • ticker
    • dismissontouch
    • priority
    • number
    • contentinfo
    • subtext
    • maxprogress
    • progress
    • indeterminateprogress
    • actionondismiss
    • cancel

2.2.12 (Beta)

  • EventGhost update will automatically be applied once you receive a message from it that matches any of your Tasker conditions. You can also manually update it by long-pressing the EventGhost device in your device list
  • Made EventGhost able to send requests via local network
  • Fixed bugs with notifications
  • You can now use EventGhost devices in the “AutoRemote Devices” Tasker action
  • Fixed wifi communication between Android devices

2.2.10 (Beta)

  • Added way to update the EventGhost plugin directly from the Android app
  • Fixed some EG plugin bugs. Download updated version here: https://dl.dropboxusercontent.com/u/9787157/AutoRemote/__init__.py
  • Fixed several Google Drive related bugs
  • Fixed bug where you could set Google Drive as favorite device
  • Fixed bug where when you added Dropbox, Google Drive or Zapier devices you could still click their Action bar buttons
  • Fixed bug where it would append a “.jpg” on all files with “content://” urls

2.2.9 (Beta)

  • Major update to EventGhost plugin. Get latest version here. Copy file to your EventGhost folder which is usually under C:\Program Files (x86)\EventGhost\plugins\AutoRemote. It’s very important to do this, or else EventGhost won’t work with this version.
    • Can receive files. Will do it over wifi so it’s way faster
    • When you receive a message with files, an EG variable is populated with these files. It’s an array, so to access the first file you use something like {eg.event.payload.files[0]} It may seem odd but 0 is the first position of an array, unlike in Tasker.  You can put this is in a Show OSD action to test it. If you want to directly open the file you can add a python command and there write:from os import startfile;startfile(eg.event.payload.files[0])
    • Can receive remote registrations
    • Can respond with own info to request from Android device

  • Added new Tasker Action “AutoRemote Query” that returns all existing devices. If there’s demand I can create filters to return only devices of a certain type, with a certain name, etc. Only works with latest Tasker beta: tasker.dinglisch.net/beta.html
  • Added support for Google Drive to send and receive files between Android devices. You can now use this or Dropbox.
  • Added device icons in the device list to more easily identify each one
  • Fixed bug where notifications couldn’t be sent
  • Fixed some other bugs

 

2.2.8 (Beta)

  • Bugfixes

2.2.7 (Beta)

  • You can now click the Wifi and Bluetooth icons in the device list to enable/disable this type of communication. This makes sending messages faster if those aren’t available because AutoRemote won’t try those methods first.
  • In the “AutoRemote Devices” action in Tasker you can now enable/disable Wifi and Bluetooth
  • Fixed crash while entering the “AutoRemote Notification” screen.

2.2.6 (Beta)

  • Sorry about the big bug that didn’t allow devices to send any messages. Fixed!

 

2.2.5 (Beta)

  • Added way to remotely send images or files if you have a dropbox account. If you don’t have an account, what are you waiting for? 🙂 Get it here. Imagine, for example, taking a picture with Tasker and have it show up on your other device’s notification bar in seconds. You can use this to even transfer any file you like from one device to the other: 
  • Fields that support this new feature are the “Files” field in the “AutoRemote Message” action, and the “Icon” and “Picture” fields in the “AutoRemote Notification” action
  • Added “Device Manage” action in Tasker that allows you to receive and send device registrations from within Tasker. You can do neat tricks setting up a Tasker action to automatically refresh your IP on another device when you get connected to a certain Wifi connection, for example.
  • Fixed the AutoRemote variable listing in Tasker issue, where it would show null instead of the variable names
  • Added some new variables to the AutoRemote condition. Check them out in Tasker’s variable list inside a Tasker action.

2.2.4 (Beta)

  • Can now send and receive messages bigger than 4 kB
  • Can now get all registered devices from another device and register them on your own: 
  • Can now send own registration to another device (you can refresh your local IP address this way, for instance)
  • Can now refresh other devices’ info. Useful if the device changes IP address for instance
  • Sending messages to Groups in Tasker now works

2.2.3 (Beta)

  • Channel Management Screen now works, and is now called “Groups”. You can access it from the main app screen now.
  • Fixed bug on pre-ICS devices that made the app crash every time

2.2.2 (Beta)

  • Bugfixes

2.2.1 (Beta)

  • Fixed bug where you couldn’t send a message to an android device if it didn’t have Wifi configured.

2.2 (Beta)

  • This is mostly invisible for users, but I’ve completely rewritten AutoRemote. It is now easier to maintain so I should be able to implement new features in a quicker way. So, if something doesn’t seem to work, please bear with me. There were LOTS of changes.
  • Added direct communication via Wifi!
    • In Tasker, add the new “AutoRemote Wifi” action to start the listening service whenever you need it. This service is needed to receive message, but not to send them
    • Go into your device list, and press the Wifi button in the action bar
    • It’ll scan your network for devices that have the Wifi service enabled, so make sure to enable it on other devices first.
    • Send a message like you normally would to that device and Wifi will be tried first. If it doesn’t succeed, message will be sent via bluetooth, and if that doesn’t work, it will be sent normally
  • Fixed Bluetooth communications. Should work now (I hope :))
  • Added quick message and notification buttons on the device list screen
  • Added Channel Management screen where you can see the current list of channels and what devices are in each. The “+” and “X” buttons are just placeholders for now. It doesn’t do anything yet, sorry! You can still manage your channels in the Tasker action.

2.1.1 (Beta)

  • Added direct communication via bluetooth!
    • Go into your device list, long press device and select “Set Bluetooth Device”
    • In Tasker, add the new “AutoRemote Bluetooth” action to start the listening service whenever you need it. This service is needed to receive message, but not to send them
    • Send a message like you normally would to that device and Bluetooth will be tried first. If it doesn’t succeed, message will be sent normally
  • Changed the way you send messages from an HTTP GET to HTTPS POST
  • Made name matching easier when sending a message to a device by name
  • Upgraded to tabbed logs
  • Fixed QR code on tablets
  • QR code now includes the name so you don’t have to type anything to pair devices

2.1 (Beta)

  • Local Personal URL backup
  • Notifications now have just about every AutoNotification feature. New properties that you can use in the direct notification URL now include (for the icons, use their name as shown in the option in the Tasker “AutoRemote Notification” action):
    • statusbaricon
    • action1icon
    • action2icon
    • action3icon
    • ticker
    • dismissOnTouch
    • actionOnDismiss
    • priority (2 is max,
    • is min)
    • number
    • contentInfo
    • subtext
    • maxProgress
    • progress
    • indeterminateProgress
    • persistent (input any value to manipulate a persistent notification)
    • persistentCreate (any value to create, no value to destroy)
  • Messages to PCs are retried if sending failed
  • Try sending messages even if not on wifi or Mobile network, because ethernet adapters exist 😛
  • Linux port setting now works
  • AutoRemote now acts as a browser, so you can send any URL to another device
  • When receiving an URL from a remote device, screen will now turn on and unlock automatically (if no lock security is present)
  • Send messages by name: you can even set the device name in a Tasker variable and send it to a variable recipient this way.
  • Messages to Zapier would sometimes indicate an error even if there was none. Fixed.