Auto provisioned device MQTT attribute write

[Francnatic]

Hello, I’ve installed OpenRemote and managed to get the Auto Provisioning setup but after I provision a new device I can’t seem to understand how I’m supposed to update attributes from that asset. I’ve tried using MQTTX ( same one I used for provisioning ) to send a write attribute using same certificate I used to enroll but nothing happens, nothing in logs and no data.

Topic: master/TestDevice/writeattributevalue/test/6ZTXcBysubWnSoxcHkzmvkQoS: 0
“hello world”

I think this is a similar post to what issue I’m having:

Auto Prosioning Response with Service User credentials

@Rich I have run into effectively the same problem, but I think I have determined the reason/cause. Either there is either a flaw with the automatic provisioning system, or I am severely missing something! So I’m using an X.509 cert to spec, with a unique CN (Common Name) comprising a UUID, guaranteeing uniqueness. The provisioning handshake works as expected, with each derivative X.509 cert (with a unique UUID) being validated by the master X.509 cert in the “Auto provisioning” screen. Afte…

Anyway somebody could help me out and explain what I’m doing wrong ?

Thank you !

[Berg]

Hi Francnatic,

What the poster in the topic you mention seemed to miss, is that the auto-provisioning mqtt session is the one you also use for pub/sub.

So everytime you want the device to connect you follow the auto-provisioning flow by publishing the certificate to the auto provisioning topic. After that, you can publish to another topic during that session.