lsibarra

It looks like the Portal is back-up. Thanks, Larry

Hi, Mine is also showing Offline and when I attempt to login to https://my.isy.io, I am getting HTTP error 500. So then I attempted to login from the main Universal Devices webpage: https://www.universal-devices.com/login/?redirect_to=https%3A%2F%2Fwww.universal-devices.com%2Fmy-account%2F And when I do so, I get this reponse: Hope, they are aware and will soon fix the problem. Larry

Hi @Goose66, I am also having issues with the VenstarCT polyglot integration regarding the Heat/Cool State as described here. My use case for this is to use it in the Program where if the State is Cooling or Heating and doors or windows are open, it will turn the thermostat off. However, the Heat/Cool State when used in the program, it is not recognizing the it the status change. I hope this can be fix. Thanks in advance.

Hi @io_guy, I am reaching out because I started having issues with my Nodelink V0.11.3 for my DSC Alarm. Below is the error log. I am not sure what causing this. My internet and all my other connected device has not issues. In addition, I checked all the logs from the polyglot v2 that I have installed in my local raspberry pi and it doesnt have any network issues. I am only getting these from the Nodelink. Do you have any idea what causing these errors? 2022-06-12 20:40:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/40/25) 2022-06-12 20:41:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 20:43:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/43/25) 2022-06-12 20:47:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/47/25) 2022-06-12 20:53:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/53/25) 2022-06-12 21:02:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 21:07:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234548/25) 2022-06-12 21:08:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234548/25) 2022-06-12 21:18:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 21:19:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234560/25) 2022-06-12 21:21:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234562/25) 2022-06-12 21:24:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234565/25) 2022-06-12 21:53:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/53/25) 2022-06-12 21:54:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/54/25) 2022-06-12 21:56:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 21:59:12 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV2/59/25) [10] 2022-06-12 22:00:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234601/25) 2022-06-12 22:53:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234654/25) 2022-06-12 22:57:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234658/25) 2022-06-12 23:01:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/1/25) 2022-06-12 23:02:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234663/25) 2022-06-12 23:05:12 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV2/5/25) [10] 2022-06-12 23:08:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/8/25) 2022-06-12 23:09:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/9/25) 2022-06-12 23:11:12 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV2/11/25) [10] 2022-06-12 23:12:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 23:13:09 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 23:18:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 23:23:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/23/25) 2022-06-12 23:24:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/24/25) 2022-06-12 23:25:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234686/25) 2022-06-12 23:30:12 - DSC: System Status - Exit Delay In Progress (Partition 1) [dsc1] 2022-06-12 23:32:11 - DSC: System Status - Armed Stay (Partition 1) [dsc1] 2022-06-12 23:35:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234696/25) 2022-06-12 23:37:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234698/25) 2022-06-12 23:41:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/41/25) 2022-06-12 23:41:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-12 23:46:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234707/25) 2022-06-12 23:47:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234708/25) 2022-06-12 23:52:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/52/25) 2022-06-12 23:53:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234714/25) 2022-06-12 23:54:03 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234714/25) 2022-06-12 23:56:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234717/25) 2022-06-12 23:58:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234719/25) 2022-06-12 23:59:03 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234719/25) 2022-06-13 00:00:03 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV1/0/25) 2022-06-13 00:01:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234722/25) 2022-06-13 00:02:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 00:03:09 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 00:09:03 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/9/25) 2022-06-13 00:10:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 00:14:03 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/14/25) 2022-06-13 00:16:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 03:00:03 - DSC: System Status - Armed Stay (Partition 1) [dsc1] 2022-06-13 04:23:34 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/234984/25) 2022-06-13 07:14:58 - DSC: System Status - Panel Disarmed By User 05 [dsc1] 2022-06-13 07:14:58 - DSC: System Status - Disarmed (Partition 1) [dsc1] 2022-06-13 08:53:19 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_dsc1/report/status/GV11/1/25) [10] 2022-06-13 08:54:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/54/25) 2022-06-13 09:01:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/1/25) 2022-06-13 09:02:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235263/25) 2022-06-13 09:05:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/5/25) 2022-06-13 09:05:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/5/25) 2022-06-13 09:06:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/6/25) 2022-06-13 09:06:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/6/25) 2022-06-13 09:07:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/7/25) 2022-06-13 09:07:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/7/25) 2022-06-13 09:08:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/8/25) 2022-06-13 09:08:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/8/25) 2022-06-13 09:09:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/9/25) 2022-06-13 09:09:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:10:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:11:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235272/25) 2022-06-13 09:12:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235273/25) 2022-06-13 09:13:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235274/25) 2022-06-13 09:14:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235274/25) 2022-06-13 09:15:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235276/25) 2022-06-13 09:17:19 - DSC: Error in received string - checksum failed (?500000) [dsc1] 2022-06-13 09:18:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:20:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235281/25) 2022-06-13 09:21:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:22:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235283/25) 2022-06-13 09:25:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235286/25) 2022-06-13 09:26:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235286/25) 2022-06-13 09:26:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235287/25) 2022-06-13 09:27:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:28:48 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) [10] 2022-06-13 09:29:19 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:29:49 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:30:08 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1] 2022-06-13 09:30:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 09:30:08 - DSC Error: Connect - Network is unreachable [dsc1] 2022-06-13 09:30:08 - DSC Error: Data Arrival Init - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [dsc1] 2022-06-13 09:30:20 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:30:38 - DSC: Reconnecting To Server [dsc1] 2022-06-13 09:30:38 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1] 2022-06-13 09:30:50 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:31:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 09:31:08 - DSC Error: Connect - Network is unreachable [dsc1] 2022-06-13 09:31:38 - DSC: Reconnecting To Server [dsc1] 2022-06-13 09:31:38 - DSC Error: Connect - Network is unreachable [dsc1] 2022-06-13 09:32:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/32/25) 2022-06-13 09:32:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 09:32:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/32/25) 2022-06-13 09:35:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/35/25) 2022-06-13 09:35:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/35/25) 2022-06-13 09:36:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/36/25) 2022-06-13 09:37:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/37/25) 2022-06-13 09:37:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:38:09 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:39:00 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/39/25) 2022-06-13 09:40:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:41:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235302/25) 2022-06-13 09:42:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:43:30 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235304/25) 2022-06-13 09:44:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:46:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/46/25) 2022-06-13 09:46:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/46/25) 2022-06-13 09:47:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/47/25) 2022-06-13 09:47:32 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/47/25) 2022-06-13 09:55:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 09:57:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/57/25) 2022-06-13 09:57:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/57/25) 2022-06-13 09:58:41 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235319/25) [10] 2022-06-13 09:59:21 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235319/25) [10] 2022-06-13 10:00:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV1/10/25) 2022-06-13 10:00:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV1/10/25) 2022-06-13 10:02:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/2/25) 2022-06-13 10:04:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/4/25) 2022-06-13 10:05:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/5/25) 2022-06-13 10:05:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/5/25) 2022-06-13 10:06:02 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/6/25) 2022-06-13 10:07:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:08:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235329/25) 2022-06-13 10:09:11 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235329/25) [10] 2022-06-13 10:09:42 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235330/25) 2022-06-13 10:10:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:12:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/12/25) 2022-06-13 10:12:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/12/25) 2022-06-13 10:13:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235334/25) 2022-06-13 10:14:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235334/25) 2022-06-13 10:14:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235335/25) 2022-06-13 10:16:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/16/25) 2022-06-13 10:16:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/16/25) 2022-06-13 10:17:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235338/25) 2022-06-13 10:18:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235339/25) 2022-06-13 10:19:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235339/25) 2022-06-13 10:19:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:20:09 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:20:15 - DSC: Error in received string - checksum failed (51081FF500000) [dsc1] 2022-06-13 10:20:15 - DSC: Error decoding data (60900130 61001028 51081FF50000025 ) [dsc1] 2022-06-13 10:22:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/22/25) 2022-06-13 10:22:34 - DSC: System Status - Exit Delay In Progress (Partition 1) [dsc1] 2022-06-13 10:23:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/23/25) 2022-06-13 10:23:35 - DSC: System Status - Armed Away (Partition 1) [dsc1] 2022-06-13 10:24:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/24/25) 2022-06-13 10:24:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/24/25) 2022-06-13 10:25:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/25/25) 2022-06-13 10:25:08 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1] 2022-06-13 10:25:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:25:08 - DSC Error: Data Arrival Init - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [dsc1] 2022-06-13 10:25:24 - DSC: System Status - Armed Away (Partition 1) [dsc1] 2022-06-13 10:28:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/28/25) 2022-06-13 10:28:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/28/25) 2022-06-13 10:30:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/30/25) 2022-06-13 10:30:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:31:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235352/25) 2022-06-13 10:32:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235352/25) 2022-06-13 10:33:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:37:31 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235358/25) 2022-06-13 10:38:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235358/25) 2022-06-13 10:40:01 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV2/40/25) 2022-06-13 10:40:38 - ISY Error: Network is unreachable (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) 2022-06-13 10:42:48 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) [10] 2022-06-13 10:44:06 - DSC: System Status - Entry Delay In Progress (Partition 1) [dsc1] 2022-06-13 10:44:37 - DSC: System Status - ALARMED (Partition 1) [dsc1] 2022-06-13 10:44:40 - DSC: System Status - Entry Delay In Progress (Partition 1) [dsc1] 2022-06-13 10:44:42 - DSC: System Status - Panel Disarmed By User 01 [dsc1] 2022-06-13 10:47:41 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235368/25) [10] 2022-06-13 10:48:11 - ISY Error: Network is unreachable (ns/1/nodes/n001_data1/report/status/GV3/235368/25) 2022-06-13 10:50:08 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1] 2022-06-13 10:50:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:50:08 - DSC Error: Data Arrival Init - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [dsc1] 2022-06-13 10:50:08 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1] 2022-06-13 10:50:38 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:51:41 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235372/25) [10] 2022-06-13 10:52:38 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1] 2022-06-13 10:52:38 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:52:38 - DSC Error: Data Arrival Init - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [dsc1] 2022-06-13 10:52:38 - DSC Error: Data Arrival Init - Connection reset by peer [dsc1] 2022-06-13 10:53:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:54:11 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV2/54/25) [10] 2022-06-13 10:55:08 - DSC TCP: No poll response, attempting to reconnect to alarm [dsc1] 2022-06-13 10:55:08 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:55:08 - DSC Error: Data Arrival Init - Cannot access a disposed object. Object name: 'System.Net.Sockets.Socket'. [dsc1] 2022-06-13 10:55:08 - DSC Error: Connected - Connection reset by peer 192.168.10.249:4025 [dsc1] 2022-06-13 10:55:38 - DSC: Reconnecting To Server [dsc1] 2022-06-13 10:56:18 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_dsc1/report/status/GV11/-1/25) [10] 2022-06-13 10:58:41 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235379/25) [10] 2022-06-13 10:59:41 - ISY Error: Timeout from the ISY (ns/1/nodes/n001_data1/report/status/GV3/235380/25) [10] Thanks, Larry

