Same here... I did a quick test by spinning up a Docker container on my machine that logs all incoming requests and configured the Flic Hub to send the requests to that container.

The results are: Flic hub has no problems with sending requests to IP addresses, but requests sent to hostnames or FQDNs won't arrive at their destination (in this case the Docker container).

For me this workaround of using IP addresses is fine, because I will trigger scripts of my Home Assistant in my local network, so I can use the according IP address.

But this should definitely be fixed for domains / hostnames!

@joomeng This is not a static IP. It is just reserving a specific IP using DHCP. This won't resolve underlaying problems that occur when there are communication problems during the DHCP operation

Improvements to Success or Failure when pressing Flic

Hi,

I recently got my FlicHub and overall I really like it! It just bothers me, that I lost the success / failure sounds that have been played by the phone the Flic button was connected to. I don't have "always-on" speakers that I could connect to my hub, and I think this scenario wouldn't even make sense because I want the confirmation at the location of the button and not the hub.

Physical light switches have the feedback of flipping up or down and when there is no immediate reaction to flipping the switch, I know there is something wrong. But when using the Flic that kind of feedback is not enough, since (often) there are network calls involved that take some time or even fail. Because of that I often don’t know if my press was registered/executed and just needs time or if it failed completely.

So my question to all of you is: How could this be improved?

Best regards,
Florian