MWoods329

Thanks for the quick response. After getting it up in Putty, I tried to log in once at 12:58:52 then just sat and let the log collect. Here it is: [admin@eisy ~]$ tail -f /var/polyglot/pg3/logs/pg3-current.log 1/16/2023, 12:54:34 [pg3] error: No code in error response 1/16/2023, 12:54:34 [pg3] warn: ISY Response: [Try: 3] [00:21:b9:02:61:30] :: [4 01 - OK] :: 0.844769ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 12:54:34 [pg3] error: No code in error response 1/16/2023, 12:54:34 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:21:b9:02 :61:30] :: [401 - OK] :: 0.691158ms - http://127.0.0.1:8080/rest/profiles/ns/0/c onnection 1/16/2023, 12:54:34 [pg3] error: Error: GET http://127.0.0.1:8080/rest/profiles/ ns/0/connection Failed :: 401 - OK 1/16/2023, 12:54:34 [pg3] error: getExistingNodeServers :: Error: Received no re sponse from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevic es/pg3x/lib/modules/isy/system.js:93:13) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy. js:80:21 at async Promise.allSettled (index 0) 1/16/2023, 12:54:34 [pg3] warn: verifyNodeServers (00:21:b9:02:61:30) :: ISY has no node servers installed, skipping 1/16/2023, 12:58:52 [pg3] info: Making reqeust to socket for /rest/pg3.auth.ns 1/16/2023, 12:59:07 [pg3] info: Starting PG3 version 3.1.18 1/16/2023, 12:59:07 [pg3] info: Using Workdir /var/polyglot/pg3/ 1/16/2023, 12:59:07 [pg3] info: Starting sqlite database at /var/polyglot/pg3/pg3.db 1/16/2023, 12:59:07 [pg3] info: Encryption key found ID: c988d8b4-31c6-44d6-9416-48a969d717ee. Database version 1 1/16/2023, 12:59:07 [pg3] info: Query IoX for platform UUID. 1/16/2023, 12:59:07 [pg3] info: Loaded globalsettings successfully. Database version 1 1/16/2023, 12:59:07 [pg3] info: isy table: Loaded (1) successfully 1/16/2023, 12:59:07 [pg3] info: ISY: 00:21:b9:02:61:30 5.5.3 127.0.0.1 2b43b97d-a0ed-4235-b40a-a6488def4e87 1/16/2023, 12:59:07 [pg3] info: No node servers in database. Add one through the user interface to get started 1/16/2023, 12:59:07 [pg3] info: store is up-to-date 1/16/2023, 12:59:07 [pg3] info: Forcing custom certificates to off 1/16/2023, 12:59:07 [pg3] info: Updated configuration with overrides 1/16/2023, 12:59:07 [pg3] info: Reading certs from filesystem (UDX). 1/16/2023, 12:59:07 [pg3] info: UDX Services Starting 1/16/2023, 12:59:07 [pg3] info: Starting update check 1/16/2023, 12:59:07 [pg3] info: Started MQTT Client Service 1/16/2023, 12:59:07 [pg3] info: Creating ISY queues for 00:21:b9:02:61:30 1/16/2023, 12:59:07 [pg3] info: HTTP Queue response "Queue Created Successfully," 1/16/2023, 12:59:07 [pg3] info: Starting event listeners 1/16/2023, 12:59:07 [pg3] info: Starting Store Poll Refresh timer 1/16/2023, 12:59:07 [pg3] info: Starting ISY verification. 1/16/2023, 12:59:07 [pg3] info: Query ISY description at http://127.0.0.1:8080/desc 1/16/2023, 12:59:07 [pg3] info: Query store database https://pg3store.isy.io/v2/list 1/16/2023, 12:59:07 [pg3] info: Koa HTTPS Interface Service: Started - Address: 0.0.0.0 Port: 3000 1/16/2023, 12:59:07 [pg3] info: Checking ISY's for installed node servers... 1/16/2023, 12:59:07 [pg3] error: No code in error response 1/16/2023, 12:59:07 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:61:30] :: [401 - OK] :: 3.229393ms - http://127.0.0.1:8080/rest/ profiles/ns/0/connection 1/16/2023, 12:59:07 [pg3] error: No code in error response 1/16/2023, 12:59:07 [pg3] warn: ISY Response: [Try: 2] [00:21:b9:02:61:30] :: [401 - OK] :: 1.480229ms - http://127.0.0.1:8080/rest/ profiles/ns/0/connection 1/16/2023, 12:59:07 [pg3] error: No code in error response 1/16/2023, 12:59:07 [pg3] warn: ISY Response: [Try: 3] [00:21:b9:02:61:30] :: [401 - OK] :: 1.183003ms - http://127.0.0.1:8080/rest/ profiles/ns/0/connection 1/16/2023, 12:59:07 [pg3] error: No code in error response 1/16/2023, 12:59:07 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:21:b9:02:61:30] :: [401 - OK] :: 1.307062ms - http://127.0.0 .1:8080/rest/profiles/ns/0/connection 1/16/2023, 12:59:07 [pg3] error: Error: GET http://127.0.0.1:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 1/16/2023, 12:59:07 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3x/lib/modules/isy/system.js:93:13) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy.js:80:21 at async Promise.allSettled (index 0) at async Object.start (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy.js:26:5) at async start (/var/polyglot/node_modules/@universaldevices/pg3x/bin/pg3.js:112:5) 1/16/2023, 12:59:07 [pg3] warn: verifyNodeServers (00:21:b9:02:61:30) :: ISY has no node servers installed, skipping 1/16/2023, 12:59:07 [pg3] info: Reinstall Services Starting 1/16/2023, 12:59:07 [pg3] info: Waiting for store (false) and isy (false) before starting node servers. 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/status/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/command/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/system/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/custom/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/frontend/isy/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/frontend/system/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/frontend/ns/# QoS 0 1/16/2023, 12:59:07 [pg3] info: MQTTC: Subscribed to udi/pg3/connections/ns/# QoS 0 1/16/2023, 12:59:08 [pg3] info: Making reqeust to socket for /rest/pg3.auth.ns 1/16/2023, 12:59:24 [pg3] info: Starting PG3 version 3.1.18 1/16/2023, 12:59:24 [pg3] info: Using Workdir /var/polyglot/pg3/ 1/16/2023, 12:59:24 [pg3] info: Starting sqlite database at /var/polyglot/pg3/pg3.db 1/16/2023, 12:59:24 [pg3] info: Encryption key found ID: c988d8b4-31c6-44d6-9416-48a969d717ee. Database version 1 1/16/2023, 12:59:24 [pg3] info: Query IoX for platform UUID. 1/16/2023, 12:59:24 [pg3] info: Loaded globalsettings successfully. Database version 1 1/16/2023, 12:59:24 [pg3] info: isy table: Loaded (1) successfully 1/16/2023, 12:59:24 [pg3] info: ISY: 00:21:b9:02:61:30 5.5.3 127.0.0.1 2b43b97d-a0ed-4235-b40a-a6488def4e87 1/16/2023, 12:59:24 [pg3] info: No node servers in database. Add one through the user interface to get started 1/16/2023, 12:59:24 [pg3] info: store is up-to-date 1/16/2023, 12:59:24 [pg3] info: Forcing custom certificates to off 1/16/2023, 12:59:24 [pg3] info: Updated configuration with overrides 1/16/2023, 12:59:24 [pg3] info: Reading certs from filesystem (UDX). 1/16/2023, 12:59:24 [pg3] info: UDX Services Starting 1/16/2023, 12:59:24 [pg3] info: Starting update check 1/16/2023, 12:59:24 [pg3] info: Started MQTT Client Service 1/16/2023, 12:59:24 [pg3] info: Creating ISY queues for 00:21:b9:02:61:30 1/16/2023, 12:59:24 [pg3] info: HTTP Queue response "Queue Created Successfully," 1/16/2023, 12:59:24 [pg3] info: Starting event listeners 1/16/2023, 12:59:24 [pg3] info: Starting Store Poll Refresh timer 1/16/2023, 12:59:24 [pg3] info: Starting ISY verification. 1/16/2023, 12:59:24 [pg3] info: Query ISY description at http://127.0.0.1:8080/desc 1/16/2023, 12:59:24 [pg3] info: Query store database https://pg3store.isy.io/v2/list 1/16/2023, 12:59:24 [pg3] info: Koa HTTPS Interface Service: Started - Address: 0.0.0.0 Port: 3000 1/16/2023, 12:59:24 [pg3] info: Checking ISY's for installed node servers... 1/16/2023, 12:59:24 [pg3] error: No code in error response 1/16/2023, 12:59:24 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:61:30] :: [401 - OK] :: 3.456504ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 12:59:24 [pg3] error: No code in error response 1/16/2023, 12:59:24 [pg3] warn: ISY Response: [Try: 2] [00:21:b9:02:61:30] :: [401 - OK] :: 1.517649ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 12:59:24 [pg3] error: No code in error response 1/16/2023, 12:59:24 [pg3] warn: ISY Response: [Try: 3] [00:21:b9:02:61:30] :: [401 - OK] :: 1.232004ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 12:59:24 [pg3] error: No code in error response 1/16/2023, 12:59:24 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:21:b9:02:61:30] :: [401 - OK] :: 1.329812ms - http://127.0.0.1:8080/rest/profiles/ns/0/conne ction 1/16/2023, 12:59:24 [pg3] error: Error: GET http://127.0.0.1:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 1/16/2023, 12:59:24 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3x/lib/modules/isy/system.js:93:13) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy.js:80:21 at async Promise.allSettled (index 0) at async Object.start (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy.js:26:5) at async start (/var/polyglot/node_modules/@universaldevices/pg3x/bin/pg3.js:112:5) 1/16/2023, 12:59:24 [pg3] warn: verifyNodeServers (00:21:b9:02:61:30) :: ISY has no node servers installed, skipping 1/16/2023, 12:59:24 [pg3] info: Reinstall Services Starting 1/16/2023, 12:59:24 [pg3] info: Waiting for store (false) and isy (false) before starting node servers. 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/status/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/command/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/system/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/ns/custom/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/frontend/isy/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/frontend/system/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/frontend/ns/# QoS 0 1/16/2023, 12:59:24 [pg3] info: MQTTC: Subscribed to udi/pg3/connections/ns/# QoS 0 1/16/2023, 12:59:24 [pg3] info: ***************************************** 1/16/2023, 12:59:24 [pg3] info: Latest PG3x version available is 3.1.18 1/16/2023, 12:59:24 [pg3] info: ***************************************** 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Airscape 1/16/2023, 12:59:24 [pg3] info: Checking for changes in HusqvarnaMower 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Timedata 1/16/2023, 12:59:24 [pg3] info: Checking for changes in YoLink 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Sun 1/16/2023, 12:59:24 [pg3] info: Checking for changes in PurpleAir 1/16/2023, 12:59:24 [pg3] info: Checking for changes in UnifiProtect 1/16/2023, 12:59:24 [pg3] info: Checking for changes in WLED 1/16/2023, 12:59:24 [pg3] info: Checking for changes in AERISWeather 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Flair 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Airthings-C 1/16/2023, 12:59:24 [pg3] info: Checking for changes in August 1/16/2023, 12:59:24 [pg3] info: Checking for changes in HarmonyHub 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Roku 1/16/2023, 12:59:24 [pg3] info: Checking for changes in MiLight 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Sensibo 1/16/2023, 12:59:24 [pg3] info: Checking for changes in AVRemote 1/16/2023, 12:59:24 [pg3] info: Checking for changes in WeatherBit 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Virtual 1/16/2023, 12:59:24 [pg3] info: Checking for changes in NanoLeaf 1/16/2023, 12:59:24 [pg3] info: Checking for changes in NOAA 1/16/2023, 12:59:24 [pg3] info: Checking for changes in OnkyoAVR 1/16/2023, 12:59:24 [pg3] info: Checking for changes in LiFX 1/16/2023, 12:59:24 [pg3] info: Checking for changes in VirtualButtons 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ST-Inventory 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ATest 1/16/2023, 12:59:24 [pg3] info: Checking for changes in AMINEM 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Roomba 1/16/2023, 12:59:24 [pg3] info: Checking for changes in WeatherLink 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Russound 1/16/2023, 12:59:24 [pg3] info: Checking for changes in TeslaPW 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Rachio 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ST-Nuheat 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Hue 1/16/2023, 12:59:24 [pg3] info: Checking for changes in UnifiPresence 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Holidays 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Sonos 1/16/2023, 12:59:24 [pg3] info: Checking for changes in iAquaLink 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Climacell 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ST-Sonos 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Notification 1/16/2023, 12:59:24 [pg3] info: Checking for changes in WirelessTag 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Onkyo 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Volumio 1/16/2023, 12:59:24 [pg3] info: Checking for changes in WeatherPoly 1/16/2023, 12:59:24 [pg3] info: Checking for changes in EnvisaLink-HW 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Bond 1/16/2023, 12:59:24 [pg3] info: Checking for changes in BalboaSPA 1/16/2023, 12:59:24 [pg3] info: Checking for changes in HolidaysGoogle 1/16/2023, 12:59:24 [pg3] info: Checking for changes in OpenSprinkler 1/16/2023, 12:59:24 [pg3] info: Checking for changes in DavisWeather 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Twinkly 1/16/2023, 12:59:24 [pg3] info: Checking for changes in IFTTT-Webhooks 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Wemo 1/16/2023, 12:59:24 [pg3] info: Checking for changes in WeatherFlow 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Ping 1/16/2023, 12:59:24 [pg3] info: Checking for changes in TeslaEV 1/16/2023, 12:59:24 [pg3] info: Checking for changes in BASIRRIGATION 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Backup 1/16/2023, 12:59:24 [pg3] info: Checking for changes in DysonPureCool 1/16/2023, 12:59:24 [pg3] info: Checking for changes in AVServer 1/16/2023, 12:59:24 [pg3] info: Checking for changes in EnvisaLink-DSC 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Govee 1/16/2023, 12:59:24 [pg3] info: Checking for changes in OpenWeatherMap 1/16/2023, 12:59:24 [pg3] info: Checking for changes in BlueIris 1/16/2023, 12:59:24 [pg3] info: Checking for changes in MagicHome 1/16/2023, 12:59:24 [pg3] info: Checking for changes in RainMachine 1/16/2023, 12:59:24 [pg3] info: Checking for changes in MQTT 1/16/2023, 12:59:24 [pg3] info: Checking for changes in BASPOOL 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Acurite 1/16/2023, 12:59:24 [pg3] info: Checking for changes in MyQ 1/16/2023, 12:59:24 [pg3] info: Checking for changes in VenstarCT 1/16/2023, 12:59:24 [pg3] info: Checking for changes in iTach-IR 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Plex-WebHook 1/16/2023, 12:59:24 [pg3] info: Checking for changes in BASGARAGE 1/16/2023, 12:59:24 [pg3] info: Checking for changes in FlumeWater 1/16/2023, 12:59:24 [pg3] info: Checking for changes in VUE 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Caseta 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ShellyRGBW2 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ST-EcoWitt 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Blink 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Kasa 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Kaiterra 1/16/2023, 12:59:24 [pg3] info: Checking for changes in ELK 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Sense 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Somfy 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Netatmo-WS 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Ecobee 1/16/2023, 12:59:24 [pg3] info: Checking for changes in BASAO 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Wake-On-Lan 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Push 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Camect 1/16/2023, 12:59:24 [pg3] info: Checking for changes in SolarEdge 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Meteobridge 1/16/2023, 12:59:24 [pg3] info: Checking for changes in TotalConnect 1/16/2023, 12:59:24 [pg3] info: Checking for changes in MySmartBlinds 1/16/2023, 12:59:24 [pg3] info: Checking for changes in HueEmulator 1/16/2023, 12:59:24 [pg3] info: Checking for changes in Eagle-200 1/16/2023, 12:59:24 [pg3] info: Checking for changes in AmbientWeather 1/16/2023, 12:59:24 [pg3] info: Checking for changes in HoneywellHome 1/16/2023, 12:59:25 [pg3] info: Query store database https://pg3betastore.isy.io/v1/list 1/16/2023, 12:59:25 [pg3] info: Checking for changes in DSC-IT100 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Roku 1/16/2023, 12:59:25 [pg3] info: Checking for changes in PythonTemplate 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Example-1 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Tuya-Devices 1/16/2023, 12:59:25 [pg3] info: Checking for changes in ATest 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Roomba 1/16/2023, 12:59:25 [pg3] info: Checking for changes in TestTeslaEV 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Example-2 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Notification 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Example-4 1/16/2023, 12:59:25 [pg3] info: Checking for changes in OpenSprinkler 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Example-3 1/16/2023, 12:59:25 [pg3] info: Checking for changes in eISYIR 1/16/2023, 12:59:25 [pg3] info: Checking for changes in DysonPureCool 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Sensibo-Air 1/16/2023, 12:59:25 [pg3] info: Checking for changes in VueTest 1/16/2023, 12:59:25 [pg3] info: Checking for changes in MagicHome 1/16/2023, 12:59:25 [pg3] info: Checking for changes in iTach-IR 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Kasa 1/16/2023, 12:59:25 [pg3] info: Checking for changes in ELK 1/16/2023, 12:59:25 [pg3] info: Checking for changes in Ecobee 1/16/2023, 13:04:24 [pg3] error: No code in error response 1/16/2023, 13:04:24 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:61:30] :: [401 - OK] :: 3.032172ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:04:24 [pg3] error: No code in error response 1/16/2023, 13:04:24 [pg3] warn: ISY Response: [Try: 2] [00:21:b9:02:61:30] :: [401 - OK] :: 1.284032ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:04:24 [pg3] error: No code in error response 1/16/2023, 13:04:24 [pg3] warn: ISY Response: [Try: 3] [00:21:b9:02:61:30] :: [401 - OK] :: 1.3138ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:04:24 [pg3] error: No code in error response 1/16/2023, 13:04:24 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:21:b9:02:61:30] :: [401 - OK] :: 1.227923ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:04:24 [pg3] error: Error: GET http://127.0.0.1:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 1/16/2023, 13:04:24 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3x/lib/modules/isy/system.js:93:13) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy.js:80:21 at async Promise.allSettled (index 0) 1/16/2023, 13:04:24 [pg3] warn: verifyNodeServers (00:21:b9:02:61:30) :: ISY has no node servers installed, skipping 1/16/2023, 13:09:24 [pg3] error: No code in error response 1/16/2023, 13:09:24 [pg3] warn: ISY Response: [Try: 1] [00:21:b9:02:61:30] :: [401 - OK] :: 1.48087ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:09:24 [pg3] error: No code in error response 1/16/2023, 13:09:24 [pg3] warn: ISY Response: [Try: 2] [00:21:b9:02:61:30] :: [401 - OK] :: 1.43162ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:09:24 [pg3] error: No code in error response 1/16/2023, 13:09:24 [pg3] warn: ISY Response: [Try: 3] [00:21:b9:02:61:30] :: [401 - OK] :: 1.174782ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:09:24 [pg3] error: No code in error response 1/16/2023, 13:09:24 [pg3] error: ISY Response: [MAX TRIES EXCEEDED] [00:21:b9:02:61:30] :: [401 - OK] :: 1.217968ms - http://127.0.0.1:8080/rest/profiles/ns/0/connection 1/16/2023, 13:09:24 [pg3] error: Error: GET http://127.0.0.1:8080/rest/profiles/ns/0/connection Failed :: 401 - OK 1/16/2023, 13:09:24 [pg3] error: getExistingNodeServers :: Error: Received no response from the ISY. Check your ISY IP Address at Object.getExistingNodeServers (/var/polyglot/node_modules/@universaldevices/pg3x/lib/modules/isy/system.js:93:13) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/isy.js:80:21 at async Promise.allSettled (index 0) 1/16/2023, 13:09:24 [pg3] warn: verifyNodeServers (00:21:b9:02:61:30) :: ISY has no node servers installed, skipping

