# Supervisor 1.0 service implementation

This service handle the management of the global logic of the device. This is the heart of the device behaviour, orchestring the other services and taking the main behaviour decision upon the device's state.

There might be different use cases in the implementation, and depending on the application that may need this service to be implemented in a scripting language. This could be very relevant on setting up a new device, to be able to easily ajust the behaviour, responses to speed up the tests, use cases.

Initially several strategies are provided, with some examples, using the python language. (battery behaviour, always connected behaviour, ... ). These can be adjusted to fit the application usage.


## Configuration

Supervisor can also takes some configuration (as it is a service), as illustrated below, the FORCE_POWERED_MODE is given for factory and test use cases on a battery powered project.


| Environment variable | Description                                                  | Additional informations |
| -------------------- | ------------------------------------------------------------ | ----------------------- |
| FORCE_POWERED_MODE   | In development mode, if this variable is positionned to "1", the luckfox will not try to push the attiny in battery mode, letting the user , use the service and plateform forever |                         |



#### Supervisor Status  :

after each supervisor execution, the supervisor can also push some status :

```
{"power_before_process": "778", "power_after_process": "790", "next_wakeup_date": "2025-03-04T06:00:00+00:00"}
```