<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://doc.eze.io/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://doc.eze.io/feed.php">
        <title>ezeio documentation - ezeio2:userinterface:configuration</title>
        <description></description>
        <link>https://doc.eze.io/</link>
        <image rdf:resource="https://doc.eze.io/_media/logo.png" />
       <dc:date>2026-04-25T10:23:12+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/alarms?rev=1666105492&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/calendar?rev=1632520675&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/devicelist?rev=1715196591&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/fields?rev=1716219459&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/scheduler?rev=1632520675&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/script?rev=1632520675&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/start?rev=1632783351&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/system?rev=1746655658&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/userinterface/configuration/timers?rev=1632521027&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://doc.eze.io/_media/logo.png">
        <title>ezeio documentation</title>
        <link>https://doc.eze.io/</link>
        <url>https://doc.eze.io/_media/logo.png</url>
    </image>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/alarms?rev=1666105492&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-10-18T15:04:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Alarms</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/alarms?rev=1666105492&amp;do=diff</link>
        <description>Alarms



Alarms are user configured event triggers (Each ezeio is limited to 200 alarms). An alarm is triggered by an “Alarm condition” and stays in alarm until the “Restore condition” is true (or until it is forced off). On their own alarms do not do anything, other than switch on or off like a digital flag.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/calendar?rev=1632520675&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-24T21:57:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Calendar</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/calendar?rev=1632520675&amp;do=diff</link>
        <description>Calendar



The “Calendar” feature works in tandem with the “Scheduler”. It can be used as the primary way of applying schedules (seasonally for example) or as a way to mark exceptions to the weekly schedule (such as holidays or school minimum days). The calendar has no independent functionality, it is dependent on the</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/devicelist?rev=1715196591&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-08T19:29:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Devices &amp; Drivers</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/devicelist?rev=1715196591&amp;do=diff</link>
        <description>Devices &amp; Drivers



The “Device” page is where most links to hardware and data sources are created. This is done through the addition of drivers. Drivers are application programs that (in most cases) establish a communication link to hardware and provide an eze.io interface. This is similar to drivers, programs and apps that you would load on your phone, tablet or personal computer. For some such as</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/fields?rev=1716219459&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-20T15:37:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Fields</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/fields?rev=1716219459&amp;do=diff</link>
        <description>Fields



Fields are the user configured points that an ezeio logs in onboard memory and sends to the Cloud. Up to 90 can be added per ezeio. These are typically mapped to inputs or outputs, but can be used to create counters, set points, constants, sums, differentials, averages, and more. The possibilities are truly endless. Each Field is evaluated every tenth of a second by the ezeio&#039;s Expression engine. The result can be visualize on Dashboards, trigger alarms, drive automation as well as bei…</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/scheduler?rev=1632520675&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-24T21:57:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Scheduler</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/scheduler?rev=1632520675&amp;do=diff</link>
        <description>Scheduler



This tool can be used in many ways for many purposes, such as operational hours and irrigation schedules. The “Scheduler&#039;s” features allow for a great amount of flexibility. The schedules are passive in nature having no directly connected actions. The result of a schedule is a status of;</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/script?rev=1632520675&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-24T21:57:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Scripts</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/script?rev=1632520675&amp;do=diff</link>
        <description>Scripts



The features of the ezeio MkII system provide tremendous configurability to create monitoring, alarming, controlling and automation solutions, but for some applications, this may not be enough. To allow users to create custom functionality, the ezeio™ system supports the PAWN script language. PAWN has a C-like syntax and executes completely inside the ezeio. The</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/start?rev=1632783351&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-27T22:55:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuration Screen</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/start?rev=1632783351&amp;do=diff</link>
        <description>Configuration Screen



By default, the ezeio will connect to the cloud servers and synchronize data in both directions. This functionality is not optional, and normally requires no configuration. There are also a lot of other basic functions in the ezeio that always runs, such as scanning inputs, managing the power supply, keeping correct time etc.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/system?rev=1746655658&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-07T22:07:38+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>System</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/system?rev=1746655658&amp;do=diff</link>
        <description>System



The System tab provides meta data, performance metrics, and user defined settings individual ezeio controllers. The window is divided in half with System information on the left and System settings on the right. We recommend naming the each ezeio and setting the time zone, all additional system settings are optional.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/userinterface/configuration/timers?rev=1632521027&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-24T22:03:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Timers</title>
        <link>https://doc.eze.io/ezeio2/userinterface/configuration/timers?rev=1632521027&amp;do=diff</link>
        <description>Timers



The timer feature is based on the software utility “cron”. The purpose is to trigger reoccurring actions such as “Set register” or “Force alarm”. Cron expressions are entered into each of the “Time setting” fields to describe the periodic interval for an action. The cron expressions work as filters. At the beginning of every second, the timer evaluates each filter&#039;s true or false status. If all of the cron expression are true compared to the current date &amp; time the action will be trigg…</description>
    </item>
</rdf:RDF>
