All Activity
This stream auto-updates
- Yesterday
-
kkersten08 changed their profile photo
-
Other platforms that would be great to run domotz on
soloithz23 replied to System_Error_Message's topic in Unofficial Hardware Support
Has anyone tried to put domotz on a chrome box or chrome os hardware? Would it even be possible? - Last week
-
Riosoft changed their profile photo
-
afrisbie joined the community
-
Dave changed their profile photo
-
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. December 11th, 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.10 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of 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: Domotz Pro Public API - API Key: Domotz Users can now create and delete the API Key in order to use the Domotz Pro Public API. Documentation on the usage of the Domotz Pro public API available here. Domotz Pro Public API - Usage: The Domotz Pro Public API (RESTfull) provides developers an easy and comprehensive way to integrate third party applications with the Domotz Pro solution. Any user has 100 available API calls per day to retrieve the list of configured Domotz Agents or other useful information related to the Account. Moreover, each Agent configured under the Advanced Plan allows for an additional 500 API calls per day, and can be accessed through the Public API. It is possible to monitor the total usage of the Public API directly from the Portal (under Account -> API-Key session for further details). Ruckus Wireless - Access Network Edition support: the Access Network Wireless Controller (C210) and Access Points are now supported as part of the Wi-Fi Access Point Advanced Monitoring (signal strength, noise level, etc). Improvements: Domotz Pro App On-boarding: the latest Domotz Pro App allows the user to explore the benefit of using Domotz. It is also now possible to create new account (Sign-Up) directly from the App. Android Push Notification upgrade: Google Cloud Messaging have been replaced with the Firebase Cloud Messaging (FCM) technology to continue providing mobile push notifications as a contact channel for Android users. Device History Endpoint: Domotz Pro Public API have been enriched with the new endpoint to retrieve the History log of the device status. Network History Endpoint: Domotz Pro Public API have been enriched with the new endpoint to retrieve the History log of the network status. Device Recognition through Fing API 2.0: the device identification is now based on Fing API 2.0. The new API provides a much wider model and type identification, making the setup and configuration phase of a new Domotz Agent faster. Fix: Users with pre-paid Agents but not migrated to Subscription model do not receive the warning message on WebApp anymore 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 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
- Earlier
-
DeanB changed their profile photo
-
fbarcella joined the community
-
Psy changed their profile photo
-
I'd love to see SNMP v3 support added or at least backward compatibility to v1.
-
Hello, I need to give this another bump. For me the biggest failure of this unit at the moment is on the reporting side, and the consequent analysis possibility. 1. The inability to schedule reports, or that reports are automatically sent at the end of the month. 2. That the reports that you do get are limited in information. It tells you how many devices are connected, and if the agent is online or not It gives you 2 graphs of showing internet speed and latency It has a list of all the devices and when they were first seen. Considering it is supposed to be a report, it gives very little insight in to what is happening! No analytics! Your Monthly (consumer) Fing report gives already a lot more .. average Down/up speeds, uptime%, outages, specifically bad days of note One would expect on minimum the same info on your professional unit?!? 3. And there is no data for analysis, something to help spot issues! If not done on the server side, at least a way to get the raw data so that you can do it yourself... a particular device not responding to the pings regularly, An overview of the alerts sent during the month, Devices not identified properly, Access made via tcp tunneling. Is there any roadmap for this? For me this is a big shortfall of this unit. I am a person who likes visibility and insight, the ability to use data to make sure things a re performing at their maximum, and also to use the same data to demonstrate to the client that their system is looked after and when and why intervention was made and if there are any potential consequences! Looking for some positive development in this aspect. Thanks, Tim.
-
gilang changed their profile photo
-
Katodik joined the community
-
The feature has not been removed, but it is available only on the Domotz Box (whether it is a Luxul, Trendnet, Krika, Blackwire branded one). If you have a Domotz Box and the feature is not available, please contact support@domotz.com
-
radioactiveman joined the community
-
Did Domotz remove this feature. I don't have any ability to edit my networks from the Web GUI.
-
Cloggs joined the community
-
No, they are not connected to a wifi extender. Thanks for the reply, I will send the email. Marco
-
Hi @Synuser , Were these devices connected to a WiFi extender configured in bridge mode? If so, that's the problem. All IP addresses will respond using the same MAC Address (the device making the bridge). The Agent considers the MAC Address when identifying a device, all IPs should be listed in the WiFi Extender details if this is the case. Could you please send your Domotz account to support@domotz.com, we will investigate what is the cause for this problem. Kind regards, Henrique Salvador Domotz Support
-
Hi all, I installed Domotz on my Synology, it has found about 15 devices, however there are a lot that it did not find, like one of my samsung tablets, one of my phones, my ereader enz... When I add it manually by entering the ip adress of the device it tells me "This address is already monitored on your network" what is wrong here? Thanks for the help.
-
Synuser joined the community
-
Any good news, Qnap toolchain for Marvell architecture is very old (2013) , we have difficult to compile new version for this architecture, we hope we can give you good news asap.
-
Dominick changed their profile photo
-
Vitaly changed their profile photo
-
Any updates on the Marvell project Mauro?
-
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
-
-
- q-sys
- remote connection
- (and 2 more)
-
Seems nobody knows a good solution. For now I've configured each network interface to be a different VLAN and that works, but it means I'm limited to having Domotz monitor a max of 4 VLANs and I lose the ability to use the interfaces for something else (they were previously setup to enable a Sophos UTM VM on the QNAP). If anyone knows how to configure domotz on a QNAP to scan multiple networks through a single interface I'd love to try it out and move to that setup.
-
This has installed correctly. Thank you.
-
Appreciate it Mauro - this is an existing client we're looking to add functionality to, but it is not time sensitive.
-
Hi BlackBridgeSystems We are trying to identify the problem on Marvell package however we are quite sure that other architecture should work well. Could you have a try? in the meanwhile we are going to to try to solve the issue and keep you up to date. Thanks you and best regards
-
Mauro, thanks for the quick reply. The TS-419P II package installed correctly, however, when attempting to start fails with this error: [/share/MD0_DATA/.qpkg/domotz/var/log/domotz] # /etc/init.d/domotz.sh restart /sbin/getcfg: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /share/MD0_DATA/.qpkg/domotz/lib/libcrypto.so.1.0.0) +--- domotz is not running ---+ /sbin/getcfg: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /share/MD0_DATA/.qpkg/domotz/lib/libcrypto.so.1.0.0) /sbin/getcfg: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /share/MD0_DATA/.qpkg/domotz/lib/libcrypto.so.1.0.0) /sbin/getcfg: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /share/MD0_DATA/.qpkg/domotz/lib/libcrypto.so.1.0.0) domotz is disabled. And checking LDD gives: # ldd --version | grep ldd ldd (GNU libc) 2.5 Can you help with this error? I'll look at the other NAS shortly.
-
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
-
Reviving this topic as we've recently attempted to complete the install of the Domotz agent on two of our QNAP NAS devices - TS-419P II (4.3.3) and TS-469L (4.3.4) and both installs fail at exactly 80%. Upon investigation, both fail on the initial start of the Domotz agent. Tricky thing is, if the package install is cancelled in any way, it deletes the whole .qpkg/domotz directory and thus, all the logs. Manually installed and can now track the issue. On both installs, the service is hanging with this repetitive entry in the log file /share/MD0_DATA/.qpkg/domotz/var/log/domotz/domotz_status.log 2018-11-11 10:59:37 [2557] LOG: Waiting for port number in /tmp/domotz_listener.port The install/startup script is looking for the service to come up but it doesn't. The start up failed long before that and will never come up actually...no matter how long you leave it. Scrolling back up the log file finds two different errors which is clearly the source of the problem. TS-419P II 2018-11-11 10:58:54 [28263] LOG: Pid file doesn't exist, program probably stopped 2018-11-11 10:58:54 [28263] LOG: +--- Start domotz ---+ 2018-11-11 10:58:54 [28263] LOG: Link static content from /share/MD0_DATA/.qpkg/domotz/lib/node_modules/domotz-remote-pawn/data node: symbol lookup error: /opt/lib/libstdc++.so.6: undefined symbol: _ZNSt11__timepunctIcE2idE, version GLIBCXX_3.4 node: symbol lookup error: /opt/lib/libstdc++.so.6: undefined symbol: _ZNSt11__timepunctIcE2idE, version GLIBCXX_3.4 TS-469L 2018-11-11 10:41:49 [28044] LOG: Pid file doesn't exist, program probably stopped 2018-11-11 10:41:49 [28044] LOG: +--- Start domotz ---+ 2018-11-11 10:41:49 [28044] LOG: Link static content from /share/MD0_DATA/.qpkg/domotz/lib/node_modules/domotz-remote-pawn/data node: relocation error: /opt/lib/libpthread.so.0: symbol __tunable_get_val, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference In the case of the TS-419P II, the linked library is there, executable, and permissions allow access to the file lrwxrwxrwx 1 admin administ 19 Feb 11 2017 /opt/lib/libstdc++.so.6 -> libstdc++.so.6.0.21* In the case of the TS-469L, the file does not exist on the NAS. Any help would be much appreciated.
-
Hi @TaylorSystems, Sometimes our Installer will not be able to check if the Virtualization is enabled or not in the system, usually when you already have a virtualization system installed. You can check this by running this command: systeminfo The output should be like this for our installer validate the virtualization support: The Domotz Agent Windows installer create a Virtual Box instance running an VM with the Agent. If you already have a virtualization environment on your system the best would be to add our image to the current environment. The latest version of the image is always available in this JSON file: https://portal.domotz.com/assets/ubuntu-domotz-agent.json This image is similar to the Windows Installer. We are working on a version of the Agent native for Windows that should be available in Q2 next year. Please do not hesitate to contact our support (support@domotz.com) if you have any problems installing the Domotz Agent Windows installer or importing it to your current environment. Kind regards, Henrique Salvador Domotz Support
-
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. November 14th, 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.7 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: WyreStorm NetworkHD deep discovery: Domotz now discover WyreStorm's award-winning NetworkHD controller on the scanned network (NHD-000-CTL). Thanks to a new recognition methodology, all the receivers and transmitters are automatically discovered by Domotz even if configured on a different VLAN/Subnet WyreStorm NetworkHD enhanced recognition: A new Domotz Pro Tile and menu entry, gives access to a new set of features specifically designed for WyreStorm. The following information are available directly on Domotz Pro: o Device Network Configuration o Device resource usage (CPU and Memory) o Firmware version o Model identifier o Audio/Video Settings/Status (timing, format, rate, bitrate, fps, HDCP, EDID, etc) o Streaming data o Encoder (TX) / Decoder (RX) - topology graph o Command to Reboot o Command to Factory Reset the device Domotz Pro Public API: documentation and example for using the Domotz Pro Public API are now available online on the Porta Improvements: SNMP OiD allowed length has been increased: this allow the configuration of very long OiD available in custom MIB Windows Domotz Agent Manager - VM as service: the latest version of the Windows Domotz Agent Manager now configure the VM as a "service" for the service, allowing the Domotz Agent to start as soon as the host starts, without requiring credentials of the user to be used (version 1.1.0) Ubuntu 16.04/18.04 Agent available on Portal: the latest version of the Domotz Agent (in SNAP package) is now listed directly in the Portal as a supported version Fix: External monitoring of public and private subnets when running on Raspberry Pi have been fixed Ruckus Controller (v10+) text body limits the AP results and inconsistency Ubiquiti EdgeSwitch PoE ports toggle may not appear for some devices 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 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
-
I recently purchased the Domotz PRO subscription for a year. I downloaded the Windows 10 Agent Manager software and installed it. I received the message that: "Domotz Requires Virtualization and that the virtualization option was not enabled on my hardware". I restarted my system and went into the BIOS and found that Virtualization IS ENABLED for my system. Anyone else run into this or have a solution?
-
Domotz Agent Manager for Windows - Available to be downloaded
Giancarlo posted a topic in Windows Host
We are glad to announce that we have completed the development of the first production version of our Domotz Agent Manager for Windows. It has been completely tested on Windows 10, but it should work also on Windows 8 and Windows 7. You can download the Agent directly from the Domotz Portal, under the Domotz Software tab. Note that the application will install an Oracle VM VirtualBox (if not installed yet) and it will download the proper image which contains the Domotz Software. Virtualization option is required to be enabled on the hardware. It is highly discouraged to use the Domotz Agent Manager for Windows in an already virtualized environment. -
Just a quick update on this thread. With the rollout of the subscription monthly model, any new user will be able to configure and run as many Domotz Agent as he/she wants during the Trial period, and the Trial is not limited to the Standard plan anymore.
-
Hi Chris, the Domotz Pro agent only requires outgoing connections to be available on the Firewall. Most of the connections are on HTTPS (port 443, which are usually enabled by default), but some services (required to perform remote connections or command to the Domotz Agent) are on different SSL secure channel. For a complete list of required outgoing ports to be available, please have a look at the following FAQ: https://www.domotz.com/ufaqs/need-configure-firewall I hope this helps.
(1)(1)(1)(1)(1)(1).jpg.7dcdeb3fb90919aa2df390a4f448ac4b.thumb.jpg.77bf24b1396f1fd80d63b164713f41ff.jpg)
