Leaderboard

I have a Fish Tank with a temperature sensor installed on a Raspberry Pi Zero W that I wanted to monitor with Domotz Pro to receive push and emails alerts when the temperature is too high or too low. This is what I did: The sensor is the DS18B20. I wired it to the Raspberry Pi Zero this way: So I enabled OneWire support to read the sensor data: Add to the end of the file /boot/config.txt this line: dtoverlay=w1-gpio And restart the system: $init 6 To find out if the sensor was correctly recognized go to the folder /sys/bus/w1/devices/ and confirm that a 28-XXXXX folder has been created: $ cd /sys/bus/w1/devices/ $ ls 28-02079245a4ec w1_bus_master1 To read the temperature see the contents of the w1_slave file inside this folder: pi@FishTank:/sys/bus/w1/devices $ cd 28-02079245a4ec pi@FishTank:/sys/bus/w1/devices/28-02079245a4ec $ cat w1_slave bd 01 55 05 7f 7e 81 66 42 : crc=42 YES bd 01 55 05 7f 7e 81 66 42 t=27812 At that moment the water temperature was 27.812 Celsius. I'm using this script in Python (/home/pi/temp_snmp.py) to get the temperatures: #!/usr/bin/env python # -*- coding: utf-8 -*- import os import glob import time os.system('modprobe w1-gpio') os.system('modprobe w1-therm') base_dir = '/sys/bus/w1/devices/' device_folder = glob.glob(base_dir + '28*')[0] device_file = device_folder + '/w1_slave' def read_temp_raw(): f = open(device_file, 'r') lines = f.readlines() f.close() return lines def read_temp(): lines = read_temp_raw() while lines[0].strip()[-3:] != 'YES': time.sleep(0.2) lines = read_temp_raw() equals_pos = lines[1].find('t=') if equals_pos != -1: temp_string = lines[1][equals_pos+2:] temp_c = float(temp_string) / 1000.0 temp_c = round(temp_c, 2) # temp_f = temp_c * 9.0 / 5.0 + 32.0 return temp_c # return temp_f temp = read_temp() print temp There are several other sensors that you can use with the Raspberry Pi, just create a script that print the current temperature. To create the OID make sure that you have installed the snmp packages: $sudo apt-get install snmp snmpd Add to the end of the file /etc/snmp/snmpd.conf: pass .1.3.6.1.2.1.25.1.7.1 /bin/sh /home/pi/temp_snmp.sh -g Create the script file /home/pi/temp_snmp.sh with the following content: #!/bin/bash if [ "$1" = "-g" ] then echo .1.3.6.1.2.1.25.1.7.1 echo integer #set the OID as INTEGER python -u /home/pi/temp_snmp.py #it will print the actual temperature. fi exit 0 Now, stop the snmpd service and run it using your actual user (if something goes wrong check the log file errlog.txt): $sudo service snmpd stop $snmpd -Lf errlog.txt And confirm that everything is working fine: $ snmpget -v2c -c public 127.0.0.1 .1.3.6.1.2.1.25.1.7.1 iso.3.6.1.2.1.25.1.7.1 = INTEGER: 28 As you can see, every time you read the OID .1.3.6.1.2.1.25.1.7.1 it will run the script that will return the temperature value. Now you can setup the Domotz Eyes to read the SNMP sensor and create the Alerts: Following this same example you can create your own SNMP sensors and monitor them using your Domotz Pro agent. This way I can receive alerts whenever the temperature goes down or increases too much: To better understand the syntax used in the snmpd.conf file refer to the man page (man snmpd.conf). Do not hesitate to comment or share your own project in our community. Henrique Salvador Domotz Support

Hello, Here's how to connect to a remote QSC Q-Sys Core via Domotz. These directions and the attached script are based off the Extron from remote thread. I've modified the script to work with the ports Q-Sys uses. Q-Sys Instructions 1. Select the Q-Sys Core from the Domotz WebApp → Device list → Device 2. Go to "Connect" tab 3. Click on "Open a TCP tunnel" 4. Insert the TCP Port. By default you will need to open 3 tunnels for the following ports: 80, 1700 and 6504. 5. Wait to have the tunnel setup 6. Repeat steps 3 and 4 for each port. 7. You will have a host and a port for each TCP Tunnel (see the Extron thread linked at the top for screenshots). 8. Open the .bat file as Administrator (see link below) and enter the requested information on the screen. 9. Add a hard link within Q-Sys Designer following QSC's documentation and use the loopback address you chose (e.g. 127.0.0.100). Note: Make sure the mode is set to HTTP. You should see it turn green. 10. Click OK, then File -> Load from Core & Connect and you should see the Core listed there to connect to. Domotz Q-Sys Connect.bat

