Modify Device(s) in DeviceHub for One Litmus Edge

to modify device(s) with litmus excel add ins, you should be familiar with how devices work in devicehub docid\ tgmyvezsra7ydtegxdvv4 on litmus edge before you begin you have installed the litmus excel add ins extension see install litmus excel add ins docid\ gzdhbj1xzznddthyocuuu for details you have prepared a prepare a new tool file to manage devicehub device(s) docid\ clsf07wli 66k4rs xuih devices have been add device(s) to devicehub for one litmus edge docid\ ot0c1ugayykjzmqiybh8j to devicehub initial preparation open a new device management tool file in excel if prompted, enable content to allow the code to run make sure the the tool is set to one le for the connect to option modify device(s) import devices import the device settings for devices defined on litmus edge using the import device(s) wizard docid\ l0cy8amra80rny4x pt3k users can set a filter to reduce the number of devices shown as selection to the user search option select what type of filter is to be used device name mask set the filter to be applied will be ignored if search option is set to all the wizard will show what filter will be applied press the search button to pull the filtered list of devices from litmus edge the user will be shown the filtered list of devices matching their filter select the devices to import and press the import button notes users can choose between press new search to set another filter and search again if the list doesn't show the devices the user wanted to import select all devices using the checkbox in the header row select a group of devices by selecting their respective check box select one device by selecting the respective check box select no device and close the wizard pressing the close button instead the selected device(s) with their settings are imported into the sheet once finished, the user can either p erform another search using the new search button finish the import using the close button the action for each imported device is set to m for modify mandatory device settings users can modify these mandatory settings for a device device name the name of an existing device can be changed important this will change the topic for all tags and will cause other services like analytics, integrations or flows not be able to read the data device properties are a mandatory set of device settings, which are populated initially with a set of default values to connect to your plc, you will have to provide your specific device properties settings instead which you can provide through one of two options option 1 you can provide your specific device properties directly through the formula bar or through the cell you will need to be careful to not remove any of the key value pairs as well as keeping the json formatting accurate option 2 you can use the device properties wizard docid\ qn07nz6dlfdz1mdpqkijc this allows you to edit the device properties without the risk of potentially invalidating the json object modify any of the modify device(s) in devicehub for one litmus edge /#not mandatory device settings as needed notes you can repeat modifying modify device(s) in devicehub for one litmus edge /#mandatory device settings and modify device(s) in devicehub for one litmus edge docid 8kucg2iuuno0h68fubql0 for every device you need to modify before modify device(s) in devicehub for one litmus edge /#executing actions executing actions when all modify device(s) in devicehub for one litmus edge /#mandatory device settings and modify device(s) in devicehub for one litmus edge docid 8kucg2iuuno0h68fubql0 settings for all device(s) are set, they are ready to be modified it is recommended but not mandatory to verify the configuration first without executing the action by pressing the verify only button this will check that all required device settings are provided and logically correct and provide any finding to the user example below the user did select to have meta data but did not provide any important the tool can not verify if all provided device settings are factually correct for example it can not verify that the network address provided for the plc is the correct ip address the device(s) can be modified on litmus edge by pressing the verify + execute button this will check that all required device settings are provided and logically correct and provide any finding to the user if no issues have been identified, the tool will verify that the user wants to execute all the actions from the action column a add device(s) m modify device(s) d delete device(s) i ignore device(s) > do nothing to perform all actions, press the yes button the tool will perform all actions row by row when finished, a result summary is shown close the result summary by pressing the x close button the tool will ask if the user wants to re compare the device(s) against litmus edge to re compare, press the yes button to not re compare, press the no button if the user selected to press the yes button from aboves messagebox , the tool will pull all the device settings from litmus edge again including the deviceid and also change the action to m for each device with a deviceid not mandatory device settings each device has a number of not mandatory settings which can be used to meet specific needs device description a short description of the device enable meta data select if you want to add meta data to the device connect a device docid\ ish7bqhzxswtdx8vbnszb provide a json object which holds all the meta data you want to add to the device see organize device and tag data by using metadata docid\ si z6r5dzyyuyhlwzq4zr to learn more it is recommended to use the meta data wizard docid\ tecprcmt6i2kyopth9dfz enable status register select if you want to add a status register which is used to monitor if the device is reachable instead of the default status check mechanism connect a device docid\ ish7bqhzxswtdx8vbnszb provide the register definition as a json object it is recommended to use the status register wizard docid\ hh2cpcevkhumoftzyqfpm connect a device docid\ ish7bqhzxswtdx8vbnszb select if you want to substitute long, unreadable device and tag ids with human readable device and tag names in topic names connect a device docid\ ish7bqhzxswtdx8vbnszb select if you want to e nable the logging option for gen 2 drivers note for gen 1 drivers this option is unavailable connect a device docid\ ish7bqhzxswtdx8vbnszb select if you want to store the collected data locally data store retention period provide the number of hours the data are to be stored optional settings this provides a json object which allows users to set settings like connect a device docid\ ish7bqhzxswtdx8vbnszb select if for gen 2 drivers the driver will always publish messages according to the polling interval configuration connect a device docid\ ish7bqhzxswtdx8vbnszb select if the driver will be monitored based on the watchdog period connect a device docid\ ish7bqhzxswtdx8vbnszb select if for some gen 2 drivers (opc ua, bacnet, dnp3, modbus) additional information such as source timestamp, server timestamp and status code it is recommended to use the optional settings wizard docid 2evk5vhpfjzhd9fmso95q troubleshooting the tool will perform several checks throughout the proces of defining the device settings if they do not pass successfully, the user will be notified the checks include device name uniqueness the tool checks if a device name already exist in the tool allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for device names and descriptions the user is shown a message box as notification the character(s) are highlighted in red and also shown in a note see allowed and not allowed ascii characters for names and descriptions docid\ fnwhcidrnnpizczkuwiyz for a full list for both names and descriptions correct json formating for device properties , meta data , status register and optional settings example for an invalid json formatting of the device properties valid entry for data store retention period to be a number and withhin allowed range example for an invalid entry for the retention period do exist json key value pairs in columns device properties , optional settings or status registers with a value being empty null empty array " \[] " empty json object " {} " are the columns device properties , optional settings or status registers empty if they are, the default json object will be automaticlly added