hart2hart

Thanks for trying.

Thanks. I authenticated a couple of times and it loaded 12 nodes as expected. Had read those posts but they didn’t help in my case. I knew about control vs status and was actually. It doesn’t trigger motion or the pressing of doorbell

Motion events are not coming from Ring NS to trigger programs to run.

@bpwwer Per Dennis’ suggestion, can you assist me? Thanks.

Thanks. I have and they are: long 35.961 lat -86.696 elevation 225 I just restated the NS and following is from its log at information level: There are several ERROR messages. 2023-05-26 09:16:27,136 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message stop 2023-05-26 09:16:27,136 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING stop 2023-05-26 09:16:27,137 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-05-26 09:16:27,137 Command udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:8883 2023-05-26 09:16:05,398 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-05-26 09:16:27,136 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message stop 2023-05-26 09:16:27,136 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING stop 2023-05-26 09:16:27,137 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-05-26 09:16:27,137 Command udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:8883 2023-05-26 09:16:27,137 Command udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2023-05-26 09:16:27,138 MQTT udi_interface.interface DEBUG interface:_startMqtt: MQTT: Done 2023-05-26 09:16:27,137 Command udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2023-05-26 09:16:27,138 MQTT udi_interface.interface DEBUG interface:_startMqtt: MQTT: Done 2023-05-26 09:16:35,873 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-05-26 09:16:35,873 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-05-26 09:16:50,080 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-26 09:16:50,080 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-26 09:16:50,787 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 13] 2023-05-26 09:16:50,787 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.26 [ISY: 5.6.0, Slot: 13] 2023-05-26 09:16:50,885 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.171', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2023-05-26 09:16:50,885 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.1.171', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'} 2023-05-26 09:16:51,414 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-26 09:16:51,414 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-05-26 09:16:51,570 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026136_13.cert 0021b9026136_13.key 2023-05-26 09:16:51,570 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL certs: 0021b9026136_13.cert 0021b9026136_13.key 2023-05-26 09:16:51,652 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-26 09:16:51,652 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-05-26 09:16:51,652 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:61:36_13 - MID: 2 Result: 0 2023-05-26 09:16:51,652 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:61:36_13 - MID: 2 Result: 0 2023-05-26 09:16:51,698 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: sunctrl not found in database. 2023-05-26 09:16:51,698 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: sunctrl not found in database. 2023-05-26 09:16:51,839 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-26 09:16:51,839 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-05-26 09:16:51,894 MainThread udi_interface.interface INFO interface:addNode: Adding node Sun Position(sunctrl) [None] 2023-05-26 09:16:51,894 MainThread udi_interface.interface INFO interface:addNode: Adding node Sun Position(sunctrl) [None] 2023-05-26 09:16:52,028 MainThread udi_interface.interface INFO interface:setController: Using node "sunctrl", driver "ST" for connection status. 2023-05-26 09:16:52,028 MainThread udi_interface.interface INFO interface:setController: Using node "sunctrl", driver "ST" for connection status. 2023-05-26 09:16:52,284 MainThread udi_interface.interface DEBUG interface:send: PUBLISHING {'setController': {'node': 'sunctrl', 'driver': 'ST'}} 2023-05-26 09:16:52,284 MainThread udi_interface.interface DEBUG interface:send: PUBLISHING {'setController': {'node': 'sunctrl', 'driver': 'ST'}} 2023-05-26 09:16:52,421 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2023-05-26 09:16:52,421 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2023-05-26 09:16:52,672 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2023-05-26 09:16:52,672 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2023-05-26 09:16:52,957 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2023-05-26 09:16:52,957 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2023-05-26 09:16:53,009 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2023-05-26 09:16:53,009 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2023-05-26 09:16:53,302 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2023-05-26 09:16:53,302 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2023-05-26 09:16:53,302 Thread-1 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2023-05-26 09:16:53,302 Thread-1 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2023-05-26 09:16:53,633 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message setController 2023-05-26 09:16:53,633 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message setController 2023-05-26 09:16:53,759 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2023-05-26 09:16:53,759 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2023-05-26 09:16:53,877 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-05-26 09:16:53,877 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-05-26 09:16:54,048 Command udi_interface.interface DEBUG interface:_handleInput: Key oauth should be passed to node server. 2023-05-26 09:16:54,048 Command udi_interface.interface DEBUG interface:_handleInput: Key oauth should be passed to node server. 2023-05-26 09:16:54,143 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} 2023-05-26 09:16:54,143 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} 2023-05-26 09:16:54,271 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2023-05-26 09:16:54,271 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2023-05-26 09:16:54,413 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2023-05-26 09:16:54,413 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2023-05-26 09:16:54,807 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-05-26 09:16:54,807 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-05-26 09:16:54,808 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-05-26 09:16:54,808 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-05-26 09:16:54,815 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '6a7f7700-e119-4348-8fc6-4899dbaa532a', 'uuid': '00:21:b9:02:61:36', 'profileNum': 13, 'address': 'sunctrl', 'name': 'Sun Position', 'nodeDefId': 'SUNCTRL', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'sunctrl', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1685054235598, 'timeModified': 1685054235598, 'dbVersion': 1} 2023-05-26 09:16:54,815 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '6a7f7700-e119-4348-8fc6-4899dbaa532a', 'uuid': '00:21:b9:02:61:36', 'profileNum': 13, 'address': 'sunctrl', 'name': 'Sun Position', 'nodeDefId': 'SUNCTRL', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'sunctrl', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1685054235598, 'timeModified': 1685054235598, 'dbVersion': 1} 2023-05-26 09:16:54,925 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING setController 2023-05-26 09:16:54,925 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING setController 2023-05-26 09:16:55,074 Command udi_interface.interface DEBUG interface:_handleInput: connection status node/driver update 2023-05-26 09:16:55,074 Command udi_interface.interface DEBUG interface:_handleInput: connection status node/driver update 2023-05-26 09:16:55,200 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-05-26 09:16:55,200 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-05-26 09:16:54,877 Thread-3 udi_interface INFO sun-poly:start: Started Sun Position 2023-05-26 09:16:54,877 Thread-3 udi_interface INFO sun-poly:start: Started Sun Position 2023-05-26 09:16:55,487 Thread-3 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-05-26 09:16:55,488 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2023-05-26 09:16:55,487 Thread-3 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-05-26 09:16:55,488 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2023-05-26 09:16:55,236 Thread-1 udi_interface ERROR udi_interface:write: Exception in thread 2023-05-26 09:16:55,236 Thread-1 udi_interface ERROR udi_interface:write: Exception in thread 2023-05-26 09:16:55,617 Thread-1 udi_interface ERROR udi_interface:write: Thread-1 2023-05-26 09:16:55,618 Thread-1 udi_interface ERROR udi_interface:write: : 2023-05-26 09:16:55,617 Thread-1 udi_interface ERROR udi_interface:write: Thread-1 2023-05-26 09:16:55,618 Thread-1 udi_interface ERROR udi_interface:write: : 2023-05-26 09:16:55,618 Thread-1 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-05-26 09:16:55,618 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 787, in sunrise 2023-05-26 09:16:55,618 Thread-1 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-05-26 09:16:55,618 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 787, in sunrise 2023-05-26 09:16:55,619 Thread-1 udi_interface ERROR udi_interface:write: tot = time_of_transit( 2023-05-26 09:16:55,619 Thread-1 udi_interface ERROR udi_interface:write: tot = time_of_transit( 2023-05-26 09:16:55,633 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 304, in time_of_transit 2023-05-26 09:16:55,633 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 304, in time_of_transit 2023-05-26 09:16:55,634 Thread-1 udi_interface ERROR udi_interface:write: hourangle = hour_angle( 2023-05-26 09:16:55,635 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 215, in hour_angle 2023-05-26 09:16:55,636 Thread-1 udi_interface ERROR udi_interface:write: hour_angle = acos(h) 2023-05-26 09:16:55,636 Thread-1 udi_interface ERROR udi_interface:write: ValueError 2023-05-26 09:16:55,636 Thread-1 udi_interface ERROR udi_interface:write: : 2023-05-26 09:16:55,634 Thread-1 udi_interface ERROR udi_interface:write: hourangle = hour_angle( 2023-05-26 09:16:55,635 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 215, in hour_angle 2023-05-26 09:16:55,636 Thread-1 udi_interface ERROR udi_interface:write: hour_angle = acos(h) 2023-05-26 09:16:55,636 Thread-1 udi_interface ERROR udi_interface:write: ValueError 2023-05-26 09:16:55,636 Thread-1 udi_interface ERROR udi_interface:write: : 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: math domain error 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: The above exception was the direct cause of the following exception: 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-05-26 09:16:55,638 Thread-1 udi_interface ERROR udi_interface:write: self.run() 2023-05-26 09:16:55,639 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-05-26 09:16:55,640 Thread-1 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: math domain error 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: The above exception was the direct cause of the following exception: 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-05-26 09:16:55,637 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-05-26 09:16:55,638 Thread-1 udi_interface ERROR udi_interface:write: self.run() 2023-05-26 09:16:55,639 Thread-1 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-05-26 09:16:55,640 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/sun-poly.py", line 76, in parameterHandler 2023-05-26 09:16:55,641 Thread-1 udi_interface ERROR udi_interface:write: self.sunrise = self.location.sunrise() 2023-05-26 09:16:55,640 Thread-1 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-05-26 09:16:55,640 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/sun-poly.py", line 76, in parameterHandler 2023-05-26 09:16:55,641 Thread-1 udi_interface ERROR udi_interface:write: self.sunrise = self.location.sunrise() 2023-05-26 09:16:55,641 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/location.py", line 330, in sunrise 2023-05-26 09:16:55,642 Thread-1 udi_interface ERROR udi_interface:write: return astral.sun.sunrise(observer, date, self.tzinfo) 2023-05-26 09:16:55,642 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 823, in sunrise 2023-05-26 09:16:55,641 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/location.py", line 330, in sunrise 2023-05-26 09:16:55,642 Thread-1 udi_interface ERROR udi_interface:write: return astral.sun.sunrise(observer, date, self.tzinfo) 2023-05-26 09:16:55,642 Thread-1 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026136_13/.local/lib/python3.9/site-packages/astral/sun.py", line 823, in sunrise 2023-05-26 09:16:55,643 Thread-1 udi_interface ERROR udi_interface:write: raise ValueError(msg) from exc 2023-05-26 09:16:55,814 Thread-1 udi_interface ERROR udi_interface:write: ValueError 2023-05-26 09:16:55,643 Thread-1 udi_interface ERROR udi_interface:write: raise ValueError(msg) from exc 2023-05-26 09:16:55,814 Thread-1 udi_interface ERROR udi_interface:write: ValueError 2023-05-26 09:16:55,531 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2023-05-26 09:16:55,531 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2023-05-26 09:16:55,927 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-05-26 09:16:55,927 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-05-26 09:16:55,956 Thread-1 udi_interface ERROR udi_interface:write: : 2023-05-26 09:16:55,956 Thread-1 udi_interface ERROR udi_interface:write: : 2023-05-26 09:16:56,108 Thread-1 udi_interface ERROR udi_interface:write: Sun is always below the horizon on this day, at this location. 2023-05-26 09:17:03,909 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-05-26 09:16:56,108 Thread-1 udi_interface ERROR udi_interface:write: Sun is always below the horizon on this day, at this location. 2023-05-26 09:17:03,909 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-05-26 09:17:03,910 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll SUN.txt

