@jaredwolff can you clarify the setup for the Golioth - there are conflicting instructions from the post referenced in the Readme.md and the code

I’ve successfully installed and built with the SUPL but am unclear how to install the PSK and PSK_ID

If you’re using the SUPL client that connects to Google there are no credentials. You’re likely referring to the PSK that is used for the Golioth connection.

    jaredwolff correct, I’m trying to devine how one installs the Golioth psk and psk_id using the instructions you suggested though the AT_client

    You should be able to issue at commands using the at shell in the app:

    https://github.com/circuitdojo/nrf9160-feather-examples-and-drivers/tree/v2.4.x/samples/tracker#update-credentials-in-modem-one-time-only

    Build and load the tracker app then you can run the commands. You will need to fill in the appropriate information in the <>. For example, <CHAR COUNT> is the number of characters of this command: AT%CMNG=0,515765868,4,"<DEVICE ID>@<LOCATION>"

    at AT+CFUN=4
    at raw <CHAR COUNT>
    AT%CMNG=0,515765868,4,"<DEVICE ID>@<LOCATION>"
    at raw <CHAR COUNT>
    AT%CMNG=0,515765868,3,"<FORMATTED PSK>"
    at AT+CFUN=1

    Alternatively you can load the at_client sample and run the AT+CFUN=4 and AT%CMNG commands only. It all does the same thing in the end.

    Hope that makes sense

      jaredwolff what I was hoping to clarify is what are the <DEVICE ID> and <LOCATION> items - and where does one retrieve those values?

      also do you literally mean to type in at raw <CHAR COUNT> and why the at prefix before the AT?

      You need to create the credentials on Golioth’s interface or CLI. That’s their naming convention (or was, I haven’t use their service lately)

      Device ID is still there - but location is not … changed … can you elaborate on the at raw <CHAR COUNT> ?

      AT%CMNG=0,515765868,4,"mydevice@home"

      is 37 characters so:

      at raw 37
      AT%CMNG=0,515765868,4,"mydevice@home"

      Would be the full command.

      If you run into issues. Load the at_client sample and issue the commands directly.

      Ah, I missed the Using the built-in shell run the following and thought you were using at_client — my misunderstanding!

      Terms and Conditions | Privacy Policy