Digital Loggers

Frequently Asked Questions

Updated 10/09/2023

ETHERNET POWER CONTROLLER 7




Users Guide •  Complete Documentation •  Check the specs
Firmware Update •  What accessories are available?

See the overview here - or call (408) 330-5599 for a free trial

 
Is there a keypad reference? 
How do I set up network with the keypad?
How do I set up the WiFi network?
How do I set up network access in Windows? From a Mac? - Thanks to John McClintock for these Mac tips.
How do I set up port forwarding?  Router Port Forwarding example. - Kudos to Mike G
What is the default IP address?  How do I reset to defaults?  What is the default password?
Where can I find the most complete help and documentation?
General FAQs
 What is the current version of firmware?
Can you develop custom firmware or custom hardware for my app?
What are the CRITICAL and PROTECT functions?
Where can I find more extensive and detailed help?
How can I set up autoping to reboot my modem and router, but have my router to come on later?
Can I set outlets to cycle at different rates?
Can I increase the internal system log size?
How can I get a dry contact relay output?
What's the new Lua Language and Scripting all about?
How can I control and customize the LCD?
How do I enable autoping?  Explain the autoping settings
What's syslog?  How can I keep an event log?
How do I set up event notifications?
How do I change the NTP servers?
The session timeout is too short. Can I make the session longer?
What is the command-line interface in the SSH shell?
How can I update the firmware via the SSH shell?
How to I install a supported VPN?
How can I clean up old SSL certificates?
How can I install my own certificate?
How do the meters work?
What's the DB-9 pinout?
What temperature sensors are compatible? What is the part number & price?
How do I enable the battery backup?  How long will the battery run?  What is the battery lifetime?
Fixes
How do I fix: email notification failed: [CURL-EASY][PEER_FAILED_VERIFICATION] SSL peer certificate or SSH remote key was not OK (60)
How do I fix: email notification failed: [CURL-EASY][COULDNT_RESOLVE_HOST] Couldn't resolve host name (6)?
I can't access the controller from another network. Cannot autoping an external server such as 8.8.8.8. How do I fix cross network access?
How do I fix: [CURL-EASY][OPERATION_TIMEDOUT] Timeout was reached (28)? Check the above 3 issues.
How do I fix: Peer certificate cannot be authenticated with given CA certificates (60)?
How do I fix: "failure while reading service directory" when trying to renew a SSL certificate?
When I unplug the Ethernet cable the WiFi quits working.
How do I clear "SECURITY LOCKOUT IN PLACE" when I try to login?
How do I fix a "Host request header not present or not recognized" error when I try to login from a different network?
External APIs - Communicating with the power controller
 How can I connect to Amazon Echo, Alexa, Dot or Tap products?
How can I connect to Google Assistant or Google Home?
How can I access the switch from my own application or remote script?  What's the cURL API?
Is this product compatible with legacy plaintext scripts and HTTP control?
How can I control the switch from my own applications? 
What is the recommended REST API?
Can I give a non-admin user limited admin access?
Have any SNMP setup tips?
Do you support MQTT?
How can I set up IFTTT?
Do you support HomeSeer?  
Do you have a Crestron control module?   
Can I use LabVIEW to control DLI power controllers?  
Where can I find ASCOM drivers?   
Do you have a Visual Basic.NET example program?  Thanks to Alan Holmes
Do you have a .NET programming example?
Do you have a Java programming example?
Do you have a compiled Windows command line tool or a Perl example?
Do you have a Python programming example?
How can I run a Perl script from LabView?
Where can I find iPhone, iPad, or Android apps for Digital Loggers?
Do you support PowerMan?
Question:  I have a different model: Web Power Switch 7, 6, 5, 4, Ethernet Power Controller II, III, V, or  PC-8000 model.  Where can I find information?
Answer:  Jump to the support page here. Don't see what you need?  Just give us a call (408) 330-5599.
Question:  Whch temperature sensors are compatible?
Answer:  The DS18B20 or DHT-11 sensors with Humidity sensor with RJ12 plugs are compatible and in stock P/N: DS18B20-RJ12 and P/N: DHT11 respectively. The pinout is shield=ground, ring=5V VCC, tip=data. Find a Lua thermostat code example here.

