@daniel-silcock You should just need to add the Alexa action to the button in the Flic app. Then, in the Alexa app add the Flic skill and login to the Flic account. That will let you add triggers. Be sure to have your Flic hub or phone connected to the internet, as this is a cloud to cloud action.
Hi. You could try to ask this question on some Apple forum since we do not have knowledge about this. We know how to deliver button events to Homekit but then it's up to Apple how the rest works.
If you're lucky maybe some Flic user that knows something will answer here.
Hi. The only way to play custom commands right now is to use the Hub SDK. Use the method at https://hubsdk.flic.io/static/documentation/#37_play to play a raw signal.
@ymsetjenesta Where do you see this? Can you send a screenshot?
@derek-erb I get your point. It's written on the back side of the button under the battery (so you have to open it), but it would be more accessible in the app. I'll see what we can do to include this serial number!
Right... In that case I don't think there is anything you can do since that is how we designed the pairing flow.
@sandro-salari You can use any general purpose Bluetooth Low Energy scanner or any of our sdks to get the bluetooth device address of nearby devices. (except on iOS where this information is not exposed)
@sandro-salari Not sure exactly why you don't want to pair, since using Flic without pairing will mean no security. In any case, if you already know the Bluetooth device address of the button, you can still connect to the Flic in private mode, even though the advertisement is empty. This would have the benefit that the user would not have to hold down the button for a few seconds.
@sandro-salari What exactly are you trying to do? Why do you want to force disconnect? Doesn't the normal pairing flow work for your use case?
Once the button is paired, the button will not be in public mode during normal user interaction. Then it will not start re-advertising if you disconnect it.
It could be a hardware issue with that particular flic. Please send a support request at https://flic.io/support.
Hi. Once the Flic 2 is set to public mode, it will stay in public mode for 30 seconds. When it disconnects before this timer expires, it will always restart advertising, regardless of the flag in the "force disconnect" packet. That flag thus only has effect in private mode, since then by default the Flic 2 will not start advertising again after a graceful disconnect.
Hello,
The only way to reset the HomeKit pairing is via a factory reset of the Flic Hub, which is how it must be done according to Apple's requirements.
Begin by looking in the Home app under Menu -> Home Settings -> "Home Hubs & Bridges" and make sure that the hub is not visible there. If it is, then delete/unpair it.
Now perform a reset by pressing and holding the pin hole button on the Flic hub for between 10-15 seconds exactly (aim for 13 seconds). Not less, not more. Once complete the LED will flash a few times and then reboot. Also delete the Hub from the Flic app and then scan for it again once rebooted.
When going through the HomeKit setup, make sure that you reach the final step where it says "Bridge Added to My Home”. (Like in this video at 1:13:
)Also, at the second last step, where it says "Bridge Name" (1:11 in video), you can press the Identify button. Doing this should immediately flash the LED on the Flic Hub and thus confirms that the HomeKit connection is properly set up and that the Hub is reachable. Verify that this is the case. Then, at the very last step (1:13), make sure you press "Done" and not "View in Home". This will take you back to the Flic app and the HomeKit actions should automatically assign to the button. Make sure that this happens, then back out of that view, then select the button again to go into it and see that they are in fact saved.
At this point you can disconnect the Hub and move over to the Home app. If the hub is not visible in the Home app at this point, then there must be some internal issue in HomeKit that has occurred.
@millbraetrains We don't have a list of exact model numbers.
We support devices that respond to SSDP requests where the device type is "bridge", "insight", "controllee", "lightswitch", "dimmer" or "Socket".
@thomas-0 We have that certificate in our trust store. Make sure the certification path is really correct. Some clients can be more permissive than a strict one. You might be able to use a third-party tool for checking the validity of the certification path.
@abboberg Edge v93 works fine for me. Do you see a green or red icon on a hub listed on the welcome screen?
@abboberg Fw 2.0.19-sdk2 was an old beta firmware that is no longer compatible. I've removed everyone on that track to be on the current. If you do a fw update now you should get a version that works.