Hi – This post is to share my experience trying to convert a small HA environment from a ZeeS2 to a ZeeS2V2 build. My environment is as follows:
ZeeS2 (Mono 3 build) Environment:
• HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.297
• Linux version: Linux HomeTrollerZeeS2 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12
• 17:20:48 GMT 2015 armv7l GNU/Linux System Uptime: 4 Days 1 Hour 48 Minutes 52 Seconds
• Number of Devices: 82
• Number of Events: 91
• Available Threads: 399
• Enabled Plug-Ins
o 3.0.0.68: HSTouch Server
o 3.0.1.87: Z-Wave
ZeeS2V2 (Mono 4 build) Environment:
• HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.297
• Linux version: Linux HomeTrollerZeeS2V2 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00
• GMT 2016 armv7l GNU/Linux System Uptime: 0 Days 15 Hours 41 Minutes 1 Second
• Number of Devices: 102
• Number of Events: 92
• Available Threads: 394
• Enabled Plug-Ins
o 3.0.0.68: HSTouch Server
o 3.0.1.87: Z-Wave
Z-Wave Controller:
• Z-NET V1 (with WiFi)
• Z-NET Configuration- Version 1.0.22
I have 19 physical Z-wave devices (a mix of Z-wave standard and z-wave PLUS). I completed a backup of my ZeeS2 (Mono 3 build) and then restored that backup to a fresh ZeeS2V2 (Mono 4 build). Both the ZeeS2 and the ZeeS2V2 builds are on separate Raspberry PI 2. I then connected to my new ZeeS2V2 (mono 4 build) to my Z-NET V1 z-wave controller. Once connected to the Z-NET, I optimized my Z-wave network. The z-wave optimization process resulted in the creation of duplicate Z-wave devices in my ZeeS2V2 (mono 4 build). The duplicate devices appear to be select child elements of all 19 physical z-wave devices. Only physical z-wave devices were duplicated (virtual devices were not duplicated). The z-wave duplicate physical devices tended to be a root device element / child element vs. the entire parent child structure. In certain cases only the duplicate z-wave child element is recognized by ZeeS2V2 build when creating new events. I discovered this when I tried to leverage “Z-Wave action” on a door lock. When I tried to “set a code” or “remove a code” for my Schlage door lock, the ZeeS2V2 (mono 4 build) will only recognize the newly created duplicate child device. It will not recognize my original restored z-wave device.
Based on my experience (and I hope I am very wrong) – it appears that a move / migration from the ZeeS2 (Mono 3 build) to the more modern ZeeS2V2 (mono 4 build) is a **very** significant move. If my experience is consistent with others performing similar migrations, then it appears that this migration could be as significant as a HS2 to HS3 migration (at least for z-wave based networks).
I only make this statement because the duplicate child z-wave devices created from the migration to the mono 4 build may require the deletion and re-addition of those z-wave devices under Mono 4 build. The reason for the deletion is to avoid potential confusion between the duplicate devices that result from a restore of the Mono 3 build to a Mono 4 build. In addition to the deletion and re-creation of the z-wave devices, all event logic must be recreated as well (which has been documented in earlier posts)….
Again – I hope my experience is unique and the scenario above related to the creation of duplicate z-wave devices (that cannot be deleted) is not the case for others. Manually recreating all event logic is going to be a large enough task…
Has anyone else experienced duplicate Z-wave devices when restoring a backup from a ZeeS2 (Mono 3 build) to a ZeeS2V2 (Mono 4 build)?
Thanks, Mike
ZeeS2 (Mono 3 build) Environment:
• HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.297
• Linux version: Linux HomeTrollerZeeS2 3.18.7-v7+ #755 SMP PREEMPT Thu Feb 12
• 17:20:48 GMT 2015 armv7l GNU/Linux System Uptime: 4 Days 1 Hour 48 Minutes 52 Seconds
• Number of Devices: 82
• Number of Events: 91
• Available Threads: 399
• Enabled Plug-Ins
o 3.0.0.68: HSTouch Server
o 3.0.1.87: Z-Wave
ZeeS2V2 (Mono 4 build) Environment:
• HomeSeer Version: HS3 ZEE S2 Edition 3.0.0.297
• Linux version: Linux HomeTrollerZeeS2V2 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00
• GMT 2016 armv7l GNU/Linux System Uptime: 0 Days 15 Hours 41 Minutes 1 Second
• Number of Devices: 102
• Number of Events: 92
• Available Threads: 394
• Enabled Plug-Ins
o 3.0.0.68: HSTouch Server
o 3.0.1.87: Z-Wave
Z-Wave Controller:
• Z-NET V1 (with WiFi)
• Z-NET Configuration- Version 1.0.22
I have 19 physical Z-wave devices (a mix of Z-wave standard and z-wave PLUS). I completed a backup of my ZeeS2 (Mono 3 build) and then restored that backup to a fresh ZeeS2V2 (Mono 4 build). Both the ZeeS2 and the ZeeS2V2 builds are on separate Raspberry PI 2. I then connected to my new ZeeS2V2 (mono 4 build) to my Z-NET V1 z-wave controller. Once connected to the Z-NET, I optimized my Z-wave network. The z-wave optimization process resulted in the creation of duplicate Z-wave devices in my ZeeS2V2 (mono 4 build). The duplicate devices appear to be select child elements of all 19 physical z-wave devices. Only physical z-wave devices were duplicated (virtual devices were not duplicated). The z-wave duplicate physical devices tended to be a root device element / child element vs. the entire parent child structure. In certain cases only the duplicate z-wave child element is recognized by ZeeS2V2 build when creating new events. I discovered this when I tried to leverage “Z-Wave action” on a door lock. When I tried to “set a code” or “remove a code” for my Schlage door lock, the ZeeS2V2 (mono 4 build) will only recognize the newly created duplicate child device. It will not recognize my original restored z-wave device.
Based on my experience (and I hope I am very wrong) – it appears that a move / migration from the ZeeS2 (Mono 3 build) to the more modern ZeeS2V2 (mono 4 build) is a **very** significant move. If my experience is consistent with others performing similar migrations, then it appears that this migration could be as significant as a HS2 to HS3 migration (at least for z-wave based networks).
I only make this statement because the duplicate child z-wave devices created from the migration to the mono 4 build may require the deletion and re-addition of those z-wave devices under Mono 4 build. The reason for the deletion is to avoid potential confusion between the duplicate devices that result from a restore of the Mono 3 build to a Mono 4 build. In addition to the deletion and re-creation of the z-wave devices, all event logic must be recreated as well (which has been documented in earlier posts)….
Again – I hope my experience is unique and the scenario above related to the creation of duplicate z-wave devices (that cannot be deleted) is not the case for others. Manually recreating all event logic is going to be a large enough task…
Has anyone else experienced duplicate Z-wave devices when restoring a backup from a ZeeS2 (Mono 3 build) to a ZeeS2V2 (Mono 4 build)?
Thanks, Mike
Comment