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

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.

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

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 was reviewing my network with Wireshark and noticed the incredible amount of ARP requests that Domotz outputs. It sends an ARP request to every IP address in my network. I have 2 VLANs that Domotz monitors. Is every 30 seconds really necessary? Looking at my L3 network switch, it looks like my CPU jumps up 10% every 30 seconds. Not a huge impact, but it seems a bit excessive. Anyone else notice this? Is there a way to change the frequency?

Hi folks, We are also seeing large amounts of broadcast ARPs - 500 broadcasts over a 1s period, every 30 seconds. Although this may be acceptable to devices with powerful processors, our humbler devices (10Base-T) are getting heavily loaded by this, and our real application messages are getting slowed/lost. Is it not possible to stagger these ARPs, or send unicast to known devices, rather than hitting a network so heavily, so often? We also notice broadcast ARPing to subnet-broadcast address x.x.x.255/24 and x.x.x.0/24?

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!

Correct. Just wipe the configuration of the Raspberry PI and install from scratch.

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

It would be nice to see device up/down history in the Logging report section. No need for PDF exports, simple text file would be nice. Sure, I could make sure all my alerts go to e-mail and then sort/search through those but why do that when you should be able to easily implement device up/down history. Also, login/illegal login attempts to our Domotz account should be logged (with IP of user trying to login) for auditing purposes, especially since you don't yet have 2FA. Additionally, creating an alert (push or email) would be really nice for login and illegal login attempts. As has been mentioned in other threadse, 2FA should be prioritized. An added security measure that could easily be implemented would be a short timeout period after so many failed login attempts (5 failed attempts = 15 minute timeout or something). Going even further, the ability to blacklist/whitelist IPs for account access would be really nice.

That was exactly what was going on. Sorry about the confusion. Good to know about the license transfer possibility.

Hi Oliver and Dave, Dave is correct that re-installing the package for the Raspberry Pi will resolve the situation. The package includes the 1.5.0 version but there were no new visible features in the 1.7.0 compared to the 1.5.0 so you will be able to get running again while we resolve any problems that may occur with the automatic update to the 1.7.0 agent. Let us know if you have any problems with this and please try to send any questions to support@domotz.com so we make sure we don't miss them. Thanks Brent

Does anyone know how to change the Domotz Box's IP to a static IP or should I juts use DHCP reserve?

I turned on my Orvibo S20 power switch using its domotz config tab, now I cannot turn it off. Each time I do that, it attempts to go "Off", then goes back to the "On" position with the following message: " Unable to toggle port 1 The port didn't respond within the expected time." The S20 switch is actually (physically) turned off each time I attempt to turn it off this way, so maybe the config interface timed out faster than the response. Orvibo's Wiwo app on iPhone shows the correct state of the S20 switch though. Another observation: I have the S20 switch set to auto off at 10:30pm, scheduled in Wiwo app, but it seems that the domotz "On" setting might have prevented it from going off at the scheduled time last night, so I manually switched it off using Wiwo app. Will monitor further. Edit: Second issue was due to incorrect timer setting on Wiwo app, please ignore that.

tapping into this. Is there a way to tweak broadcasting or use unicast? I was troubleshooting our network performance an 3.5 million packets a day. happy to sacrifice realtime alers for the network. for the moment turning off domotz

Our sites are mostly business sites not home users, so violet seems a bit misplaced for them, I would like to see far more customization, to allow us to prescribe what an app shows, for some users it may only be a few items of many on their network, others it might be several sites (agents) and all or a few devices from each. Essentially most of he customisation and setup of alerts in violet shouldn't be soley in the app we should have access to it from domotz. I look forward to seeing developments. Kindly, John

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

Silvio, What's the status on setting up a static ip for Domotz? Thanks.

Hi, Unfortunatelly my W10 machine is very limited (in terms of hardware - I am running first version of Intel Compute Stick), so running virtual machine on it is not really an option. Are there any plans for releasing Windows client? BR, Mikolaj

Swipe left to right on the top of the screen for clipboard and keyboard options. It's demo'd here

fully agreed with IJoe, and this is why we implemented PerfSonar(which is much less stable and full of servers that are not working... but when it works is very reliable). But unfortunately 90% of our users are complaining about the significant differences they get as compared to speedtest.net and they would like to use that. So we are moving to that direction. But I am not going to delete the perfsonar code (and hope at some point we can have both, which I think would be great for users to have two different measures). I do not think we have resources for having both soon. But it is definitely something that I am very willing to do

ability to configure VLANs via the UI vs. SSH

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

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

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

What you ask is already possible if the agent is offline or down (change the settings of many devices from the app and then reconciliate all the data when back on - click-to-enter and other features are disabled in such cases). I know this is not what you meant, but somehow testify our efforts and willingness to keeping the user experience tolerant to disconnections any time this is possibleCaching inside the app, is quite more complicated, but our APP experts are just telling me, not so impossible!

Performed the entire uninstall, download, and install process remotely using SSH today from my smartphone. Then went into Chrome to link the agent to my account. I had to make port forwards for those to work outside of my network but there were no issues with the actual steps.

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.

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.