Posts made by Emil

@knewe Thanks, I got your video.

After you have pressed Save & disconnect, and the configuration has been saved successfully, the button is now ready to be used as a keyboard on any Bluetooth compatible device such as a PC, tablet or phone. To use it as such a device, you must manually go into your system's Bluetooth settings and add it as such a device, even if you want to use the Flic button on the same device (i.e. the one that has the Flic app).

Note that after you have pressed Save & disconnect and have been taken back to the home screen of the app, you must NOT press the icon representing the button again, since that will reconnect the Flic button to the Flic app and hence change the mode of the Flic button from a keyboard to a normal Flic button. You should only do this when you for some reason want to reconfigure the Flic button again.

@knewe I don't really understand why it's not working for you. Maybe you can shoot a video or something from the point where you press save & disconnect and then try to pair the device "FLIC" that should appear in the system's bluetooth settings when you search for devices. (Note that you need to make a short press on the Flic button to make it advertising)

@knewe You need to follow this step where you click "Save & Disconnect". Otherwise it won't work:

@werner-kneile Did you press "Save & Disconnect"? This will disconnect your button as a Flic button. The Flic will instead advertise itself as a normal Bluetooth keyboard and you need to add it using the system's Bluetooth settings.

@hmmwhatsthisdo Could you elaborate what you did when you unregistered the hub from device manager? There should be a red trash can icon which will delete the hub. Make sure you are not just removing it from a group or similar but remove it completely.

@hmmwhatsthisdo Sorry, I was maybe too fast typing my reply or not clear enough. The hubs on the Device Manager path have slightly different firmware builds compared to firmwares for non-device manager. Therefore, the "latest stable" on Device Manager does not necessarily correspond to the same latest stable version for the normal consumer firmware as we require different testing for Device Manager hubs vs consumer hubs. The Device Manager firmwares might also lag a bit in regards to functionality compared to the consumer version.

That said, I now see that the Twist features have yet not reached the firmware used for Device Manager hubs. I will escalate this issue and try to get it resolved ASAP. In the meantime I suggest that you deactivate Device Manager for this hub if you want to try out the feature.

@hmmwhatsthisdo I see. That hub is registered with the Device Manager. With the Device Manager activated, you select yourself which firmware version you want it to have in the Device Manager portal. Try to select the latest version instead and then trigger a firmware update.

@hmmwhatsthisdo-flic Can you please try to update the firmware to the latest version (should be 4.4.2)?

@johan-0 The IR functionality in the Flic Hub is pretty simple. It just records an IR signal and then replays it. If the IR remote typically sends a dynamic signal (or something that is not static), the receiver might not accept a replayed signal. If you use the Hub SDK, you can both inspect recorded signals but also create your own signals by defining the "raw" data.

@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 don't have a voting system unfortunately.

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