Skip to main content

Create Custom Services

Sometimes, the pre-defined services won't implement the functionality that you're looking to have in your AutoPi. It is possible to create custom services that run on the device alongside the rest of AutoPi's services. This guide will explore how to do that.

Creating a Custom Service#


Make sure that your device is updated, as that will otherwise prevent you from syncing the modules.

  1. Go to the Services section and click Create.

  2. Fill out the fields, and click save.

  3. The service along with a custom module has now been created.

  4. Now you can navigate to the custom module and change the code. See examples below

  5. Now sync the changes by clicking the sync button or restarting the device which automatically pulls the changes.

  6. When asked if you want to restart the salt-minion process, you should click yes, as the service is not loaded until the process has been restarted. You can also restart the minion process by running the following commands:

    # In web terminal$ minionutil.restart
    # In SSH terminal$ systemctl restart salt-minion

PIP Requirements#

You can add PIP requirements to custom code modules like so:

Adding PIP requirements


You must follow the default python requirements.txt convention to define your PIP requirements.

Pass Settings Into the Service.#

To pass settings into the service, you should set the settings field to a valid JSON object.

Passing settings to custom service

Which can then be accessed inside the service like so:

some_setting = settings.get("some_setting", "default_value")

A Few Examples#

Log Hello World Every 5 Seconds#

Let's try creating a service that simply outputs "Hello World" to the log every 5 seconds.

import loggingimport time
log = logging.getLogger(__name__)
def start(**settings):    try:"Starting SERVICE with settings: {:}".format(settings))
        while True:  'HELLO WORLD, anything new in the last 5 seconds?')            time.sleep(5)
    except Exception:        log.exception("Failed to start SERVICE")
        raise    finally:"Stopping SERVICE")
        # Stop everything, close connections etc.

And if you have info level debugging configured on your device, you should now see it logging 'HELLO WORLD' every 5 seconds.


The log level of the device can be changed from the advanced settings, under System > Logging level

Basic service with support for configuring workers from the cloud interface, and reporting of failures via events.#

import loggingimport time
from common_util import factory_renderingfrom messaging import EventDrivenMessageProcessor
log = logging.getLogger(__name__)
context = {}
edmp = EventDrivenMessageProcessor("custom_service", context=context)
@factory_renderingdef start(**settings):    try:"Starting custom manager")
        context["settings"] = settings
        # Init the message processor        edmp.init(__salt__, __opts__,            hooks=settings.get("hooks", []),            workers=settings.get("workers", []),            reactors=settings.get("reactors", []))
        # Initialize stuff here        except Exception as ex:        log.exception("Failed to start custom manager")
        if settings.get("trigger_events", True):            try:                edmp.trigger_event({                    "reason": str(ex),                }, "system/service/{:}/failed".format(__name__.split(".")[-1]))            except:                log.exception("Unable to trigger service failed event")
        restart_delay = settings.get("restart_delay", 1)        if restart_delay:  "Enforcing restart delay of {:} second(s)...".format(restart_delay))            time.sleep(restart_delay)
    finally:"Stopping custom manager")        # Clean up

Listen to MQTT Topics#

This service will subscribe to all topics and log the messages. Remember to add the following PIP requirements to the module:



import loggingimport paho.mqtt.client as mqtt
log = logging.getLogger(__name__)
connect_results = {    0: "Connection accepted",    1: "The Server does not support the level of the MQTT protocol requested by the Client",    2: "The Client identifier is correct UTF-8 but not allowed by the Server",    3: "The Network Connection has been made but the MQTT service is unavailable",    4: "The data in the user name or password is malformed",    5: "The Client is not authorized to connect",}
def on_message(mqttc, obj, msg): + " " + str(msg.qos) + " " + str(msg.payload))
def on_subscribe(mqttc, obj, mid, granted_qos):"Subscribed: " + str(mid) + " " + str(granted_qos))
def on_log(mqttc, obj, level, string):
def on_connect(mqttc, obj, flags, rc):    result = "{:}: {:}".format(rc, connect_results.get(rc, "Unknown result code"))        if rc == 0:    else:        raise Exception(result)
    try:        mqttc.subscribe("#", qos) # Subscribes to all topics.    except Exception as ex:        log.exception("Exception occurred when setting up registers")
# glocal settingsqos = 0
def start(**settings):    global qos
    usetls = True    tlsVersion = None # will use most recent version    cacerts = None
    port = 8883    host = ""    username = "username"    password = "password"
    debug = False    keepalive = 60
    # Setup    mqttc = mqtt.Client(None, clean_session=True)    if usetls:        mqttc.tls_set(ca_certs=cacerts, certfile=None, keyfile=None, cert_reqs=ssl.CERT_REQUIRED, tls_version=tlsVersion)    mqttc.username_pw_set(username, password)
    mqttc.on_message = on_message    mqttc.on_connect = on_connect    mqttc.on_subscribe = on_subscribe
    if debug:        mqttc.on_log = on_log
    try:"Starting MQTT engine")"Connecting to {:} port: {:}".format(host, port))        mqttc.connect(host, port, keepalive)        mqttc.loop_forever(retry_first_connection=True)
    except Exception:        log.exception("Failed to start MQTT engine")
        raise    finally:"Stopping MQTT engine")        mqttc.disconnect()

Further inspiration on how to write custom services (or engines as they are also called):


If you'd like to discuss this topic with us or other fellow community members, you can do so on our community page dedicated for this guide: Creating Custom Services.

You can also write us an email on We usually respond back in 24 hours on working days.