TFay

Excellent!! I’ll upgrade and report back with the appropriate logging.

Excellent! Thanks so much! I totally get the end of year craziness. No worries! -Ted

Hi, he's been pretty responsive to others, including me, but I believe he's gone a lot with work, and this week was Thanksgiving, so I would encourage you to be patient in terms of awaiting a response. NodeLink has a number of great features, and I think it's great that he's put it out there for the community. Happy holidays to you!

My apologies, I didn't see your response until this morning. I had check the forum a few times this weekend for a notice you'd responded, and didn't see one, but I should have checked the thread itself, as I didn't have the "follow topic" slider set. 😕 I have disabled all but the set of plugins in HomeSeer that I believe are required for testing, and also removed the CAI WebControl device from NodeLink to reduce extraneous log entries. I have configured the following devices in HomeSeer H4, for which NodeLink has created corresponding nodes in the ISY-994i. "SS01 - Tuya Smart Socket" n001_hs1_v678 Smart Socket devices managed via Tuya HS4 plugin Works properly (on/off) from HomeSeer HS4 interface Does not yet respond to control from ISY via NodeLink Does not yet display on/off status properly in ISY (always shows off) "Virtual Device 01" n001_hs1_v690 HS4 native virtual device created for testing purposes Does not yet respond to control from ISY via NodeLink Does not yet display on/off status properly in ISY (always shows off) "Sample Plugin Linked to SS01" n001_hs1_v696 HS4 Sample Plugin-based switch Linked to "SS01 - Tuya Smart Socket" E.g. when "Sample Plugin..." is triggered on, it then triggers "SS01..." on as a linked device. Properly controls SS01 on/off from HS4 interface Does not yet respond to control from ISY via NodeLink Does not yet display on/off status properly in ISY (always shows off) "Test Thermostat" n001_hs1_v656 HS4 native virtual thermostat device created for testing purposes Does not yet respond to control from ISY via NodeLink Does not yet display on/off status properly in ISY (always shows off) I have attached the full, unedited logs of all log entries cited below as .txt files. As the NodeLink startup includes a lot of detail, I have included only what I believe to be the relevant sections of the NodeLink startup log (NodeLink Log 01) here within the text of this post. The remaining entries after that are unedited. With debug set for HomeSeer in NodeLink and displayed on the Main page, attached are the log results from a fresh restart of NodeLink. --->----------NodeLink Log 01 -------------> [[[[[[[[[START OF BOOT LOG REMOVED TO REDUCE SPACE - See attachment "NodeLink-HS4 - NodeLink Log 01.txt" for full log entry for this section]]]]]]]]]]]]]] <!-- === Homeseer ============================================================ --> <nodeDef id="Homeseer" nls="108HS" > <sts> <st id="ST" editor="I_HEARTBEAT" /> </sts> <cmds> <accepts> <cmd id="QUERY" /> </accepts> </cmds> </nodeDef> <nodeDef id="hsDoorLock" nls="111DL" > <sts> <st id="ST" editor="I_DOOR" /> <st id="GV1" editor="I_BATTERY" /> <st id="GV2" editor="I_DSC_USER" /> <st id="GV3" editor="I_DOOR_INFO" /> </sts> <cmds> <accepts> <cmd id="QUERY" /> <cmd id="LOCK" /> <cmd id="UNLOCK" /> </accepts> </cmds> </nodeDef> <nodeDef id="hsLeakSensor" nls="169LS" > <sts> <st id="ST" editor="I_LEAK_SENSOR" /> <st id="GV1" editor="I_BATTERY" /> <st id="GV2" editor="I_TEMP_1" /> </sts> <cmds> <accepts> <cmd id="QUERY" /> </accepts> </cmds> </nodeDef> <nodeDef id="hsSwitch" nls="121SW" > <sts> <st id="ST" editor="I_SWITCH" /> </sts> <cmds> <accepts> <cmd id="QUERY" /> <cmd id="ON" /> <cmd id="OFF" /> </accepts> </cmds> </nodeDef> <nodeDef id="hsDimmer" nls="121D" > <sts> <st id="ST" editor="I_DIMMER" /> </sts> <cmds> <accepts> <cmd id="VAL"> <p id="" editor="I_DIMMER" init="ST" /> </cmd> <cmd id="QUERY" /> <cmd id="ON" /> <cmd id="OFF" /> </accepts> </cmds> </nodeDef> <nodeDef id="hsVirtual" nls="121V" > <sts> <st id="ST" editor="I_VIRTUAL" /> </sts> <cmds> <accepts> <cmd id="QUERY" /> <cmd id="ON" /> <cmd id="OFF" /> </accepts> </cmds> </nodeDef> <nodeDef id="hsPlug" nls="121PG" > <sts> <st id="ST" editor="I_SWITCH" /> <st id="GV1" editor="I_GEM_V" /> <st id="GV2" editor="I_GEM_A" /> <st id="GV3" editor="I_GEM_W" /> <st id="GV4" editor="I_GEM_WH" /> </sts> <cmds> <accepts> <cmd id="QUERY" /> <cmd id="ON" /> <cmd id="OFF" /> </accepts> </cmds> </nodeDef> [[[[[[[[[REMOVED TO SACE SPACE - See attachment "NodeLink-HS4 - NodeLink Log 01.txt" for full log entry for this section]]]]]]]]]]]]]] ND-Homeseer-NAME = Homeseer Controller ND-Homeseer-ICON = GenericCtl ND-hsDoorLock-NAME = Door Lock ND-hsDoorLock-ICON = DoorLock ST-111DL-GV1-NAME = Battery ST-111DL-GV2-NAME = User ST-111DL-GV3-NAME = Action CMD-111DL-LOCK-NAME = Lock CMD-111DL-UNLOCK-NAME = Unlock ND-hsSwitch-NAME = Switch ND-hsSwitch-ICON = LampAndSwitch CMD-121SW-ON-NAME = On CMD-121SW-OFF-NAME = Off ND-hsDimmer-NAME = Dimmer ND-hsDimmer-ICON = LampAndSwitch CMD-121D-VAL-NAME = Value CMD-121D-ON-NAME = On CMD-121D-OFF-NAME = Off ND-hsVirtual-NAME = Virtual ND-hsVirtual-ICON = Input CMD-121V-ON-NAME = On CMD-121V-OFF-NAME = Off ND-hsLeakSensor-NAME = Leak Sensor ND-hsLeakSensor-ICON = Irrigation ST-169LS-GV1-NAME = Battery ST-169LS-GV2-NAME = Temperature ND-hsPlug-NAME = Wall Plug Switch ND-hsPlug-ICON = LampAndSwitch ST-121PG-GV1-NAME = Volts ST-121PG-GV2-NAME = Amps ST-121PG-GV3-NAME = Watts ST-121PG-GV4-NAME = kWH CMD-121PG-ON-NAME = On CMD-121PG-OFF-NAME = Off ND-InternetWeather-NAME = Internet Current Weather ND-InternetWeather-ICON = Weather ND-InternetWeatherForecast-NAME = Internet Weather Forecast ND-InternetWeatherForecast-ICON = Weather (profiles/family/10/profile/1/download/nls/en_us.txt) 2022-11-21 11:03:19 - ISY Send: Variable hs1-ST added to queue (Val: 1, QS: 1) 2022-11-21 11:03:19 - ISY Send: Variable hs1_v690-ST added to queue (Val: 0.0, QS: 2) 2022-11-21 11:03:19 - HS: Connected - Credentials Sent [hs1] 2022-11-21 11:03:19 - ISY Send: Variable hs1_v656-ST added to queue (Val: 0.0, QS: 3) 2022-11-21 11:03:19 - HS: Data - ok [hs1] 2022-11-21 11:03:19 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:03:19 - ISY Send: Variable hs1_v678-ST added to queue (Val: 0.0, QS: 4) 2022-11-21 11:03:19 - ISY Send: Variable hs1_v696-ST added to queue (Val: 0.0, QS: 5) 2022-11-21 11:03:19 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1/report/status/ST/1/25) 2022-11-21 11:03:20 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1_v690/report/status/ST/0.0/25) 2022-11-21 11:03:20 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1_v656/report/status/ST/0.0/25) 2022-11-21 11:03:20 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1_v678/report/status/ST/0.0/25) 2022-11-21 11:03:20 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1_v696/report/status/ST/0.0/25) 2022-11-21 11:03:21 - Web Request: / <------------NodeLink Log 01 ----------<--- The corresponding log entry from HomeSeer is: --->---------HS4 Log 01-------------> 11/21/2022 11:03:19 AM HomeSeer Info ASCII connection authorization OK from IP: 192.168.0.99 for user default <------------HS4 Log 01----------<--- The Next set of log entries to appear in NodeLink are: --->----------NodeLink Log 02 -------------> 2022-11-21 11:03:24 - ISY Send: Variable data1-GV1 added to queue (Val: 11, QS: 1) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV2 added to queue (Val: 3, QS: 2) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV3 added to queue (Val: 467223, QS: 3) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV4 added to queue (Val: 1, QS: 4) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV5 added to queue (Val: 47, QS: 5) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV6 added to queue (Val: 1, QS: 6) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV7 added to queue (Val: 11, QS: 7) 2022-11-21 11:03:24 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV1/11/25) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV8 added to queue (Val: 21, QS: 7) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV9 added to queue (Val: 2022, QS: 2022-11-21 11:03:24 - ISY Send: Variable data1-GV10 added to queue (Val: 325, QS: 9) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV11 added to queue (Val: 3, QS: 10) 2022-11-21 11:03:24 - ISY Send: Variable data1-GV12 added to queue (Val: 0, QS: 11) 2022-11-21 11:03:24 - ISY Send: Variable data1_sun-GV1 added to queue (Val: 170, QS: 12) 2022-11-21 11:03:24 - ISY Send: Variable data1_sun-GV2 added to queue (Val: 35, QS: 13) 2022-11-21 11:03:24 - ISY Send: Variable data1_sun-GV3 added to queue (Val: 55, QS: 14) 2022-11-21 11:03:24 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV2/3/25) 2022-11-21 11:03:24 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV3/467223/25) 2022-11-21 11:03:24 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV4/1/25) 2022-11-21 11:03:24 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV5/47/25) 2022-11-21 11:03:24 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV6/1/25) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV7/11/47) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV8/21/25) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV9/2022/25) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV10/325/25) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV11/3/25) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV12/0/25) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1_sun/report/status/GV1/170/14) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1_sun/report/status/GV2/35/14) 2022-11-21 11:03:25 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1_sun/report/status/GV3/55/14) 2022-11-21 11:03:34 - ISY Send: Variable data1-GV3 added to queue (Val: 467224, QS: 1) 2022-11-21 11:03:34 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV3/467224/25) 2022-11-21 11:03:49 - ISY Send: Variable hs1-ST added to queue (Val: -1, QS: 1) 2022-11-21 11:03:49 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1/report/status/ST/-1/25) 2022-11-21 11:04:04 - ISY Send: Variable data1-GV2 added to queue (Val: 4, QS: 1) 2022-11-21 11:04:04 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV2/4/25) 2022-11-21 11:04:19 - ISY Send: Variable hs1-ST added to queue (Val: 1, QS: 1) 2022-11-21 11:04:19 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1/report/status/ST/1/25) 2022-11-21 11:04:34 - ISY Send: Variable data1-GV3 added to queue (Val: 467225, QS: 1) 2022-11-21 11:04:34 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV3/467225/25) 2022-11-21 11:04:49 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:05:04 - ISY Send: Variable data1-GV2 added to queue (Val: 5, QS: 1) 2022-11-21 11:05:04 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1/report/status/GV2/5/25) 2022-11-21 11:05:14 - ISY Send: Variable data1_sun-GV1 added to queue (Val: 171, QS: 1) 2022-11-21 11:05:14 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:05:19 - ISY Send: Variable hs1-ST added to queue (Val: -1, QS: 2) 2022-11-21 11:05:34 - ISY Send: Variable data1-GV3 added to queue (Val: 467226, QS: 3) 2022-11-21 11:05:44 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:05:49 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 3) 2022-11-21 11:06:04 - ISY Send: Variable data1-GV2 added to queue (Val: 6, QS: 4) 2022-11-21 11:06:14 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:06:19 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:06:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467227, QS: 4) 2022-11-21 11:06:44 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:06:49 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 4) 2022-11-21 11:07:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 7, QS: 4) 2022-11-21 11:07:14 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:07:15 - Web Request: / 2022-11-21 11:07:19 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 4) 2022-11-21 11:07:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467228, QS: 4) 2022-11-21 11:07:45 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:07:49 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:08:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 8, QS: 4) 2022-11-21 11:08:15 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/171/14) 2022-11-21 11:08:19 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 4) 2022-11-21 11:08:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467229, QS: 4) 2022-11-21 11:08:44 - ISY Send: Variable data1_sun-GV1 replaced in queue (Val: 172, QS: 4) 2022-11-21 11:08:45 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:08:49 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 4) 2022-11-21 11:09:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 9, QS: 4) 2022-11-21 11:09:15 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:09:19 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:09:29 - ISY Send: Variable data1_sun-GV2 added to queue (Val: 36, QS: 5) 2022-11-21 11:09:29 - ISY Send: Variable data1_sun-GV3 added to queue (Val: 54, QS: 6) 2022-11-21 11:09:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467230, QS: 6) 2022-11-21 11:09:46 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:09:49 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 6) 2022-11-21 11:10:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 10, QS: 6) 2022-11-21 11:10:16 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:10:19 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 6) 2022-11-21 11:10:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467231, QS: 6) 2022-11-21 11:10:47 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:10:49 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:11:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 11, QS: 6) 2022-11-21 11:11:17 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:11:19 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 6) 2022-11-21 11:11:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467232, QS: 6) 2022-11-21 11:11:48 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/172/14) 2022-11-21 11:11:49 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 6) 2022-11-21 11:12:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 12, QS: 6) 2022-11-21 11:12:14 - ISY Send: Variable data1_sun-GV1 replaced in queue (Val: 173, QS: 6) 2022-11-21 11:12:19 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/173/14) 2022-11-21 11:12:19 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:12:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467233, QS: 6) 2022-11-21 11:12:49 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/173/14) 2022-11-21 11:12:49 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 6) 2022-11-21 11:13:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 13, QS: 6) 2022-11-21 11:13:19 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 6) 2022-11-21 11:13:19 - ISY Receive: (ns/1/nodes/n001_data1_sun/report/status/GV1/173/14) 2022-11-21 11:13:27 - Web Request: / <------------NodeLink Log 02 ----------<--- When I then try to turn on the HS device "SS01 - Tuya Smart Socket" using the Universal Devices Administrative Console, the following log entries are generated: --->----------NodeLink Log 03 -------------> 2022-11-21 11:13:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467234, QS: 6) 2022-11-21 11:13:49 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:13:50 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_data1_sun/report/status/GV1/173/14) 2022-11-21 11:13:50 - ISY Receive: (ns/1/nodes/n001_hs1/report/status/ST/1/25) 2022-11-21 11:14:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 14, QS: 5) 2022-11-21 11:14:19 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 5) 2022-11-21 11:14:20 - ISY Receive: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="true"><status>200</status><reason code="0" /></RestResponse> (ns/1/nodes/n001_hs1/report/status/ST/-1/25) 2022-11-21 11:14:20 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467234/25) 2022-11-21 11:14:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467235, QS: 4) 2022-11-21 11:14:49 - ISY Send: Variable hs1-ST added to queue (Val: 1, QS: 5) 2022-11-21 11:14:50 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467235/25) 2022-11-21 11:15:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 15, QS: 5) 2022-11-21 11:15:19 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:15:20 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467235/25) 2022-11-21 11:15:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467236, QS: 5) 2022-11-21 11:15:44 - ISY Send: Variable data1_sun-GV1 added to queue (Val: 174, QS: 6) 2022-11-21 11:15:49 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 6) 2022-11-21 11:15:50 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467236/25) 2022-11-21 11:15:57 - Web Request: /isylink/nodes/n001_hs1_v678/cmd/ON 2022-11-21 11:16:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 16, QS: 6) 2022-11-21 11:16:06 - Web Request: / 2022-11-21 11:16:19 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 6) 2022-11-21 11:16:20 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467236/25) 2022-11-21 11:16:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467237, QS: 6) 2022-11-21 11:16:49 - HS: Data - 4.2.16.0 [hs1] 2022-11-21 11:16:51 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467237/25) 2022-11-21 11:17:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 17, QS: 6) 2022-11-21 11:17:19 - ISY Send: Variable hs1-ST replaced in queue (Val: -1, QS: 6) 2022-11-21 11:17:21 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467237/25) 2022-11-21 11:17:34 - ISY Send: Variable data1-GV3 replaced in queue (Val: 467238, QS: 6) 2022-11-21 11:17:49 - ISY Send: Variable hs1-ST replaced in queue (Val: 1, QS: 6) 2022-11-21 11:17:51 - ISY Receive: (ns/1/nodes/n001_data1/report/status/GV3/467238/25) 2022-11-21 11:18:04 - ISY Send: Variable data1-GV2 replaced in queue (Val: 18, QS: 6) 2022-11-21 11:18:10 - Web Request: / <------------NodeLink Log 03 ----------<--- There is no corresponding log entry generated in HomeSeer. Thoughts? Next steps? NodeLink-HS4 - NodeLink Log 01.txt NodeLink-HS4 - HS4 Log 01.txt NodeLink-HS4 - NodeLink Log 02.txt NodeLink-HS4 - NodeLink Log 03.txt

