Developer: | Jason's Plugins |
Category: | IP Communications |
Github: | Github Repo |
Assistance: | Get help! |
Plugin ID: | com.heddings.indigo.netdev |
Latest release: | v2.4.1 released on Dec. 13, 2020 (this release is only compatible with Indigo 2022.2 and earlier) |
Release downloaded: | 1 times |
Requires: | Indigo v7.0.2 thru v2022.2 |
(Check the Releases tab below for older releases that may have different requirements) | |
Download latest release |
Represents devices on the network, such as computers or other connected devices.
Indigo Pro is required to get support for plugins. If you haven't tried Indigo and are interested in home automation, please give it a shot right away... You won't be disappointed!
To communicate with remote devices, this plugin depends on the ssh
command locally. It
must be executable by the user running the Indigo server to function properly.
Additionally, this plugin requires Indigo 7 or higher.
This plugin is installed like any other Indigo plugin. Visit the releases page and download the latest version. For advanced users, you may also clone the source tree directly into your Indigo plugins folder, making updates as easy as pull & reload.
After installing the first time, you will be prompted for the plugin configuration. You can also access the plugin config at any time from the Plugins menu in Indigo.
The "Refresh Interval" determines how often Indigo will poll your network devices for status (in seconds). This value should be something reasonable that your network and remote systems can tolerate. Note that some systems get unhappy if they are polled too often, which may result in blocking your IP address. Values for this option range from 1 to 3600 (1 hour) seconds.
Specifying the "Connection Timeout" establishes how long the plugin will wait for a remote system to respond before considering it unreachable. This value should be small enough to keep things responding quickly, but long enough to account for any network latencies or system performance variations.
Network services are monitored by performing a basic check on the supplied port. This is usefuly to get a quick status for remote systems when the service itself is less important.
These device support status only.
Pings an address and reports 'Active' if it responds succesfully.
Examine the HTTP status of a path and set device as OK or ERROR.
Querries ipify for the current external IP (either IPv4 or IPv6).
Uses the local ARP table to find devices on the network by their hardware or MAC address.
NOTE this device type depends on the arp
command. You can see the active devices by
running arp -a
on your Indigo server to troubleshoot issues. Due to different network
configurations and routers, some wireless devices may not be seen on a wired network. In
this case, joining the wireless network on the Indigo server may help.
All SSH commands are authenticated using a shared keypair. This must be generated and available for the local Indigo user (typicall in the local user's .ssh folder). Here is a basic overview for setting up SSH keys.
When checking status, the SSH server will use a safe command (true
by default) to
determine whether the system is off or on. The exit code is also examined to ensure the
command completed succesfully. This has a few interesting side effects, namely that this
will ensure SSH is responding correctly and any errors running the command are seen as
the device being "off."
SSH Devices may be turned off like an Indigo relay device. The advanced configuration in
the device configuration allows the user to set a specific command to safely shut down as
if running on the command line. Some devices, such as routers or other embedded linux
servers, use the poweroff
command rather than shutdown
.
The "Username" property will be passed to the SSH client to authenticate on the remote system. If this is left blank, the Indigo server user will be used. For most applications, this value will be set to the super user account (e.g. "root") to enable shutting down the system from the command line.
NOTE once turned off, these devices must be turned on at the system.
Once devices are configured, their state may be monitored for triggers. Servers and devices that support Indigo's relay features may be acted upon as any other device.
Released on: | Dec. 13, 2020 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 1 times |
Download this release |
Released on: | July 22, 2020 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
Released on: | May 3, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
Released on: | May 1, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
Released on: | May 1, 2018 |
Requires: | Indigo v7.0.2 thru v2022.2 |
Downloaded: | 0 times |
Download this release |
Released on: | Jan. 1, 2017 |
Requires: | Indigo v6.0.0 thru v2022.2 |
Download this release |
Released on: | Dec. 31, 2016 |
Requires: | Indigo v6.0.0 thru v2022.2 |
Download this release |