JeffR

@gzahar Thank you for the assist! Worked for me as well.

I have this lock and it has never relayed status on manual lock\unlock events. I use a YoLink door sensor and when the door closes a program queries the lock in 5 minutes and updates the lock status. If you unlock but don't open\close the door the status will be incorrect. Periodically querying the lock for its status will probably not be good for battery life. Below I unlocked manually and nothing showed up in the logs. I then ran a query, which returned unlocked for the status, and then I clicked lock in the EISY and the results are shown below. The command was successfully executed and the status was changed to locked. Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00161 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00162 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:20 PM : [ZW-TX-A 00163 2.0 ] [ZY002_1] Battery Get Sun 05/12/2024 12:01:21 PM : [ZW-DONE 00161 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:22 PM : [D2D EVENT ] Event [ZY002_1] [ST] [0] uom=11 prec=0 Sun 05/12/2024 12:01:22 PM : [ZY002_1 ] ST 0 (uom=11 prec=0) Sun 05/12/2024 12:01:22 PM : [ZW-DONE 00162 2.0 ] [ZY002_1] Door Lock Config Get Sun 05/12/2024 12:01:23 PM : [ZW-DONE 00163 2.0 ] [ZY002_1] Battery Get Sun 05/12/2024 12:01:27 PM : [ZW-TX-A 00164 2.0 ] [ZY002_1] Door Lock Set mode=255 Sun 05/12/2024 12:01:29 PM : [ZW-DONE 00164 2.0 ] [ZY002_1] Door Lock Set mode=255 Sun 05/12/2024 12:01:35 PM : [D2D EVENT ] Event [ZY002_1] [ST] [100] uom=11 prec=0 Sun 05/12/2024 12:01:35 PM : [ZY002_1 ] ST 100 (uom=11 prec=0)

I have the same problem with the BE469ZP. I have a Yolink open/close door sensor and a program that waits 3 minutes after the door status changes to closed to query the lock. I programmed the lock to auto-lock so this updates the lock status and battery level in EISY. Someone else posted this idea in the forum and it's the only thing that works for me. These locks are quite expensive so it's disappointing we can't get status updates from them.

Same here...Thank you!

Same problem as the others and EISY is current on everything. Yo-Link did upgrade to 0.9.63, but is disconnected. I agree Yo-Link and this Node server are great to have.

I ordered a Smartwings full blackout shade yesterday as a trial. Based on this discussion it appears connection and control with the EISY will be smooth. I bought a remote but probably won't need it with UD Mobile. I'll report back on mine after I receive it, but these shades sound promising. Customizations: Create a New Custom Size Mount Type : Outside Mount Custom Order Width : 36" Width Fraction : 1/2" Custom Order Height : 47" Height Fraction : 1/4" Reconfirmation : 36 1/2" W x 47 1/4" H Contact Information : Motor Remote Power Motor Type : Motor work with Z-wave Smartwings Smart Link : Not Required Remote Controller : 5-Channels Remote Solar Panel : Not Required Valance Cover : Cassette with Fabric Insert

Ordered mine a while back and finally received it Monday. Same upgraded hardware note and Rev 2.6 1223. Replacement went smooth including leak sensors and motion sensors. Keypads I had to do Restore Device for some reason, but everything is now up and responding in EISY.

Michel determined 5.5.4 has a bug to fix. My Admin password had a $ in it and once we changed that everything came back online. It was a very strange issue and even took a while for him to track down but all is good now.

I was having issues with LifX so decided to upgrade to 5.5.4 \ 3.1.20 yesterday morning. I now have the red screen problem in PG3 so I'll issue a ticket. I've tried all the regular fixes - update packages again, power cycle, flush cache, different PC, etc. It appears the ISY UUID can't be found or manually added and related to auth.ns Jan 21 10:12:15 eisy daemon[69112]: 1/21/2023, 10:12:15 [pg3] ^[[31merror^[[39m: Getting IoP UUID failed: Error: connect ECONNREFUSED 127.0.0.1:8080 Jan 21 10:12:15 eisy daemon[69112]: 1/21/2023, 10:12:15 [pg3] ^[[31merror^[[39m: Is the IoX service enabled? The IoX service must be enabaled for PG3 to start. Jan 21 10:12:15 eisy daemon[69112]: 1/21/2023, 10:12:15 [pg3] ^[[32minfo^[[39m: PG3 shutdown complete with code: 0 Jan 21 10:12:31 eisy daemon[69112]: 1/21/2023, 10:12:31 [pg3] ^[[32minfo^[[39m: Starting PG3 version 3.1.20 Jan 21 11:03:48 eisy daemon[2441]: 1/21/2023, 11:03:48 [pg3] ^[[32minfo^[[39m: Making reqeust to socket for /rest/pg3.auth.ns Jan 21 11:03:48 eisy daemon[2441]: 1/21/2023, 11:03:48 [pg3] ^[[31merror^[[39m: uncaughtException: socket hang up Jan 21 11:03:48 eisy kernel: pid 1332 (udx-freebsd-x64), jid 0, uid 0: exited on signal 11 (core dumped) Jan 21 11:03:48 eisy daemon[2441]: Error: socket hang up Jan 21 11:03:48 eisy daemon[2441]: at connResetException (node:internal/errors:711:14) Jan 21 11:03:48 eisy daemon[2441]: at Socket.socketOnEnd (node:_http_client:518:23) Jan 21 11:03:48 eisy daemon[2441]: at Socket.emit (node:events:525:35) Jan 21 11:03:48 eisy daemon[2441]: at endReadableNT (node:internal/streams/readable:1359:12) Jan 21 11:03:48 eisy daemon[2441]: at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Jan 21 11:03:48 eisy daemon[2441]: 1/21/2023, 11:03:48 [pg3] ^[[31merror^[[39m: uncaught ECONNRESET exception: Error: socket hang up Jan 21 11:03:48 eisy daemon[2441]: at connResetException (node:internal/errors:711:14) Jan 21 11:03:48 eisy daemon[2441]: at Socket.socketOnEnd (node:_http_client:518:23) Jan 21 11:03:48 eisy daemon[2441]: at Socket.emit (node:events:525:35) Jan 21 11:03:48 eisy daemon[2441]: at endReadableNT (node:internal/streams/readable:1359:12) Jan 21 11:03:48 eisy daemon[2441]: at process.processTicksAndRejections (node:internal/process/task_queues:82:21) Jan 21 11:03:48 eisy daemon[2441]: 1/21/2023, 11:03:48 [pg3] ^[[32minfo^[[39m: Caught SIGTERM/SIGINT Shutting down. Jan 21 11:03:48 eisy daemon[2441]: 1/21/2023, 11:03:48 [pg3] ^[[32minfo^[[39m: Stopping running node servers...

I have the same issue on eisy v5.5.3 \ v3.1.18. I assume since the auto discovery fails the DB object is never correctly created. I added a devlist file using the serial number for mac as recommended for firmware 3.7+ and the node is created. Unfortunately the status is always shown as offline and commands always fail. I created static addresses in my router since mac and serial numbers are no longer the same. 2023-01-14 14:17:10,559 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address d073d56ade00 does not exist. {'address': 'd073d56ade00', 'cmd': 'DON', 'query': {}}