Excellent!! Happy I could help.

So I took a working IFTTT network resource I have that was formatted for JSON, and converted it back to the format you are using here, and it still works. Your host and port look correct. Can you confirm that you are using https vs. http? (in the first field at the top left just before POST) Also, ensure you have the "Use SNI" checkbox checked, and that your mode is "C Escaped." Also, as a sanity check, have tried running the trigger via curl from a terminal to see if you get a response? curl https://maker.ifttt.com/trigger/WaterLeak/with/key/<YOURKEYHERE> A success response should look something like: StatusCode : 200 StatusDescription : OK Content : Congratulations! You've fired the WaterLeak event RawContent : HTTP/1.1 200 OK

Excellent! Much appreciated!

Using default/default solved the authentication error, but I also didn't reed your device description carefully, which is that your HS support is for Zwave devices. So I suspect that may be the reason that I still can't turn on and off devices in HomeSeer, is because I am trying to control a combination of HS virtual devices (which can be used to trigger other devices), and Tuya devices. My Zwave transmitter for my RP3-based HS hasn't arrived yet. I sent you a PayPal donation, as I definitely plan to integrate your CAI WebControl device control, which is working great. By way of suggestions, if there was a way to configure Node Link to use a different set of credentials for HomeSeer other than default/default? That would be helpful from a security standpoint. Another suggestion would be that if the Node Server HS device could support could HomeSeer Virtual Devices, which can use Features -> Linked Devices to control other HD devices. Maybe this could be a way to expand control of other plugin-based devices without having to support them directly? Thanks again, great stuff!

