TSinclair

Clever programing workaround. I wonder if moving the ZEN51 to the fan junction box would help? Also, another use case for the ZEN 51 is to make an existing switch smart (without the wife noticing).

For your 3-prong devices, I've had good luck with both the Zooz ZEN04 and ZEN05. I used several ZEN05s for outside Christmas lights; I was impressed that they worked flawless even being roughly 100' from the nearest Z-Wave device.

Well I just upgraded to 5.5.6 which went flawless. File>Themes>Theme Size>3 is PERFECT! Thank you UDI!

Me too. Even PG3 came back up with just a System>Restart Polyglot 3x.

I saw that. Not sure if this was in the pipeline or if it's evidence of UDI monitoring this forum and listening to feedback, but BRAVO either way. Now, after the 5.5.5 pain, there is no way I'm upgrading to see how this works until I see positive feedback overall!

We are taking a similar approach with the ZEN32 and a separate folder for all of the extra nodes. What made my ZEN32 scenario a bit challenging is I am using 3 of the 5 buttons to control ~8 lights/lamps in the Family room, effectively high, medium, low or Movie, TV and Bright. A press on any any of those 3 buttons determines the current state, turns on the appropriate brightness, and turns on the appropriate LED and turns off the LED on the other buttons. So for example if the current state is medium and the high button is pressed the program turns off the medium button LED and turns on the high button LED and adjusts the lights. I should add that this was unworkable with the 994 as it took 3-5 seconds for the lights to respond to a button press and 8-10 seconds for the button LED change to occur. With eisy the lights are instantaneous and the LED change is in a second or two.

As I have migrated to eisy, I've tried to be organized and specific in my device and program naming. HOWEVER, the issue this has created is now some of the device names are too long to fit into the space of the drop down menu in programs (see screen print). By chance is there a way to see the full device name or a work around? Thanks in advance.

Partial success. Got PG3x node servers connected after upgrade, but not the portal occupancy node server...it says not configured. any guidance appreciated.

Nevermind. The issue seems to have resolved itself. Now showing "connected".

I've noticed this morning that UD mobile is constantly trying to "restart connection" (see screenshots). Oddly when I query a device it updates the status on that device, but none of the statuses are updating automatically. Thoughts?

Success!! With Michel's help, this was solved by deleting the NS, removing it from IoX, logging off PG3, and then reinstalling. I had done this a couple times, but left off the step of logging out of PG3 before reinstalling.

Unfortunately 3.1.18 did not resolve it. Same behavior; TCP client request failed [ISY:401] and error below on PG3 log 1/5/2023, 20:51:48 [pg3] error: ISY Inbound Status: UnauthorizedError: Unauthorized at Object.throw (/var/polyglot/node_modules/koa/lib/context.js:97:11) at checkAuth (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:29:56) at getNodeserver (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:39:11) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:148:16 at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9

Having just set up my eisy, I experienced the "no device control" as well. The only thing that worked for me was restoring a backup from before the device control "freeze". It happened twice to me after several hours of investment. It seems you are adding insteon devices, so not sure if the issue is the same, but my solution was to perform a backup after adding a few devices (I added about 50 Z-wave devices). At least for me it was after the Z-Wave add process that the device control would freeze. I could see the device I last added, but would not be able to control any of them. Restoring the last backup and then readding devices worked for me.

Nevermind. It took a couple restarts, but I'm up and running!

I'm new to Node Servers but here is what I am experiencing. I was able to connect the harmony hub node server to eisy. I see all of my devices/automations when I execute a command from the "main" tab for a device, I get "TCP client request failed [ISY:401] when I execute a command from a program, nothing seems to happen for either scenario I see the below on the PG3 log What have I done wrong? 12/29/2022, 20:57:12 [pg3] error: ISY Inbound Status: UnauthorizedError: Unauthorized at Object.throw (/var/polyglot/node_modules/koa/lib/context.js:97:11) at checkAuth (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:29:56) at getNodeserver (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:39:11) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/Node Server.js:148:16 at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9

I'm going from 994 to eisy so I am new to this. I've set up a couple node servers so far, but I cannot seem to get this one to connect. I should add that I have been using DSCLink for years, but excited about running this on eisy. I have populated hostname, password and usercode but cannot get it to connect. I can see it "installed" on eisy, but in PG3 the status is disconnected. Below is the log after hitting "restart" 12/29/2022, 20:34:34 [pg3] info: [] Retrieved customparams 12/29/2022, 20:34:34 [pg3] info: [] Retrieved customtypeddata 12/29/2022, 20:34:34 [pg3] info: [] Retrieved oauth 12/29/2022, 20:34:56 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:24 [pg3] warn: stopLogging: unwatch failed, TypeError: Cannot read properties of undefined (reading 'pg3frontend_VPABX') 12/29/2022, 20:35:27 [pg3] info: [] Retrieved customparams 12/29/2022, 20:35:27 [pg3] info: [] Retrieved customtypeddata 12/29/2022, 20:35:27 [pg3] info: [] Retrieved oauth 12/29/2022, 20:35:28 [pg3] info: [EnvisaLink-DSC(1)]: Restarting Node Server 12/29/2022, 20:35:28 [pg3] info: [EnvisaLink-DSC(1)]: Stopping Node Server 12/29/2022, 20:35:28 [pg3] info: Making reqeust to socket for /rest/pg3.stop.ns 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:30 [pg3] info: Starting log stream for pg3frontend_VPABX :: /var/polyglot/pg3/logs/pg3-current.log 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC is valid 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: checkLicense:: EnvisaLink-DSC Valid perpetual license found. 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC finished update check 12/29/2022, 20:35:32 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted) 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC starting polls 12/29/2022, 20:35:32 [pg3] info: Starting Node Server Info timer 0 12/29/2022, 20:35:32 [pg3] info: startNs:: EnvisaLink-DSC updating database (enabled, timestarted)

I may be premature to ask these questions, but I’ve been limping along the last 4 months on my 994 since the PLM died, so I am definitely overanxious for eisy’s arrival and my brain has moved into planning mode! At issue is since ditching Insteon, I’m now at roughly 50 Z-Wave devices, my ISY randomly goes into “system busy” 15 or so times a day, which has a noticeable and detrimental impact (to my wife especially who cannot tolerate turning on a switch when the pantry or other light doesn’t come on automatically, although it is also annoying for me when I get home to find the pool equipment didn't turn on). Without going into my theories, and efforts to diagnose and remedy, I want to set up eisy from scatch, fully recognizing the time/effort involved (~100 programs). The question is what do I need to do with my Z-Wave devices? Do I have to exclude them all from ISY before I retire it and bring eisy online? And would this require uninstalling the switch/device to bring it close to ISY? Or would I have to uninstall them anyway to add them close to eisy? Do I need to factory reset each Z-Wave device? Does a factory reset take the place of “excluding” on ISY? And lastly is possible or harmful to keep ISY and eisy both online at the same time to gradually move devices from ISY to eisy, or is this an all at once thing? The bottom line is I want to make certain I follow the best practice so I start with a pristine environment for eisy.