While you are able to subscribe to some Xiaomi Cube events from the MQTT app, they are never published to the MQTT broker. Further it seems that by virtue of subscribing to Xiaomi Cube events, after awhile the MQTT bridge stops receiving events. Causing a bridge reset (by adding / removing device subscription) restores event processing. Based on this it would seem the issue is with the Xiaomi Cube device driver, however not being familiar with driver requirements in general, not exactly sure what the problem may be.
You of course can make the case that there is no point in subscribing to Xiaomi Cube events if they are not published to the broker, but perhaps the two issues are related and someone more familiar with the code can determine the issue.
While you are able to subscribe to some Xiaomi Cube events from the MQTT app, they are never published to the MQTT broker. Further it seems that by virtue of subscribing to Xiaomi Cube events, after awhile the MQTT bridge stops receiving events. Causing a bridge reset (by adding / removing device subscription) restores event processing. Based on this it would seem the issue is with the Xiaomi Cube device driver, however not being familiar with driver requirements in general, not exactly sure what the problem may be. You of course can make the case that there is no point in subscribing to Xiaomi Cube events if they are not published to the broker, but perhaps the two issues are related and someone more familiar with the code can determine the issue.