junkycosmos

hi @Nitemare - are you 100% sure that our locks are BE469ZP and not BE469v5.8 ? Reason I ask is that your comment of only getting a single entry, no control for the lock on EISY but worked fine on ISY is the exact same I am running into with my BE469v5.8 Also I tested a BE469ZP unit and they add into EISY fine, it asked for ZP security code, adds multiple nodes as expected. After that does require additional steps after enrollment of turning on compatibility, turning off confirmation, and rewriting links (see several posts above). I can understand how people are likely confused on which version of the BE469 the might have (as the locks look identical on the outside of the units) AND most retailers just started selling the new version w/o much notice.. BE469v5.8 = S0 device, worked on ISY994 v4.9 older Zwave board, when attempting to add into the EISY the EISY does not ask for security code, removing battery cover of the lock there is NOT and enrollment button (instead Zwave enrollment is done by typing 8 digit code then 0 on the lock keypad BE469ZP (Zwave Plus)= S2 device, does NOT work on ISY994 running v4.9 (might work on V5.x not sure), when attempting to enroll on EISY will ask for Secure code (code is sticker on part of lock that mounts to door that holds outside keypad on -remove lock to see it), to enroll the lock there is a button under the battery cover. Please reply back to confirm which version you have. Also if you have other examples in forum of those stuck getting the single node you mentioned and can easily find pls reference here. thx cheers

Sure .. agreed the newer Zwave Plus stuff has security. Those add to EISY with S2 while the non security devices add as S0. These BE469v5.8 are before z wave plus was a thing and add as non secure. The ISY994 v4.9 was indeed non secure non zwaveplus (on the 1st non beta board) .. and the BE469v5.8 are very happy there. Now onto EISY where S2 (secure) and zwave plus is the norm.. however it does claim support older non secure S0 enrollment or at least it tries to and has options to …but that is crux of the space I’m stuck in. Given roll out timing of EISY and when Schlage updated their own BE469 models from v5.8 to ZP (zwave plus) years ago .. I really suspect most users and testing probably skipped this use case (older be469v5.8 on EISY). Also most on forum posts on Schlage in EISY all focus on lack of status change alerts .. which again confirms those users were on BE469ZP - since we know fix for that (in post) At least the EISY is not asking for s2 code on the be469v5.8 and does start the interview, but then it fails to communicate properly with the lock and enrollment fails.

thanks @firstone - indeed had not thought of going the Home Assistant route to try enrolling my BE469v5.8. Thank you for the idea. Noted this same lock enrolls great on ISY994 v4.9 and runs well (last 10rs have 9x of them at this location). So the variables here are EISY Zwave board and V5.8.... and my existing network. While I do understand these locks are older (ie when Zwave really stabilized), since they run fine on ISY994 v4.9 this seems to be an issue of incompatibility how the EISY Zwave board, v5.8 or how it is implemented or something on existing network (largest variable). The existing Zwave network does have 30 or so devices some of which are S0 repeaters for the other locks. My original plan was to completely wipe the ISY994 v4.9 Zwave network and re-enroll everything "clean" on the EISY v5.8. Did one lock to "test" on EISY before wiping all from ISY994 so I could roll my migration back .. and hit this road block. I did do an exclude on ISY994 for this lock, then powered down the ISY994 .. but back of my mind I am wondering if the other devices and repeaters (still enrolled with ISY994) could be interfering with the ESIY enrolling this lock. Suppose I could remove this lock from the door, take it and the EISY to middle of a quiet parking lot, then try the enroll process .. kinda a pita. Appreciate the Home Assistant Idea - would need to pick up a Zwave USB dongle which is no big deal. J

sharing update so far .. it has been bit of a slow process of back and forth on the ticket with support - did just get lower level Zwave logs back to support during attempt at re-enrollment, hoping Chris finds something useful... So far no progress to report on the older Schlage BE469v5.8 - to EISY we tried increasing the interview timeout to 1 minute / the lock still only enrolls on EISY as 1 node with no functions available. Really does appear to be some issue with ESY on 5.8.4 and the older BE469v5.8, noting that these do and have worked fine on the ISY994 over the past 10yrs (with older zwave board) and on 4.9.0. In other words the variables here are 1. ISY994 Zwave board to EISY Zwave /Matter board , 2. going from ISY v4.9.0 to ISY 5.8.4 (on EISY). Locks are in same location, ISY & EISY are in same location.. I did find this older forum posting that references similar sounding issue from Jan of 2023 and reference to a fix due in Feb, not sure how to confirm that was fixed .. For clarity sake the newer Schlage be469zp (zwave plus) unit I setup as a test lock is still working well on EISY after the suggestions made above by @kandlg (compatibility mode on, confirmations off, re-write all links) - this post is all focused on the older be469v5.8 - original schlage locks us early zwave users were rolling back at the start .. thx

Anyone else run into this .. I'm kinda embarrassed it took me a few cycles to try integrations of the capital for Admin / this is a new EISY on 5.8.4 (bug? = user capitalization here fails login .. must be in lower case for ssh but not for PG3 or Admin) 1. IoX admin console login admin/admin = FAIL Admin/admin = pass 2. Polygolt dash https://192.168.1.##:3000/dashboard admin/admin = FAIL Admin/admin = pass 3. ssh either local or via IP ssh Admin@192.168.1.## / admin = FAIL ssh admin@192.168.1.## / admin = pass Yes, I tried a reset of Admin user and password via Admin consul setting to User ID of Admin/ password of admin

@kandlg - thank you very much for the post here. Indeed your note added 2 steps that I had not tried before of steps 2 and 3. Doing all three here now I can indeed see local status changes made on the new BE469ZP lock on the Admin and they trigger programs too. so fix for BE469ZP to function as expected on eISY 5.8 (where the lock adds as S02) are to .. 1) right+click Z-Wave | Compatability Mode ON 2) right+click Z-Wave | Validation | OFF 3) right+click Z-Wave | Rewrite All Device Links Also noted that IF someone wants to change their lock to use a 6 digit code instead of a 4 digit code then set Par number 16 to 6 - (lock now takes 6 digit user codes locally OR via users button on eISY Admin consul) This is great as it gives a way forward for most users here who have BE469ZP. <<wonder how this type of info can be on WIKI vs bit buried here in the forum>> ? Does still leave some of us with the question BE469 v5.8 (the units pre ZP) that were used on ISY994 pre 500 ZW boards - older units. When I had tried to add them into eISY from the 994 by removing/then re-adding them things were very messy. I do have a ticket open with Support in hopes they have a path forward that does not involve replacing all my locks at this time. thx J