Hmm... Did you happen to Tweet something nasty at the IFTTT CEO? Can you post a scrubbed version of the network resource you are trying to send IFTTT Webhooks? (removing your key, and any other private info). I'd be happy to try it on my end and see if IFTTT accepts it or not.

If you have an Epson projector made between 2006 and 2020 with a serial port, and you would like to control it from your ISY, these network resources will allow for ON/OFF control of a wide variety of Epson projectors. You will need a $21 Ethernet to Serial adapter, such as the USR-TCP232-302, configured as a TCP server listening on port 3629. You will also need a straight through DB-9 male to female serial cable (not null modem). "Epson Power On" can be fired off at any time, so long as the project is in Standby mode, and will remotely power on your applicable Epson projector. To power off, first trigger "Epson Prompt Init" followed by a wait of 6 seconds in your program before triggering "Epson Power Off." (It may work for you without initiating the prompt first, but I find it is more reliable this way.) "Epson Power ?" can be used from the ISY Admin Console to remotely check the current power status of your projector, but I don't know of a way to directly feed the network resource response back into an ISY variable without using an off-ISY intermediary to update an ISY variable via the REST interface. Thankfully I have not found monitoring the power state necessary for stable usage. The file "Epson 2006-2020 Power Control via Ethernet to Serial Bridge" includes network resources should work with dozens of Epson projectors from 2006-2020 (and perhaps later). I have also included network resources which include both power control and input source selection for the following long-throw Cinema models: Epson EMP-TW2000, ProCinema 1080UB, and HomeCinema 1080UB models Epson EMP-TW1000, ProCinema 1080, and HomeCinema 1080 models For other models, at this link you can find a spreadsheet you can use as a reference to find your projector model and map the appropriate source inputs to the binary command to switch to that input. ESC/VP21 Command User’s Guide License Agreement for Home Projectors | Epson US The "Epson 2006-2020 Power Control via Ethernet to Serial Bridge" network resources should work for all of the following Epson projector models: EH-TW750/TW740 PL-HC740HD/HC1040/HC640 Home Cinema 660/760HD/1060 EH/CH-TW650/610 EH-TW540 PL-HC740HD/HC1040/HC640 EH-TW410/TW490/TW495 PL-HomeCinema 725HD/730HD EH/CH-TW570 EH-TW400/TW480/TW490C/TW470C PL-Home Cinema 710HD/707 EH-TW5825/TW5705 CH-TW5800T/TW5700T Home Cinema 2250 EH/CH-TW5820/TW5800/TW5750/TW5700 HomeCinema2250/2200 EH/CH-TW5650/TW5600/TW5400 PL-HomeCinema2150/2100 EH/CH-TW5350/TW5300/TW5210 PL-HomeCinema2040/2045 EH-TW5200/PL-HomeCinema 2030 EH-TW5100/PL-HomeCinema2000 EH-TW6100/HomeCinema 3020/3020+/TW6510C/TW5910/TW5810C EH-TW6100W/TW6515C/PL-HomeCinema3020e EH-TW6000/HC3010/3010+/TW6500C/TW5900/TW5800C EH-TW6000W/PL-HC3010e/TW6550C EH-TW3500/2900 PL-HomeCinema 8100/9100 EH-TW2800/TW3000/TW3800 PL-HomeCinema 6100/ProCinema 7100 EF-12 EF-10/11 EH-TW7100/TW7000 CH-TZ3000/TW7000 Home Cinema 3800/3810/3200 EH/CH-TW6700/TW6700W/TW6800/TW6800W/TW6300 PL-HC3900/HC3700/HC3710/HC3100 EH/CH-TW6600/TW6600W/TW6200 PL-HomeCinema 3500/3510/3600e/3000 EH/CH-LS100 Home Cinema LS100 EH-LS500W/LS500B PC 6050UB/HC 5050UB/HC 5050UBe EH/CH-TW7400 PC4050/HC4010 EH/CH-TW9300/TW9300W/TW8300/TW8300W/TW7300 PL-PC6040UB/4040UB/HC5040UB/5040UBe EH/CH-TW7200/8200/8200W/9200/9200W PL-ProCinema 5030UB/UBe, PL-ProCinema 6030UB PL-ProCinema 4030 EH-TW8100/PL-HC5020UB/TW8510C/TW9100/PL-PC6020UB/TW9510C EH-TW9100W/HC5020UBe/TW8515C/TW9100W/TW9515C EH-TW8000/PL-HomeCinema5010/EH-TW8500C/TW9000/PL ProCinema6010/TW9500C EH-TW8000W/PL-HomeCinema5010e/EH-TW9000W EH-TW3600/3200/3300C/3700C/3850C PL-HomeCinema 8350/8345/ProCinema 9350 EH-TW4400/TW4500/TW5500/TW5850C PL-HomeCinema 8500UB/8700UB, ProCinema 9500UB/9700UB EH-TW4000/TW5000/TW5800C PL-HomeCinema 6500UB/ProCinema 7500UB EMP-TW2000 PL-ProCinema 1080UB/HomeCinema 1080UB EMP-TW1000/TW980 PL-ProCinema 1080/HomeCinema 1080 EH/CH-LS12000B/LS11000W EH/CH-LS10500 PL-ProCinemaLS10500 EH-LS9600W/PL-ProCinema LS9600e EH/CH-LS10000/PL-ProCinema LS10000 EH-R1000/R2000/R3000C/R4000/R5000C PL-HomeCinema 21000/ProCinema 31000/61000 Epson 2006-2020 Power Control via Ethernet to Serial Bridge.zip Epson TW1000 Pro-Home Cinema 1080 - Power and Sources.zip Epson TW2000 Pro-Home Cinema 1080UB - Power and Sources.zip

