Zebra FX7500 RFID reader: IoT Connector service to send data through HTTP POST not working - tags

In the latest firmware update (3.10.30) of the FX7500 RFID reader a new service has been introduced called IoT Connector. This service enables you to transfer RFID tag data through the HTTP POST method. I've configured the endpoint for the tag data AND management data to a webhook.site URL.
When I enable the IoT Connector service the management data is sent out to the webhook.site URL but not the tag data. I assume that my RFID reader and antenna are not scanning.
Somebody know if i have missed any configurations?

You have to issue a Start REST API to get tag data, and set the Management and Control interface to Local REST to receive REST API calls. Please see documentation available from FX9600 support site - https://zebradevs.github.io/rfid-ziotc-docs/

Related

Request Body of IBM Watson Assistant for webhook

I'm creating a bot using IBM Watson Assistant. I am trying to use a webhook, but don't know the format of the POST request JSON/HTML which is sent to the webhook.
My case study is a shop where user can pre-order. I want to send the order details to my back-end server and give the user a reference number for the pre-order. I found nothing in the documentation about what POST request format is sent from IBM Watson Assistant and in what format response should be returned.
I know IBM Watson Assistant does not require a particular response format. It allows the developer to manipulate the response as the developer wants.
IBM Watson Assistant has a documented API. There are the recommended V2 Assistant API which can be used to create session and then send messages. The older V1 Assistant API has more functions and is deeper into the system. Both APIs can be used to write chatbots.
If you mean a Webhook as the Watson Assistant feature to reach out from a dialog node to an external service, the process is the following:
in the global configuration, you define the URL and the header
for a dialog node, you enable webhooks, then define the key / value pairs that are sent as payload. They can differ by dialog node.
Typically, the expected result is JSON data because it is the easiest to process.
This IBM Cloud Solution tutorial on building a Slack bot with Watson Assistant uses webhooks to call out to a Db2 database. The code is available in a GitHub repo.

Send existing geolocation data from cloud server to Live Objects

I currently have a running instance in Google Cloud which stores geolocation data from an IoT device. I wanted to connect my Google Cloud server to Live Objects so that these geolocation data can be used. Is there a way to connect Google Cloud and Live Objects together, to share data? Or is there a way to send a post request from an external server script (Node.js) to Live Objects without using MQTT? The post request is just a normal HTTP post. The HTTP post will be sent using REST API.
Thanks in advance.
Yes you can push data in Live Objects by using HTTPS REST API
check https://liveobjects.orange-business.com/swagger-ui/index.html#!/Data_management_data_store/addDataMessageUsingPOST
and example here: https://liveobjects.orange-business.com/doc/html/lo_manual.html#STREAMS
cheers

how to get live data from REST API using guzzle

I'm new to whole live data broadcast. I'm creating a website on laravel 5.1, and I need to get live data from a REST API, and after making some changes, broadcast the result to my own users.
I'm using pusher to broadcast data to my clients. and I figured, I should use Guzzle and/or CURL to get data from API. but the part I don't understand is how to get live data from API? Is there an option in guzzle that will keep the connection open continuously,or should I create a job to execute guzzle code every few seconds?
I know we use websockets to create a persistent connection between the server and clients to broadcast live data. but how to create a persistent connection between API server and my server to transfer the data?
Thank you friends in advance, appreciate any help :)
It depends on an API that you are using. If it's an usual REST API, then there are no options to make a "live" catching. Only pull the API periodically.
You API provider might support webhooks, websockets or some other technologies for push model. Depends on a provider, as I said before.

Zebra FX7500. Using HTTP POST to send data from reader to url

I bought a zebra FX 7500 fixed rfid reader. I have connected it to my work laptop. I want to transfer the read data of the tags from the reader to a web application hosted on my localhost. The application is hosted on http://127.0.0.1:8000 using a django server. How can I POST data to a specific URL of my web app with this configuration?
You could:
Upgrade to the latest firmware ([3.10.30.0])1 which is free and use the IoT Connector service to use the HTTP POST method to send the tag data.
Buy a license for the FX7500 service "FX Connect" to use the HTTP POST method to send the tag data.
Both are done in the web GUI of the reader.
The FX7500 SDK is here: https://www.zebra.com/us/en/support-downloads/software/developer-tools/fx7500-series-sdk.html and supports applications in both C & Java. You would need to write an application in one of those two lanaguages to post the received data to your web app.

Kontakt iBeacon: REST API - Updating the Beacon using the secure config

Anyone here have used the Kontakt's REST API, to completely update the beacon the new way (beacon with at least Firmware 4.0) using the secure config? I have followed their API document and have done the steps below, but I am stuck at the last/3rd step. Just checking here while waiting from Kontakt's technical support to help me out.
STEPS:
Update beacon by creating a config e.g. "/config/create?uniqueId=abc&deviceType=beacon&txPower=2"
For the newest beacon (Firmware 4.1), get the secure config from the response of e.g. "/config/encrypt?uniqueId=abc". The secure response is from response's configs[0].config value, and this is what I send in the response parameter in the 3rd step below.
I am not sure if that is the right one to pass as it's not clearly stated in the document.
And lastly to synchronize state, update the cloud by sending the secure config e.g. "/device/update?uniqueId=abc&updated=1489619160440&response=AAMQIgDbyMlY7zruGWl89..."
The API is throwing Error 500 - Internal Server Error with this exact error code API_ERROR_1489800045650.
A beacon's configuration needs to be applied to the beacon by connecting to it using a Bluetooth interface, this cannot be done through a RESTful API service alone.
Changes in configuration for Kontakt.io beacons can be prepared over their RESTful API, but need to be applied through a BLE connection; at which point, the beacon will create a "secure response" that needs to be synced back to their API.
Kontakt.io's SDK already handles this, documentation for "Writing a new configuration to a beacon" covers this in depth, and there is some sample code in their GitHub account:
Fetch configs from API
Apply configs to nearby devices