IoT Data Widget lets you embed live values from smart home sensors and devices \u2014 temperature, humidity, tank levels, device status, anything with a numeric or text value \u2014 on any WordPress page or post. Activating the plugin drops you straight into a guided setup wizard that gets you from \"no connection\" to a working widget and a ready-to-paste shortcode in a few clicks.<\/p>\n\n
The free version is fully functional, not a crippled trial: unlimited connections, Home Assistant, push mode, Generic REST, the Card\/Status list\/Gauge display styles, the shortcode and Gutenberg block, the setup wizard, and the diagnostics page all work with no time limit and no license. Pro adds more data sources, history graphs and alerts \u2014 see \"What's included in Free vs Pro?\" in the FAQ below for the full breakdown.<\/p>\n\n
This plugin connects to two services that are not<\/strong> the smart-home API\/device you configure yourself:<\/p>\n\n Every other outbound request goes only to the URL\/host you<\/strong> configure for a connection.<\/p>\n\n\n blocks\/iot-widget\/build\/index.js (the Gutenberg block editor script) is a compiled bundle. Its full, human-readable source is included in this plugin's ZIP at Free (no time limit, no license, unlimited connections): Home Assistant, push mode, Generic REST data sources; Card\/Status list\/Gauge display styles; the setup wizard, shortcode, Gutenberg block, and diagnostics page.<\/p><\/dd>\n Card (single value): Status list (several entities at once): Gauge (numeric value with a min\/max range): Generic REST (entity is a JSONPath into the JSON response): Entities with a non-numeric state (a relay's on\/off, a presence sensor's home\/away...) show their real value (\"ON\", \"true\") in Card and Status list styles.<\/p><\/dd>\n Yes, every wizard screen has a \"Skip the wizard, I'll configure manually\" link that takes you straight to the regular Connections page, where everything works exactly as it did before the wizard existed. Nothing about manual configuration changed or was removed.<\/p><\/dd>\n Yes \u2014 click \"Run the setup wizard again\" on the Connections page. It always creates a brand-new connection through the same guided steps; it never edits or overwrites one you already have.<\/p><\/dd>\n If you activated several plugins at once (the \"bulk actions\" checkbox list on the Plugins screen), the wizard intentionally doesn't open \u2014 a redirect in the middle of a bulk action would be disruptive. Open it anytime from IoT Data Widget \u2192 Setup Wizard<\/strong> in the admin menu.<\/p><\/dd>\n In Home Assistant, click your username in the bottom-left corner to open your profile, scroll to Security<\/strong>, then Long-Lived Access Tokens<\/strong> \u2192 Create Token<\/strong>. Copy it immediately \u2014 Home Assistant only shows it once.<\/p>\n\n Home Assistant doesn't let you limit what a token can do \u2014 it inherits the full permissions of whichever account created it, and it never expires until you revoke it. We recommend creating a separate, non-administrator account in Home Assistant just for this token. If your WordPress site is on external\/shared hosting, also consider push mode instead \u2014 it never stores a Home Assistant token at all.<\/p><\/dd>\n Credentials you enter (Home Assistant tokens, MQTT broker passwords, Shelly Cloud keys) are encrypted before being stored in your WordPress database, using a key derived from your site's own configuration. This protects them if the database itself leaks \u2014 a backup, a database dump, a SQL injection in an unrelated plugin on the same install, or a staging clone. It does not<\/strong> protect against someone who has already fully compromised your server, since the encryption key lives on that same server.<\/p>\n\n If you ever uninstall the plugin, we recommend also revoking the Home Assistant token (and rotating any MQTT\/Shelly Cloud credentials) from the device\/service side.<\/p>\n\n Push mode sidesteps this entirely: the plugin never stores any credentials to your devices, because your device sends data to the plugin instead of the other way around.<\/p><\/dd>\n Both. The Generic REST connector (free) works with any API that returns JSON over HTTP(S), authenticated or not.<\/p><\/dd>\n No. The values shown in your widgets never leave your own WordPress installation to any third party \u2014 the plugin only connects to the URL you configure in each connection. See \"External services\" below for the small number of exceptions.<\/p><\/dd>\n The widget fails gracefully: site visitors simply see nothing where the widget would be, while logged-in administrators see a clear error message in its place.<\/p><\/dd>\n No \u2014 responses are cached for 60 seconds by default (not configurable per widget in this version), so repeated page views within that window are served from cache.<\/p><\/dd>\n\n
\n
iot-data-widget<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the zip through Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/li>\n\n
http:\/\/homeassistant.local:8123<\/code>) and a Long-Lived Access Token. Generate one in Home Assistant under your profile page \u2192 Security<\/strong> \u2192 Long-Lived Access Tokens<\/strong> \u2192 Create Token<\/strong>.<\/li>\nAuthorization: Bearer xxx<\/code> or X-API-Key: xxx<\/code>) if the API requires one.<\/li>\n<\/ul><\/li>\n\n
[iotdw_widget]<\/code> directly \u2014 see the FAQ below for examples.<\/li>\n<\/ul><\/li>\n<\/ol>\n\n\n\n
Where's the human-readable source for the minified JavaScript?<\/h3><\/dt>\n
blocks\/iot-widget\/src\/<\/code> \u2014 build it yourself with npm install && npm run build<\/code> (standard @wordpress\/scripts<\/code> toolchain, see package.json<\/code>).<\/p><\/dd>\nWhat's included in Pro?<\/h3><\/dt>\n
What shortcode examples are there?<\/h3><\/dt>\n
[iotdw_widget connection=\"Home\" entity=\"sensor.living_room_temperature\"]<\/code><\/p>\n\n[iotdw_widget connection=\"Home\" style=\"list\" entities=\"sensor.temperature,sensor.humidity,sensor.battery\"]<\/code><\/p>\n\n[iotdw_widget connection=\"Home\" style=\"gauge\" entity=\"sensor.tank_level\" min=\"0\" max=\"100\"]<\/code><\/p>\n\n[iotdw_widget connection=\"Weather API\" entity=\"current_weather.temperature\"]<\/code><\/p>\n\nI don't want to use the setup wizard \u2014 can I skip it?<\/h3><\/dt>\n
Can I run the setup wizard again after my first connection?<\/h3><\/dt>\n
Why didn't activating the plugin open the setup wizard?<\/h3><\/dt>\n
How do I get a Home Assistant Long-Lived Access Token?<\/h3><\/dt>\n
How are my device credentials protected?<\/h3><\/dt>\n
Does this work with any REST API, or only Home Assistant?<\/h3><\/dt>\n
Does the plugin send my data anywhere else?<\/h3><\/dt>\n
What happens if a connection or entity is misconfigured?<\/h3><\/dt>\n
Will this hit my Home Assistant instance on every page view?<\/h3><\/dt>\n
Something isn't working \u2014 what's the fastest way to get help?<\/h3><\/dt>\n