Commands¶
Where commands come from¶
The app does not hard-code command ids. room-configuration-list returns, for each
device, its deviceCommandList. The app caches it (ObjectBox Command entity) and, when
a button is pressed, asks for an (action, param) pair that is resolved against that
list. CommandDao#mapCommands contains per-model tables, but they are only used in
demo/direct mode.
Consequence for the SDK: commandId / lowlevelCommand values (e.g. 94/CH4) are
never constants; they are read from the device's command list. Implemented in
aioteleco/commands.py.
Actions and parameters sent by the device screens¶
| Action | Parameters |
|---|---|
POWER |
ON, OFF, LEV1…LEV4 |
LEVEL |
LEV1…LEV4, an integer 0–100 (sliders), or 7 values joined by § (generic slider) |
OPEN_STOP_CLOSE |
OPEN, STOP, CLOSE, LEV1, LEV4, START_O, START_C, END_O_A, END_O_M, END_C_A, END_C_M |
COLOR |
AxxxRxxxGxxxBxxx (A = brightness 0–100), or a preset name + that string (model 26), optionally ;S |
CYCLE |
ON, PLAY, PAUSE |
SPEED |
33, 67, 100 |
CHANNEL |
CHn, CH8-L |
PAUSE_PLAY |
PLAY, PAUSE |
AUDIO_ACTION |
VOLUME_UP, VOLUME_DOWN, REWIND, FORWARD |
START_* / END_* implement hold-to-move buttons: END_*_M if the button was held
more than 1.5 s, END_*_A otherwise.
Pergola slats (model 27, OpenStopCloseStepsDeviceActionFragment): position 0 →
OPEN_STOP_CLOSE CLOSE (models 44/45: LEVEL LEV1), 33 → LEVEL LEV2,
66 → LEVEL LEV3, 100 → LEVEL LEV4.
Dimmers (OnOffStepsDeviceActionFragment, models 17–20 and 34): the step buttons send
POWER LEV1…LEV4, ON and OFF. Only model 34 shows the slider, which sends
LEVEL <0-100> (POWER OFF at 0); the Brustor app hides it too. Stepped dimmers also
list a parametric LEVEL command (commandParam "0"), but the box ignores a free
level sent to them: the SDK maps Dimmer.set_level to the nearest step there.
Open/stop/close devices (models 21–25, 31, 43, 47, OpenStopCloseDeviceActionFragment)
only take OPEN, STOP and CLOSE. The percentage the app shows is derived from the
status: LEVEL while OPEN_CLOSE == "OPEN", 0 when CLOSE (a closed device can report
LEVEL 100), and "-" otherwise (Cover.position). The SDK can still reach any position
by timing a move and sending STOP (Cover.travel_to, teleco cover travel), from
full travel times measured once (teleco cover calibrate); the app does not do this.
Selection algorithm (DaisyApplication#sendCommand, from smali)¶
send_command(device, action, param):
flag_S = ";" in param; p = param.split(";")[0] if flag_S else param
flag_L = "-L" in p; p = p.replace("-L", "")
mapped = "OPEN" if p in (START_O, END_O_M, END_O_A)
"CLOSE" if p in (START_C, END_C_M, END_C_A)
else p
template = None; out = []
for cmd in device.commands: # server order
if (cmd.action == action and cmd.param == "0") or device.model == 42:
template = cmd (with param := p); continue # parametric command, last one wins
match = (cmd.param in mapped # substring test, action NOT compared
and cmd.param not in ("25","50","75","100","0") and cmd.action != "SPEED")
or (cmd.action == "SPEED" and p == cmd.param and p in ("100","33","67"))
if match:
low = f"CH{int(cmd.low[2:]) + 10}" if flag_S else ""
out = [toCommandCloud(cmd)]
if device.model == 26 and mapped != cmd.param:
out[0].param = mapped.replace(cmd.param, "") # "RED"+ARGB → ARGB
break
if not out: out = [toCommandCloud(template)] # the app crashes when there is none
c0 = out[0]
if flag_S: c0.low = low
if device.feedback: c0.action += "-F"
if flag_L: c0.action += "-L"
if p in (START_O, START_C): c0.param = "START"
if p in (END_O_A, END_C_A): c0.param = "END_A"
if p in (END_O_M, END_C_M): c0.param = "END_M"
if device.model == 44 and device.sub_model in ("2", "3"): swap CH5 <-> CH8 in out
→ LAN (TCP 400) if at home and the box IP is known, else cloud feedthecommands
CommandDao#toCommandCloud(cmd):
{idInstallationDevice, deviceCode: str(device.index), idInstallationDeviceCommand,
commandAction, commandParam, lowlevelCommand, commandId: idDevicetypeCommandModel,
idDevicetypeCommandModel, commandStatus: 0, commandreceived: 0, commandReceivedUR: "0",
commandProcessed: 0}.
Before sending, the app checks (no internet and at home) or nodeStatus, otherwise it
shows "board not reachable".
Cloud delivery and acknowledgement¶
tmate20/feedthecommands/→{MessageType: "INFO", ActionReference: "…"}. A nullActionReferencemeans "done".- Poll
tmate20/getackcommand/ {id: ActionReference}: - device screens: every 500 ms until
MessageText == "PROC"(processed by the box); - timer / schedule / scenario-upload flows: every 1 s until
MessageText == "ACK", 5 tries; - room/scenario lists: every 1 s, 7 tries;
- any other
MessageTextmeans "not yet"; aMessageTypeother thanINFOis an error (handleAckCommand). - The device screen then reads
status-device-list.
Scenarios¶
Running a scenario (ScenarioDao#toFeedCommandPost, DaisyApplication#sendScenario)
sends every step as a full command in one feedthecommands with
isScenario: true and idScenario: <idInstallationScenario>. For a parametric step
(cached commandParam == "0"), the step's commandParam is substituted. On the LAN the
frame is prefixed with S and the read timeout is 10 s.
CommandDao#isCommandCompatible (commands allowed in a scenario): never STOP;
models 26/46 exclude PLAY, 33, 67, 100, PAUSE, audio and OPEN/CLOSE; model 28 excludes
audio and OPEN/CLOSE; model 44 excludes OPEN/CLOSE.
System (box) commands¶
Built by CommandDao#commandTo*: commandId = 122, idInstallationDevice = the box's
device id, deviceCode = "0" unless noted, lowlevelCommand = "". Always sent through
the cloud.
| Action | Param | Notes | SDK (TelecoHub) |
|---|---|---|---|
GET_FEEDBACK |
box short code of the device model (PER, PEG…, CommandDao#getBoardDeviceCodeName) |
idInstallationDevice = the device, deviceCode = device index |
request_feedback |
UP_DEV |
Feedback: S\|N Timers: S |
idInstallationDevice = the device, deviceCode = device index, lowlevelCommand = box device id; firmware ≥ 1.3.3 only |
update_device |
UP_SCHED |
Timers: S\|N |
master switch for timers | set_timers_enabled |
UP_TIMERS |
see Timers | deviceCode = device index |
save_timer, set_timer_active |
DEL_TIM |
timer id, 8 hex digits | delete_timer, set_timer_active |
|
UP_SCEN |
scenario string, see Scenarios on the box | save_scenario |
|
DEL_SCEN |
scenario id (decimal) | delete_scenario |
|
UP_INST_NAME |
installation name | rename_installation |
|
GET_TIME, GET_SIGNAL, GET_VERSION, GET_INFO, GET_DIAGNOSTIC |
— | the box refreshes its status items (CURRENT_TIME, SIGNAL, DIAGNOSTIC…); the ack is ACK |
query_box |
TEST_SCAN |
— | Wi-Fi scan of the box setup screen | test_scan |
SYNC_BOARD, END_SYNC |
— | frame a full re-send, see Board sync | sync_box |
SET_TIME |
value (no caller in the app) | set_box_time |
|
SET_WIFI |
SSID: x PASS: y |
set_wifi |
|
AP_CHANNEL_CMD |
00R read; write 20W (static) or 06W |
read_ap_channel, set_ap_channel |
|
MEMORY |
ADDR: <decimal address> NB: <count, 2 digits>R |
read-only; the answer lands in the box's DIAGNOSTIC status item, see Box memory |
read_memory |
UPDATE_BOARD |
firmware links, see Firmware update | flashes the box | update_firmware |
Any action can also be sent with TelecoHub.send_system(installation, action, param).
Box memory¶
MEMORY reads up to 50 bytes. The box writes the answer to its DIAGNOSTIC status item
as space-separated decimal bytes with a leading space (" 152 8 50"), or ERROR. Over
the setup access point the same read is FMEMORY ADDR: %s NB: %sR (see
Local channels). There is no write counterpart. Addresses used by the app's
debug screen:
| Address | Bytes | Content |
|---|---|---|
| 273 | 1 | time zone: 0, n = +n h, 100 + n = −n h |
| 290 | 6 | daylight saving time rule |
| 576 | 50 | Wi-Fi name |
| 640 | 50 | Wi-Fi password |
| 823, 832 | 7, 7 | latitude, longitude |
| 842, 876, 910 | 10, 10, 15 | registration, account and virtual ids |
| 940 | 1 | region: 1 US, 2 EU, 3 Japan, 4 other |
| 950 | 50 | last Wi-Fi |
The read goes well past these addresses — tens of thousands of bytes answer rather than
ERROR, holding config records (scenarios, timers) then filler and zeros: MEMORY maps
the box's data storage, not its program flash. The box also keeps its 868 MHz radio state
there; the radio link is documented in
radio-teleco.
Firmware update¶
The box updates itself; the app never handles a firmware image. It only sends one
UPDATE_BOARD command whose parameter is a space-separated list of links, and the box
downloads and flashes the file on its own (over plain HTTP, from S3). The app triggers
this when the box's reported version is older than a version hard-coded in the app; the
one seen is 1.4.0.2 (firmware date 08-03-24).
The parameter carries three link triplets, one per radio variant, so the box picks the file that matches its own radio:
L <url> N <file> V <version> L916 <url> N916 <file> V916<version> L8686 <url> N8686 <file> V8686<version>
<version> is the target with the dots removed (1.4.0.2 → 1402). L* is the URL,
N* the file name the box saves, V* the version. The plain (868 MHz) variant has no
suffix, 916 is the 916 MHz build, 8686 (file suffix _P6) an 868.6/"P6" model.
Where the images are. Public Amazon S3 buckets, plain http, one set per hardware
generation and region. HW2 is chosen when the cloud install's workdays field looks like
x.y.z (2.0.0 = HW2); the region defaults from the phone's time zone (EU below +7 h,
else AU) and can be overridden in the app's advanced-update picker (EU / AU / two-step).
| Set | Bucket | File names (for 1402) |
|---|---|---|
| EU HW1 | http://tlc-frmw-upd.s3.eu-central-1.amazonaws.com/ |
UPG_1402.gbl, UPG_1402_9.gbl, UPG_1402_P6.gbl |
| EU HW2 | http://tlc-frmw-upd-hw2.s3.eu-central-1.amazonaws.com/ |
UPG_1402HW2.gbl, UPG_1402HW2_9.gbl, UPG_1402HW2_P6.gbl |
| AU HW1 / HW2 | …-au.s3.ap-southeast-2.amazonaws.com/ (tlc-frmw-upd-au, tlc-frmw-upd-hw2-au) |
same file names |
| Two-step ("slim") | EU buckets | an s before the suffix: UPG_1402s.gbl, UPG_1402s_9.gbl, … |
The links are anonymously downloadable (the plain and _9 files return HTTP 200; some
variants such as _P6 are absent, HTTP 403). They are Silicon Labs Gecko Bootloader
images (.gbl), so the box is built on an EFR32-family SoC. The images are
encrypted and signed (an AES-CTR encryption tag, encrypted program data, an
ECDSA-P256 signature): they can be downloaded but neither read nor modified.
Progress is reported in the box's UPDATE_STATUS status item (Starting the upgrade...,
Downloading upgrade..., Loading upgrade...NN%, Applying the upgrade...,
Upgrade completed successfully!, or an error); the box gives up downloading after about
6 minutes.
Remote controls¶
Remote pairing (CommandDao#commandToTx) uses its own commandId and targets the
scenario's idInstallationDevice (every scenario has one), deviceCode = "0":
| Action | commandId |
Param | SDK (TelecoHub) |
|---|---|---|---|
PAIR_TX |
127 | scenario string | pair_remote |
UNPAIR_TX |
128 | scenario id | unpair_remote |
RESET_TX |
129 | scenario id | reset_remotes |
PAIR_BUTTON, UNPAIR_BUTTON |
108, 109 | (no caller in the app) | send_remote_command |
A scenario has a remote bound when its own device reports TX_NUM > 0 or
PAIRING_STATUS == "ON" (SetupScenariosListActivity#handleStatusDeviceList).
Scenarios on the box¶
After scenario-setup succeeds, the app sends UP_SCEN with the scenario string, or
DEL_SCEN when the scenario has no step left (SetupScenarioActivity). Deleting a
scenario sends DEL_SCEN after scenario-delete. Scenario string
(ScenarioDao#toScenarioString):
<scenario id>N<step count, 2 digits>( <device index, 2 digits><V><command model, hex><device id, 8 hex>)*
V is as for timers, except that an integer is always L + hex (at least 2 digits) +
000000. Example: 7001N02 01C0200000062000007d1 03R50ff800089000007d3.
Board sync¶
DaisyApplication#syncBoard re-sends the whole configuration as isScenario: true
feeds of at most 30 commands, each waiting for ACK: SYNC_BOARD, UP_INST_NAME,
UP_SCHED, then UP_DEV per device (firmware ≥ 1.3.3), UP_SCEN per scenario bound
to a remote, UP_TIMERS per timer, and END_SYNC.
Rooms¶
Deleting a room (SetupRoomsListActivity): room-delete, then DEL_TIM for every
timer of its devices, then UP_SCEN (or DEL_SCEN) for the scenarios that used them.
Timers¶
A timer is saved in two steps (SetupDeviceTimersActivity, DaisyApplication#updateTimers):
- send
UP_TIMERS(one per timer) and wait forMessageText == "ACK"; - post the device's complete timer list to
timer-device-setup/.
A new timer is first created with idInstallationDeviceTimer: 0 through
timer-device-setup/ to obtain its id. Disabling a timer on firmware ≥ 1.3.3 sends
DEL_TIM instead of UP_TIMERS.
Deleting a timer (SetupTimerListActivity#deleteTimer): send DEL_TIM (timer id on 8
hex digits, DaisyBaseActivity#delTimerString), wait for ACK, then post the device's
timer list without it to timer-device-setup/. The box runs timers on its own clock,
which is local time (CURRENT_TIME), so timerDate is local time too.
timer-device-list/ has been seen returning an empty timerList for a device that
has timers; room-configuration-list (deviceTimersList) is the reliable source.
UP_TIMERS parameter (CommandDao#commandToUpdateTimer):
<V> HShhmm DSddMM HE0000 DE0000 Gnnn Annn <device id, 8 hex> M<command model, hex> <timer id, 8 hex> T<S|N>
V(value): ARGB param →R+ 4 hex bytes (A100R255G000B010→R64ff000a); integer →L+ hex +000000(single hex digit:0+ digit +000000); otherwiseC+ channel (2 digits) +000000, where the channel comes from the command'sCHn(colors: PURPLE 13, YELLOW 12, CYAN 11, WHITE 14; no channel → 8).HS/DS: time and day/month oftimerDate(local time,yyyy-MM-dd HH:mm).G: day mask,int("0" + bits(giorni), 2)with Monday first (Mon = 64 … Sun = 1), 3 digits.A: astronomical flags,int(sun + "000" + offset, 2)withsun=00(no twilight),01(sunrise) or10(sunset) andoffset−2 →001, −1 →010, 0 →000, +1 →011, +2 →100(hours); 3 digits. Examples: sunrise →A064, sunrise +2 h →A068, sunset −1 h →A130.