Posts made by Emil

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

@gabrielmgrossman Please file your issue to https://flic.io/support.

The problem is that groups can be pretty dynamic. You can hold the play button on one player and it automatically joins another group that is playing music in your household. And with the sonos app it is easy to move around speakers between different groups. That said, it is possible that a group id that was valid when a flic was configured might not be valid after a while after grouping back and forth.

That's why we think it's more simple to pick a player you want to play on, and we will then at runtime when the action is executed check which group that player belongs to and play on that group. May I ask in what circumstances this strategy is a bad idea?

@mx5_94 Seems like a very powerful option. We'll definitely implement that!

@SME This works perfectly fine in the Android app. You find the KEYBOARD COMMAND action under the Flic Universal category. There you select "Keys" and then A, B or C.

@mx5_94 thanks for the feedback. I assume you think it's more convenient to use sonos favourites over sonos playlists?

@craig-2 we are internally experimenting with our new hub sdk features (https://community.flic.io/topic/18536/new-flic-twist-features-for-the-hub-sdk) together with home assistant (communicating over mqtt) and it works pretty good. So that is one option.

The other option is to expose devices in home assistant as matter devices, as explained here https://community.flic.io/topic/18457/home-assistant-twist-another-angle.

@mosthated Sorry forgot to mention that only the iOS app shows this provider right now. It will come later to Android.

@bmatest0910 You need to carefully study the readme at https://github.com/50ButtonsEach/flic2lib-android, in particular the section https://github.com/50ButtonsEach/flic2lib-android?tab=readme-ov-file#scanning-for-new-buttons. What API level does your app target and what Android version does your device have?

If targeting and running on Android 12 or higher, ACCESS_FINE_LOCATION is not the permission that you should request at runtime, but BLUETOOTH_SCAN and BLUETOOTH_CONNECT.

If you really need ACCESS_FINE_LOCATION in your app for your other purposes, not Flic-related, such as GPS, you need to follow the instructions at https://github.com/50ButtonsEach/flic2lib-android?tab=readme-ov-file#api-versioning-and-manifest-permissions.

@beachb_sl the buttons communicate using Bluetooth, not wifi. May I ask you where you have read that they use wifi?

Bluetooth Long Range is a feature introduced in Bluetooth 5.0 (also called Coded PHY) which uses error correcting codes so that the receiver can restore the packet content even if a few bits are lost.

@gerald don't you see my reply?