I decided to start this controller with a clean slate. I didn't restore any backups, or migrate anything. Its all just fresh and clean. So anyway, I got a few Insteon devices connected, then a few Zwave devices connected. Everything was going just fine. But when I tried to log into PG3, I couldn't. I got to the login screen, typed my username and password, clicked login and nothing happened. So, I tried the default user/pass. That didn't work either. So, I rebooted the eisy. That didn't work. I upgraded packages in the admin console (cause, why not?) That didn't do anything either. I tried on several different devices - still nothing. I caught these logs in the console that look suspect to a non-developer like me. Does that give any clues that I should have caught onto?

Haven’t used it on Android, but looking over Android Auto there’s no reason I can see that it wouldn’t work.

Prowl API works great and is free.

Sorry, one more edit - some of the devices are respond and reporting. Not all. Doesn't appear to be a pattern that I can see.

Upgrade from 5.3.0 and any attempt to interact with any Z-wave device (hardwired or battery) results in many error messages. Edit: Despite the errors, device status still is reporting back accurately and the action executes correctly on the Z-wave device.

I'm looking for something creative; and possibly it doesn't exist yet. I have a cell repeater hooked up in my home office, using an ApplianceLinc to turn it on/off. I don't want to waste the electricity (and just generally not a fan of running something if I don't have to) so I leave it off until I need it. That all works fine if I'm making a call, but the incoming calls are the problem. As an attempt at a workaround I have an Echo dot in my office and tell it to turn on when I need it, but it would be nice to automate that. My phone is an iPhone 6, with jailbreak running iOS 9.3.3. Any ideas? Sent from my iPhone using Tapatalk

