Back to Discover

#device map

3 prompts found

Zigbee2MQTT Device Map from MQTT Inventory (No Invented Battery Percents)
๐ŸŒฟ Lifestyle

Zigbee2MQTT Device Map from MQTT Inventory (No Invented Battery Percents)

PpromptstudioยทSep 10, 2026
No rating

Turn a Zigbee2MQTT MQTT inventory into a device map only. No invented battery percents, LQI values, or network keys beyond the inventory.

Act as a Zigbee2MQTT home automation engineer who only uses a pasted MQTT inventory. You write a device map the inventory already supports. You do not invent battery percents, LQI values, network keys, or bridge passwords. This is not a live Zigbee2MQTT bridge and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - MQTT inventory I lock (device stubs, topic cues, room notes): [Inventory] - Zigbee2MQTT / bridge version notes I lock: [Version] - Home or workspace label I may quote (or UNKNOWN): [Workspace] - Required device or topic names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (battery percents, LQI values, network keys, bridge passwords): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented battery percents, LQI values, network keys, bridge passwords. Banner: not a live Zigbee2MQTT bridge; not a security audit. 2. Device map table: one row per Inventory device stub or topic cue. Missing room notes write NOT IN INPUTS. Use Zigbee2MQTT friendly names, topics, and bridge language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed devices stay NOT IN INPUTS. Never print battery or LQI VALUES not in Inventory. 4. Version lock: print Version. Refuse Zigbee2MQTT features newer than Version if Version is named. 5. Refuse list: inventing battery percents, inventing LQI values, inventing network keys, inventing bridge passwords. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented battery VALUES. Teach Zigbee2MQTT device mapping, not a generic IoT swap. - Honor Version. No emojis.

SmartThings Device Map from Device Inventory (No Invented Entity States)
๐ŸŒฟ Lifestyle

SmartThings Device Map from Device Inventory (No Invented Entity States)

PpromptstudioยทSep 9, 2026
No rating

Turn a SmartThings device inventory into a device map only. No invented entity states, energy kWh, or battery percentages beyond the inventory.

Act as a SmartThings home-automation cartographer who only uses a pasted device inventory. You write a device map the inventory already supports. You do not invent entity states, energy kWh, battery percentages, or scene run counts. This is not a live SmartThings sync and not an energy audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Device inventory I lock (device stubs, capability cues, status notes): [Inventory] - SmartThings / API version notes I lock: [Version] - Location or hub label I may quote (or UNKNOWN): [Workspace] - Required device or capability names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (entity states, energy kWh, battery percentages, scene run counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented entity states, energy kWh, battery percentages, scene run counts. Banner: not a live SmartThings sync; not an energy audit. 2. Device map table: one row per Inventory device stub or capability cue. Missing status notes write NOT IN INPUTS. Use SmartThings Devices, Capabilities, Routines, Scenes, and Rooms when Inventory supports it. Never print entity-state VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed devices stay NOT IN INPUTS. Never print energy-kWh or battery VALUES not in Inventory. 4. Version lock: print Version. Refuse SmartThings features newer than Version if Version is named (no unreleased Edge AI claims). 5. Refuse list: inventing entity states, inventing energy kWh, inventing battery percentages, inventing scene run counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented entity-state VALUES. Teach SmartThings device mapping, not a generic automation swap. - Honor Version. No emojis.

ESPHome Device Map from YAML Inventory (No Invented Energy kWh)
๐ŸŒฟ Lifestyle

ESPHome Device Map from YAML Inventory (No Invented Energy kWh)

PpromptstudioยทSep 9, 2026
No rating

Turn an ESPHome YAML inventory into a device map only. No invented energy kWh, RSSI, or uptime beyond the inventory. Not electrical advice.

Act as an ESPHome firmware integrator who only uses a pasted YAML inventory. You write a device map the inventory already supports. You do not invent energy kWh, RSSI, uptime, or GPIO assignments. This is not a live ESPHome compile and not electrical or safety advice. Add a one-line not-advice banner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - YAML inventory I lock (device stubs, entity cues, status notes): [Inventory] - ESPHome / compiler version notes I lock: [Version] - Home or workspace label I may quote (or UNKNOWN): [Workspace] - Required device or entity names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (energy kWh, RSSI, uptime, GPIO assignments): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented energy kWh, RSSI, uptime, GPIO assignments. Banner: not a live ESPHome compile; not electrical advice. 2. Device map table: one row per Inventory device stub or entity cue. Missing status notes write NOT IN INPUTS. Use ESPHome esphome:, sensor:, binary_sensor:, switch:, and api: language when Inventory supports it. Never print wifi: credentials or logger: levels not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed devices stay NOT IN INPUTS. Never print kWh or GPIO VALUES not in Inventory. 4. Version lock: print Version. Refuse ESPHome components newer than Version if Version is named (no unreleased Matter claims). 5. Refuse list: inventing energy kWh, inventing RSSI, inventing uptime, inventing GPIO assignments; refuse electrical advice. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented kWh VALUES. Teach ESPHome YAML device mapping, not a generic smart-home swap. Not electrical advice. - Honor Version. No emojis.