/
Defining Connection Assemblies
Defining Connection Assemblies
IzoT network devices can be 'hosts', 'clients', neither, or both. A host device advertises that it wants to find any other devices with matching datapoints that it can connect to.
A client device answers the call from any hosts that the client feels it is willing to match up with. To prepare the framework for registering blocks as hosts, or as clients, an assembly is needed for each block.
The following are two assemblies, one for the keypad, and another for the lux.
# ISI Assembly objects global lux_assembly global keypad_assembly keypad_assembly = izot.device.isi.Assembly( assembly = ( keypad.nvoLoadControl, keypad.nviLoadStatus), enrollment = izot.device.isi.Enrollment ( direction = izot.device.isi.IsiDirection.VARIOUS, type_id = keypad.nvoLoadControl)) lux_assembly = izot.device.isi.Assembly ( assembly = lux.nviAnalog, enrollment = izot.device.isi.Enrollment ( direction = izot.device.isi.IsiDirection.INPUT, type_id = lux.nviAnalog)) framework.assembly1 = keypad_assembly framework.assembly2 = lux_assembly
, multiple selections available,
Related content
Creating an IzoT Python Application
Creating an IzoT Python Application
More like this
Defining Blocks and Datapoints
Defining Blocks and Datapoints
More like this
Mapping IzoT Device Datapoints to IzoT Server Datapoints Overview
Mapping IzoT Device Datapoints to IzoT Server Datapoints Overview
More like this
Adding a New Device
Adding a New Device
More like this
Defining the Program ID
Defining the Program ID
More like this
Implementing a Device Property
Implementing a Device Property
More like this