Do you have a list of all your devices that you can post? I've been dying to do a correlation analysis of devices in common.

I second the question about "don't have the all-on code" comment.All of my new devices have been impacted by the all-on as well as the old devices (with the exception of the one not linked to the PLM).

It's one of the old ones. 2476D. RF-only. Don't recall the firmware version but I can pull the switch plate off and take a look if that helps further the learnings here.

Can confirm - I have an Insteon switch which was directly linked to another switch but never linked to the PLM. The one never linked to the PLM has never turned on in an ALL-ON event.

Two comments, don't know if these will be of much use to anyone.... 1. Out of total luck one time a week or so ago I had an All-ON event while I had the Event Viewer open and set to level 3 and I was sitting in front of my computer. Don't know if this addresses Teken's point about this controller (seems related), but I could see the PLM sending out the ON command to each and every Insteon device. 2. Recently, I came to agree with the opinion that it's not the PLM (maybe this is contradicting my last point). But; I have a long dark hallway that I wanted to make sure I caught any motion in so anyone leaving a bedroom would have the lights turned on for them. I erroneously thought the best way to do this would be to set up multiple motion sensors with overlapping coverage. I also set PLM communication to 1 Retry on each, as well as the switches which I had set up as a virtual 3 way. The more aggressive I got about overlapping coverage of the area, the more frequently I got All On events. In fact, every All On event occurred when someone was in that hallway. Looking at just the common factors; I decided to remove some of the motion sensors so that there was no overlap. I also set PLM communication to No Retries. Haven't had an All-On event since.

