No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Hi all, I have been working with a Honeywell CT40 to iron out the configuration before we roll it out to our end users and the last thing I am struggling with is having the built-in SmartTE app use the device name for the WSID. I figure the best way to do with would be to write the SOTI %MCDEVICENAME% to the staylink.ini file where the app hosts this file. Is there any way to script this out? This realistically only needs to be done either when the device is configured or renamed
We leverage MobiControl to manage our CK65s and CT60s. We also leverage Staylinked SmartTE and have historically pushed the staylink.ini file located in "%sdcard%/Android/data/com.staylinked.AndroidClient" using a MobiControl package so that it can establish the initial Staylinked sever connection.As of Android 11, MobiControl can no longer push files to the "../Android/data" directory. I had come across this on the Honeywell support site: https://support.honeywellaidc.com/s/article/Android-11-permission-required-for-Workspace-One-Agent-SotiAgentBut this doesn't seem to work for the CT60 or CK65.Staylinked allows you to manage the SmartTE config once connected, but we need to be able to pusht he server address via the staylink.ini file prior to it taking control.Soti is currently working a case on this.I have a ticket into Honeywell.I have a support request with Staylinked.I also have some help coming from a VAR we purchased the equipment through.So now I'm reaching out to the community to see if anyone has had any luck with this at this point?One of the issues is that when the Honeywell firmware package is pushed to upgrade the devices from 10 to 11, it seems like the SmartTE config is also wiped out as the application is updated.Unfortunately, I'm running out of ideas short of a firmware rollback, which isn't something I want to worry about later since 80 of these devices have yet to be deployed. It'd be incredibly helpful to get them on the latest version of Android for the device prior to deployment.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
