@gordon-0 If you use the Android app, then you can create a custom config using the "Configs" provider in the app. Then you can create a Task having the "Change Config" action which loads the settings of a specific Flic button with a precreated config. You can repeat this for every config you want. Then, execute the task when you want to change the config. If you hold on your phone's home screen, you can create a Flic widget, which will allow you to easily execute tasks.
@Astro We have in the backlog to add the feature to play a Sonos Favourite. That way you can set a radio station as a favourite and then start that using Flic.
@stevehurcombe Hi. We will take a look at this when we are back from summer holidays.
@thomas-vorndran Hmm ok... What Hub FW version do you have (and what Hub variant) and what app version?
@stevehurcombe said in Matterbridge, Flic twist and Home Assistant:
Hi,
I've installed Matterbridge, connected it to Home Assistant and I've connected it to the Flic app.However in the app all the devices show as the name 'Matter device'. What am I doing wrong? Obviously I'm aware that there are two API connections and three developers involved, but I have to start somewhere.
Ok, let's start here then 
The name that shows up is read directly from the remote device over the Matter protocol. The name is stored in the NodeLabel attribute in the (Bridged Device) Basic Information cluster. If the name is missing, we try to show something else, like the product name. You can however change the stored name using the Flic app if you go in to the Providers settings and then under Matter. This will send the new name over the Matter protocol to the remote device and it will be stored there.
Since you are using a Bridge, the name is most likely simply stored in the Bridge software. I'm not sure if Matterbridge has a UI to configure the name or not.
Secondly, I've added a Spotify account to Home Assistant, which then appears as a media device. Matter supports Media, can that be enabled for the Flic twist? Then I can use it for volume control and playback and even track\playlist selection.
In my opinion the Media support in Matter is currently not the best. In any case, can you check using the "Matter Other" action to see if it exposes the Level Control cluster (for volume), the Media Playback cluster (for next/previous/skip etc.) and/or the Content Launcher cluster (for launching content either from a search or a URL)?
@thomas-vorndran Sonos will soon require Sonos account authentication for accessing Sonos products. Before this is enforced in a few months, the latest firmware currently requires the user to login using the Sonos account before any action can be saved. So please press "Setup" and then login with your Sonos credentials.
@mosthated Hmm I just tried to reproduce this, but the latency is always instant for me. The LED on the hub should light up when the button is pressed. Does this have the same latency as well? Have you tried any other actions, like turning on some smart light? Just trying to figure out where the issue might be...
@rickard Yes! This will be possible, but note that we have not yet started to ship Flic Duo. We still need to finalize the Hub SDK events for the Duo so I can't give you an example right now. For MQTT itself, please see https://github.com/50ButtonsEach/flic-hub-sdk-mqtt-js.
@mosthated The Android app with this functionality has now been released!
@buckyswider Yeah you shouldn't really trust all the generated nonsense text AI bots spit out, especially if there are no cited sources that can validate the stated facts. In this case, you can ignore everything it says as everything it says is just misleading.
During the commissioning phase, the device does not advertise _matter._tcp but _matterc._udp.
The _matter._tcp service is advertised in the operational state, i.e. after it has joined a fabric. If it has joined multiple fabrics, it will advertise one service per fabric. It will continue to advertise this service (forever) as long as it wants to accept Matter commands and stays on the network.
When I say "advertise", I use the same terminology as in RFC 6762 (the mDNS standard specification), i.e. when a service is "advertised", it means the service is registered on the local network according to the rules in the mDNS standard. On a low level, according to the mDNS specification, this means that unsolicited udp packets containing the dns record can be sent from the device, e.g. when it boots up so that clients performing service browsing can quickly be notified about its presence, as well as that it will respond to explicit queries requesting that service. It seems ChatGPT means "send a udp packet" when it says advertise, which is not really the same thing. It is of course true that a device does not blast mDNS packets all the time as long as it is "advertising" a service.
DNS-SD with mDNS is more or less standard nowadays for devices on the local network that need to be able to be discovered by other devices. Chromecast, Spotify Connect, Airplay, printers etc. all use this protocol.
@pico We currently use QuickJS and it seems like that js engine does not support that Intl feature.
We might add the feature to set time zone, it can be useful for a few other purposes as well, e.g. in timestamp header for our Internet Request action. But right now I suggest to use the workaround I suggested.
@pico As you can see on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleString, the parameters supplied are only used if the Intl.DateTimeFormat API is supported. We don't support that API and hence you can't get any time zone support, unfortunately.
I would suggest you to manually extract the components using getUTCHours, getUTCMinutes, getUTCSeconds etc. and then apply your time zone offset and DST formula manually, which should be doable if you know you will only be using a fixed time zone.
@buckyswider _matterc._udp is for commissioning, so that one is only present while the device is "pairable", typically 15 minutes after boot when the device is factory reset (i.e. no Matter pairings yet).
_matter._tcp shall be advertised after the device has been commissioned (paired), one service per "fabric" (i.e. per "hub" it has been commissioned to), as long as it is powered on and connected to the network. If it does not advertise this service, it will not be possible to reach it by Matter controllers. If you don't see this service when you expect to, it seems like a bug in that device.
Maybe you have devices from other Matter brands you can test with?
@buckyswider yes, assuming your phone/tablet you run the app on is connected to the same network as the flic hub and the Matter device, all Matter devices that are currently paired shall advertise that service, regardless of if it's connected or not.
@buckyswider We have planned to add network packing logging to the hub in order to be able to debug situations like this, but have not yet had time to do that. The Flic Hub runs a DNS-SD listener in the background, waiting for its paired Matter devices to come available, and then connects to these. So the first step you can do is to use any DNS-SD app (like this https://play.google.com/store/apps/details?id=com.druk.servicebrowser) and verify that your device is there. Matter devices advertise themselves under the _matter._tcp service.
@djadin14 maybe you got a defect unit. You should contact support at https://flic.io/support and see if you are eligible for a replacement.
@j that is the simplest way to get automatic access to your flows. You can probably set up your manual web hooks if you want, using the http request action, but you need to manually enter the url.
@j the homey action is cloud based. The Flic Hub communicates directly with the Homey cloud servers.
@kerry-thacher the action should definitely be there for Flic 2 buttons, as long as they are directly connected to a phone/tablet (not through flic hub).