I’ve tried usual reboot restart and query and it appears connected but nothing but in the position fields.

The node server is running and I can see the flash on the IR emitter when I press buttons on RC but no nodes are being added. When I loaded your file in Flirc application, I expected to have to push a button to restore/write it to the Flirc dongle however it appeared that it was auto restored to dongle during load. Is that correct? In one of the other posts , there is a mention from January of needing to run a Sufi command so node server will see the dongle when you plug it into the eISY. Do I need to do that or is that from early days and has been fixed? If yes, which command? My next thought is it could be different timing on IR codes. I had this issue moving from mx-980 to mx-990 in the same URC same line. I’m using URC MX-990 remotes. Maybe I need to teach Flirc IR codes from my remote control.

I've installed all and restarted everything from node server up to eISY a few times, but events are not showing up to following programs. The version of NS instaled is 1.1.1. The ISY Log shows entries for voltage per sample below: Ring / Ring / Front Porch Custom Control 1 4022 mV Thu 2023/05/25 11:24:10 AM System Unknown Front Porch:Doorbell Rang 'Ring / Ring / Front Porch' is switched Ding Then Send Notification to 'me' content 'Front Porch Doorbell' Else - No Actions - (To add one, press 'Action') I only created this program to see if i was getting any events Front Porch:Motion Detected If 'Ring / Ring / Front Porch (Motion)' is switched Motion And ( From Sunset To Sunrise (next day) ) And $Front_Porch_Motion_Running is 0 Then Run Program 'Front Porch:Motion Processing' (Then Path) Else - No Actions - (To add one, press 'Action') For this program, I confirmed that variable Front_Porch_Motion_Running is properly set to 0. These are same programs used vy PGC version of Ring with the device updated when PGC was removed and new version was installed.

