@Emil I am sympathetic to the difficulties of effectively communicating product complexities. These implementation details you provided are interesting to me personally, but they are not particularly helpful to an average customer. It really feels like y'all have not carefully considered the types of questions a customer new to any of your products might ask. e.g. "I have/am interested in this product; does it have this capability?" or "I already have a Flic Button, can I do the same things with a Flic Twist?" Customers expect a certain level of consistency between different products from the same company. When you fail to deliver that consistency—and you do not effectively document the differences—it leads to frustrated customers.
The product matrix on the Twist product page comparing the Flic Button and the Flic Twist seems like a good place for some of this information. You already have a "Compatibilty" row in that matrix where you could explicitly list "Flic For Mac app" in the Flic Button column, and omit it from the Flic Twist column.
In the Flic For Mac app itself, on the "Add Flic" page next to the Flic Button illustration you could show a picture of the Flic Twist encircled by the crossed out sign.
Meanwhile, the Flic For Mac app page does not explicitly mention that it cannot configure a Flic Hub. That seems like a good place to mention that, especially when it is perfectly reasonable for a customer to assume that it can. Maybe add a feature matrix somewhere comparing the respective capabilities of the Android, iOS, and Flic For Mac app?