Question:  What is the current version of firmware?
Answer:  Find the revision history here, and firmware update instructions here.
Question:  How does this model compare to the earlier wired-only models?
Answer:  These units have both hardwired Ethernet and WiFi, thanks to a more powerful 32 bit CPU from Qualcomm Atheros.  The design includes expanded memory for the Atheros including FLASH, EEPROM, and SDRAM.  Leveraging open-source code and expanded memory allowed us to add several firmware features including SNMP, HTTPS, SSL, SSH, Rest API and Alexa Compatibility, a REST API and MQTT.   The BASIC scripting language has been replaced by Lua.  A much more powerful watchdog supervisory processor has been added.  Most important, there's good news on price: the new, more powerful ICs are less expensive. Here's a feature matrix comparing the older Taifatech and newer Atheros power models. Courtesy of Mike Gillen
Question:  Where can I find more extensive and detailed help?
Answer:  Click on the Help menu link on the power controller itself.


Then click on the on-line help icon.
Question:  I have a different model: Web Power Switch 7, Ethernet Power Controller II, III, V, or  PC-8000 model.  Where can I find information?
Answer:  Jump to the support page here. Don't see what you need?  Just give us a call (408) 330-5599.
Question:  How can I control and customize the LCD?
Answer:  The LCD can be used to display settings, outlet status, or any message of your choice.  You can operate the LCD in "billboard" style, displaying a series of user defined messages.  To customize the LCD, you'll want to write a script using the Lua scripting language.   You can also use the display to send messages from remote systems (ie. service alert warnings).  To send messages remotely, write a script first, saving it in FLASH then start the script from your remote system.  Learn more about scripting here.
Question:  How can I set up autoping to reboot my modem and router, but have my router come on later?
Can I set outlets to cycle at different rates?
Answer:  OF course, this can be done via Scripts.
However, you can also make the outlets cycle at individual rates by using the REST API or UOM. Log into the power controller and be sure that the REST API is enabled.

Go to the Outlets in the REST API. e.g. http://192.1680.100/restapi/relay/outlets/
Select the outlet to set the custom cycle time on.


Select the cycle delay setting.


Set the custom cycle delay.


For example, you can set the modem delay to 15 seconds and the router delay to 45 seconds.
In this example, when Autoping cycles the outlets, the modem will come on after 15 seconds and the router will come on after 45 seconds.
Question:  Is this product compatible with the older (less secure) HTTP plaintext command syntax? 
Answer:  To use the earlier HTTP commands described here and CURL scripts that use plaintext login, you'll need to enable this legacy setting on the SETUP page:
Question:  What is the default IP address? How do I reset to defaults? What is the default password? 
Answer:  Follow this procedure to reset to the default IP address of 192.168.0.100:


    Press and release the reset button. After about 5 seconds, you will hear a beep, then use the up and down keys to choose the type of reset.
    The following reset modes are available:

    1. Clear lock bits: Clear protection bits only. Other settings are preserved.
    2. Reset Net&Script: Clear protection bits, reset network settings and admin login, disable autoping and scripts. Other settings are preserved.
    3. Reset + WiFi:   Clear protection bits, reset network settings and admin login, disable autoping and scripts, and enable open WiFi access. Other settings are preserved.
    4. Complete wipe: Reset all settings to factory defaults and remove any user files. All settings will be lost!
    5. Wipe + WiFi: Reset all settings to factory defaults and remove any user files, then enable open WiFi access. All settings are lost!
    6. Reboot: Reboot only. All settings are preserved.  (firmware versions 1.12.14.0+)

    To activate the selected reset mode, press cycle or the reset button and hold it.

     

    The default master login is "admin" and default password is "1234".  The default IP is 192.168.0.100.


    If all settings are reset (the two last 'wipe' reset modes), the Subnet Restriction will be enabled to prevent remote access using the default password. ONLY MACHINES IN THE SAME SUBNET WILL BE ABLE TO CONNECT AFTER RESETTING TO DEFAULTS.
    Besides setting your computer to a compatible network, you can also use the keypad to set it up.
    The keypad settings Pro/V222/DC3/ISO32 are slightly different from the keypad settings for the DIN and EPCR models.
