@martinm When an incoming FIN packet is received from the remote endpoint, the socket is automatically properly closed unless the allowHalfOpen option is set. If that option is set, the socket is properly closed at the time when both an incoming FIN has been received and the local user has called the end method on the socket (in any order). Nothing is done at garbage collection time, so if you use the allowHalfOpen property, remember to close the socket by calling the end method. If the allowHalfOpen is not set, you can still use the end method to send your own FIN packet.

@idoygr Hi there! Please note we will be sending you a replacement for the Hub. Could you please contact us to laura@shortcutlabs.com with your updated address details? Many thanks!

Which bit should work?
Updating the firmware,
Discovering the devices in Alexa,
or
Adding a Smarthings device?
Or Possibly all 3 ?

What has been changed?
I can't test until I get home in the next couple of hours !!

For more information, please read https://stackoverflow.com/questions/2678551/when-should-space-be-encoded-to-plus-or-20.

In the current firmware version, a + in a query string is translated to %20 before the request is being sent. So, your device will receive the query string 1%20PowerOn, which should be interpreted exactly the same as 1+PowerOn.

In the next firmware version, we will no longer translate + to %20 anymore.

@info-6 Thank you so much for reporting this, we will check this out and update the branch with this change!

@Emil

Thank you very much for the idea.

I tried again using my phone's hotspot, and it worked.

It gave me the idea the home network could be the issue.

I turned off the Eero Advanced Security feature. Now, the Hub can talk to Alexa.

@dgnhans Do you have any other issues except that the name got lost?

@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.

One of my two flic twists was missing the adhesive.

I am using command strips. So far so good. I've one in place for a couple of weeks. I am using the command strip that is similar to velcro.

@Emil The posts are a bit confusing. Am I to take it that you can’t program Twist to control Alexa volume at all? I can’t seem to have it respond to the twist motion. I can use the button to pause and play next track though.
Thank you.

@email any update on this?

@finn probably some bug or something in Homepod then. The mapping between button click type and what lights should be controlled is fully contained within the homepod/Apple TV. The flic hub only delivers the click events.

@Emil Thanks for response! Good to know its still coming. 🙏

@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.

@nascent Thanks for the info!

Wow 14 days go by with out a reply ?

Is anyone out there ??

@oskar Can now use the device Manager with my account, thank you for the support.

UPDATE:
This only seems to work, when my phone is awake and the flic app is on the screen...:-(

@scullracer isolating's answer helped me to do so (with flic 1).
I asked flic to open chrome
using the url like described in the article.

I used it without passing on any input.
Just starting the Shortcut

shortcuts://run-shortcut?name=[name]&input=[input]&text=[text]

I replaced [name] with the name of my shortcut and deleted from the first "&" onward.

That helped me to - finally - start the iphone timer.

Thank you @isolating - thank you so much!