Core module and core module events in Ezlo hubs

According to architecture core module provides an access to a coreD functionality.
CoreD implements and supports the abstract model of gateways/devices/items to provide a universal way to control smart devices.
Gateway represents a communication domain or communication technology, like ZWave, Zigbee, Bluetooth, TCP/IP, SPI, RS232, etc.
Device represents a smart device to be controlled/monitored, like smart outlet, smart lock, smart switch, etc.
Item represents a virtual control point [vcp], like turn on/off, set some value, get current value, etc. Such virtual control point [pcp] gets mapped to a physical control point like electrical relay, shift register, AC/DC meter, etc.

example:

gateway: zwave
device: smart_lock_1
items: lock/unlock, set_password, get_password???

The Core module notifies a script subscribed by core.subscribe( "script_name" ) about state of the Core module. Structure of an event is table.

Type of events:

  • device_added
    Sent when device got registered for some gateway
  • device_updated
    Sent when some changes happened to a device (contains only changes)
  • device_removed
    Sent when a device got unregistered from some gateway.
  • item_added
    Sent when an item got registered for some device (can be sent only as a part of a device.added sequence).
  • item_updated
    Sent when some changes happened to an item (contains only changes).
  • item_dictionary_updated
    Sent when some changes happened to an dictionary item.
  • item_removed
    Sent when an item got unregistered from some device (can be sent only as a part of a device.removed sequence).

Detailed description of Core events:
Core Events - eZLO API.pdf (124.4 KB)

3 Likes

Best Home Automation shopping experience. Shop at getvera!

© 2020 Vera Control Ltd., All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules