Hi Guys,
I’m trying to connect Qubitro MQTT service with Blues Route, but I can’t get the expected outputs. And I always got an error as below.
Note:Double-checked the cred. But no luck.
Regards,
Pradeep S.
Note:Double-checked the cred. But no luck.
Hi Pradeep,
I ran into the same thing at first but finally figured out how to get it working.
On notehub.io, in order to set the MQTT Client ID we need to set the _sn environment variable for the device and to give it the value of the qubitro Device ID:
- go to notehub.io
- in the left nav click ‘devices’
- double click on the row for your device
- click the ‘Environment’ tab
- under Device Environment Variables make a variables _sn (serial-number)
- give it the value from qubitro for
Device ID. See screenshot. - click Save
Unfortunately that step is a bit odd because now your device will often show up as 9fd5de4a-3327-4e4b-8f48-94d98935c968 (or whatever) in Notehub if you choose to view devices by their serial number. We are considering ways of making this easier in the future and allowing a device’s serial-number (_sn) can be different from the MQTT Client ID.
On the Notehub MQTT Route settings (see screenshot):
- Set Username to the Qubitro Device ID
- Set Password to the Qubitro Device Token
- Set Topic to the Qubitro Device ID
- Optionally, choose a specific notefile and transform the data to simplify it if you don’t want everything going to Qubitro. See second screenshot for both the long-form and simplified data in qubitro.
Unfortunately, It looks like you’ll need to go through all these steps for each individual device because of the way qubitro uses a different Client ID and Client token for each device. If you want to do this at scale with many devices you can use our API to create each route and set each environment variables as needed.
Let me know if there’s anything else I can help with.
Hope this helps,
-Carl
Hi @Carl-Henderson,
It’s working and this was a perfect clear-cut answer 
, thanks.
Regards,
Pradeep S.