SOTI Pulse Logo

Enable Honeywell EZConfig service

Solved
R
Rick

I am trying to configure Honeywell CP45 devices using .xml files on the devices themselves.
Before enrolling the devices into SOTI MobiControl, the ezconfig service on the Honeywell devices would automatically read and apply the settings inside of the .xml files.

Unfortunately it seems as though SOTI disables the ezconfig service.


My question: Would anyone know how to re-enable the ezconfig service? Or perhaps another way to automatically trigger the reading & applying 

Short answer (thanks to @Rafael Schäfer): 
1. Enable the ezconfig app using the following script: "enable_system_app com.honeywell.tools.ezconfig"
2. Add the EZConfig app to the lockdown kiosk

Thank you.

honeywell
2 years ago
SOTI MobiControl
ANSWERS
MD
Matt Dermody Diamond Contributor
2 years ago

I don't think it's SOTI that is disabling EZConfig I believe its the mechanism of Provisioning Mode being disabled automatically on the Honeywell devices after the first provisioning barcodes are scanned. You need to setup your provisioning profile to keep Provisioning Mode enabled if you want it to remain enabled. 

R
Rick
2 years ago

Currently I am installing a package (.pcg) that contains a "DeviceConfig.xml", which sets the Provisioning Mode to "Always On". The package also contains a Post-Install script which manually reads and implements that:
"sendintent -b intent:#Intent;action=com.honeywell.tools.deviceconfig.enabledeviceconfig;S.path=/sdcard/honeywell/persist/DeviceConfig.xml;launchFlags=0x1400020;end

I can confirm that Provisioning Mode stays 'on' after the installation of the package.

Unfortunately I can't use this same method for the other '.xml' files, since one of them can be placed on the device at any time and needs to be read by the device automatically (as it is before enrolling).

RS
Rafael Schäfer
2 years ago

Hi Rick,

if you know the bundleID of the app, you can send the script "enable_system_app bundleID" (without ") to enable it again. For future you have 2 possibilitys:

1. As Matt already said you have to take a look into the provisioning of your devices. If you use Zero-Touch or QR-Enrollment you may need to add to leave all system apps enabled and set it to true. Be aware that you then must blacklist all unwanted apps afterwords via profile. If you enroll using afw#mobicontrol, there's no such possibility and the behavior is the default one.

2. Other way around: So you keep enrollment as it is and put the script (i mentioned first) into a package and provide it to the devices when connecting to Soti only enabling those apps you want to be enabled.

Which one fits best is your decision.

R
Rick
2 years ago

Hello Rafael,

1. I am using the afw#mobicontrol method. If I need a system app I usually use the script you mentioned         (enable_system_app). But when I use it on the "com.honeywell.tools.ezconfig" app it doesn't seem to restore   the functionality of "reboot and the .xml file will be implemented".
 In your opinion, would it also be possible that I have been misinformed by Honeywell and that EZ Config is   nót actually responsible for automatically reading and implementing the .xml file?

2. As I mentioned to Matt above, I am currently using a package to send a script that sets Provisioning Mode   to 'Always On'. I have also manually sent "enable_system_app com.honeywell.tools.ezconfig" to the device,   and rebooted it (before enrolling, rebooting was all that was needed for ezconfig to read + implement the .xml file). 

RS
Rafael Schäfer
2 years ago

I hope honeywell knows how their apps work (i don't have honeywell devices right here anymore to cross check).

Did you check in the device details if the ezconfig app is listed there? If not: Did you try to provide it via package or enterprise app policy if it (re)appears and working then? (I haven't found it anywhere but hopefully you can download it from honeywell directly yourselve.)

R
Rick
2 years ago

Yes, when I look up 'ezconfig' in the settings app I can find it, and it states that it is currently running. It's the same within MobiControl, status is Installed.

From what I can see, the 'enable_system_app' script has done what I wanted.

Yet somehow the .xml file is still being ignored.

RS
Rafael Schäfer
2 years ago

Did you check this: https://support.honeywellaidc.com/s/article/How-to-run-DeviceConfig-with-a-SOTI-MobiControl-script-on-an-Android-device

R
Rick
2 years ago

Yes, I have used the method on that page before to manually read the existing .xml file. Which works fine for an initial state but one of the .xml files can change at any moment. 

And I am sorry but I just found out my use case is different than I previously mentioned...
The user wishes to scan a barcode to change configuration, not transfer a different .xml configuration file to the device. 

Scanning a configuration barcode works fine after enrolling, manually enabling ezconfig and scanning OUTSIDE of the lockdown kiosk.
So my problem has now changed to: why can't I scan a configuration barcode inside of the kiosk, and only outside.
Scanning it outside of the kiosk triggers the ezconfig app, scanning inside of the kiosk seems to do nothing.

But this is a different problem than I mentioned in the title of this discussion so I believe it might be better for me to create a new discussion.

Terribly sorry for the miscommunication on my part.

RS
Rafael Schäfer
2 years ago

Add the ezconfig app to the kiosk (maybe as "hidden" app) and try again.

Solution
R
Rick
2 years ago

I added EZConfig to the kiosk and it (finally) works like a charm! All I need to do now is edit the Template to hide the app.

Thank you for your help!

RS
Rafael Schäfer
2 years ago

No problem, always nice to help ;)

M
MPMOD@SOTI
2 years ago

Hi Rick,

Thank you for posting on SOTI Pulse!

I am glad to see that you were able to find a solution. Also, thanks to our platinum contributor Rafael for providing the solution.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter 

Similar Discussions