Do you really need two different objects to communicate with these devices ?

Hi @larkei15
I don't think using a Repeater for dynamically changing models is the best approach.

From the Cadaques book:
https://qmlbook.github.io/ch06/index.html

For static models, a Repeater can be used as the view. It is easy to combine it with a positioner such as Row, Column, Grid or Flow to build user interface parts. For dynamic or large data models, a view such as ListView or GridView are more appropriate. These create delegate instances on the fly as they are needed, reducing the number of elements live in the scene at once.

And from the QML doc:
http://doc.qt.io/qt-5/qml-qtquick-repeater.html

Considerations when using Repeater
The Repeater type creates all of its delegate items when the repeater is first created. This can be inefficient if there are a large number of delegate items and not all of the items are required to be visible at the same time. If this is the case, consider using other view types like ListView (which only creates delegate items when they are scrolled into view) or use the Dynamic Object Creation methods to create items as they are required.

I wager your syncing problems are due to that...

Is there any reason why you are choosing the Column + Repeater approach over the ListView approach?

For future reference, the bug I logged was marked as a duplicate.

Here is the link to the original, QTBUG-43454.