Please see attached for a ready compiled version of the RDP wrapper. To install, unzip the file, run install.bat followed by update.bat. You can then run RDPConf to make sure everything is working, all the text should be green. If the included RDPCheck takes you to a Windows login screen, you should be able to use the RDP Wrapper with the Remote Desktop option under Connect in the Domotz mobile apps or web app. Note: You might have to disable Allow Remote Assistance in Windows before the RDP wrapper allows RDP connections. We can't guarantee that this works with all versions of Windows, but it's worth giving it a try if the version you have doesn't support Remote Desktop connectivity. We've tested on Windows Vista, Windows 8 and Windows 10 and have successfully made it work. RDPWrap-v1.6.zip

Hi, I have been meaning to make this post for a while now, but now I'm finally doing it Over the years I have been involved in a lot of betas for both hardware and software and I have to say this is probably the best run beta I have been in. The product was almost a finished product before it even got to the beta stage. However, the best part of this beta has been the staff. You guys have first hand knowledge of the product, are involved with the direction it is going, respond to every post on the forums, and answer every email. So with that said, Lars, Giancarlo, and Silvio give yourselves a pat on the back for a job well done.

I have it enabled on most of my agents. Saves me running my own nmap scan. Has revealed some interesting results... like one particular ISP here leaving 50001 open on their modem/routers.

As mentioned this can be done using a simple bit of programming. If you are running Domotz on a Raspberry Pi, or if you just have some form of Linux-type OS set up and running somewhere, this feature can be added with a cronjob. You would need a couple of things, the agentid for the site the Domotz device is located at, and the deviceid for the device itself you wish to powercycle the port. The network switch you are using will need to support Power-Cycle as opposed to just ON and OFF. curl -X POST your-domotz-api-endpoint/public-api/v1/agent/{agent_id}/device/{device_id}/action/power/cycle \ -H 'X-Api-Key: {your API_KEY}' If your network switch only supports ON and OFF then just create a simple 3 line script: curl -X POST your-domotz-api-endpoint/public-api/v1/agent/{agent_id}/device/{device_id}/action/power/off \ -H 'X-Api-Key: {your API_KEY}' sleep 5 curl -X POST your-domotz-api-endpoint/public-api/v1/agent/{agent_id}/device/{device_id}/action/power/on \ -H 'X-Api-Key: {your API_KEY}' That will reboot your NSP-1 every day for you

Hi all, This is all the steps to connect from remote to your Control4 Director using Domotz Pro: Control4 Instruction Select the Control4 Director Go to "Connect" tab Click on "Create a TCP tunnel" Insert the Control4 Director TCP Port. By default "5021" Wait to have the tunnel setup You get two informations: Host Port Run as administrator the Control4.bat script (see attachment bellow) and enter the HOST and PORT previously provided. Open Control4 Composer and create a connection to the local address 127.0.0.1 (it will be forwarded to the Domotz TCP Tunnel). Let us know if you have any problem. Henrique Salvador Domotz Support support@domotz.com Control4.bat

