Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. henriquesalvador

    Internet Connection History Tech Overview Request

    Hi @aks_Dale, Here's a detailed explanation about the Downtime tab: Network Health Analysis --> Downtime Tab: Agent Connection Lost Alert (marked with a bell) vs Simple Disconnections The two features ( Agent Connection Lost Alert - Simple Disconnections) are similar in the idea, but technically speaking they have been implemented in a very different way. This is very important, because it is a good way to guarantee that both are working correctly, or to identify if there is a misalignment in one of the two mechanisms Basically, every Domotz Agent sends a packet (or train) of 4 ‘pings’ toward "echo.domotz.com" (alias of Google DNS - 8.8.8.8) once every minute. It also sends a Heartbeat to our cloud, to notify our backend that the agent is still alive. Agent Perspective: Missing Ping --> triggers an entry in the Downtime Tab - Simple Disconnections If we do not receive a reply on at least one of the pings in the packet, (either the DNS is failing, or there is not any internet connection, network cable is detached from the Domotz Box/Pi, or simply our ping server - echo.domotz.com is not available) the Domotz Agent tracks the time that the first ping was lost. Two minutes after we start receiving replies to our ping messages again, the Agent notifies our backend that the connection is UP again and that there was a Downtime of X minutes (starting from the first ping lost). This is going to populate the Downtime Tab. (This delay is to ensure that the connection has become stable again before recording the data). What happens if the Domotz Agent is turned off (unplug the power cable from the Domotz Box/Pi)? In this case, the Agent does not send any ping (of course) and cannot be aware if there is connectivity or not. Therefore, there will be no entry in the Downtime Tab, for the whole period the Domotz Agent is off. However, our backend is still aware that something is going on. See next: Cloud Perspective: Missing Heartbeat --> triggers the alert (if configured in the Alert management) and mark disconnection with Bell After Five(5) minutes have passed since our backend received the last Heartbeat from an Agent, the backend declares that Agent to be OFFLINE. If the Agent Connection Lost alert is configured, you will receive an email from our backend stating that the we haven’t received any information from that agent in the last five minutes. In any the disconnection in the Downtime tab is marked with a bell. As soon as the Agent starts sending the Heartbeats again, you will receive an email from our backend stating that the connection to the Agent was recovered. This last mechanism works both if you disconnect the power cable or the network cable from the Domotz Box/Pi, because it's triggered by our backend. If you still believe there may be a problem with the Agent, please contact our support (support@domotz.com) informing your Domotz account and Agent Mac Address. Kind regards, Henrique Salvador Domotz Support
  3. henriquesalvador

    Reset Raspberry Pi Domotz - No access to original account

    Hi @Crustyloafer, Please contact our support (support@domotz.com) informing your Domotz account and Agent MAC Address. We will assist you. Thanks, Henrique Salvador Domotz Support
  4. We have pulled a Raspberry Pi Domotz out of a takeover job and wish to re-use it for our own purposes. Is there a way to factory reset the device without having access to the original Domotz account it is currently linked to?
  5. Just installed a new Raspberry PI w/ Domotz. This site is showing the Internet connection is bouncing with over 650 up/down entries in 20 hours. The connection is via wireless distribution to a site about 2 miles away. Normally a solid connection, currently the Internet is spotty at best. To present to the client and the wireless distribution provider, I'd like a technical overview of how Domotz monitors/records the internet connection history. Thanks!
  6. Yesterday
  7. thomas_n

    Windows Agent on Hyper V

    Ah, yes, that makes sense. I actually scanned the VM with Fing, but port 3000 showed up as something other than http so I did not bother to try that. But all is well now and I am successfully using the "official" image in a first installation. Looking forward to roll this out further. Thomas
  8. Giancarlo

    Windows Agent on Hyper V

    Well, once started, just connect to port 3000 of that VM via a Web Browser. In that way you can configure the Domotz Agent running within that VM. For example if you get the IP by scanning the network (using Fing for example) or from the Router information, just connect to: http://<IP_of_VM>:3000 If you want to login via SSH to the VM, use domotz/domotz for the credentials.
  9. Last week
  10. thomas_n

    Windows Agent on Hyper V

    Update: actually, I can't log into my hacked VM either. But I never needed to do that as I used the Agent Manager to link it to my account.
  11. thomas_n

    Windows Agent on Hyper V

    Thanks for this clarification. Unfortunately after installing the VM as you suggested I find that it won't accept my login credentials. First I thought it might not be connected to the internet, but I see it on my network. Secondly I thought it might be due to two factor auth on my account, so I disabled that but it changed nothing. So, I'm not sure what I am doing wrong but at this moment I don't see how I can get this to work so I'll have to stick with my hack for now...
  12. Giancarlo

    Windows Agent on Hyper V

    Hi Thomas, thanks a lot for this guide and your feedback with the package. Definitely the Domotz Windows Agent Manager is not supposed to be hosted on an already virtualized Windows environment. Best would be to get directly the image installed by the Domtoz Windows Agent Manager. The current image (OVA format that you can convert in OVF or VMDK) is publicly available at: https://s3-eu-west-1.amazonaws.com/domotz-vm-images-temp/domotzpro-ubuntu-18.04.1-amd64-1.0.3-b003.ova MD5: e87e9cedee648ebdf9cb8ba16e7a0134 Note: we are going to upgrade that soon. You can check the latest version released here: https://portal.domotz.com/assets/ubuntu-domotz-agent.json The image is based on Ubuntu 18.04 and it provides automatic upgrade to the Domotz Agent (packaged in a SNAP format). I hope these details will help for the self configuration of a Virtual Machine with the latest Domotz Agent version. We are also upgrading the Domtoz Windows Agent Manager, so that it will overcome the following limitation: "What I don't like about the setup is that it uses Virtualbox which runs only when a user is logged on" This new version (will be marked as the first production one, since the current one is in Beta Mode) will be available in around 1 week. I hope this helps clarifying.
  13. thomas_n

    Windows Agent on Hyper V

    I have just switched an installation from a separate device with the agent to a VM on a Windows 10 computer acting as a home server. What I don't like about the setup is that it uses Virtualbox which runs only when a user is logged on. Secondly, I don't want to use Virualbox for my other VM's. So, here's how I did it: Installed and ran the Domotz agent for a first time, linking it to my account. Stop the VM and export it from within Virutalbox to the ovf 2.0 format, this also creates a VMDK file Use any tool to convert this to a vdk file (I used Starwind V2V) Create a virtual switch in Hyper V connected to the external network Create a new VM in Hyper V with the correct settings (copy the ones from Virutalbox) and use the vmdk file for the harddisk Start the VM (Optionally) set the VM to autostart when the computer starts If you follow these steps, you now have a VM with Domotz running in Hyper V as soon as the computer is started. You can then proceed to unistall Virtualbox and the Domotz Agent Manager. Honestly, I don't understand why the agent is not made available as a VM, rather than the complete package with the agent manager. It seems too complicated for the purpose to me. Disclaimer: not sure how this will survive any software upgrades by the Domotz team, use at your own risk.
  14. henriquesalvador

    Domotz Eyes with Custom OIDs - Temperature monitoring example

    Hi @GregS, Readings of SNMP values are made every 30 minutes by the Agent. Which is sufficient for most cases, it's on our backlog a way to customize this frequency.
  15. GregS

    Domotz Eyes with Custom OIDs - Temperature monitoring example

    We did something very similar to this last year for monitoring rack temperatures, but found that Domotz did not check snmp often enough to make it useful for things like that. It was randomly between 30-55 minutes. Have they updated that now? I've lost track of most of the features in Domotz these days as there was so many coming out so quickly.
  16. Earlier
  17. 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
  18. TimAG

    Report Scheduling

    Hi Giancarlo, Thanks, good to hear. The reporting feature is a major bonus to this unit, as it is the assurance as an integrator to their client that their system is being maintained and you are being active about it. Cheers, Tim.
  19. Giancarlo

    Report Scheduling

    Hi Tim, Jarret I agree with your view, and I like the idea of having the possibility to automatically schedule the report to be generated on a specific date. It is in our roadmap of features to be developed, even though I can't promise exactly when this will be available. Thanks for your patience, Giancarlo
  20. installersteve

    Stop pinging a device

    Apologies, I found it in 'Manage Devices or Subnets'
  21. installersteve

    Stop pinging a device

    Hi, have the features above been enabled through the app yet? I can't see them anywhere. Thanks.
  22. TimAG

    Report Scheduling

    Adding to this note; Today I received a monthly FING report.. which includes quite a detailed internet performance report. It is very nice, informative and comes at the end of the month.... Anything from the Domotz box in that regard? An automatic end of month report... details about the connection - internet performance? I assume all info available to Fing is available to Domotz. And needless to say, with a way to download the same in a raw format so that it can also be integrated into our AV integrator monthly report? Thank you, Tim.
  23. Giancarlo

    TCP Tunnel - Crestron from remote

    Hi all, This is all the steps to connect from remote to your Crestron Processor using Domotz Pro: Crestron Instruction Select the Crestron Processor from the Domotz WebApp → Device list → Device Go in "Connect" tab Click on "Create a TCP tunnel" Insert the Crestron Processor TCP Port. By default "41795" Wait to have the tunnel setup You get two information: Host Port Open Crestron Toolbox program on your Laptop and: Open a new project Insert the previously retrieved Host/Port to be inserted in the following scree (see below as an example) Save & Apply
  24. henriquesalvador

    TCP Tunnel - Lutron from remote

    Hi all, This is all the steps to connect from remote to your Lutron Processor using Domotz Pro: Lutron Instruction Select the Lutron Processor from the Domotz WebApp → Device list → Device Go in "Connect" tab Click on "Create a TCP tunnel" Insert the Lutron Processor TCP Port. By default "51023" Wait to have the tunnel setup You get two information: Host Port Open Lutron Designer program on your Laptop and: Activate -> Processors --> Remote Access form Insert the previously retrieved Host/Port to be inserted here (see attachment as an example) Save & Apply Now you can use your Lutron tool to to remotely access to the processor: a. Designer+ Tool for Lutron HomeWorks QS: b. Lutron RadioRA 2 System Overview for Lutron RadioRA: Go to the Find Main Repeater Screen from here in the Design Tab And select Advanced, then Remote for System communications as shown here: He should also have had a previous transfer without the checkbox being selected “Restrict Communications to Local LAN”. Let us know if you have any problem. Henrique Salvador Domotz Support  support@domotz.com
  25. The Luxul Router have on its own the possibility to configure multiple-VLANs and make them available to the Domotz Software running on the Luxul Router itself. Therefore, even though it is not possible to configure multiple-VLANs from the Domotz Agent WebGui, when the Domotz Agent is hosted on the Luxul Router users can configure multiple-VLANs on the Router itself (from the Router WebGui) and make them available to the Domotz Agent software. This is available on the latest Epic 3, 4 and 5 Router firmwares. --- I am really sorry for this. As a matter of fact, there is currently this limitation: if the network is configured as /16, you won't be able to configure other parts of that network as additional subnets in Domotz. Our engineering team is working to remove this limitation. One possible workaround, for the moment, would be to configure the Domotz Box on a Static IP with a smaller subnet mask, and then you will be able to configure the additional part of network as external subnets. For example, let's imagine you have the following situation: Main Network: 172.16.0.0/16 And you want to monitor two different parts of that network through the Domotz Box: 172.16.0.0/22 172.16.50.0/24 172.16.65.0/24 You can basically configure the Domotz Box to sit on the first part of the network, with a smaller mask: Configure the Box with Static IP. E.g. IP: 172.16.2.25 mask: 255.255.252.0 In that case, you will be allowed to add scanning of the additional part of subnets: 172.16.50.0/24 172.16.65.0/24
  26. So, i have eth0 assigned a subnet of /16 (255.255.0.0). If the limit is /22. then I should still be able to add an individual IP address outside of the /24 mask as an single external host/IP... but Domotz reports that the IP is already being monitored... but it doesn't show on the web portal. I so can't even add one host within the /16 subnet that the interface is assigned?
  27. Hello Giancarlo, Out of your comment above, can I clarify one thing please. You mention that when the Domotz Agent is hosted on "own" hardware it is limited to its vlan scan because of the inability to re-configure, where as on the Domotz Box this is not an issue. Does this also apply to 3rd party hostings, i.e. when hosted on one of the switches that sells themselves as having Domotz included? (i.e. the Luxul routers) Or alternatively said, we should always buy the standalone Domotz box to have the "full" functionality? Thank you, Tim.
  28. Thanks for your feedback. With regard to the Advanced plan trial, we know this limitation, and in 2 weeks this should be resolved. New users will be able to trial for 21 days, regardless the number of Agents they want to install and regardless the plan. At the moment, we have such limitation: therefore I took the liberty of adding a few credits to your account, so that you can extend your existing Agents, and also perform a proper trial on the Advanced plan. With regard to the limitations you listed, please note that the Domotz Agent will scan automatically the main interface (i.e. eth0) with a maximum network size of /22. However, you are allowed to add VLANs as you like. Note that the Domotz Agent, when hosted on your own hardware, cannot perform network interface re-configuration to configure VLANs. On the other hand, this is possible on the Domotz Box (where we own the network stack and we can perform that kind of action). In the cases you are not able to configure additional VLANs (truck - Layer 2), Domotz offer the possibility to scan routed subnets (maximum size of each subnet is /24), when the Agent is configured on the Advanced Plan. Note that when the scan is on a Layer 3 (routed subnets), the scan is not able to retrieve MAC address of devices. Therefore, this is only recommended on subnets using static IP. I hope this helps clarifying. For any other doubt, or if you need specific assistance, you can send an email to support@domotz.com
  29. After reading the manual some more, and deploying a Pi. It seems we won't even be able to test the Remote/Private Subnet features at all due to the demo licensing is not Advanced...
  1. Load more activity
×