When I tap on the virtual devices on iOS, nothing happens, there are no options, I can't delete them. I can add more however.

I have tried tap and hold, I have swiped in all directions, quick taps. Not sure how to remove any of these and they seem to persist even after deleting the app and reinstalling. I'm sure they're stored on the hub itself. Would resetting the hub clear them? is there a way through the app to remove Virtual Devices I've previously added?

Since it seems like whatever issue is occurring might be device-specific, I'll move this to a support ticket to reduce spam for others following this thread.

edit: Factory-resetting the Hub seems to have fixed it? I had some trouble getting the factory-default password to apply when connecting from a new phone - a couple of resets were needed, but deleting the hub from DM after resetting and immediately triggering a firmware update seems to have gotten my Hub onto 4.4.6.

However, as I was mentioning earlier, I don't recall using Device Manager before this evening: My DM2 account was set up this evening, these are consumer (not corporate) devices, and I don't have anything in my email suggesting I had interacted with an earlier version of Device Manager in the past.

It seems odd that the Hub was stuck on firmware version 4.2.14 even before registering with Device Manager.

That said, I now see that the Twist features have yet not reached the firmware used for Device Manager hubs. I will escalate this issue and try to get it resolved ASAP. In the meantime I suggest that you deactivate Device Manager for this hub if you want to try out the feature.

Triggering a firmware update via the app while the Hub is in this state yields the same behavior ("Firmware already latest version")

Deleting and re-adding the Settings component (with the same config) has the same effect. I'd manually set it to 4.4.2, but the latest available in Device Manager is 4.3.9:

Let me re-register the device (interacting with the Hub via Device Manager caused my Twist to unpair, it seemed) and see if I can get it to a newer version.

When I hit the "Install Firmware" button, the app switches to a "Downloading" screen. Packet captures from the network my Flic Hub is on show it's opening an HTTPS connection to api.flic.io when this happens. A very small (<2 KiB encrypted) amount of data is exchanged, then the devices gracefully close the connection. The app then shows "Done" with "Firmware already latest version".

Is there a way to manually update firmware? The Hub's serial number is HBACG46-44223 if you'd like to check logs.

I have version 3.13.1 of the Flic Android app, with Hub LR firmware version 4.2.14. When I open my Hub in the Flic app, then pick "Providers" from the ellipsis menu in the upper right, I don't see any Flic Hub Studio provider listed.

Github: https://github.com/loosrob/Flic-Studio-Yamaha-control

It's working well for me.

Thank you!

I am debating on if it is even worth asking if there is an expected ETA on the Android release..

My hub itself is showing v4.4.0. I don't see anything 'Studio' related showing up in providers, or in any settings.

const buttonManager = require("buttons");
const flicapp = require('flicapp');
const net = require("net");
const http = require("http");
const client = 'INSERT IP ADRESS HERE'
const port = 4710;

let client = new net.Socket();
var muteCommand = Buffer.from('set /devices/0/outputs/20/Mute/value/true \0', 'utf-8');
var volumeCommand = Buffer.from('set /devices/0/outputs/20/CRMonitorLevelTapered/value/ ');

flicapp.on("actionMessage", function(message) {
		if(message == 'mute') {
			sendToSocket(muteCommand);
		} 
		// handle more (else) cases here 
});

function sendToSocket(msg) {
		client.connect(port, client, function() => {
                client.write(msg);
		})
};

flicapp.on("virtualDeviceUpdate", function(metaData, values) {
	let virtualID = metaData.virtualDeviceId;
        if(values.volume && values.volume != "") {
	     sendToSocket(volumeCommand + values.volume + ' \0');
        }
	// console.log(metaData.virtualDeviceId);
	// console.log(values.volume);
});

Although…

Can you PLEASE update the existing Spotify Connect "provider"/service to also include the volume (up, down, mute) endpoints as well as the existing ones?

It would require next to no time and effort for you to configure, but it would probably make a world of difference for a lot of the "average" end users of your products.

Think about it…the access token/authentication mechanisms are already there, the Spotify volume endpoints have been up and ready to serve since long before the dinosaurs, and it wouldn't require anything out of the ordinary to add it to your already working Spotify service provider.

Don't get me wrong. The Hub SDK is really great now with the latest updates. I enjoy and love that level of flexibility and all the customization goodies, but it's clearly not for everyone - as the learning curve can be somewhat steep and in my opinion it's a total overkill if you have no prior programming skills or interest, but still want to make use of your Flic hub, Twist, Flic 2 button, Duo or whatever. Yay or nay? Oh and btw, great work. I don't just say that

(And please fix the Flic 2 Universal MIDI functionality, as it's useless at this point).

🤍

Andreas