Fetch the devices Let's continue in implementing the functionalities required to fetch and modify our agents. We have to define a `getAgents`-like function that fetch the device list from a specific agent and render the result into our spreadsheet. In this case, the implementation is a bit more tricky since we need to specify which agent we want to query. I've found this solution: when you request a list of devices, a popup is shown to pass the agent ID. To implement this solution we need, first of all, create a new file called `selectAgentIdPopup.html` and define in it the template of the popup <!DOCTYPE html> <html> <head> <base target="_top"> </head> <body> Agent Id: <input type="number" placeholder="1234" id="agentId"/> <input type="button" value="Close" onclick="google.script.run.getDeviceList(document.getElementById('agentId').value)" /> </body> </html> And then, create the function to fetch the devices. If the agentId is not specified (as it is when you invoke it clicking on the menu item), this function opens the popup, otherwise, if you pass a deviceId (as happens when it is invoked by the popup itself), it fetches the data. Even in this case the login to fetch and render the data is similar to the previous one, except the mapping object between the devices fields and the table values. function getDeviceList(agentId, cell){ if(!agentId){ var html = HtmlService.createHtmlOutputFromFile('selectAgentIdPopup'); SpreadsheetApp.getUi() // Or DocumentApp or SlidesApp or FormApp. .showModalDialog(html, 'Please, specify the agent ID'); return; } var fetchUrl = BASE_URL+'agent/'+agentId+'/device'; var jsondata = domotzFetch(fetchUrl); var object = JSON.parse(jsondata.getContentText()); var keys = { 'id': 'DeviceId', 'display_name': 'Name', 'importance': 'Importance', 'ip_addresses': 'IP Addresses', 'hw_address': 'MAC Address', 'user_data.vendor': 'Make', 'user_data.model': 'Model', 'details.zone': 'Location', 'details.room': 'Room' }; var result = createTableFromJSON(object, keys); /* Prepend agentId */ result.map(function(line, index){ if(index == 0) line.unshift('AgentId'); else line.unshift(agentId); }); if(!cell){ cell = SpreadsheetApp.getActiveSheet().getCurrentCell(); } writeTable(cell.getRow(), cell.getColumn(), result); } Notice, as in the previous case, the function starts to fill the spreadsheet from the cell you are on, so be sure to don't select an agent cell otherwise the data will be overwritten. Edit device field And then the last part! After you edit some device information, you want to update the Domotz Device. To help you in this operation I wrote the following functions: the usual handler (as seen before) and a function that, starting from a deviceId cell, read the values (you can extend them as you prefer) and create the JSON object to sent back to Domotz. function updateDeviceField_(deviceId, agentId, field, newValue){ var url = BASE_URL+['agent/', agentId, '/device/', deviceId, '/', field].join(''); Logger.log(url); UrlFetchApp.fetch(url, { method: 'PUT', payload: JSON.stringify(newValue), headers: { 'X-Api-Key': API_KEY, 'Content-Type': 'application/json' } }); } function updatedevice(){ var deviceIdCell = SpreadsheetApp.getActiveSheet().getCurrentCell(); var agentId = SpreadsheetApp.getActiveSheet().getRange(deviceIdCell.getRow(), deviceIdCell.getColumn()-1).getValue(); var make = SpreadsheetApp.getActiveSheet().getRange(deviceIdCell.getRow(), deviceIdCell.getColumn()+5).getValue(); var model = SpreadsheetApp.getActiveSheet().getRange(deviceIdCell.getRow(), deviceIdCell.getColumn()+6).getValue(); var zone = SpreadsheetApp.getActiveSheet().getRange(deviceIdCell.getRow(), deviceIdCell.getColumn()+7).getValue(); var room = SpreadsheetApp.getActiveSheet().getRange(deviceIdCell.getRow(), deviceIdCell.getColumn()+8).getValue(); // Update every property, one each API call updateDeviceField_(deviceIdCell.getValue(), 11822, 'user_data/vendor', make); updateDeviceField_(deviceIdCell.getValue(), 11822, 'details/zone', zone); updateDeviceField_(deviceIdCell.getValue(), 11822, 'user_data/model', model); updateDeviceField_(deviceIdCell.getValue(), 11822, 'details/room', room); }

I really like the new Domotz desktop app! I'm really hoping this will allow for more robust VPN capabilities and better performance when loading up agents.

Hello, We use Domotz as our main network-monitroing tool for broadcast events. It is a massive tool to improve our workflow during the setup of each new event. But we think, there is a goal-feature missing; It would be a massive help, when the switch-interface would be showed in a map. To see the network topology could help us in many diffrent points. -> faster and detailed view of the entire network -> overview of the trunk ports (they are always at a load of 80% -> easier watch of which part of the setup is ready for show What do other think about this? greetings out of switerland! silas

On one of my sites, I would really love to have the ability to automatically clean my offline device list. A clean device list after X days offline would be very very useful.

We just added a simple application showing how to use the Public API and some clever open source libraries to create an Excel file containing all the devices in every managed Domotz Agent. The code and the instructions to run it can be found here.

hi BlackBridgeSystems We are sorry to read you have problems with our software. Checking on Qnap site it seems that TS-419P II have a marvell cpu and TS-469 an Atom x64, could you try to install again the agent using our last packages and let us now if they fix the problem? https://s3-eu-west-1.amazonaws.com/domotz-temporary/qnap/domotz-qnap-x64-4.3.0-2.4.1-2.3.1-b001-0058.qpkg for TS-469 and https://s3-eu-west-1.amazonaws.com/domotz-temporary/qnap/domotz-qnap-marvell-4.3.0-2.4.1-2.3.1-b001-0058.qpkg for TS-419P II

We are looking into this at the moment, together with the QNAP team

This is a trivial thing to do if you are using a Raspberry Pi. Just install a DynDNS updater. sudo apt-get install ddclient I've got this running on all of mine and it works great, even on a double NAT'ed situation.

The install and running of the Agent on the BeagleBone Black (Rev C using bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img) went without any problems.

Here is some feedback on the v0.9.4-b008 Android App: 1) I like the new dashboard. Brings a bunch of key pieces right to the front. 2) Will the "tiles" be able to be rearranged? 3) For the Devices tile. Would it be possible to move the # of devices so it is inline with the Devices tile label? That way you see you have (in my case) 37 devices total. Then break out the online and offline below that instead of having the total devices and number of online ones. 4) Network tile opens to the Route Analysis but the information it shows as the default is the Speed Test. So it would be better if it opened up the Speed Test. 5) The speed test data only remains on the Network tile until the app is shut down and cleared from memory. Could it retain the last time run maybe with an "as of X days ago"? 6) Something is odd with Alerts. I had 2 custom alerts but one was for an Arduino I no longer need (came up with a better temp/humidity sensor based on a Photon). When I cleared the alert out and saved it it still shows in the alert list as having an alert. The Alerts tile shows me as having 2 custom. But going back into the device alert shows it is blank (nothing there). 7) The Collaboration and Help tiles need to be brought so they are all on the initial screen. Not sure if all the tiles need to be made a bit smaller or what, but I did not even realize there was a Guests number and a Documentation area for them that I could see if I scrolled down. So I guess that leaves a bit of interface training for the user. Either change the layout so all tiles (6 total) show completely on the screen or add a scroll bar when they extend past it. That would allow users (if/when tiles are customizable) to add even more but risks getting a bit sloppy.