Question:  On initial setup, I can't establish a Ethernet communications from a Windows PC.  Help!
Answer:  If your default Windows settings won’t access the controller, follow these steps to reach the controller’s IP.  You'll find a more extensive explanation in the user's manual. Details for setting up via the keypad can be found here.

Before adding an IP, close network programs and browsers.

Go to the Network Settings – Local Area Network or use the keyboard shortcut <Windows-R> - type “ncpa.cpl” and click OK. 

Right click on your LAN connection and choose “Properties”

Highlight “Internet Protocol” and click the “Properties” button.

Make note of the current settings.

Select "Use the following IP address".

Enter an IP address such as 192.168.0.5.

Enter a subnet mask of 255.255.255.0.

Delete any gateway entry.

Close all windows for the configuration to take effect.

Start your Browser and type 192.168.0.100 in the URL field. The index page should be displayed.

The default user name is "admin" (lower case) and password is “1234”

Set the IP address of the unit to your network, then restore your settings.
Question:  How can I change the NTP servers?
Answer:  Log into the unit and choose the External APIs link.
If the REST API is not enabled, check the REST API checkbox and press submit.
Either:
  Scroll down to the "Browse the REST API" link
  Select config
  Select ntp_peers
or
  enter it manually  Eg: http://192.168.0.100/restapi/config/ntp_peers/

Now you can select NTP peer #1 and edit it
Click the PUT button.
Edit or delete the other NTP peers as needed.
Question:  Can I set the session timeout longer?
Answer:  Yes
Log into the unit and choose the External APIs link.
If the REST API is not enabled, check the REST API checkbox and press submit.
Scroll down to the "Browse the REST API" link <strong>or enter it manually  Eg: http://192.168.0.100/restapi/
Select the auth (Authentication server object) link
Select Cookie timeout Eg: http://192.168.0.100/restapi/auth/cookie_timeout/

Enter a time in seconds.
3600 = 1 hour
7200 = 2 hours
86400 = 1 day
604800 = 1 week
31536000 ~ 1 year

Click the PUT button.

The next time you login, the timeout will take effect.
Question:  Can I increase the internal system log size?
Answer:  Yes, but this must be done using the SSH shell.

Log into the unit via SSH.
The default is 16KB; to make it 64, use these commands:

uci set system.@system[0].log_size=64
uci commit system
/etc/init.d/log restart

*Note that this will clear the log.
Question:  How to I install a supported VPN?
Answer:  Currently OpenVPN, Tailscale, ZeroTier, NetBird and innernet are supported in the latest firmware.

These must be installed and configured using SSH.
OpenVPN:
cd /tmp
opkg update
opkg install openvpn

Edit the /etc/config/openvpn file
https://openwrt.org/docs/guide-user/services/vpn/openvpn/client
/etc/init.d/openvpn start

*The configuration is retained across firmware updates.
  The package must be reinstalled unless the firmware is 1.13.1.0 or higher and the "Preserve user installed packages" is checked in the Firmware Upload page before the udpate.

The VPNs options below require firmware 1.12.7.0 or higher. (Firmware 1.12.11.0 or higher recommended)

ZeroTier:
cd /tmp
opkg update
opkg install zerotier

edit /etc/config/zerotier and write the network ID
/etc/init.d/zerotier restart
The device appears in the net in the zerotier web UI control panel but isn't authorized (and thus has no IP)
Tick the Auth checkbox, and it gains an IP.

*The configuration is retained across firmware updates.
  The package must be reinstalled unless the firmware is 1.13.1.0 or higher and the "Preserve user installed packages" is checked in the Firmware Upload page before the udpate.

Tailscale:
cd /tmp
opkg update
opkg install tailscale-combined
tailscale up

You will be prompted to authorize the device (copy the URL and paste into the browser):

*The configuration is retained across firmware updates.
  The package must be reinstalled unless the firmware is 1.13.1.0 or higher and the "Preserve user installed packages" is checked in the Firmware Upload page before the udpate.

