Smart Sockets, Relays and Remotes: Device Power — IZI

Smart Sockets, Relays and Remotes: Device Power

A console, gaming PC or custom device can be tied to a Yandex smart home, and IZI then powers it up when a session starts and cuts power when the session ends. This used to cover smart sockets and relays only; now an appliance set up behind a Yandex infrared remote works too — the TV next to a console, a media box, an air conditioner. The setting lives in the device card, in the Power controllers block, and needs the DEVICE_POWER_CONTROLLER_EDIT right from club access permissions.

What can be bound

Anything in the Yandex account that can be switched on and off qualifies. The appliance type does not matter.

What you bind	Example in a club	State readable	On and off
Smart socket	PlayStation power	yes	separate commands
Relay	power line of a row of seats	yes	separate commands
Smart lamp	desk backlight	yes	separate commands
TV or set-top box behind a remote	screen at a console seat	no	depends on remote
Air conditioner behind a remote	climate in the gaming hall	no	depends on remote

A device already taken by another binding cannot be chosen: the picker shows which club device or which club holds it. A lamp assigned as a POD booth light counts as taken too.

How it works

• Session starts — every binding of the device receives an on command.
• Session ends — an off command is sent, immediately or after the configured delay.
• A new session during the delay — the power-off is cancelled and power stays on.
• Creating a hold on a free device powers it up; releasing or expiring the hold powers it down.
• A console that does not answer — a console runs on external power only, so a failed power-on aborts the session start instead of leaving the player in front of a dark screen.
• A PC in monitoring mode is not power-driven: IZI only watches such a machine.
• A failed automatic power-off is retried on schedule and reported to Telegram when club power alerts are enabled.

Preparation

1. Add the hardware to the Yandex smart-home app on the club account and confirm it switches on and off from the app itself.
2. For a TV, set-top box or air conditioner, add a Yandex infrared remote. The app offers several similar models — pick a profile and try it on the appliance: switch it on and off from the app. A profile that only partly matches leaves some commands dead.
3. Get a smart-home token for the same account. The token is pasted once per club and afterwards picked from the saved list by its last characters and date.
4. Switch the appliance off before binding it. A fresh binding holds no record of the state, so the first “on” is always sent: if the TV was lit at that moment, a toggle code turns it off while IZI records “on” — and every command after that is one step out.

Binding in the CRM

1. Open CRM → Devices and the card of the device.
2. In the Power controllers block press Add controller.
3. Pick a saved smart-home token or paste a new one.
4. Pick the appliance from the list — its type and identifier tail are shown under each entry.
5. Set a name (the smart-home name is filled in for you) and the power-off delay in seconds.
6. Save.

The binding can also be prepared while adding a device: the form keeps the choice and creates the binding right after the device is saved.

Infrared appliances: state cannot be read back

An infrared remote shines at a receiver and gets no answer, so Yandex does not know whether the TV is on. Sockets and relays are measured; appliances behind a remote are not. The CRM shows the last delivered command rather than a measured state, and marks the binding “Behind an infrared remote: state cannot be read back”.

That leads to the rule by which IZI drives such appliances.

IZI never repeats a command

Infrared appliances do not tolerate a repeated command. Measured on a live Yandex remote:

Appliance	Repeated “on”	Repeated “off”
TV	switches off	switches on
Receiver	stays on	switches on

So the TV’s power is a single toggle code, while the receiver has a discrete on code and a toggling off. None of this is predictable from Yandex’s data: it advertised separate on and off codes for both. Often the cause is that the remote profile picked from a list of similar models only partly matches the appliance.

IZI therefore ignores those claims, remembers the last command it delivered and never sends it a second time. In practice:

• Pressing “Off” again in the hall on an already dark TV sends nothing — the TV will not flick back on.
• The cron that finishes a power-off after a connection failure only re-sends when the previous attempt never landed.
• If the appliance is switched by hand — its own remote, or a button on the case — IZI will not know, and keeps assuming the appliance is where IZI last put it. Drifted state is corrected by hand.

If you want repeats to be safe and state to be measured, put a smart socket on the appliance: it answers a state query and none of the limits above apply.

Power-off delay

The delay is the number of seconds between the end of a session and cutting power. Zero means cut it immediately. A delay matters where an abrupt cut does harm: a gaming PC gets to finish shutting down, a console gets to save its state. While the countdown runs the device counts as powered-claimed — a new session cancels the power-off.

Per-kind control from the hall

A seat can carry as many appliances as needed: a socket for the console, the TV behind a remote, the air conditioner behind a remote. The device command menu shows a separate on/off pair per kind, with a grey caption on the right naming it — “Sockets”, “TV”, “Air conditioner”, “Receiver”. An operator can switch the TV off without touching the console.

The caption is counted: two sockets on one seat give a single “On/Off — Sockets” pair that switches both at once.

Limits

• One smart-home device, one binding across the whole system.
• POD booths are not power-driven; their lamps are configured in POD lighting.
• A binding cannot be deleted while the device has an active or upcoming session.
• A token cannot be deleted while any power or light binding still uses it.

When something does not work

Message	What to check
Yandex token is not configured	The club has no saved smart-home token — add one in the binding form
Yandex token is invalid or expired	The token was revoked or expired — save a new one and rebind the appliance
Device not found in Yandex Smart Home account	The appliance was removed from the smart home, or it is on another account
Smart plug is offline	The smart-home device itself has no power or no connection
Yandex API error	A temporary failure on the Yandex side — retry later

A TV switching on instead of off is not a connection failure but a single-button remote — see the section above.

See also

• Devices Overview
• Add Device
• Club Access Permissions