• Announcements

    • Giancarlo

      Windows Domotz Agent Manager - Available to be downloaded   08/02/18

      We are glad to announce that we have completed the development of the first Beta 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 following link:   DomotzAgentManager   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.    For any feedback, issue or concern, please do not hesitate to contact support@domotz.com
allsystemsgo

RTI Support

5 posts in this topic

Hey guys, any plans to support RTI control processors and possible their ZW9 zwave controllers?

1

Share this post


Link to post
Share on other sites

Not in the short term. But plans might change. In case we will proactively contact you.

0

Share this post


Link to post
Share on other sites

RTI support on this would be amazing, I guess it would need to be some sort of VPN tunnel. 

0

Share this post


Link to post
Share on other sites

Well, we haven't done direct tests with RTI. But I guess the Open TCP can be used to remotely connect to RTI control processor, in the same way it is currently possible with Savant, Crestron, Lutron, Contro4, and more... we have guides for those control systems, but not yet had a chance to perform a test on an RTI system.

1

Share this post


Link to post
Share on other sites

Here is the RTI info.

Its service for RTI Panel talks on port 4110. Monitoring this port lets me know when the RTI processor locks up.

Port 80 is used for the diagnostics page and USUALLY goes off line when the processor is locked up.

ICMP can be used to monitor the processors... but they continue to respond to pings EVEN AFTER A COMPLETE LOCK UP.

 

AS for updating a system remotely... there are 2 ports required... 5053 has to be forwarded to the DEVICE BEING UPDATED and 5056 has to be forwarded to the computer SENDING THE UPDATE. (THIS ABSOLUTELY SUCKS, and is the reason I have to use VPNs to send updates to systems remotely.) Its also BS to have to keep changing ports in the router to forward to each RTI device before you can send to it.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now