I just tested it on my computer running macOS 11.3.1.
Maybe double check that Flic has the correct Automation permission in the Mac settings?
Go to "System Preferences -> Security & Privacy -> Automation" then check that Keyboard Maestro.app is selected under Flic.app
@anton said in Error code 1 on scan:
@info-6 All flic2lib.buttonscanner error codes are documented here: https://github.com/50ButtonsEach/flic2lib-ios/wiki/Documentation#flicbuttonscannererrorcode
error 1 appears to be "The scan could not be started since bluetooth was not in the powered on state."
Also keep in mind that the state will not be "in the powered on state" if you have forgotten to request for bluetooth permissions in your app, or if the user has rejected the request.
@info-6 All flic2lib.buttonscanner error codes are documented here: https://github.com/50ButtonsEach/flic2lib-ios/wiki/Documentation#flicbuttonscannererrorcode
error 1 appears to be "The scan could not be started since bluetooth was not in the powered on state."
@ddcaruso7 Don't worry about flooding with questions.
First, start by verifying that the Flic Hub is connected to the same network. Go into the settings view of the Flic app while connected to a hub and see what IP you have. The first 3 numbers should match your Mac's IP. You can also try the "TEST INTERNET ACCESS" button. Also, try to execute the action manually from within the app (by pressing the three-dot-icon next to the action). This is to rule out if there are any troubles with the connection between the Flics and the Hub. After doing this, if still not working, check in the terminal window on the mac to see if the program has output any error messages.
Regarding the IP, you are correct that it can change, and it would be an issue in that case. I forgot to mention it, because usually the router will give the same address to the same computer, but it is possible that your router to re-use addresses for other devices.
Anyhow, to solve this, you can set a Static (permanent) IP in your mac settings. You can have a look at this guide: https://www.linksys.com/my/support-article?articleNum=142254 . Only change the IPv4 address field and the first 3 numbers must match the old address. So if you had 192.160.2.10, you can set it manually to, for example, 192.168.2.150. Use a last number in the range of 10-250.
The server program I created does not support https. It could be updated to support it, but that I can't help you with right now.
Hope it helps 
/A
@ddcaruso7 Great! I was a little bit worried that it was too technical, but good to hear that you got it working
The next step (configuring the Hub and the Buttons) should be the easy part:
Delete the buttons from the Mac app (or any other application that you have paired them to) so that they are free to use with the Hub.
Login to the the Flic app for iOS (or Android). You will only need to use the app during configuration.
Make sure that you are within range, say 5-10 meters, of the hub and then press the âAdd Hubâ on the main screen.
Once you are inside the hub in the app, follow the instructions in the app to scan all your buttons. Make sure that you name them something so that you can remember which button is which. It is not guaranteed that they will be ordered in the correct way in the UI. Alternatively you can choose to start with only 2-3 buttons just to try it out and then add the rest later on.
On one of the buttons, add the âInternet Requestâ action to the âClickâ trigger. Input the same URL that you verified earlier. Once you have saved the action you should be able to try it out by pressing the button and see if your Mac reacts with a keypress.
Once verified, use the âClone Configâ feature to copy this action config to all the other buttons (so that you donât have to manually add them). This can be done via the settings menu (gear icon up to the right). Make sure you select all the other buttons as the target.
Once copied to all other buttons, you will now need to manually go into each of the buttons and update the last number in the URL /1 - /18.
That should be it!
Let me know how it goes! If you are happy with it then we can add the program to Autostart so that you don't have to start it from the terminal. Unless you are ok with doing it manually.
/A
@ddcaruso7 Ok, I have written a really simple web server program in Python that translates web requests into local keyboard presses. However, I must mention that you need to keep in mind that this server will be accessible by any device on your same WiFi network. So anyone who knows the URL can also send the same requests to your computer. You need to decide if you trust your own network.
Instructions:
Save As...) If you want to you can also view the code if you are interested in how it works: https://misc-scl-cdn.s3.amazonaws.com/FlicServer.py~/Documents/Flic or similar.cd ~/Documents/Flic to move into the folder where you saved the program.python2.7 FlicServer.pyctrl+chttp://192.168.1.10:4343/api/v1/button/1 (remember to change the IP address correctly). The last number "1" in the URL can be changed between 1-18 for the buttons.Now, before we configure the Flics, we want to see if it actually works. So, open a text editor on your Mac and make sure that the window is selected. This way you will be able to see if the keyboard presses are working as they should. Using another computer/phone on your network, open a web browser and type the URL. If it works, then confirm the URL for all 18 buttons.
Let me know once you have gotten this far and I can help you with setting up the Flic Hub (if you donât figure it out for yourself)
For reference, here is the code:
#!/usr/bin/python2.7
import sys
import time
import threading
from BaseHTTPServer import BaseHTTPRequestHandler, HTTPServer
from Quartz.CoreGraphics import CGEventPost
from Quartz.CoreGraphics import kCGHIDEventTap
from Quartz.CoreGraphics import CGEventCreateKeyboardEvent
# Button 1: '8' -> 28
# Button 2: '9' -> 25
# Button 3: 'b' -> 11
# Button 4: 'n' -> 45
# Button 5: 'm' -> 46
# Button 6: 'j' -> 38
# Button 7: 'k' -> 40
# Button 8: 'l' -> 37
# Button 9: 'z' -> 6
# Button 10: 'x' -> 7
# Button 11: 'c' -> 8
# Button 12: 'e' -> 14
# Button 13: 'r' -> 15
# Button 14: 'v' -> 9
# Button 15: 'q' -> 12
# Button 16: 'w' -> 13
# Button 17: '6' -> 22
# Button 18: '7' -> 26
PORT_NUMBER = 4343
def keyPress(keyCode):
print "Sending Keycode..."
eventDown = CGEventCreateKeyboardEvent(None, keyCode, True);
eventUp = CGEventCreateKeyboardEvent(None, keyCode, False);
CGEventPost(kCGHIDEventTap, eventDown);
CGEventPost(kCGHIDEventTap, eventUp);
class handleRoutes(BaseHTTPRequestHandler):
# GET request handler
def do_GET(self):
if (self.path.startswith('/api/v1/button/')):
keyCode = self.keyCodeForPath(self.path)
if (keyCode != None):
threading.Thread(target=keyPress, args=(keyCode,)).start()
return self.sendResponse('{"status": "success"}', 200, 'application/json')
else:
print "Could not find keycode for this button number."
return self.sendResponse('Not found.', 404, 'text/plain')
else:
return self.sendResponse('Not found.', 404, 'text/plain')
def sendResponse(self, res, status, type):
self.send_response(status)
self.send_header('Content-type', type)
self.end_headers()
self.wfile.write(res)
return
def keyCodeForPath(self, button):
if (button.endswith('/1')):
return 28
elif (button.endswith('/2')):
return 25
elif (button.endswith('/3')):
return 11
elif (button.endswith('/4')):
return 45
elif (button.endswith('/5')):
return 46
elif (button.endswith('/6')):
return 38
elif (button.endswith('/7')):
return 40
elif (button.endswith('/8')):
return 37
elif (button.endswith('/9')):
return 6
elif (button.endswith('/10')):
return 7
elif (button.endswith('/11')):
return 8
elif (button.endswith('/12')):
return 14
elif (button.endswith('/13')):
return 15
elif (button.endswith('/14')):
return 9
elif (button.endswith('/15')):
return 12
elif (button.endswith('/16')):
return 13
elif (button.endswith('/17')):
return 22
elif (button.endswith('/18')):
return 26
else:
return None
try:
server = HTTPServer(('', PORT_NUMBER), handleRoutes)
print 'Started Flic Button server on port ', PORT_NUMBER
server.serve_forever()
except KeyboardInterrupt:
print '\nClosing Flic Button server...'
server.socket.close()
@ddcaruso7 Ok, thank you, now I understand what you are trying to do! I'll try to figure out something that you can try, but I cant promise that it will be perfect.
Regarding "make the hub findable in the Mac app", this will not help you, since the Hub is stand-alone and the app is only used for setup of the hub. Once it is setup the events are not routed via the app.
So my idea is that I create a simple web server program that you can run on your mac. This program can emulate keyboard presses (just like Keyboard Maestro). Then you can setup the Hub via the iOS/Android app and configure it to send the press events to your computer via your local network. (Don't worry, I can make step-by-step instructions).
Can you give me a list of the keystrokes that you want to use? That way I can pre-configure the program for this.
Keep in mind, the requirements would be:
I can't say for sure if the click latency will be good enough for your use case, you will have to try that out for yourself.
/Anton
@ddcaruso7 I need to understand better how you integrate the buttons. Im guessing that Hauptwerk is some sort of VST / Software Instrument that receives midi events from your connected midi controller, correct? Then, on the same machine, you run the Flic app and want to integrate that with the VST. How do you want to achieve this? Does Hauptwerk have some sort of API that you integrate with, or is it all through midi?
You are correct that the Mac app does not see the Hub, but you can still configure the Hub via an iOS device and have it send the click events to the Mac via HTTP requests. The iOS app would then only be needed during initial setup.
Like I said, I'll try to help you out, but I need to understand better.
/Anton
The reason why we cannot give you transparency is because we simply donât know ourselves how long it will take. We are currently working with the MFi Test labs to certify our product. This MFi process is under NDA so we cannot simply share all the details on whatâs going on and where we are at.
What I can say is that we have had some setbacks due to improper implementation on our end, but also due to delays caused by Covid19. Having said that, my hope is that we will have submitted all the materials/documents/samples needed by next week. After that your guess is as good as ours as to how long time it will take. We have never completed a HomeKit (or MFi) certification before, so this process is completely new to us as well.
I know that this is not what you want to hear, but it is the truth.
I also feel the need to say that even though communication with Apple has not always been the quickest, they have been very professional and helpful towards us. So I will not put any blame on them.
Strange. I tested it just now on iOS 13.3.1 and it works.
Calling:
[button disconnect];
Causes:
- (void)button:(FLICButton *)button didDisconnectWithError:(NSError *)error;
And you are sure that the delegates are set properly and that you are not accidentally calling on a nil-object or something?
Can you tell me if you are using the fliclib or flic2lib? Also, does this callback not get sent when you manually call the disconnect method of the framework, or does it not get sent when the button goes out of range?
@poczta I don't have an IR in front of me to confirm, but from my notes this should be the pinout (in order):
However, this will be at your own risk. Let me know if you need further info!
Regards,
Anton
Thank you for posting this! It is really nice for us to hear about good use-cases like this.
I think bt .tn closed down (or similar) about a year ago unfortunately.
To your questions:
I believe that the output from both stderr and stdout is consumed within the Flic app. This is if I recall correctly. If so, no output is available. This could be changed in a future release, but for now it is the case.
To be honest with you, this is largely a business decision rather than a technical requirement. Sure, some features, such as IFTTT, Zapier, Microsoft Flow, need a Flic account in order to work, but in reality the app does not really need a login for most features. What I can say though is that once you are logged in, the app will not rely on our backend in order to work locally (at all). If our backend goes down your app will continue to work fine, unless of course you log out (in which case you would not be able to log back in again). I do understand your concern and if you truly want to have an offline solution with full control, then I recommend that you take a look at our https://github.com/50ButtonsEach/fliclib-linux-hci. Using that you could yourself fully implement Flic into a Raspberry Pi, for example. If you feel really motivated and don't even want to use our SDK, then you can also take a look at the Flic 2 Open Protocol Specification, but maybe that would require a fair bit of work.
This is mostly due to Appleâs App Sandbox . Basically the Flic app can not access any folder on your computer other than exactly /Library/Application Scripts/com.shortcutlabs.FlicMac. The app also does not have write access, only read and execute, which is why you have to manually place the files there.
Anyhow, I think it is cool what you have implemented. However, I will say that if reliability is critical to your use-case, then a purposefully build Raspberry Pi server might be a better way to go. It is more difficult to guarantee uptime on a Mac since it can go to sleep mode, software updates, etc.. I mentioned the fliclib-linux-hci earlier and I donât think it would be very difficult for you to set that up, judging by the code you have already written
The Flic app version 4.0.1 for iOS should fix the Security Code issue with IKEA Tradfri gateways. Let me know if you have further issues.
@robert-j-erickson Yes, we know. I am trying to delete this when I see it, but I agree that it is just way too much.
.
Hello again. It turns out that this was in fact an issue introduced with iOS 13. This has now been fixed and will be released new week. Sorry for the inconvenience 
@garethw00 I have some follow-up questions:
Is the behavior the same regardless of the color setting, as in, does it still happen if you choose the option to keep the current color and not alter the color setting?
It is slightly unclear whether you use toggle or on/off. Can you verify that the issue is still the same if you have only "on" or "off" and not "toggle"?
What exactly do you mean when you say "First one or two turn off, then they all come back on"?
Sorry for the inconvenience, but the more information the better.
@garethw00 I will take another look at the implementation of the LIFX LAN toggle feature next week. Although I can't seem to understand why it would occur. The toggle feature sends the same command to each lightbulb once the toggle state has been decided. So it should not be that they end up with different states.
The only thing I can think of is if some of the lights for whatever reason don't process these commands properly.
This is noted. Once we are done with all the features promised in the Hub LR campaign we will look into implementing additional features. So we will take a look at it then!
@info-6 Filc 2 support has not been released yet for the Mac app, but it will be available within a couple of weeks.