Leaderboard

Would be great to see two factor enabled for the Domotz apps and web portal - especially since this gives remote access to my network...

Is it possible to add the history of Important Devices and the ISP downtime into the report? It would be nice if we had the option to enable or disable this information when generating a report. Right now I have to print the screen separately for these. This way we can show the client something more then the number of times the device or ISP lost a connection.

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

Excellent, thanks for the explanation and quick response. Once again, I have to tell you how much I like your platform and service! Nothing else like it, and you have a polished implementation too. Much appreciated.

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.

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

Wondering if OpenMesh is on your radar for integration? Cheers, Matt

Here you go

Giancarlo, I sense a bit of frustration in your response given the explanation marks and the general tone of your response. Probably doesn't give the best impression to new potential customers like myself as he asked a very valid question. I prefer to work with companies that appreciate feedback of all kinds, even frustration. I will venture to say that I think his question/point is more about policy and communication, or at least mine are below. BTW I also noticed the same increase between the time I installed my first agent and then my second which caught me by surprise. I could be wrong but I also recall the increase being similar to what was mentioned. However to set the record straight would you clarify for a single credit what was the price increase percentage then? Were any other pricing changes made aside from single credit, and do you expect any more in the near future? 1) What is your policy for pricing changes, do you have some timeframe you will commit to where we wont expect them to go up? Will you commit to your customers that when and if they increase they will only increase by X%? Thats extremely important to understand for a small business given your expectation to be a core piece of our infrastructure. I typically expect such a commitment from new vendors with little to no established history of pricing control yet. Otherwise the risk/financial exposure can be too much for some. 2) If a price change is expected, do you give customers advance notice so they can plan ahead and work that cost into their services? If so how much advanced notice do you plan to offer? Do you look for feedback from your customers on such changes or are those decisions only made within the internal vacuum of Domotz? Please don't take these questions as criticism, they are merely necessary for planning and level setting a mutually beneficial relationship.

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

Hi there are 2 reports available, the last 30 days and a device report. The last 30 day report only shows 30 day status for the wan connection and then basically shows a device list which is useless as that is available in the other report. I would love to see a report that showed the amount of offline events for all the devices. I realize with a large project that could be lengthy so maybe there could be a "filter by device" option before the report is generated. This would be a phenomenal feature that is an absolute necessity. After all, this would prove to the client the value of the domotz box. Please implement this asap.

Hello, I'm wondering if it is possible to separate the device listing for each network/VLAN. Typically, we have a guest VLAN and it's not so important who/what is on it. But of course being able to see what's happening is still good/important. And if it could be possible to switch alerts off for a specific VLAN/nework would be really nice. Best, Daniel

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

I actually prefer the PerfSonar system to be honest- those of you saying you get repeatable results should consider what you are saying. Is it really your belief that a broadband trunk will have the same response at 6pm as it will at 4am. These are like Highways and there will always be traffic at certain points that will cause congestion and variances. If you are not seeing these it is likely that the test is not a legitimate implementation, and is perhaps skewed as may be the case in both OOkla and speedtest.net who are both receiving large amounts of advertising funds from a few large players. Now I would never insinuate that a company that survives off of advertising funds would ever skew reports about connectivity results from their key clients as that would be inappropriate and completely unheard of in life in general. Just in comparison PerfSonar is an implementation of a truly pure and scientific Link quality and bandpass test that is directed towards and managed by purely scientific organizations that do not operate off any type of advertising blood money. I will say I was amazed at the quality and predictable results of my tests run by OOKla on the Comcast network despite getting significantly contradictory findings in both Speedof.me and personal experience. Lastly Dsl reports does seem to have updated their speedtest and it appears to be a genuine implementation of a tool, however great care was taken to shield the operation from prying eyes so there is little way to know the true nuts and bolts of the operation. It is clear that most the test legs are not hosted by Dsl reports but thats not anything of much concern as who wants to own a data center just to provide a speed test. Besides the key is to vary your test vectors and targets to get clear picture of the issue, which again is a good reason to stick with PerfSonar. Ok so besides counting myself as a backyard scientist and having fun with DryIce I have no connection to PerfSonar I just like their scientific roots. Ok so thats my vote thanks for reading. Last thought, If my doctor told me he saw a dark spot on my chest Xray while I would hope for a smudge if it appeared in 4 successive Xrays at other doctors I would stop blaming the Xray and start chemo --point being the indication is theirs a bad network issue in the Canadian border region, amazingly a tap point for certain state level players, why are we blaming perfsonar again and the customers not complaining to the Broadband providers???

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!

