Thank you for purchasing or considering the ezeio® !

The ezeio is a complete solution for monitoring, alarming, control and automation of commercial and industrial equipment.

The ezeio hardware connects to sensors, meters, thermostats, VFD’s and other control devices locally via a number of industry standard interfaces.

It connects securely and seamlessly via the Internet (Ethernet or Cellular) to the eze.io cloud application, where the user can access all data in real time as well as historical.

All configuration settings and programming is done via the cloud interface, allowing multiple concurrent users, automatic synchronization and secure access from anywhere without any special software or setup.

• Monitoring energy meters (electrical, water, gas)
• M&V applications (energy saving, improvements)
• Monitoring refrigeration systems (temperature, pressure)
• Controlling & monitoring HVAC systems (thermostats, room sensors)
• Construction site monitoring (cement curing, heating/cooling, alarms)
• Automating thermal energy storage systems (*TES)
• Technical alarm systems (fan monitors, temperature, tank levels)
• Lighting control, monitoring and scheduling/automation
• Irrigation control, monitoring and scheduling/automation
• Battery / EV charging, monitoring and control
• Vehicle tracking, monitoring (GPS)

The ezeio system is designed for easy deployment in geographically spread out, multi-dicipline applications where traditionally several single-purpose systems were needed.

The ability to support different kinds of sensors, meters, actuators and applications within a single, low cost yet complete and secure system makes the ezeio system unique.

Please contact eze System for other cloud-connectivity options.

Local connectivity includes;

Additional inputs and outputs can be added using ezeio expansion devices and/or third party devices.

Standard & Optional Features; ²⁾

• Data logging with over 50 days of local buffer storage ³⁾
• Flexible alarming functions
• Reporting to email, SMS, Voicecalls, Pushover, API and more
• Direct control from web
• Complete remote access to configuration and programming
• Easy to configure local logic
• Scheduling with 10 year calendar
• Powerful Scripting running on hardware
• REST API
• Built-in Real Time Clock
• Low power consumption (<1Watt)
• Smart drivers for common Modbus, SDI12 and CAN devices
• Multiple dashboards
• Easy management and hierarchical groups
• Unlimited user access with multiple permission levels from view only to full admin

The ezeio connects to the Internet via Cellular or Ethernet. A cellular modem is built in to the unit, but an external antenna is required. By default, if there is an Ethernet connection that allows Internet access, Ethernet is prioritized. If for any reason the Ethernet connection is not available, the ezeio will automatically switch to use the cellular connection. If the Ethernet becomes available after the cellular connection has been established, the ezeio will switch to the Ethernet after a few seconds.

All communication via Ethernet and Cellular is secure, encrypted and controlled. The ezeio is always a 'client', which means that it will actively seek a connection to the servers. Typically this means there is no special network configuration required, and the ezeio should be expected to work on any network setup - even behind routers and firewalls. However if the network blocks certain traffic or uses proxy technologies, there is a risk that the ezeio will not work on that network, and fall back to the cellular connection if coverage is available.

The ezeio connects to local sensors and devices through the green screw terminal. There are several connection options.

There are eight (8) discrete inputs on the ezeio. Each input can be individually configured to monitor voltage, current, resistance or pulses. The configuration is done via the web interface at https://eze.io.

More information about connecting to the inputs is available here.

There are four (4) discrete outputs on the ezeio. The function of each output is completely controlled by software.

Output 1 and 2 are purely on/off. The will output the supply voltage when on, and no voltage when off.

Output 3 is a Pulse Width output. It will output a 50Hz rectangular wave, with duty cycle from 0-100%. The high state is the supply voltage. This output can also be used as a regular on/off output by only setting it to 0 and 100% in software.

Output 4 outputs an analog voltage between 0 and 10V. The software controls this in 100mV steps (0-100%).

More information about connecting to the outputs is available here.

SDI-12 is a bidirectional communications protocol for relatively simple sensors, and commonly used for monitoring environment data. See http://www.sdi-12.org for more details.

The ezeio supports the standard SDI-12 protocol and multiple drivers are available for different types of sensors. The SDI-12 port can also be used as a generic serial input to read GPS data and other nonstandard devices.

