Requests based on using hawkBit eventing

[lizziemac]

I'm using hawkBit eventing, and noticed a couple areas for improvement:

• Target events come through with only the entity ID, and not the controller ID, and the API doesn't allow lookups. Could we either:
  • provide the controller ID in all target events
  • or allow for getting the target by the entity ID via API? neither /targets/{id} nor /targets?q=id=={id} work.
• DownloadProgressEvent events don't have any identifying information (from what I can tell). Can we add the action they are related to?
• It would be lovely to have documentation of the events

[strailov]

Hello @lizziemac ! Could you please specify which events do you refer ? Are they dmf events ? DmfTarget & DmfCreateThing ? Or you are getting use of the repository events ?

[lizziemac]

hi @strailov ! I'm referring to the Spring Cloud Bus events suggested here. I'm guessing that traditionally they weren't/aren't intended for external use by other services, but they fit my use case better than DMF and as a result I think it would be great if we started enhancing them for that use case.

[strailov]

Ah ok now I got it. As far as I can see controllerId could be added in target events. Feel free to extend it and open a PR.

[lizziemac]

I will get to it if I can, otherwise others can take it on if they would like. I think even documentation would go a long ways as well in making the eventing a great tool for others.