NetBird:
FIRST prepare a netbird account AND verify the email (activation will otherwise fail).
cd /tmp
opkg update
opkg install netbird
netbird up

You will be prompted to authorize the device (copy the URL and paste into the browser)

*The configuration is retained across firmware updates.
  The package must be reinstalled unless the firmware is 1.13.1.0 or higher and the "Preserve user installed packages" is checked in the Firmware Upload page before the udpate.

Innernet summary: (requires 1.12.9.0)
This release includes two new installable packages, innernet and innernet-server supporting, as of now, Linux and Mac OS only (no Android, Windows, etc.).
They enable you to build kernel-mode-routed mesh networks based on the Wireguard protocol, but there's no central server: you need to host it yourself by installing "innernet-server" on a device with a public IP, installing "innernet" and following the documentation (both packages have a text-mode user interface for configuration).
The summary is that it may be tricky to configure and limited to UNIX-like systems, but shaves off ~15% of median ping time, reduces RAM usage and CPU load, and isn't controlled by third parties.
Question:  How can I clean up old certificates from prior firmware versions?
Answer:  Beginning with firmware 1.12.14.0, you can get a list of certificates not shipped with the current firmware via the RESI API.
http://192.168.0.100/restapi/config/certificates/all;custom=true/
or curl e.g.:
curl -u admin:1234 -H "Content-type: application/json" --digest http://192.168.0.100/restapi/config/certificates/all;custom=true/
You can delete selectively via SSH or the REST API.

To delete all certificates not shipped with the current firmware via curl e.g.:
curl -u admin:1234 -X DELETE -H "X-Requested-With: XMLHttpRequest" --digest http://192.168.0.100/restapi/config/certificates/all;custom=true/

Alternatively, a full reset will clear them.
Perform a complete backup, except uncheck the "Trusted certificate and revocation list store".
Perform the full reset (complete wipe).
Restore from backup.
Question:  How can I install my own certificate?
Answer: 

Your certificate and key must in PEM format with the certificate being the full chain.

Once created, login via SSH and place them into /etc/uhttpd.key and /etc/uhttpd.crt, respectively.
Next run:
/etc/init.d/uhttpd
restart

Question:  When I unplug the Ethernet cable, WiFi quits working.
Answer:  This happens when the Wired and WiFi are on the same network and subnet.
1. Change the LAN Metric to 1. This resolves most of these issues. (Firmware 1.9.8.0+)



If you plan to run the WiFI and Ethernet on the same network continually or still have issues;

2. Change the last character of the WiFi MAC address.
e.g. http://192.168.0.100/restapi/network/wireless/mac_address/

Changing the last HEX number is all that is required.
Question:  How do I fix: email notification failed: [CURL-EASY][COULDNT_RESOLVE_HOST] Couldn't resolve host name (6)?
Answer:  1. Verify that "Same subnet only" is unchecked in the General Network Settings
2. Verify that a gateway is entered in Network Settings
3. Verify that a DNS server are entered in Network Settings
Question:  How do I fix: [CURL-EASY][PEER_FAILED_VERIFICATION] SSL peer certificate or SSH remote key was not OK (60),
Peer certificate cannot be authenticated with given CA certificates (60) or
Certificate renewal error "failure while reading service directory".
Answer:  If the firmware version is below 1.9.x, then update the firmware to support the latest certificates.

Otherwise, log into the unit via SSH.
Type:
ls -l /etc/ssl/certs/

You'll likely see the .crt files but no symlinks like 12345678.0 -> XXX.crt.
Type or copy/paste:

rm -f /etc/ssl/certs/[0-9a-f]*.[0-9]
uci delete system.__dliconf_trust_all_known_root_ca_certificates
uci commit system
sh /rom/etc/uci-defaults/trust-all-known-root-ca-certificates

uci: Entry not found      < -- This is normal
then check that
ls -l /etc/ssl/certs/

shows the symlinks have appeared.
Question:  How do I clear "SECURITY LOCKOUT IN PLACE" when I try to login?
Answer:  When you enter an incorrect password or use an old "hidden key" too many times, you may be *locked out.