Just an update to say that the problem was fixed by an update to the domotz agent with help provided by Giancarlo. Must say that I'm impressed with the quick responses and problem resolution. Thanks!

Following along with that.. we deploy Domotz on Raspberry Pis for all our clients and they usually sit in racks. I connect a DHT11 temp/humidity sensor on it and did some snmp scripts so it can be polled regularly. Cost of the sensor is usually less than $5. If you don't want to build your own Pi, investigate what Giancarlo show above. It can help provide some insight into possible failures in clients systems.

Google Spreadsheet is the tool Excel-like that offered to every Google Account. In this tutorial, I'll show you how to use it to fetch data from a Domotz Agent and how to modify them. Set the environment First of all, we need to open a new Google Spreadsheet. To do that, we can easily go https://spreadsheet.new To fetch data using Domotz Public API, we need to create an API Key. The idea is to store it in the spreadsheet itself so to reference it whenever we need. You can generate a new API Key going to Domotz Portal (http://portal.domotz.com) > Settings (Top Right Corner) > API Keys > Create an API Key. Enter your password and write a name to remember why you created the API Key (i.e. Google Spreadsheet). Copy the API Key and paste it on the Spreadsheet wherever you prefer (in this tutorial I'm going to use the cell `C1`). Do the same for the endpoint, so copy and paste it in another cell (in this tutorial I'm going to use the cell `E1`). Let's code! Now we have to write a script to fetch the data and render it. Are you ready? Let's start to code! Open the Script Editor (Tool > Script Editor) and rename the default file in `utils.gs`. We are going to write there some essential function needed: - A function to customize our menu - A function to fetch the data from Domotz - A function to write the data down into the Spreadsheet file Customize the menu Google Spreadsheet permits to add custom field in the main menu. To do that let's insert the following script into the file: function onOpen(){ // Invoked everytime the Spreadsheet is open var ui = SpreadsheetApp.getUi(); ui.createMenu('Domotz') .addItem('GetAgents', 'getAgents') .addItem('GetDeviceList', 'getDeviceList') .addItem('Update Selected Device', 'updatedevice') .addToUi(); } The result will be Add function to fetch the data Now we need a function that helps us to invoke the Domotz API. I defined the function below that automatically adds the API Key in the request reading it from the spreadsheet. This function can be extended as you want but keep it simple for this tutorial. var API_KEY = SpreadsheetApp.getActiveSheet().getRange('C1').getValue(); function domotzFetch(url){ return UrlFetchApp.fetch(url, { headers: { 'X-Api-Key': API_KEY, 'Accept': 'application/json' } }) } Add function to write the JSON into the file Now we need to find a way to render our JSON into the Spreadsheet table. This can be tricky stuff since JSON has, potentially, a huge amount of nesting levels instead of the table... is just a table. To convert a JSON into a table, I defined a function that has two input parameters: the JSON with the data (it is an array of object in our case) and a map used to convert the JSON (maybe nested) field into a flattened array. The result of the function is an array of arrays containing all our fields defined in the map. function createTableFromJSON(jsonObject, keys){ var result = []; var header = []; for(var key in keys){ header.push(keys[key]); } result.push(header); jsonObject.map(function(agent){ var agentArray = []; for(key in keys){ var prop = key.split('.').reduce(function(o, i){ return o ? o[i] : null }, agent) agentArray.push(prop); } result.push(agentArray); }); return result; } It can be used in this way: var object = JSON.parse(fetchedDataFromDomotz); var keys = { 'id': 'DeviceId', 'display_name': 'Name', 'importance': 'Importance', 'ip_addresses': 'IP Addresses', 'hw_address': 'MAC Address', 'user_data.vendor': 'Make', 'user_data.model': 'Model', 'details.zone': 'Location', 'details.room': 'Room' }; var result = createTableFromJSON(object, keys); Write data into the table These two functions are pretty easy. The `writeTable` gets a cell coordinates and an Array of Array as input (the result of the function above) and start to write down the values into the file. function writeTable(startingRow, startingColumn, values) { values.map(function(value, index) { writeRow(startingRow+index, startingColumn, value); }); } function writeRow(row, startingColumn, values){ const fn = function (v) { return [v]; } SpreadsheetApp.getActiveSheet().getRange(row, startingColumn, 1, values.length).setValues([values.map(fn)]); } Fetch the agents If all the functions above are clear, we can now proceed in writing the function to fetch data from Domotz. Let's start from fetching Agent List. var BASE_URL = SpreadsheetApp.getActiveSheet().getRange('E1').getValue(); function getAgents(){ var fetchUrl = BASE_URL+'agent?page_size=4000'; // API Resource to retrieve the Agent List var jsondata = domotzFetch(fetchUrl); var response = JSON.parse(jsondata.getContentText()); var keys = { 'display_name': 'Name', 'creation_time': 'Creation Time', 'id': 'Id', 'access_right.api_enabled': 'Can use API', // The Agent specific API can be used only by the premium agents 'status.value': 'Status' }; var result = createTableFromJSON(response, keys); var cell = SpreadsheetApp.getActiveSheet().getCurrentCell(); // Get the selected cell writeTable(cell.getRow(), cell.getColumn(), result); } Run it This is a good point to try to execute your code. Let's go to the main Spreadsheet tab, reload it. Then select the first empty cell, wait until the Domotz label appears in the menu, select GetAgents and voilà! Your agents are automatically fetched from your Domotz Account. (In progress...)

We are in contact with the Product Management at ITGlue. The integration is more on their side (given that it is already possible to use the Domotz Public API to retrieve data and then import into ITGlue), but we will also see if we can do the integration in Domotz (for an initial update of custom data). It is on our priority list of developments. In any case, it would be beneficial, if you have contacts in ITGlue (or through the Community forum) to stimulate this type of discussion. With regard to ConnectWise Manage, this is on our roadmap to start development before the end of the year. On a similar integration, in the next few weeks we should be able to release the integration with Zendesk (soon after we will work on the ConnectWise Manage for the ticket creation and updates.

Thank you for the expeditious reply! Best wishes, Cheers!

Good news is that our team is productizing what has been a PoC for a long time. Few benefits should be visible in 2 weeks (automatic Parent / Child relationship between devices). And within the first half of August we should also be able to show the Topology MAP of a network within Domotz. I apologize for the delay, but in the last few months we have been completely absorbed by other activities to work better with HW manufacturer companies (I hope you notice the recent announcements about Crestron and you will see more soon in the future). Stay tuned on the Release notes. This is something we will add soon.

Few screenshots related to the new functionalities: New WebApp: Re-organized Single Agent Dashboard: New device list with quick access to additional functionalities and settings: Quick access to Search and Filtering functionalities: New toolbar with quick access to back visited pages: New device details with quick access to last events/remote connections: New graphical tools: Direct access to UserGuide (related to the specific page/functionality in use): Traffic usage for Remote Connection in the month: Cisco SX20 Integration: Firmware version and Software Reboot functionality: Conference Data collection: Niveo PoE Switch Support: Interface tab available for Niveo PoE switches:

Any ETA, beyond bandwidth availability? This seems like an obvious feature given electronics and reset procedures. Like Motech, we are having a hard time also making the switch from OVRC to Domotz without this since its the majority of the reason remote management is useful to us.

Can we create macros that the client can more easily understand? "Restart cable boxes" "Restart Den System"

Updated: May 07, 2019 Brand Specific Model Tested/Supported Notes Domotz Features Millson PDU WireFrame PDM on/off/cycle of outlet Eaton PDU/UPS Eaton 5P 1500 RC http based on/off/cycle of outlet TP Link HS100 (HW Version 1.0 - FW 1.2.5) HS110 (HW Version 1.0 - FW 1.2.5 and HW 2.0 - FW 1.5.3) HS103 (HW Version 2.1 FW 1.0.12) HS105 (HW Version 1.0 FW 1.5.4) on/off of outlet cycle of outlet Lindy PDU http based on/off of outlets(s) cycle of outlets MegaTec / Megasys PDU MSNswitch http based on/off of outlets(s) cycle of outlets Luxul PDU PDV-1608 PDV-908 PDV-202 http based on/off of outlets(s) cycle of outlets PS Audio PLAY IPC-9000 snmp based on/off of outlets(s) Minuteman ZDL-2 snmp based on/off of outlets(s) cycle of outlets CyberPower UPS PDU - fully tested on: PDU81001 PDU81002 PDU15SW8FNET All other models based on the same SNMP MIB bases: SysOiD 1.3.6.1.4.1.3808.1.1.3 - First Generation Monitored/Switched PDU SysOiD 1.3.6.1.4.1.3808.1.1.6 -Second Generation Monitored/Switched PDU snmp based on/off of outlets(s) cycle of outlets Synaccess NP-02B NP-05B NP-0201DT http and telnet based on/off of outlets(s) cycle of outlets Raritan PX3-5146R PX2-2190CR snmp based on/off of outlets(s) cycle of outlets JJPlus (similar to Kankun, JJPlus) on/off of outlet(s) APC (American Power Corp) APC Rack PDU, Switched, 1U, 12A/208V, 10A/230V, (8)C13 Rack PDU, Switched, 1U, 16A, 208/230V, (8)C13 Rack PDU, Switched, 2U, 32A, 230V, (16)C13 Rack PDU, Switched, Zero U, 10A, 230V, (16) C13 APC-AP7932-Switched-Surge-Protector UPS Network Management Card (APC UPS NMC2) AP8953 AP9538 AP8930 AP9630 AP9631 UPS BG500 cycle of outlets on/off of outlet(s) Aten P6208AV PE6108G PE8108G http based on/off of outlet(s) cycle of outlets model Baytech snmp based on/off of outlet(s) cycle of outlets Belkin Belkin WeMo Switch on/off of outlet(s) cycle of outlets Bryant Unlimited Bryant eyePower PDU on/off of outlet(s) cycle of outlets Digital-Loggers Digital-Loggers 85-240V Smart Switched 1-U Rack Ethernet Power Controller 5 - Datacenter PDU Pro Switch How to configure on/off of outlet(s) cycle of outlet(s) model(some) Edimax Edimax SP-2101W on/off of outlet(s) Gude Expert Power Control 8210 / 8211 snmp based on/off of outlet(s) cycle of outlet(s) model JJPlus (similar to Amcrest, Kankun) ssh based on/off of outlet(s) Kankun (similar to Amcrest, JJPlus) ssh based on/off of outlet(s) Keene Keene Electronics IPSMW1 http based on/off of outlet(s) cycle of outlet(s) Middle Atlantic PDU RackLink PDU SW820r RLNK-1015V RLNK-1615V RLNK-215 RLNK-SW215-NS RLNK-415 RLNK-915R RLNK-SW815R-SP http based on/off of outlet(s) cycle of outlet(s) model Middle Atlantic UPS UPS - 2200R UPS-2200R-8IP http based on/off of outlet(s) Orvibo/WiWo Orvibo Smart Socket S20 (WiWo) Time2 Wi-Fi Smart Socket WiFi Smart Plug on/off of outlet(s) Pakedge Pakedge tested on P2E model but P8 and P20 should work too PE-08I PE-09N on/off of outlet(s) cycle of outlet(s) Panamax / Bluebolt Panamax SM3 Panamax M4315 Panamax M4320 Panamax MB1500 Panamax M4000-PRO Panamax VT4315-PRO on/off of outlet(s) cycle of outlet(s) model (some) Snap AV/ WattBox Snap AV WattBox IP+ Controllable Outlet http based on/off of outlet(s) cycle of outlet(s) Time2 Wi-Fi Smart Socket on/off of outlet(s) TrippLite TrippLite PDUMV20NET TrippLite PDUMV30NET TrippLite PDUMV20HV snmp based on/off of outlet(s) cycle of outlet(s) model Ubiquiti - Mfi Ubiquiti mFi Controllable Power Outlet http based on/off of outlet(s) WISPP Wifi Smart Plug (and similar ones) on/off of outlet(s) SurgeX SX-AX15E Axess ELITE snmp based on/off of outlet(s) cycle of outlet(s) model Crestron PC-200 PC-300 snmp based on/off of outlet(s) cycle of outlet(s) model Liberty AV PSU-12-N http based on/off of outlet(s) firmware/model TechLogix TL-RKPS-01 http based on/off of outlet(s) firmware/model

Hi Giancarlo Ive just set up a Synology DS218+ and I can't see Domotz in the Package Center. Is there an ETA for the 18 Series? Is there a download available? Domotz and Synology are a great combination! Many thanks. Tim

I'd love to see SNMP v3 support added or at least backward compatibility to v1.

Hi Giancarlo, Good news! I have installed the agent on my DS218+ with no issues at all. Discovery was a breeze and I’ve also got the iPhone app displaying data. So far, so very good. I’ll post back after a few days of running with further feedback. thanks!

Hi Torben, The device mentioned in your post seems to be an x64 architecture. We created a new package that should solve your problem. The package is almost ready to be uploaded on the market and you should be able to install it manually. You can download it from this url https://s3-eu-west-1.amazonaws.com/domotz-temporary/domotz-qnap-x64-4.3.0-2.1.3-preprod.qpkg If you need help in order to install it manually you should follow these steps - Download domotz qpkg packet ffrom the link above - open "app center" on your qnap - Click on "install manually" , select the downloaded package and install it hope this can help you enjoying Domotz Regards Mauro

Hey Arek, On your switch you'll need to configure the port that domotz connects to as a Trunk port type. Then you'll have to Tagged all the vlans on that port that you want Domotz to monitor. Domotz won't monitor other vlans/subnets over a routed network. The reason for this is because it uses arp and other scans that are not all things that would pass over TCP routes.

Well done - worked perfectly on Windows 10 Home And your Raspberry Pi

Any update regarding SNMP on Ubiquiti Unifi / Edge / Airfiber equipment? There is a fair amount of useful information which OID's can provide. Currently I'm using my unifi cloud for some of this info and was able to find out that a switch is overheating (88deg C) but info that would have been a thumbs up if it came from Domotz.

Sorry to hear this. I believe its some settings of your Raspberry PI. In any case please can you zip the content of the folder /var/log/domotz and send over to support@domotz.com (Please quote: as discussed with Silvio in the forum). Thx

Plug a monitor and a keyboard into it. Drop to a terminal window and ifconfig at the command line. It will tell you the MAC address of eth0 there Add that to your allowed table on your router. Plug the Pi into a network. Enjoy.

I tried this once before and it failed at the very end of the installation, but I think the problem before was that the OS installation wasn't very clean (it was a system I'd been testing a lot of different things with). Put a fresh copy of Ubuntu 14.04 (with LXDE) on and installed the raspberry pi package directly and it seems to be working just fine. Alongside it I've also installed the Ubiquiti Unifi Controller (our main reason for using ODroid PCs) to check that the two can run concurrently without issues. Details: ODroid C1+ rev 0.4 16GB C10 Transcend Micro SD Ubuntu 14.04 (available from odroid.com / odroid.in)

First off, not sure where this should go. I think a new category in the community might be useful to discuss the Web App as more people start to use it. Anyways, on to the feedback (in order I stumbled on things, not necessarily logical): 1) The tiles should be oriented vertically like the smartphone app. You folks are doing a good job keeping things consistent so please stick with that ideology. 2) Nice quick response. I changed a device's information in the Web App and saw the changes show on my App within seconds. 3) The device icons still have the round background like the app but it appears to be a much lighter gray on the Web App and fades into the white background. I would prefer if it gets darkened a bit. 4) Got kicked out of the web app (back to login screen) due to a browser refresh. Refreshing the webpage really should not log me out. 5) Web app does not remember which Agent I was using last (unlike the phone app). This is a touch annoying as the first agent I have on my list has been dead for some time so I need to switch agents each time. But that part works fine. 6) Favorites do not seem to work in the Devices listing. I selected a device as a favorite in my phone app but it did not show up starred in my web app. Selecting it in the web app did not show it in the phone app. 7) Switching devices to Important also does not appear to be working properly, same as favorites. 8) Device Types selection icons are HUGE, or at least the white space around them is giant. The window displayed is far too big for the icons within it arranged in 3 columns. 9) On the Device Types selection window the icon backgrounds and the gray dividing lines between icons are both very faint gray (as mentioned in #3 above). They need to be much more visible. 10) The Device page lacks visible boundaries between areas on the page, like with the phone app. This does not even appear to be a case of the borders being too faint (like in #9 above), rather they do not appear to exist. 11) General Note (not specific to Web App). Not sure what constitutes a status change as I noticed my Router is listed as having had it's last status change 2 months ago. I know I have rebooted it since, including within the last week as new software was release for it that I rebooted it for. 12) Device Connect page appears to be missing it's graphic at the top of the page. There is a box like there should be a graphic though... 13) General Note (not specific to Web App). I noticed that the First Seen date/time for a device was listed as EDT... I would not recommend using that timezone or necessarily ANY timezone other than UTC. The reasoning (at least for EDT) is that time zone is also tied to Daylight Savings Time. That has now ended and my area is back on the EST timezone. Therefore EDT is currently invalid... Trust me, I hate daylight savings time stuff also... Which is why all my projects use UTC even if I do have to change it in my head. 14) Web App "Cannot find an available server..." for doing a Speed Test. Yet the Phone App found one almost instantly (which is a TOTALLY different server, in Vermont, than it has ever used before and one that definitely is not "nearer" than the one it used to use in Toronto). 15) The Web App did not retain the Speed Test information completed by the phone app in it's overall tiles section. 16) The titles for the web pages do not seem to get updated when moving back using the "Back" link on the page. For example I just went back to the main tiles page from the Network Health Analysis page and the title remained Network Health Analysis. 17) No titles exist (thus it remains whatever title was previously populated) for the "Important Devices", "Devices", "Collaboration", and "Give Domotz" tiles. 18) I did not see any copyright notice on the webpages anywhere... Might want to look into that. As a further note there is not even any listed in the source for the webpage. 19) Might want to restrict right-clicking on the webpages if you are concerned about people easily getting the source. It is simple enough to get it otherwise but for some users this would stop them, if you wanted to at least. 20) Ending on a good note! Impressed with the Web App so far. Also appreciate that it gets a nice green lock icon from Google Canary, meaning it is fairly secure (uses TLS, not SSL).

