Update SDK to use the FlicTwist ?
-
@Emil
" But we want to make sure that what we release is something well-thought so that's why we are not rushing this. "You have had over 2 years since the success of the kickstarter if I'm not mistaken.
Not planning the SDK from the start was the problem, and now you have to "take your time" in order to "skohorna in skiten i efterhand" as we say here in Sweden.Whats the status? My twists are still lying in their boxes. Can't you at least open source your blutooth protocol, so that we can fix it ourselves?
-
We are currently working as fast as we can to fulfill the promises we gave in the campaign. The biggest thing there was Matter which is still our top priority.
For things we did not promise in the campaign, such as any kind of SDK support is also important for us due to the many requests we have got for it. We are aware that many of you in this thread want it "today" and would be happy to see something minimal viable rushed out to fit your particular purpose. But we want to make sure that what we release is something well-thought so that's why we are not rushing this. I hope you will enjoy the result when it gets released.
Please feel free to continue to post your preferred use cases for twist+sdk so we can take the right decisions
-
@Emil Please can we have an update? I almost bought an additional flic hub LR to use with my Flic Twist - I have 10s of buttons and 5 twists, several hubs... so I'm heavily invested, but did not imagine the SDK on flic hub still wasn't updated for Twist! I'm glad I tried it and found the support missing, before buying more...
I also use the linux sdk, which has been rock solid for years, it's really great! https://github.com/50ButtonsEach/fliclib-linux-hci but, it looks like ALSO is lacking Twist.
-
Ping @Emil, any update? My 3 twists are still used as paperweights….
Cant you just release something basic to start with?
I saw something about problems with how the sdk support will work with other integrations.I do not want any other integrations. SDK+MQTT is all I need. So just release SDK-support that disables everything else to start with! At least then we can start using the products we paid and waited for….
Or just Open source the hub software and I will fix it myself.
-
@dustingtorres Yes! It is one of the priorities we have currently.
-
@Emil Curious if Flic Twist SDK support is a priority for the Flic team? I just want to know if there will be support or not.
I am a huge fan of the hub SDK and I use it for my buttons (more than the native app). I have a lot of thoughts on how I could use Flic twist to help my team at work, but only with SDK support. I want to take advantage of the sale to purchase twists but only if I know SDK support will come in the future.
As a side note, I am very excited for matter support too but Hub SDK is even more versatile for those who want to do the deep dive technically.
-
@abboberg Side note, I have been trying to see if I could find anything useful in the Hub LR, but it's pretty limited, and no where near "like a raspberry pi", as listed on the product page.
It seems like the button doesn't yet have any twist properties on it yet, at least from what was passed in the button event.
I don't do much JS, so I had to look up some ways to get the properties, and I only checked when listening to the 'buttonSingleOrDoubleClickOrHold' event, and since the flicd or lib repos has not been updated, I have yet to find what other events it might be possible to listen to.
Button: CA22 [ "bdaddr", "wasQueued", "isSingleClick", "isDoubleClick", "isHold", "age", "constructor", "__proto__", "toString", "toLocaleString", "valueOf", "hasOwnProperty", "isPrototypeOf", "propertyIsEnumerable", "__defineGetter__", "__defineSetter__", "__lookupGetter__", "__lookupSetter__", "on", "emit" ]
-
@abboberg Yeah, it's quite frustrating to now be two years waiting and $200~ invested into this ecosystem under the marketing promises that it was to be super customizable, open and 'fully programmable' to do with what you please. Only to receive items which are currently no more useful to me than the pile of other buttons I have sitting around which cost a fraction of the price, and at least work out-of-the-box as advertised.
Starting to feel rather duped by said marketing promises. No one gives any actually useful information, just vague, eventually/maybe type answers, etc. Definitely not an experience I would want to recommend to anyone else to have to deal with.
Why even bother shipping the product when it, effectively, provides none of the major selling points that were pushed toward the targeted audience?
All I have received so far is disappointment.
-
@mosthated said in Update SDK to use the FlicTwist ?:
It's been over two weeks since the last official reply. It would definitely be nice to see some updates on the status of this. As of now, I waited two years for a pair flic paperweights.
I see an update of the version number from 4.2.11 to 4.2.13.
No sign of any changelog. Neither in the sdk-documentation.My hope is still on a added 'ButtonTwist'-event in the Button_class
-
It's been over two weeks since the last official reply. It would definitely be nice to see some updates on the status of this. As of now, I waited two years for a pair flic paperweights.
-
I paid for my FLic Twists in Dec 2021 and I have eventually received them. There were many stories along the way about delays with getting the mechanical aspects of the manufacturing right so you would have thought that by the time they were delivered there would have been ample opportunity to get the software ready ... but apparently not. Can we at least have a timescale for when you hope to have the SDK updated?
-
@Emil You really need to fix this. It can't be a big fix to include the new button presses in the SDK, everything else seem to already be in place.
Please prioritize this. Or make the SDK open source so that we can fix it for you. -
@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 ok. thank you for your reaction.
But if the current hub fw version is 4.2.11, where is the 'full Flic Twist support' (mentioned in the blog-post)?
Second; i can see a [changelog] button next to the Phone App version (3.10.3 on my Android) but no [changelog] button next to the Hub version.
-
The Backers waited a very long time for their purchases, now the flics get delivered and there is no other event avaiblable as ''buttonSingleOrDoubleClickOrHold", did i get that right? No twist oder push twist events supported via SDK?
I can't believe that.
What's the timeline for supporting the whole product?
-
@Niels See my reply here: https://community.flic.io/post/20836
-
@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?
-
Agreed, most functions of the Twist should be supported by the Hub, as I'm using many devices that aren't supported by Flic out of the box, but I'm using them e.g. via API
-
@abboberg All our firmwarers are auto-updated. In some cases we have assigned a specific firmware to specific people on request. Please reach out to us if you want to go back to the public release track.
The current hub fw version is 4.2.11.
Usually when we update the hub firmware we also update the apps. In the apps you can see a Change log in the settings menu.
-
@abboberg @Emil
I have FlicHubLR firmware v4.2.11, visible in SDK and FlicApp.In the recent backer-post-update (#21, 16-oct-2023) you wrote
"We have a new firmware released for our Hubs (including the old Flic Hub) so they now have full support for Flic Twist and its functions."great !
But I am wondering;
- what is the version of this new firmware?
- are there any proper release-notes and documentation?
- is the firmware at someday auto updated or can I do anything?
Keep us updated and informed!
(this can also be in this flic-community)