Skip to content

mlava/ninja-autoremote

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

45 Commits
 
 
 
 
 
 
 
 

Repository files navigation

ninja-autoremote

v0.4.2

A driver for Ninja Blocks to allow communication via the Autoremote plugin for Tasker, written by João Dias.

This driver contains large parts of code that comes directly from the ninja-ipcam driver written by @thatguydan. Thanks to @paulcull for answering several noob questions that nonetheless were stumping me completely! Any mistakes made in the reintegration of the work of the above are mine.

With thanks for the open nature of the Ninja Blocks platform and community.

Installation

cd /opt/ninja/drivers

git clone https://github.com/mlava/ninja-autoremote

cd ninja-autoremote && npm install

sudo service ninjablock restart

Configuration

Select 'Drivers' in the ninja dashboard.

Select the ninja-autoremote driver.

Add or remove Autoremote devices via the menu.

Enter a suitable device name: this will be used to name the widget as well as differentiate your devices in the rules engine.

For arpar fill in the value you want to appear to the left side of the =:= in your message. For help, see http://joaoapps.com/autoapps-command-system/.

Enter the device key for the device you want to send data to. This can be found by following the instructions at http://joaoapps.com/autoremote/direct/.

Message will send a message to your device with arpar=:=data where data is what you enter in the widget or in the rules engine. Notification will send a notification to your device with the notification title being arpar and the notification text the data you enter.

Use

Type your message in the widget (old dashboard), and send.

Check your Autoremote log to confirm you are receiving messages from the Ninja Blocks platform, or, if you selected to send a notification, check your device's notification area.

Your Autoremote devices should also be available via the rules engine as actuators - complete the text to receive that message on your Autoremote device when the rule fires.

Changelog

v0.4.2 Corrected message format to use =:= convention.

v0.4.1 Deprecate TTS announcement feature as already part of Autoremote and Tasker capcabilities... no need to duplicate. Sorry for confusion!

v0.4 Implement TTS announcements using the Google Translate TTS engine and a specific tasker profile and task combination (see configuration above).

v0.3 Implement automatic registration of new devices from configuration menu as devices on dashboard. (Avoid having to restart Ninja Block service to register the Autoremote widget on dash.)

To-do

  1. Allow further notification configuration options as per http://autoremotejoaomgcd.appspot.com/AutoRemoteNotification.html.

DONE:

  • Deprecate TTS via Google Translate TTS engine - not needed as already part of Tasker functionality.
  • Implement TTS via Google Translate TTS engine.
  • Implement Send message vs Send Notification option when adding Autoremote devices, and invoke different widgets for each option.
  • Implement naming of Autoremote devices. (In the meantime, just click on the gear and Rename on the old dashboard widget...)
  • Implement user-defined arpar text in messages (ie. the left side of the =:= in the Autoapps commands structure). For now this defaults to 'Nina=:='.
  • Gist for widgets on beta dashboard.

About

Ninja Blocks Autoremote driver

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published