Hi, I am very happy to see this app developed. I just downloaded it today. I have been using ISY since 2015 and have been waiting for a descent app for Android. I've used ISY, Mobilinc, Agave, Tasker, and I even integrated ISY to Home Assistant just to have an app but nothing really fully support all the new development that is currently happening in ISY. I am really liking this app since I am now able to see all my devices and all of its functionality/statuses regardless if the device is integrated from Nodelink or Polyglot. I am hoping to see this app thrive in the coming years. I will continue to use the app and will provide some feedback later in this thread. Thanks you for all that you do in the ISY community. Best, Larry

Hi io_guy, I am currently have a running Raspbian with your nodelink but due to some my file-systems got corrupted, I need to do re-install Raspbian which is now running the most recent OS (Raspbian buster). I ran your curl command to install Nodelink. However, if all possible I would like to retain my current Nodelink connection in my ISY as I have many programs that are tied to those nodes. I am afraid that once I connect the new Nodelink, it will create new nodes in my ISY. Is there a way to have the new setup recognize the existing nodes? Please advise. Thanks, Larry

Hi io_guy Thanks for this new script to install and load the nodelink. I noticed that NodeLink Server v0.9.21 no longer have the option to install the geofence/location device. Is this node device no longer supported in this version? Thanks.

Hi xKing, I cannot thank you enough for guiding me through this. The '/' was indeed the issue and after adding that.. all is well. I changed the TOKENTTL to 60 and all of that is working perfectly as well. Thank you again for all your help and patience with me.