Hi, I'm trying out NodeLInk, and this looks great! Nicely done! However, I appear to be having issues authenticating to HomeSeer, even though I have HomeSeer configured as follows: No Password Required for Local (same subnet) Login Enable Control with JSON (Required for Alexa/Google Home/IFTTT/Etc.) Enable Control using ASCII Commands NodeLink was setup sudo from user "pi," which is configured as an admin in HomeSeer. NodeLink and HomeSeer are both currently runnign on the same Raspberry Pi RP3. I have tried using both a setup of NodeLink on the same Raspberry Pi (RP3) as HomeSeer, as well as NodeLink running separately on a Windows host, both with the same results, which is that I am unable to control On/Off commands from the ISY that are HS nodes created via NodeLink. I would love to get this working, so any suggestions of what to tweak would be highly appreciated! I believe the applicable sections of the log are: 2022-11-11 03:53:59 - HS: Data - error, no user or bad pass and 2022-11-11 03:54:38 - Web Request: /isylink/nodes/n001_hs1_v678/cmd/ON 2022-11-11 03:54:38 - HS: Data - error, not authorized This looks to me like an obvious authorization issue, but I'm stumped as to where I've gone wrong. I don't see anywhere in NodeLink to set a username and password for HomeSeer, and NodeLInk is successfully creating HS nodes in the ISY. So it seems to be in the path of the WebRequest from the ISY -> NodeLink -> Homeseer when I try to turn an HS device on or off from an ISY node. The following is my error log from NodeLink currently configured on the same RP3 as Homeseer. Thanks in advance! HS4 NodeLink auth topic 01.txt

