photogeek54

I reinstalled the node server and this is working again.

I've had unifipresence working fine for weeks now but I recently noticed it does not recognize the 2 iphone mac addresses I have set up. I've put them on and off the network several times but I see no status. I've restarted the node server, PG3 and IOX. I see the controller heartbeat. Could this be related to my recent upgrade to 5.5.7? UnifiPresence_2-27-2023_95545-PM.zip

I also had the same problem after a package upgrade to 5.5.7 From 5.5.5. A power cycle of eisy , a 2nd package update and a reboot of eisy ,it is working once again.

Thanks but that did not work. speaking "discover devices" did not find any new devices either. Would that require the old ISY994 to still be plugged in?

I'm having this problem too. After migrating to Eisy, alexa seems to point to my old ISY994 ZW devices. using the above "add devices" or the spoken command "discover devices" doesnt find any new devices. I can delete a device in the portal and re-add it with the "ZY" device and alexa will discover it but I'm hoping there is a way to do this without deleting all the devises I already have setup. Anyone know of a way?

I changed the host name from "AVR" (which is what its called in Unifi) to "192.168.1.50". This made the TV and the AVR controllers show as online but nodes under the AVR node actually pointed to the TV. I deleted the TV configs from the node server configuration and all the nodes in Iox to focus on the AVR. Restarting the node server now shows that it can't find 192.168.1.50. Could port 23 be wrong? the re-discover button I pushed was in the AVRemote controller node. 2023-02-04 19:17:35,496 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2023-02-04 19:17:35,802 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.22 [ISY: 5.5.5, Slot: 13] 2023-02-04 19:17:35,803 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.10.1.171', 'netmask': '255.255.255.0', 'broadcast': '10.10.1.255'} 2023-02-04 19:17:35,803 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-02-04 19:17:35,804 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-02-04 19:17:35,804 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026068_13.cert 0021b9026068_13.key 2023-02-04 19:17:35,804 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-02-04 19:17:35,805 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '1.0.1'}} 2023-02-04 19:17:35,811 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-02-04 19:17:35,812 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:60:68_13 - MID: 2 Result: 0 2023-02-04 19:17:35,854 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-02-04 19:17:38,824 MainThread udi_interface.interface INFO interface:addNode: Adding node AVRemote(controller) [None] 2023-02-04 19:17:38,825 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-02-04 19:17:38,867 Thread-1 udi_interface INFO remotecontroller:handle_level_change: AVRemote New log level: {'name': 'INFO', 'level': 20} 2023-02-04 19:17:38,908 Thread-4 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 19:17:38,909 Thread-4 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 19:17:38,909 Thread-4 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 19:17:38,925 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 19:17:38,992 Thread-4 udi_interface INFO remotecontroller:handler_custom_typed_data: Regenerating profile 2023-02-04 19:17:39,009 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 19:17:39,011 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 19:17:39,015 Thread-4 udi_interface INFO remotecontroller:handler_custom_typed_data: Profile not changed. Skipping 2023-02-04 19:17:39,015 Thread-4 udi_interface INFO remotecontroller:createDevices: Creating Devices... 2023-02-04 19:17:39,016 Thread-4 udi_interface INFO denon_avr:__init__: Loaded DenonAVR driver 2023-02-04 19:17:39,016 Thread-4 udi_interface INFO remotecontroller:createDevices: AVR 2023-02-04 19:17:39,016 Thread-4 udi_interface.interface INFO interface:addNode: Adding node AVR(d_0) [None] 2023-02-04 19:17:39,017 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Zone2(d_1) [None] 2023-02-04 19:17:39,017 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Zone3(d_2) [None] 2023-02-04 19:17:39,111 Thread-9 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-02-04 19:17:39,111 Thread-9 udi_interface INFO remotecontroller:handler_start: Starting AVRemote Node Server 2023-02-04 19:17:39,112 Thread-9 udi_interface INFO remotecontroller:handler_start: AVRemote Node Server Version 1.0.1 2023-02-04 19:17:39,112 Thread-9 udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-02-04 19:17:39,127 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-02-04 19:17:39,136 MainThread udi_interface INFO remotecontroller:createDevices: Creating Devices... 2023-02-04 19:17:39,137 MainThread udi_interface INFO remotecontroller:createDevices: AVR 2023-02-04 19:17:39,138 MainThread udi_interface.interface INFO interface:addNode: Adding node AVR(d_0) [None] 2023-02-04 19:17:39,138 MainThread udi_interface.interface INFO interface:addNode: Adding node Zone2(d_1) [None] 2023-02-04 19:17:39,139 MainThread udi_interface.interface INFO interface:addNode: Adding node Zone3(d_2) [None] 2023-02-04 19:17:39,146 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customtypedparams 2023-02-04 19:17:39,852 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2023-02-04 19:18:37,544 Command udi_interface.node ERROR node:runCmd: node controller command DISCOVER not defined 2023-02-04 19:18:55,660 Thread-12 udi_interface ERROR base_driver:start: Connection to 192.168.1.50:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) TimeoutError: [Errno 60] Operation timed out 2023-02-04 19:18:55,660 Thread-13 udi_interface ERROR base_driver:start: Connection to 192.168.1.50:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) TimeoutError: [Errno 60] Operation timed out 2023-02-04 19:18:55,901 Thread-20 udi_interface ERROR base_driver:start: Connection to 192.168.1.50:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) TimeoutError: [Errno 60] Operation timed out 2023-02-04 19:18:55,902 Thread-21 udi_interface ERROR base_driver:start: Connection to 192.168.1.50:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) TimeoutError: [Errno 60] Operation timed out 2023-02-04 19:19:03,807 Command udi_interface.interface ERROR interface:_handleInput: _parseInput: node address d_6 does not exist. {'address': 'd_6', 'cmd': 'power', 'value': '1', 'uom': '25', 'query': {}}