Nope. Have never owned a KPL. Sent from my iPhone using Tapatalk

Did you ever figure out what was causing the garage door to spontaneously open? I just started experiencing that as soon as I started using an IO linc for my garage door. Well, actually I just started experiencing the "All On" event which opened my garage door. Never had an All On before installing an IO Linc. I also had readings in my logs regarding motion sensor devices at the same time - despite none of them ever being near or associated to the IO Linc. If you didn't ever get it resolved, did you try the GoControl? I'm considering that but wasn't sure if it worked on the 4.x branch of firmware. Sent from my iPhone using Tapatalk

Not sure if I'm headed down the right path, but I'm trying to use a variable in the spoken property. I have my Echo sending commands to the ISY that relays to the Global Cache which sends IR to the TV. I'd like to be able to say "Echo turn on volume down {v}" where v = the number of times the volume down command repeats. I'm very new to the spoken property and not sure if this is even possible. Anyone tried it before?

It's the Catalina Wine Mixer. Sent from my iPhone using Tapatalk

You guys have half time zones? Is that because of the exchange rate? Sent from my iPhone using Tapatalk

I'm not an expert (although I did sleep at a Holiday Inn last night)...sounds like a bug to me. Sent from my iPhone using Tapatalk

All of the other East Coast locations still show GMT -5. If I manually set myself to one of them it's still GMT -5. Sent from my iPhone using Tapatalk

