@mega-yfue/eufy-sdk / MqttScope
Type Alias: MqttScope
ts
type MqttScope = "default" | "eufy_life";Which get_user_mqtt_info credential a device's realtime traffic rides on. "default" is the headerless credential (observed eufy_mega-scoped) that serves every non-life MQTT device.
A scope exists only where a DISTINCT credential does. eufy_life is one because its topic space is denied to the default credential. The Clean line (eufy_home) is NOT: its cmd/eufy_home/<model>/<sn>/res subscribe is confirmed against a T2351 on the default credential, which is the only one get_user_mqtt_info was ever asked for. Giving it a scope of its own would open a second connection under the SAME thing_name — AWS IoT treats a duplicate client id as a takeover and evicts the incumbent, so both lines would flap.