Flic Home

    Community

    • Login
    • Search
    • Popular
    • Users

    New Flic Twist features for the Hub SDK

    Flic Hub SDK
    6
    12
    2157
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • rob.loosx
      rob.loosx last edited by

      Nice! It took me some time to get going with it, but I managed to create a script to control my Yamaha receiver volume & playback status using the Flic Twist and the Hub Studio.

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

      1 Reply Last reply Reply Quote 0
      • nick-flic
        nick-flic last edited by

        Really excellent to finally (!) have this released.

        It's working well for me.

        Thank you!

        1 Reply Last reply Reply Quote 0
        • Emil
          Emil FlicTeam @mosthated last edited by

          @mosthated The Android app with this functionality has now been released!

          1 Reply Last reply Reply Quote 0
          • mosthated
            mosthated @Emil last edited by

            @Emil

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

            Emil 1 Reply Last reply Reply Quote 0
            • Referenced by  Emil Emil 
            • Emil
              Emil FlicTeam @mosthated last edited by

              @mosthated Sorry forgot to mention that only the iOS app shows this provider right now. It will come later to Android.

              mosthated 1 Reply Last reply Reply Quote 0
              • mosthated
                mosthated last edited by mosthated

                How do I enable these features? I do not see anything related to virtual devices in the flic app, and it looks like the most recent update available is 3.12.3 from 02/11/2025. I don't see any options or settings, either in the play store, or in the app to enable any sort of beta access.

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

                Emil 1 Reply Last reply Reply Quote 0
                • andreas.lorentsen
                  andreas.lorentsen @Emil last edited by

                  Here's a quick and dirty script I created to test volume control. Might be errors (even dragons) here, use at own risk. Maybe it's useful for someone sometime…I don't know.

                  
                  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);
                  });
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • andreas.lorentsen
                    andreas.lorentsen last edited by andreas.lorentsen

                    Nice. I already got it up and running with a couple of custom volume controls. I use it in my home studio (remote controlling input/output volume on Universal Audio gear, controlling playback and recording when tracking vocals and drums etc), and one for my home surround system as well.

                    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

                    1 Reply Last reply Reply Quote 0
                    • Emil
                      Emil FlicTeam @sgemmen last edited by

                      @sgemmen Thanks! Fixed.

                      1 Reply Last reply Reply Quote 0
                      • sgemmen
                        sgemmen @Emil last edited by sgemmen

                        @Emil Been playing with this a bit and so far it's pretty great! Thank the team for landing this!

                        I noticed one thing..

                        I believe:

                        flicapp.virtualDeviceUpdateValue("Light", "my_ceiling_light", {hue: 0.6, saturation: 0.7, brightness: 0.8});
                        

                        should be virtualDeviceUpdateState:

                        flicapp.virtualDeviceUpdateState("Light", "Virtual_light", {hue: 0.6, saturation: 0.7, brightness: 0.2});
                        

                        That seems to work for me. UpdateValue results in a "TypeError: not a function".

                        Emil 1 Reply Last reply Reply Quote 0
                        • Referenced by  Emil Emil 
                        • sgemmen
                          sgemmen @Emil last edited by

                          @Emil Exciting update! Looking forward to giving it a go. Will report back. Thank you!

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post