Hi Jason, please advise what is the uuid of the device fails to claim. 

Thanks,
Ayman

Hi Jason, please advise what is the uuid of the device fails to claim. 

Thanks,
Ayman

Hi Stephen,

I see you've opened a support case #00230203 and one of our team members will get back to you regarding this shortly. 

Thanks,
Ayman

Hi Muhammed,

Please make sure you are downloading it from the official link, then ask your system admin to allow it in the firewall/antivirus policy. Nothing much we can do here.

Thanks,
Ayman

Hi Muhammed,

Please make sure you are downloading it from the official link, then ask your system admin to allow it in the firewall/antivirus policy. Nothing much we can do here.

Thanks,
Ayman

Hi Tom,

Would be hard to tell exactly what is going on until we see the exact code and/or settings file. Would you please submit a technical case on the support portal for your code privacy and attach the code there. Here is the portal link: https://siliconlabs.force.com/s/contactsupport

Thanks,
Ayman

Hi Tom,

Would be hard to tell exactly what is going on until we see the exact code and/or settings file. Would you please submit a technical case on the support portal for your code privacy and attach the code there. Here is the portal link: https://siliconlabs.force.com/s/contactsupport

Thanks,
Ayman

Hi Jose,

The original post above does not show the right command syntax. For device's programmed with ZentriOS, you have three options:

1. dms activate <ACTIVATION_CODE>

where this activation code is obtained as you said via Product > Manufacturing > Activation Tokens. Please note here that you do not pass the product code, but only the toekn

2. dms claim <username> <password>

where this is the old fashion method if you are signed up to dms using a username and password (this only works if you have a direct dms account, not via Silicon Labs / Salesforce). Otherwise the next command should be used instead:

3. dms claim <dummy_username> <API user token>

where the token is obtained as you said above: Profile > API Token

Please note that starting from Gecko OS, the dms claim command only accepts one parameter which is the "API user token". The two parameters mentioned in option 3 above only works for earlier ZentriOS release where the command used to have two arguments (that is why the first argument is a dummy entry ignored by dms

Hope that helps.

Thanks,
Ayman

Hi Diem,

I just gave this a quick test and seems like it works as expected. What TCP server you are using (it seems to be locally hosted). Also what other configurations you have set on the module? What is the frequency of failure (you said sometimes, is that 50% or 1%)?

Please provide as much info as you can here that would help us reproduce the issue locally.

Thanks,
Ayman

Hi Diem,

I just gave this a quick test and seems like it works as expected. What TCP server you are using (it seems to be locally hosted). Also what other configurations you have set on the module? What is the frequency of failure (you said sometimes, is that 50% or 1%)?

Please provide as much info as you can here that would help us reproduce the issue locally.

Thanks,
Ayman