|
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.
You will need the following mandatory information for the configuration (ask your Engine Administrator or Hoster).
user_id
(MQTT broker username)pass
(MQTT broker password)host
(MQTT destination host, IP of azeti Engine/)organizationShortName
(Short name of the Organization where the broker user was created in)Alter the SiteController.cfg
and set the credentials accordingly.
[ExternalBroker] host = broker.azeti.net port = 1883 ... user_id = username@example.com password = VerySecretPasswordGoesHere organizationShortName = azeti tls_enable = True ... |
The Site Controller is controlled by the central start script.
Start the Site Controller, it will start the mosquitto automatically if necessary
root@ubuntu:~# /opt/azeti/SiteController/run_SiteController.py start |
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) |
This command stops all site controller modules.
root@raspberrypi /opt/azeti/SiteController # ./run_SiteController.py stop |
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.