I'm first trying to get AVremote working on my Eisy w PG3 to a Denon AVR and an LG TV and getting the error that the DISCOVER command is not defined. Any ideas?. 2023-02-04 15:23:49,493 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-02-04 15:23:49,493 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-02-04 15:23:53,737 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-02-04 15:23:53,737 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-02-04 15:23:54,097 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2023-02-04 15:23:54,097 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... 2023-02-04 15:23:54,400 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.22 [ISY: 5.5.5, Slot: 13] 2023-02-04 15:23:54,400 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.22 [ISY: 5.5.5, Slot: 13] 2023-02-04 15:23:54,400 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.10.1.171', 'netmask': '255.255.255.0', 'broadcast': '10.10.1.255'} 2023-02-04 15:23:54,400 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.10.1.171', 'netmask': '255.255.255.0', 'broadcast': '10.10.1.255'} 2023-02-04 15:23:54,400 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-02-04 15:23:54,400 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-02-04 15:23:54,401 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-02-04 15:23:54,401 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026068_13.cert 0021b9026068_13.key 2023-02-04 15:23:54,402 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-02-04 15:23:54,402 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '1.0.1'}} 2023-02-04 15:23:54,401 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-02-04 15:23:54,401 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026068_13.cert 0021b9026068_13.key 2023-02-04 15:23:54,402 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2023-02-04 15:23:54,402 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '1.0.1'}} 2023-02-04 15:23:54,409 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-02-04 15:23:54,409 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-02-04 15:23:54,409 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:60:68_13 - MID: 2 Result: 0 2023-02-04 15:23:54,409 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:60:68_13 - MID: 2 Result: 0 2023-02-04 15:23:54,452 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-02-04 15:23:54,452 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-02-04 15:23:57,513 MainThread udi_interface.interface INFO interface:addNode: Adding node AVRemote(controller) [None] 2023-02-04 15:23:57,513 MainThread udi_interface.interface INFO interface:addNode: Adding node AVRemote(controller) [None] 2023-02-04 15:23:57,513 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-02-04 15:23:57,513 MainThread udi_interface.interface INFO interface:setController: Using node "controller", driver "ST" for connection status. 2023-02-04 15:23:57,556 Thread-1 udi_interface INFO remotecontroller:handle_level_change: AVRemote New log level: {'name': 'INFO', 'level': 20} 2023-02-04 15:23:57,556 Thread-1 udi_interface INFO remotecontroller:handle_level_change: AVRemote New log level: {'name': 'INFO', 'level': 20} 2023-02-04 15:23:57,598 Thread-3 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 15:23:57,598 Thread-3 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 15:23:57,599 Thread-3 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 15:23:57,599 Thread-3 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 15:23:57,599 Thread-3 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 15:23:57,599 Thread-3 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2023-02-04 15:23:57,613 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 15:23:57,613 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 15:23:57,681 Thread-3 udi_interface INFO remotecontroller:handler_custom_typed_data: Regenerating profile 2023-02-04 15:23:57,681 Thread-3 udi_interface INFO remotecontroller:handler_custom_typed_data: Regenerating profile 2023-02-04 15:23:57,698 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 15:23:57,698 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 15:23:57,699 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 15:23:57,699 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2023-02-04 15:23:57,704 Thread-3 udi_interface INFO remotecontroller:handler_custom_typed_data: Profile not changed. Skipping 2023-02-04 15:23:57,704 Thread-3 udi_interface INFO remotecontroller:handler_custom_typed_data: Profile not changed. Skipping 2023-02-04 15:23:57,704 Thread-3 udi_interface INFO remotecontroller:createDevices: Creating Devices... 2023-02-04 15:23:57,705 Thread-3 udi_interface INFO web_os:__init__: Needs device registration acceptance 2023-02-04 15:23:57,704 Thread-3 udi_interface INFO remotecontroller:createDevices: Creating Devices... 2023-02-04 15:23:57,705 Thread-3 udi_interface INFO web_os:__init__: Needs device registration acceptance 2023-02-04 15:23:57,705 Thread-3 udi_interface INFO web_os:__init__: Loaded WebOS driver 2023-02-04 15:23:57,705 Thread-3 udi_interface INFO remotecontroller:createDevices: OLED65C9PUA 2023-02-04 15:23:57,705 Thread-3 udi_interface INFO web_os:__init__: Loaded WebOS driver 2023-02-04 15:23:57,705 Thread-3 udi_interface INFO remotecontroller:createDevices: OLED65C9PUA 2023-02-04 15:23:57,706 Thread-3 udi_interface.interface INFO interface:addNode: Adding node OLED65C9PUA(d_0) [None] 2023-02-04 15:23:57,706 Thread-3 udi_interface.interface INFO interface:addNode: Adding node OLED65C9PUA(d_0) [None] 2023-02-04 15:23:57,706 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Audio(d_1) [None] 2023-02-04 15:23:57,706 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Basic Media(d_2) [None] 2023-02-04 15:23:57,706 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Audio(d_1) [None] 2023-02-04 15:23:57,706 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Basic Media(d_2) [None] 2023-02-04 15:23:57,707 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Inputs(d_3) [None] 2023-02-04 15:23:57,707 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Inputs(d_3) [None] 2023-02-04 15:23:57,707 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Media(d_4) [None] 2023-02-04 15:23:57,707 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Media(d_4) [None] 2023-02-04 15:23:57,708 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Navigation(d_5) [None] 2023-02-04 15:23:57,708 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Navigation(d_5) [None] 2023-02-04 15:23:57,708 Thread-3 udi_interface INFO denon_avr:__init__: Loaded DenonAVR driver 2023-02-04 15:23:57,709 Thread-3 udi_interface INFO remotecontroller:createDevices: AVR 2023-02-04 15:23:57,709 Thread-3 udi_interface.interface INFO interface:addNode: Adding node AVR(d_6) [None] 2023-02-04 15:23:57,708 Thread-3 udi_interface INFO denon_avr:__init__: Loaded DenonAVR driver 2023-02-04 15:23:57,709 Thread-3 udi_interface INFO remotecontroller:createDevices: AVR 2023-02-04 15:23:57,709 Thread-3 udi_interface.interface INFO interface:addNode: Adding node AVR(d_6) [None] 2023-02-04 15:23:57,709 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Zone2(d_7) [None] 2023-02-04 15:23:57,710 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Zone3(d_8) [None] 2023-02-04 15:23:57,709 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Zone2(d_7) [None] 2023-02-04 15:23:57,795 Thread-9 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-02-04 15:23:57,710 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Zone3(d_8) [None] 2023-02-04 15:23:57,795 Thread-9 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-02-04 15:23:57,795 Thread-9 udi_interface INFO remotecontroller:handler_start: Starting AVRemote Node Server 2023-02-04 15:23:57,796 Thread-9 udi_interface INFO remotecontroller:handler_start: AVRemote Node Server Version 1.0.1 2023-02-04 15:23:57,796 Thread-9 udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-02-04 15:23:57,795 Thread-9 udi_interface INFO remotecontroller:handler_start: Starting AVRemote Node Server 2023-02-04 15:23:57,796 Thread-9 udi_interface INFO remotecontroller:handler_start: AVRemote Node Server Version 1.0.1 2023-02-04 15:23:57,796 Thread-9 udi_interface.custom INFO custom:_save: Sending data customtypedparams to Polyglot. 2023-02-04 15:23:57,812 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-02-04 15:23:57,812 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-02-04 15:23:57,825 MainThread udi_interface INFO remotecontroller:createDevices: Creating Devices... 2023-02-04 15:23:57,828 MainThread udi_interface INFO remotecontroller:createDevices: OLED65C9PUA 2023-02-04 15:23:57,828 MainThread udi_interface.interface INFO interface:addNode: Adding node OLED65C9PUA(d_0) [None] 2023-02-04 15:23:57,825 MainThread udi_interface INFO remotecontroller:createDevices: Creating Devices... 2023-02-04 15:23:57,828 MainThread udi_interface INFO remotecontroller:createDevices: OLED65C9PUA 2023-02-04 15:23:57,828 MainThread udi_interface.interface INFO interface:addNode: Adding node OLED65C9PUA(d_0) [None] 2023-02-04 15:23:57,829 MainThread udi_interface.interface INFO interface:addNode: Adding node Audio(d_1) [None] 2023-02-04 15:23:57,829 MainThread udi_interface.interface INFO interface:addNode: Adding node Audio(d_1) [None] 2023-02-04 15:23:57,830 MainThread udi_interface.interface INFO interface:addNode: Adding node Basic Media(d_2) [None] 2023-02-04 15:23:57,831 MainThread udi_interface.interface INFO interface:addNode: Adding node Inputs(d_3) [None] 2023-02-04 15:23:57,831 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customtypedparams 2023-02-04 15:23:57,831 MainThread udi_interface.interface INFO interface:addNode: Adding node Media(d_4) [None] 2023-02-04 15:23:57,832 MainThread udi_interface.interface INFO interface:addNode: Adding node Navigation(d_5) [None] 2023-02-04 15:23:57,832 MainThread udi_interface INFO remotecontroller:createDevices: AVR 2023-02-04 15:23:57,832 MainThread udi_interface.interface INFO interface:addNode: Adding node AVR(d_6) [None] 2023-02-04 15:23:57,833 MainThread udi_interface.interface INFO interface:addNode: Adding node Zone2(d_7) [None] 2023-02-04 15:23:57,833 MainThread udi_interface.interface INFO interface:addNode: Adding node Zone3(d_8) [None] 2023-02-04 15:23:57,830 MainThread udi_interface.interface INFO interface:addNode: Adding node Basic Media(d_2) [None] 2023-02-04 15:23:57,831 MainThread udi_interface.interface INFO interface:addNode: Adding node Inputs(d_3) [None] 2023-02-04 15:23:57,831 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customtypedparams 2023-02-04 15:23:57,831 MainThread udi_interface.interface INFO interface:addNode: Adding node Media(d_4) [None] 2023-02-04 15:23:57,832 MainThread udi_interface.interface INFO interface:addNode: Adding node Navigation(d_5) [None] 2023-02-04 15:23:57,832 MainThread udi_interface INFO remotecontroller:createDevices: AVR 2023-02-04 15:23:57,832 MainThread udi_interface.interface INFO interface:addNode: Adding node AVR(d_6) [None] 2023-02-04 15:23:57,833 MainThread udi_interface.interface INFO interface:addNode: Adding node Zone2(d_7) [None] 2023-02-04 15:23:57,833 MainThread udi_interface.interface INFO interface:addNode: Adding node Zone3(d_8) [None] 2023-02-04 15:23:59,841 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2023-02-04 15:23:59,841 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: ST to 1 UOM 25 2023-02-04 15:24:01,013 Thread-12 udi_interface WARNING web_os:connect: (64, 'Host is down') 2023-02-04 15:24:01,013 Thread-12 udi_interface WARNING web_os:connect: (64, 'Host is down') 2023-02-04 15:24:02,742 Thread-49 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:02,742 Thread-49 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:02,742 Thread-48 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:02,742 Thread-48 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:03,197 Thread-72 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:03,197 Thread-72 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:03,197 Thread-73 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:03,197 Thread-73 udi_interface ERROR base_driver:start: Connection to AVR:23 failed Traceback (most recent call last): File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/base_driver.py", line 24, in start self.connect() File "/var/polyglot/pg3/ns/0021b9026068_13/drivers/denon_avr.py", line 37, in connect self.conn.connect((self.config['hostName'], self.config['port'])) socket.gaierror: [Errno 8] Name does not resolve 2023-02-04 15:24:47,789 Command udi_interface.node ERROR node:runCmd: node controller command DISCOVER not defined 2023-02-04 15:24:47,789 Command udi_interface.node ERROR node:runCmd: node controller command DISCOVER not defined

