Release 5.3.1 Test Build - OUTDATED

[TexMike]

In previous versions I could determine the current value of a Z-Wave configuration parameter. I can't seem to do that in 5.3.1, can it be done?

I finally took the plunge since I had some time today and upgraded my Z-Wave board and ISY firmware. I was hesitant because of my older Kwikset lock, but no major issues have been discovered. Lock reports user codes and no problems with Z-Wave plug status as others have experienced, however mine are fairly new and Z-Wave plus.

Thanks UDI and Merry Christmas

[danbutter]

On 12/23/2020 at 9:29 AM, Michel Kohanim said:

@danbutter,

Right mouse click | Z-Wave | Remove failed node.

With kind regards,
Michel

Thanks for the tip, but I had to try twice. The first time what I got is this:

Worked the second time though!

 

Thanks

[lilyoyo1]

This firmware makes using Yale locks even worse than 5.3. which isnt saying much when compared to 5.0.16. Even after removing the locks and re-adding, there is zero communication. The ISY shows the repeaters connecting to it but no communication at all when it comes to the isy actually seeing the locks.

[btreinders]

On 12/27/2020 at 12:01 PM, lilyoyo1 said:

This firmware makes using Yale locks even worse than 5.3. which isnt saying much when compared to 5.0.16. Even after removing the locks and re-adding, there is zero communication. The ISY shows the repeaters connecting to it but no communication at all when it comes to the isy actually seeing the locks.

I finally had to quit using the ISY altogether for locks.  I now use Smartthings to control them and Webcore to send ST lock status to the ISY so the ISY can announce status through my Elk M1 and update my widgets on my phone.  I have the ISY use IFTTT to send lock and unlock commands to ST since I have not gotten the rest interface working for ISY to ST communications yet.  Not optimal but works way better than the ISY natively.  Mine are Kwikset though.

Edited January 9, 2021 by btreinders

[jdmcpherson]

Schlage locks are no better. I was able to connect to my lock a long time ago but no longer. Advice is always the same - get ISY close to the lock. That is a pain but did it. Even at 2 inches fails.

Edited January 9, 2021 by jdmcpherson
typo

[Bumbershoot]

1 hour ago, jdmcpherson said:

Schlage locks are no better.

I only have one, but it functions under 5.3.1 better than any firmware version to date (it's an old lock, not Z-Wave +).  I wish I understood why there's such a wide variability with peoples experience.

[TexMike]

33 minutes ago, Bumbershoot said:

I only have one, but it functions under 5.3.1 better than any firmware version to date (it's an old lock, not Z-Wave +).  I wish I understood why there's such a wide variability with peoples experience.

Same for me, my old not + Kwikset works great on 5.3.1. I delayed the card and firmware upgrade because I was worried about the lock, but it worked out fine including user codes.

[jeffdoo]

First I am still on the Insteon train and after experiencing flakiness with a six year old PLM I ordered two new ones from SH which arrived today (figured I'd have a backup just in case).

I have followed the instructions to replace the PLM but every Insteon device is unreachable and unprogrammable;  They all have the green "1011" icon indicating write are to be done.  I have also tried resetting a few switches via the ISY Java client without any luck.  I have looked at the PLM Links Table and it only shows the single switch I attempted to perform a restore device, therefore the "File > Restore Model (PLM)" didn't do anything.

Has the procedure changed with regard to restoring a PLM?  

I am using an "old" ISY-994i PRO ... I say old because the system has never accepted the serial number on the back of the unit.

I understand this might not be a 5.3.1 beta problem but as that's what I have installed I figured I would start here.

The new PLM state they are Revision 2.6 4520 and I have tried both.

I have also tried two CAT5E cables (< 6 ft) and a CAT6 (6 ft) cable just to eliminate the cable as an issue. 

Thanks!

- Jeff

Edited January 15, 2021 by jeffdoo
Added PLM revision/cable.

[lilyoyo1]

Nothing's changed. What were the steps that you took? 

[oberkc]

Just to be sure...does your ISY show the PLM as "connected"?  (TOOLS>>>DIAGNOSIS>>>PLM INFO/STATUS)

 

[MrBill]

13 hours ago, jeffdoo said:

First I am still on the Insteon train and after experiencing flakiness with a six year old PLM I ordered two new ones from SH which arrived today (figured I'd have a backup just in case).

I have followed the instructions to replace the PLM but every Insteon device is unreachable and unprogrammable;  They all have the green "1011" icon indicating write are to be done.  I have also tried resetting a few switches via the ISY Java client without any luck.  I have looked at the PLM Links Table and it only shows the single switch I attempted to perform a restore device, therefore the "File > Restore Model (PLM)" didn't do anything.

Has the procedure changed with regard to restoring a PLM?  

I am using an "old" ISY-994i PRO ... I say old because the system has never accepted the serial number on the back of the unit.

I understand this might not be a 5.3.1 beta problem but as that's what I have installed I figured I would start here.

The new PLM state they are Revision 2.6 4520 and I have tried both.

I have also tried two CAT5E cables (< 6 ft) and a CAT6 (6 ft) cable just to eliminate the cable as an issue. 

Thanks!

- Jeff

did you plug the PLM in first, wait 30 seconds or so, then plug the ISY in?  the only time the ISY checks for a different PLM is during the boot process.  If the ISY was no rebooted it won't work.  the first thing After that the next step must be Admin Console > File > Restore Modem (PLM) which may take awhile to complete it's task depending on how many devices you have.

[jeffdoo]

lilyoyo1, oberkc, and MrBill,

Thanks to all three of you for the responses!

The ISY and new PLM are pretty much working fine as of this evening.  Very late last night after lilyoyo1's reply I unplugged the ISY, PLM, and started again documenting each step.  I again observed things just simply failing for no clear/obvious reason so I decided to try moving the PLM to a circuit just outside the server closet using an extension cord and it started working but wasn't perfect (pretty much all keypads failed to be programmed).  This morning unplugged the ISY, PLM, reset the PLM, and plugged everything back in but in our guest/spare room as it is the most electrically silent and has ethernet jack available.  Fired everything up and started the restore process which resulted in only three devices failing to be reprogrammed and some being programmed incorrectly (i.e.; Ramp rate set to 9 minutes).  A number of devices I had to perform an individual device reset because they would respond to off command but not "on".   As of this moment there are only two switches left in the dining room which refuse to respond to the device reset but no error is displayed.  I moved a repeater from the foyer to the dining room but it didn't make a difference.  I will continue to work on it tomorrow....

I do see a UI issue where I see "garbage" between the "Beep" button and value which I do not recall and it is not present on all devices:

 

Thank you again for the quick responses to help!

  - Jeff

 

 

Edited January 16, 2021 by jeffdoo

[Scyto]

When i add a 2852-222 leak sensor it asks me for a device name.

The wet and heartbeat nodes get named with the name I give it (with the right suffix)

The dry node is named '2D.5D.1B - dry' as an example.

No biggie as one can rename, so just FYI.

[WFP]

At some point, all FOUR of my Schlage BE469ZP locks have become "generic" nodes.  Instead of reporting locked or unlocked, they have ON and OFF as the status.  When I do a Z-Wave "Show Info" in Event viewer, it appears to report correct info for a Lock.

[WFP]

Also, the FOUR locks are NOT available in the dropdown menu for a program when setting a THEN command to SET a device.

[WFP]

Z-WAVE>SYNCHONIZE NODES>ALL seems to have brought them back...still ODD!

Bill