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.
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:
Sent when device got registered for some gateway
Sent when some changes happened to a device (contains only changes)
Sent when a device got unregistered from some gateway.
Sent when an item got registered for some device (can be sent only as a part of a device.added sequence).
Sent when some changes happened to an item (contains only changes).
Sent when some changes happened to an dictionary item.
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)