I have started to go through each z-wave device and s-wave->synchronize->update with interview them all. This brings back most devices but you have to look carefully after each synchronize for any programs that show changes and fix the "not specified devices" which result from each synchronize. it looks like some z-wave plus devices need to be removed and re-added to specify whether they have S2 security or not. but my aoetec trisensor will not add. see below

by exclude and include do you mean the "remove a zwave device" and "add a zwave device" under the zwave menu? I tried that with 1 switch and it works fine but it changed the zwave node number and I really don't want to do this with all 58 devices and then have to fix all the references in the programs. Also, I did a factory reset on the eisy and restored the ISY from backup and the zwave dongle from backup. The zwave node numbers came back without the descriptive names I had given them and most of the red circles went away but the devices are still not controllable. I still get the platform error

After restoring from my ISY994 backup the eisy refreshed the views but all my zwave devices have the red circle with a line through it. I tried restoring the zwave and synchronizing update with interview on one device but still no go. I restarted IoX and it refreshed the views again but all zwave devices still show red circles with a line through them. I can enable individual zwave devices but they they still show no status and I get platform errors 10108. ideas?

So i've unchecked insteon support and rebooted the eisy. I got system busy again but this time is showed "refreshing views". If it had previously said "looking for insteon I would have saved me many hours. I didn't have the option of unchecking insteon support the first time the system came up as the system busy started immediately. A note in the migration instructions about this might save someone else some time. NEW PROBLEM: the eisy refreshed the views and system busy has gone away! But all my zwave devices have the red circle with a line through it. I tried restoring the zwave and synchronizing update with interview on one device but still no go.