Hi xKing, I just updated the TOKENTTL to 60. I will let you know how it goes. One thing I noticed after changing the config.read path to full path ('home/pi/node/config.ini') I am no longer able to run it from the terminal. I started getting this error below when i sent this command from the terminal [pi@raspberrypi:~/node $ ./myq-garage.py status] pi@raspberrypi:~/node $ ./myq-garage.py status Traceback (most recent call last): File "./myq-garage.py", line 57, in <module> USERNAME = config.get('main', 'USERNAME') File "/usr/lib/python2.7/ConfigParser.py", line 330, in get raise NoSectionError(section) ConfigParser.NoSectionError: No section: 'main' However, changing it back to [config.read('config.ini')] works in the terminal but not in ISY. Any idea what I am doing wrong here? Thanks for all your help.

Hi xKing, Disregard the issue I mentioned above regarding the new file. I forgot to declare the full path on the config file as you instructed earlier. After adding /home/pi/node/config.ini on the config.read line, it is working now. I will keep you posted on the myqtoken file issue. I still have the TOKENTTL set to 8. Thanks

Hi xKing, I downloaded the file and the ISY network resource commands is not responding with the new file. However, it is working if I run the command ./myq-garage.py open [doorname] via terminal.

Hi xKing, after 58 minutes I started getting this error and the garage will not respond at this time. See error below 2017-03-04 12:53:13,503 ERROR Traceback (most recent call last): 2017-03-04 12:53:13,503 ERROR File "/home/pi/node/myq-garage.p ", line 407, in <module> 2017-03-04 12:53:13,504 ERROR gdoor_main() 2017-03-04 12:53:13,504 ERROR File "/home/pi/node/myq-garage.p ", line 396, in gdoor_main 2017-03-04 12:53:13,505 ERROR print(doorname + ' not found in av ilable doors.') 2017-03-04 12:53:13,505 ERROR UnboundLocalError 2017-03-04 12:53:13,505 ERROR : 2017-03-04 12:53:13,505 ERROR local variable 'doorname' referenc d before assignment 2017-03-04 14:37:59,209 INFO ================================== TARTED================================== 2017-03-04 14:41:08,850 INFO ================================== TARTED================================== pi@raspberrypi:~/node/logs $

