Quantcast
Channel: HomeSeer Message Board
Viewing all articles
Browse latest Browse all 4847

HomeTroller-ZeeS2 (MONO 3.x) vs. HomeTroller-ZeeS2V2 (MONO 4.x) – Z-Wave Action Issue

$
0
0
I have started the process of migrating (recreating) my events from the HomeTroller-ZeeS2 (MONO 3.x) to the newer build HomeTroller-ZeeS2V2 (MONO 4.x). I have experienced my first problem (with my first event…).

The Z-Wave action “Remove a security user code” is not identifying my Schlage Locks under the MONO 4 build. My setup is as follows:

• Prod Machine: HS3 Build - HomeTroller-ZeeS2 (Raspberry Pi 2)
• Dev Machine: HS3 Build - HomeTroller-ZeeS2V2 (Raspberry Pi 2).
• My z-wave controller is the Z-NET V1.
• Door Locks: Schlage Deadbold Model: BE3619-619

I have attached two images to highlight what I am experiencing:

HomeTroller-ZeeS2 (MONO 3.x) Event: (First Attached Image: HS3-Event-Image-Mono3.png)


HomeTroller-ZeeS2V2 (MONO 4.x) Event: (Second Attached Image: HS3-Event-Image-Mono4.png)



I have rebooted my ZeeS2V2 and Z-Net several times, however, the MONO 4.X Zee Build is not identifying my Z-Wave door locks via the Z-Wave action “Remove a security user code” ....Anyone else experiencing this??

Thanks, Mike

Attached Images
  

Viewing all articles
Browse latest Browse all 4847

Trending Articles