Just wanted to report App ver 0.9.7b003 crashes on start "Unfortunately, Domotz has stopped" when starting on: - Samsung Note 3 running CM13 ROM - HTC One S running CM12.1 ROM - Nexus 7 2012 running CM13 ROM - Nexus 7 2013 running CM13 ROM Not sure what am I doing wrong, but I am not having much luck with it. Is it something specific to CyanogenMod ROMs?

I have to agree with the other comments on here. Just had an issue and Giancarlo was right there to help me. Its wasn't a big issue but I wanted to continue to test out the product. I'm using other monitoring systems and while Domotz has some areas for improvement, the staff is very knowledgeable and very responsive. Great job guys.

I agree with ilkevinli. I have been on many betas over the years and this is one of the best for knowledge, company involvement, and responsiveness. Keep up the good work folks!

Feedback for the RasPi Knowledge Base: 1) Step 2 starts with "If you uses..." Probably was meant to be "If you are using..." 2) I recommend separating out the "Headless" install. There are extra steps needed for the browser one, such as "cd Downloads" that are not needed when headless. Another example is in step 3 the user would not need the status information because they should already know the IP (or hostname) that they connected to for the headless install. 3) The status portion has an easier command (as in shorter) "service domotz status" that is listed in the KB but in Step 4 NOT in Step 3 where the status is actually obtained (with the longer command). Feedback for Agent 0.9.6-152: 1) After installing domotz agent the steps listed for starting it are not actually correct. It states "/etc/init.d/domotz start". Running that will get you lots of permission denied errors. It needs to be "sudo /etc/init.d/domotz start" as stated in the User Portal and KB. 2) The status portion has an easier command (as in shorter) "service domotz status" that is listed in the KB but in Step 4 NOT in Step 3 where the status is actually obtained (with the longer command). Same feedback as #3 for the KB. 3) Network Info page, Provider is blank. This leads to 2 things. The first is that the field could be configurable by the user. The second is that I have a public name that ends in rr.com (which is Roadrunner, a Time Warner Cable service in the United States), so that can be added to your records for future identification. The Public IP Address also can be resolved to identify this using https://db-ip.com/all/. 4) The Network Info page has a large gap at the top which makes the page able to be scrolled for some reason. 5) The Network Info page fields are not selectable. Thus I cannot copy and paste them to other pages if desired (which I was trying to do, thus found this). 6) For the Route Analysis Page, it might be nice to note somewhere that the default 8.8.8.8 is a static IP assigned to Google. This way people do not need to wonder who they might be bouncing data off of. 7) On the Route Analysis Page, it lists "Packets Number" when it most likely means "Number of Packets". 8) Something I noticed in a posting from Lars makes me wonder... Does the agent auto-update? If so... how do I disable that? Especially during a Beta I would like to have to actively note which version of the software I am using so I can provide proper feedback. Plus, what if I did not WANT regular updates (I want them, but I want to know) or if I wanted to be notified (in the app) and then approve them for install?

