# Zone Priority

## Show current zone priority list

 - [GET /zone_priority](https://docs.cognitivesystems.com/assets/specs/api/app_cloud/zone-priority/get_zone_priority.md)

## Replace zone priority list

 - [PATCH /zone_priority](https://docs.cognitivesystems.com/assets/specs/api/app_cloud/zone-priority/patch_zone_priority.md): Accepts a list or array of strings, these do not have to match or be contained in the list of strings produced by GET /default_locations. Patching is not additive, every request will replace the values.

Making this list empty is the feature switch on whether to use the new zone prioritized leaf blower, or whether to default to legacy leaf blower. 

[] tells the network to use legacy leaf blower. 

Non empty, for example: ["Kitchen"] disables legacy leaf blower and enables the zone prioritized leaf blower.

## Batch update leafs and nodes

 - [PATCH /devices](https://docs.cognitivesystems.com/assets/specs/api/app_cloud/zone-priority/patch_devices.md): Receives a list of objects that mutate nodes and/or leafs. 

Network nodes (star or mesh) cannot be targeted using a mac_address but only using the node_id. The auto key is also not supported by nodes so the input validation will throw. Mutations to node require node_id and cannot include auto or mac_address.

We expect leafs in the array to not have node_id, and they must have auto and mac_address.

Both mutations to nodes or leafs must always have location and friendly_name keys.

Order does not matter. The payload can include only leafs or only nodes.