Hey guys, any plans to support RTI control processors and possible their ZW9 zwave controllers?

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

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

Anyone who has questions, concerns or input regarding the visibility of Domotz pricing (boxes and services), please contact me directly: seth@domotz.com. I'm especially interested to learn how a consumer might come to know what Domotz is -- and what they would do with Domotz without the time or expertise to use it. Since 2016 Best Buy has been selling SLA's based 100% on Domotz - they call it Mag-Care. I just got off the phone with Luis, a Domotz user who is getting paid $2,400.00 per month from one of his customers for a box that can be purchased for $99 on Amazon and service he is paying $19.00 per month for -- Premium, as seen on www.domotz.com. I'm more than happy to share every resource I am able to, offer as many examples as I can think of and provide every bit of encouragement I can muster to anyone who is interested in learning how not to sell a drill -- please: seth@domotz.com PS: On the Best Buy home page. At the bottom, I clicked on Support & Services, then scrolled down to the bottom right, under Best Buy Brands > Magnolia® - and at the bottom of that page: Learn About Magnolia… > Magnolia Care (video - 46 seconds) - Domotz screenshots at seconds 30-35

This is just to update on the status of this request. We have added the possibility to select multiple devices from the Device List and then delete all the selected one with the "Pick an Action" functionality: With regard to the request of automatically delete devices which are offline for more than X months, the easiest way to accomplish that is by using the Domotz Public API.

Hello Everyone, We currently have a package that runs on OpenWRT. It looks like the Ubiquiti Edgerouter is the same type and should run the open source package and the Domotz agent. I underlined "should" in the previous sentence because running this package on the Ubiquiti Edgerouter is not yet supported. However, you are free to download the package and test it out for yourselves. Here's the link to the package: https://portal.domotz.com/download/agent_packages/domotz-octeon-1.0.ipk (sha1 checksum: https://portal.domotz.com/download/agent_packages/domotz-octeon-1.0.ipk.sha1) Be sure to respond to this thread with your successful installation notes. Cheers, Steven

Hi @Giancarlo Thank you for making Domotz available on the x18 series! I was so happy to see it appear in the package centre and it's now running on my client's DS-218+ Many thanks Tim

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!

It is definitely possible to use the Domotz "Open a TCP Tunnel" feature to remotely connect to your Apple Airport device. Please find below the instruction: Apple Airport Utility Instruction Select the Airport device from the Domotz Pro App -> Device list Go in "Connect" tab Click on "Create a TCP tunnel" Insert the Airport Processor TCP Port. By default "5009" - please check in your system (might be 5001) Wait to have the tunnel setup You get two informations: Host Port Open Airport Utility program and: Go to File > Configure Other Insert the previously retrieved <Host_Address>:Port and the password

Two-factor authentication is a great addition! I have a security-related question: Is there a document or description of the security policies of Domotz? (Not privacy and user data, but security practices and any independent audits or standards compliance.) What level of access is provided to Domotz via the automated software update and provisioning process? Is the access provided through this mechanism a "Back Door" that bypasses the normal login credentials, including 2-Factor authentication? In the theoretical but possible situation of a disgruntled employee or engineer, how much access do they have to my client's networks? Can they initiate remote connections and remote sessions without my knowledge or control?

I'm trying to determine which is a better fit for my needs. What would be great is to see a side by side comparison of features between the two. Is there a place this exists? I'm still trying to determine whether the fing box has a WebUI, which I don't believe it does, but in general I'd like a comparison of all features to see which will best suit me. Maybe someone out here can help clear that up for me Thanks!

