Don't Throw Away Your Old Devices
3 3

39 posts in this topic

Yes.  We are about to release a video later this week listing all of the devices and manufacturers that we have integrated with.

There is one exception.  We have not done any work on door locks.  Can you tell me the most popular / common door lock?

Share this post


Link to post
Share on other sites
21 hours ago, Vettester said:

Is this system compatible with the Gen 2 Iris devices?

Not 100% sure but since it also says it works with other brands I believe it works with other nonproprietary zwave and zigbee devices. But with that said I think he mentioned to me in a PM early on that you would need another usb stick...one for iris one for normal zwave and or zigbee.

Share this post


Link to post
Share on other sites

The system will work with Iris Gen 2.

There are essentially two standards, the current HA standard, and the standard used by AlertMe, which also developed the Iris Gen 1 range.

We will be releasing another video later this week, which lists and explains all of the various device types and manufacturers that we have tested with the system so far.

All of the modern ZigBee devices use a very similar application layer.  

AlertMe, in the UK, and Iris Gen 1, have a common application layer, but it differs from the modern standard.

For this reason, we use two different ZigBee network adapters, one for the latest standard, and the other for AlertMe / Iris Gen 1.

There is only one standard for Z-Wave, but the radio frequency differs between the UK (868 MHz) and the USA (908 MHz).

For this reason, a different Z-Wave adapter has to be used for each country.  Otherwise, there is no difference across Z-Wave devices.

We are using USB adapters, because we think its easiest approach for anyone with a Raspberry Pi.  We have also used other, hard wired network adapters.

 

Share this post


Link to post
Share on other sites
On 7/17/2018 at 7:15 PM, Wlepse said:

Are you considering IFTTT compatibility?

Our software is designed to cater for all of the requirements of a smart home control system without relying on IFTTT.   This includes communications with external services, such as Alexa, sourcing local environmental data, and sending email alerts to the user’s phone.

Even so, we have anticipated the use of IFTTT in the design.

IFTTT applets provide a standardised means of configuring simple online tasks.  It is especially useful when the service delivering the IFTTT trigger differs from the service that receives the IFTTT action.

Although an IFTTT applet responds to an individual trigger, the processing needed to generate that trigger within the delivering service can be very complex.  Similarly, an IFTTT applet invokes an individual action.  Again, the processing within the receiving service can be very complex.

One of the main limitations of many existing IFTTT applets used for smart home systems is that they refer to a particular manufacturer’s device.

To avoid this, our action definitions refer to the data that is being processed, and not to the device that generates the data.

For example, the temperature output from an Iris motion sensor located in the living room might be referenced in an action as the “living room temperature”.  This “living room temperature” definition is related separately to the particular device.

The user might decide to replace the Iris motion sensor in this example with, say, an Aqara temperature sensor.  If the user then relates the “living room temperature” definition to this new device, any action using the “living room temperature” data is unaware that the sensor type has changed.

This also means that the IFTTT applet does not need to be changed, because it still refers to the same action. 

This approach makes the IFTTT applets more universally applicable, because they do not depend on the actual devices being used within the system.

Although this illustration is for actions, the same principle applies to the generation of the triggers.

Share this post


Link to post
Share on other sites

We have uploaded another video.  This one describes the range of devices that we have tested successfully with the new hub software.

Our approach has been to start with the ZigBee HA standard, and then investigate the characteristics of individual ZigBee HA devices.  We then repeated this process for Z-wave devices.

On investigating the older AlertMe devices, we discovered that they were compliant with an earlier non-HA standard.  We then discovered that the first generation Iris devices, which were developed by AlertMe, were also compliant with this earlier standard.

We have also investigated the characteristics of these earlier ZigBee devices.

A video describing each of the 50 plus devices from 30 plus manufacturers that we have tested can be viewed at this URL:

http://app4orce.uk/tested-devices.html

We have profiled each of these devices such that when they join the network, all of their clusters / endpoints / attributes are made accessible to the system.  

The events that each device generates, and the associated data, is brought up to a common level for use within the rest of the system.  This, for example, enables a door / window sensor to be handled as generic type, rather than a specific manufacturer’s sensor, and regardless of the network protocol being used.

Some of the narration is rather repetitive on this aspect, but our approach is fairly unique, and it makes a big difference to the rest of the system design.

We will be expanding on the use of this data, such as for actions, for system health monitoring, fault diagnostics, etc. in future videos.
 

Our future testing schedule includes the following devices:

  • Lowes Iris 1st Generation Thermostat (US Z-Wave)
  • Lowes Iris 1st Generation Siren (US Z-Wave)
  • Lowes Iris 2nd Generation Smart Plug (ZigBee w/ US Z-Wave Repeater)
  • Lowes Iris 2nd Generation Motion Sensor (ZigBee)
  • Lowes Iris 2nd Generation Door / Window Sensor (ZigBee)
  • Lowes Iris 2nd Generation Keypad (ZigBee)

Share this post


Link to post
Share on other sites
On 7/17/2018 at 12:25 AM, scunny said:

I have one of these in Satin brand new with a good price if anyone needs one.

Can you please message me the price?

Smart US door locks are not available for purchase in the UK, because Z-Wave operates at 908 MHz in the US, against 868 MHz in the UK.  We have a 908 MHz Z-Wave adapter, so that’s not a problem.

The main obstacle is the total price of the door lock, just for testing, which we have to balance against the risk of it being faulty, even if it’s a new unit.

Even pre-owned locks run at $200.00 plus on eBay.  To this is added a shipping cost to the UK of $18.00, and a UK import charge of $37.00.

Share this post


Link to post
Share on other sites

The Iris Gen 1 devices that we have tested successfully so far are:

  • Door / window sensor Item # 388558 Model # DWS901
  • Motion detector          Item # 388557 Model # MOT501
  • Smart plug                  Item # 388564 Model # SPG902
  • Alarm key fob             Item # 388559 Model # KEY903
  • Smart keypad             Item # 388562 Model # KDP901   
  • Range extender           Item # 388560 Model # REP901
  • Senior pendant           Item # 235554 Model # PDT900
  • Smart button              Item # 388563 Model # BTN900

The Iris Gen 1 devices still to be tested:

  • Programmable thermostat       Item 388565 Model # CT-101-L
  • Utilitech siren                          Item # 4222360 Model # TSE07-1

Share this post


Link to post
Share on other sites
16 hours ago, Wlepse said:

Would also be interesting to know if you plan on this being an open format like ST where people develop their own device handlers.

We have tested a range of different devices from several manufacturers, as you may have seen from the last posted video. 

We have created profiles (handlers) for each of these devices.  When any devices of these types join the network, their profile us presented a standardised interface to the control system.

We have developed in-house tools to expedite and simplify this profiling.  These tools can be made available for users to develop profiles for their own devices, although we will need to improve the user interface beforehand.

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
3 3