pkauf

OK, this morning when I got up, decided to do some messing with it. Noticed this morning that even though I manually set the alarm last night (in Zero Entry), on the AC, Partition 1 of the Alarm Panel was showing Ready. No errors in the log that I could see. I ended up restarting the node server for DSC and now everything works . . . Something had to be whacked on the Polyglot side . . . Very odd. Thanks for your help, but this looks like something was just off, can't tell what it was.

As far as I know, I have not updated the firmware (unless something can do that without me manually doing something). Here is the debug logs on trying zero entry. 2025-03-18 08:09:43.591 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:09:43.591 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:09:43.591 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:09:43.591 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:09:43.591 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:09:43.592 Thread-66670 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:09:59.956 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-03-18 08:09:59.956 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:09:59.956 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_ZEROENTRY', 'query': {}} from Polyglot 2025-03-18 08:09:59.956 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_ZEROENTRY', 'query': {}} from Polyglot 2025-03-18 08:09:59.956 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_ZEROENTRY', 'query': {}} from Polyglot 2025-03-18 08:09:59.956 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_ZEROENTRY', 'query': {}} from Polyglot 2025-03-18 08:09:59.956 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 032, Data 1 2025-03-18 08:09:59.956 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 032, Data 1 2025-03-18 08:10:13.586 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:13.586 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:13.586 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:13.586 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:13.587 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:10:13.587 Thread-66671 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:10:43.593 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:43.593 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:43.593 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:43.593 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:10:43.593 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:10:43.593 Thread-66672 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data When I do "Arm Stay" (unlike the Arm Zero Entry) the alarm panel immediately beeps and turns red to arm. Here is that log 2025-03-18 08:14:09.530 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-03-18 08:14:09.530 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command 2025-03-18 08:14:09.543 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:14:09.544 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_STAY', 'query': {}} from Polyglot 2025-03-18 08:14:09.543 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:14:09.543 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command 2025-03-18 08:14:09.544 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_STAY', 'query': {}} from Polyglot 2025-03-18 08:14:09.544 Command udi_interface INFO nodes:arm_stay: Arming partition 1 in stay mode in arm_stay()... 2025-03-18 08:14:09.544 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 031, Data 1 2025-03-18 08:14:09.544 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 031, Data 1 2025-03-18 08:14:09.544 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': 'partition1', 'cmd': 'ARM_STAY', 'query': {}} from Polyglot 2025-03-18 08:14:09.544 Command udi_interface INFO nodes:arm_stay: Arming partition 1 in stay mode in arm_stay()... 2025-03-18 08:14:09.544 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 031, Data 1 2025-03-18 08:14:09.544 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 031, Data 1 2025-03-18 08:14:09.544 Command udi_interface INFO nodes:arm_stay: Arming partition 1 in stay mode in arm_stay()... 2025-03-18 08:14:09.544 Command udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 031, Data 1 2025-03-18 08:14:09.544 Command udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 031, Data 1 2025-03-18 08:14:13.608 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:14:13.608 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:14:13.608 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:14:13.608 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:14:13.608 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:14:13.608 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:14:13.608 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:14:13.608 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:14:13.608 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:14:13.608 Thread-66679 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:14:13.609 Thread-66679 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:14:13.608 Thread-66679 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:14:13.608 Thread-66679 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:14:13.609 Thread-66679 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:14:13.609 Thread-66679 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:14:13.609 Thread-66679 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:14:13.609 Thread-66679 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:14:13.609 Thread-66679 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:14:43.607 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:14:43.607 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:14:43.607 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:14:43.608 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:14:43.607 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2025-03-18 08:14:43.607 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:14:43.608 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:14:43.607 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2025-03-18 08:14:43.608 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS shortPoll message {} from Polyglot 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evltpi_dsc:sendCommand: Sending command to EnvisaLink device: Command 008, Data 2025-03-18 08:14:43.608 Thread-66680 (_poll_handler) udi_interface DEBUG evltpi_dsc:_send_cmd: In _send_cmd(): Command 008, Data Arm Away does the same thing, works, and then I get the countdown beeps for exit delay.

Odd issue - all of the sudden I can't use the arm zero entry anymore. I watch my panel when it runs, I see the light go off like its getting the command, but then instead of hearing the normal beeps and then after exit delay seeing the red armed light, it just goes back to green. I see this in the log: 2025-03-18 06:06:48.728 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... 2025-03-18 06:06:48.728 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... 2025-03-18 06:06:48.728 Command udi_interface INFO nodes:arm_zero_entry: Arming partition 1 in zero_entry mode in arm_zero_entry()... Then see nothing. I can toggle the chime, I can set other armed modes (Stay, etc.), but this no longer works. Any help would be appreciated!

Thanks! Appreciate the insight.

