logo
Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt
Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

    IoT Dev Tools

    Download

    Windows

    Mac OS

    Linux

    Introduction

    IoT Dev Tool is a free software tool that simulates IoT devices for testing data communication between IoT clients and Dialog IoT Portal. This tool supports MQTT, HTTP and TCP protocols. The IoT Dev Tool is automate several API calls with the Dialog IoT portal in the API Automation part.

    Features

    IoT Simulator

    API Automation

    IoT Simulator

    The IoT simulator is used to simulate IoT devices. It supports MQTT, HTTP, CoAP and TCP protocols for data communication with the Dialog IoT portal.

    When the user first launches the IoT Dev Tool, it is taken to the IoT simulator section. At the top of the app, there is a drop-down box where the user can choose the protocol. The text boxes and buttons for the selected protocols are located on the right side of the app. The app’s left side displays a list of previously created connections organized by protocol. The connections list will hide when the user minimizes the app, but it can be accessed by clicking the top left menu item in the App bar.

    MQTT

    The user can create a new connection by clicking the plus icon in front of the connection heading and he can update an existing connection by clicking the setting icon. The user can select the Qos level using the drop-down box, then can connect the selected client by clicking the connect button.

    Publish

    First, the user should select the MQTT client in the connection list and connect the client by clicking the connect button. The user needs to choose the Qos Level before clicking the connect button, by default it is 0.

    Then the user can publish a message by clicking the publish button after the given the correct action topic and message. For automating the publish click the Automate check box and enter the time interval and number of publishing.

    Subscribe

    First, the user should select the MQTT client in the connection list and connect the client by clicking the connect button. Then Enter the correct subscribe topic and click subscribe button.

    Users can send response messages for the actions. Follow the below steps.

    • Click the Action response check box.
    • Enter the correct action response topic and action response message.
    • Click the subscribe button.

    Users can send action response messages with random values by replacing relevant random value patterns.

    If you click the Save Logs check box, timestamp, subscribe and response messages will be written in a CSV file and the file will save in the user given path.

    HTTP

    Select URL from the connection list or enter the new Url. After entering the correct message, click the send button for sending the messages. By clicking the Automate check box, users can send multiple messages automatically.

    You can save new URLs by clicking the plus icon in front of the connection heading and he can update existing URLs by clicking the update button.

    TCP

    You can save new connections by clicking the plus icon in front of the connection heading and you can update the existing connection by clicking the update button.
    Save the connection is not mandatory to connect the host and send the messages.

    Send Messages

    Follow the below steps

    • Select an existing connection or enter relevant details into the text boxes.
    • Click the connect button.
    • You can enter messages in the text box on the left side corner in the below box.
    • Click the send button.
    • You can add more message boxes by clicking the plus icon.
    • Using multiple message boxes you can send various message types at the same time.
    • By clicking the Automate check box, You can send multiple messages automatically. Note: This will apply to all message boxes.
    • Click the send button.

    All messages and replies are displayed in the right-hand corner console.

    You can save all messages and replies which display on the console as a CSV file by clicking the Save File button.

    Automate

    Users can automate data sending from this in the IoT simulator area. The user must check the box and input the count and time interval before sending the message.

    • Count – Number messages users want to publish (should enter natural numbers  Eg:1,2,3).
    • Time Interval – The time interval between two messages.

    The IoT Dev Tool may deliver users customisable random values that are created automatically. According to the parameter kinds, you should replace the value that has to be randomized with one of the suitable Random value patterns.

    Random value patterns

    • Integer – $d$0$<minimum value>$<maximum value>$    Eg: $d$0$50$100$
    • Double – $d$<number of decimal points>$<minimum value>$<maximum value>$   Eg: $d$2$50.5$100.5$
    • String – $s${string1,string2,…}$
    • Boolean – $s${true,false}$

    API Automation

    This section allows you to automate API requests to your IoT core. This area can be accessed by selecting the API button from the app bar. In this section, there are five API calls to choose from. The relevant API request can be selected using radio buttons.

    X-secret, username and password are required for all API calls.

    The messages and errors will be displayed near the bellow buttons after clicking the submit or export button.

    Explore IDs

    1. Get Devices – you can get your onboard devices.
    2. Get Device Events – you can get all events relevant to the device ID.
    3. Get Device Actions – you can get all actions relevant to the device ID.
    4. Get Scenes – you can get all existing scenes.

    After clicking the Submit button, the IoT Dev Tool will prompt you to choose a location to save the CSV file containing the relevant data if the API call is successful.

    Get Events

    This API is used to get history data for set of devices in the IoT core. User can determine the start date that needs to get history data, number of records that needs to get history and also, the time zone for records.

    • Event Name – Event name which you need to get history data.
    • Device Ids – Comma separated device list you need to get history data. (Eg: 24523,32342)
    • Start Date – The start date you need to get history data.
    • End Date – The end date you need to get history data.
    • No of Events – no of records you need to get history from each device. (If you leave this field blank, you will receive all history data entries made during the given period.)
    • ZoneId  – zoneId user wants to get the time of records.
    • Event Params – Event parameters user wants to get in records. Event parameters list should send as comma separated string. (Eg: temp, speed)

    The IoT Dev Tool will prompt you to choose a location to save the CSV file containing the history data if the API call is successful.

    Execute Actions

    By using this API, the user can execute an action that is related to the given device.

    Follow the below steps

    • Enter the correct Device ID and Action Name that you want to execute.
    • Enter the parameter name and value. You can add more parameters by clicking the plus mark.
    • You can send random parameter values by replacing relevant random value patterns.
    • Enter the number of actions that you want to execute.
    • Enter the time interval (in seconds) between two execution. The Time interval should be greater than 10s.

    By pressing the Save Logs button, you may save all action messages, together with their responses, as a CSV file.

    Add Devices

    This API facilitates for adding new devices to the IoT core. Users can build a feasible IoT environment to their own device and do the functionalities here.

    Follow the below instructions.

    • Device Definition ID, Brand, Type, Device parent ID(If you haven’t parent device put 0) and Zone Id are required fields.
    • By clicking the file icon, you should pick the CSV file with devices and mac addresses.
    • CSV File should be as follow
    DeviceName MacAddress
    Device1 123456
    Device2 23478
    Device3 56893
    • The spelling in the headings should be exact, with no gaps between letters.
    • There is no case sensitivity in the headers.
    • The order of the device names and mac address columns can be changed.

    Create Device Summary will appear as a pop-up message box after the API call is successful. If all mac addresses have already been used, it will be shown in the below message box.

    Add Scenes

    This API is used to add new scenes to the IoT core. This is only supported for the create ‘By device Event’ type scenes. You may create scenes using three global actions. (only parameter type)

    1. email
    2. sms
    3. callUrl(NoAuth only)

    By clicking the file icon, you should pick the CSV file with scenes details. CSV File should be as follow

    <scene name> <device ID> <Event name> email <user mail> <email subject> <email body>
    <scene name> <device ID> <Event name> sms <user phone> <message>
    <scene name> <device ID> <Event name> Callurl <url>

    The user should not use column headings, and all columns should be in the proper order. All fields are case sensitive, and spaces between letters in the global action  (Eg: ’email’/’sms’/’callUrl’) field should be avoided.

    Scenes Create Summary will appear as a pop-up message box after the API call is successful. You can create scenes by combining all supported scene types(email/sms/callUrl) into a single file.