Versions Compared

Old Version 1

changes.mady.by.user Sebastian Koch

Saved on

compared with

New Version 2

changes.mady.by.user Alexander Beate (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column
width400px

Introduction

This page covers the first steps after you've installed the azeti Site Controller on your edge device. It will show you how to start and stop the system, connect to the middleware and getting started in the azeti Control Panel. The next steps are the basic ones and will not cover advanced topics like TLS encryption or special configuration tweaks.

Tip

The following instructions assume that you changed into the Site Controller base directory, typically:

Code Block
root@raspberrypi /home/pi # cd /opt/azeti/SiteController/
root@raspberrypi /opt/azeti/SiteController #
Column
width400px
Panel
borderColorlightgrey
bgColor#f0f0f0
titleOn this page:

Table of Contents

Related pages:

  • Filter by label (Content by label)
    showLabelsfalse
    showSpacefalse
    sortcreation
    cqllabel = "getting-started"

Configure Access to the azeti Engine

The Engine is the central point of contact for all Site Controller instances. It provides the control and configuration user interface as well as dashboards and reporting. Each Site Controller has to be configured with the right Engine credentials.

...

Code Block
languageerl
[ExternalBroker]
host = azetibroker02.azeti.net
port = 1883
...
user_id = broker_username@example.com
password = VerySecretPasswordGoesHere
organizationShortName = azeti
tls_enable = False
...

Starting the system

The Site Controller is controlled by the central start script.

  1. Start the Site Controller, it will start the mosquitto automatically if necessary 

    Code Block
    root@ubuntu:~# /opt/azeti/SiteController/run_SiteController.py start
  2. Verify that everything runs fine after you started the Site Controller. Running modules will be highlighted green and labelled as running with. The status command also shows your configured broker username and the destination URL, double check to make sure these are correct.

Code Block
languageruby
root@raspberrypi /opt/azeti/SiteController # ./run_SiteController.py status
Time zone set to: Etc/UTC
Serial of this installation: raspi-test-sebastian
Main version of this installation: 1.2.0
Host type: RasPi
External Broker set to: azetibroker02.azeti.net:1883, TLS disabled
Checking installation ...
OK: Integrity check passed.
OK: Module mosquitto is running with PID (2175)
OK: Module Watchdog.py is running with PID (2355)
OK: Module cloudConnector.py is running with PID (2388)
OK: Module HD2CloudExporter.py is running as sub thread of cloudConnector.py with PID (2388)
OK: Module ConfigProvider.py is running with PID (2489)
OK: Module RawResultsDeMux.py is running with PID (2595)
OK: Module CalibResultsEvaluator.py is running with PID (2609)
OK: Module JobProcessor.py is running as sub thread of cloudConnector.py with PID (2388)

Access the new Location in azeti Control Panel

Now we can go to the web based azeti Control Panel and access our newly created location.

...

Finally you will now be able to see live data flowing in to the azeti Control Panel.