<?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:drivers:doc</title>
        <description></description>
        <link>https://doc.eze.io/</link>
        <image rdf:resource="https://doc.eze.io/_media/logo.png" />
       <dc:date>2026-04-25T10:11:13+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/accumulator_diff?rev=1716413457&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/apogee_sp522?rev=1716414300&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/atmos22?rev=1719525266&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/bewis_accelerometer?rev=1716477748&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/cs320?rev=1716478288&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/cs_va520?rev=1716477916&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/demand_monitor?rev=1716412514&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/discreteinput?rev=1715268624&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/discreteoutput?rev=1715272460&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/ee_press_diff?rev=1716501846&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/ee_temp_rh?rev=1716501461&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/fields_via_lan?rev=1719874254&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/formc?rev=1717447200&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/gps_gn803g?rev=1715363813&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/gps_gn8603g?rev=1715364279&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/gps_mr350s4?rev=1715364478&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/hukseflux_sr05?rev=1716502123&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/iot-s300aq?rev=1718652332&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/iot-s300nois?rev=1716502961&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/modbustool?rev=1715296392&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/pid?rev=1716412337&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/pulseinput?rev=1715272589&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/runtime?rev=1716411360&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/shelly_relay?rev=1716412830&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/systeminfo?rev=1715268367&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/temp_rh1020?rev=1715364791&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/thermistor?rev=1715295736&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/tz_temp_rh1030?rev=1715368018&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/vantage_pro2?rev=1716501087&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/wattnode_basic?rev=1715369064&amp;do=diff"/>
                <rdf:li rdf:resource="https://doc.eze.io/ezeio2/drivers/doc/weather_forcast?rev=1715369751&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/drivers/doc/accumulator_diff?rev=1716413457&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-22T21:30:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Accumulator Difference driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/accumulator_diff?rev=1716413457&amp;do=diff</link>
        <description>Accumulator Difference driver

Description

This driver monitors an accumulating field value, for example an energy (kWh) or volume (L) register that continuously counts up. The driver captures the field value at a given interval (hourly, daily etc..) and computes the difference between the start and end of the interval. Current value and the four previous are provided.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/apogee_sp522?rev=1716414300&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-22T21:45:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Apogee SP-522 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/apogee_sp522?rev=1716414300&amp;do=diff</link>
        <description>Apogee SP-522 driver

Description

The SP-522-SS is an upward-looking thermopile pyranometer with a digital signal using Modbus RTU protocol over RS-232 or RS-485. The sensor incorporates a blackbody thermopile detector and acrylic diffuser with a rugged, self-cleaning sensor housing design, and high-quality cable terminating in pre-tinned pigtail leads for easy connection to dataloggers and controllers.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/atmos22?rev=1719525266&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-27T21:54:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>METER ATMOS 22 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/atmos22?rev=1719525266&amp;do=diff</link>
        <description>METER ATMOS 22 driver

Description

This driver is design to allow communication with the sensor via SDI-12. This sensor provides air speed, direction and temperature readings. 

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/bewis_accelerometer?rev=1716477748&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T15:22:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Bewis Compass &amp; Accelerometer driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/bewis_accelerometer?rev=1716477748&amp;do=diff</link>
        <description>Bewis Compass &amp; Accelerometer driver

Description

This driver is design to allow communication with the Bewis two axis accelerometer and compass via Modbus RTU.   

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/cs320?rev=1716478288&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T15:31:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Campbell Scientific CS320 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/cs320?rev=1716478288&amp;do=diff</link>
        <description>Campbell Scientific CS320 driver

Description

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/cs_va520?rev=1716477916&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T15:25:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>CS Instruments VA520 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/cs_va520?rev=1716477916&amp;do=diff</link>
        <description>CS Instruments VA520 driver

Description

This driver is design to allow communication with the VA520 via the ezeio&#039;s Modbus RTU serial port.   

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/demand_monitor?rev=1716412514&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-22T21:15:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Demand monitor</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/demand_monitor?rev=1716412514&amp;do=diff</link>
        <description>Demand monitor

Description

This driver produces metrics based on user defined energy consumption within a specified demand (time) window and instantaneous power reading from a connected power/energy meter. The resulting values can be used to drive demand shift automation in order to stay under demand window limits.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/discreteinput?rev=1715268624&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-09T15:30:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Discrete Input driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/discreteinput?rev=1715268624&amp;do=diff</link>
        <description>Discrete Input driver

Configuration settings (center panel)

Description

This driver (located in the Core drivers folder) is designed for use with the ezeio MkII controller and the ezeio MkII I/O Expander. It is ideal for reading resistance (Ohms), and sensors with DC current (0-30 mA) or voltage (0-10 VDC) signals.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/discreteoutput?rev=1715272460&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-09T16:34:20+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Discrete Output driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/discreteoutput?rev=1715272460&amp;do=diff</link>
        <description>Discrete Output driver

Description