In the Settings page is a "Delays" section. The duration of the security lockout is set there:


There are a few ways to end the lockout.
Option A. Don't access the unit until the lockout expires

There are three ways to end the lockout prematurely without power-cycling.
Option B. Press the reset button and choose option 1 or option 6:
Press and release the reset button. After about 5 seconds, you will hear a beep, then use the up and down keys to choose the type of reset.
The following reset modes are available:

1. Clear lock bits: Clear protection bits only. Other settings are preserved.
2. Reset Net&Script: Clear protection bits, reset network settings and admin login, disable autoping and scripts. Other settings are preserved.
3. Reset + WiFi:   Clear protection bits, reset network settings and admin login, disable autoping and scripts, and enable open WiFi access. Other settings are preserved.
4. Complete wipe: Reset all settings to factory defaults and remove any user files. All settings will be lost!
5. Wipe + WiFi: Reset all settings to factory defaults and remove any user files, then enable open WiFi access. All settings are lost!
6. Reboot: Reboot only. All settings are preserved.  (firmware versions 1.12.14.0+)

To activate the selected reset mode, press cycle or the reset button and hold it.


Option C. Login via SSH and type:
reboot

Option D. Login via SSH and type:
/etc/init.d/generic_state_server restart

* To help prevent lockouts: With each visit to the login page a secret key is generated. If another key is generated because someone else brought up the page after you did, then the key has expired. Before logging in, press the F5 key to refresh the browser if it has been some time since going to the login page. If you make a mistake on the password and press the "back" button on the browser to go back and try again, press F5 to refresh the page and get a new key. If you don't do this, you are using the old key and will get locked out.
Question:  How do I fix a "Host request header not present or not recognized" error when I try to login from a different network?
Answer:  Firmware 1.12.12.0+ supports "Host request header filtering for DNS rebinding protection".
Login via a local IP address and check the "Allowed Hostnames setting in the general network settings section.
If the top field empty, enter an asterisk ( * ) in and submit the changes. For better security, see below:



If the unit is accessible only via a private (e.g. RFC1918) IP address, a malicious site can manipulate its DNS entry to trick your browser into sending a request to the private address. Host header restriction can used to prevent such DNS rebinding attacks. The default permitted list contains just the wildcard "*" for backwards compatibility. To enable the protection, add patterns for hostname(s) you use to address the unit to the list and remove the "*" wildcard.

AFTER REMOVING THE "*" WILDCARD, THE UNIT MAY ONLY BE REACHED VIA HOSTNAMES MATCHING THE PATTERNS LISTED, OR BY ITS LOCAL IP. If connectivity is lost, use a local connection as discussed above and use the explicit IP address, which always is an allowed Host header value.

Hostname patterns support the following special sequences:
"*" stands for any sequence of characters, e.g. "*.example.com" will match "pcr.example.com" and "another.pcr.example.com"; "${hostname}" stands for the current unit hostname (as configured), and will usually be used for as part of a fully-qualified domain name (e.g. "${hostname}.example.com") for uniform configuration between several units.
Question:/i>  My program used to run fine on an earlier model, but won't run on this one. What can I do?
Answer:  It's possible that the program requires legacy login methods which accept plaintext authentication. Go to the Setup page and tick the "Allow legacy plaintext login methods" checkbox, then click "Submit".
If the program works, please inform the author that the preferred authentication method is by using the more secure challenge/response mechanism. Have a look at the Rest API here for new development. 
Question:  I can't access the controller from another network. Autoping will not ping an external server such as 8.8.8.8. How do I fix it?
Answer:  1. First make sure the "Same subnet access only" is unchecked in the General network settings



2. Next, verify that the network gateway is correct. It is usually the same gateway as your computer uses.

Gateway

The issue should be resolved.



If the issue remains (very rare):
3. Enable SSH
 
Login via SSH and type route
Look for a default route entry as shown here: 

