# \[APP\]\[Pro\] VDB Systeem monitor **URL:** \ **Category:** Apps\ **Tags:** app, homey-pro, system\ **Created:** [November 14, 2024, 8:50pm UTC](https://community.homey.app/t/app-pro-vdb-systeem-monitor/120553 "2024-11-14T20:50:14Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jeroen\_van\_den\_Booga](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_van_den_booga/32/34198_2.png) [@Jeroen\_van\_den\_Booga](https://community.homey.app/u/Jeroen_van_den_Booga)\ **Post date:** [November 14, 2024, 8:50pm UTC](https://community.homey.app/t/app-pro-vdb-systeem-monitor/120553/1 "2024-11-14T20:50:14Z")
Homey is an incredible system, and as system administrators, we were looking for a way to simplify our monitoring management even further. With advanced flows, you can create impressive automations, so we decided to develop a computer system monitoring solution. This system comprises three main components: 1. **Homey VDB System Monitor** 2. **MQTT Server** 3. **VDB System Monitor App** You can find the Homey app here: [VDB Systeem monitor | Homey](https://homey.app/en-gb/app/nl.vdbcomputers.mqttmonitor/VDB-System-Monitor/) We have developed an `.exe` application for Windows systems and a Python script for Linux systems, compatible with Python 2.7. ### Privacy, Security, and Data Protection No data is logged or stored by this system; it relies entirely on a self-managed MQTT server, giving you complete control over your data. For security reasons, **it is required** to protect the MQTT server with a **username and password**. Do not use a public MQTT server, as the system includes commands to **reboot and shut down computers** remotely. For optimal security, consider using the MQTT server app available in the Homey store to manage your server securely. ### Easy System Overview with Homey Dashboard Widget We’ve also built a widget to display a quick overview of your systems directly on your Homey dashboard. This widget provides the **computer name** , **uptime** , and the **online/offline status** of each device, allowing you to monitor your systems at a glance. ### Installation Details During the installation of the `.exe` file, you will be prompted to enter the following details: - System name - MQTT Broker server - Username and password - Port number In the Homey app, you’ll input the same server details. After installing both the Homey app and the client, and once they are connected to the MQTT server, you can add a new device in Homey. All systems that communicate with the MQTT server will automatically appear. ### Community and Support If you have any suggestions, tips, or bug reports, please leave them on this forum, and I will look into resolving them for you. We have tested this system with over 100 systems. Please note that using this app is at your own risk. ### GitHub and Downloads I will be publishing the app on GitHub later this week. The Windows installation runs as a service, while the Python script needs to be manually installed as a service. You may also need the Python modules `requests` and `psutil`. The services can be downloaded here: - Python Universal Monitor: [https://vdbcomputers.nl/Downloads/Monitoring\_Universal\_Python.zip](https://vdbcomputers.nl/Downloads/Monitoring_Universal_Python.zip) - Windows Monitor Setup: [https://vdbcomputers.nl/Downloads/Setup\_VDB\_Monitor\_Wiz\_new.exe](https://vdbcomputers.nl/Downloads/Setup_VDB_Monitor_Wiz_new.exe) ### Example `config.json` File An example configuration file (`config.json`) is as follows: json Code kopiëren ```auto { "mqtt_broker": "broker.example.com", "mqtt_username": "username", "mqtt_password": "xxxxxxxxxx", "mqtt_port": 1883, "mqtt_topic": "monitor/system_info", "mqtt_notify_topic": "monitor/system_notify", "mqtt_command_topic": "monitor/system_command", "friendly_name": "Systemname", "interval_seconds": 30 } ``` ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [November 15, 2024, 5:59am UTC](https://community.homey.app/t/app-pro-vdb-systeem-monitor/120553/2 "2024-11-15T05:59:30Z")
> [@Jeroen\_van\_den\_Booga](#): > > compatible with Python 2.7. Any reason why you’re still using Python 2 (which has been deprecated for almost 5 years now)? None of my Linux servers come with it anymore. ---
**Author:** ![Jeroen\_van\_den\_Booga](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jeroen_van_den_booga/32/34198_2.png) [@Jeroen\_van\_den\_Booga](https://community.homey.app/u/Jeroen_van_den_Booga)\ **Post date:** [November 15, 2024, 7:12am UTC](https://community.homey.app/t/app-pro-vdb-systeem-monitor/120553/3 "2024-11-15T07:12:23Z")
I am indeed aware that Python 2.7 is an outdated version. I wanted to keep the script as compatible as possible. I was also working on getting the script to run on Synology, Xpnology, and Linux routers. Sometimes older hardware does not receive software updates. Of course, I also prefer Python 3+, but when developing, if I can take older hardware into account and provide support, I do so. For the script itself, I didn’t have to make many adjustments, but I did ensure compatibility. ---
**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\ **Post date:** [January 11, 2025, 11:33pm UTC](https://community.homey.app/t/app-pro-vdb-systeem-monitor/120553/4 "2025-01-11T23:33:40Z")
First of all, why is everything german? And how do i even set this up? ---
**Author:** ![Martin\_Leslie](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_leslie/32/120744_2.png) [@Martin\_Leslie](https://community.homey.app/u/Martin_Leslie)\ **Post date:** [February 6, 2026, 8:54am UTC](https://community.homey.app/t/app-pro-vdb-systeem-monitor/120553/6 "2026-02-06T08:54:05Z")
Hi all. I have installed this app but have run into a problem trying to shutdown a Linux server. I have created a VDB Systeem Device in Homey which receives MQTT information from the Linux server but when I try to ‘Turn On’ or 'Turn Off’ I get an error in Homey saying ‘Missing Capability Listener: onoff’. ![Missing Listener 2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/7/d707191e14898a0421d026abf2ae6c6e371ec939.png) I have done some investigation and I can see the OnOff capability is listed when I view the device in ‘Homey Developer Tools’ and I have sent a manually crafted JSON ‘shutdown’ command to the MQTT Broker which worked. That confirms the Client and Broker are working but it seems the VDB Systeem Device in Homey is not taking any action when the On/Off button is pressed. Has anyone else seen this problem? I have also tried creating a VDB device linked to a Windows server with the same results. Thanks