OMG xKing... after changing the TOKENTTL to 8, it is now working without deleting the file. I've been checking it every minute to see where it will break.. but so far, its been 26 minutes since myqtoken.json file was created and still working. Just for my understanding, do you know why changing it to 8 made a difference?

I noticed that it stops responding between 10 to 15 minutes after the myqtoken.json file was created. For sure its good at least 8 minutes.

Hi xKing, Please disregard that error message that i provided in the above comment. I just replicated the issue and actually the commands from the either the Terminal or Network Resource in ISY will not respond to the garage door. I just looked at the log and all it shows is this. Not sure what the means but in order for the garage door to respond to the commands, the token file must be deleted. Somehow the token seems to not able to get a new token when it expires. 2017-03-03 20:53:55,261 INFO ==================================STARTED================================== 2017-03-03 20:54:37,143 INFO ==================================STARTED================================== 2017-03-03 20:55:13,465 INFO ==================================STARTED==================================

If the file exists, the garage door will not respond regardless if the command is run from the Terminal or Network Resource in ISY. I am basically getting this error message: 2017-03-01 18:21:50,377 ERROR Traceback (most recent call last): 2017-03-01 18:21:50,377 ERROR File "/home/pi/node/myq-garage.py", line 407, in <module> 2017-03-01 18:21:50,378 ERROR gdoor_main() 2017-03-01 18:21:50,378 ERROR File "/home/pi/node/myq-garage.py", line 396, in gdoor_main 2017-03-01 18:21:50,379 ERROR print(doorname + ' not found in available doors.') 2017-03-01 18:21:50,379 ERROR UnboundLocalError 2017-03-01 18:21:50,379 ERROR : 2017-03-01 18:21:50,379 ERROR local variable 'doorname' referenced before assignment

