@Emil thanks Emil. Mine is working too after the Sonos v16 update.

@ncd1284 We're doing the best to communicate the features of different hubs. See https://flic.io/flic-hubs which at least I think explains it pretty good.

@jasperruijsink When you connect a cable, you get an automatically assigned link local IP address, starting with 169.254. The DHCP server, typically running on a router, is then going to assign an available IP address to the hub. If it has no available IP address (i.e. it has run out of addresses) or otherwise doesn't give the hub one, the hub will stuck with its link local IP address.

The Hub LR runs https://github.com/NetworkConfiguration/dhcpcd, which is one of the most commonly used DHCP clients and should work with most routers or DHCP servers.

If nothing works, I suggest you to try another router, or factory reset the router and/or the Flic Hub.

@house I had my Ikea hub on a different VLAN then my Flic Hub LR and a firewall rule to drop all inter-VLAN traffic.

All fixed now!! 🎉

@Emil I've sent you the serial number of the hub over a PM

@Emil are there any updates regarding Matter or even better HA integrations?

@pan-orko I haven't checked if Smartthings has changed anything, but when we implemented it Smartthings made the mistake to only distribute one set (the same set) of oauth2 credentials every time you log in. That way, when the auth token expires and the refresh token must be used to get new credentials, only that hub learns the new credentials. The other hubs that had the same original credentials now have old invalid credentials.

Other oauth2 providers give you new unique credentials every time you log in so they don't have this problem.

@kush-shah-kush "home hub" is the term for the "brain device" of Apple Homekit, typically an Apple TV or Homepod. If your app says "cannot connect to home hub", I guess that means your phone or tablet cannot reach the home hub. Maybe your home hub cannot connect to your LAN?

@fjolnir Please try again now.

You can set up multiple hubs if you want. There is nothing that stops you from doing so. You can pair the same button to multiple hubs. The button will simply connect to the first hub that it can reach when pressed.

Exact same problem. The app shows button presses, but no action. Restarting the mini hub fixes the problem for a few days.
I also have a hub LR that does not present this issue.

@balucanb The Hub mini has "mini" in its name for a reason. It has a significantly smaller footprint and a completely different software architecture which unfortunately means the hub sdk, as it is currently implemented, cannot run on the Hub mini. If you want to use our hub sdk, simply use the Hub LR instead.

However, it's not that we have abandoned the idea of having a hub sdk on the Hub mini as well (since it would be very cool), but that would require more or less a total rewrite of it and we have more urgent priorities right now (see https://community.flic.io/topic/18311/flic-twist-not-what-i-was-hoping-for).

I'm a little disappointed too but understand.

I have used external PoE splitters for my Raspberry Pi's. They work well and not expensive.

For example, take a look at this on Amazon... https://www.amazon.com/gp/product/B07CNKX14C/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

I have a few of those and they work well.

David

The Philips Hue hub is discovered using mDNS on the local network.

Some debugging tips:
I guess you tried power cycle also the Philips Hue hub?
Try if the Hue hub can be found using our Android and iOS apps, without being connected to a Flic hub. That should help figure out if the problem is with the network connectivity on the Hue hub or the Flic hub.
You can for example use the app Service Browser https://play.google.com/store/apps/details?id=com.druk.servicebrowser to see if the Hue hub can be discovered on the network (look for _hue._tcp).

@Emil I hate bluetooth. It worked fine from another phone, so I removed the hub from my primary phone and re-added it. Still didn't work, so I cycled BT on the primary phone, connected with no problem. sigh Not sure why I didn't try that before. Thanks for the pointer! (Taking logs reminded me how awful BT is)

@benjamin-0 ok maybe something is broken with the hub mini then. Send a message at https://flic.io/support to our support team and they can help you out. You can include a link to this post.

@Emil How often is the settings UI collectively opened that this traffic could genuinely be a concern? This could be a super lightweight request, even just an http HEAD method to a CDN cached response that includes the version in one of the headers.

But let's say that even this traffic is too much, and you must avoid any network activity on Settings load. As soon as the "Check for New Firmware" button is pressed on the settings page, you could initiate this version check call to get the most recent version number. The next page should tell you either 1) that a new version is available and ready to be installed with an "Install" button (also showing the current version, the new version you will be installing, and a link to the release notes), or 2) that you already have the latest version with a "Back to Settings" button (e.g. "4.2.13 is already the latest version"). If there is a network issue, you could report that here with a "Retry" button.

If you are already checking and automatically updating the firmware every 24 hours, that information should be shown in the interface, too. Maybe an info button next to the "Hub Version" on that settings page that explains this. Ideally you would also show a log of the last N firmware updates, or the timestamp of the most recently installed update and link to its release notes at the very least.

The issue is now fixed, flic pushed a new firmware to the Hub LR. It is now on version 4.2.13.

Thank you Flic 🙂