More information about SDI-12 is available here.

Modbus/RTU is also a bidirectional communication protocol, but faster and more powerful than SDI-12. Developed 1979, it is still by far the most common protocol in industrial automation systems, and supported by multiple manufacturers in many industries.

The ezeio supports standard Modbus/RTU as a 'master', meaning the ezeio controls the communication between multiple devices. eze System provides drivers for many types of devices from various manufacturers.

Several devices can be connected at the same time on the same Modbus/RTU cable. The protocol is very robust, uses low cost bulk wires and can be used in noisy environments and over long distances.

More information about Modbus/RTU is available here.

Modbus/TCP is similar to Modbus/RTU, but uses Ethernet network signalling to connect to the devices. This allows for faster data transfers than over Modbus/RTU and has the benefit of using standard plug-and-play Ethernet hardware (switches, cabling). Modbus/TCP can be routed using standard WiFi hardware, allowing one ezeio to communicate directly to another ezeio or other device within range. The downside is somewhat more complex configuration, shorter range without using additional hardware and higher device cost.

The ezeio supports standard Modbus/TCP as both a 'server' and a 'client'. There are multiple drivers available for various devices.

More information about Modbus/TCP is available here.

The ezeio has a CAN port, which by default is used for expanding the system with additional I/O hardware and terminal made by eze System. When used for this purpose, the protocol is proprietary to eze System, and other devices cannot be connected to the CAN port.

The CAN port is controlled by software and may be configured for other protocols, such as NMEA2000, J1939, DeviceNet or CANopen. Please contact eze System for options.

The ezeio will automatically connect to the cloud services when power is applied. It is designed to be always-on, and always stay connected to the servers. If the communication is interrupted, the ezeio will automatically attempt to reconnect until the connection is restored.

The user can configure each ezeio with multiple sensors and devices, to collect data (log), set alarm conditions, construct automation logic and directly remote control the units.

All configuration is managed through the cloud portal at https://eze.io. Any changes to the configuration of an ezeio unit is stored in the cloud databases, and automatically synchronized to the unit as soon as possible - typically within a few seconds assuming the unit is powered up and connected.

Captured data is first buffered in the built-in memory, which holds over 50 days of 10 minute interval data, or 300000 samples at other intervals. Buffered data is uploaded automatically to the cloud databases as soon as the connection allows, and can be easily viewed in real time or historically, and downloaded as CSV or via API. The data is kept in the servers databases for a minimum of three years.

If the ezeio is programmed to trigger alarm events, messages can be sent via email, SMS, Pushover or voice calls to any number of recipients. The conditions that trigger such events is completely user programmable, and can be changed at any time from the portal.

The user may construct any logic using a powerful scripting language, and download this logic into the ezeio unit(s). Such logic will run independent of the servers.

On the server/portal side, the user may manage multiple units, provide access to multiple users with varying privileges, design dashboards, reports and have a quick overview of the real-time state of all units. The system scales easily from a single ezeio to thousands.

The ezeio hardware is highly optimized for its purpose. An embedded microcontroller (ARM Cortex-M4) manages all the communications, logic, I/O's, ports and memories. There are several different types of memory chips for programs, configuration, recorded data and status, as well as power management, I/O interfaces, real-time clock/calendar etc. The inputs and outputs are protected against excessive voltages/currents and the hardware is designed for wide temperature and rugged for interference expected in harsh environments.

There are no provisions for directly connecting to the hardware for configuration. All configuration is managed through the servers https://eze.io.

The ezeio runs a proprietary software stack, designed from scratch by eze System. The software is embedded in the microcontroller and runs immediately when power is applied. The configuration, drivers and user designed logic is synchronized automatically from the cloud servers, and runs locally on the ezeio.

Each ezeio unit has unique keys for validating with the ezeio cloud system and will refuse any other attempts to communicate than with the ezeio servers. The system is inherently secure, designed for direct use on the public Internet with no need for additional VPN, firewalls or other third-party security measures.

In case the communication is interrupted, all logic continues to run, and any messages/log data is buffered and automatically sent to the servers when the communication is restored.