Info message sends blank `DevId` about eve

[eriknordmark]

Looking at the code I see the info (device and app) as well as metrics messages all consistently using the zcdevUUID, which is set first from /config/uuid, and later potentially updated from the UUID in the reply to the GET of /config.

@deitch can you check that you are setting a uuid in the config payload, and what /config/uuid contains when using your controller?

[deitch]

It is possible that the config message was misconfigured. If so, that would do it. I will check it out early next week (traveling now).

[deitch]

Question: assuming this is the problem, should the device in some way validate the config to say, "I don't have a valid UUID" or "the UUID in this GET /config is different from the last one", and some way to tell the Controller that it has that issue?

[deitch]

I checked an actually zedcloud-generated config, it has the same structure, specifically:

{
  "id": {
    "uuid": "abcd-546-abcdf"
  }
}

The auto-generated one is:

{
  "id": {
    "uuid": "bd2c05c0-f7ec-4db3-9a54-acaea973ab43",
    "version": "4"
  }
}

So they do align. Looks like need to dig deeper.

[rvs]

@nordmark already fixed it in the EVE I believe

[eriknordmark]

FIXED by 4722372#diff-83f59c66c1453f094f27390ffa085704