New Eisy v5.5.4 is just coming up and appears to be interviewing the devices (Zwave? Insteon? ) forever. This is following a restore from my ISY994Z. I haven't plugged in the Insteon PLM yet (may not use it anymore), could that be the problem? Message on the screen says "please do not power off/unplug the system or make adjustments to linked/attached devices". Do I dare reboot it? I was at the following step in the migration: When Eisy / Polisy restarts, it automatically does the following: Writes you Z-Wave network into the ZMatter Z-Wave controller Interviews every Z-Wave device in the Z-Wave nework, creating/updating nodes, programs and scenes.

This information is a huge help! Thanks. It would be even easier if I could interface to my existing wired Moose system but looks like an Elk or DSC is in my future.

I don't see any DSC node server in the official UD node store or one from @Goose66. can you point me there?

Thanks , I plan to move to the Eisy and then watch for the new Elk product to come out. I’m hopeful that the new API will be similar enough to the current one for the M1 and @Jimbo.Automates adds it to his node server.

I also see that the ISY has some native Elk M1 support via a $99 Elk module. This is what made me assume Elk was the only brand I should consider. Is this a requirement for your node server or is the node server a replacement for the elk module? Sorry for all the questions, Ive had my ISY for many years but this is a new area for me.

I'm considering upgrading my 27 year old Moose alarm system to an Elk system since there seems to be ISY/Polisy/Eisy support primarily for Elk alarm systems. Elk announced a new E27 Alarm engine last year. Would the Elk Node server likely support this system when it comes out? Any other suggestions folks suggest I consider for my upgrade?

