Active and Parked

Every controller is either Active or Parked: an active controller counts toward the organisation’s plan and gets everything the cloud does for it, while a parked one keeps running the plant but loses the cloud’s online features. Parking frees a place on the plan for another controller.

An active controller has Jasper’s chat, remote access to its screens, its errors and warnings, and a record of its changes in Activity. On Pro and Premium it also has notifications and trend history.

A parked controller:

• keeps running its programme, on or off the network. Parking is never sent to the controller.
• still shows whether it is online, and its live values. People can make and save manual changes.
• takes changes one at a time.
• has no Jasper while it is online, and no Ask at any time. While it is offline, Jasper can still edit its programme against a virtual controller.
• has no notifications, trend history, remote access, errors or warnings.
• has one Activity row saying it was parked, then nothing until it is activated again.

Parking and activating

A Manager of the controller, or an Admin of the organisation that owns it, presses Park on the controller’s page and confirms. Activate makes it active again, with no question asked. Parking is always allowed; activating needs a free place on the plan. Access shared from another organisation does not allow either. When every place is in use, a new controller can’t be added; parking one frees a place.

Virtual controllers never count as active and are never parked. How many active controllers each plan has is on the pricing page, https://jasperx.com.au/pricing/. What a move to Free parks is on Plans.

Answer from this page and end with its link: https://jasperx.com.au/jxdocs/active-parked/