[1.1.4-rc14] - 2026-02-21
Fixed
- Offline device not registered — Devices that fail local network connection (e.g.
online: false) are now registered in Matterbridge in MQTT-only mode instead of being silently skipped. Previously, a failedget_network_inforequest caused an early return, resulting in only one device appearing when multiple vacuums were configured. - Message routing DUID filtering —
V1ResponseBroadcasterandB01ResponseBroadcasternow filter incoming messages byduidbefore dispatching to listeners, preventing messages intended for one device from being routed to another device's listeners. - Multiple map active map update —
getRoomMapis now only called whenisMultipleMapEnabledis enabled, avoiding unnecessary MQTT requests for single-map setups. SimpleMessageListenercrash on non-object result — FixedCannot use 'in' operator to search for 'state' in 104error when a device returns a primitive value (e.g.result: [104]) instead of a status object. Addedtypeofguard before the'state' in messageBodycheck.
Improved
- MQTT connection readiness check —
initializeMessageClientnow waits for bothisReady()andisConnected()before proceeding, ensuring the MQTT connection is fully established. - MQTT topic logging — The full MQTT publish topic is now included in the debug log for easier tracing.