I currently use the presence poly, haven’t got UniFi poly to work. I’m not sure the presence poly was getting moved to PG3 but another post suggested that I can keep my RPi running PG2 and it can still communicate with an EISY. If that works I’m set.

I'm currently relying on the Presence-Poly on PG2 on an ISY994. I'm hoping to upgrade to the EISY and PG3 when it comes out in November. It doesn't seem like the presence-Poly will be supported on PG3 as I haven't seen any development activity for years and can't find contact information for the developer. all my networking equipment is Unify based. Should I expect UnifiPresence to be a suitable replacement? Is there a cost to the PG3 node servers?

I've been having the same problem for several months now on a number of z-wave devices with my ISY-994 on v5.1 and series 500 dongle. They all seem to be older devices that I bought from monoprice. Same exact message on UD Mobile. I've cleared java cache and removed and re-added the Zwave device. No improvement. The devices function properly, just don't return a successful response. Was some change made that would affect only older series Z-wave devices?

I have an aeotec Home Energy Meter Gen5 z-wave and am currently seeing energy reports every 60 seconds on my ISY994i v5.1.0. Rather than check my energy usage via UD mobile I'd love to see it on the home screen of my Alexa show. When I connect the energy meter to the portal the only options I see are to connect it as a light, switch or outlet. the portal seems to understand devices like thermostats but not an energy meter. Any ideas?