I found the previous thread about the password length limit to 6 . . . Thanks, it fixed my issue shortening the password to 6. The thing I don't understand is why my EnvisaLink with a password I set years ago to 9 characters worked and the node server logged in fine up until about 3 weeks ago. Was some old code (and the Envisalink 3) truncating the password I typed in, as well as the node server? I'm just curious why it worked forever, and stopped working (maybe the recent update on my Eisy?

Awesome to hear. I'm out this week, but will install new version when i get back Monday. @bpwwer - really appreciate your help on this!

I agree it should be, but I know I've seen cases when it doesn't seem to work. Just making sure in this case. Thanks!

Will the program trigger when status is disconnected or failed or do you have to schedule it to check the status? I just know sometimes status aren't triggering events . . .

Nice. I will try that.

Well, it appears the fix didn't work. Blue Iris updated a day ago, and connects started failing. Waited a bit, but had to restart to get it working again.

Seems to be working so far. My motion counts are now working, and is staying connected so far. @bpwwer - thanks again for doing this!!

Yeah, there was a post to add a line at 122 to fix the issue. It didn't work (seemed to break the script). So I reverted it. I should have saved off the original to be smart, but I didn't. Ran the checkout, got this error (see below), but ran the suggested command, then the git checkout worked. Reinstall of 2.0.3 worked! Thanks for all of your help. I'll do some testing to see if it stays up now. [root@eisy /var/polyglot/pg3/ns/0021b9026669_2]# git checkout blue-iris-poly.py fatal: detected dubious ownership in repository at '/var/polyglot/pg3/ns/0021b9026669_2' To add an exception for this directory, call: git config --global --add safe.directory /var/polyglot/pg3/ns/0021b9026669_2

I see this in the git.log file . . . error: remote origin already exists. fatal: a branch named 'master' already exists From https://github.com/UniversalDevicesInc-PG3/udi-blue-iris-poly * branch master -> FETCH_HEAD error: Your local changes to the following files would be overwritten by merge: blue-iris-poly.py Please commit your changes or stash them before you merge. Aborting ~

Hey, just curious - I installed new version , but on details it still shows 2.0.2 - but on the store, shows installed.

I can test, just saw the new version - I will upgrade and let you know how it goes. THANK YOU VERY MUCH!!! I am like you, if I had a little time to understand python better, I would try to figure out what its doing. And, I TOTALLY agree with you on the band aid stuff, I hate at work when we don't find the real fix, I much prefer that as opposed to "we have a memory leak, let's reboot". 🤣

I think this has been discussed before, but when Blue Iris server is auto updated and restarted, the Node Server stops working. A restart of the node server for Blue Iris fixes this. There was a solution to add code to possibly make it fix itself on a disconnect on a previous thread. I tried it, didn't seem to work (adding the suggested line makes the node server stay in disconnected state and won't connect). It appears this node server isn't actively being maintained. @bpwwer - I have seen you comment on others who would like the functionality of being able to restart a single node server either by a schedule or command line. I do understand your comments that it's just a band aid, but it would be nice to either have a real fix here, or this ability. You also indicated you are willing to help when the author might not be responsive or can't help (I believe the author here indicated they don't use Blue Iris anymore and can't test). Bottom line, any help here would be appreciated. I do code alot, I just don't use python, so I don't think I can easily figure out a solution . . . Thanks!

I had an unused zone (Default name of Zone 15) that I recently ended up using and named it something new. The nodes in PG3 and the ISY still show Zone 15. Is there a way to get this to update or would I have to drop/rediscover all over. Thanks!

Adding a later log file. Looks more like it might be querying, but not getting any data in eisy . . . debug 7.log

Not sure what the invalid token is . . . I set both variables, and restarted. Any help would be appreciated. Thanks! debug 5.log

So i just got a set of test bulbs, added one, and have the "Color/Hue/Saturation" device. Have no idea how to set bulb to different K color temps, or colors. Is there a wiki that explains this?

No, just started using it. Using in a front bathroom to kick on the lights.

I'd open up a ticket and ask Michel. I do know you can buy the USB enclosure to convert the board to an external version. So , barring the cost, I'm wondering if you could buy the USB version and pull the card and install it to avoid it sticking out. They also might have stock to sell if you ask via a ticket.

I think the external usb works on the polisy, would that be an option?

Yep, after the new support came out in 5.6.4 I installed the same motion sensor. Works great. Only issue is it only supports status, not "control on/control off" so you have to do a little programming to get the status on/off to work for controlling lights properly. But yes, its cheap and now works great.

https://www.amazon.com/COEMA-Hygrometer-Thermometer-Temperature-Notification/dp/B0B6MY343B/ref=sr_1_5?crid=39AQICRQNIBY0&keywords=zwave+thermometer+sensor&qid=1690467410&s=lawn-garden&sprefix=zwave+thermometer+s%2Clawngarden%2C99&sr=1-5 COEMA Hygrometer Thermometer.