Do you have any network resources besides IFTTT that use DNS URL's out on the internet? If so, you might try those and see if you're having issues with any other services/servers, or if the problem is specific to your IFTTT requests.

This pack of network resources will control your ESP32-based Dingtian IOT Relay (found here in the 4 channel version). For two channel, just delete the extra network resources, and for 8, just copy and adjust the channel number in the URL. These relays have some pretty cool features, like scheduling, and configurable actions on trigger input. The inputs can also be monitored via http (GUI or http calls), but these network resources simply control the on/off state the of the relays. These boards are superior to the Nuvoton M0517LBN based relay boards you can find all over Amazon and ebay, as the Dingtian IOT Relays have a configurable MAC address, rather than a fixed MAC address that is duplicated on every Nuvoton M0517LBN based relay board. This means you can have more than one Dingtian IOT Relay board on your network. They have both an onboard RJ45 LAN port and WiFi. As these are based on ESP32 WROOM32D chipsets, you can also program them yourself using their SDK, or in theory roll your own customer firmware using standard ESP32 coding (similar to Arduino). Dingtian (dingtian-tech.com) An example of the these boards in a wide variety of form factors can be found here: Ethernet Relay Network Wifi Switch Modbus MQTT TCP UDP Web HTTP Schedule Task CA | eBay (I'm not the seller, if you're wondering. ) Dingtian IOT Relay - 4 Channel.zip

