Skip to content

@mega-yfue/eufy-sdk / BIZ_CHANNEL

Variable: BIZ_CHANNEL

ts
const BIZ_CHANNEL: object;

The channels a map frame can arrive on, by id.

The trap. Ids 1–10 come from Metadata.ChanIds in stream.proto, where each field names a message and each field's value is the id the device chose for it. The names below pair each channel with its field NUMBER, because that is the numbering the vendor ships and the one a live capture shows — but a device announcing a Metadata frame is announcing its own numbering, and a firmware that renumbers would make this table wrong without making it look wrong. Anything that decodes a channel's bytes must therefore prefer a device-declared mapping when one has been seen; this table is the default to fall back on, not an authority.

Channel 0 is the exception and is not in ChanIds at all: the app hard-codes it, routing it to a scene-data event rather than a map one, and asks for the scene list on it by number. That one is fixed.

Type Declaration

CRUISE_DATA

ts
readonly CRUISE_DATA: 10 = 10;

DYNAMIC_DATA

ts
readonly DYNAMIC_DATA: 6 = 6;

MAP_DATA

ts
readonly MAP_DATA: 9 = 9;

MAP_INFO

ts
readonly MAP_INFO: 1 = 1;

OBSTACLE_INFO

ts
readonly OBSTACLE_INFO: 8 = 8;

PATH

ts
readonly PATH: 2 = 2;

RESTRICTED_ZONE

ts
readonly RESTRICTED_ZONE: 5 = 5;

ROOM_OUTLINE

ts
readonly ROOM_OUTLINE: 3 = 3;

ROOM_PARAMS

ts
readonly ROOM_PARAMS: 4 = 4;

SCENES

ts
readonly SCENES: 0 = 0;

Scene (room-group) data. Hard-coded in the app, not part of ChanIds.

TEMPORARY_DATA

ts
readonly TEMPORARY_DATA: 7 = 7;

Independent and unofficial. Not affiliated with, endorsed by, or sponsored by Anker Innovations, Anker eufy, or eufy. "Anker eufy", "eufy" and "Anker" are trademarks of their respective owners. Use responsibly — rapid or failed logins can trigger captcha or temporary cooldowns.