I got fed up with the way that Apple and the BBC refuse to play nice. I want to stream BBC radio stations through my HomePod. So I set up a flic to auto stream the radio from my mac to the HomePod. The steps are:

1. Open the BBC radio station URL in Music (e.g. itls://as-hls-ww-live.akamaized.net/pool_904/live/ww/bbc_radio_two/bbc_radio_two.isml/bbc_radio_two-audio=320000.m3u8) and add it to a playlist (e.g. "BBC Radio 2")
2. Create a folder within plugins called PlayRadio2.
3. Within that folder create an AppleScript called Radio2.scpt

tell application "Music"
	play playlist "BBC Radio 2"
	set airPlayDevices to (get name of AirPlay devices) --returns a list of names
	set current AirPlay devices to AirPlay device (item 2 of airPlayDevices) --sets device to item 2 of list
	
end tell

4. Also create a config.json file containing

{
	"pluginName": "Radio2",
	"pluginDescription": "Starts Playing Radio 2 and streams to HomePod Mini",
	"protocolVersion": 1,
	"actions":
	[
		{
			"actionName": "PlayRadio2",
			"fileName": "Radio2.scpt"
		}
	]
}

5. Reload plugins and off you go...

@scullracer I’ve not got a flic on me to check this but I think that you want to choose the option for the flic to open a URL and then use the URL shortcuts://run-shortcut?name=Your%20Shortcuts%20Name
The full documentation is at apple https://support.apple.com/en-gb/guide/shortcuts/apd624386f42/ios
Hope it works for you
Matthew

I got fed up with the way that Apple and the BBC refuse to play nice. I want to stream BBC radio stations through my HomePod. So I set up a flic to auto stream the radio from my mac to the HomePod. The steps are:

1. Open the BBC radio station URL in Music (e.g. itls://as-hls-ww-live.akamaized.net/pool_904/live/ww/bbc_radio_two/bbc_radio_two.isml/bbc_radio_two-audio=320000.m3u8) and add it to a playlist (e.g. "BBC Radio 2")
2. Create a folder within plugins called PlayRadio2.
3. Within that folder create an AppleScript called Radio2.scpt

tell application "Music"
	play playlist "BBC Radio 2"
	set airPlayDevices to (get name of AirPlay devices) --returns a list of names
	set current AirPlay devices to AirPlay device (item 2 of airPlayDevices) --sets device to item 2 of list
	
end tell

4. Also create a config.json file containing

{
	"pluginName": "Radio2",
	"pluginDescription": "Starts Playing Radio 2 and streams to HomePod Mini",
	"protocolVersion": 1,
	"actions":
	[
		{
			"actionName": "PlayRadio2",
			"fileName": "Radio2.scpt"
		}
	]
}

5. Reload plugins and off you go...

@mbkjeldsen
It's tricky but this may do what you want. It'll work using flic connected to your iPhone but will have issues if the phone is locked. This is an apple issue.

1. Create a Shortcut to add data to your health app (e.g. Nutrition data add 100ml on today's date) and give it a name e.g. Water100
2. On the flic app for iphone set the action to be Safari (open a website in Safari) and give it the URL of:
   shortcuts://run-shortcut?name=Water100
   The shortcut will run every time the flic is pressed.
   Hope that helps,

@magnus-0 In order to toggle HomeKit devices you need to have a HomeKit hub (Apple TV, iPad or HomePod) and be running iOS 13 on your phone or iPad to set it up. But as long as you do then all you need to to is have the flic button run a HomeKit shortcut (If X is 'on' then do scene A, Otherwise do scene B). I use such shortcuts for my lights and plugs so that a single click toggles between them. Here's a link to a detailed walkthrough link text.
Hope that helps.

@hello_marley
As I've been playing around with these I'm sorry to have to tell you that the limitations that you've identified lie with Apple.

The first is a Homekit limitation. Homekit will only set 'scenes' of a light being on or off. In order to have flic toggle a light you have to assign the flic to start a homekit shortcut that gets the state of the light and then changes it to the opposite light. If you've a homekit hub (iPad, Homepod or AppleTV) then these shortcuts will run on those devices, so you dont' need the phone to be on. It's pretty simple but an annoying HomeKit limitation.

The second limitation, that a flic assigned to Homekit cannot be used for anything else, was Apple's requirement to get HomeKit approval. It's easy to implement what you want but Apple thought "it'd be easier' if the buttons just did one thing, their thing. Totally counterintuitive for a device that's designed to run routines but flic labs just had to comply. I agree that's the one thing I really want as it'd allow flic hub to 'glue together' HomeKit and non-Homekit control.

Sorry to be the bearer of bad news.

@leemorgan Having just set it up the process is as follows:
You need iOS 13.3. or later on your apple device.
Using the flic app, select your HubLR and then select the flic that you want to add to HomeKit.
At the top of the options for that button should be a slider "Add to HomeKit", slide it ON
You get a warning that this will overwrite any exisiting actions for that button, so agree to that.
If this is the first time that you've added a button to HomeKit the app will then take you through process of adding your hub into the HomeKit ecosystem. As long as you Homekit account is the administrator for your setup this is just a matter of clicking 'yes' a few times.
Once this is done the flic app shows the button as being connected to HomeKit. You cannot add additional actions (i.e. Non-homekit ones) to the actions for each button as I can tell, nor can you have some actions being HomeKit and some non-Homekit :-(.
To set actions for the buttons you have to go into the HomeKit app and then select the flic. Don't try and go through automations, it doesn't work that way.
Once you've selected a flic then you can select a scene, shortcut or accessory to control for each type of action (click, double click or hold).
Hope that helps,
MJ

This is now working (at least I can program my flic2 to do this through the app on iPad) along with Mouse and Keyboard commands

Hi there Stefan.
What you're asking should be fairly simple though may require a bit of work to find out the ID's of everything that you are going to trigger.

What you are going to do is make an Internet Request (usually a POST) to your Domoticz . So the URL to select will be:

http://192.168.0.12:8080

Where 192.168.0.12 will be replaced by the IP address of your NAS. You can find this by looking at the 'connected devices' page on your router. 8080 is the port that Domoticz listens to. If you haven't changed this it should stay the same.

The 'Headers' and 'Body' of the Internet Request will then depend up the authentication that you've set up and the device and command that you want to control.This link API should be useful.

For example: to toggle a switch with an id of 99 you would sent the command in json of:

type=command&param=switchlight&idx=99&switchcmd=Toggle

I'm still learning myself but hope this helps

With iOS 12 iPhone and iPad users got the ability to create a whole slew of actions that they can trigger with a word, but all of these actions are also available to flic.
You do this by giving the flic app (on your iPhone or iPad) the instruction of:
New Action/Phone Control/Safari (open a website)
and then giving the URL
shortcuts://run-shortcut?name=Your%20shortcut%20name
if you want to pass a parameter then add &input=[input]
e.g.
shortcuts://run-shortcut?name=Quick%20Action
The first time that this is run the app asks if it’s OK to open Shortcuts but after that it’s just click and go!

Very old post but relevant to others. The way to launch an app is to open the url of the app that you want, with a 'deep link' if that app supports it. So to open Waze you want to select: New Action/Phone Control/Safari (open a website)
with the URL of https://waze.com/ul?
You can find details of how to send a parameter to waze here https://developers.google.com/waze/deeplinks/