Tasker.lppsa.com is an internal enterprise portal for LPP SA, designed for management and logistics operations for employees and partners. Access is restricted via an Active Directory Federation Services (ADFS) sign-in page to support the retail group's technology-driven, 41-market operations. For more details, visit LPP SA tasker.lppsa.com. Sign In - LPP SA

How to import a tasker.lppsa-style file

  1. Transfer the file to your device (download, USB, or cloud).
  2. In Tasker, open the menu → Data → Restore or use Import → Project.
  3. Select the exported file and confirm import.
  4. Check and grant required permissions (notification access, accessibility, system settings) after import.
  5. Test each profile and task — imported profiles may need permission or path fixes (e.g., file paths, app package names).

The Future: Is tasker.lppsa Dying or Evolving?

The golden era of LPP-SA was around 2016-2018. Since then, Google has progressively locked down Android (Scoped Storage, restricted accessibility APIs). Many developers have migrated to alternatives like AutoInput (by joaomgcd) or Termux (for shell scripting).

However, tasker.lppsa persists for three reasons:

  1. Lua is lightweight: Compared to Python in Termux, Lua launches instantly.
  2. Offline capability: Unlike cloud-based automation, LPP-SA works entirely offline.
  3. Legacy systems: On older Android versions (8, 9, 10), LPP-SA is still remarkably stable.

If you are on Android 12 or higher, expect some friction. Newer "Protected App" layers may block LPP-SA’s overlay capabilities.

Example: Simple “Arrive Home” export outline

  • Profile: Location or Wi‑Fi connected
  • Tasks:
    • Set phone to Home volume and brightness
    • Turn on Wi‑Fi and connected smart‑home scene via HTTP GET (uses secure placeholder for API key)
    • Send a notification: “Welcome home”
  • Notes: Uses AutoTools/HTTP Auth plugin and requires notification/accessibility permissions.