@Emil Are you there Emil?

@chris-3 Our current number one priority is support for Matter. Assuming Home Assistant implements Matter bridge, that should mean the Twist will be able to control devices in Home Assistant through Matter.

@samjay You're a legend. That was absolutely the problem; the buttons were indeed showing in Default. Thanks 🙂

@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.

@Emil

Thank you very much for the idea.

I tried again using my phone's hotspot, and it worked.

It gave me the idea the home network could be the issue.

I turned off the Eero Advanced Security feature. Now, the Hub can talk to Alexa.

@steven Hi Steven, no it is not available in the Hub Actions in the Flic App. This is a module which can be used in the HubSDK with your Hub LR. Please check out this repo: https://github.com/50ButtonsEach/flic-hub-sdk-mqtt-js
And in case you are not familiar with the HubSDK, please check hubsdk.flic.io, https://hubsdk.flic.io/static/tutorial/ and https://hubsdk.flic.io/static/documentation/

@djay @Emil After several attempts to reset the Hub LR again and stuck even not getting it back/discovered by the Flic App, now it's back. And out of the blue the “Configuration needed - need to pair Flic Hub with your home - wants to access Home-Dialog, showed up again.
I have no idea what caused the problem and no idea what really solved it, other than to try and try and try again for two hours. 😕

@djay I see... Something seems to be wrong with the iOS app; we're working on it. You should be able to use the Android app in the meantime to configure Dirigera, if you have an Android device.

@Emil It was before the factory reset which put it back to 3.0.3 as reported in the app. I heard via email that someone fixed it in the backend and I should be able to try updating again, just checked for updates and now it is back on 4.2.4 as of 2 minutes ago.

Thanks!

@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.

@oskar I try to get the hub to communicate with Touch Designer. As I understood I need to fill in the correct IP and Port in the first line of the main.js
Unfortunately I can't get it to work. The console tells me that the message is sent but nothing happens in Touch Designer. Any hints on that?
All the best, Pascal

@mp What exactly do you mean when you say "network loop"? This is not a problem we have heard of before, so any more info would be helpful.

@tnx this is by design.

Buttons connected to the phone will sound on the phone and buttons connected to the hub will sound on the hub.

It does not make much sense to play sound on the phone for buttons connected to the hub since the communication channel between the hub and the phone is down when you close the app, or go out of range.