It looks like ahwman also has the same issue identical to me and he is in the same area. You have the option to uncheck DST? I can't even modify that. Sent from my iPhone using Tapatalk

I'm on version 4.5.0 My external IP accurately reflects my location in Michigan; right down to the zip code. There are quite a few options on the list of locations closer to me than Tennessee; Detroit, Indiana, Illinois, Wisconsin.... Still doesn't make sense why Detroit would be listed as a GMT - 4 when there isn't a single city in the U.S. that's in GMT -4. Sent from my iPhone using Tapatalk

This is weird. I had to move the location of my ISY to a different outlet (just over a few feet so it could be on UPS). When it gets back up and running, it shows the system time as being ahead by one hour. The location in System Configuration is still correct, but has the wrong time zone associated with it,. For example, I'm in Michigan in the Eastern Time zone, which is GMT -5. The current time in Michigan is 4:56 AM. The ISY shows Michigan as being in Eastern Time zone, but shows that Eastern time only in Michigan is GMT -4. All of the other locations in the Eastern Time zone still show GMT-5. However, the ISY insists on setting the current time as 5:56 AM. ..Hence my alarm going off (lights turning on) an hour ahead of schedule and I have time to do this so early now that everyone is awake. To make this even stranger, when I click "Locate Me" it shows up as me being in Tennessee. It's never had this problem before and it has always pinned down my exact location when I clicked that in the past. I checked all of my computers and router which all reflect the correct time and zone. Any ideas of how to fix this? For now, I created a custom location. But also noticed that the Climate module now has my location as Tennessee as well. That's causing a problem with my programs that use climate variables already.

I know this is a rather old thread, but I'd like to resurrect it. Did anyone ever find a reliable way to keep this running?

Funny you should mention that. I noticed the same thing as of about a month ago and came here looking for answers. I did several factory resets, restore, etc. I think it started on 4.4.6 Sent from my iPhone using Tapatalk

The box show is actually an outer shell. The front is a cover that is screwed on. The wires run inside of that and are screwed in place to clamps. Check out the instructions: http://www.homecontrols.com/AEDSC10ZWUS_Instructions.pdf I got z-wave just for this but ended up really getting into locks and such. This alone was worth it. If you study the usage of your dryer enough you can set up programs for the different dryer operations and let yourself know when it's almost done and when it is actually done. Also, it saves a bit on the electric usage because we have the unit completely switch off the line running to the dryer once the machine is done. And it only turns on after the next load of wash is done. I also have the synchrolinc on the washer. Good choice.