@normshige please go to https://flic.io/support

@normshige Apple has made some rearrangements in the Home app. Could you go in and see if they are located in the "Default room"?

@snorre-svendsen After a recent round of updates from Apple, buttons are again showing up in «Default room».

@Smellyglove I understand it like you want a Flic button action to trigger a computer (far, far away..) via Ethernet? I would probably set up a HTTP request command from the Flic to an endpoint. Directly or via a server, or maybe an websocket connection. But you might be able to do this even easier using some automation, like Zapier, a "no code" solution. 👍🏻 https://zapier.com/apps/flic/integrations/zapier

@Emil After 4.2.5 update for the hub the brightness control works again. Thanks for the quick solution.

@me-2 It's a work in progress. May I know why the server requires TLS 1.3? TLS 1.2 is still widely used and will probably be that for a long time.

@Emil sorry, that was a pre-coffee morning typo, I meant DNS, not DSN.

I didn't know .local was reserved for mDNS only, as it has been working fine so far. Thanks! I should be able to solve the issue from here.

@adrian_tam You can make an action chain "directly" under a button as well. Just assign multiple actions and they will all be executed.

@bolloxed what do you mean exactly when you say "open and running"? Do you mean the app is in the foreground and visible on the screen?

It should work even when you suspend the app, i.e. when you navigate to another app or turn off the screen. It will however not work if you terminate the app by force quitting it ("swipe kill" in the recent apps list, https://daringfireball.net/2017/07/you_should_not_force_quit_apps).

@atruttmann Hi! Unfortunately this clashes with a build in functionality that after 8 seconds the Flic will disconnect and advertise in "Flic mode". This is to give users a way to connect the Flic back to the Flic app in the case you would not be able to disconnect it from the other device.

@oskar echoing @N3Op's question. I am also seeking this functionality in the Android app.

@oskar Thanks for the suggestion. I tried that and the BT setting as well just to cover both bases. Turning them off and back on did not resolve the issue. I know I'm running something called SonosNet on my Sonos setup due to the amount of Sonos devices and the layout of my home. Are you aware of any issues with the Flic working in that configuration? Running out of ideas to try so let me know before I start a return process.

Thanks

Dumb response - asking why serial number is required. Clearly not a good developer - It should be patently obvious that Homekit uses button Serial number not Hub button name.
Therefore, if you have a number of buttons it becomes a chore to identify which is which, e.g. lounge appliance button or kitchen appliance button

@info-c Solved, thanks to support Uzoma. turn off the sound of the button on your device, tap the button you want to change in the app. At the top of your screen, on the right, click on the three dots for options and select settings. In the settings page you'll see Button notifications with options for (None, Vibrate, and Sound). Here, you can select either None or Vibrate; depends on what you want

@jeanna-h I still would recommend Lifx in case you don't want any hubs, since Lifx has a built in wifi chip. Flic communicates with the Lifx bulb without the Lifx app, so it will still work if you shut it down.

Other lights that work with Flic than the one we support directly go through for example Alexa or IFTTT.

@klaas it's not something we have a direct integration with. You will need to write an integration using our sdks or so.

We could maybe give better help if you provide more details.

@mp not sure exactly what you mean here. You say that both interfaces take the same ip address but having two ip addresses is an issue?

What happens is that each interface will get an own ip address. This is how it always is when a device has multiple interfaces. When the hub makes for example an http request, it will use the interface that the kernel determines currently is the best one. If one interface gets disconnected, it will use the other one.

How would you like it to work instead?