Configuring Multi-VLAN support for Remote Network Monitoring with Domotz Pro Domotz Pro is a remote network monitoring software which supports multi-VLAN configurations for remote network and device monitoring. The software which is designed for integration companies and IT professionals enables a host of network monitoring features including: Remote Access, Remote Power Management, Network Mapping, SNMP, Alerts, Network Diagnostics and more. Read more about Domotz’s Remote Network Monitoring Features. Domotz supports monitoring of multi-VLAN network configuration through a variety of network installation options which include: Self Installation on a Raspberry Pi (i.e. your own Raspberry Pi device) or via the Domotz Box or Domotz Pi which are available for purchasing from the Domotz Portal. This post will explain how to configure mutli-VLAN support via your own self-installed Raspberry Pi device. Configuring Multi-VLAN support on a Self-Installed Raspberry Pi device for Remote Monitoring Starting from Package version 1.03-201(April 2016) of the Domotz Agent for Raspberry Pi, the full package can be installed on your own Raspberry Pi device and supports the discovery and monitoring of devices hosted on two or more VLANs accessible from the Raspberry Pi. (Instructions and latest package are available here https://portal.domotz.com/portal/hardware/instructions/raspberry) This short guide is meant for users who have multiple VLAN and are already aware of related configuration and procedures. For further details, and step by step guides, on how to configure VLANs on Switches and Raspberry Pi, the user should refer to detailed guides (for example, please refer to: http://www.sbprojects.com/projects/raspberrypi/vlan.php). In order to allow the Domotz to discover and monitor devices on two or more VLANs, the user should configure both the Switch and the Raspberry Pi to multiple VLANs: Switch Configuration The interface port of the switch which will be used to connect the Raspberry Pi, should be configured: - in Access mode / Untagged for the main interface used by the Raspberry to communicate with the gateway (e.g. eth0). - in Trunk 802.1q mode / Tagged for the additional VLANs to be monitored (e.g. the eth0.10 used for lan 10) Please, refer to your specific switch/model guide on how to configure Trunk 802.1q and Access mode (Untagged/Tagged) for the port. Raspberry Pi Configuration In order to configure the Raspberry Pi to access both the main and VLAN interfaces, execute the following steps: 1. Install vlan package and configure moduels: sudo apt-get install vlan sudo su echo 8021q >> /etc/modules exit 2. Open with your favorite text editor /etc/network/interfaces and configure the Network Interface to access the main and VLANs. E.g. if we have a primary network on 192.168.5.0/24 (DHCP) and a secondary VLAN 10 on network 192.168.100.0/24 (Static IP: 192.168.100.200): auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet dhcp post-up ifup eth0.10 iface eth0.10 inet static address 192.168.100.200 netmask 255.255.255.0 In bold the part of the configuration due to the VLAN support, if you are using the Stretch version please see bellow the additional steps. 3. Restart the Raspberry Pi Stretch Additional Steps For the new version of Raspbian (Stretch) the "post-up" has no more effect, for this version please do the following: 1 - Create a file “vlans” in /etc/network/if-up.d/: $sudo nano /etc/network/if-up.d/vlans 2 - Add the following to it: #!/bin/sh ifup eth0.10 3 - Make the file executable: $sudo chmod 755 /etc/network/if-up.d/vlans 4 - Reboot the Agent, the interface eth0.10 should be up automatically now. Further reading about Domotz Pro: · Remote Network Monitoring Features · Pricing · Remote Network Management Installation Options

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.

It's all a-OK on my TS-451. New agent shows up, installs without a glitch, and registers fine. Good to see it back up and running. Thank you!

This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud APIs, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of: Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.3.3 Violet - Digital Support (Domotz Customer Facing App): check on Apple Store or Google Play. Latest version as of today is 1.1.5 Domotz Agent: check on Domotz Portal under the license tab. Latest version as per today is 1.3.0 Domotz Pro WebApp is always updated to the latest version. November 23rd, 2016 Domotz Pro App: 1.3.3 - Domotz Agent: 1.3.0 – Violet Version 1.1.5 New Features: · Violet – Digital Support (Domotz Customer Facing App) (Available for large dealers only) o Latest events area improved o Simplified dashboard and device details · Reboot buttons added for: o Crestron DM o Chromecast o Direct TV · Multiple selection in Domotz Pro · Delete all offline devices · Note field on Customer Management tile · Latency graph added to monthly report · New Supported Devices: PDU and UPS: o American Power Corp UPS BG500 o Baytech PDU (Needs SNMP enabled) o Panamax models SM3-PRO, VT-4315-PRO and M4000-PRO Improvements · Improved SNMP discovery · DHCP naming and improved type detection Bug Fixes · Under certain conditions data from APC, UPS, Tripplite and Baytech could be missed

This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud APIs, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of: Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.3.0 Domotz Agent: check on Domotz Portal under the license tab. Latest version as per today is 1.2.1 Domotz Pro WebApp is always updated to the latest version. October 21st, 2016 Domotz Pro App: 1.3.0 - Domotz Agent: 1.2.1 New Features: · Periodic ping graph added to Speed Test graph · Search and Sort capabilities added to the Dashboard · Reboot buttons added for: o Sonos o Control4 · New Supported Devices: o Netgear GS728TP PoE switches o Planet SGSW-24040P4 PoE switches o Araknis AN-300-SW-8-POE switches Fixes · Up/down count now accurate Team members can now set Alerts on Services

I have installed Domotz on a Raspberry Pi 3 and am not having any issues with running Domotz. Blind ignorance and following the instructions got me to where I am so far.

This changelog covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud APIs, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. In order to fully exploit the new features, functionalities and bug fixes released, we invite you to verify that you have installed the latest version of: Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as per today is 1.1.8 Domotz Agent: check on Domotz Portal under the license tab. Latest version as per today is 1.1.0 Domotz Pro WebApp is already updated to the latest version. June 8th, 2016 Domotz Pro App: 1.1.8 - Domotz Agent: 1.1.0 New Features: o Alert for new devices discovered: from the Alerts section the user can now set a new type of alert that will be triggered as soon as a new device joins the network o Custom name on PDU and Smart Plugs ports: from the Config panel the user can now assign a name to each port, instead of assigning an IP device to it; this way the port can be recognized even if it’s used for a non-IP device o Professional Dashboard with Map: the access to the Professional Dashboard has been extended to all users o Agent site information and location customizable: every user can now set additional information to their Agent and assign a proper location in order to see it correctly positioned on the Map o Improved display of PoE information: user experience has been improved o Menu restyle Bugfixes: o Page scrolling issues on some desktop browsers o Copy/paste function on webapp: now available on devices list and device detail o Login errors when passwords contained UTF-8 chars o Expired agents appearing on map o Discovery not properly handling multi ip devices

I hadn't even thought of doing that. Still, there are people out there most likely using Domotz on a Raspberry Pi who would want that taken care of through the Domotz app. In the meantime I've put together my own Python script that drops me an email with a public IP.

Hi Neal, We automatically push new upgrades of the agents, sometimes few days after it has been released. You should have the latest version now. Kind regards, Silvio

I know this is a fairly low-priority item but it would be useful for those of us with RasPis (and maybe others in structure). The ability to get the Domotz agent to login without a web browser by allowing a command-line submission of email address and password. We already are doing a number of steps to install (or upgrade) the agent in command line (regardless of whether it is headless or not). This would allow a person to just continue following steps (easily copied from the Domotz Portal's instructions) to complete the entire process. No other windows or browser needed. This would allow the steps to be more easily automated. Related to this, if the Domotz agent can be downloaded the same every time (example, in the future you could always go to: wget https://portal.domotz.com/download/agent_packages/latest/raspi.deb) the entire process could be a single script and would never change IF someone wants the latest. Such a structure works for any of the releases (with different end file names) and could readily be altered for future betas that you might not want accessible to everyone (by making it .../agent_packages/betas/... and having user/password restrictions based on portal access). Then someone could actually LOGIN to get the beta software also easily added to the wget command.

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).

The Selection for Device Type will not allow me to scroll down on the Webb App. works great on the Domotz App.

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.

+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

Seems like it does not want to install on my Synology. Anyone see this error yet? Model: DS415Play CPU: INTEL Atom CE5335 DSM: 5.2-5592 Update 4 Version Tried: domotz-syno-x64-5.1-0.9.3-109.spk Date: Oct 13, 2015 Error: The package is not supported on the platform of DiskStation

Some feedback on the Android app: 1) In general, some release notes might be nice. Added into an about or other section within the app would be handy especially for the beta. 2) Starts off with "All devices are down" when first connecting (or attempting to). As I have a poor data connection at times this is not actually accurate. When the app first starts it should not have this warning but rather just have the Loading (or a "Connecting") more prominent. This appears to be because mine is opening on the "Online" tab (which seems appropriate). However the Offline tab shows "All devices are up" at the same time and the All tab shows "No devices detected". Obviously these are incorrect if it is a case of the app being unable to connect to Domotz. 3) If there is no data connection when the app starts it appears that it "gives up" checking after a bit. Not sure what the timing involved is but mine never said anything beyond "All devices are down" with the "Loading..." at the bottom even after my data had come back. 4) My agents list appears to have been cleared out. Only the currently active one "Backup" remains (which is fine). I assume this was done for the beta and is not a bug? After restarting the app a couple times over the testing the other Agents reappeared. I was actually happy they had gone away. 5) Customized names, locations, favorites, etc... did not get retained. 6) Favorites symbol added to icon on list would be better if it is filled in with yellow (to make it easier to spot). 7) The symbol that the domotz agent is running on a particular piece of hardware is useful. However I would add it to the icon (like the favorites) instead of taking up space in the name area. 8) Every device defaults to "Important". Instead I think most should default to indifferent. At least until such a time as you can determine general types (router for example) that should default to important. Until then the only one I would default as important would be the hardware for the agent. 9) Some devices have a Last Status Change date of much longer than when the agent was reinstalled. Not exactly sure why they would not be based on when the agent could first detect them. Even if this is due to some retained cloud information that could be inaccurate. Ex: My router was rebooted last week (prior to the current agent being installed) which should have triggered a change. But nothing is listed in the History for it. 10) When entering a custom name or location there is a little white circle with an X at the end of the entry line. Selecting this clears the line and sets it back. However this icon is FAR too close to the checkmark confirming entry. I have selected it a couple times by accident which is... annoying. Further it does not seem to have a lot of purpose. You can always select the red X to back out of the entry or use the backspace function in your keyboard... 11) It might be nice if you could have the favorites appear at the beginning of whatever sort is performed (but sorted amongst themselves) then the non-favorites sorted after them. This could be a checkbox in the settings "Sort Favorites First" type of thing. If they are favorites then I want them most. Or make Favorites be a selectable Group By. 12) What is the current expectation for importance? It does not impact sorts. There does not appear to be any function built around it (that I have found yet). If you were able to set up general alerts (ex: alert me if anything important drops offline) then that would make sense. 13) When creating a custom alert... maybe I am dense, but why would HB (Heartbeat I assume) Lost be any different from the device going Down? 14) Would it be possible to create an alert for "IP Change"? The device did not go "down" or "up" but it changed IP (maybe the DHCP renewal gave it a different one for some reason). 15) Hitting Back from a major screen (Devices, Alert Manager, etc...) immediately exits the app. Confirmation on the Devices screen would be nice (that can be disabled in settings). It would also be preferable that selecting Back from the other screens switches back to the Devices screen. This gets pretty annoying when using the other screens as I keep accidentally exiting the app. I also found you can hit Back when the search is displayed for devices to exit... Instead of exiting the search (like the red X) it exits the app. 16) Network Info is only displaying "N/A" for the Public IP Address, Public Name, and Provider. Pretty sure these were populated when I checked yesterday while at home (on the network). Not sure why they are dependent (if so) on being on the network. 17) No selections available within the Speed Test. What if I wanted to select a different server versus whatever is determined to be "Nearest". Not clear (in the app) how the nearest is determined as mine decides to go to Ontario (which is in Canada). There are none closer in the US? 18) It would be nice if a history of Speed Tests could be made to compare results over time. Also if it were possible to set the agent to do a speed test on a regular basis so you could see how it is working over time without having to set it up manually every time. Maybe 1 hour and 1 day intervals? Able to be set for 12hrs, 24hrs at the 1 hour interval and 7 days, 14 days, and 30 days for the 1 day interval? That should not cause undue strain on the speed servers. 19) Assuming the Diagnostics section will get more tests... The Start should be "Start Test(s)". Further it would be nice, once there are more, if each test could be selectable by a checkbox. Maybe I will only want the ECHO and not the PING (?) test, or the "Port Security" test. 20) Speaking of Port Security... A test that attempts to connect to a device (or all over time) and tests which ports are exposed on the device(s) would be handy. Especially if that information is then recorded in the device's info. It would help detect potential security threats or just areas that were forgotten. 21) Ability to configure tests to be run automatically on a regular cadence (like the Speed Test) and the results logged would be useful. Even more useful if much of the logging could be exported for better analysis (using an XML file maybe) or downloaded from the cloud (or the agent itself). 22) It is necessary to hit the Done button when adjusting the device sort/grouping. Selecting it once implements it (it is possible to see behind it) and the second time to actually close the dialog. 23) Devices without a location set are grouped at the front of the sort when Location grouping is set. IMO they should be at the end. 24) The ability to set the refresh interval MAY be desired. Some people may not want the app checking with the agent all the time (if they have data caps for example). This leads to other points... It may be desirable to only allow the app to refresh when a person is on WIFI or adjust the intervals separately. I have unlimited data, so I do not care... but that is becoming rare here in the US and we are charged pretty absurd rates for data (overall). It is also not clear how much data domotz uses. This might be something you want to provide examples of. 25) Being able to trigger a sample alert might be nice so people know what it looks like before it happens. 26) A time based alert trigger for when a device goes down could be useful. On things I really do not worry about they could go down for periods of time and I may not worry too much. Other things I would want to know... but only if it does not recover in a "reasonable" period of time. Where I set the time. For example I have a number of custom sensors. If they do not reconnect in a day... I would like to know. Less than that... I can live with (and I would not leave work for any of them). My aquarium controller goes down though... I want to know if it does not recover within an hour (if not sooner). 27) The ability for the app to determine if it cannot reach the domotz agent because it does not have data (oops, your phone is not connected to anything) versus the agent being unreachable (your phone is connected but we cannot reach the agent). In the example of my house, that could mean the RasPi failed, the router failed, or the cable modem failed (or any combination). 28) Once entered I think the Username and Password section should move to the bottom of the list, under the Agents. It is far less useful than the others at that point.

