Zwave 700 Series Tips and tricks

[lilyoyo1]

With many people deciding to swap out their insteon for zwave or simply adding zwave support to their Polisy, I decided to do another write up to focus on the 700 series/Polisy than wade through Isy 994 boards. 

Much of the same information applies but those who never used the old boards or ISY994 (future newbies) may not think to look there. 

Zwave Boards

UDI officially supports the Zooz 700 series zwave USB stick. Unoffically, the Silicone labs Uzb7, also works with Polisy. 

There's been ongoing debate as to whether all devices need to be 700 series to take advantage of the benefits it offers. I talked to my contact at Qolsys and was told that as long as the path goes through all 700 devices, you'll realize the benefits. The flip side is that you do not control the path that something takes which is why they recommend all devices be part of the same series. His answer is specific to the iq4 panel but I'd assume it's the same for all zwave controllers. 

If you have a house full of zwave, the range is irrelevant as the greater device density builds a stronger mesh than fewer devices with longer range. The current iteration of polisy (with 3rd party usb boards) does not support S2 security nor will this functionality be added. You will need to purchase the ZMatter board for that functionality and future features as well.

Choosing Devices

There are many caveats when choosing zwave devices. I won't touch this but will answer questions if someone has any. The main thing is to choose zwave plus devices at a minimum. The amount of 700 series devices being released has grown a lot, though you'll still find standard zwave plus devices in abundance. Starting with a new install, I'd focus my energies only on 700 series devices. If there is something specific you want that's not available, I'd settle for 500 series. Anything lower, you'll be upset from a performance standpoint. 

The 700 series stuff is backwards compatible with older series so you don't have to swap out devices to get them to work with polisy. There's a big performance gap between 300 and 700 so that may be worthwhile depending on finances. However, the gap narrows between 500-700. It's there. Just not worth the money IMO. That's up to each person to decide on their own though. 

As with the last write up, I'd still stick with well known manufacturers such as Zooz, aeotech, fibaro, homeseer, and ge. Quality  issues aside, you'll find more help and support with them than some fly by night no name company. Saving money is great. However ask yourself if those few dollars are worth the hassle and no help.

Mesh Network and Repeating

700 series touts greater range (just like 500 before it and 800 after). However that's open range. Great if you want to go from the back door to your barn 250' away but not so great if you have lots of separate spaces in your home. Save yourself frustration and assume you'll still need some type of repeating device or 3. No, battery powered devices do not extend range. 

If you only have 1 or 2 devices for your network, there is really no point in asking for help in regards to why the isy won't talk to them or intermittent communication issues. The advice from everyone will be the same. Add more devices. This can be in the form of a repeater such as those from aeotech. You can also use in wall receptacles or plug in modules. I prefer in wall receptacles since plug in modules can be unplugged or moved to a different location by someone. Keep in mind embedded devices such as receptacles will not have the range of external devices so you will need more if you go that route. 

Range

This ties in with building out your mesh. 700 series touts longer range but that's generally open air testing. Performance/range may vary depending on your home. An all 700 series install will have greater overall range than 3 or 500 series but thats not something I'd depend on. I'd still invest in repeating devices to ensure everything works exactly the way i want it to every single time. While anything can happen, I want to be able to trust that my doors will lock/unlock the way they're supposed to vs having to double check every single time due to uncertainty. 

While range is great, additonal repeating devices also allows for self healing. This is especially important for small installs such as those where one is trying to control some locks. Obviously a large install or zwave only install makes this a moot point. By adding extra devices, you are potentially adding a secondary path for the signal to route through should a device fail or something interferes with your path. Remember, what works today may not work tomorrow as you busy new furniture etc. 

I've said this before and I'll say it again. Do not fall for the range hype. Some will argue about greater range of zwave plus (and now 700 series)...However, all tests are done in open air under perfect conditions. The increased range will help if you have a modern home with an open floor plan. HOWEVER- older homes with doors and walls everywhere will still suffer from range issues that any other wireless device suffers from. This is made worse once devices are installed in metal boxes, behind fish tanks, etc. Save yourself the headaches and simply buy extra devices

Beaming

Tis is geared towards those who may look to save money by buying older devices. Finding specific devices that support beaming isn't as big of an issue with 700 series the way it is for 300 (especially) & 500 series devices. 