Hi xKing, Here is the result from the ls -la /tmp root@raspberrypi:~# ls -la /tmp total 624 drwxrwxrwt 14 root root 4096 Mar 3 18:28 . drwxr-xr-x 21 root root 4096 Oct 23 15:26 .. -rw-r--r-- 1 pi pi 566459 Mar 3 18:28 cloud-print-connector srwxr-xr-x 1 pi pi 0 Feb 28 21:33 cloud-print-connector-monitor.sock drwx------ 2 pi pi 4096 Feb 28 21:32 dhcpcd-(null) drwxrwxrwt 2 root root 4096 Feb 28 21:32 .font-unix drwxrwxrwt 2 root root 4096 Feb 28 21:32 .ICE-unix srwxr-xr-x 1 pi pi 0 Feb 28 21:32 .menu-cached-:0-pi -rw------- 1 pi pi 93 Mar 3 18:28 myqtoken.json srwxr-xr-x 1 pi pi 0 Feb 28 21:32 .pcmanfm-socket--0-pi drwx------ 2 root root 4096 Feb 28 21:32 pulse-PKdhtXMmr18n drwx------ 2 pi pi 4096 Feb 28 21:32 ssh-oqIsvg9tmD9E drwx------ 2 pi pi 4096 Feb 28 21:32 ssh-Yo2MOcnXwp3g drwx------ 3 root root 4096 Feb 28 21:32 systemd-private-f8bc8ad405b641e5a97c881569d15787-colord.service-Eihu69 drwx------ 3 root root 4096 Mar 3 07:35 systemd-private-f8bc8ad405b641e5a97c881569d15787-cups.service-gDB9XS drwx------ 3 root root 4096 Feb 28 21:32 systemd-private-f8bc8ad405b641e5a97c881569d15787-rtkit-daemon.service-B5pspF drwxrwxrwt 2 root root 4096 Feb 28 21:32 .Test-unix -r--r--r-- 1 root root 11 Feb 28 21:32 .X0-lock drwxrwxrwt 2 root root 4096 Feb 28 21:32 .X11-unix drwxrwxrwt 2 root root 4096 Feb 28 21:32 .XIM-unix it doesn't look like the file is getting created as root anymore. Another observation I noticed is that the myqtoken.json file only gets created as soon as I make a call to myq-garage.py from the ISY Network Resource. My Network Resource setting in ISY is as follows: Command Type: tcp Host: <isy_iip_address> Port: <nodelink_port_nbr> Mode: C Escaped When I run the network resource from ISY, it will communicate with the NodeLink Relay Server which will call the myq.garage.py to run with proper arguments [open/close/status] [doorname]. For now, I created this shell script #!/bin/sh file=/tmp/myqtoken.json if [ -f "$file" ] ; then rm -f "$file" fi and setup crontab -e to * * * * * /home/pi/node/del_myqtoken.sh to delete the file if it exist. This cron is running every minute to see if there is a file there. I know that this isn't really fixing a root cause, but for now, it is working. However, any guidance you may have to identify the root cause is greatly appreciated.

