Posts made by Emil

@mullz Now I get it. There is another bug in both the code from @oskaremilsson as well as the code from @jitmo. By using the .on method on the IR object, you add a new listener (i.e. append it to the list of listeners). You never remove the listeners, however. That's why all the registered listeners get called on every recordComplete event. You can for example use the .once method instead. Just remember to also manually remove the listener when you cancel the recording process using for example the .removeAllListeners method.

@mullz I couldn't reproduce the issue. Seems to work as intended for me with oskaremilsson's code.
One thing I noticed is that the conversion to string might not always work correctly the way the encoding is done. The string that is to be saved needs to be stored in proper UTF-16 format; now you could theoretically accidentally create invalid surrogate pairs.

@sam What do you mean with "I can't remove it"? If you press the item there should be a menu appearing where you can select "Delete".

@nathan-scofield If you press the item there should be the option to Delete it?

@HSDK Do you mean that the Sonos integration works as follows:

• Android: Yes
• iOS: No
• Flic Hub: No

?

@rickard the hub sdk will now emit duo events. There is no documentation written yet but if you print the events json serialised you will see how it works.

@gamhacked00 said in Spotify Web Connect on iOS is really unreliable:

Reopening the app fixes the problem

Do you mean the flic app or the Spotify app?

We have noticed this as well, but it is simply how the Spotify API works.

See https://github.com/50ButtonsEach/flic2-documentation/issues/5#issuecomment-3693331760

@sgemmen The hub firmware with Hub SDK support for Flic Duo is pushed out now (version 4.6.0). The documentation is not yet out but you can see an example event here that includes button number, orientation and gesture:

buttonUp {"bdaddr":"90:88:a9:5b:10:62","wasQueued":false,"buttonNumber":1,"orientation":{"x":-1.530368,"y":0.109312,"z":1.952},"gesture":"right","age":0}

@sgemmen

1. We have just finished implementing the Flic Duo support for the Flic Hub SDK. This week we will push both a new firmware as well as update the documentation.
2. There should be a metal plate (magnetic) attached to every Duo, together with a sticker so you can attach it to a wall. Didn't you get this?
3. Haven't tested Copilot. Our ChatGPT integration is extremely simple actually. We have more or less just taken the Hub SDK API documentation and fed that as a context into their template. I guess you should be able to do something similar with Copilot.

@HSDK Do you possibly have an Android phone or tablet device? I would like to know if it can be controlled by the Flic app on that platform if possible (without involving any Flic Hub).

May I ask what kind of sonos device it is, and if it is a rather new or an old one? (model type)

If only the IP address gets listed with the generic name "Sonos", it means that it found the device during a network scan, but communication with it later failed.

I guess you have tried to log out from your Sonos account and log back in again (in case your access token for some reason has become invalid)? Also tried to reboot your flic hub?

Could you please give me the text output that you can see in a browser if you go to http://sonos-ip-address:1400/info ?

I don't understand. You say: "When I setup Sonos provider on the hub, all my speakers are just listed as “Sonos” with different ip’s." but also "( or the hub), there I see the correct speaker names". So do you see the correct name when connected to a Flic hub or not?

@gabriel_g Hi, when you have a Hold & Twist function active, a Swipe action must be performed within 0.5 seconds.

@chachee35 thanks, we will investigate

@rick-0 right... I noticed the same. I'll forward this internally.

@rick-0 Is this on Android on iOS? Can you send a screenshot? Are you connected to a Flic Hub or not?

@edziu-konczewski The reason is indeed due to technical limitations.
Android does not expose any way for third party apps to answer an incoming phone call, at least not using publicly defined APIs. It might be the case that Tasker uses some internal hidden private API in Android, but such use is discouraged by Google and might stop working at any time. In every Android release, Google blocks more and more internal APIs.

That said, if you are happy with Tasker, you can simply use the Flic integration inside Tasker to trigger whatever you want in Tasker by the click of a Flic button.

@perege If you have a Flic hub, you can use our Smartthings integration. If you set up a scene in Smartthings that does what you want, you can trigger that from flic.

@buckyswider You can remove a non-responding Matter device, but in that case the Flic hub pairing will not be removed from the Matter device in question.