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

Please read https://developer.android.com/guide/topics/connectivity/bluetooth#Permissions:

The other permission that you must declare is ACCESS_FINE_LOCATION. Your app needs this permission because a Bluetooth scan can be used to gather information about the location of the user. This information may come from the user's own devices, as well as Bluetooth beacons in use at locations such as shops and transit facilities.

Hi, just use this method: https://developer.android.com/reference/android/bluetooth/BluetoothAdapter#isEnabled(). Or use https://developer.android.com/reference/android/bluetooth/BluetoothAdapter#ACTION_STATE_CHANGED to listen to state changes.

Hi @Emil I wanted to follow up. Is there a capability in the API now to control the Flic LED?

Thanks

Any news on this, really do need a way to show HTTP responses.
Ideally, I want to chain the "play sound" on the HUB2 based on HTTP response.

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?

I have figured it out. When I started flicd through /etc/rc.local it was running as root with no environmental variables, and the data of the buttons was stored in the root directory. When I ran the exact same command as user pi, the environmental variables were set, PATH, USER etc. The fix was simple: use full path names for the data base file.
My apologies for wasting your time when the error was mine.

@Emil Our client is sending 4 buttons to a tender and with the issues that are happening on version 8 could we request the following buttons also be placed on version 7 for the mean time. They are
BA48 – A39996
BA48 – A54514
BA48 – A54466
BA48 - A51788
It would be greatly appreciated.

I think Web Bluetooth implementations kind of sucks at this stage because of the following reasons:

No good scan API. No browsers implement the ability to abort a pending connection. No possibility to "store" a device persistently and later re-connect upon next page reload. Some platforms were very bad at either having multiple pending connections or pending connections that were long-outstanding.

Other than that, it should work fine.

Thanks Emil for the quick reply and the clarification.

That makes sense, just wanted to make sure I wasn't missing anything.

now: https://github.com/50ButtonsEach/fliclib-linux-hci I think

Correct me if I'm wrong, but I seem to recall that if an app wish to communicate with another app using the x-callback-url scheme, then that app needs to be in the foreground in order to send the request? If so, then it would unfortunately defeat the purpose of a button.

But please correct me if I'm wrong.

@little_master They have already been released at https://github.com/50ButtonsEach (Android, iOS, Linux currently).

Yes it's possible. If you actually get a status code such as 404 then it was the server that responded with the error code 404. Maybe you have the wrong url?