Jump to content

Leaderboard

The search index is currently processing. Leaderboard results may not be complete.

Popular Content

Showing content with the highest reputation since 05/14/2020 in all areas

  1. Thanks for this question Daniel. The activation for that second method is relatively easy. Just activate the agent before sending the unit to your customer please do the following: 1. Plug the Domotz Box your office network as you normally do at the customer site. 2. During activation with the Domotz Pro app make sure that only one Domotz Box not configured at a time is connected to the local network or it will be difficult to know which one is being activated. You have also the option to access the Domotz Box port 3000 through a browser. Tip: Double check the unit you are sending to the remote site are the same by matching the MAC Address from the Portal and the one at the bottom of the unit: 3. To fix the agent location at the map go to Mobile App or WebApp, select the Agent --> Customer Management tile --> Agent Location: Enter your customer's address in this field. 4. Once the unit appears at the Portal and it is connected and online for at least 10 minutes (enough to install the latest updates). Disconnect it from the network and ship it to the remote site. 5. Once you customer connects the unit to their network and it is shown as Online at the Portal, execute the agent cleanup to remove any data discovered from your office: From the Portal > Subscriptions tab click at Edit button next to the Agent and then Cleanup Agent Data: That is it, doing so you should have no problem.
    2 points
  2. Hello, An additional field I would like to request is an ASSET number field, or a database reference field. I use this field to cross reference between inventory lists, drawings and other device identifying functions. Something that is unique to each device and seen in the exported excel sheet, and that I can adjust to my internal inventorying system. Thanks, Tim.
    2 points
  3. Hello Motech, I apologize for my late response to your comments here. As one of the product owners at Domotz, we always appreciate productive feedback. Your four bullet points are clearly around the User Interface and Rebooting of devices. We are continuing to invest time into the Domotz Dashboard and our team is currently building out the infrastructure to make these changes. Our current plan is to have a complete overhaul of our UI by the end of the year. Addressing a few of your comments specifically; 1) There are multiple ways of rebooting devices in our UI, whether through the PDU/Managed Switch device page, or the device itself. I agree that elevating power management to a tile is a good way to simplify the UI further. 2) Please note that our APIs are cloud-based and therefore you can leverage a PC in your office to control all you clients. There is no need for an onsite device to run the APIs and scripts. I'd like to better understand your need for scheduled reboots more. Unless there are fundamental issues with a device, there should not be a need to reboot a device on a regular basis. Maybe I am missing something in your set-up and services that could help me better realize the need for this. 3) Regarding the client facing app, we have found that many people did not leverage Violet version 1 or version 2 that we developed, therefore we chose to minimize the development efforts associated with this. That said, it is on our roadmap to create these macro behaviors that you're suggesting here. We have found, especially with Crestron, that dealers leverage the Domotz APIs to build out macros in control system interface. I'd like to better understand some of the needs when you say "reboot network" or "reboot Crestron". If you have more details on what is means to reboot Crestron, we can get a better idea of how we can help. 4) Under the reports and logging tile, you can see when a device was rebooted and who initiated that action. This capability has been there for several years now. I'd be happy to walk you through this on a zoom meeting if that would help. Domotz is primarily a monitoring tool and service for secure, remote connectivity to network based systems. Rebooting of devices is actually a secondary aspect of the service that we provide, as many people recognize power cycling as a management method. Our team has done a great job making sure that we work with many different major manufacturers to provide a common UI across different PDUs and managed switches to ensure this secondary functionality is possible. Have you reached out to our team directly with your feedback? Given the anonymity of forums, I'm not sure if we have personally spoken about some of your concerns. I'd be happy to have a call with you so you can expand on some of these points you are making and allow you to articulate why your findings about Domotz are negative. I'll also get with the head of residential systems at Crestron to better understand the feedback he is getting regarding Domotz and the Crestron platforms to find out how we can improve. Let's set up a time together to discuss this. Feel free to reach out to me directly with times you are available, if it makes sense to have the Crestron team involved, we can invite them too. Regards, J.B. Fowler jb@domotz.com
    2 points
  4. 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
    2 points
  5. I'm with MarkB on this, do you have a roadmap or plan to extend the Network Statistics for interfaces to the API? Would it be better for us to generate Eyes on the Oid's and interfaces we want to monitor specifically? I write custom reporting / dashboards for our customers, and I integrate with other TimeSeries databases, and it would be nice to have this be able to dump into my Database, where I could then graph that historical data with tools like Grafana, or my own custom JS without having to expose the Domotz. It's great to have one tool actually doing the snmp scraping to keep device load down.Thanks for a clean product!
    2 points
  6. Hi All, Here you can find a link to Download our Hyper-V prebuilt image based on Ubuntu Server 20.04: https://domotz-vm-images-temp.s3-eu-west-1.amazonaws.com/Ubuntu_20.04_Domotz_Agent_2.5.9-3.1.0-b001_HyperV.zip To import the image and activate the agent do the following: 1. Open the Hyper-V Manager > Click on Action > Import Virtual Machine...: 2. Select the folder where you Downloaded and extracted the Image above: 3. Select the VM found: 4. Import it using a new unique ID: 5. Select the place where you want to save the VM and its virtual Disk: 6. Click on finish. 7. Once the VM is imported make sure the VM is connected to the correct virtual switch configured in bridge mode, so the VM will get a valid IP Address on the network: 8. Start the VM. To login and see the current IP address use the following credentials: User: domotz Password: domotz 9. At the command prompt run command "ifconfig", the current IP Address will be shown. 10. Activate the agent from a browser access the VM IP address on its port 3000 (e.g. http://192.168.1.104:3000). If you need assistance, please do not hesitate to answer to this thread or contact our Support team: support@domotz.com. Henrique Salvador Domotz Support
    1 point
  7. Just updating this very old post It is possible to rename a Domotz Agent from two different places: Domotz Portal (https://portal.domotz.com), click on Subscriptions then Edit the Agent and update the name of the Agent. From the App or WebApp (https://portal.domotz.com/webapp), select the Agent, then "Customer Management", and then edit the name of the Agent
    1 point
  8. Hi Tubblog, thanks for posting your questions on the Community Forum. Let me address both of your questions: No side effects in having 2 Domotz Agents on the same network. Consider that in some of our labs, we have tens of Agents running concurrently on the same network The two Domotz Agents will run separately (there is not yet a concept of "merging" data from two different Domotz Agents). Therefore, if one of the two Agents (or the machine hosting it) fails, you will have the second one which continues to allow you monitoring and managing your network from remote.
    1 point
  9. We're big fans of Domotz and it's been great to see so many useful features added over the last couple of years. The development of the API is great for those with the expertise and resources to tailor their own solutions, but there are some improvements to the out of the box notifications and device statuses that would be a real help. It's great to see that one of these, nested devices, is already on the roadmap. This will help reduce a lot of unnecessary notifications being generated simultaneously (NVR + cameras, network switch + connected devices etc). There are 3 other suggestions that would make things a lot more useable: Flagging offline devices as known issues - The majority of our sites have at least one offline device awaiting a service visit to resolve. Depending on the distance to site, outstanding payments etc, these can hang around for a long time, meaning most of our sites are showing Issues/Yellow at any given time. This makes it very difficult to spot sites with new issues at a glance of the dashboard. Would be great if we could tag these devices so the site shows as Healthy/Green but with offline devices (or by some other means). Reduce recurrent alerts - We regularly receive multiple (sometimes 50+) alerts overnight from a single site in everyone's inbox because of an issue with a device that is alternating between online and offline. Would be great to have a way to limit the alerts generated within a specified timeframe because several times we have cleared these from our inbox and missed a unique notification in the process. Schedule Notification Delivery - We currently use 2 classifications for our alerts, Critical and Important, but they all currently generate real-time alerts 24/7. During business hours it's useful to know if the less important devices go down, but out of hours this generates a lot of alerts on sites that don't necessarily have service contracts covering this period. It would be great if we could configure shared alerts that only generate within specific time periods. Thanks, Tom
    1 point
  10. This is a new capability offered by Domotz (September 2020). It is now possible to search for a specific OID by searching about a keyword within the available MIBs loaded within Domotz. Domotz automatically scans on the network for all the devices that offer SNMP capabilities. When Domotz can read SNMP values out of a devices (SNMP version and authentication match between Domotz and the device), Domotz will identify all the possible MIBs available for that specific device. The attached file is the current list of all available MIBs which can be searched through Domotz. We will add more and more MIBs to the following list. Please feel free to provide us with either public or private MIBs you would like to see available into Domotz. Just drop an email to support@domotz.com for this purpose. For example, if a device supports one of the following MIBs, when adding SNMP monitoring through Domotz (EYEs), you will be able to search among all the possible values: -- Updated list of supported MIBs [2021-04-05]: Domotz_MIBs_Available_20210405.xlsx -- You can check for a practical usage of SNMP through Domotz in this Blog Post: Guide to Server Room Temperature Monitoring using SNMP sensors Domotz_MIBs_Available_20210405.xlsx Domotz_MIBs_Available_20200902.xlsx
    1 point
  11. I'm starting this thread, because very often we have been asked (either during demos, presentations or via Support) "how to configure a new Domotz Agent without being physically on the same network". Let's start with a couple of definitions. The Domotz Agent is the software which needs to run locally to a network. It is the software that scans and monitor that network, and reports the data to the Domotz Cloud. Let's say that it is a sort of proxy. The Domotz Agent requires a physical hardware to be connected to that network. It can be a simple Virtual Machine (within a physical server), a Windows PC or Server (our installer at the moment creates a VM within that), a Linux PC or Server, a NAS drive (such as Synology, QNAP, ReadyNAS, etc), a maker-board (such as a Raspberry Pi, a BeagleBone Black, Banana Pi, Orange Pi, etc), or the Domotz Box (which is basically a sort of maker board with steroids, and comes with the Domotz Agent pre-installed). You might get already familiar to configuring new Domotz Agents when you are local to the network. It is quite easy with the usage of the Domotz Mobile App. Or if you know the IP address of the physical hardware hosting the Domotz Agent, just connect to its port 3000. E.g. assuming the Domotz Agent runs on a server with IP 10.10.100.125, just connect to the following: http://10.10.100.125:3000 When you install the Domotz Agent on a NAS, on a Windows or Linux PC or server, you are also guided to that WebPage to configure the Agent. However, the question is: "How can I install a new Domotz Agent, without being on the same physical network?" There are at least three ways of doing it: 1. Virtual Connection to the network Let's assume you have a network where you can have a remote access to a PC, VM, or Linux Server. In this case, it is relatively easy to install the Domotz Agent on that machine (either physical or virtual) and then connect to its port 3000 to configure the Domotz Agent. A usual scenario is when there is already a PC remote in that location, where you usually connects using tools like TeamViewer, GoToMyPC, etc. Well, you can install and configure the Domotz Agent on that same PC, using that same TeamViewer or GoToMyPC, and the job is done. Using that connection, you can connect to the page 3000 on the localhost (e.g. http://127.0.0.1:3000) In other cases, you might have already a VPN in place, which you can use to access to an existing hardware on that remote location (including a NAS drive). In this case, you can connect to the physical hardware to host the Domotz Agent and then to its port 3000 to configure it. Once your new Domotz Box is onsite, you can simply sweep out the data already recorded by the Agent (by scanning your office network), and it will start from scratch in its new location (you can do this in the Portal). You can also change the location of the site (within the Customer Management data of that Agent). Easy, no? 2. Usage of a Domotz Box In case you have no pre-existing access to the remote network, and you only need Domotz into that remote location, you can choose to ship a Domotz Box to your customer. Pre-configure it in your office, and then ship to your customer. Your customer will only need to connect to the power and network, and job is done. This approach has been chosen by Krystal Burger - IT team. They preconfigured more than 250 Boxes in their IT office (one single location), and then they shipped all those boxes to their restaurants around US. It has been a relatively easy and fast job for the Restaurant Manager just to plug-in that Box to one of the available switch ports. Job done. All the different fast-food sites under remote monitoring in few days, no travel and a lot of savings for the IT department of that fast-food chain. 3. Prepare the hardware in the Office and ship to your customers Still in the case you have no pre-existing access to the remote network, and you don't want to use a Domotz Box, one easy job is to prepare one physical device in your Office, pre-configure the Domotz Agent, and then ship that hardware to your customer. It will be your customer's responsibility only to power it and connect to the first available ethernet port (either on the Router or on the Switch). You can choose the hardware of your preference. If you are already thinking of providing your customer with a NAS drive, choose one that support Domotz Agent. Configure it in the office, and ship to your customer. If you are willing to use that same hardware for other scripts or something, configure a maker board (or even better a NUC) with the Domotz Agent and ship to your customer. This approach has been also the choice of an anonymous MSP, which was required to supervision the migration of technology on a ~40 different oil production sites around the world. He prepared all the Domotz Agents in his office, and he shipped around the world. In less than 15 days he had all his site under constant monitoring, and he was able to monitor and conduct the migration of technology for all of them, without stepping out of his office. Can you imagine the savings generated by this smart idea? Once your new Domotz Agent is onsite, you can simply sweep out the previous data it recorded (by scanning your office network), and it will start from scratch in its new location (you can do this in the Portal). You can also change the location of the site (within the Customer Management data of that Agent). -- Please comment here below with your personal ways of ideas on how to further optimize this process.
    1 point
  12. Domotz is mainly a tool for IT Professionals, MSP and System Integrators in general. It provides a complete Remote Network Monitoring and Management solution for multiple networks at a very reasonable price: all the professional tools and services with a similar set of functionalities cost much more than Domotz. On the other hand, we also have multiple personal users which are fine with the cost of Domotz for the functionalities offered by the tool. For learning more about that, please do not hesitate to contact us directly at support@domotz.com
    1 point
  13. Postman can be used to test any REST API, it is an easy-to-use client with powerful features. You can use it to create a collection of methods for calling the Domotz API. Once started, just click into the 'Import' button and choose 'Link' then insert the following URL: https://api-us-east-1-cell-1.domotz.com/public-api/v1/meta/open-api-definition (or https://api-eu-west-1-cell-1.domotz.com/public-api/v1/meta/open-api-definition if you are not located in North America). A new 'Domotz Public API' collection will be created: for using it you need your API key. My suggestion is to create a new variable (right-click on 'Domotz Public API'->Edit->Variables), let's call it 'api_key', and use a reference to it - ${{api_key}} - in the rest of the collection. You'll need to copy ${{api_key}} as the value of the header 'X-API-Key' in all the methods you want to use: once finished you can save your collection so that you can test it with different API keys by just change the variable value.
    1 point
  14. Perfect, Thanks for your help 🙂
    1 point
  15. Hi, we appreciate your recommendations and suggestions. As a matter of fact, the following two features are on our roadmap, and they might address your needs: 1. Possibility to group "entities" in a single device: basically the possibility to tell the system that 2 or more MAC addresses belong to the physical device. This should address your first concern 2. Parent-child relationship for alerts: basically the possibility to configure the system so that if a "parent" goes down, you receive one single Alert. Thanks for your continuous interest in Domotz and keeping suggestion coming. Best regards, Giancarlo
    1 point
  16. this is a very good idea. At the moment, it is possible to be notified if there is a NEW device (in general) connecting to a specified Network, but it does not allow to filter on the OS. So, my recommendation is that on a specific network, where you only expect a certain list of devices connected, you set that Alert so that you are notified as soon as a New Device connects to it. Then you will need to check the OS of that new device. We will take your suggestion as a feature request.
    1 point
  17. I'm writing this out of frustration, because i really want to use DOMOTZ, but we cant. We are an AV firm out of NYC, we do around $250k a year with crestron, so we arent small. Until domotz can do these things then its not for us: make it easier to reboot things, currently it takes several taps to get to what we want to reboot. Instead you should make a TILE on the front page that lets you get to all your rebootable devices quickly, and on that note, since you can also reboot POE devices, make a filter that shows just 120v, just POE, and all together. schedule reboots of PDU outlets and of POE ports (without scripting, we are paying monthly and yearly for this service, and we arent going to install a 2nd device on each site to script these things) an easier client side app that just lets clients reboot things based on what we allow them to, and in groups. So the client see a few buttons like "Reboot Cable" "Reboot Crestron" Reboot Network" but behind the scenes those are actually macros that reboot several things at once (this is one of the most important features and is the MAIN deal breaker for why we cant use this, compared to say, OVRC) A reboot log, this may already exist but i cant find it. If i reboot something, i want to see a log that it was done, and which user initiated it We bought a few DOMOTOZ units from crestron with a year of service and we are so disappointed with them. 1 at my personal system and 2 at 2 different large clients. They are useless to us. We currently use OVRC with Wattboxes, and we arent a huge fan of the hardware and are looknig to get away. The problem is the OVRC app is significanly more useful for the AV industry. DOMOTZ has the ability to replace OVRC for us, but so far every request we ever made has been met with a version of "we might get to this eventually maybe" I hope this helps other AV companies out there, and I hope DOMOTZ listens to this feedback if they really want to be useful to us. I'm posting this in a few different places ,and i already let the head of residential systems at crestron know our feelings about DOMOTOZ.
    1 point
  18. 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
    1 point
  19. Apologies - I see the ability to create custom alerts per device.
    1 point
  20. Giancarlo After some tweaking, things seems back to "normalcy". I can not say for sure, but culprit so far seems QNAP "Virtual Switch", which was automatically created and for long giving me difficulties (now deleted). Thank you once again for your support. Besides difficulties, I learned a bit further on agent cleanup, reset, etc... Best, Xant
    1 point
  21. We configure networks with multiple VLANs at our clients and one of the most frustrating aspects of deploying domotz is adding additional VLANs because it requires static IPs for each VLAN. And each time you add a VLAN, it restarts the network an sometimes fails or corrupts the native VLAN1 config for domotz by changing the default gateway. I have made a feature request (using a different account) to have the option of DHCP on the additional VLANs but this has not be incorporated as of yet. Please add DHCP, as this would greatly ease in our particular deployments and I imagine for others.
    1 point
  22. Not at the moment. However we have this in our backlog of features to be developed.
    1 point
  23. Following along with that.. we deploy Domotz on Raspberry Pis for all our clients and they usually sit in racks. I connect a DHT11 temp/humidity sensor on it and did some snmp scripts so it can be polled regularly. Cost of the sensor is usually less than $5. If you don't want to build your own Pi, investigate what Giancarlo show above. It can help provide some insight into possible failures in clients systems.
    1 point
  24. I have used the API to set up InfluxDB with Grafana to log and graph long term trends of our internet speed tests past the 1 month data retention you have. Plus use the Grafana dashboard to show key information at a glance. It would be great to extend the API to allow reading traffic history of select interfaces on devices in the same way we can query 'getspeedtesthistory'. For example; to log the throughput of a firewalls WAN interface or a core switch. Happy to test any beta API's Keep up the great work;
    1 point
  25. Yes, you are able to migrate you Windows agent to a Domotz Box. For that you will need to send to support@domotz.com the following info: Agent Name: Windows Agent MAC Address: Domotz Box MAC Address: Note that whenever you are ready to migrate, your current agent will need to be offline before the support team can do so. Fore more information, please feel free to refer to the following FAQ: How Do I Move my Domotz Agent to New Hardware Without Losing My Configuration?
    1 point
  26. Great suggestion! Those features would be super helpful with switches that either do not have a GUI management interface or do not have the Web GUI enabled. I like the way you think!
    1 point
  27. Sometimes happens to connect to the home network misconfigured devices or other appliances that have an active DHCP server on board. This creates confusion and malfunctions. Is it possible to detect unwanted DHCP servers? It would be enough sending a DHCP discover packet from time to time and check the MAC address from which come the answer (DHCP offer).
    1 point
×
×
  • Create New...