#route 
Kernel IP routing table
Destination    Gateway         Genmask        Flags  Metric  Ref  Use  Iface
default        192.168.11.1    0.0.0.0         UG      0      0    0   eth0
192.168.11.0   *              255.255.255.0   U       0      0    0   eth0
Only if you don't see a default route and items 1 and 2 are verified, enter these commands into the SSH shell.

/etc/init.d/default_route_manager stop
/etc/init.d/default_route_manager disable
rm /etc/udhcpc-filters/500-divert-default-route-updates
/etc/init.d/network restart

*Let support@digital-loggers.com know that these default_route changes were made.
Question:  Can you develop custom firmware for my application?
Answer:  Gladly.  We've done this for many customers.  After we agree on a -very specific- project description, we can send you an estimate of the time involved to code, debug and test. In most cases, a kick-off meeting in Silicon Valley is required.
Question:  Do you support HomeSeer?
Answer:  Yes! Alex Khassapov has created a plugin for HomeSeer.
Question:  Can you develop custom hardware for my application?
Answer:  Gladly.  We've done this for many customers.   Please call with your requirements.  To amortize NRE, practical minimum order quantities are typically 100-1000 units.  In most cases, a kick-off meeting in Silicon Valley is required.
Question:  Do you support PowerMan?
Answer:  Yes, absolutely.  The latest code is added to the tarball. Download the latest User Utility here.
Question:  What is the blue LCD for?
Answer:  The blue LCD shows outlet status during power up, the IP address, netmask, outlet names, and other useful information.  Time and date stamps for significant events (such as power outages or emergency shutdowns) are also displayed. Using the keypad, you can set up some of the features such as the network settings.  You can program this display to display your own messages using the scripting feature.
Question:  How does the sensor port work?
Answer: 

 

 

The sensor port is an ESD protected TTL level bidirectional port.  It's suitable for Dallas 18B20 or DHT11 style sensors. The RJ12 pinout is: 1 &2 - 5V power out. 5V current is limited to about 50mA.  Pins 3 Data (bidirectional) & clock. Pin 4 is ground. The power controller will automatically detect the attached sensor, and it can be interrogated via the RestAPI. There is also a DB-9 connector for expansion or custom-built peripherals.  Email engineering@digital-loggers.com with your needs and suggestions.
Question:  How do the meters work?
Answer:  The Ethernet Power Controller 7 has four internal meters.  Bus A and Bus B each have one separate current and voltage meter.  The voltage meters measure the input voltage on each bus.  The current meters measure the total current drain for all the switched devices on each bus.  One un-switched outlet on each bus bypasses the meters to provide un-metered "house power". Keep this in mind when planning your wiring. The un-switched outlets are located in the center of the panel.  Although the product will easily handle 15A on each bus, it's recommended to stay in the 13A range or so to leave headroom for dynamic loads. The circuit breakers are a "guaranteed hold" at 14.8A.  There is a manual power factor correction which can be entered for each bus to correct known non-PFC loads.  Histograms and meter readouts can be customized to suit your needs. Two cumulative energy meters are provided. They accumulate power use over time to display energy in kWh. 
Now that the firmware now includes internal notification, so no external utilities are necessary. In version 7, the voltage metering time constant has been changed to ~1500ms.  DB9 ADC inputs may also be supported in future firmware releases.
Question:  How do I enable the battery backup? How long will the battery run?  What is the battery lifetime?
Answer:  Open the battery hatch on the right side of the faceplate by gently pressing the tab behind the faceplate to the right and pulling the hatch cover forward.  Connect the polarized battery connector, positive-to-positive, negative-to-negative.  The battery will power the web server, internal logic, Ethernet, RS-232 port and LCD for several minutes during a power outage.  Recharge time to 90% capacity is 48 hours.  Batteries are Li-ION.  Typical battery life is 24 months at 100F.  Do not attempt to replace the battery with any other type of cell.  Inexpensive replacement batteries are available from digital Loggers (408) 330-5599.  Disconnect the battery if you leave the power controller shut off for more than a month.

Back To Top

 

If we haven't answered your questions here, please call (408) 330-5599 or send us an email.  We'll be glad to help.


© Digital Loggers, Inc. 2005-2020.