iot-developer
Expert in IoT development, microcontrollers, sensors, and MQTT protocols
What this skill does
# IoT Developer Skill
I help you build IoT applications, connect sensors and devices, and create smart home/industrial IoT solutions.
## What I Do
**Device Integration:**
- Microcontroller programming (Arduino, ESP32)
- Sensor reading and data collection
- Actuator control (motors, LEDs, relays)
- Hardware interfacing
**Communication:**
- MQTT messaging
- WebSocket connections
- REST API integration
- Bluetooth/WiFi connectivity
**IoT Platforms:**
- Real-time dashboards
- Device management
- Data logging
- Alerts and automation
## MQTT Basics (Web Client)
```bash
npm install mqtt
```
```typescript
// lib/mqtt-client.ts
import mqtt from 'mqtt'
export class MQTTClient {
private client: mqtt.MqttClient
constructor(brokerUrl: string) {
this.client = mqtt.connect(brokerUrl, {
clientId: `web_${Math.random().toString(16).slice(3)}`,
clean: true,
connectTimeout: 4000
})
this.client.on('connect', () => {
console.log('MQTT connected')
})
this.client.on('error', error => {
console.error('MQTT error:', error)
})
}
subscribe(topic: string, callback: (message: string) => void) {
this.client.subscribe(topic, err => {
if (err) console.error('Subscribe error:', err)
})
this.client.on('message', (receivedTopic, message) => {
if (receivedTopic === topic) {
callback(message.toString())
}
})
}
publish(topic: string, message: string) {
this.client.publish(topic, message)
}
disconnect() {
this.client.end()
}
}
```
**Usage:**
```typescript
'use client'
import { useEffect, useState } from 'react'
import { MQTTClient } from '@/lib/mqtt-client'
export function TemperatureDashboard() {
const [temperature, setTemperature] = useState(0)
const [humidity, setHumidity] = useState(0)
useEffect(() => {
const mqtt = new MQTTClient('ws://broker.hivemq.com:8000/mqtt')
mqtt.subscribe('home/temperature', (msg) => {
setTemperature(parseFloat(msg))
})
mqtt.subscribe('home/humidity', (msg) => {
setHumidity(parseFloat(msg))
})
return () => mqtt.disconnect()
}, [])
return (
<div className="grid grid-cols-2 gap-4">
<div className="p-6 bg-white rounded-lg shadow">
<h3 className="text-gray-600">Temperature</h3>
<p className="text-4xl font-bold">{temperature}°C</p>
</div>
<div className="p-6 bg-white rounded-lg shadow">
<h3 className="text-gray-600">Humidity</h3>
<p className="text-4xl font-bold">{humidity}%</p>
</div>
</div>
)
}
```
---
## Arduino/ESP32 Code
### Temperature Sensor (DHT22)
```cpp
// ESP32 + DHT22 Temperature/Humidity Sensor
#include <WiFi.h>
#include <PubSubClient.h>
#include <DHT.h>
#define DHTPIN 4
#define DHTTYPE DHT22
const char* ssid = "YOUR_WIFI_SSID";
const char* password = "YOUR_WIFI_PASSWORD";
const char* mqtt_server = "broker.hivemq.com";
WiFiClient espClient;
PubSubClient client(espClient);
DHT dht(DHTPIN, DHTTYPE);
void setup() {
Serial.begin(115200);
dht.begin();
// Connect to WiFi
WiFi.begin(ssid, password);
while (WiFi.status() != WL_CONNECTED) {
delay(500);
Serial.print(".");
}
Serial.println("WiFi connected");
// Connect to MQTT
client.setServer(mqtt_server, 1883);
}
void loop() {
if (!client.connected()) {
reconnect();
}
client.loop();
// Read sensor
float temperature = dht.readTemperature();
float humidity = dht.readHumidity();
// Publish to MQTT
if (!isnan(temperature)) {
client.publish("home/temperature", String(temperature).c_str());
}
if (!isnan(humidity)) {
client.publish("home/humidity", String(humidity).c_str());
}
delay(5000); // Publish every 5 seconds
}
void reconnect() {
while (!client.connected()) {
if (client.connect("ESP32Client")) {
Serial.println("MQTT connected");
} else {
delay(5000);
}
}
}
```
---
## Smart Home Dashboard
```typescript
'use client'
import { useEffect, useState } from 'react'
import { MQTTClient } from '@/lib/mqtt-client'
interface Device {
id: string
name: string
type: 'light' | 'sensor' | 'thermostat'
status: string | number
}
export function SmartHomeDashboard() {
const [devices, setDevices] = useState<Device[]>([
{ id: '1', name: 'Living Room Light', type: 'light', status: 'off' },
{ id: '2', name: 'Temperature', type: 'sensor', status: 22 },
{ id: '3', name: 'Thermostat', type: 'thermostat', status: 20 }
])
const [mqtt, setMqtt] = useState<MQTTClient | null>(null)
useEffect(() => {
const client = new MQTTClient('ws://broker.hivemq.com:8000/mqtt')
// Subscribe to device topics
client.subscribe('home/light/1', (msg) => {
updateDevice('1', msg)
})
client.subscribe('home/temperature', (msg) => {
updateDevice('2', parseFloat(msg))
})
setMqtt(client)
return () => client.disconnect()
}, [])
const updateDevice = (id: string, status: string | number) => {
setDevices(prev => prev.map(device =>
device.id === id ? { ...device, status } : device
))
}
const toggleLight = (id: string) => {
const device = devices.find(d => d.id === id)
if (device && mqtt) {
const newStatus = device.status === 'on' ? 'off' : 'on'
mqtt.publish(`home/light/${id}`, newStatus)
updateDevice(id, newStatus)
}
}
return (
<div className="max-w-4xl mx-auto p-6">
<h1 className="text-3xl font-bold mb-6">Smart Home</h1>
<div className="grid md:grid-cols-2 lg:grid-cols-3 gap-4">
{devices.map((device) => (
<div key={device.id} className="p-6 bg-white rounded-lg shadow">
<h3 className="font-semibold mb-2">{device.name}</h3>
{device.type === 'light' && (
<button
onClick={() => toggleLight(device.id)}
className={`px-4 py-2 rounded ${
device.status === 'on'
? 'bg-yellow-400 text-black'
: 'bg-gray-300'
}`}
>
{device.status === 'on' ? '💡 ON' : '🌑 OFF'}
</button>
)}
{device.type === 'sensor' && (
<p className="text-2xl font-bold">{device.status}°C</p>
)}
{device.type === 'thermostat' && (
<div>
<p className="text-xl">Target: {device.status}°C</p>
<div className="flex gap-2 mt-2">
<button className="px-3 py-1 bg-blue-600 text-white rounded">
-
</button>
<button className="px-3 py-1 bg-blue-600 text-white rounded">
+
</button>
</div>
</div>
)}
</div>
))}
</div>
</div>
)
}
```
---
## WebSocket Real-Time Sensor Data
```typescript
// app/api/sensor-stream/route.ts
export async function GET(req: Request) {
const encoder = new TextEncoder()
const stream = new ReadableStream({
start(controller) {
const interval = setInterval(async () => {
// Simulate sensor data (or read from actual IoT device)
const temperature = 20 + Math.random() * 10
const humidity = 40 + Math.random() * 20
const data = `data: ${JSON.stringify({
temperature,
humidity,
timestamp: new Date().toISOString()
})}\n\n`
controller.enqueue(encoder.encode(data))
}, 1000)
req.signal.addEventListener('abort', () => {
clearInterval(interval)
controller.close()
})
}
})
return new Response(stream, {
headers: {
'Content-Type': 'text/event-stream',
'Cache-Control': 'no-cache',
Connection: 'keep-alive'
}
})
}
```
---
## When to Use Me
**Perfect for:**
- Building smart home systems
- Creating industrial IoT solutions
- Implementing sensor networks
- DeRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.