The email was from these guys:
Here it is in its entirety:
Thank you for registering an interest in our new home automation system.
In parallel with completing the development and testing of the system, we have been working with partners on specific niche applications. The recent news about Iris has prompted us to put all of our energies back into enabling the continued use of the earlier Iris and AlertMe devices for HA, alongside the more recent devices.
A new website, SystronicsRF.com, will be put online by the end of next week, December 7th. The website describes the system features, how it can be used, and the thinking behind our approach, which we have also mentioned in previous posts. Its content will also be expanded over time.
The target date for the release of a Beta version is mid-January, and we will explain the procedure for accessing this version ahead of time.
We are providing more information by email to those of you who have registered their interest in using the system via the video pages. You will also be able to register your interest via the new website.
We have been building a complete solution, including the control system within the home, the supporting cloud-based services. The solution has been built from the ground up, and the last stages have been the user interface and a website explaining all of the features.
Most of the system is in place, is fully functional, and has been tested in real environments for the last 12 months, and we will be focusing totally on its release, once we have the website online.
We have opted for the name SystronicsRF, because it is a control system employing radio frequency electronic devices, which can be tailored through the software to several differing areas of application, both within the home, and elsewhere.
The following are some further notes on the design and operation of the system: -
A Self-Contained System
The hub hardware is a Raspberry Pi 3B, to which USB based network adapters can be added, as required. The software, for both the in-home control system, and the supporting cloud services, is written in Microsoft C#, has been developed in its entirety by us, and without any reliance being placed on any third-party software.
The in-home part of the system runs self-contained, and without any reliance on the cloud, or an internet connection. Users are able to control the system operation locally via a mobile phone, tablet, or other WiFi device, connected directly via the home WiFi to the hub. Supporting cloud services are provided, so that users can also control the system remotely, as required, and can use cloud services, such as Alexa, local weather, but none of these are essential for the normal everyday control and use of the system.
The hub software supports the current ZigBee protocol, as well as the earlier AlertMe and 1st generation Iris protocol. It also supports the Z-wave protocol running at both the European and North American frequencies. Most recently, it has been extended to support a local hub-based WiFi network, as distinct from the normal home WiFi.
The hub software is also intended to operate with any device from any manufacturer, so that users can employ the best combination of devices to suit their requirements.
Each device has a predefined profile, which equivalent to the peripheral drivers found in PCs.
These profiles enable the control system to operate within a standardised software environment, regardless of device manufacturer. So far, the software has been tested successfully with more than 60 devices from over 30 different manufacturers.
Most recently, the focus has been on the development of the user interface, which has been divided into two parts, one for everyday use, and the other for tailoring the system to each user’s needs. All of the user interfaces are browser based, and access a web service running on the hub, in the same way as a conventional website, and via a local SSL connection.
Everyday use in this context includes switching devices on and off, such as lights and other powered devices, and enabling or disabling automated actions, such as overnight security, heating and other schedules, as well as boosting the heating, etc. This everyday user interface is based on responsive website design technology, which optimises the page layout to suit the screen of the device being used, from mobile phones to wide screen monitors.
The design of the automated actions, and the setting up of the features for the everyday use of the system, are undertaken via a separate user interface. Following the general trend towards the use of larger screen devices for these aspects, they are only made available on larger screen devices, and not on mobile phones. Responsive website design technology is still employed, to cater for different screen sizes, but the functionality is disabled when the screen size is less than that of a 10” tablet in a portrait orientation.
Action Designer & IDE
In practice, the automated actions consist of the actual actions, which control the devices, and a user interface layer, which we are calling activators. In general, an activator can call any action, and an action can call any other action. This approach enables the widest possible range of functionality to be provided, from a simple on / off switch through to the more complex applications, which can be built from a structure of actions. The action designer enables these activators and actions to be defined by simple device selectors and conditional selectors.
The system also includes an Integrated Development Environment (IDE), which enables much more complex applications to be created. The devices are selected in the same way as for any other type of action, but the conditional statements are written in Microsoft C#. These programs do not have to be compiled separately, such as with Microsoft Visual Studio, because the built-in IDE includes its own compiler.
We have also used these tools to create standard applications, such as for hot water and central heating control.
As with the normal everyday use of the system, the action designer and the IDE do not rely on any cloud services, or an internet connection, because they run in a self-contained manner on the hub.
Secure Web Services
Secure web services are provided in support of the system. Each hub has an associated secure area within the cloud, through which all communications with then hub are made.
For example, if the user chooses to access the system remotely, then they connect their mobile device to the web service in their secure area, and the requests from their browser are forwarded to the hub.
In addition to the normal cloud based firewall, the web service validates the received request, as does the hub. The hub also only accepts request from the associated secure cloud based web service, and not from any other source.
Similarly, the hub sends its responses back to the secure cloud based web service, from where it is forwarded to the originating browser.
SSL connections are used between the user’s browser and the web service, and between the web service and the hub.
System Health & Security
Extensive self-monitoring features have been added to the system. All of the connected devices are monitored for their battery level, where applicable, and to their signal strength and quality, etc. The system also attempts to self-heal, wherever possible, before referring any issue back to the user.
Particular attention has also been given to protecting the system against radio frequency interference, including denial of service and the attachment of rogue devices.
The new website will be online by the end of next week, December 7th.
SYSTRONICSRF – Radio Frequency Networked Systems
Tel: +44(0)1635 876699
Mobile: +44(0)7799 893 613
firstname.lastname@example.org | www.systronicsrf.com