Another +1 here.
Not being able to use the SDK means that the twist is just a bigger button for now.

I don't understand how it's being communicated that there is full hub support for the twist when there isn't SDK support.

@Emil said in Flic Twist - not what I was hoping for:

When we released the Flic 1 button, the functionality was quite limited too.

But you (probably) didn't advertise that as being fully supported. At best it was fully supported with everything that was there then. The Twist currently just isn't fully supported yet. Your company grew and so did the expectations that people have. Being told truthfully what the limitations of a product are is pretty basic. Unless I missed something, there was no indication that current features would not be supported initially and that some features were excluded from being 'fully supported'.

That said, we are actively working on adding the features that our users request for the Twist

SDK functionality isn't just something that users are requesting, it's something that was promised (or expected) to be there. The Hub supports the SDK and 'fully supports' the Twist, what do you mean with 'fully supports' if it isn't supported in everything. At best, there is partial support now.

Matter support was promised at a later date, now it gets priority over basic functionality? I'd say that's backwards. Matter is cool additional functionality, SDK access is required to make it function at all for many people here.

I'm probably underestimating the difficulty, but how hard could it be to add the required events in the already existing sdk. Or even better, why aren't you building your functionality on your own sdk? That's imo the best way to ensure that the SDK is complete and useful.

My personal priority list:

• SDK support: This will allow me to use the device on any Smart Home system using MQTT.
• Native Home Assistant support: or SDK access on the Hub Mini, or native MQTT support.

@Emil This is a response to the secondary questions, not the primary one about SDK availability.

Seeing that the twist is fully supported, how can we use it in the SDK? If we can't is there a timeline for when we can?

@Emil what part of that reply answers the question?
The question was 'How can we use it in the SDK?' and 'Is there a timeline for when we can?', at best the reply states 'We are actively working on... stay tuned'.
Is that a 'You can't' on on being able to use it and a 'No' on having a timeline?

@Emil what part of that reply answers the question?
The question was 'How can we use it in the SDK?' and 'Is there a timeline for when we can?', at best the reply states 'We are actively working on... stay tuned'.
Is that a 'You can't' on on being able to use it and a 'No' on having a timeline?

@Emil said in Flic Twist - not what I was hoping for:

When we released the Flic 1 button, the functionality was quite limited too.

But you (probably) didn't advertise that as being fully supported. At best it was fully supported with everything that was there then. The Twist currently just isn't fully supported yet. Your company grew and so did the expectations that people have. Being told truthfully what the limitations of a product are is pretty basic. Unless I missed something, there was no indication that current features would not be supported initially and that some features were excluded from being 'fully supported'.

That said, we are actively working on adding the features that our users request for the Twist

SDK functionality isn't just something that users are requesting, it's something that was promised (or expected) to be there. The Hub supports the SDK and 'fully supports' the Twist, what do you mean with 'fully supports' if it isn't supported in everything. At best, there is partial support now.

Matter support was promised at a later date, now it gets priority over basic functionality? I'd say that's backwards. Matter is cool additional functionality, SDK access is required to make it function at all for many people here.

I'm probably underestimating the difficulty, but how hard could it be to add the required events in the already existing sdk. Or even better, why aren't you building your functionality on your own sdk? That's imo the best way to ensure that the SDK is complete and useful.

My personal priority list:

• SDK support: This will allow me to use the device on any Smart Home system using MQTT.
• Native Home Assistant support: or SDK access on the Hub Mini, or native MQTT support.

@Emil This is a response to the secondary questions, not the primary one about SDK availability.

Seeing that the twist is fully supported, how can we use it in the SDK? If we can't is there a timeline for when we can?

Exactly the same issue here. Ordered a few minis to get better reception than when using a single hub but everything for me is connected to Home Assistant. I should have, but hadn't noticed that the hub mini doesn't have the SDK.

This repo is GPL licensed, but it should be an easy template to implement Home Assistant support via MQTT, but not being able to use the SDK on the mini makes it useless:
https://github.com/id628/flic2hass

If the hub would be able to connect to MQTT and publish events it wouldn't even need to add the HA Discovery stuff, we would be able to do that ourself.

Smart home devices like these should have first class MQTT support nowadays.

Another +1 here.
Not being able to use the SDK means that the twist is just a bigger button for now.

I don't understand how it's being communicated that there is full hub support for the twist when there isn't SDK support.