Coming from ISY994 on 4.9 to EISY on 5.8.4. Been trying to troubleshoot why many of my programs are failing to "Send Notification". In troubleshooting I've torn down a few of the example programs to the only action be "send notification", then I am testing with right click run then. 3 issues - 2 fixed but appear to be as a result of the my migration from ISY 4.9 to eISY 5.8 so maybe migration bugs, 1 issue outstanding which is livable but could use confirmation / checking by others or if something unique to me here .. all three potentials to cause others issues on migration. Issue #1 - Text to SMS/MMS from EISY not working / Group Name needing to be renamed .. Understood it can have issues and sometimes it does but at of this moment I have my ISY994 and my eISY both up, both targeting same address via same mail server an 1 works while the other does not at all. - notification test from eISY to phone works fast shows up - GOOD (this is group ID 4) - have isolated program with no other condition or action other than "Send Notification" to test by right clicking - tried with the content of "Default Template" and my newly rebuild template (see #3 below) - both fail - target is ##########@mypixmessages.com - only has 1 address in this group - recreated a new group (group ID10) for this target phone (was in its own group before) .. and that fixed it .. umm, wow .. - went back to my original group and deleted the recipient, clicked ok, went back into the group, added same exact address back in, closed and hit save at bottom - did not fix it .. so issue here is that the same exact target address in to new group ID10 works while in the old Group ID4 it does not. - When to Group ID4 name = 17 characters long and edited the name - it started working - ok .. wow .. , originally shorted to 15 characters but later changed back to my exact same name it had prior and all has stayed functional. So the fix appears to be related to something in in the group name needing to be edited/changed and then resaved. . ******************************** Issue #2- Send Notification FAILS If Program Names over 31 Characters - Seems there is some new limit or something that breaks which used to work extremely fast on ISY994 (really silly fast as in 1-2sec) I have checked that both the ISY994 and ESIY is using same mail server / password - (not that is should matter) Testing has lead to show that IF a program name is over 31 characters the mail never shows up however, if the program name is 31 characters or less the mail shows up right away. These are both using the Default Template... Example programs 31 passes / 32 character name mail never shows PASS Program Name is 31 character OK - [ID 00DA][Parent 00A6] If Then Send Notification to 'J_Email' FAIL Program Name is 32 character BAD - [ID 00D7][Parent 00A6] If Then Send Notification to 'J_Email' ******************************** ******************************** <Fixed>Issue #3 - EISY is not sending any notifications to email that use my custom template from ISY994 - / new ISY uses slightly different context in the alert variables... Old Customization Template on ISY994 4.9 Subject: ISY ${alert.program.name} Body: ${alert.event} at ${alert.date} ${alert.time24} FIX = recreating my template as the subject format changed when moving to EISY 5.8.4 Subject: ISY ${sys.program.#.name} Body: ${alert.event} at ${alert.date} ${alert.time24}