Hi xKing, I changed the line in my rc.local per your instructions. However, it is still not working. The file still needs to be deleted in order for the command to respond. Is it bad to run contab -e every 1 min to delete the file? Please advise. pi@raspberrypi:~ $ ps -ef | grep mono root 1237 1 0 Feb28 ? 00:00:00 su pi -c mono /home/pi/node/NodeLink.exe pi 1244 1237 5 Feb28 ? 01:11:12 mono /home/pi/node/NodeLink.exe pi 3283 3267 0 20:04 pts/0 00:00:00 grep --color=auto mono

Thanks xKing. I will give this a try when I get home tonight. Thanks for your help. I've learned so much from you

Hi xKing, The Nodelink run on mono. The program is executed as follows: mono ~/node/NodeLink.exe However, I added this line on the rc.local so that when I reboot the raspberry pi, it will automatically launch the program. mono /home/pi/node/NodeLink.exe & Hope you can help me change the ownership from this info. Thanks again.

Hi xKing, Here is the result pi@raspberrypi:~ $ ps -ef | grep mono root 978 1 5 Feb26 ? 01:44:16 mono /home/pi/node/NodeLink.exe pi 9439 9392 0 20:15 pts/0 00:00:00 grep --color=auto mono Looks like the NodeLink.exe is showing as root. how do I fix that. Larry

Hi xKing, Yes you are right... the myqtoken.json is getting root ownership because the config.xml for Nodelink is set as root ownership. I just changed that to pi as well the myq-garage.log and now everytime the myqtoken.json is created.. it is being created as pi ownership. I will continue to monitor it. I disabled the cron job that I was running to delete the file and see how this one will go. Thanks again

Hi xKing, I checked it again since it stopped working again. The myq-garage.log seems like it is retaining the ownership as pi and NOT root. However, the myqtoken.json must be deleted each time when it stops working. I am not sure why this file is causing it to stop working. Any ideas?

Hi Jimbo and xKing, Deleting the myqtoken.json file worked as long as the myq-garage.log file is under pi ownership. I am not sure what is triggering this to change. This morning when i checked the ownership of the file, it is back to root again. Could you help explain what is causing this to keep reverting back to root? Also, could you explain how the myqtoken.json file got created if it is not needed? I just want to understand kinda understand this more. Thanks again for all your help. Larry

Hi xKing, I changed the permission owner and group to pi per your instruction as well as the permission to 0755. Below is the error message from the log. 2017-02-25 17:59:45,567 ERROR Traceback (most recent call last): 2017-02-25 17:59:45,567 ERROR File "./myq-garage.py", line 407, in <module> 2017-02-25 17:59:45,568 ERROR gdoor_main() 2017-02-25 17:59:45,568 ERROR File "./myq-garage.py", line 373, in gdoor_main 2017-02-25 17:59:45,568 ERROR myq = MyQ() 2017-02-25 17:59:45,569 ERROR File "./myq-garage.py", line 224, in __init__ 2017-02-25 17:59:45,569 ERROR self.read_token() 2017-02-25 17:59:45,569 ERROR File "./myq-garage.py", line 250, in read_token 2017-02-25 17:59:45,570 ERROR self.login() 2017-02-25 17:59:45,570 ERROR File "./myq-garage.py", line 277, in login 2017-02-25 17:59:45,570 ERROR self.save_token() 2017-02-25 17:59:45,570 ERROR File "./myq-garage.py", line 240, in save_token 2017-02-25 17:59:45,571 ERROR f = open(self.tokenfname,"w") 2017-02-25 17:59:45,571 ERROR IOError 2017-02-25 17:59:45,571 ERROR : 2017-02-25 17:59:45,572 ERROR [Errno 13] Permission denied: '/tmp/myqtoken.json'