Thank you gzahar! I've downloaded and installed the Flirc application on Windows. That was followed by a firmware update to the dongle. Next, I loaded the config file that you created (Thanks). The dongle has now been moved back to the eISY. Is the next step to start pressing those buttons on the remote that is routed to the eISY location (IR emitter is stuck to the dongle) and those button presses will cause eISY device nodes to be created? For example. do I have a simple press for each button or do I need to press one time and then another time press and hold? Thanks again. I don't like to experiment any more than possible because the recovery from bad steps can be much more labor intensive than taking time to understand before starting.

I’ve always indulged myself to have a backup device on-site. Just moved from live Polisy to eisy. So as title says I’ve got a new Polisy Pro for sale. I’ll sell for $250 plus shipping of choice. PM me if interested.

ISY994 would have zwave 300 or 500 board installed internal. The Insteon PLM is external. I just made the migration last week. As always, product and UD staff are world class.

@firstone Again, thanks for creating this node server. I've been a long-time user of sophisticated IR (with RF) remotes. I use them less with Alexa in place but sometimes IR is still better. I moved to the eISY and PG3x last week, so I want to get this node serve in place to replace the IR i'd been using on ISY. 1) First when I installed this node server last week, I didn't see/notice the following about different install methods based on device and PG3 version: Connect Flirc to eISY/Polisy eISY / PG3x Once node server is installed, nothing else needs to be done. Just plug-in Flirc. Or if already plugged in, unplug and plug back in. Polisy / PG3 At this point Flirc cannot be connected automatically and requires the following procedure: SSH into your eISY/Polisy Execute curl https://raw.githubusercontent.com/firstone/eisy-ir-poly/main/flirc.conf -o flirc.conf Execute sudo mkdir -p /usr/local/etc/devd Execute sudo cp ./flirc.conf /usr/local/etc/devd Execute sudo service devd restart I did the longer instructions for Polisy / PG3. Is this a problem? 2) Second. I see the files for the 40 ir codes already learned. Can you provide a bit more of the steps to levearge the files and get the process started? Also, can you comment a bit about if you already have the ISY994 IR programming in place the method on replacing it with this node server. Maybe an example using Pressed, Held, Released and Idle states would get me going? Again Thanks!

