Jump to content
Monthly Subscriptions Are Here Read more... ×

Leaderboard

  1. Silvio

    Silvio

    Staff


    • Points

      27

    • Content Count

      280


  2. Giancarlo

    Giancarlo

    Staff


    • Points

      27

    • Content Count

      377


  3. fillibar

    fillibar

    Members


    • Points

      16

    • Content Count

      75


  4. LFalkenburg

    LFalkenburg

    Members


    • Points

      12

    • Content Count

      20



Popular Content

Showing content with the highest reputation since 09/14/2015 in all areas

  1. 8 points
    Would be great to see two factor enabled for the Domotz apps and web portal - especially since this gives remote access to my network...
  2. 4 points
    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.
  3. 3 points
    Please see attached for a ready compiled version of the RDP wrapper. To install, unzip the file, run install.bat followed by update.bat. You can then run RDPConf to make sure everything is working, all the text should be green. If the included RDPCheck takes you to a Windows login screen, you should be able to use the RDP Wrapper with the Remote Desktop option under Connect in the Domotz mobile apps or web app. Note: You might have to disable Allow Remote Assistance in Windows before the RDP wrapper allows RDP connections. We can't guarantee that this works with all versions of Windows, but it's worth giving it a try if the version you have doesn't support Remote Desktop connectivity. We've tested on Windows Vista, Windows 8 and Windows 10 and have successfully made it work. RDPWrap-v1.6.zip
  4. 3 points
    Hi, I have been meaning to make this post for a while now, but now I'm finally doing it Over the years I have been involved in a lot of betas for both hardware and software and I have to say this is probably the best run beta I have been in. The product was almost a finished product before it even got to the beta stage. However, the best part of this beta has been the staff. You guys have first hand knowledge of the product, are involved with the direction it is going, respond to every post on the forums, and answer every email. So with that said, Lars, Giancarlo, and Silvio give yourselves a pat on the back for a job well done.
  5. 2 points
    I actually prefer the PerfSonar system to be honest- those of you saying you get repeatable results should consider what you are saying. Is it really your belief that a broadband trunk will have the same response at 6pm as it will at 4am. These are like Highways and there will always be traffic at certain points that will cause congestion and variances. If you are not seeing these it is likely that the test is not a legitimate implementation, and is perhaps skewed as may be the case in both OOkla and speedtest.net who are both receiving large amounts of advertising funds from a few large players. Now I would never insinuate that a company that survives off of advertising funds would ever skew reports about connectivity results from their key clients as that would be inappropriate and completely unheard of in life in general. Just in comparison PerfSonar is an implementation of a truly pure and scientific Link quality and bandpass test that is directed towards and managed by purely scientific organizations that do not operate off any type of advertising blood money. I will say I was amazed at the quality and predictable results of my tests run by OOKla on the Comcast network despite getting significantly contradictory findings in both Speedof.me and personal experience. Lastly Dsl reports does seem to have updated their speedtest and it appears to be a genuine implementation of a tool, however great care was taken to shield the operation from prying eyes so there is little way to know the true nuts and bolts of the operation. It is clear that most the test legs are not hosted by Dsl reports but thats not anything of much concern as who wants to own a data center just to provide a speed test. Besides the key is to vary your test vectors and targets to get clear picture of the issue, which again is a good reason to stick with PerfSonar. Ok so besides counting myself as a backyard scientist and having fun with DryIce I have no connection to PerfSonar I just like their scientific roots. Ok so thats my vote thanks for reading. Last thought, If my doctor told me he saw a dark spot on my chest Xray while I would hope for a smudge if it appeared in 4 successive Xrays at other doctors I would stop blaming the Xray and start chemo --point being the indication is theirs a bad network issue in the Canadian border region, amazingly a tap point for certain state level players, why are we blaming perfsonar again and the customers not complaining to the Broadband providers???
  6. 2 points
    This is a trivial thing to do if you are using a Raspberry Pi. Just install a DynDNS updater. sudo apt-get install ddclient I've got this running on all of mine and it works great, even on a double NAT'ed situation.
  7. 2 points
    The install and running of the Agent on the BeagleBone Black (Rev C using bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img) went without any problems.
  8. 2 points
    Here is some feedback on the v0.9.4-b008 Android App: 1) I like the new dashboard. Brings a bunch of key pieces right to the front. 2) Will the "tiles" be able to be rearranged? 3) For the Devices tile. Would it be possible to move the # of devices so it is inline with the Devices tile label? That way you see you have (in my case) 37 devices total. Then break out the online and offline below that instead of having the total devices and number of online ones. 4) Network tile opens to the Route Analysis but the information it shows as the default is the Speed Test. So it would be better if it opened up the Speed Test. 5) The speed test data only remains on the Network tile until the app is shut down and cleared from memory. Could it retain the last time run maybe with an "as of X days ago"? 6) Something is odd with Alerts. I had 2 custom alerts but one was for an Arduino I no longer need (came up with a better temp/humidity sensor based on a Photon). When I cleared the alert out and saved it it still shows in the alert list as having an alert. The Alerts tile shows me as having 2 custom. But going back into the device alert shows it is blank (nothing there). 7) The Collaboration and Help tiles need to be brought so they are all on the initial screen. Not sure if all the tiles need to be made a bit smaller or what, but I did not even realize there was a Guests number and a Documentation area for them that I could see if I scrolled down. So I guess that leaves a bit of interface training for the user. Either change the layout so all tiles (6 total) show completely on the screen or add a scroll bar when they extend past it. That would allow users (if/when tiles are customizable) to add even more but risks getting a bit sloppy.
  9. 2 points
    Just an update to say that the problem was fixed by an update to the domotz agent with help provided by Giancarlo. Must say that I'm impressed with the quick responses and problem resolution. Thanks!
  10. 1 point
    I turned on my Orvibo S20 power switch using its domotz config tab, now I cannot turn it off. Each time I do that, it attempts to go "Off", then goes back to the "On" position with the following message: " Unable to toggle port 1 The port didn't respond within the expected time." The S20 switch is actually (physically) turned off each time I attempt to turn it off this way, so maybe the config interface timed out faster than the response. Orvibo's Wiwo app on iPhone shows the correct state of the S20 switch though. Another observation: I have the S20 switch set to auto off at 10:30pm, scheduled in Wiwo app, but it seems that the domotz "On" setting might have prevented it from going off at the scheduled time last night, so I manually switched it off using Wiwo app. Will monitor further. Edit: Second issue was due to incorrect timer setting on Wiwo app, please ignore that.
  11. 1 point
    Configuring Multi-VLAN support for Remote Network Monitoring with Domotz Pro Domotz Pro is a remote network monitoring software which supports multi-VLAN configurations for remote network and device monitoring. The software which is designed for integration companies and IT professionals enables a host of network monitoring features including: Remote Access, Remote Power Management, Network Mapping, SNMP, Alerts, Network Diagnostics and more. Read more about Domotz’s Remote Network Monitoring Features. Domotz supports monitoring of multi-VLAN network configuration through a variety of network installation options which include: Self Installation on a Raspberry Pi (i.e. your own Raspberry Pi device) or via the Domotz Box or Domotz Pi which are available for purchasing from the Domotz Portal. This post will explain how to configure mutli-VLAN support via your own self-installed Raspberry Pi device. Configuring Multi-VLAN support on a Self-Installed Raspberry Pi device for Remote Monitoring Starting from Package version 1.03-201(April 2016) of the Domotz Agent for Raspberry Pi, the full package can be installed on your own Raspberry Pi device and supports the discovery and monitoring of devices hosted on two or more VLANs accessible from the Raspberry Pi. (Instructions and latest package are available here https://portal.domotz.com/portal/hardware/instructions/raspberry) This short guide is meant for users who have multiple VLAN and are already aware of related configuration and procedures. For further details, and step by step guides, on how to configure VLANs on Switches and Raspberry Pi, the user should refer to detailed guides (for example, please refer to: http://www.sbprojects.com/projects/raspberrypi/vlan.php). In order to allow the Domotz to discover and monitor devices on two or more VLANs, the user should configure both the Switch and the Raspberry Pi to multiple VLANs: Switch Configuration The interface port of the switch which will be used to connect the Raspberry Pi, should be configured: - in Access mode / Untagged for the main interface used by the Raspberry to communicate with the gateway (e.g. eth0). - in Trunk 802.1q mode / Tagged for the additional VLANs to be monitored (e.g. the eth0.10 used for lan 10) Please, refer to your specific switch/model guide on how to configure Trunk 802.1q and Access mode (Untagged/Tagged) for the port. Raspberry Pi Configuration In order to configure the Raspberry Pi to access both the main and VLAN interfaces, execute the following steps: 1. Install vlan package and configure moduels: sudo apt-get install vlan sudo su echo 8021q >> /etc/modules exit 2. Open with your favorite text editor /etc/network/interfaces and configure the Network Interface to access the main and VLANs. E.g. if we have a primary network on 192.168.5.0/24 (DHCP) and a secondary VLAN 10 on network 192.168.100.0/24 (Static IP: 192.168.100.200): auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet dhcp post-up ifup eth0.10 iface eth0.10 inet static address 192.168.100.200 netmask 255.255.255.0 In bold the part of the configuration due to the VLAN support, if you are using the Stretch version please see bellow the additional steps. 3. Restart the Raspberry Pi Stretch Additional Steps For the new version of Raspbian (Stretch) the "post-up" has no more effect, for this version please do the following: 1 - Create a file “vlans” in /etc/network/if-up.d/: $sudo nano /etc/network/if-up.d/vlans 2 - Add the following to it: #!/bin/sh ifup eth0.10 3 - Make the file executable: $sudo chmod 755 /etc/network/if-up.d/vlans 4 - Reboot the Agent, the interface eth0.10 should be up automatically now. Further reading about Domotz Pro: · Remote Network Monitoring Features · Pricing · Remote Network Management Installation Options
  12. 1 point
    We have a number of engineers and support staff who are all 'team members' under our Domotz account. When someone sets up a new agent, each team member who needs to receive alerts for devices in that project has to set them up for themselves. I can see how this can be advantageous, but it would be great if there were a way to share your alerts set up for a particular project to other members so that they don't have to go through everything themselves. Maybe it would be possible to set up more team member types (e.g. technical, sales, etc) and then on each project set up the default alerts for that team member type? Or perhaps you could set up alert groups that a person could subscribe to? Using a system like this means that if a new device is added and an alert set up for it (e.g. an engineer goes to site and installs something new) everyone who is subscribed to that projects alerts would then automatically be set up and ready to go.
  13. 1 point
    I have just setup a Raspberry Pi for the first time. So far so good.... I noticed on the Site Details page the location of the Site Agent can be specified. However, I live in a rural country location and all the options are tagged to a civic street address so it is appears that the best I can do is specify my local town which is 5 miles away. It would be wonderful to be able to specify a GPS location.
  14. 1 point
    Any update regarding SNMP on Ubiquiti Unifi / Edge / Airfiber equipment? There is a fair amount of useful information which OID's can provide. Currently I'm using my unifi cloud for some of this info and was able to find out that a switch is overheating (88deg C) but info that would have been a thumbs up if it came from Domotz.
  15. 1 point
    Are there any issues with having the list grow and grow? Am I correct in thinking that I have read somewhere the clients are recorded by mac address (not IP address) and so even though they may have the same DHCP ip address assigned they will be listed as a new device as they have a different mac address? Oh and +1 for "remove all devices that have been inactive for X days"
  16. 1 point
    Plug a monitor and a keyboard into it. Drop to a terminal window and ifconfig at the command line. It will tell you the MAC address of eth0 there Add that to your allowed table on your router. Plug the Pi into a network. Enjoy.
  17. 1 point
    Manually updated the agent and is back online and working perfectly.
  18. 1 point
    Very good question. It's quite hard to find a reliable SD card, and in any case, they are not very cheap. For professional usage, we recommend the Domotz Box. It will be available in few weeks (it's now in the packaging and shipping phase). Check-out features and advantages of Domotz Box here: https://www.domotz.com/installation/#domotzbox It is equipped with an on-board eMMC, with a much much longer life than any SD card you can use on Raspberry Pi. Moreover it's much faster (it's based on an Intel Processor), and faster communication: ethernet card speed up to 1 Gbps (instead of the 100 Mbps offered by the Raspberry Pi): in this way, you can also perform speed-tests with much higher bandwidth.
  19. 1 point
    First off, not sure where this should go. I think a new category in the community might be useful to discuss the Web App as more people start to use it. Anyways, on to the feedback (in order I stumbled on things, not necessarily logical): 1) The tiles should be oriented vertically like the smartphone app. You folks are doing a good job keeping things consistent so please stick with that ideology. 2) Nice quick response. I changed a device's information in the Web App and saw the changes show on my App within seconds. 3) The device icons still have the round background like the app but it appears to be a much lighter gray on the Web App and fades into the white background. I would prefer if it gets darkened a bit. 4) Got kicked out of the web app (back to login screen) due to a browser refresh. Refreshing the webpage really should not log me out. 5) Web app does not remember which Agent I was using last (unlike the phone app). This is a touch annoying as the first agent I have on my list has been dead for some time so I need to switch agents each time. But that part works fine. 6) Favorites do not seem to work in the Devices listing. I selected a device as a favorite in my phone app but it did not show up starred in my web app. Selecting it in the web app did not show it in the phone app. 7) Switching devices to Important also does not appear to be working properly, same as favorites. 8) Device Types selection icons are HUGE, or at least the white space around them is giant. The window displayed is far too big for the icons within it arranged in 3 columns. 9) On the Device Types selection window the icon backgrounds and the gray dividing lines between icons are both very faint gray (as mentioned in #3 above). They need to be much more visible. 10) The Device page lacks visible boundaries between areas on the page, like with the phone app. This does not even appear to be a case of the borders being too faint (like in #9 above), rather they do not appear to exist. 11) General Note (not specific to Web App). Not sure what constitutes a status change as I noticed my Router is listed as having had it's last status change 2 months ago. I know I have rebooted it since, including within the last week as new software was release for it that I rebooted it for. 12) Device Connect page appears to be missing it's graphic at the top of the page. There is a box like there should be a graphic though... 13) General Note (not specific to Web App). I noticed that the First Seen date/time for a device was listed as EDT... I would not recommend using that timezone or necessarily ANY timezone other than UTC. The reasoning (at least for EDT) is that time zone is also tied to Daylight Savings Time. That has now ended and my area is back on the EST timezone. Therefore EDT is currently invalid... Trust me, I hate daylight savings time stuff also... Which is why all my projects use UTC even if I do have to change it in my head. 14) Web App "Cannot find an available server..." for doing a Speed Test. Yet the Phone App found one almost instantly (which is a TOTALLY different server, in Vermont, than it has ever used before and one that definitely is not "nearer" than the one it used to use in Toronto). 15) The Web App did not retain the Speed Test information completed by the phone app in it's overall tiles section. 16) The titles for the web pages do not seem to get updated when moving back using the "Back" link on the page. For example I just went back to the main tiles page from the Network Health Analysis page and the title remained Network Health Analysis. 17) No titles exist (thus it remains whatever title was previously populated) for the "Important Devices", "Devices", "Collaboration", and "Give Domotz" tiles. 18) I did not see any copyright notice on the webpages anywhere... Might want to look into that. As a further note there is not even any listed in the source for the webpage. 19) Might want to restrict right-clicking on the webpages if you are concerned about people easily getting the source. It is simple enough to get it otherwise but for some users this would stop them, if you wanted to at least. 20) Ending on a good note! Impressed with the Web App so far. Also appreciate that it gets a nice green lock icon from Google Canary, meaning it is fairly secure (uses TLS, not SSL).
  20. 1 point
    The Selection for Device Type will not allow me to scroll down on the Webb App. works great on the Domotz App.
  21. 1 point
    True. Yeah... I am getting side tracked from the main topic. So far no problems with the RasPi Zero running the domotz agent. It seems to be responding just fine. Probably not going to get to stress it more until the weekend though.
  22. 1 point
    I would like domotz to keep/report some basic internet connection history. Since most homes use a dynamic public IP addresses. i would like to have a history of when it changes and what the new IP address is. Gives me an idea of when my ISP may have made some equipment changes and maybe I should re-run some speed tests. Timestamp of every time my internet connection goes down and when it comes back up. With this data logged you could also create a monthly or quarterly total downtime trend chart to see if your ISP is getting better or worse over time. Thanks
  23. 1 point
    So I know this is a bit out there but I just wanted to get it written down before I lost the idea. It would be nice if Domotz comes out with an Android Widget that could give you a couple key status points all the time on your phone without opening up the app. Also interesting would be an active (or are they called live) background that is a more expansive version of the same. Taking dashboards to a whole new level. Widgets could be simple but expand up to cover many different things if the user wants to dedicate more tiles to it. Another item would be Tasker integration. As an automation tool Tasker for Android is hugely useful. I already have it monitor all sorts of things about my aquarium and notify me if anything starts to go astray (and get more adamant the worse it gets) as well as network awareness, data connections, various locations, etc... Some level of integration with Domotz would be excellent because it could allow Tasker much more awareness of a network's situation without you having to set up everything so Tasker can check it directly (or query some device within the network). Doing this as a plugin or such would be wonderful.
  24. 1 point
    So... I finally got a chance to do a little more in-depth checks and when I startup the App I get the following message: "The agent went Offline 2 days ago." This strikes me as a touch cryptic. Is it meant to say: 1) "The agent has been offline for 2 days." (major problem) 2) "The agent went offline 2 days ago but is running now." (problem you should look into but not major) Considering the fact that none of the statuses are more recent then 2 days, I think it is the first. Maybe it should be rephrased. This would appear to coincide with when we had a power failure. However... My BACKUP Domotz agent is running just fine. So something about PRIMARY is problematic. I will attempt to reboot it. Reboot does not appear to have worked. The agent still registers as offline. Looking further into the network... It shows as Offline, despite the reboot. I am going to have to look into the RasPi itself...In any case, the topic was about the status message displayed being a touch off for what it meant (IMO). So looking into the RasPi I need to completely recreate it. The file system was corrupted and read-only so a whole bunch of things were having trouble and it could not fully boot. Not sure why that would have happened due to a power failure. As it goes through it does mention starting domotz but has errors with bunch of lines trying to write to a log, but everything is read-only. This RasPi was being powered directly from my router which is on a backup battery... So it actually should not have been affected by the power failure (the router was unaffected, uptime >23 days).
  25. 1 point
    The Domotz Agent has the following system requirements. If your hardware doesn’t meet or exceed them, the Domotz Agent will most likely not work with your hardware. QNAP QTS 4.3 or later. Minimum 512MB of RAM Any x86/x64 processor Annapurna Alpine Unfortunately QNAP has recently discontinued range of devices, so if your NAS doesn't support QTS 4.3, it won't be able to run Domotz. QNAP offers a product status list here https://www.qnap.com/en/product/eol.php Please contact QNAP support if you don’t know what processor is used in your NAS or what OS it runs. Raspberry Pi Raspberry Pi Model B, Raspberry Pi Model B+, Raspberry Pi 2 model B and Raspberry Pi 3 model B. Note that the Raspberry Pi Model A, Raspberry Pi Model A+ and the Raspberry Pi Zero are not recommended due to hardware limitations. ReadyNAS OS 6.x or later. Minimum 512MB of RAM Any x86/x64 processor The following ARM based processors: Marvell Armada 370 and Annapurna Alpine. Synology DSM 5.x or later. Minimum 512MB of RAM Any x86/x64 processor The following ARM based processors: Marvell Armada 370, 375 and XP. We also anticipate to support the following ARM based processors: Annapurna Alpine, Freescale QorIQ LS1024A/ Mindspeed Comcerto 2000. Note that Marvell Kirkwood processors are not supported, nor are any PowerPC based processors, such as the Freescale PowerQUICC or QorIQ P-series. No models prior to the x10-series are supported. Synology lists the CPU used in their various models on their website, although for older models you might have to contact Synology's support.
×