This driver (located in the Core drivers folder) is designed for use with the ezeio MkII controller and the ezeio MkII I/O Expander.

----------

Configuration Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/ee_press_diff?rev=1716501846&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T22:04:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>E+E Differential Pressure Sensor driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/ee_press_diff?rev=1716501846&amp;do=diff</link>
        <description>E+E Differential Pressure Sensor driver

Description

This driver is design to allow communication with E+E Elektronik&#039;s EE610 pressure differential sensor, via the ezeio MkII&#039;s Modbus serial port. 

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create th…</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/ee_temp_rh?rev=1716501461&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T21:57:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>E+E Temperature &amp; Humidity driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/ee_temp_rh?rev=1716501461&amp;do=diff</link>
        <description>E+E Temperature &amp; Humidity driver

Description

This driver is design to allow communication with E+E Elektronik&#039;s EE210 humidity sensor, via the ezeio MkII&#039;s Modbus serial port. The driver may be compatible with other E+E humidity sensors with Modbus connectivity, such as EE072, EE150, and EE211.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/fields_via_lan?rev=1719874254&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-07-01T22:50:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ezeio Fields via LAN driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/fields_via_lan?rev=1719874254&amp;do=diff</link>
        <description>ezeio Fields via LAN driver

Description

This driver allows one ezeio access to the Fields of another ezeio/s over a local network. All 90 “Fields” are presented as “Available registers”. Both ezeio must be on the same IP subnet.  

----------</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/formc?rev=1717447200&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-03T20:40:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Form C alarm contact driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/formc?rev=1717447200&amp;do=diff</link>
        <description>Form C alarm contact driver

This driver allows monitoring a Form-C (SPDT) contact, or two SPST (Form-A/B) contacts using a single ezeio input.

Using a few resistors, the driver can monitor each contact state individually, and also indicate if there is a wiring fault (short or open), all with just a single input. Note that the resistors shall be located physically as close to he monitored contact as possible to achieve the desired security function.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/gps_gn803g?rev=1715363813&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T17:56:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>GPS receiver GN-803G driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/gps_gn803g?rev=1715363813&amp;do=diff</link>
        <description>GPS receiver GN-803G driver

Description

This driver is design to allow communication with the GN-803G (TTL/UART) GPS receiver through the ezeio MkII&#039;s SDI-12 serial port or input #8 on ezeio with serial numbers BBx-xxx and higher.   

----------

Configuration settings (center panel)</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/gps_gn8603g?rev=1715364279&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T18:04:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>GPS receiver GN-8603G driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/gps_gn8603g?rev=1715364279&amp;do=diff</link>
        <description>GPS receiver GN-8603G driver

Description

This driver is design to allow communication with the GN-8603G (RS232) GPS receiver through the ezeio MkII&#039;s SDI-12 serial port.   

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/gps_mr350s4?rev=1715364478&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T18:07:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>GPS receiver GlobalSat MR350S4 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/gps_mr350s4?rev=1715364478&amp;do=diff</link>
        <description>GPS receiver GlobalSat MR350S4 driver

Description

This driver is design to allow communication with the MR350S4 (TTL/UART) GPS receiver through the ezeio MkII&#039;s SDI-12 serial port.   

----------

Configuration settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create t…</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/hukseflux_sr05?rev=1716502123&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T22:08:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Hukseflux Pyranometer SR05 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/hukseflux_sr05?rev=1716502123&amp;do=diff</link>
        <description>Hukseflux Pyranometer SR05 driver

Description

This driver is design to allow communication with the 

----------

Settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/iot-s300aq?rev=1718652332&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-17T19:25:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Linovison IOT-S300AQ Air Quality Sensor driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/iot-s300aq?rev=1718652332&amp;do=diff</link>
        <description>Linovison IOT-S300AQ Air Quality Sensor driver

Description

This driver is design to allow communication with the sensor via Modbus. This sensor provides instantaneous readings of the concentration of particulate matter. Readings are given for particles 2.5 microns or less and 10.0 microns or less. Using this information, the driver converts these reading into a US-EPA Air Quality Index value.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/iot-s300nois?rev=1716502961&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T22:22:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Linovison IOT-S300NOIS Noise Sensor driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/iot-s300nois?rev=1716502961&amp;do=diff</link>
        <description>Linovison IOT-S300NOIS Noise Sensor driver

Description

This driver is design to allow communication with the sensor via Modbus. This sensor provides instantaneous as well a 60 second min, max and average values in dB.

----------

Settings (center panel)</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/modbustool?rev=1715296392&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-09T23:13:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Modbus port tool driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/modbustool?rev=1715296392&amp;do=diff</link>
        <description>Modbus port tool driver

Description

The Modbus port tool driver provides the means to set RTU serial bus parameters and directly read / write to devices connected via RTU (serial bus) or TCP (Ethernet).    

Configuration settings

