diyjeff

Update after going to 5.8.3; Originally posted on Posted February 25 MOES ZS-B-US2-WH-MS Still is only added as a single node (not 2)

MOES ZS-B-US2-WH-MS https://www.amazon.com/gp/product/B0C4XWW87F/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 On/Off for each switch. EISY does add but as a single node. Toggling only one of the 2 switches is seen in Admin Console. Nothing for the second switch. Toggling the on and off from the AC causes both switches to toggle. The device is available as 1, 2, 3 or 4 switches.

Updated successfully.

I had the same issue. I found that it relates to the PG3 trying to log into the EISY (I currently have no nodesevers). I was able to stop that informational "error" by going to "Node Servers" - "Launch Polyglot V3 (PG3)" and the logging in. Once I did that apparently it now has my id/pw and the "error" goes away. I had a ticket open that covered that issue and when I told Michel what I found, his reply was: "...It makes sense and 100% normal. The reason is that, to make commissioning easier, pg3 authenticates against IoX. This way, you only need one username/pwd. Soon, this will be completely removed as we move communications to mqtt."

Upgrade done without any issues. Removed now phantom node. Everything looks good. Also, did a synchronize and no new nodes appeared. Thanks.

Successfully upgraded to 5.2 with really no significant issues. However a new node appeared on my Kwikset 916 deadbolt; showing as address_140 - Thermostat with a Heat/Cool state? The parent node seems to be working correctly. The nodeInfo shows as: <nodeInfo> <node flag="0" nodeDefId="UZW007D"> <address>ZW073_140</address> <name>ZW 073 Thermostat</name> <family>4</family> <parent type="1">ZW073_1</parent> <type>4.64.3.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>ZW073_1</pnode> <rpnode>ZW073_1</rpnode> <sgid>140</sgid> <custom flags="12" val1="30"/> <devtype> <gen>4.64.3</gen> <mfg>144.1.1</mfg> <cat>140</cat> <model>4</model> </devtype> <ELK_ID>H12</ELK_ID> </node> <properties> <property id="CLIHCS" value="2" formatted="Cooling" uom="66"/> </properties> </nodeInfo> Any ideas? For now I am just ignoring it.

I have periodically tried to see if it will work. I am now on 5.0.15A. Comms are seen in the event viewer, but the status does not change. In my latest attempt, I tried changing parameter 20 (Open/Close Report Method) from the default value of 1 (Notification) to 2 (Basic Set) to 3 (Basic Report). None shows a status change in the admin console. There are different reports in the Event Viewer. With Parameter 20 = 2 Fri 08/23/2019 10:20:05 AM : [ZWAVE-RX ZW043_1] [20/01] Basic Set val=0x00 ACK,AUTO,EXPLORE From=0x2B Fri 08/23/2019 10:20:12 AM : [ZWAVE-RX ZW043_1] [20/01] Basic Set val=0xFF ACK,AUTO,EXPLORE From=0x2B With Parameter 20 = 3 Fri 08/23/2019 10:22:04 AM : [ZWAVE-RX ZW043_1] [20/03] Basic Report val=0x00 ACK,AUTO,EXPLORE From=0x2B Fri 08/23/2019 10:22:17 AM : [ZWAVE-RX ZW043_1] [20/03] Basic Report val=0xFF ACK,AUTO,EXPLORE From=0x2B With Parameter 20 = 1 Fri 08/23/2019 10:26:18 AM : [ZWAVE-RX ZW043_1] [71/05] Alarm Report [0617] Unrecognized Event 0x17 [000000FF06170000] ACK,AUTO,EXPLORE From=0x2B Fri 08/23/2019 10:26:29 AM : [ZWAVE-RX ZW043_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x2B I hope this information helps someone get this sensor working.