Jump to content

Leaderboard

  1. henriquesalvador

    henriquesalvador

    Staff


    • Points

      3

    • Content Count

      24


  2. CoolAEW

    CoolAEW

    Members


    • Points

      3

    • Content Count

      14


  3. travislpriest

    travislpriest

    Members


    • Points

      2

    • Content Count

      1


  4. Mauro

    Mauro

    Administrators


    • Points

      2

    • Content Count

      9



Popular Content

Showing content with the highest reputation since 03/25/2018 in all areas

  1. 3 points
    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
  2. 2 points
    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.
  3. 2 points
    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
  4. 2 points
    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
  5. 2 points
    Wondering if OpenMesh is on your radar for integration? Cheers, Matt
  6. 2 points
  7. 1 point
    Can we create macros that the client can more easily understand? "Restart cable boxes" "Restart Den System"
  8. 1 point
    Correct. Just wipe the configuration of the Raspberry PI and install from scratch.
  9. 1 point
    Great, thanks for the help with this. Paul
  10. 1 point
    I'd love to see SNMP v3 support added or at least backward compatibility to v1.
  11. 1 point
    This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. October 15th, 2018 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.8.5 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as per today is 2.3.1 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.6.7 Domotz Pro WebApp and Portal are already updated to the latest version What's new: Subscription Plan: a convenient way to purchase Domotz agents have been added. Users can now pay for what they are using, instead of a large, up-front purchase with the credit system. Users are able to receive an invoice at the end of the month period for the agent currently installed in the Account. Pre-Paid agents: Domotz users are allowed to continue pre-paying Agent using residual credits or credits redeem through Partner Vouchers. Redeem of Credits during Agent configuration: Domotz users can now redeem vouchers directly during the configuration of a new Domotz Agent. This method can be used to pre-pay specific Agents with the credits purchased through Partner Vouchers. Public API: it is now possible to request an API-Key and the documentation to use Domotz Public API to access the data related to a specific account. API-Key and documentation will be available directly in the Portal. At the moment the request can be submitted to the Support Team. Windows Agent: Domotz users can now download the latest version of the Windows Domotz Agent directly from the Portal. Windows Domotz Agent can be installed on any Windows 10/8/7 with Virtualization option enabled. Ubuntu 16.04/18.04 Agent: new Domotz Agent can be directly downloaded from the Application Manager of Ubuntu 16.04/18.04 OS. Domotz Snap (package) is available on Snapcraft.io. Package benefit of the complete automatic upgrade. Improvements: iPad mobile App: left side menu can now be hidden. Dish Network Tile: Domotz users with Agent discovering Dish Network devices can now easily access the device using the specific Tile. New PDU/Smart Plugs: Support for TP-Link HS-100 HW version 2.0+. New Portal landing page: Domotz Users can now easily access to the download page for software version of the Domotz Agent. Trial period for unlimited Agents: new users have now the possibility to configure an unlimited number of Agents and use different Plans during the Free Trial period (21 days). Domotz Agent Windows Manager: a new version of the manager (1.1.0) have been released. The latest version overcome the limitation of requiring the login credentials after the reboot of the machine to allow the start of the Domotz Agent (through Virtual Machine). Fix: iPad misalignment has been fixed Device report (XLS) did not properly manage WiFi type of connected devices It is now possible to open properly multiple TCP tunnel on the same or different devices Invalid emails are not accepted anymore during the registration phase of new accounts Custom Route analysis can now be performed through iOS mobile App Known limitations: Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Static IP address on the Domotz Box cannot be configured before configuring the Agent External monitoring of public and private subnets might not work properly on Raspberry Pi installations Multiple Devices logically connected to a Managed Switch Port: in case of WiFi AP connected to a switch port, the information is not available at the WiFi AP info
  12. 1 point
    Ok. That explains why the Domotz is reporting that the network is bouncing....I can't ping 8.8.8.8 from within the network from any box. The ISP (a local wireless internet provider) appears to be blocking 8.8.8.8. I'll have to discuss the implications with them. Today, the Internet connection appears solid from the user's viewpoint, but, Domotz is reporting bouncing about every minute. At least your explanation gives me a point of reference and direction to move. Hopefully, others will find this helpful. Dale
  13. 1 point
    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. 1 point
    It would be useful if (in addition to Important and Indifferent) there was a category for Critical items, that we can use for control processors, NVRs etc, and an option to alert all team members by default if anything in this category goes offline. We are currently using an email distribution group account to do achieve the same thing, since otherwise we have to rely on individual team members configuring critical device alerts, and have no way of confirming that they've done so without access to their account.
  15. 1 point
    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
  16. 1 point
    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
  17. 1 point
    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.
  18. 1 point
    Just wanted to let you guys know that the Domotz portal app works great as a web side panel in the Vivaldi Browser! Just add https://portal.domotz.com/webapp/#/overview as a web panel
  19. 1 point
    Hi TonyC, you can check the version from the Domotz portal. Under the Subscriptions menu, go under the Edit button and there the agent version is indicated. We automatically upgrade the agent every time there is a new release. Please note that, when you install our package on a raspberry, it includes the agent as well as a number of libraries. While the agent is upgraded by us, the rest of the package cannot be upgraded. We always do our best to avoid incompatibilities, and currently we have happy customers even with old or very old packages, but it is highly recommended to reinstall the package to a newer version from time to time.
  20. 1 point
    You've got some nerve rolling out an "advanced" version of a product that is so severely lacking the most basic functionality and still so severely bug-ridden. Until now I kept hanging on, hoping Domotz would eventually come anywhere near to deserving the "Pro" moniker. I guess it's time to cut the losses and look elsewhere for a real network monitoring solution for small to medium networks. I like Fing, but I don't really trust it any longer, knowing it comes from the same stable. I can't even begin to describe the extent of my disappointment. At least I still only have two test installations. There is no way I could deploy this to any of my customers and charge them with a straight face. And frankly, I can't see it being ready for prime time anytime in the foreseeable future. Very sad, but that's how it is. In the brief time Domotz was in the picture, my initial enthusiasm was worn down to nothing, being replaced by mounting frustration at all the limitations, idiosyncrasies, omissions and bugs.
  21. 1 point
    to change the ip address connect to the box locally or thru connect function in app box ip address and port 3000 example http://192.168.1.30:3000 or on the app create use port 3000 then select network info on tabs of left the edit network settings this is also where you setup VLANs
  22. 1 point
    Not sure where you got the idea that vlan supports requires domotz hardware. I have my domotz that is running on vm monitoring all my vlans. Yes what your running the software requires the ability to have an interface in each vlan.. Domotz does discovery via arp. Monitoring across a router has a flaw that maybe the router/firewall your crossing to access that other network is just blocking the monitoring. So is the device down really? Can your NAS create sub interfaces or vlan interfaces - if so then it should be able to monitor any vlan you want. If not then yeah your going to need something else to do your monitoring from if you want to monitor more than 1 vlan.
  23. 1 point
    Hi Can I add to this discussion please? I don't believe this is just a Mac issue. I have an Intel NUC PC running Windows 10, which when I put it in sleep mode still looks online to Domotz - and therefore I can't wake it because the WOL button is greyed out. I have done some investigation. When the PC is in sleep, it does not return IP pings, but Domotz thinks it is still online. I presume that Domotz is doing a heartbeat check of the card at the MAC address level, and sleeping PC (and Mac) is passing this check. It seems there are three device states - powered off (you can't wake it), sleeping (you can wake it) and online. And Domotz can't identify the sleeping state for (new) PC and Mac? Would it be possible to modify the heartbeat check for PCs and Macs so they appear offline when they are sleeping? Thanks
×
×
  • Create New...