You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried on contiki platform. If I set name to through AwaStaticClient_SetEndPointName then from contiki logs you get info about registered but calling awa-serverr-list-clients returns empty list. Removing '<', '>' characters make removes problem.
Checked on version 0.2.5
The text was updated successfully, but these errors were encountered:
I'm guessing this might be more related to the IPC call for awa-server-list-clients than to the actual registration - did you test this against the deviceserver?
I suspect this is almost certainly due to using XML over IPC. The initial expectation was that endpoint names would only contain characters that can be specified in a CoAP URL (since it is used as a bootstrap parameter) however I don't think this is enforced. The endpoint name should be encoded/decoded over IPC to avoid reserved XML characters, and also encoded appropriately when used in the bootstrap URL.
@boyvinall I didn't check with DS. No time to dig around this. @DavidAntliff I think you are right, when I tried to do awa-server-list-clients -o it crashes with some errors and NULLs. However I didn't copy those logs.
I believe method AwaStaticClient_SetEndPointName should return some error if invalid name is passed, or it do some silent strip off wrong characters.
Tried on contiki platform. If I set name to through AwaStaticClient_SetEndPointName then from contiki logs you get info about registered but calling awa-serverr-list-clients returns empty list. Removing '<', '>' characters make removes problem.
Checked on version 0.2.5
The text was updated successfully, but these errors were encountered: