Skip to main content

I am trying to connect to an MQTT broker with Cognite’s MQTT Extractor.

I know that the broker is fully functional, verified by several tools.

However, when completing the “Add MQTT Topic”.

Error code indicates that the API does not accept “Datapoints” as “Target type”, even though “Target type” is a mandatory field in the interface window. And: “Datapoints” is the only available selection.

Any quick feedback to progress my testing is appreaciated!

 

Hi @Erling Johannessen thanks for testing the MQTT extractor. This is a bug in the UI that we will address as soon as possible (I already created an internal ticket for following up). 
 In case you are using the API directly, it is possible to remove the “target type” and continue the testing. 

Best Regards

Elka


Hello @Erling Johannessen , 

The team has taken a closer look at this behaviour. Can you please confirm where you see this error, and what version of the Extractor you are using?

In the recent versions of the UI, and the API, we were unable to re-create the issue. 

Thank you, 

Kat


Hi @Erling Johannessen, do you need any further help from us?


I am at this web-site when setting up the MQTT Extractor:

https://alma.fusion.cognite.com/alma-dev/extractors/extractor/cognite-pluto-mqtt/create_new_connection?cluster=westeurope-1.cognitedata.com&env=westeurope-1

How can I retrieve the extractor version?

 

rgds

Erling


Hi Erling, 

MQTT Support for the Hosted Extractors service will have a Beta release shortly. As such, the UI may have changed, or been updated to prepare for this release. 

Can you please go through the UI flow, and confirm if you still see this error? If you do, screenshots would be much appreciated, and helpful. At the moment, we are unable to recreate this error. 

Thank you, 

Kat


I have an ongoing dialogue with Pål Rønning. Are you perhaps co-operating with him on this?

An online test session would be appreciated.

I can be reached at erling.johannessen@almacleanpower.com


Thank you for the reply - I will reach out to Pål. Can you please confirm if the original UI issue noted is still seen, or is this mitigated now?


From my understanding this issue has been sorted out directly with you, @Erling Johannessen . I am closing the thread for now. 


Reply