seven.io SMS & Communication

ioBroker adapter for seven.io

This adapter connects ioBroker to the seven.io SMS and communication API. Send SMS messages and trigger text-to-speech voice calls directly from your automations, Blockly scripts, or JavaScript — with contact management, delivery tracking, inbound SMS polling, and account balance monitoring included.

Features

• Send SMS — trigger via data point, Blockly block, or sendTo()
• Flash SMS — message appears directly on the recipient's screen
• Voice calls (TTS) — read any text aloud via an automated call
• Delivery status — automatic check ~60 s after sending, written to a dedicated state
• Contact management — sync contacts from seven.io as individual data points; create new contacts directly from ioBroker
• Recipient by name — enter a contact name instead of a phone number; the adapter resolves it automatically
• Account balance polling — configurable interval, result available as a readable state
• Inbound SMS polling — receive incoming SMS (requires a rented virtual number, see below)
• Blockly block — ready-to-use block in the sendTo category with checkboxes for SMS and/or voice call
• sendTo() API — full scripting support for JavaScript adapter

Requirements

• An account at seven.io
• A valid API key (found in your seven.io dashboard under Developer → API Keys)

Cost model:

• Sending SMS and voice calls is pay-per-use — you only pay per message or call, no monthly fee
• Receiving inbound SMS requires a virtual phone number rented from seven.io (~€20/month). Without a rented number, inbound polling is not available

Private users: seven.io is primarily a business service. When registering, a company name is required. Private users may simply enter their own name or the word Privat in that field — seven.io has confirmed this is acceptable.

Configuration

Data points

info

account

contacts

sms

sms.inbound

voice

pricing

stats (rolling 30 days)

Statistics always cover the rolling window today − 30 days → today. They are fetched once on adapter start and on manual trigger — there is no automatic refresh timer.

Inbound SMS

To receive SMS replies you need a numeric sender — alphanumeric names (e.g. MyCompany) cannot directly receive replies. You have two options:

Option 1 — Shared pool (free, for testing and light use)

Pass getReplies: true per message (Blockly checkbox or sendTo() parameter). seven.io automatically assigns a temporary shared pool number as the sender, so replies work even with an alphanumeric sender ID.

Option 2 — Own inbound number (~€20/month)

Rent a virtual inbound number directly in your seven.io dashboard. Replies arrive reliably and permanently.

Configure the polling interval in the adapter settings. Set to 0 to disable inbound polling (e.g. if you use webhooks instead).

Multiple messages per cycle: If several SMS arrive between two polls, the adapter processes them all — oldest first. Each message triggers a separate state change on sms.inbound.text, so every Blockly rule or JavaScript automation that watches this state fires once per message. The data points always reflect the most recent message after the cycle.

Blockly

After installing the adapter a ready-to-use block appears in the sendTo category of the ioBroker Blockly editor.

┌─ seven.io  |  SMS ☑  Voice call ☐ ─────────────┐
│  sender (optional)  [ ""                  ]      │
│  recipient          [ "+491234567890"     ]      │
│  message            [ "Alarm!"            ]      │
│  flash SMS ☐  replies (shared pool) ☐           │
│  ring time (s)  30                               │
│  instance  sevenio.0 ▼                           │
└──────────────────────────────────────────────────┘

• Check SMS to send a text message
• Check Voice call to trigger an automated TTS call
• Check both to send an SMS and make a call at the same time (parallel, no extra delay)
• replies (shared pool) — when checked, seven.io uses a shared pool number as sender so the recipient can reply (see Inbound SMS)
• The recipient input accepts a phone number or a contact name from your seven.io contact list

sendTo() scripting

All functions are available via sendTo() in the JavaScript adapter.

Send an SMS:

sendTo('sevenio.0', 'send', {
    to: '+491234567890',   // or a contact name: 'Max Mustermann'
    text: 'Door opened!',
    flash: false,          // optional
    getReplies: true,      // optional — enable shared pool so recipient can reply
}, result => {
    console.log(result.statusText); // e.g. 'Success'
});

Trigger a voice call:

sendTo('sevenio.0', 'voice', {
    to: '+491234567890',
    text: 'Attention! Motion detected in the garage.',
    ringtime: 30,          // optional, 5–60 s
});

Get account balance:

sendTo('sevenio.0', 'get_balance', {}, result => {
    console.log(result.amount, result.currency);
});

Get contact list:

sendTo('sevenio.0', 'get_contacts', {}, contacts => {
    console.log(JSON.stringify(contacts));
});

Create a contact:

sendTo('sevenio.0', 'create_contact', {
    name: 'Max Mustermann',
    number: '491234567890',   // without +
});

Test SMS (send a test message to verify the API key):

sendTo('sevenio.0', 'test_sms', { to: '+491234567890' }, result => {
    console.log(result.statusText);
});

Test voice call:

sendTo('sevenio.0', 'test_voice', { to: '+491234567890' }, result => {
    console.log(result);
});

Refresh statistics immediately:

sendTo('sevenio.0', 'get_stats', {}, result => {
    console.log(result); // raw analytics data
});

Alternatively, set the sevenio.0.stats.refresh data point to true — the adapter fetches fresh statistics and resets the state to false automatically.

Delayed SMS (scheduled delivery):

sendTo('sevenio.0', 'send', {
    to: '+491234567890',
    text: 'Good morning!',
    delay: '2026-12-24 08:00:00', // ISO datetime or Unix timestamp (seconds)
}, result => {
    console.log(result.statusText);
});

The delay parameter is forwarded directly to the seven.io API. Use an ISO datetime string (YYYY-MM-DD HH:MM:SS) or a Unix timestamp in seconds. The message is queued by seven.io and delivered at the specified time.

SMS status codes

The sms.lastStatus state contains a human-readable translation of the seven.io status code:

Changelog

0.1.2 (2026-07-22)

• (ipod86) Maintenance: fix io-package.json structure, improve CI and dependabot configuration

0.1.1 (2026-07-22)

• (ipod86) Fix: multiple inbound SMS per poll cycle now each trigger automations (processed oldest-first)

0.1.0 (2026-07-22)

• (ipod86) SMS sending via state, Blockly, and sendTo()
• (ipod86) Voice calls (TTS) via state, Blockly, and sendTo()
• (ipod86) Contact management — sync, create, send by name
• (ipod86) Inbound SMS polling with shared pool and own number support
• (ipod86) Delivery status check ~60 s after sending
• (ipod86) Account balance polling
• (ipod86) SMS pricing data with per-country price state
• (ipod86) Usage statistics (rolling 30-day window)

License

MIT License

Copyright (c) 2026 ipod86 david@graef.email

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.