Prepare a new Tool File to manage DeviceHub Device(s) on multiple Litmus Edge

to manage devicehub devices on multiple litmus edge with the litmus excel add ins with a new tool file, you must prepare the tool file first before you begin you know the ipv4 addresses of your litmus edge devices you create api credentials docid\ dxgpm5ir bz wk3iv s9q on every litmus edge device you want to use step 1 navigate to home actions open a new excel file with litmus excel add ins enabled see install litmus excel add ins docid\ gzdhbj1xzznddthyocuuu to learn more expand home actions click on new configuration click on device management template a new file will be created, based on the device management template, with a default name of "litmus configuration devicemanagement \<user name> \<date> \<time> xlsm" example litmus configuration devicemanagement jane doe 08122025 132020 xlsm it is stored by default in your documents folder step 2 add ip and api key for one litmus edge the device management tool will inform the user if no litmus edge device is defined acknowledge the message through a click on the ok button select for connect to the multiple le option which will show the target litmus edge ip column provide the ipv4 of one of the litmus edge you want to work on in the first row (row 5) and press the yes button provide the manage api credentials docid 7 o3n hxk7c 7hxeuw5qe from litmus edge press the enter key and click on the green save button the tool will now verify if it can connect to the defined litmus edge notes it is not necessary to add all the ipv4 addresses for every litmus edge you want to work on their ipv4 addresses will be added as needed troubleshooting the system will attempt to establish a connection with the litmus edge if successful, you will see the red banner disappear and the cell change to green if the connection fails example devicehub service not responding you want to select a cell in column target litmus edge ip with the ipv4 address to verify verify the ipv4 address confirm the api key confirm if all services are in a running (green) state confirm if the stats service is not running correctly