-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON device reference does not mention session.keys.session_key_id #1256
Comments
I have a PR coming that documents this. Will get back here when that's merged. |
More experimentation shows some fields not mentioned on the reference page are ignored so can be left in the JSON, and others are accepted. For example, I left in things like the servers and created time at the top level and they were ignored which is fine. I also left the |
I think the page should also mention that |
Further to my comment above, I have found that exporting with I moved 2 devices between apps following the JSON reference and the devices do uplink, but very sporadically. I moved another 2 devices (all the same type) using the method described in this comment and these two devices missed 1 uplink but then carried on with regular uplinks. So following the JSON reference to the letter does not seem to work for all devices. It also means you lose device-specific formatters. |
Please check the API section of our docs for information on fields. |
I have been moving devices between applications by exporting the device JSON via the CLI and then feeding that JSON back to the CLI dev create command. I am trying to keep the device session alive.
I removed all the fields not mentioned on the JSON file reference page and received an error mentioning the
session.keys.session_key_id
field. When I put that field back the device creation worked.I think this field needs to be added to the JSON reference table.
The text was updated successfully, but these errors were encountered: