Search the Community
Showing results for tags 'agent webservice'.
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.
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. May 15th, 2019 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.14.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.5.0 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: Team Management: users can now better manage and have visibility on the list of team members created under their Team Leader account Improvements: Public API - Delete devices new endpoints: it is now possible to delete and hide devices directly using the Domotz Public API Public API - SNMP Community new endpoints: it is now possible to retrieve and edit community strings configured for each Domotz device directly using the Domotz Public API Portal Restyle - Add Agent: Domotz Portal have been redesigned to allow an easier understanding on how to add new Domotz Agents to the account Agent WebService - new landing page: local Agent landing page have been redesigned to allow new user to best navigate from the local Agent based WebService to the App and WebApp Agent Access Management: Team Leader accounts can now get the full list of users having access to a specific Domotz Agent Crestron PDU drivers: Crestron PDU PC-200 and PC-300 have been added to the list of supported drivers SoundUnited - 2019 device support: Denon and Marantz 2019 devices have been added to the list of supported ones Fix: Account history now shows failed and restored payment events Packedge PDU driver now logouts from the telnet session in order to avoid blocking the behavior Ruckus Zone director password management have been fixed Known limitations: Crestron PDU driver is triggered only when CTP port is enabled on the Crestron PDU 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 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