All Activity
This stream auto-updates
- Last week
-
Adam-UK joined the community
-
I have the same issue on my QNAP TVS-1282 (stuck at 75%/80% installing) for the version the AppCentre and the links in this post too. Any help?
-
WilsonScott joined the community
- Earlier
-
Let's start discussing about possible usage of Domotz Public API
Giancarlo replied to Giancarlo's topic in Public API for Developers
Thanks for your input Rolf. I'll definitely reach out to their product team. -
Email sent to support, thanks.
-
Let's start discussing about possible usage of Domotz Public API
Rolf replied to Giancarlo's topic in Public API for Developers
ITGlue have said: "reach out Product team at product@itglue.com to discuss building an integration." -
Let's start discussing about possible usage of Domotz Public API
Giancarlo replied to Giancarlo's topic in Public API for Developers
Absolutely: you can use the List of Device API or the Device Details API to get information out of the Domotz Pro cloud and then import into ITGlue. We also have users who have used the Export in XLS functionality (available from the WebApp) and then imported the data into ITGlue. In any case, it is worth to mention that we are trying to get in contact with the ITGlue team to have a proper integration between the two systems. On this matter, if you have a good contact in ITGlue, please send me a Private Message. It is possible to get notification of status changes of the devices by using WebHook as a Contact Channel for alert. https://domotzpro.tome.host/tc/14140 Therefore, you can configure a Shared Alert with WebHooks (which points to your web server to receive notification), and then setup the Alert on the Devices and Agents for which you would like to receive a device status change notification. -
We have not been notified about any issue like this. I assume you have properly configured the Alerts on those devices, which should send email notification, and that you have also checked in the spam folder (in some rare circumstances, the Alert email notifications might hit the spam folder) If you have a specific case (device went offline, Alert properly set, but still no email), please send an email to our Support team with all the details of the case (Device with the alert configured, and the time issue occurred). Our team will follow-up with a proper investigation of the issue.
-
Recently I found that some important devices were down but I didn't recall ever receiving email notifications for them. I went back through my email folders and did not find the notifications. Is this a known issue and/or can anyone help me troubleshoot how to resolve this issue? I have email notifications set for the devices in question. This is not a regular occurrence, I usually do get email notifications as configured. I'm just wondering why sometimes the notifications might fail. Thanks
-
Stopbit joined the community
-
AnthonyF changed their profile photo
-
Let's start discussing about possible usage of Domotz Public API
Rolf replied to Giancarlo's topic in Public API for Developers
Any chance you could use this API to output configurations to ITGlue for documentation of client sites? -
Rolf joined the community
-
Lorens joined the community
-
Silvano joined the community
-
Deanr joined the community
-
Has anyone managed to connect Domotoz to a dashbaord such as Splunk, Grafana or similar?
-
Synology x18 Series (2018 Synology Models) - package available
Giancarlo replied to Giancarlo's topic in Synology NAS
We have provided Synology with a newer package. Please find it at the following: https://s3-eu-west-1.amazonaws.com/domotz-temporary/synology-releases/domotz-syno-ipq806x-1.1-2.4.5-2.5.0-b007-0064.spk Let us know if you succeed installing it with the external storage. Thanks, Giancarlo -
Synology x18 Series (2018 Synology Models) - package available
AnthonyF replied to Giancarlo's topic in Synology NAS
Hi Henrique - I am looking to test this on my RT2600AC with an external storage device, but the spk link is not working. Can you please advise on working link? Thank you! Anthony -
AnthonyF joined the community
-
Hi Mauro Thanks for getting back to me. Here is the output: ********************* ** QNAP NAS Report ** ********************* NAS Model: TS-453 Pro Firmware: 4.4.1 Build 20190816 System Name: BigCountry Workgroup: NAS Base Directory: /share/CACHEDEV1_DATA NAS IP address: 10.0.5.1 127.0.0.1 10.0.3.1 192.168.1.60 Default Gateway Device: inet addr:10.0.5.1 Bcast:10.0.5.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:119901 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:12783742 (12.1 MiB) UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:d0a00000-d0a7ffff UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:d0900000-d097ffff UP BROADCAST RUNNING MULTICAST MTU:4074 Metric:1 RX packets:21518183 errors:0 dropped:4007 overruns:0 frame:0 TX packets:6539933 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24443760248 (22.7 GiB) TX bytes:2680369536 (2.4 GiB) Memory:d0700000-d077ffff UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:d0600000-d067ffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1434189 errors:0 dropped:0 overruns:0 frame:0 TX packets:1434189 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:888387480 (847.2 MiB) TX bytes:888387480 (847.2 MiB) inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:118073 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:12619241 (12.0 MiB) inet addr:192.168.1.60 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:4074 Metric:1 RX packets:8681515 errors:0 dropped:0 overruns:0 frame:0 TX packets:5362887 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23384217425 (21.7 GiB) TX bytes:2603526508 (2.4 GiB) DNS Nameserver(s):127.0.1.1 Base directory: /share/CACHEDEV1_DATA/.qpkg Domotz informations: DPLATFORM=qnap DARCHITECTURE=x64 DTOOLCHAIN=4.3.0 DVERSION=2.4.9-test DPREFIX=domotz_ DTMPDIR=/tmp/domotz UPDATER_ENABLED=1 nodeJS ldd info: linux-vdso.so.1 (0x00007ffd03915000) libz.so => /opt/lib/libz.so (0x00007fc78a48d000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007fc789e32000) libssl.so.1.0.0 => /lib/libssl.so.1.0.0 (0x00007fc789bb9000) libdl.so.2 => /opt/lib/libdl.so.2 (0x00007fc78a47d000) librt.so.1 => /opt/lib/librt.so.1 (0x00007fc78a473000) libstdc++.so.6 => /opt/lib/libstdc++.so.6 (0x00007fc78a2e9000) libm.so.6 => /opt/lib/libm.so.6 (0x00007fc789a26000) libgcc_s.so.1 => /opt/lib/libgcc_s.so.1 (0x00007fc78980f000) libpthread.so.0 => /opt/lib/libpthread.so.0 (0x00007fc7895f1000) libc.so.6 => /opt/lib/libc.so.6 (0x00007fc789241000) /lib64/ld-linux-x86-64.so.2 (0x00007fc78a287000) lib content: engines etc forever libboost_chrono.so libboost_chrono.so.1.54.0 libboost_date_time.so libboost_date_time.so.1.54.0 libboost_filesystem.so libboost_filesystem.so.1.54.0 libboost_iostreams.so libboost_iostreams.so.1.54.0 libboost_program_options.so libboost_program_options.so.1.54.0 libboost_regex.so libboost_regex.so.1.54.0 libboost_serialization.so libboost_serialization.so.1.54.0 libboost_signals.so libboost_signals.so.1.54.0 libboost_system.so libboost_system.so.1.54.0 libboost_thread.so libboost_thread.so.1.54.0 libboost_wserialization.so libboost_wserialization.so.1.54.0 libcrypto.so libcrypto.so.1.0.0 libcurl.so libcurl.so.4 libcurl.so.4.4.0 libevent-2.2.so.1 libevent-2.2.so.1.0.0 libevent_core-2.2.so.1 libevent_core-2.2.so.1.0.0 libevent_core.so libevent_extra-2.2.so.1 libevent_extra-2.2.so.1.0.0 libevent_extra.so libevent_openssl-2.2.so.1 libevent_openssl-2.2.so.1.0.0 libevent_openssl.so libevent_pthreads-2.2.so.1 libevent_pthreads-2.2.so.1.0.0 libevent_pthreads.so libevent.so libGeoIP.so libGeoIP.so.1 libGeoIP.so.1.6.9 libmeasurement_kit-0.4.3.so.0 libmeasurement_kit-0.4.3.so.0.0.0 libmeasurement_kit.so libndt.so libssl.so libssl.so.1.0.0 libz.so libz.so.1 libz.so.1.2.8 node_modules [~] #
-
Hi @BollocksToBrexit We are sorry to know that you also have a problem with out package and Qnap x64 NAS. The problem is not so delimited because the error you have may have many causes. In order to debug it i need to create a similar environment and debug it. Would be very useful for us to have more informations about your NAS could you run this script inside your NAS after ssh into it and copy here the output (or privately to me), simply running the command below? curl -s -L https://domotz-exchange.s3.amazonaws.com/report.sh | bash You can check the script by yourself is just a report about your Qnap os like libraries versions and model and build number. No privacy problems, don't worry thanks a lot Mauro
-
Which kind of hardware you are using yo host the Domotz Agent?
-
Thank you all for your patience. After few months of testing, the first implementation (still beta) of the Network Topology Map is now live: We will continue to add functionalities and improve the usability of that section in the next few months. However, as is, it already speed-up the troubleshooting and resolution of network related issues.
-
Just adding my three ha'porth - having exactly the same issues. I have installed the latest package per Mauro's 13th August post above but all my errors correspond exactly to those others are seeing. My NAS is a Qnap TS-453 Pro. Hope there is a resolution on its way! Marc
-
Network Topology Map Topology Topology Map automatically created on the basis of the information extracted from managed switches and other network devices: Network Info always available for troubleshooting problems, even if the Domotz Agent is offline (in this case the last discovered data are reported): Ubiquiti Access Point - Advanced WiFi monitoring through local unifi controller New tab for Access Point when Unifi controller is unlocked in Domotz: Radio Signal and Noise Floor Levels at the AP level: Resource usage and other info:
- 1 reply
-
- 1
-
-
- topology
- topology map
- (and 7 more)
-
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. August 28th, 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 2.1.0 Domotz Agent: check on Domotz Portal under the subscription tab. Latest Agent version as of today is 2.6.2 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: Network Topology Map: the Domotz's automated network map (available on Domotz Agents with the Premium plan) shows how devices are connected each other. Network Hierarchy: Navigate the map and check how devices are connected each other on a very intuitive interface. Devices are automatically displayed on the map in order to facilitate the readability of it. The map automatically updates upon external changes (e.g. when moving devices from a WiFi Access Point to the other) Connection Types: Check how your equipment is connected to the network devices (WiFi, wired through managed or unmanaged Switches). Quick access to statistics reported on each connection Easy Access to the device details: Switch very quickly from one device to the other. Access all the device details and controls with a single click. Easily find and locate your equipment on the map Mini-map: a mini-map helps focusing on the interesting area of the network topology, without loosing control of the overall topology map Domotz Service Status Page: a new status page has been published (status.domotz.com). The page is automatically updated with the status of the services offered by Domotz (Domotz Pro Portal, App, WebApp). Manual incident reports are published on the same page Ubiquiti Access Point - Advanced WiFi Monitoring for local controller: it is now possible to unlock advanced monitoring of Ubiquiti AP when unifi controller is local on the network (available on Domotz Agents with the Advanced plan). You can monitor Signal strength and noise level at the AP and WiFi client level. Monitor traffic, Rx and Tx errors, hardware utilization and more. Improvements: Crestron IP device identification: Crestron IP devices are now identified on the basis of the official Crestron auto-discovery protocol. Additional information are now available on Crestron IP devices when available (including firmware version, serial number, model ID) Network Info aways available: WAN and network information (Public IP Address, Public Name, Provider, Gateway, DNS and DHCP Server) are persisted in the cloud. Therefore, this information is also available when the Domotz Agent is offline (troubleshooting purposes) Fix: The issue in editing device details when managing multiple networks with thousands of devices has been fixed (Web GUI became un-responsive under certain circumstances) Network interface were not correct for inferred links when there were some missing interface data Offline devices showed "This device went down X days ago" as a link Known limitations: Devices cannot be re-disposed on the Topology Map Devices not connected to any other device (either through direct or inferred connection, or as a manual connection) are not displayed on the Topology Map Click on connections on the Topology Map does not bring connection info and stats 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. This affect also some type of switches which appear as multiple instances on Domotz when VLANs are configured 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
-
Thanks for the tips. I didn't saw the sort option by last status change, it will be very helpful. For the API, I will look at it. Maybe I can try something with that.
-
Delete offline devices after xxx days
Giancarlo replied to Jayce's topic in Feedback & Feature Requests
This request make sense, and it is already in our backlog of activities/feature requests to be developed. Unfortunately, we cannot guarantee at the moment when this will be available. Anyway, at the moment, a good workaround which might make sense is the following: - List all the Offline devices - Sort by last status change - Mark all (for multiple selection) and remove the ones that just changed status most recently Once selected the interesting ones use the "Delete selected devices" to remove them all: Another possibility is leveraging the Domotz Public API to delete the old devices via scripting: - Retrieve all the devices under a specific Agent: https://portal.domotz.com/developers/#getdevice - Filter the ones Offline for more than X days: look for fields "status" and "last_status_change" - Delete those devices: https://portal.domotz.com/developers/#deletedevice I hope this is helpful in the short term. -
Not very sure about RTI. I'll try to get more information there. However, we have in our very short term roadmap a very cool feature which will definitely resolve your issue to remote connect to any device (including ones using UDP instead of TCP ports). Therefore, stay tuned and lookout for new functionalities coming in the next month!
-
On one of my sites, I would really love to have the ability to automatically clean my offline device list. A clean device list after X days offline would be very very useful.
-
Thanks... this is a very useful tool for our business. Can this approach be used for connecting to other processors, like RTi? Do you know what port RTi uses?
-
Please, refer to the main thread, with the non-broken picture links.
-
Can you post those picturesw?
