Bob Gratton

Hi @Jimbo.Automates, I finally managed to catch the full notification I get from the Wireless Tag app. (following image). I don't know if it can help you, but the IP address in the attempted URL call is my Polisy. Did you have a chance to get some answers from Wireless Tag or to get further with this issue? Thanks,

I also get the same error. But I've also been receiving some error notifications from the WirelessTag app for a little while. I can't find one right now but will add the details here once I get a new notification, in case it might help identifying the source of the issue.

Thanks Dennis, that was it. Nodes are currently populating.. I'm mad at myself cause I knew I needed to use the non secure port and I thought I had confirmed. Thanks again!

Hi all, I'm still using my ISY994 with ELK module. In the process of finally migrating from the 994 to IoP, I installed PG3 and got the ELK NS. I managed to transfer the other NS I had on PG2 to PG3 with minimal issues, but I'm having a hard with this one (I did not have the ELK NS installed on PG2). In the AC, I have only the "ELK Controller" node related to this NS. The NS is connected (Node Server Online : Connected), but the M1XEP Status keeps flip flopping between "Connected" and "Disconnected" every couple seconds. Here what's in the log. The same lines repeat constantly with the "WARNING" line coming once a while: 2023-02-22 20:22:21,664 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:26,245 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None 2023-02-22 20:22:26,246 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:30,669 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None 2023-02-22 20:22:30,671 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:33,232 Thread-9 udi_interface WARNING Controller:handler_poll: waiting for sync and node initialization to complete 2023-02-22 20:22:35,189 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None 2023-02-22 20:22:35,191 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:39,612 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None 2023-02-22 20:22:39,614 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:44,247 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None 2023-02-22 20:22:44,249 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:48,750 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None 2023-02-22 20:22:48,752 ELK-13418 elkm1_lib.connection WARNING connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected 2023-02-22 20:22:53,201 ELK-13418 elkm1_lib.connection ERROR connection:connection_lost: [Errno 54] Connection reset by peer NoneType: None My ISY994 is on the last release (V5.3.4) and PG3 is on V3.1.17 I do not have ELKRP2 or any other device connected to the M1XEP (I disable the ELK module from the 994 when testing) Any ideas? Thanks

Hi @Jimbo.Automates, I finally upgraded to PG3 and I have 2 questions about your Ecobee NS: 1- Do you still plan on working on the “Changing fan mode changes schedule mode to hold” issue? (Opened issue #1 on Github) 2- Would the API allow for humidity setpoint to be changed from programs? Would it be simple to add this feature to the NS? Thanks