When you say cloud its like you're saying it needs internet to work which is a very big problem with many smart devices. Obviously internet would be needed for it to work remotely but wouldnt it be easier if the device running it could be directly queried?. So instead of going to domotz cloud to see your devices you could use port forwarding/VPN and just query the server directly. Using LAN when possible for the app to connect to the server would be cheaper for domotz and more responsive for the app which sits well in the privacy question and security since you could connect to your home using VPN. Although SSL or HTTPS does add security for using the app through the cloud but it needs to be enforced with certs and keys. A lot of smart devices require internet to function which can go horribly wrong if the internet connection drops for a minute which is not uncommon to get a few packet losses but it also makes them expensive since the manufacturer has to provide the server to handle the processing for the smart devices on top of the status page and development costs for their products and apps. The issue with this is that there arent many good coders and with the CPUs that smart devices use bad programming becomes very apparent when the CPU has no out of order processing such as the ARM A7 that the raspberry pi2 uses. It is also common that consumer routers arent stable enough to run 24/7 reliably.

General: 1) Interesting that the app can control vibration (I assume for alerts) and prevent the phone from sleeping. 2) First time logging in does not immediately present you with the login screen, you need to hit the menu or swipe left to right for it. 3) Login failure provided no notification. I accidentally entered my password incorrectly but nothing happened that I could see. I just noticed I had the wrong letter at the end but hit enter before I stopped myself. Correcting the password accessed showed my agent. 4) Your available agents is at the bottom. I would recommend this be at the middle, with the login moving to the bottom after you have been successfully logged in and the 3 sets of information at the top (Devices, Alert Manager, and Diagnostics). 5) Username and password COULD be hidden after successful login from this screen and only displayed as needed or with a link button at the bottom.They take up a fair amount of space otherwise. 6) There is no option to logout or a timeout for login or such displayed. No idea when/if my login might cease. Since this is fairly valuable network information there should be options for such things if someone wants them. 7) If someone has multiple agents it might be nice to have a tree structure of agents, and the 3 sets beneath each... but I would have to set that up to check and I only have 1 RaspPi available at this time. 8) Devices listing is the main section displayed, which works for me. 9) Having all items immediately listed as generic is a bit of a downer. It would be good if Domotz starts building up an inventory of things and auto-identifies devices as they are found. A user can easily change it otherwise. For example, known routers could be set as Network Equipment. The RaspPi itself should be specially identified running the Domotz Agent. 10) Scrolling on the individual device screen is a bit tricky. If you scroll all the way down it hides the top section (the status, ip, and changes) which is quite a visible change. However in order to scroll back up you need to use a quicker, more "vigorous" swipe motion to scroll it back. Slow swipes just are not as effective for some reason. 11) There is a lot of information presented and the top of the device page is a bit dense. Some information on the page is repetitive (Status, # of Status Changes, IP) lower on the page. I would remove those unless the idea is the sections at the top be configurable (3 things that show information, but you can change them individually). 12) Once much of the top information is configured (Type, Place, etc...) it would be good to move these down the list towards the bottom. For the most part they are set once. The other data on the page you want to have easy to see. 13) Favourites is listed. This would be the UK English version. US English users will find this odd (indeed my spell checker indicates I have an misspelling). 14) Delete Device is greyed out. Not exactly sure what that would do from a network monitor perspective nor how I might get a deleted device back again if it just removes them from the listing. Not sure if this should remain. 15) First Seen attribute uses time in BST timezone. It would be better if it recognized the timezone from the smartphone and used that. Worst case use GMT. BST (Biel Mean Time) was made by Swatch for goodness sake. It matches CET. BST is basically a horrible... horrible thing that should die. Do not encourage anyone. 15) From the main devices screen it would be nice if swiping did more. Swiping from left to right gets the menu (as limited as it is and despite there being a menu button someone can select). Swiping right to left feels like it should switch between the device lists and then maybe into the Alerts and Diagnostics pages. But it does not. 16) Not sure what the ordering of the devices is. A little header row at the top that would allow you to sort by each of the columns would be nice. Hours uptime, type, Name, IP Address sorted high-low and click again for low-high. 17) Categories acts as a filter. Did not get that at first and you can only select one category at a time. Other useful filters would be by the device type and by location. 18) Not sure what the "Plugged" category is. Some of my devices are wired, some are wireless. This does not show any devices. 19) Some help or tooltips might be useful in such cases as trying to determine what "Plugged" is... but not critical for me (eventually I would figure to view it on a website). 20) Favorites in the device list should be highlighted more. Besides making their star a nice bright yellow (like on the device details page) maybe they could have a slightly shaded background. More visual distinction is really needed for them. 21) Alerts are interesting... Little more work needed for me to understand them completely. But first and foremost I would like the ability for the Domotz app to be able to notify me if the agent cannot be reached. That most likely means my network is down and that is something very important. I do not see any way to set this and how long is "too long" before it starts to warn me (in case my phone does not have a good data connection, I do not need notices every second or minute, but X time let me know and if it continues to be unavailable let me know at X interval). This should be easy to turn on and off. If I go camping I know I am not going to have a connection for example. Enough for now. Thanks for the initial look. VERY interesting stuff.