I was having issues last night, but I made two changes and got it working. 1.) First I tried updating my URL to match the current IFTTT documentation, adding the word "json" and giving it a dummy json payload: /trigger/projector_on/json/with/key/ - This had no immediate effect (if any) 2.) Second, I tried changing my DNS in the ISY System/Network Settings to use 4.2.2.1 instead of 8.8.8.8, rebooted, and was back in business.

These sample ISY network resources can be used to launch PowerShell scripts on a Windows host that can speak to guests are your gate, welcome you home, inform you if the garage door has been left open, etc. You can create scripts that are as simple or as complex as you'd like. I have attached a pair of simple scripts that announce if your garage door is open or closed. I have also attached a rather complex set of scripts and supporting files that when triggered by a Weigand Access Controller will grab the swipe log from the Access Controller, parse it, and use that to announce a customer welcome to that specific gate user, as well as inform them if rain is expected (based off .json forecast data from Weather Underground). To launch PowerShell scrips remotely, you will need to make sure the scripts are in your $PATH, and configure PSExec from Microsoft's PSTools collection to allow for remote execution. You will also need to replace the basic authentication in these network resources with username and password for your Windows host. You will also need to enable something like HTTPListener (by Steve Lee) with settings such as those in the attached HttpListener_Start.ps1 script. https://learn.microsoft.com/en-us/sysinternals/downloads/pstools Simple HTTP api for Executing PowerShell Scripts - PowerShell Team (microsoft.com) I've attached the HTTPListener script by Steve Lee, as the link to his PowerShell script in the blog above appears to be no longer working. There may be a newer version available, or alternative solutions, but this works well with ISY. ISY PowerShell_Script_Launchers.zipHTTPListener-1.0.2.modified.zip Sample Powershell Scripts.zip HttpListener_Start.ps1 HTTPListener-1.0.2.modified.zip