hart2hart

Bob, thanks for developing and supporting the node server. I implemented it just ahead of the weekend as part of move from ISY994 and Polisy to eISY. Working great!

Goose66, thanks for another needed node server that is working well in first couple of days. Two quick questions: 1) Is there a form of Set Query for each thermostat (I have 3) to ensure they have most recent values from keypads? I've found this beneficial as we can make changes at the keypad and IOx will see the results and adjust accordingly. Form history though, they sometimes got out of date so I periodically queried each thermostat to keep all in sync. Is this feature this already there and I missed it and if not can it be added (or do you use techniques to keep them closer in sync)? 2) An additional issue is that sometimes a thermostat will lose WiFi. Other devices I have will signal through their iOS app that connection has been lost but not the Venstar thermostats. Looks like you have this covered- Thank you. Is this the Thermostat Online function.

Goose66, I moved over to EnvisaLink-DSC from NodeLink. Glad to report success and thank you for the NS as all went well, but following are three questions and a request to ponder: 1) Is Panel "Force Update" a form of Set Query to the NS to update all data elements? 2) Is Panel "Alarm Panel Connected" the heartbeat that NS and Envisalink are talking? 3) I have not created firewall rules and in fact my security system is monitored by Eyez-On. In my case, is there an advantage either way to the NS param disablewatchdog? Which way would you set it? -- Why? Request to Ponder) I have many programs that use the status of the security system. An example and there are many others -- for that at home look, lights are turned on and off at times based on is the security system armed away. A big difference between EnvisaLink-DSC and NodeLink is that NodeLink represents panel status as Armed Away, Armed Stay and Disarmed so there was little traffic related to status changes. Envisalink-DSC has the armed statuses (with zero entry variants) and the very accurate Ready and Not Ready (vs Disarmed). I've got several interior motion sensors in the security system. The result is that every time you walk around, they turn on and then off. Given my setup, this translated to high volume of programs triggering (even if false) as the status changed usually between Ready and Not Ready. The result was multiple Random all on events an hour after I updated the NS dependent programs and restarted the node server. As I was converting the programs, I was a little concerned at the number of programs using the armed away construct as the list had grown over multiple years. However, I thought (wrongly) it had worked for years and I felt/assumed it would work with a different node server. When it quickly happened a couple times, I realized something was structurally different and isolated it to the status changes and how many/how fast they were occurring. I isolated the rapidly changing statuses to 3 programs that set integer variables (simple example below) and updated all the programs to use the variables as the programs real triggering event (except for one as we will see) was the other part of the If and the security status was secondary. The restructuring stopped the random all on events. Security:Set Armed Stay If 'Security System / Security System:Partition' Partition State is Armed Stay Or 'Security System / Security System:Partition' Partition State is Armed Stay Zero-Entry Then $Security_Armed_Stay = 1 Else $Security_Armed_Stay = 0 I quickly made several program updates to stabilize my lighting setup. However, by doing this, I could no longer see and diagnose the issue looking at the actual problem. However, through a review of text file of all programs (supported by a log and event capture), I isolated the source of the problem to one program being triggered on both the true and false side. The program was only updating a scene and a device but the number of times it was occurring and likely the much faster speed of the eisy executing the event translated to random all on events. I'll restructure that program, so it is only triggering a couple times a day and put Wait between the scene and device updates for when it does occur. The ponder moment is -- could another status be maintained by the node server that only presents armed and disarmed so this kind of "hidden" event is less likely to occur for me and others? Finally, I really like the new setup and thanks for the hard work to develop and support. Paul

Thanks Bob. I’ll look forward to the update.

I just got created a situation that would cause them multiple times in an hour. Diagnosed and fixed it this weekend. It was caused by way I was using a specific node server. Which if any do you utilize?

In general, almost all devices and programming will transfer. All Insteon will come over and depending on your zwave controller choice and compatibility with your devices, all or most of zwave will come over. To be clearer, all programs will come over but some device specific parameters may not.

Hope everyone is having a great holiday weekend. I’m all migrated and upgraded to eISY and PG3x - great hardware and software. It and the UD staff are world class. Michel and everyone else connected with UD set the bar high and then achieve even more! I planned to purchase another eISY to have as an onsite backup but they just went out of stock. I don’t want to compete with those needing their first unit. As luck would have it, it appears that with latest release that PG3X now runs on the Polisy. Am I correct in my understanding that a Polisy (for now) can be that backup? If so, I will keep it updated and then purchase another eISY when the demand is not as high.

Do you have DHCP server turned on in your router?

Started it at same setting with same emitter that had been in the ISY994. I turned it up and down a bit with no luck. Even pulled it off and held it near. The eISY is next to my media PC so I was able to test the learn feature with the IR emitter attached and it didn’t seem to have an issue learning. Thanks again. I’ve got another great solution in place.

Yep, they’ll get me to the promised Ring land and I’ll come back with the results. The entire UD team is excellent from Michel to all staff.

Felt like this was going to be a gimme - NOT. I've abandoned my efforts after a few hours of getting nowhere. It clearly is one of those if it works it works but if not you have to shake the black box from every angle to attempt to locate the issue. The Dongle would learn on a PC so its seeing IR and the NS could detect when it was and was not connected. Creating a new Flirc file did not help. No combination of any of this came close to working so I simply give up. My goal was to move existing programs quickly but, in the end, I used another method to resume IR. I’m not being critical. It just didn’t work for me. By all means, if interested give it a trial mode try. Thanks for the help! Know anyone that wants to buy a slightly used Flirc dongle?

Thanks Geddy. Agreed so I created a new program but alas it does not trigger either: Front Porch:Motion Detected TEST DELETE IT - [ID 0005][Parent 00E3] If 'Ring / Ring / Front Porch (Motion)' is switched Motion Then Run Program 'Front Porch:Motion Processing' (Then Path) Else - No Actions - (To add one, press 'Action') Eleven nodes were newly created when I authenticated to the Ring server from the NS. I'm with you on the old PGC having potential for causing an issue. Through a ticket I messaged with Michel for that very reason. He had me delete the PGC one from the eISY and then I purchased and installed the new version. There were no nodes after the delete and a boot and the new ones were created after I authenticated. Also, I confirmed that motion detection and alerts were configured in the Ring app for the doorbell.

Thanks. It is under Control. I’m running PG3X. I did not catch needing remote access enabled. I configured it and it rebooted my eISY and was busy for about 20-30 minutes. It now says it’s enabled but not current talking with UDI. Do you have other advice on this? It’s all new to me. I did a restart with debug mode of log and got several entries. Do you have time / desire to review them?

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.

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.