@Emil Thanks: whatever you have done seems to have worked. My hub updated successfully to 3.0.9 and Alexa integration now seems to be working.

We have rewritten the Chromecast integration from scratch. We'll send out a new firmware update in the upcoming days. This should fix the isuse.

@theo I think you need to add the http:// prefix to the url.

Hi. Please use https://flic.io/support for support questions.

Everything runs from a read-only system, so i doubt malware has gone into it. Probably just some bug in the widely used Linux OS we run on it if anything.

I would be glad if you could share Wireshark logs or something of the packets you are seeing.

It has a built-in Bluetooth Classic radio inside the wifi chip, but for now we are not using it for anything. Maybe in the future.

I think the easiest would be to just set up a http server on your computer and then use the Internet Request action on the Flic hub. Then your http server can then further make osc requests or whatever when a button event is received.

@anton Hello! I just wanted to update you and let you know that so far, everything you have helped me with on this project has worked quite well. I still don't have any clue how to autostart terminal, but so far it has not been hard to just restart it when I need. What I'm wondering about now is this - I've bought six more flic buttons to add (these will complete what I've planned on the virtual organ), and need to add them to the hub. I've got enough keystrokes left to assign to them, but am now wondering if I need to do anything to the python program to allow it to recognize them and send the internet request. Could you advise? I'm adding to this thread instead of starting a new one, in order for you to place it in context. Thanks! Diane

You can use a tablet also.

@yea I find your story very strange for a couple of reasons.

First, the Flic hub uses "locally administered addresses", which is indicated by b1 in the first byte of the MAC address (0x9A = 0b10011010). Such addresses cannot be looked up in an OUI registry. It's not a "fake address". It's just not a "globally administered address". This relates exactly to how "static random addresses" is commonly used nowadays in Bluetooth Low Energy compared to "Public addresses" in order to avoid the hassle with address registration in the production, since nobody believes that a 48-bit randomly generated address could be duplicated on a local network.

Now, if you have a gateway in your house in front of your LAN that connects to the internet, all internet traffic the ISP will see will contain the MAC address of your gateway, not any MAC address on your local network since that will be rewritten by your gateway.

Any DHCP traffic should also exist solely on your local network and should not be seen by an ISP.

The Flic hub runs the firmware from a read only memory, so I've hard to see that an intruder could have added some botnet software on it.

The Flic hub should only send NTP, DNS, DHCP, and mDNS traffic, as well as communicating with our backend over TLS. (And of course perform the actions you assign flic buttons)

I'd be glad to get more logs or info on what this "suspicious traffic" might be.

I think I figured this out. My hub was connected to my WiFi AND my LAN. I unplugged the LAN cable from the hub so that it just runs on WiFi and it found yeh speakers straight away.

@Emil There are 2 total mentions of the hub on that page. One is an tiny numeric annotation that takes you to the fine print of the bottom of the page. The second is a single bullet in a list of other items. In my opinion, it’s not prominent enough if the entire integration relies on it. I understand it is on your customer (me) to read it all in detail.

More set up explanation / troubleshooting would be helpful.

The set of Wemo switches that the hub can not find are the newer small model WSP080. I have several Insight switches and model F7C063 that all come up no issue.

Thanks.

@Emil I think I figured it out. The problem is with the Hub. I'll retry once I fix the issue.

Was thinking of getting a hub but not interested if it does not work. I have the same issue and any other chrome cast function just does not work. I have 2 phones and one works perfectly fine when the other one doesn't so it just seems to be a software issue or it could be not having a certain permission on my phone. But I have allowed everything I can think of and there should be more information on what permissions I need to enable. The fact that this is a problem and nobody has been able to get a fix for months makes me wonder if this will ever get fixed.