I would like domotz to keep/report some basic internet connection history. Since most homes use a dynamic public IP addresses. i would like to have a history of when it changes and what the new IP address is. Gives me an idea of when my ISP may have made some equipment changes and maybe I should re-run some speed tests. Timestamp of every time my internet connection goes down and when it comes back up. With this data logged you could also create a monthly or quarterly total downtime trend chart to see if your ISP is getting better or worse over time. Thanks

+1 for being able to select more than just one IPv4 /24. While this is common for basic home networks, more folks are adding guest subnets, DMZ subnets, and so on. Thoughts based on experience: 1. Use the IP subnets from the interface(s) as the default range(s). 2. Have a settings box that allows the user to add/change/delete IP subnets to their heart's content. 3. Same logic applies to IPv4 and IPv6. Hope this is useful! Jason

Can domotz be integrated with IFTTT?

I think it was just put into Beta today or yesterday so I understand why you are not sure yet. I will go ahead with upgrade and give my feedback.

The development team is working at a User Portal, which will also include the possibility of interacting with the WebUI. This will be available for beta testing in nearly 1 month from now

I have been using SSH to work with my RasPi and it has worked fine for all steps. Makes it easier to use another full-fledged browser for the final account activation/linkage step.

The Domotz Agent has the following system requirements. If your hardware doesn’t meet or exceed them, the Domotz Agent will most likely not work with your hardware. QNAP QTS 4.3 or later. Minimum 512MB of RAM Any x86/x64 processor Annapurna Alpine Unfortunately QNAP has recently discontinued range of devices, so if your NAS doesn't support QTS 4.3, it won't be able to run Domotz. QNAP offers a product status list here https://www.qnap.com/en/product/eol.php Please contact QNAP support if you don’t know what processor is used in your NAS or what OS it runs. Raspberry Pi Raspberry Pi Model B, Raspberry Pi Model B+, Raspberry Pi 2 model B and Raspberry Pi 3 model B. Note that the Raspberry Pi Model A, Raspberry Pi Model A+ and the Raspberry Pi Zero are not recommended due to hardware limitations. ReadyNAS OS 6.x or later. Minimum 512MB of RAM Any x86/x64 processor The following ARM based processors: Marvell Armada 370 and Annapurna Alpine. Synology DSM 5.x or later. Minimum 512MB of RAM Any x86/x64 processor The following ARM based processors: Marvell Armada 370, 375 and XP. We also anticipate to support the following ARM based processors: Annapurna Alpine, Freescale QorIQ LS1024A/ Mindspeed Comcerto 2000. Note that Marvell Kirkwood processors are not supported, nor are any PowerPC based processors, such as the Freescale PowerQUICC or QorIQ P-series. No models prior to the x10-series are supported. Synology lists the CPU used in their various models on their website, although for older models you might have to contact Synology's support.

Reported as a bug.