Alex2Node/test/compat
David 2f6730eb52 device: the client of new Device() and setMqttClient() warn once
2.0 ignored the first argument of the Device constructor in silence and
had removed setMqttClient(), so a 1.x call threw a TypeError. Both are
deprecated shims now, as the design lists them: setMqttClient() is back
and does nothing, a client given to the constructor is ignored, and each
says once in a process what to do. The line goes to the log hook of the
bridge; a device on no bridge has none and emits a DeprecationWarning
(ALEX2NODE_DEVICE_CLIENT, ALEX2NODE_SET_MQTT_CLIENT).
null and undefined as the client warn nothing: the bridge passes null.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-28 21:19:10 +00:00
..
capabilities.test.js discovery: generate capability JSON from the registry 2026-09-28 15:35:46 +00:00
deprecations.test.js device: the client of new Device() and setMqttClient() warn once 2026-09-28 21:19:10 +00:00
messages.test.js bridge: publish through a Publisher; devices no longer hold the broker client 2026-09-28 19:34:39 +00:00