Understand and respect your schedule. Thanks for everything you do. Let me know if I can test etc when it starts.

I’d really like to have Encode Plus integrated via a node server. I bought the Plus because it had Home Kit thinking either that fact or that it appears to have Matter would eventually afford me avenue for support. I would prefer a node server. Do you feel you’ll be building it?

Fantastic! From what you saw, would this apply to the Encode Plus?

I installed an encode plus yesterday! Hope the same api will work! I’m in for a node server.

You need to use Control in the program and not status to see the motion nodes.

I resolved it with Michel’s assistance.

Resolved. I deleted ns from slot and added to different slot and then readded config. Of course, I had to repair programs and UD Mobile as the links to old virtual switches were lost.

Thanks @bmercier , for making a Ring NodeServer available again. The PGC version of it was a great tool for me to use motion sensors to control outdoor lights and I expect this will be even faster and better. I've just upgrade from ISY994 5.0.16C with 300 Zwave bard and PG3 on Polisy to eISY 5.6.0, Zmatter USB, and PG3x. Like always, everything UD is excellent -- especially the staff starting with Michel. I never uninstalled the PGC version and was going to leave it in place as a resource for nodes and programming. PG3x is offering upgrade from existing PGC version in its same slot. If I do an upgrade in that slot will it likely keep the nodes the same — that would be perfect! …or should I install new version in a different slot …or do I need to just make good notes before the upgrade in same slot and then put all back in place. No worries either way. Thanks again!

Javi, thanks so very much for your patience! It took a couple try’s but UD Mobile is now working with old favorites and new eISY on my iPad and iPhone. UD Mobile like everything UD produces is excellent and first rate. Keep it coming and I’ll stay caught up in the future. Thank you, Paul

I don’t know if anything was cleared. I followed instructions to migrate items from old ISY and Polisy to the new eISY. Most of what I can see is good. What do you mean by does it show at top after pressing? Pressing what? Selecting which system and synchronizing it where? I’m really lost. Sorry.

It says it can’t get UUID. It’s visible at top of that same form. Also, the search icon next to the remote URL button finds it but it does not help. Does it need to be on the network?

Thanks. I got interrupted during migration from pg3 to PG3x including the portal migration. Im 99.99% I did something wrong or out of order. I had to reinstall all nodeservers in their same slot and enter various parameters. They all worked except for this one. It was odd how you config it and I can’t recall even the basics. I’m fine to recreate the 5 virtual switches but I don’t remember how it works and can’t find an example. I usually put this stuff in a document for future reference. But not for this or I can’t find it. Looking at its config screen again, there appears to be a missing section at the bottom. There is a header and then save button but no add another parameter button for that section.

I reinstalled Virtual nodeserver and the nodeserver did not retain the config including nodes and config. The 5 virtual switch devices I created still exist in the admin console, but they are not listed in the nodeserver custom configuration parameters or as nodes. I'm thinking I need to add them back on the nodeserver side. Is that correct and is there a way to keep what is in admin console and nodeserver synchronized?