instruction large_stringlengths 50 1.88k | input large_stringclasses 1
value | output large_stringlengths 566 16.3k | prompt_type large_stringclasses 2
values | platform large_stringclasses 3
values | flow_title large_stringlengths 8 163 | source_idx int64 0 152 | json_valid bool 1
class | inst_tokens float64 12.5 471 | output_tokens float64 142 4.07k | total_tokens float64 159 4.09k | l1_score float64 0 1 | l1_matched listlengths 0 10 | l1_mismatched listlengths 0 4 | l1_passed bool 2
classes | l2_score float64 0.15 0.9 | l3_score int64 5 9 | l3_verdict large_stringclasses 2
values | l3_reason large_stringlengths 25 291 | l3_passed bool 2
classes | verdict large_stringclasses 1
value | fail_reason large_stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create a Node-RED flow that simulates a Shelly Energy Meter and provides real-time energy data to a Victron VenusOS system using a WebSocket connection.
**OBJECTIVE** - This flow aims to create a virtual Shelly Energy Meter within a Node-RED environment, allowing for monitoring of energy consumption and providing this... | [{"id": "80792cf660f87bf6", "type": "tab", "label": "Flow 2", "disabled": false, "info": "", "env": []}, {"id": "d9f7b8675aac7695", "type": "websocket out", "z": "80792cf660f87bf6", "name": "", "server": "", "client": "b553283038cd31d8", "x": 1050, "y": 120, "wires": []}, {"id": "d4c1a8f69bccbfaf", "type": "websocket i... | rich | colab | victron-virtual-shelly-em | 141 | true | 429.5 | 2,381 | 2,810.5 | 0.6 | [
"websocket",
"parse",
"debug"
] | [
"mqtt",
"publish"
] | true | 0.55 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Create a Node-RED flow that reads data from an air quality sensor. | [{"id": "98dbc86a.74e228", "type": "tab", "label": "JQ-300", "disabled": false, "info": "# JQ-300 Workflow\n\nReads and parses sensor data from ypyt cloud for given device token.\n\nsee https://github.com/xoseperez/espurna/issues/1644 for more context\nextracted from https://gist.github.com/zerog2k/b3afcaf3ff92a60474a1... | short | kaggle2 | JQ-300 Sensor Read values from cloud to InfluxDB | 20 | true | 16.5 | 1,342.5 | 1,359 | 1 | [
"sensor"
] | [] | true | 0.22 | 7 | PASS | The prompt describes the flow's general purpose of reading data from a sensor and writing to a database, but it doesn't specify the exact nodes used or the data transformation steps involved. | true | PASS | ok | |
I want to automatically retrieve data from my manufacturing execution system. | [{"id": "b1c4fd7a8bbae612", "type": "debug", "z": "a6504363d2aa7b56", "name": "", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 1270, "y": 440, "wires": []}, {"id": "b69e9a8424bdea8d", "type": "ui_text_input", "z": "a6504363d2aa7... | short | colab | Manufacturing Execution System(MES) with node MSSQL | 28 | true | 19.25 | 1,648 | 1,667.25 | 0.5 | [] | [] | true | 0.56 | 6 | FAIL | The prompt mentions retrieving data from an MES, but the flow details don't show any actual data retrieval or processing nodes, only input and output nodes and functions, making it a partial match but not a complete description. | false | PASS | ok | |
Create a Node-RED flow that allows controlling a WLED device's RGB LEDs based on tweets containing the hashtag #DoesTheLiverbirdPlay. The flow should respond to new tweets matching the specified hashtag, triggering a color change within the WLED device.
**OBJECTIVE** - This flow aims to create a dynamic lighting syste... | [{"id": "db1d65be.42f728", "type": "tab", "label": "Flow 1", "disabled": false, "info": ""}, {"id": "8c94ab52.90aa9", "type": "inject", "z": "db1d65be.42f728", "name": "On", "props": [{"p": "payload"}, {"p": "topic", "vt": "str"}], "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "topic": "", "payload": "{... | rich | colab | Control WLED neopixels from Twitter | 53 | true | 413.25 | 3,118.5 | 3,531.75 | 1 | [
"transform",
"change"
] | [] | true | 0.35 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
I want to automatically send alerts from The Things Network gateways via Telegram. | [{"id": "96beb4bd.b0d418", "type": "comment", "z": "f2a3fe14.e7db8", "name": "Gateway Management", "info": "", "x": 160, "y": 240, "wires": []}, {"id": "efe2cc40.4ab8b", "type": "inject", "z": "f2a3fe14.e7db8", "name": "ttn-gw01", "topic": "ttn-gw01", "payload": "eui-0000000000000001", "payloadType": "str", "repeat": "... | short | colab | TheThingsNetwork gateway monitor with Telegram alarms | 16 | true | 20.5 | 982.75 | 1,003.25 | 1 | [
"telegram",
"alert"
] | [] | true | 0.3 | 7 | PASS | The prompt mentions sending alerts from The Things Network gateways and Telegram, which aligns with the flow's purpose, though it doesn't detail the specific nodes or their functions. | true | PASS | ok | |
Create a Node-RED flow that deciphers LoRaWAN messages using provided network and application keys.
**OBJECTIVE** - This flow aims to decrypt LoRaWAN packets received via MQTT, extracting the decrypted hexadecimal representation of the original data. It’s designed for analyzing LoRaWAN sensor data where the raw payloa... | [{"id": "e3322e49.7b59f", "type": "tab", "label": "LoraWAN Decrypt", "disabled": false, "info": ""}, {"id": "cd91624b.2fa5c", "type": "debug", "z": "e3322e49.7b59f", "name": "Decrypted", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "true", "targetType": "full", "x": 310, "y": 460,... | rich | colab | LoRaWAN Packet Decrypter using Network & App keys | 13 | true | 420.75 | 1,268.5 | 1,689.25 | 0.75 | [
"function",
"debug",
"sensor"
] | [
"mqtt"
] | true | 0.52 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Build a flow using a Telegram bot configuration node and a Telegram bot command node. | [{"id": "35feb884.bd5478", "type": "link in", "z": "df2398d5.956ea8", "name": "", "links": ["21be9a2f.daf7a6", "b9ab70c4.1723c"], "x": 675, "y": 160, "wires": [["33815a04.cfaf16"]]}, {"id": "33815a04.cfaf16", "type": "exec", "z": "df2398d5.956ea8", "command": "hostname -I", "addpay": false, "append": "", "useSpawn": "f... | short | colab | Send Raspberry Pi IP address via Telegram | 70 | true | 21.25 | 814.5 | 835.75 | 0 | [] | [
"telegram"
] | false | 0.18 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Create a Node-RED flow that connects my OPC UA data to Blockbax. | [{"id": "d4b9a328.1d54b", "type": "tab", "label": "Flow 3", "disabled": false, "info": ""}, {"id": "6bab7cd2.385d84", "type": "OpcUa-Item", "z": "d4b9a328.1d54b", "item": "ns=2;s=AlternatingBoolean", "datatype": "Double", "value": "", "name": "IngestionID1", "x": 530, "y": 240, "wires": [["44ae4015.652e5"]]}, {"id": "4... | short | colab | OPC UA to Blockbax | 99 | true | 16 | 737.5 | 753.5 | 0.5 | [] | [] | true | 0.83 | 7 | PASS | The prompt describes the general direction of the flow (OPC UA to Blockbax), but it doesn't specify the exact nodes and their arrangement, which are crucial for a complete understanding. | true | PASS | ok | |
Create a Node-RED flow that monitors daily gas consumption from an energy meter connected via MQTT and displays it in a user interface chart and gauge.
**OBJECTIVE** - This flow aims to track and visualize the total daily gas consumption recorded by a smart energy meter connected to a Raspberry Pi over MQTT. The goal ... | [{"id": "88fa0739.2e94a8", "type": "tab", "label": "Energie verbruik", "disabled": false, "info": ""}, {"id": "9ca1a2c.bafe76", "type": "inject", "z": "88fa0739.2e94a8", "name": "Start of the day", "topic": "", "payload": "", "payloadType": "date", "repeat": "", "crontab": "00 00 * * *", "once": false, "onceDelay": 0.1... | rich | kaggle2 | Smart Energy Meter | 56 | true | 403 | 2,994.25 | 3,397.25 | 0.78 | [
"schedule",
"inject",
"transform",
"change",
"dashboard",
"gauge",
"chart"
] | [
"mqtt",
"publish"
] | true | 0.74 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Create a Node-RED flow that triggers an Alexa alarm when the current time is available via MQTT or another source, incorporating a two-second delay before execution.
**OBJECTIVE:** This flow aims to automatically trigger an Alexa alarm based on the current time, retrieved dynamically from an MQTT topic or alternative ... | [{"id": "25072fa1.be223", "type": "tab", "label": "alexa Alarm", "disabled": false, "info": ""}, {"id": "690a2da0.6e9004", "type": "ioBroker out", "z": "25072fa1.be223", "name": "Bedroom Echo", "topic": "alexa2.0.Echo-Devices.xxxxxx078376xxxAlarm.New", "ack": "false", "autoCreate": "false", "x": 620, "y": 20, "wires": ... | rich | colab | Trigger an Alexa Alarm (IOBroker) now ( if you can say a GV of the time it is now to MQTT or by other mean)) | 15 | true | 385 | 2,077 | 2,462 | 0.75 | [
"mqtt",
"timer",
"schedule"
] | [
"publish"
] | true | 0.48 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Create a Node-RED flow that monitors Dell iDRAC sensor data and publishes it to MQTT for analysis.
**OBJECTIVE** - This flow aims to retrieve real-time temperature and fan speed data from a Dell iDRAC (Integrated Dell Remote Access Controller) via IPMI commands, specifically using `ipmitool`, and then publish this dat... | [{"id": "19a7443e5e6d6551", "type": "exec", "z": "3d86e78e.17ff28", "command": "ipmitool -I lanplus -H <ip-addr> -U root -P \"<passwd>\" ", "addpay": "payload", "append": "", "useSpawn": "false", "timer": "", "winHide": false, "oldrc": false, "name": "", "x": 300, "y": 1600, "wires": [["9ab4ed850dfdcbf4"], [], []]}, {"... | rich | kaggle2 | Get server sensor detail over IPMI (iDRAC / iLO etc.) | 5 | true | 398 | 556.25 | 954.25 | 0.8 | [
"timer",
"schedule",
"inject",
"parse",
"debug",
"alert",
"sensor",
"temperature"
] | [
"mqtt",
"publish"
] | true | 0.29 | 7 | PASS | The prompt describes the flow's general purpose of monitoring iDRAC sensor data and publishing it, though it doesn't specify the exact method (IPMI/ipmitool) or MQTT details, which are key elements of the flow. | true | PASS | ok | |
Create a Node-RED flow to monitor data from my Xiaomi Miflora sensor. | [{"id": "fa795f97.61e78", "type": "tab", "label": "MiFlora MQTT"}, {"id": "8b334812.a19a98", "type": "mqtt in", "z": "fa795f97.61e78", "name": "Miflora MQTT", "topic": "/home/miflora", "qos": "2", "broker": "cea5258a.b34038", "x": 89, "y": 35, "wires": [["f4621ab.43b90e8", "cf640b9b.5379b8"]]}, {"id": "cf640b9b.5379b8"... | short | kaggle2 | Xiaomi Miflora sensor integration | 50 | true | 17.25 | 1,369 | 1,386.25 | 1 | [
"sensor"
] | [] | true | 0.65 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
I want to automatically display MQTT data in Grafana. | [{"id": "d6e8edce.d5fb88", "type": "change", "z": "49e8c24b.3113ac", "name": "Set Headers", "rules": [{"t": "set", "p": "headers", "pt": "msg", "to": "{}", "tot": "json"}, {"t": "set", "p": "headers.content-type", "pt": "msg", "to": "application/json", "tot": "str"}], "action": "", "property": "", "from": "", "to": "",... | short | colab | mqtt to grafana simpleJson bridge (webservice) | 20 | true | 13.25 | 886.75 | 900 | 1 | [
"mqtt"
] | [] | true | 0.36 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Build a flow using the Pushover API and an API call service to share images from my Xiaomi gateway. | [{"id": "7995a1a6.a2f5e", "type": "switch", "z": "8508cc29.fd96b", "name": "Doorbell", "property": "payload.entity_id", "propertyType": "msg", "rules": [{"t": "eq", "v": "binary_sensor.switch_158d00018b4254", "vt": "str"}], "checkall": "true", "repair": false, "outputs": 1, "x": 280, "y": 560, "wires": [["5cf06743.fb12... | short | colab | Xiaomi Gateway Doorbell with Camera Image and Pushover Message | 72 | true | 24.75 | 673 | 697.75 | 0.5 | [] | [] | true | 0.35 | 8 | PASS | The prompt accurately describes the flow's core functionality of using the Pushover API to send images from a Xiaomi gateway, though it doesn't detail the specific steps or node types involved in the image processing and triggering. | true | PASS | ok | |
I want to automate sending sensor readings to AIoThings. | [{"id": "1799663a.4ff55a", "type": "inject", "z": "b0b895e4.1d37a8", "name": "", "topic": "", "payload": "", "payloadType": "date", "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "x": 149.5, "y": 120, "wires": [["82257007.3539e"]]}, {"id": "2821e6f1.5f146a", "type": "mqtt in", "z": "b0b895e4.1d37a8", "na... | short | kaggle1 | AIoThings Connector | 88 | true | 14 | 615.25 | 629.25 | 1 | [
"sensor"
] | [] | true | 0.42 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Create a Node-RED flow to connect to an MQTT test server. | [{"id": "3297959a.e7fe7a", "type": "inject", "z": "e9540138.5f5c2", "name": "", "topic": "Topic", "payload": "Hello from Injector through mqtt", "payloadType": "str", "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "x": 217, "y": 136, "wires": [["d56cce71.5286a"]]}, {"id": "99bf04c.196c7f8", "type": "debu... | short | kaggle2 | MQTT Basic Example with MQTT test server | 152 | true | 14.25 | 326.25 | 340.5 | 1 | [
"mqtt"
] | [] | true | 0.57 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
I want to automate Enocean sensor readings with Node-RED. | [{"id": "a6d29d13.3c30c", "type": "tab", "label": "Flow 4", "disabled": false, "info": ""}, {"id": "cc35e6a6.347f58", "type": "enocean-in", "z": "a6d29d13.3c30c", "serialport": "cfcf4fbc.4250e", "name": "", "x": 190, "y": 40, "wires": [["75dd71b9.5c90a"]], "info": "Light and Blind Control - Application Style 1"}, {"id"... | short | kaggle1 | node-red-contrib-enocean listening to incomming data | 66 | true | 14.25 | 499.5 | 513.75 | 1 | [
"sensor"
] | [] | true | 0.24 | 7 | PASS | The prompt mentions Enocean sensors, which is the core of the flow, but it doesn't detail the specific data handling or injection stages. | true | PASS | ok | |
Create a Node-RED flow that plays internet radio streams on my Raspberry Pi. | [{"id": "99f9aba4.5b2ed8", "type": "exec", "z": "5966e67.7532218", "command": "mplayer -slave -input file=/tmp/mplayer-control http://81.93.193.35:8945/ > /dev/null 2>&1 &", "addpay": false, "append": "", "useSpawn": "false", "timer": "", "oldrc": false, "name": "FehervarRadio", "x": 820, "y": 800, "wires": [["77f504c... | short | colab | Internet Radio on Raspberry Pi | 84 | true | 19 | 3,536 | 3,555 | 0.5 | [] | [] | true | 0.87 | 7 | PASS | The prompt describes a flow that plays internet radio streams, which is the core functionality of the flow, but it doesn't detail the specific nodes or their arrangement, making it a good but not perfect match. | true | PASS | ok | |
Create a Node-RED flow that saves data from my Arduino to a CSV file. | [{"id": "ab1e3f80a4d839fc", "type": "tab", "label": "Flow 1", "disabled": false, "info": "", "env": []}, {"id": "3ac2ad4d.8e5542", "type": "timestamp", "z": "ab1e3f80a4d839fc", "name": "", "x": 350, "y": 300, "wires": [["1918709f.849b3f"]]}, {"id": "ea0f294b.577388", "type": "timestamp", "z": "ab1e3f80a4d839fc", "name"... | short | colab | COMPASS_Arduino string to .csv | 58 | true | 17.25 | 884.5 | 901.75 | 0 | [] | [
"file"
] | false | 0.34 | 7 | PASS | The prompt describes the general goal of saving data from an Arduino to a CSV file, although the specific nodes and their arrangement aren't detailed in the flow description. | true | PASS | ok | |
Create a Node-RED flow that visualizes MQTT topic trees using the shiftr.io service.
**OBJECTIVE** – This flow aims to provide a real-time visual representation of MQTT topics and their associated message data within a shiftr.io instance, allowing me to monitor the structure of my MQTT communication without relying on... | [{"id": "57388f26.9cdc68", "type": "mqtt out", "z": "dfbad1a1.a09ee8", "name": "data->shiftr.io", "topic": "", "qos": "", "retain": "", "broker": "fb69a6a5.d14a", "x": 940, "y": 440, "wires": []}, {"id": "39a5b1c5.6f8ca6", "type": "mqtt out", "z": "dfbad1a1.a09ee8", "name": "input->shiftr.io", "topic": "", "qos": "", "... | rich | colab | visualize MQTT topic tree with shiftr.io | 36 | true | 375.75 | 1,909.25 | 2,285 | 1 | [
"mqtt",
"publish",
"subscribe"
] | [] | true | 0.68 | 8 | PASS | skipped - clear pass/fail | true | PASS | ok | |
Create a Node-RED flow to gather MQTT messages from a Husdata H60 gateway. | [{"id": "b84964ae.d21338", "type": "tab", "label": "Nibe geothermal heat pump", "disabled": false, "info": ""}, {"id": "85bd383.339d7c8", "type": "debug", "z": "b84964ae.d21338", "name": "", "active": false, "tosidebar": true, "console": false, "tostatus": false, "complete": "true", "targetType": "full", "x": 850, "y":... | short | kaggle2 | A flow that's collect mqtt meassages from Husdatas H60 gateway. Store it in GlobarVars uses Influxdb and Initialstate Rest API. | 114 | true | 18.5 | 4,012 | 4,030.5 | 1 | [
"mqtt"
] | [] | true | 0.33 | 7 | PASS | The prompt accurately describes the flow's primary function of collecting MQTT messages and storing them, though it lacks specific details about the functions and inject nodes used. | true | PASS | ok | |
Build a flow using the Google Light RGB Temp and Google Smarthome Client nodes for lighting control. | [{"id": "7aaa3f3563b06eda", "type": "tab", "label": "Flow 3", "disabled": false, "info": ""}, {"id": "c8ebebd4ee5641c0", "type": "google-light-rgb-temp", "z": "7aaa3f3563b06eda", "client": "ceaea6c.add92d8", "name": "Kitchen Light", "room_hint": "Kitchen", "topic": "homeassistant/lights/kitchen", "passthru": false, "x"... | short | kaggle2 | Neewer 660 - RGB + Scene | 113 | true | 25 | 2,572 | 2,597 | 0.5 | [] | [] | true | 0.24 | 7 | FAIL | The prompt mentions Google Light RGB Temp and Google Smarthome Client, but the flow details don't include the Smarthome Client node, and it uses multiple function nodes which are not described in the prompt. | false | PASS | ok |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 4