Controllers make poor repeaters. Their job is to send a signal to a device and move on to the next task. If they have to wake up a device, wait for it to wake up, send a signal (especially if it's encrypted), wait for a response....what happens to the rest of your devices/programs in the meantime? Another reason for have an extra device or 2 to repeat. 

Beaming devices can hold that message until the device wakes up, send it to the device, and wait for the response. During this time, the controller can handle its other duties and get the message when ready. 

Adding Devices

All 700 series devices support NWI (Network Wide Inclusion). Even with NWI, I still add my devices within a few feet of the system. This is generally a requirement of security devices (such as locks) but it's one I follow with all my devices (including insteon and my hue with the hue hub). This allows me to verify the isy can control things without issue before installing in it's final location. This way, if there is an issue, I've taken the isy out of the equation. I add devices in the order I'm installing from closest to farthest. While this isn't necessary, I still do this from when zwave first came out. With secure devices such as doorlocks, you should have them within a few feet of polisy when adding to the network to ensure everything works properly. Once done, verify functions, move to permanent location, Install, and heal.

Both my test polisy and house polisy units had NWI prechecked. I'd go into your zwave settings panel and verify that it's turned on. The proper way to use NWI would be to include devices that are closest to your polisy and work your way out. To exclude devices it's the opposite. Work your way from the farthest reaches to the closest. 

For the most part, most devices can only be added to one controller. Yes, there are some variables such as primary and secondary controllers but for a newbie, that's advanced information that can cause confusion. Should more detail be needed, ask and I will explain.

Exclude/Include

The best way to add a device is to exclude it first and then add it. This process wipes out any potential links which could prevent a device from being added. Once im done adding devices, I'll run a heal (update neighbors). Those using NWI while devices are already install can probably skip this process. 

For those wanting to use polisy/Isy as a secondary controller, it must be added to the primary controller before you add your zwave devices to the Isy. 

While an exclude is not necessarily needed for new out of the box devices, I still do it before including. Devices can come from the factory with test links still there which will prevent inclusion. For me, it's easier to simply exclude and move straight to include than break my rhythm because one doesn't include. Its your choice however. 

If moving from the Isy or another controller, you'll need to exclude first then include. The good thing is that you can use polisy for that. You don't have to run the exclusion on the Isy (or other controller) before trying to add it to polisy. 

Nodes

You'll probably notice a zillion different nodes will show up when you add a device to the Isy. The zwave code supports those nodes though the mfg. of your device may not be using them for your product. Because the admin console shows everything, they are there. If it's a small install, you can create a folder for them and call it a day. If it's a larger install, I recommend deleting the ones you do not or will not use as they count towards your node count. It's easier to do this as you add each device vs once you have 40+ devices in there. 

If you go to the mfg. website, you'll find their full owners manual. That's where you can find the parameter settings for your device. Some of those extra nodes will populate once you set the specific parameter for it. Once you've verified what you'll need to keep, feel free to delete the additional nodes. You don't need them for anything. 

Edited October 8, 2022 by lilyoyo1

[Bumbershoot]

Nicely done, and thank-you!

[asbril]

3 hours ago, lilyoyo1 said:

With many people deciding to swap out their insteon for zwave or simply adding zwave support to their Polisy, I decided to do another write up to focus on the 700 series/Polisy than wade through Isy 994 boards. 

Much of the same information applies but those who never used the old boards or ISY994 (future newbies) may not think to look there. 

Zwave Boards

UDI officially supports the Zooz 700 series zwave USB stick. Unoffically, the Silicone labs Uzb7, also works with Polisy. 

There's been ongoing debate as to whether all devices need to be 700 series to take advantage of the benefits it offers. I talked to my contact at Qolsys and was told that as long as the path goes through all 700 devices, you'll realize the benefits. The flip side is that you do not control the path that something takes which is why they recommend all devices be part of the same series. His answer is specific to the iq4 panel but I'd assume it's the same for all zwave controllers. 

If you have a house full of zwave, the range is irrelevant as the greater device density builds a stronger mesh than fewer devices with longer range. 

Choosing Devices

There are many caveats when choosing zwave devices. I won't touch this but will answer questions if someone has any. The main thing is to choose zwave plus devices at a minimum. The amount of 700 series devices being released has grown a lot though you'll still find standard zwave plus devices in abundance. Starting with a new install, I'd focus my energies only on 700 series devices. If there is something specific you want that's not available, I'd settle for 500 series. Anything lower, you'll be upset from a performance standpoint. 

The 700 series stuff is backwards compatible with older series so you don't have to swap out devices to get them to work with polisy. There's a big performance gap between 300 and 700 so that may be worthwhile depending on finances. However, the gap narrows between 500-700. It's there. Just not worth the money IMO. That's up to each person to decide on their own though. 

As with the last write up, I'd still stick with well known manufacturers such as aeotech, fibaro, homeseer, and ge. Quality  issues aside, you'll find more help and support with them than some fly by night no name company. Saving money is great. However ask yourself if those few dollars are worth the hassle and no help.

Mesh Network and Repeating

700 series touts greater range (just like 500 before it and 800 after it). However that's open range. Great if you want to go from the back door to your barn 250' away but not so great if you have lots of separate spaces in your home. Save yourself frustration and assume you'll still need some type of repeating device or 3. No, battery powered devices do not extend range. 

If you only have 1 or 2 devices for your network, there is really no point in asking for help in regards to why the isy won't talk to them or intermittent communication issues. The advice from everyone will be the same. Add more devices. This can be in the form of a repeater such as those from aeotech. You can also use in wall receptacles or plug in modules. I prefer in wall receptacles since plug in modules can be unplugged or moved to a different location by someone. Keep in mind embedded devices such as receptacles will not have the range of external devices so you will need more if you go that route. 

Range

This ties in with building out your mesh. 700 series touts longer range but that's generally open air testing. Performance/range may vary depending on your home. An all 700 series install will have greater overall range than 3 or 500 series but thats not something I'd depend on. I'd still invest in repeating devices to ensure everything works exactly the way i want it to every single time. While anything can happen, I want to be able to trust that my doors will lock/unlock the way they're supposed to vs having to double check every single time due to uncertainty. 

While range is great, additonal repeating devices also allows for self healing. This is especially important for small installs such as those where one is trying to control some locks. Obviously a large install or zwave only install makes this a moot point. By adding extra devices, you are potentially adding a secondary path for the signal to route through should a device fail or something interferes with your path. Remember, what works today may not work tomorrow as you busy new furniture etc. 

I've said this before and I'll say it again. Do not fall for the range hype. Some will argue about greater range of zwave plus (and now 700 series)...However, all tests are done in open air under perfect conditions. The increased range will help if you have a modern home with an open floor plan. HOWEVER- older homes with doors and walls everywhere will still suffer from range issues that any other wireless device suffers from. This is made worse once devices are installed in metal boxes, behind fish tanks, etc. Save yourself the headaches and simply buy extra devices

Beaming

Tis is geared towards those who may look to save money by buying older devices. Finding specific devices that support beaming isn't as big of an issue with 700 series the way it is for 300 (especially) & 500 series devices. 

Controllers make poor repeaters. Their job is to send a signal to a device and move on to the next task. If they have to wake up a device, wait for it to wake up, send a signal (especially if it's encrypted), wait for a response....what happens to the rest of your devices/programs in the meantime? Another reason for have an extra device or 2 to repeat. 

Beaming devices can hold that message until the device wakes up, send it to the device, and wait for the response. During this time, the controller can handle its other duties and get the message when ready. 

Adding Devices

All 700 series devices support NWI (Network Wide Inclusion). Even with NWI, I still add my devices within a few feet of the system. This is generally a requirement of security devices (such as locks) but it's one I follow with all my devices (including insteon and my hue with the hue hub). This allows me to verify the isy can control things without issue before installing in it's final location. This way, if there is an issue, I've taken the isy out of the equation. I add devices in the order I'm installing from closest to farthest. While this isn't necessary, I still do this from when zwave first came out.

Both my test polisy and house polisy units had NWI prechecked. I'd go into your zwave settings panel and verify that it's turned on. The proper way to use NWI would be to include devices that are closest to your polisy and work your way out. To exclude devices it's the opposite. Work your way from the farthest reaches to the closest. 

For the most part, most devices can only be added to one controller. Yes, there are some variables such as primary and secondary controllers but for a newbie, that's advanced information that can cause confusion. Should more detail be needed, ask and I will explain. The best way to add a device is to exclude it first and then add it. This process wipes out any potential links which could prevent a device from being added. Once im done adding devices, I'll run a heal (update neighbors). Those using NWI while devices are already install can probably skip this process. 

For those wanting to use polisy/Isy as a secondary controller, it must be added to the primary controller before you add your zwave devices to the Isy. 

Nodes

You'll probably notice a zillion different nodes will show up when you add a device to the Isy. The zwave code supports those nodes though the mfg. of your device may not be using them for your product. Because the admin console shows everything, they are there. If it's a small install, you can create a folder for them and call it a day. If it's a larger install, I recommend deleting the ones you do not or will not use as they count towards your node count. It's easier to do this as you add each device vs once you have 40+ devices in there. 

If you go to the mfg. website, you'll find their full owners manual. That's where you can find the parameter settings for your device. Some of those extra nodes will populate once you set the specific parameter for it. Once you've verified what you'll need to keep, feel free to delete the additional nodes. You don't need them for anything. 

Yes very well done. Great job. Just one question.....  when deleting the not-usable nodes, don't they come back when synching ISY ?

[lilyoyo1]

28 minutes ago, asbril said:

Yes very well done. Great job. Just one question.....  when deleting the not-usable nodes, don't they come back when synching ISY ?

Thank you. Unfortunately they will come back if you choose sync nodes. However, this isn't something that one should really have to do for their network. 

If a sync needs to be done. You're better off doing that for the individual device than for the whole system. 

[vbPhil]

Is there any way to poll a device to determine what Series it is? The few I have are from GE labeled as Z-Wave Plus but no mention of series. 

[lilyoyo1]

3 hours ago, vbphil said:

Is there any way to poll a device to determine what Series it is? The few I have are from GE labeled as Z-Wave Plus but no mention of series. 

Not that I've seen. If they are zwave+ then your devices would be 500 series. 

[stillwater]

Thanks for this @lilyoyo1  With all the interest right now in moving from Insteon to Zwave (or adding Zwave devices to an Insteon system),  It would be great to have a table that shows closest equivalents to the various Insteon devices --  I had the impression that Z-wave was mostly switches and outlets..  It looks there is more than I had assumed (for example. sensors). 

I have seen the Zen17 recommended as a replacement for the Insteon IO module. 

  I was wondering are there Z-wave plus or (better) 700 series equivalents to the Insteon Micro On/Off, Micro Dimmer,  and Micro Open/Close modules?  Though they are not exact replacements I see the Zooz Z51 could work instead of the Micro On/Off and the Z52 instead of the Micro Open/Close.   

I looked at a few other brands but haven't yet found a Zwave 700  equivalent to the Insteon micro dim.  

[Techman]

@stillwater

Here's a site worth checking out: - The Internet of Things is powered by Z-Wave. (z-wavealliance.org)

 

 

[lilyoyo1]

3 hours ago, stillwater said:

Thanks for this @lilyoyo1  With all the interest right now in moving from Insteon to Zwave (or adding Zwave devices to an Insteon system),  It would be great to have a table that shows closest equivalents to the various Insteon devices --  I had the impression that Z-wave was mostly switches and outlets..  It looks there is more than I had assumed (for example. sensors). 

I have seen the Zen17 recommended as a replacement for the Insteon IO module. 

  I was wondering are there Z-wave plus or (better) 700 series equivalents to the Insteon Micro On/Off, Micro Dimmer,  and Micro Open/Close modules?  Though they are not exact replacements I see the Zooz Z51 could work instead of the Micro On/Off and the Z52 instead of the Micro Open/Close.   

I looked at a few other brands but haven't yet found a Zwave 700  equivalent to the Insteon micro dim.  

I don't know of any 700 series micro modules but I know aeotec and fibaro makes them

[stillwater]

Thanks! The Zen51 and Zen52 appear to be 1.5 x 1.4" and I don't know how thick so they look micro size.   They are 700 /S2 series. 

Thanks for the direction to Fibaro and Aeotec.  The Fibaro Dimmer 2 is slightly larger and is 500 series.    Aeotec Nano Dimmer is 2.9" x 2.9" x 1.1" and also 500 series.  I see on the site linked by Techman that Silicon Labs is already out with 800 series modules that are available to be incorporated into products. ...  haven't looked at whether that means 700 series stuff will become somewhat obsolete or whether 800 series  just allows longer battery life  or something.  

[stillwater]

2 hours ago, Techman said:

@stillwater

Here's a site worth checking out: - The Internet of Things is powered by Z-Wave. (z-wavealliance.org)

 

 

Thanks.  This is the North American product index page  -- listing of all certified Zwave products with North American frequency.   https://products.z-wavealliance.org/regions/2/categories   Lots of products.. Some of which are available! 

[lilyoyo1]

45 minutes ago, stillwater said:

Thanks! The Zen51 and Zen52 appear to be 1.5 x 1.4" and I don't know how thick so they look micro size.   They are 700 /S2 series. 

Thanks for the direction to Fibaro and Aeotec.  The Fibaro Dimmer 2 is slightly larger and is 500 series.    Aeotec Nano Dimmer is 2.9" x 2.9" x 1.1" and also 500 series.  I see on the site linked by Techman that Silicon Labs is already out with 800 series modules that are available to be incorporated into products. ...  haven't looked at whether that means 700 series stuff will become somewhat obsolete or whether 800 series  just allows longer battery life  or something.  

I wouldn't hold off for 800 series. 700 series was released 3 years ago and is just starting to gain traction. It'll be some years before mfg start producing 800

[johnnyt]

On 1/25/2022 at 12:47 PM, lilyoyo1 said:

 

If moving from the Isy or another controller, you'll need to exclude first then include. The good thing is that you can use polisy for that. You don't have to run the exclusion on the Isy (or other controller) before trying to add it to polisy. 

 

I'm planning my move from 994iZW to IoP. Is the above saying that I won't need to exclude zwave devices from 994i and that IoP will just see them as they were on 994i when I restore the ISY backup (with the embedded zwave backup)? I didn't get that from reading other posts about migrating to IoP. Rather I was under the impression I needed to re-include my zwave devices one by one and manually realign all my 994i device name/numbers to use their inevitably new 'out of the box' device names and the new ZWxxx numbers starting at 001 when doing inclusion. This would change a lot.

[Techman]

Currently there is no migration option for moving Z-wave devices from the ISY to the Polisy. You'll have to exclude the devices from the ISY then include them into the Polisy

However, there's the possibility that when UD releases their new internal Z-wave board later this year for the Polisy it may include a migration option from the ISY 500 dongle to the Polisy.

[lilyoyo1]

16 minutes ago, johnnyt said:

I'm planning my move from 994iZW to IoP. Is the above saying that I won't need to exclude zwave devices from 994i and that IoP will just see them as they were on 994i when I restore the ISY backup (with the embedded zwave backup)? I didn't get that from reading other posts about migrating to IoP. Rather I was under the impression I needed to re-include my zwave devices one by one and manually realign all my 994i device name/numbers to use their inevitably new 'out of the box' device names and the new ZWxxx numbers starting at 001 when doing inclusion. This would change a lot.

No it does not. It's specifically for (excluding/including) removing a device from an old controller in order to add to a new one. Migrating is a different story which polisy doesn't support currently

Edited June 9, 2022 by lilyoyo1

[brians]

When you start including Z-Wave devices on the polisy, they will start at ZW 002 (controller is 001), and increment each time. It is nearly impossible to line up the numbers the same because of gaps and one is bound to get errors and have to exclude/include a device multiple times in order for a device to work - eg. Door Locks are picky, Zen17 requires you to re-include after setting certain parameters etc.

After restoring to Polisy, if you happen to include "new" devices that share an old ZW XXX then your existing programs will see it and think it is the old device and this can be confusing.

Currently the best way now is to do a complete Audit of your existing system, make a spreadsheet or something of old numbers and new numbers then go edit all programs and scenes.

 

[Athlon]

@lilyoyo

Just installed my first Z-Wave stuff - ZST10 700 and some ZEN77 switches. All is good so far.

I figured out how to set parameters in IoP for those switches by referring to the information here:

https://www.support.getzooz.com/kb/article/550-zen77-s2-dimmer-700-advanced-settings/

I wanted to change the way the LEDs were working as well as their colors.

Thank you for this thread!

[Dave-N1DCH]

On 1/25/2022 at 12:47 PM, lilyoyo1 said:

 

For the most part, most devices can only be added to one controller. Yes, there are some variables such as primary and secondary controllers but for a newbie, that's advanced information that can cause confusion. Should more detail be needed, ask and I will explain.

 

I just read an article that was saying adding secondary controllers was a good thing.  But I didn't get a sense of why. is there any documentation on why and how one would add and additional controller?

[upstatemike]

I think I am going to give up on Z-Wave and return my small test area (about 20 devices) to Insteon. Z-Wave just consumes too much effort every time I want to change something and I still can't get groups and associations (direct or programmatic) to work the way I want them to.

[lilyoyo1]

1 hour ago, Dave-N1DCH said:

I just read an article that was saying adding secondary controllers was a good thing.  But I didn't get a sense of why. is there any documentation on why and how one would add and additional controller?

Do you have a link to that article? Secondary controllers are great for large or spread out systems. If you have an avg home with a typical install, 1 centralized controller would be better. To put things into perspective, my old house was 5400 Sq ft and I was able to use a single controller with all of my devices (about 40-50). 

There is no documentation as each system has their own way of doing things. Some will only be a primary and can't be used as a secondary. Some will not pass on security keys to track secure devices such as locks. Because each has their own stipulations, you'll have to look through each manual of your chosen system and/or talk to them (which they probably won't help with anyway).

The why you'd use a secondary controller is simple. If you have a large home with devices on opposite ends, it would be cheaper to have 2 controllers than fill in the gap with unnecessary additional devices just to communicate with each other. 

Second reason is a large system. Zwave controllers are limited to around 250 devices. Real world is probably half that (depends on device types). In addition, the larger the install, the slower your system will be as well as the likelihood of issues. Secondary controllers allows you to bypass those limitations while having the benefits of integrating everything under 1 controller. 

[Dub]

31 minutes ago, lilyoyo1 said:

Do you have a link to that article?

I would be interested as well.  

36 minutes ago, lilyoyo1 said:

There is no documentation as each system has their own way of doing things. Some will only be a primary and can't be used as a secondary. Some will not pass on security keys to track secure devices such as locks. Because each has their own stipulations, you'll have to look through each manual of your chosen system and/or talk to them (which they probably won't help with anyway).

I recently tried adding my Polisy as a Secondary because my Qolsy wouldn't add as secondary.  What I read was that controllers are inconsistent to how different manufactures make them to work with each other.  Several other articles mentioned their controllers worked better as primary. I wanted to see my lock and thermostat status from my POLISY that are connected to my Qolsys.  I really like my Qolsys, but it is limited on what devices it supports, and I don't like how the automations are handled on the backend.  Ultimately it limited my POLISY's Z-Wave capabilities because I couldn't add devices to my Z-Wave network that Qolsys didn't recognize.  I don't have much technical understanding about Z-Wave like @lilyoyo1, but have learned a lot from his posts.  Based of his info and my experience I don't think I would try it again.  

Side note.  Supposedly I can get some info over MQTT but I haven't attempted that, as its a little over my head for now. I can see status in my Alarm.com app and use Siri voice control for my locks.  I just cant automate off those states with anything in POLISY.  It's a limitation I can live without for now.

 

[lilyoyo1]

32 minutes ago, Dub said:

I would be interested as well.  

I recently tried adding my Polisy as a Secondary because my Qolsy wouldn't add as secondary.  What I read was that controllers are inconsistent to how different manufactures make them to work with each other.  Several other articles mentioned their controllers worked better as primary. I wanted to see my lock and thermostat status from my POLISY that are connected to my Qolsys.  I really like my Qolsys, but it is limited on what devices it supports, and I don't like how the automations are handled on the backend.  Ultimately it limited my POLISY's Z-Wave capabilities because I couldn't add devices to my Z-Wave network that Qolsys didn't recognize.  I don't have much technical understanding about Z-Wave like @lilyoyo1, but have learned a lot from his posts.  Based of his info and my experience I don't think I would try it again.  

Side note.  Supposedly I can get some info over MQTT but I haven't attempted that, as its a little over my head for now. I can see status in my Alarm.com app and use Siri voice control for my locks.  I just cant automate off those states with anything in POLISY.  It's a limitation I can live without for now.

 

Things may have changed since I've last looked into it but I'm not aware of any alarm system that can be used as a secondary controller. Due to the nature of the product, all want to be the primary.

Once polisy supports S2 encryption, you may be able to get your locks to show up in polisy (at least i hope so). 

[Dub]

6 minutes ago, lilyoyo1 said:

Once polisy supports S2 encryption, you may be able to get your locks to show up in polisy (at least i hope so). 

My locks did show up.  They were added as encrypted because when they failed to add securely I got forced to add them again.  I'm using Kwikset.  I did have to take a couple of locks off the door to get them closer to the controller, consistently get the lock to add securely.  I guess I added them with S0.  I havent looked at my Qolsys version.    I was also able to see the locks on Apple Home through the Home Assistant, Home Kit integration(screenshot is from the orphaned config I havent removed yet).  I was also forced to add each lock separately in HA, as I understood it because the locks needed their own integration for security.

[upstatemike]

1 hour ago, Dub said:

What I read was that controllers are inconsistent to how different manufactures make them to work with each other.

This of course is one of the problems that Matter will solve once and for all.

[Michel Kohanim]

We just tested backup restore from Zooz to MatterZ. It works great. We also tested migration from 500 series. 90% there. We are also implementing some scene improvements plus OTA. Looks great thus far.

With kind regards,

Michel