This sounds strange. First of all, are you using the Android or iOS app to configure? And just to confirm, you don't get any error messages?

Harmony Hub support will be added to the next firmware update of the Flic Hub. It should be available next week.

A play sound action will be made available in a later update. Our main focus now that the hubs are being shipped out is to gradually increase the functionality. We will have a V1.2.0 release of the Hub coming out shortly that adds more actions, but unfortunately Play sound will not be available in that update. However, It is likely that it will be available in the one after that.

/Anton

It is on our list, but I can not comment on a release date. Right now we are working hard on adding more features to the hub (as well as fixing any bugs that may arise during this initial release phase). We will have a Hub release coming out soon that adds more actions, but the Change Configuration action will not be part of that release.

Hopefully we will get to it soon though.

/Anton

Hello, I am one of the developers of the hub.

First of all I would like to ask what kind of technique you are using to decide if a UDP port is open or closed? UDP is connectionless so by design they don’t really behave like TCP when doing port scans. With TCP you often either get a Connection Reset response or no response at all if you try to connect to a closed port, at which point you can assume that the port is actually closed. With UDP it does not work like that since you are not guaranteed to get a response in either scenario. And even if a port is temporarily open it does not mean that you actually have a service on the other side listening.

I seem to remember that tools like NMAP use ICMP responses to decide if a UDP port is open (correct me if I’m wrong). But this generates a lot of false positives since a lot of ports are not really bound to a permanent service, but rather temporary ports used by both the Linux OS (DNS requests, NTP requests, etc..) and our host application for different features (like action executions etc). This is normal UDP behavior and not an indication of a security flaw.

But again, I don’t fully trust the results of this scan. UDP port 22 (SSH) for example I know for sure is not bound to anything.

If you have any further questions then I will try to answer but you need to be more specific with what kind of tools you use and what kind of amplification attacks you are referring to.

/Anton

@ginissimo We do have battery status in the app, but it only appears once the battery level goes under a certain threshold (30% on iOS). I am not fully sure if the threshold is the same on Android.

• With Passive Mode the Flic button will disconnect the bluetooth LE link 10 seconds after each press in order to save battery power. The downside of this is that the link has to be established again the next time you press the button so the click latency will be worse.

• With Active Mode the Flic button stays connected for as long as possible while the phone is within range and will automatically reconnect once the phone comes into range. The idea of this is that the button should be ready to send the button events immediately when you press it. This may sound wasteful, but in reality this mode will still allow for a long battery life due to the conservative connection parameters we use.

So if you experience poor battery life on your Flic then you can try out Passive Mode. Keep in mind that either of these modes will not affect the Phone’s battery consumption. Also, I should mention that the setting is only applied on the next disconnect of the Flic (the next time you go out of range) since the connection parameters are negotiated during the connection phase.

I know that this information would have been hard to figure out on your own since it is not really documented anywhere.

/Anton

There will be a new version released soon that should fix this.

@manuel.kumar101 I have heard from a few people that they are having issues with bluetooth running macOS Sierra.. I have not been able to troubleshoot it yet, but hopefully I can take a look at it soon.

If you want to do me a huge favor then you could send me one of the HaxWithFlic crash logs. They should be located at '~/Library/Logs/DiagnosticReports/'. My email is my username (at) shortcutlabs .com

@woodhams Yes the lights are working fine for us and they should work in the release that is currently on the App store. We have also verified this from many of our users. It worries me a bit that you say that the WeMo Light Link does not appear when you search in the Flic app. Perhaps there are different versions of the Link that works different ways that I don't know of. If that is the case then I think the only solution would be if we send you a Beta version with added logging so that we can see the network traffic. I'll think about that..

One more comment is that we have just now finished the integration for the WeMo US lightswitches (the ones that are wall mounted inside the sockets). So that will be added to the next release.