Closed samuelbles07 closed 1 year ago
Thanks for reporting this, and also for the resources that made it easy for me to find the problem. There was an error in the MQTT binding that put the wrong ID in the topic etc. when sending notifications.
I released a new version of the master branch 0.11.2 . I hope it solves you problem.
Yes, it works!
Hi,
I found that when POA of AE is using MQTT, CSE notify to the wrong receiver. What i expect is when new
contentInstance
under containercontrol-glass
created, i get notification since i already create subscription resource under the container.AE attributes
Container attributes
Subscription attributes
CSE log debug
And when i see in sendMqttRequest "to" parameter haven't been used and when build request topic, it use originator as mqtt topic receiver path.
Or maybe i am doing something wrong since i am new in oneM2M. Thank you!