AWS IoT library and access to mqtt topics

RE: AWS IoT library and access to mqtt topics

psychogenic — Thu, 16 Apr 2020 16:57:01 GMT

Ok, great. If R&D can implement a cleaner solution than mine, that would be awesome. Access to

param.publish.message.topic

isn't just verbose, it's "dangerous"...

mqtt_evt_param being a union, you have tread carefully when accessing members (e.g. the size of the topic can easily be non-zero if the param is being used as something else) and you windup with trouble.

Short version, some kind of safe accessor for the topics would be nice.

In any case, thanks.

RE: AWS IoT library and access to mqtt topics

Øyvind — Thu, 16 Apr 2020 16:36:09 GMT

No worries! From the information you have provided, it looks like your on a fairly updated master branch from before Easter.

I forwarded your solution to one of our R&D engineers and he confirms the issue. If the workaround works for you, then please use this for now. The engineer informs that your request has been added to the todo list, and a solution will be added in a future release.

Kind regards,
Øyvind

RE: AWS IoT library and access to mqtt topics

psychogenic — Thu, 16 Apr 2020 14:37:27 GMT

P.S. I wasn't being facetious or flippant, there, with "how would I know?": where is this information stored, there's no mention of in any top level documents of ncs/ or ncs/nrf...

RE: AWS IoT library and access to mqtt topics

psychogenic — Thu, 16 Apr 2020 14:21:29 GMT

Hi,

How would I know? I can tell you that the freshest commit shown by a 'git log' in the nrf/ subdir (may be from you!) is date Mar 25 2020:

commit c8fcc56888ab9bb96777fb964e2d2f61c7fc1d0d (HEAD -> master, origin/master)
Author: Øyvind Rønningstad <oyvind.ronningstad@nordicsemi.no>
Date: Wed Mar 25 15:40:26 2020 +0100

RE: AWS IoT library and access to mqtt topics

Øyvind — Thu, 16 Apr 2020 14:18:00 GMT

Hello P,

What NCS version are you running?

Kind regards,

Øyvind