pkauf

Also, the Zone status update fine. So it can see some of it.

I don't think so. What's the solution? Reinstall?

I watch the node server itself and I can see GV0 toggle when I change the chime status, it just doesn't update on the ISY device for the partition.

I have a DSC alarm and running this node server, and having issues with the statuses on my partitions. I can send a toggle command on the "Door Chime" device, but the status of the Door Chime doesn't show up on the partition. In fact, even though I have seen data here before, now it's all blank. Not sure what the problem it, but it makes my programs not work as they can't get the current setting for the door chime to turn it on or off (I have a program that checks status of chime to determine whether or not to send the toggle command to turn it off or on as requested. Any thoughts on what's wrong here? See Screen shot.

OK, thanks. If you ever get the want to do it, let me know. Thanks for all the replies.

So is there any instructions on how to do it or does it just not work?

Am I doing something wrong? What is the process to allow the NS to connect for the j7+? 023-05-12 13:10:02,369 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:02,372 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:02,373 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:02,376 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:02,377 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:02,380 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:07,380 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:07,383 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:07,383 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:07,387 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:07,499 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:07,500 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:12,509 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:12,510 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:12,513 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:12,515 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:12,619 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:12,620 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:17,632 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:17,635 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:17,636 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:17,639 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:17,640 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:17,643 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:22,649 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:22,652 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:22,655 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:22,658 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:22,757 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:22,758 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:27,760 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:27,762 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:27,764 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:27,766 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:27,877 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:27,878 Thread-6 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused 2023-05-12 13:10:32,883 Thread-6 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:32,883 Thread-11 udi_interface INFO roomba-poly:getPassword: start password discovery 2023-05-12 13:10:32,886 Thread-6 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:32,889 Thread-11 udi_interface INFO roomba-poly:getPassword: Connecting to 192.168.5.217 on port 8883 2023-05-12 13:10:32,997 Thread-11 udi_interface ERROR roomba-poly:getPassword: Failed to connect to robot: [Errno 61] Connection refused

Want to also say thanks to @bpwwer for spending a couple hours remotely on my system trying to figure this out. Very bizarre problem, doesn't make sense. Really learned a lot about the entire config by watching him troubleshoot. Thanks again!

I just converted my old ISY994i to Polisy Pro, and needed to convert my old PG2 Node servers to PG3. I installed the trial version of the Envisalink-DSC and get this error in the log file when it tries to start. Any idea what's wrong? 2023-05-08 10:46:25,857 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.59 Starting... 2023-05-08 10:46:25,869 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-05-08 10:46:25,870 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9594074_3/./evldscns.py", line 11, in <module> 2023-05-08 10:46:25,871 MainThread udi_interface ERROR udi_interface:write: import evldscns 2023-05-08 10:46:25,872 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9594074_3/evldscns/__init__.py", line 2, in <module> 2023-05-08 10:46:25,872 MainThread udi_interface ERROR udi_interface:write: from .nslib import Nodeserver, Node, getValidNodeAddress, getValidNodeName 2023-05-08 10:46:25,873 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db9594074_3/evldscns/nslib.py", line 1 2023-05-08 10:46:25,873 MainThread udi_interface ERROR udi_interface:write: poly 2023-05-08 10:46:25,874 MainThread udi_interface ERROR udi_interface:write: IndentationError 2023-05-08 10:46:25,874 MainThread udi_interface ERROR udi_interface:write: : 2023-05-08 10:46:25,875 MainThread udi_interface ERROR udi_interface:write: unexpected indent

Very cool, I did not know that. I have my own subscription on my existing ISY, so I can do that. I will contact support. Thanks for the info!!!

My original question also was asking - Can I run my ISY on Polisy in parallel with my 994 and access the ISY portal? I bought the Polisy and a USB PLM a couple weeks ago, and would like to transition some of it over gradually. Is there a way to do that?

I am in the process of working on phasing out (EVENTUALLY) my isy994 due to the issues with the serial PLM (I am a huge Insteon user and don't want to trash all my devices) and hopefully replacing it with my new Polisy Pro/USB PLM. I have integrated some basic Polyglot stuff on RPII to my ISY, but am trying to understand the implementation here . . . Will the Polisy be my standalone replacement for all ISY functions, or do I still need to run the ISY hardware? Will my ZWAVE devices work? I use the portal integration for Amazon Echo - can I have 2 PLMs running during my migration? I'm sure I'll have more questions as I move forward, but just starting at the basics here . . . . Is there any documentation that goes over this at a high level? Thanks!!! Paul

Why four instances? Performance?

Mine are actually sitting in a DMZ outside my home network, so I'd rather pull it inside and not have to deal with poking correct ports/routes/etc. through my firewall. Or I'll just buy another one, as you can't every have enough RPis. :--)

Wow, very cool, really appreciate the detailed explanation. I'm very familiar with the RPi (running 2 to do dns/web services/perl script automation, etc.), used it since the original came out. Mine are version 2, so I might repurpose one for this. I haven't bought the Echo yet, been watching these threads, and am finally to the point with other projects I can spend some time on this. Once again, thanks a bunch for consolidating this info here . . . It took you some time, and I appreciate it!!! Paul

OK, looping through these many pages, I'm confused on the current support of Echo and ISY994i. I have been using the 994i for about 2 years and love it. Already integrated by alarm using ISY/DSCLink running on a PC, and I'd like to integrate and Echo, but can't find a source for what the current support is (direct, need some sort of intermediate device/hub/etc). I'm mainly wanted to start just controlling lights or kicking off ISY programs via Echo. I don't mind configuring/etc extra things, but would rather not if possible. Is there a better place to find "current status of ISY/Echo direct integration" or do I just have to filter through the pages of info here (It's all good, but looking for the easiest way to start). Thanks in Advance. Paul