I’ve been struggling to get a very high confidence method for home/away detection for years now. Network detection seems pretty good but yes I see occasional short dropouts that I need to program around but it’s not 100% foolproof in my house. I supplement this with some Bluetooth beacons using locative on iOS but it’s also not 100%. I also add in geofencing with both ifttt and locative. Here again sometimes one of them misses an entry or exit. Seems like the iOS api should provide some knowledge not only of crossing the geofence but the fact that if I’m within the geofence for some length of time then it should use that to override a missed geofence crossing.

Got my ISY back again, thanks for the tips! I opened my SD card under windows and found the offending program under conf\d2d\000F.PGM. Opening the file in notepad it was pretty easy to find the variable I had set to the wrong value and change it. The ISY booted without the infinite loop and I added a new condition to "My Programs" of a debug variable initially set to 1 and doesn't allow programs to run until I set it to 0. Yes this means the programs wont run after a reboot until I change the variable but I'm OK with that. We haven't had a power failure here in over 10 years. Thanks Goose66 and MrBill!

I edited a program and created an infinite loop. How can I get control of my ISY back? I can load the admin console but can't change variables. The console won't show the programs so I can edit them. I tried restoring from a backup but get a socket open error. rebooting the ISY does not help. Help

I have a geofence and device setup in the portal. I assigned the geofence to the device and synced with the ISY. the instructions at: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Node_Server_Occupancy_V2_%26_UDI_Mobile_app_Instructions say I should see a request to enter the 6 digit code on UD mobile on my iphone but I never see it and it never gave me a way to setup the geofence location. Ideas?