The IzoT Router has a built-in IzoT Server that allows you to monitor and control external devices (e.g., FT 6000 devices)
If you are using a Self installing ISI network then the IzoT Router should always detect the external devices, on the same subnet, Service Pin but if you are using IzoT CT or IzoT Net Server network then you need to configure the IzoT Router to detect the external device service pin messages.
Devices show up in the IzoT Server either by pressing the devices Service pin or by manually entering the device's Neuron ID. A valid Device Class File is needed for each device type that you try to use.
1. IzoT Server Device Browser shows detected devices
The Device Browser shows the up and running external devices.
If you don't see a device then check the Show all devices checkbox to see all devices in the Server database. The "Show all devices" view shows all detected devices including devices in which a valid Device Class File was not found. If the device has a red circle then the device is truly off line or missing a Device Class File.
You may also see a problem with there is another Device Class File with the same Program ID (that is, you can't have two Device Class Files with the same Program ID in the IzoT Server)
2. Change IzoT Server lonbridge config.xml file (not needed for ISI networks)
If a CT or IzoT Net Server network then you also need to configure the lonbridge config.xml to use the Domain ID used by the CT/IzoT Net network before devices will be detected.
/home/debian/izot-sdk/etc/lonbridge/config.xml
The following config.xml file shows the setting for single byte domain ID = 8. You will also need to add a subnet ID/node Id that isn't being used. The subnet ID is the subnet ID of the IP side of the IzoT Router. The Node ID is an unused Node ID (one that isn't used by the CT or IzoT Net network. In this case we are using
<bridge>
<id value="lon1" />
<interface value="default" />
<ip value="127.0.0.1" />
<port value="3050" />
<pollrate value="1.0" />
<logging value="general" />
<isi value="disable" />
<subnetnodeid value="5/250" />
<domainid value="1, 3 0 0" />
</bridge>
See "Configuring the IzoT Network Server" section in the IzoT Manual for more details.
3. Did you add the Device's Device Class File to the IzoT Server
Each device type has a Device Class File with a unique program ID that specifies the devices datapoint types that you will see in the Server. If there is a missing Device Class File or invalid file then you will see them show in the Device Browser with Show all devices checkbox checked.
/home/debian/izot-sdk/etc/lonbridge/classes
See "Mapping IzoT Device Datapoints to IzoT Server Datapoints" in the IzoT Manual for more details.
4. Manually Entering the Device's Neuron ID
In the case where you can't press the external device's service pin button, you can manually add
/home/debian/izot-sdk/etc/lonbridge/instances/devices.xml
Sample
<devices>
<device nid="00D07105C253" id="7" fblock="-1" type="unknown" name="Unknown Device" brand="IzoT" active="false" pid="8000010101010421" />
<device nid="00D07110020D" id="1" fblock="-1" type="room_controller" name="FT_6000_Multi_Sensor" brand="Echelon" active="true" pid="9FFFFF0501840430" illuminance="35841" temperature="102" switch-setting-1="off" switch-state-1="off" state-setting- 1="off" state-1="off" switch-setting-2="off" switch-state-2="off" state-setting-2="off" state-2="off" />
</devices>
See "Adding a New Device" in the IzoT Manual for more details on manually adding exernal devices using the Device's Neuron ID.