Found the Configuration Parameters sheet for Schlage BE469ZP - need to convert to dec for ISY use but can do via Set Configuration Button on the node in 5.8.4 - example to change user code length to 6 digit set Par number 16 to 6 - lock now takes 6 digit user codes locally OR via changing on Admin consul. However now that I have user codes working I am running into what was reported in that thread I referenced from Jan 2023, status of the lock does not appear to change on Admin consul when the a user code is entered or the knob is turned manually to lock or unlock... ...maybe what was noted as "a fix coming soon never came ?" or perhaps something else I am missing .. 24352403.pdf

Found a Schlage b469ZP (newer z-wave plus model) in garage to test with - its a new unit but prob 5 yrs old. I found when adding it to 5.8.4 the only option is to add as S2 via code. So this would indicate what I bet some of you already know::: Schlage BE469 v5.8 (older non Z-wave plus) worked well in v4.9 ISY but seem to have trouble on the new 5.8 on Z-Wave Matter board- these would appear to be adding as S0 since ISY does not prompt for ZPlus code .. maybe someone can chime in here with more of a test set as I only sacrificed one of my locks from v4.9 to test on ISY v5.8.4. This is the lock I tried before my 1st post with strange mixed results.. Schlage BE469ZP (newer z-wave plus) - cannot be added to ISY v4.9 (needs v5.4+) - tried that long ago - but does add into ISY 5.8.4 however the interview process has issues, the lock has 2 nodes with the 1st adding quick and 2nd hanging. Furthermore there appear to be some missing features lost when moving from ISY v4.9 to v5.8.4 (see Qs below) / Also the lock is forced to add as S2 via code (i.e. cannot go fall back to using as S0 if we wanted) I can report that when locked and unlocked manually or via UD Mobile the locked / unlocked status does seem to report on UD mobile (I did not try triggering program). so there are some key missing items .. Q1- how do you set access code length now ? (in 4.9 you had an option button on the lock node in ISY which seems to be missing in 5.8.4) <attached pict> Q2- also how do you setup the programs to alert when a specific user code unlocks the lock ? On 4.9 the program of this worked great but on 5.8.4 I see no option to set more then generic lock/unlock <attached pict> as example .. **former program in 4.9 that has worked great to alert when specific user code was used on any of the locks** Lock Unlock by J - [ID 001E][Parent 002B] If ( Control 'Locks / Bedroom Deck Door' is switched Unlocked by Keypad And Status 'Locks / Bedroom Deck Door' is Access Code 1 ) Or ( Control 'Locks / Down Patio Door' is switched Unlocked by Keypad And Status 'Locks / Down Patio Door' is Access Code 1 ) Then Send Notification to 'J_All' content 'MyTemplate' Maybe I am missing something not so obvious here on 5.8.4 on how to accomplish this ? Clearly I am new to eISY and ISY 5.x but have been kicking around here since isy99i .. thx for any help. The BE469 v5.8 have worked well for over last 10yrs so I suppose we could replace them if that is the best route. If anyone has suggestion on what locks might fit my needs here the reqs are as follows. keypad locks with codes that can be changed from ISY deadbolt lock only but can lock/unlock by remote can trigger program (ideally variable) on ISY that sends notification via specific user code (the BE469 v5.8 do this) decent battery life (we get 6-18 months from our 4aa in BE469 v5.8 quantity x9 - ouch

Having trouble moving my Schlage Be469 v5.8 (non Z-wave Plus) locks from ISY994 to Zmatter/ZWave. These are older locks (9 of them) that have worked near flawlessly with ISY994 on older Zwave board .. today moved over to EISY and having trouble with Zwave. Did not migrate my Zwave network as I know the links and such are hairball old. So far working with only 1 lock so I can roll back to ISY if needed .. on that 1 lock I did a factory reset. Then an exclude (worked) then did an include and eISY stuck on interviewing 2 (as seen in event viewer) for 15 mins. Restarted eISY and then did another exclusion and re-add. This time I have a device listed but has IOIOI with writes missing to it. Tried remove and re-add again and this time lock fully added but programming and control is not functional although ISY event viewer thinks successful. Is my old too old ? This is a Schlage Be469 v5.8 (non Z-wave Plus) .. ? IF so .. before I buy 9 replacement locks can someone confirm if the eISY firmware was actually fixed to fully see S2 updates from the newer Schlage Be469 ZP models .. as noted in the thread here below from Jan 2023 ? Was this confirmed as fixed ? Cannot add Schlage BE469 to Polisy w/zwave zmatter board (thread is old and closed so cannot ask there)

ah ok so I figured out that the "up time" is purely a java counter so that pulled from my browser cache after restart // even though I had closed browser and thought I cleared cache .. but this cleared after a few page navigations on the PG3 / now shows correct uptime of 21 mins .. Would still be nice to post proper way to restart PG3 when you cannot login / or is yanking power really best way ??? Also .. next newbie Q, please.. how to set proper time in PG3 (the log files are all 2 hours off) was the ISY had been due to default time zone which I change 10mins back .. however seems updating time zone (time offset) in ISY does not flow over to PG3 ? thx

Just had what seems to issue others have hit where they could not login to the Polyglot 3x web page at https://192.168.1.53:3000/dashboard - was getting error 503 as if my pass was bad / tried resetting via admin consul but no effect after searching on how to gracefully restart eisy to no avail I yanked power for 15 seconds then plugged in again (some easier answer maybe ?) .. Good news is that after 2 mins I could login again with my credentials of admin/admin . (same I had been using 2 weeks ago last I started testing out my new eisy) .. Interesting news is that my portal page shows uptime of roughly last time I was using eisy / kinda expected to see this at 2 mins vs 2 weeks since the eisy was just unplugged for 15 seconds ..

thank you @IndyMike for all the testing and tables here ! Also @Techman for the heads up about Steve. As reference my boated (as in too many devices) Insteon / Zwave does pretty well overall. The ALL-ONs which started for me many years ago have greatly reduced as I have dropped out many of my batt devices. I am down to having 1 every 1-2 months typically. I have put numerious work arounds in place to ensure the ALL ONs do not cause significant issues. Some examples include removing/readding the TSTATs when in auto mode with moderate temps set (since the ALL ONs sometimes cause the TSTATs to bounce to whatever they were at when included in ISY), replacing I/O lincs I had on skylights and furnace zones with mimos, replacing key switches with ones, few others over past 8yrs I am not recalling at the moment. I also created ALL ON and ALL OFF "detectors" with 2 seperate i/o lincs - wiring the relay to sensor input of each unit then leaving relay in state which would be toggled by the signal and lastly setting program that sends a warning text when changed. The phantom signals always impact the relay and not the sensor but you can use the sensor to "reset" the detector. Silly that I never tested the ALL ON button from ISY devices page - wondering if that does same as the protocol "crash" or whatever we call it that creates the phantom ALL ON ? I can also report that SwitchLinc Dual-Band Relays starting with 46.xx.xx.xx do not react to all ons

Long time back we know SH adjusted the Firmware in switches to no longer listen to the ALL ON signal. This appeared to be a remedation attempt fixing the Phantom ALL ON events those of us with larger networks started to see when using battery powered devices and dual band devices. Hope you are GREAT. Can you please remind me what switchlinc dimmer firmware SH removed the ALL ON response.I know the2476D SwitchLinc Dimmer v38 is impacted/still responds to the phantom ALL ONand that2477D Dual Band SwitcLinc Dimmer v.45 ignores / does not follow thephantom ALL ON signalshowever I cannot recall which firmware it was removed from ..anyone know for sure?Seems my v.40 Switchlinc Dimmers are impacted (still respond to) however not sure on the v.41 and v.44 Dual Band SwitchLinc Dimmers.thanks J

curious here too as I am in same boat for cabinet vs where my PLM is located .. great idea on the USB extenders