Passcode for pairing a bluetooth device - qt

I'm developing a Bluetooth app using Qt 5.5. Using QBluetoothLocalDevice, I can see the device which I want to pair for. Need to submit a passcode as part of the pairing process. How to do this?
Paired the same device with my phone and passcode entry showed up immediately.
connect(m_localDevice, &QBluetoothLocalDevice::error, this, &BluetoothModel::handleLocalDeviceError);
connect(m_localDevice, &QBluetoothLocalDevice::pairingDisplayConfirmation, this, &BluetoothModel::handlePairingDisplayConfirmation);
This isn't showing any debug message from BluetoothModel::handlePairingDisplayConfirmation slot. The debug / error messages are
qt.bluetooth.bluez: Failed to create pairing "org.freedesktop.DBus.Error.NoReply"
BluetoothModel::setPairingStatusMessage "Pairing request failed."
Anyone tried doing this? Thanks in advance.

Related

How to check if the biometric scanner is available and initialized in Xamarin android BiometricPrompt

Failed biometric(fingerprint) scan attempts are handled by OnAuthenticationFailed() callback of BiometricPrompt.AuthenticationCallback class.
The behavior I noticed is, it lets the user attempt 5 invalid fingerprint scans (each time the fail callback is invoked) and then the prompt dismisses. Within the next 30 secs, if we try to re-build a BiometricPrompt instance and try to authenticate, it does not show the prompt which I think is the default behavior of BiometricPrompt.
Is there anyway to check if the biometric scanner is available and initialised if the user attempts to re-invoke biometric prompt within the said 30secs?
How can I handle that use case?
xamarin android BiometricPrompt.AuthenticationCallback does not have an override method "onAuthenticationError" to handle error callbacks and thus I'm unable to handle error code "BIOMETRIC_ERROR_TIMEOUT".
If someone has a solution for this, please do let me know your resolution.
I believe that BiometricPrompt is not fully ported to Xamarin yet...
I'm still looking for a source that can double check this info for me, but I haven't found it either.

Quectel BG96 MQTT publish error

I'm try to publish my data to ThingsBoard server i use this types of AT commands
AT+QIACT=1
OK
AT+QMTOPEN=1,"demo.thingsboard.io",1883
OK
AT+QMTCONN=1,"demo.thingsboard.io","MY_ACCESS_TOKEN",""
OK
AT+QMTPUB=1,0,0,0,"v1/devices/me/telemetry"
>{"temperature":35.00,"humidity":80.00} // MY_POST_DATA This line hanging my module
All AT commands response is ok But i finally enter MY_POST_DATA the module doesn't provide no response hanging the previous command.. and i check my ThinksBoard data never post telemetry..
Please help any one how can i fix this problem and publish MQTT server.
Step 1: Get hold of the official AT command documentation for the modem (Quectel BG96 I assume?). It should document how the AT+QMTPUB command behaves and what it expects. Everything else is just guessing. The manufacturer should provide this, and if not you should demand to get one.
...
Step 873, when you have exhausted absolutely all possible ways of getting hold of the official AT command documentation for the modem: You can try my guess that the command behaves similar to other commands that read arbitrary length user data, most notably AT+CMGS which sends SMS messages, which expect a Ctrl-Z (ascii value 26) as an end of data indicator.
+QMTPUB: 1,0,0 simply mean that BG96 has successfully published and your broker (thingsboard) have also acknowledged publication of message.
If you can't see data on broker, then please check if the topic you are publishing is correct or not.
It may happen you are publishing to another topic (or to a different PATH).
Ask 'thingsboard' for help regarding proper topic.

System Center Configuration manager Push Notification with read receipents

We need to push Push Pop up notifications for ex: “urgent message to warn users” and also generate a report on the success rate as to how many users in the network received it and read it, how many users did not receive it or did not read it.
Microsoft has suggested to use SCCM Power Schell scripting to send Client notifications with close button to confirm receive.
Is there any other way of accomplishing it through SCCM without any customization?
Have you considered pushing a VBScript to all clients which displays the message? If the user clicks "OK" to say they've read and understood the message then it could exit with a return code of 0, otherwise it could return a 1. It's then trivial to report each computer's success result in SCCM.

How to fix ERROR_NOACCESS = -7 in google pepper plugin API

From NACL SDk examples i am trying to run socket example. Example available at ..\nacl_sdk\pepper_34\examples\api\socket
While i am trying to connect to google.com:80 using TCP socket, given error is flashed:
Resolving ...
Resolve failed with status-7
After googling i found ERROR_NOACCESS = -7, Indicates failure due to insufficient privileges.
Does anyone come across this error?
What can be the reason for that, and what is the fix for this?
In order to use TCP/UDP sockets in a NaCl app, you have to create a packaged app in the Chrome Web Store since these permissions require an accept gesture from the user.
https://developer.chrome.com/apps/app_network
"Apps permission socket with subrule tcp-connect is required for Connect(); subrule tcp-listen is required for Listen()." - https://developer.chrome.com/native-client/pepper_dev/cpp/classpp_1_1_t_c_p_socket

Does the Xively API -> Product Management -> Devices -> Update a Device work for anyone?

As you know, Cosm just turned into Xively on Tuesday.
They've added APIs for Products and Devices, and I'm trying to connect to them.
I'm running into problems getting the "Update a Device" API to work. The specific API is documented here:
https://xively.com/dev/docs/api/product_management/devices/update_device/
Anyone else have problems getting this call to return anything other than a 500 error message: '{"title":"Oops, something's broken","errors":"We've been unable to complete your request due to a problem with our server"}' ?
it's probably best mailing support#xively.com with this question I think. I just tried making the serial number update request on one of my devices via the API, and it seemed to work ok; so if you mail them then they'll be able to investigate your specific device.

Resources