sophokles73 on master
[#1679] Update device informati… (compare)
sophokles73 on master
[#1679] Pull up a method to che… (compare)
we recently updated our Hono installation from v.0.8 to v.1.0.1. In this process we also wanted to switch from the deprecated AMQP
control topics to the new
command topic for our Command&Control workflow.
We adjusted the application on our device to receive commands on the
command topic but we now don't get any commands from the AMQP adapter. The commands, in our case, get published to the Hono dispatch-router from Ditto via a connectivity-mapping. We adjusted that mapping to publish messages to
command/TENANT_ID/DEVICE_ID as well.
Are there any additional adjustments that we need to make in order to receive on the
command topic? The release-notes for Hono 1.0.M5 state that the topics have just been renamed..
I would appreciate any tips. Thx :).
controltopics still works...
I tried to publish a command to the dispatch router like so but only got SSL errors. Is there a way to see in the log that a command was received by hono? I don't see anything in the dispatch router or the AMQP adapter.
java -jar target/hono-cli-*-exec.jar \ --hono.client.host=hono-dispatch-router.OUR_DOMAIN \ --hono.client.username=user-application@HONO \ --hono.client.password=PASSWORD \ --spring.profiles.active=command,ssl
toproperty of the command message is always tied to the AMQP link address. That means that the
toproperty, as contained in the message reaching the AMQP adapter, doesn't contain the expected address (ending in a device id).
If I enable the ditto connection logs I see the following error in the publish phase ... this then could occur because the message never was delivered!?
Ran into a failure when publishing signal: Failed to send message: Timed out waiting for credit to send Message - Message headers: [message-id=command-and-control, content-type=application/vnd.eclipse.ditto+json, reply-to=control/TENANT/replies, subject=startMeasurement, correlation-id=command-and-control]
address of command message is invalidin our log. The message from ditto should be credited by the dispatch-router right?!