MODBUS RTU PORT SETTINGS</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/pid?rev=1716412337&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-22T21:12:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>PID control driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/pid?rev=1716412337&amp;do=diff</link>
        <description>PID control driver

Configuration settings (center panel)

Description

Single sensor input, single process variable output
Adjustable process speed, P/I/D and polarity

----------

Configuration settings (center panel)

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/pulseinput?rev=1715272589&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-09T16:36:29+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Pulse Input driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/pulseinput?rev=1715272589&amp;do=diff</link>
        <description>Pulse Input driver

Description

This driver (located in the Core drivers folder) is designed for use with the ezeio MkII controller and the ezeio MkII I/O Expander. Pulse outputs on common on meters for gas, water, and electrical. Most are designed to provide a volume total, such as liters or Kilowatt hours. The ezeio can also determine a flow rate based on the interval between pulses or the frequency (both methods can be employed by the driver to produce the most accurate flow value). This fea…</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/runtime?rev=1716411360&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-22T20:56:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Runtime / Service driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/runtime?rev=1716411360&amp;do=diff</link>
        <description>Runtime / Service driver

Description

This driver creates a runtime clock from a Field value. The runtime is then used to send service reminder messages, based on a user defined service interval. When scheduled service is completed, a reference number is entered to reset the service interval counter to zero.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/shelly_relay?rev=1716412830&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-22T21:20:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Shelly relay driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/shelly_relay?rev=1716412830&amp;do=diff</link>
        <description>Shelly relay driver

Description

This driver is designed for use with multiple Shelly relays via WiFi and Ethernet cable. Control logic features are identical to the those found in the eze Discrete output driver.

----------

Configuration settings (center panel)</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/systeminfo?rev=1715268367&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-09T15:26:07+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ezeio System Info driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/systeminfo?rev=1715268367&amp;do=diff</link>
        <description>ezeio System Info driver

Description

The ezeio MkII System Info driver provides system performance data as well as configuration settings for two of the ezeio&#039;s serial buses. In addition to the data and settings, registers 17 and 20 provide a means of locking in a location and measuring the units distance from that point, if it moves (requires a GPS receiver). This driver is loaded by default on units with serial numbers BBA and higher.</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/temp_rh1020?rev=1715364791&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T18:13:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Temp / RH Stick driver (TA1020)</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/temp_rh1020?rev=1715364791&amp;do=diff</link>
        <description>Temp / RH Stick driver (TA1020)

Description

This driver is designed for use with the temperature and humidity sensor sold by eze System (P/N TA1020). 

----------

Settings

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/thermistor?rev=1715295736&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-09T23:02:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Thermistor driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/thermistor?rev=1715295736&amp;do=diff</link>
        <description>Thermistor driver

Description

This driver is designed for use with the ezeio MkII controller and the ezeio MkII I/O Expander. 

----------

Settings

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/tz_temp_rh1030?rev=1715368018&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T19:06:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Temp / RH Sensor (TA1030)</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/tz_temp_rh1030?rev=1715368018&amp;do=diff</link>
        <description>Temp / RH Sensor (TA1030)

Description

This driver is designed for use with the temperature and humidity sensor sold by eze System (P/N TA1030). 

----------

Settings (Center panel )

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/vantage_pro2?rev=1716501087&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-23T21:51:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Davis Vantage Pro 2 driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/vantage_pro2?rev=1716501087&amp;do=diff</link>
        <description>Davis Vantage Pro 2 driver

Description

This driver is compatible with Davis Instruments, Vantage Pro 2 series weather station. Weather station connects directly to ezeio&#039;s SDI-12 port, bypassing the Davis (cabled) Vantage Pro2 Console.  

----------</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/wattnode_basic?rev=1715369064&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T19:24:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>WattNode driver (Basic)</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/wattnode_basic?rev=1715369064&amp;do=diff</link>
        <description>WattNode driver (Basic)

Description

This driver is designed for use with WattNode Modbus Module (WND) WattNode Modbus (WNC) and Multi-Circuit meter (MCM). This driver is included with the “Basic ezeio service” package and provides a limited set of power circuit measurements. The full set of measurements is available from the</description>
    </item>
    <item rdf:about="https://doc.eze.io/ezeio2/drivers/doc/weather_forcast?rev=1715369751&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-10T19:35:51+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Weather forcast driver</title>
        <link>https://doc.eze.io/ezeio2/drivers/doc/weather_forcast?rev=1715369751&amp;do=diff</link>
        <description>Weather forcast driver

Description

This driver provides 3 days of local weather forecast based on the ezeio&#039;s “system location”

Features

	*  3 Days of forcasts
	*  Updates every 4 hours
	*  18 Metrics

----------

Settings

Name - The name is up to the user. Our suggestion is to choose a naming convention that makes the viewing the device list intuitive. Such as referring to the sensor and/or application. Keep the name short as it will be combined with the register name to create the default…</description>
    </item>
</rdf:RDF>
