www.homeseer.com    
 

Go Back   HomeSeer Message Board > Thermostat / HVAC Plug-ins > Thermostat / HVAC Discussion > Sinope Thermostat (3P)

Sinope Thermostat (3P) Discussions related to the Sinope Thermostat plugin by Spud.

Reply
 
Thread Tools Display Modes
  #21  
Old August 7th, 2017, 11:35 AM
JoelWener JoelWener is offline
Seer
 
Join Date: Oct 2012
Location: Canada
Posts: 19
I have re-added the load controllers, as they dissapeared after re-starting the pluggin.

Here are some lines from the log file.


Aug-07 11:29:54 AM Sinope DEBUG Unknown cmd id 0x243
Aug-07 11:29:54 AM Sinope DEBUG RX:55 00 1C 00 43 02 3D 00 00 00 0B 00 00 17 54 01 00 0E 02 0D 00 00 02 00 00 03 0D 00 00 02 00 00 D5
Aug-07 11:29:53 AM Sinope DEBUG Unknown cmd id 0x243
Aug-07 11:29:53 AM Sinope DEBUG RX:55 00 14 00 43 02 3C 00 00 00 0B 00 00 17 54 01 00 06 00 10 00 00 01 00 A1
Aug-07 11:29:53 AM Sinope DEBUG Request 159, device ID 87063: answer received
Aug-07 11:29:53 AM Sinope DEBUG RX:55 00 14 00 45 02 9F 00 00 00 0A 01 00 17 54 01 00 06 00 10 00 00 01 00 76
Aug-07 11:29:53 AM Sinope DEBUG Request 159, device ID 87063: ACK received
Aug-07 11:29:53 AM Sinope DEBUG RX:55 00 0E 00 45 02 9F 00 00 00 00 00 01 17 54 01 00 00 30
Aug-07 11:29:53 AM Sinope DEBUG TX:55 00 18 00 44 02 9F 00 00 00 00 00 00 00 00 00 00 17 54 01 00 06 00 10 00 00 01 00 EC
Aug-07 11:29:53 AM Device Control Device: Heat Pump Master Output Intensity to Off (0) by/from: CAPI Control Handler

Aug-07 11:28:46 AM Sinope DEBUG System.NullReferenceException: Object reference not set to an instance of an object. at HSPI_Sinope.SinopeApp.DataAnswerEventHandler(Object sender, DataAnswerEventArgs e)
Aug-07 11:28:46 AM Sinope ERROR Object reference not set to an instance of an object.
Aug-07 11:28:46 AM Sinope DEBUG Request 133, device ID 87051: answer received
Aug-07 11:28:46 AM Sinope DEBUG RX:55 00 23 00 45 02 85 00 00 00 0A 01 00 0B 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 FB
Aug-07 11:28:45 AM Sinope DEBUG Request 133, device ID 87051: ACK received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 0E 00 45 02 85 00 00 00 00 00 01 0B 54 01 00 00 03
Aug-07 11:28:45 AM Sinope DEBUG System.NullReferenceException: Object reference not set to an instance of an object. at HSPI_Sinope.SinopeApp.DataAnswerEventHandler(Object sender, DataAnswerEventArgs e)
Aug-07 11:28:45 AM Sinope ERROR Object reference not set to an instance of an object.
Aug-07 11:28:45 AM Sinope DEBUG Request 132, device ID 87063: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 23 00 45 02 84 00 00 00 0A 01 00 17 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 1F
Aug-07 11:28:45 AM Sinope DEBUG TX:55 00 27 00 44 02 85 00 00 00 00 00 00 00 00 00 00 0B 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 90
Aug-07 11:28:45 AM Sinope INFO Device 87051 is a LoadController
Aug-07 11:28:45 AM Sinope DEBUG Request 131, device ID 87051: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 18 00 41 02 83 00 00 00 0A 01 00 0B 54 01 00 0A 01 00 00 00 05 78 00 C9 09 00 A7
Aug-07 11:28:45 AM Sinope DEBUG System.NullReferenceException: Object reference not set to an instance of an object. at HSPI_Sinope.SinopeApp.DataAnswerEventHandler(Object sender, DataAnswerEventArgs e)
Aug-07 11:28:45 AM Sinope ERROR Object reference not set to an instance of an object.
Aug-07 11:28:45 AM Sinope DEBUG Request 130, device ID 87063: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 23 00 45 02 82 00 00 00 0A 01 00 17 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 57
Aug-07 11:28:45 AM Sinope DEBUG Request 132, device ID 87063: ACK received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 0E 00 45 02 84 00 00 00 00 00 01 17 54 01 00 00 FA
Aug-07 11:28:45 AM Sinope DEBUG TX:55 00 27 00 44 02 84 00 00 00 00 00 00 00 00 00 00 17 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 E7
Aug-07 11:28:45 AM Sinope INFO Device 87063 is a LoadController
Aug-07 11:28:45 AM Sinope DEBUG Request 129, device ID 87063: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 18 00 41 02 81 00 00 00 0A 01 00 17 54 01 00 0A 01 00 00 00 05 78 00 C9 09 00 0B
Aug-07 11:28:45 AM Sinope DEBUG Request 112, device ID 2315: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 15 00 41 02 70 00 00 00 0A 01 00 0B 09 00 00 07 04 02 00 00 02 FC 7F FA
Aug-07 11:28:45 AM Sinope DEBUG Request 111, device ID 2315: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 14 00 41 02 6F 00 00 00 0A 01 00 0B 09 00 00 06 11 02 00 00 01 02 F9
Aug-07 11:28:45 AM Sinope DEBUG Request 110, device ID 2315: answer received
Aug-07 11:28:45 AM Sinope DEBUG RX:55 00 14 00 41 02 6E 00 00 00 0A 01 00 0B 09 00 00 06 20 02 00 00 01 00 51
Aug-07 11:28:44 AM Sinope DEBUG Request 109, device ID 2315: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 15 00 41 02 6D 00 00 00 0A 01 00 0B 09 00 00 07 08 02 00 00 02 DC 05 CC
Aug-07 11:28:44 AM Sinope DEBUG Request 108, device ID 2315: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 15 00 41 02 6C 00 00 00 0A 01 00 0B 09 00 00 07 03 02 00 00 02 7B 08 C6
Aug-07 11:28:44 AM Sinope DEBUG Request 93, device ID 5261: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 15 00 41 02 5D 00 00 00 0A 01 00 8D 14 00 00 07 08 02 00 00 02 34 08 2E
Aug-07 11:28:44 AM Sinope DEBUG Request 92, device ID 5261: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 15 00 41 02 5C 00 00 00 0A 01 00 8D 14 00 00 07 03 02 00 00 02 86 08 11
Aug-07 11:28:44 AM Sinope DEBUG Request 131, device ID 87051: ACK received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 0E 00 41 02 83 00 00 00 00 00 01 0B 54 01 00 00 57
Aug-07 11:28:44 AM Sinope DEBUG TX:55 00 16 00 40 02 83 00 00 00 00 00 00 00 00 00 00 0B 54 01 00 04 01 00 00 00 52
Aug-07 11:28:44 AM Sinope DEBUG Requesting device model info
Aug-07 11:28:44 AM Sinope INFO Device 87051 added
Aug-07 11:28:44 AM Sinope DEBUG Device link report received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 07 00 16 01 00 0B 54 01 00 0F
Aug-07 11:28:44 AM Sinope DEBUG Request 91, device ID 2315: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 15 00 41 02 5B 00 00 00 0A 01 00 0B 09 00 00 07 04 02 00 00 02 FC 7F A3
Aug-07 11:28:44 AM Sinope DEBUG Request 90, device ID 2315: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 14 00 41 02 5A 00 00 00 0A 01 00 0B 09 00 00 06 11 02 00 00 01 02 8E
Aug-07 11:28:44 AM Sinope DEBUG Request 89, device ID 2315: answer received
Aug-07 11:28:44 AM Sinope DEBUG RX:55 00 14 00 41 02 59 00 00 00 0A 01 00 0B 09 00 00 06 20 02 00 00 01 00 72
Aug-07 11:28:43 AM Sinope DEBUG Request 88, device ID 2315: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 15 00 41 02 58 00 00 00 0A 01 00 0B 09 00 00 07 08 02 00 00 02 DC 05 8E
Aug-07 11:28:43 AM Sinope DEBUG Request 87, device ID 2315: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 15 00 41 02 57 00 00 00 0A 01 00 0B 09 00 00 07 03 02 00 00 02 7B 08 DC
Aug-07 11:28:43 AM Sinope DEBUG Request 69, device ID 2315: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 14 00 41 02 45 00 00 00 0A 01 00 0B 09 00 00 06 11 02 00 00 01 02 A1
Aug-07 11:28:43 AM Sinope DEBUG Request 68, device ID 2315: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 14 00 41 02 44 00 00 00 0A 01 00 0B 09 00 00 06 20 02 00 00 01 00 09
Aug-07 11:28:43 AM Sinope DEBUG Request 67, device ID 2315: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 15 00 41 02 43 00 00 00 0A 01 00 0B 09 00 00 07 08 02 00 00 02 DC 05 12
Aug-07 11:28:43 AM Sinope DEBUG Request 66, device ID 2315: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 15 00 41 02 42 00 00 00 0A 01 00 0B 09 00 00 07 03 02 00 00 02 7B 08 18
Aug-07 11:28:43 AM Sinope DEBUG Request 130, device ID 87063: ACK received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 0E 00 45 02 82 00 00 00 00 00 01 17 54 01 00 00 33
Aug-07 11:28:43 AM Sinope DEBUG TX:55 00 27 00 44 02 82 00 00 00 00 00 00 00 00 00 00 17 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 CC
Aug-07 11:28:43 AM Sinope INFO Device 87063 is a LoadController
Aug-07 11:28:43 AM Sinope DEBUG Request 64, device ID 87063: answer received
Aug-07 11:28:43 AM Sinope DEBUG RX:55 00 18 00 41 02 40 00 00 00 0A 01 00 17 54 01 00 0A 01 00 00 00 05 78 00 C9 09 00 6A
Aug-07 11:28:42 AM Sinope DEBUG Request 54, device ID 5899: answer received
Aug-07 11:28:42 AM Sinope DEBUG RX:55 00 15 00 41 02 36 00 00 00 0A 01 00 0B 17 00 00 07 08 02 00 00 02 34 08 DE
Aug-07 11:28:42 AM Sinope DEBUG Request 53, device ID 5899: answer received
Aug-07 11:28:42 AM Sinope DEBUG RX:55 00 15 00 41 02 35 00 00 00 0A 01 00 0B 17 00 00 07 03 02 00 00 02 86 08 4A
Aug-07 11:28:42 AM Sinope DEBUG Request 52, device ID 5261: answer received
Aug-07 11:28:42 AM Sinope DEBUG RX:55 00 15 00 41 02 34 00 00 00 0A 01 00 8D 14 00 00 07 04 02 00 00 02 FC 7F 4F
Aug-07 11:28:42 AM Sinope DEBUG Request 51, device ID 5261: answer received
Aug-07 11:28:42 AM Sinope DEBUG RX:55 00 14 00 41 02 33 00 00 00 0A 01 00 8D 14 00 00 06 11 02 00 00 01 02 E5
Aug-07 11:28:41 AM Sinope DEBUG Request 50, device ID 5261: answer received
Aug-07 11:28:41 AM Sinope DEBUG RX:55 00 14 00 41 02 32 00 00 00 0A 01 00 8D 14 00 00 06 20 02 00 00 01 00 4D

Aug-07 11:28:48 AM Sinope DEBUG System.NullReferenceException: Object reference not set to an instance of an object. at HSPI_Sinope.SinopeApp.DataAnswerEventHandler(Object sender, DataAnswerEventArgs e)
Aug-07 11:28:48 AM Sinope ERROR Object reference not set to an instance of an object.
Aug-07 11:28:48 AM Sinope DEBUG Request 135, device ID 87051: answer received
Aug-07 11:28:48 AM Sinope DEBUG RX:55 00 23 00 45 02 87 00 00 00 0A 01 00 0B 54 01 00 15 01 0F 00 00 10 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 C3

After re-adding the load controllers, the status is updating for now. I will check within 24 hours to see if still operational.


More Debug Info: Aug-07 11:29:30 AM Sinope DEBUG Request 158, device ID 25531: answer received
Aug-07 11:29:30 AM Sinope DEBUG RX:55 00 14 00 41 02 9E 00 00 00 0A 01 00 BB 63 00 00 06 00 07 00 00 01 00 E0
Aug-07 11:29:30 AM Sinope DEBUG Request 157, device ID 87051: answer received
Aug-07 11:29:30 AM Sinope DEBUG RX:55 00 14 00 41 02 9D 00 00 00 0A 01 00 0B 54 01 00 06 00 10 00 00 01 00 E1
Aug-07 11:29:30 AM Sinope DEBUG Request 156, device ID 87063: answer received
Aug-07 11:29:30 AM Sinope DEBUG RX:55 00 14 00 41 02 9C 00 00 00 0A 01 00 17 54 01 00 06 00 10 00 00 01 64 83
Aug-07 11:29:30 AM Sinope DEBUG Request 155, device ID 34146: answer received
Aug-07 11:29:30 AM Sinope DEBUG RX:55 00 15 00 41 02 9B 00 00 00 0A 01 00 62 85 00 00 07 04 02 00 00 02 FC 7F 98
Aug-07 11:29:29 AM Sinope DEBUG Request 154, device ID 34146: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 14 00 41 02 9A 00 00 00 0A 01 00 62 85 00 00 06 11 02 00 00 01 00 E4
Aug-07 11:29:29 AM Sinope DEBUG Request 153, device ID 34146: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 14 00 41 02 99 00 00 00 0A 01 00 62 85 00 00 06 20 02 00 00 01 00 16
Aug-07 11:29:29 AM Sinope DEBUG Request 152, device ID 34146: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 15 00 41 02 98 00 00 00 0A 01 00 62 85 00 00 07 08 02 00 00 02 FC 7F 7A
Aug-07 11:29:29 AM Sinope DEBUG Request 151, device ID 34146: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 15 00 41 02 97 00 00 00 0A 01 00 62 85 00 00 07 03 02 00 00 02 ED 07 55
Aug-07 11:29:29 AM Sinope DEBUG Request 150, device ID 5899: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 15 00 41 02 96 00 00 00 0A 01 00 0B 17 00 00 07 04 02 00 00 02 FC 7F D6
Aug-07 11:29:29 AM Sinope DEBUG Request 149, device ID 5899: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 14 00 41 02 95 00 00 00 0A 01 00 0B 17 00 00 06 11 02 00 00 01 02 7E
Aug-07 11:29:29 AM Sinope DEBUG Request 148, device ID 5899: answer received
Aug-07 11:29:29 AM Sinope DEBUG RX:55 00 14 00 41 02 94 00 00 00 0A 01 00 0B 17 00 00 06 20 02 00 00 01 00 D6
Aug-07 11:29:28 AM Sinope DEBUG Request 147, device ID 5899: answer received
Aug-07 11:29:28 AM Sinope DEBUG RX:55 00 15 00 41 02 93 00 00 00 0A 01 00 0B 17 00 00 07 08 02 00 00 02 34 08 C9
Aug-07 11:29:28 AM Sinope DEBUG Request 146, device ID 5899: answer received
Aug-07 11:29:28 AM Sinope DEBUG RX:55 00 15 00 41 02 92 00 00 00 0A 01 00 0B 17 00 00 07 03 02 00 00 02 83 08 B7
Aug-07 11:29:28 AM Sinope DEBUG Request 145, device ID 5261: answer received
Aug-07 11:29:28 AM Sinope DEBUG RX:55 00 15 00 41 02 91 00 00 00 0A 01 00 8D 14 00 00 07 04 02 00 00 02 FC 7F 58
Aug-07 11:29:28 AM Sinope DEBUG Request 144, device ID 5261: answer received
Aug-07 11:29:28 AM Sinope DEBUG RX:55 00 14 00 41 02 90 00 00 00 0A 01 00 8D 14 00 00 06 11 02 00 00 01 02 AB
Aug-07 11:29:28 AM Sinope DEBUG Request 143, device ID 5261: answer received
Aug-07 11:29:28 AM Sinope DEBUG RX:55 00 14 00 41 02 8F 00 00 00 0A 01 00 8D 14 00 00 06 20 02 00 00 01 00 06
Aug-07 11:29:27 AM Sinope DEBUG Request 142, device ID 5261: answer received
Aug-07 11:29:27 AM Sinope DEBUG RX:55 00 15 00 41 02 8E 00 00 00 0A 01 00 8D 14 00 00 07 08 02 00 00 02 34 08 0D
Aug-07 11:29:27 AM Sinope DEBUG Request 141, device ID 5261: answer received
Aug-07 11:29:27 AM Sinope DEBUG RX:55 00 15 00 41 02 8D 00 00 00 0A 01 00 8D 14 00 00 07 03 02 00 00 02 84 08 B3
Aug-07 11:29:27 AM Sinope DEBUG Request 140, device ID 2315: answer received
Aug-07 11:29:27 AM Sinope DEBUG RX:55 00 15 00 41 02 8C 00 00 00 0A 01 00 0B 09 00 00 07 04 02 00 00 02 FC 7F D1
Aug-07 11:29:27 AM Sinope DEBUG Request 139, device ID 2315: answer received
Aug-07 11:29:27 AM Sinope DEBUG RX:55 00 14 00 41 02 8B 00 00 00 0A 01 00 0B 09 00 00 06 11 02 00 00 01 02 D7
Aug-07 11:29:27 AM Sinope DEBUG Request 138, device ID 2315: answer received
Aug-07 11:29:27 AM Sinope DEBUG RX:55 00 14 00 41 02 8A 00 00 00 0A 01 00 0B 09 00 00 06 20 02 00 00 01 00 7F
Aug-07 11:29:27 AM Sinope DEBUG Request 137, device ID 2315: answer received
Aug-07 11:29:27 AM Sinope DEBUG RX:55 00 15 00 41 02 89 00 00 00 0A 01 00 0B 09 00 00 07 08 02 00 00 02 DC 05 06
Aug-07 11:29:26 AM Sinope DEBUG Request 136, device ID 2315: answer received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 15 00 41 02 88 00 00 00 0A 01 00 0B 09 00 00 07 03 02 00 00 02 7D 08 72
Aug-07 11:29:26 AM Sinope DEBUG Request 158, device ID 25531: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 157, device ID 87051: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 9D 00 00 00 00 00 01 0B 54 01 00 00 B3 55 00 0E 00 41 02 9E 00 00 00 00 00 01 BB 63 00 00 00 35
Aug-07 11:29:26 AM Sinope DEBUG Request 156, device ID 87063: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 9C 00 00 00 00 00 01 17 54 01 00 00 4A
Aug-07 11:29:26 AM Sinope DEBUG Request 155, device ID 34146: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 154, device ID 34146: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 9A 00 00 00 00 00 01 62 85 00 00 00 40 55 00 0E 00 41 02 9B 00 00 00 00 00 01 62 85 00 00 00 1D
Aug-07 11:29:26 AM Sinope DEBUG Request 153, device ID 34146: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 99 00 00 00 00 00 01 62 85 00 00 00 A7
Aug-07 11:29:26 AM Sinope DEBUG Request 152, device ID 34146: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 151, device ID 34146: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 97 00 00 00 00 00 01 62 85 00 00 00 88 55 00 0E 00 41 02 98 00 00 00 00 00 01 62 85 00 00 00 FA
Aug-07 11:29:26 AM Sinope DEBUG Request 150, device ID 5899: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 96 00 00 00 00 00 01 0B 17 00 00 00 78
Aug-07 11:29:26 AM Sinope DEBUG Request 149, device ID 5899: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 148, device ID 5899: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 94 00 00 00 00 00 01 0B 17 00 00 00 C2 55 00 0E 00 41 02 95 00 00 00 00 00 01 0B 17 00 00 00 9F
Aug-07 11:29:26 AM Sinope DEBUG Request 147, device ID 5899: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 93 00 00 00 00 00 01 0B 17 00 00 00 56
Aug-07 11:29:26 AM Sinope DEBUG Request 146, device ID 5899: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 145, device ID 5261: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 91 00 00 00 00 00 01 8D 14 00 00 00 0A 55 00 0E 00 41 02 92 00 00 00 00 00 01 0B 17 00 00 00 0B
Aug-07 11:29:26 AM Sinope DEBUG Request 144, device ID 5261: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 90 00 00 00 00 00 01 8D 14 00 00 00 57
Aug-07 11:29:26 AM Sinope DEBUG Request 143, device ID 5261: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 8F 00 00 00 00 00 01 8D 14 00 00 00 EE
Aug-07 11:29:26 AM Sinope DEBUG Request 142, device ID 5261: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 141, device ID 5261: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 140, device ID 2315: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 8C 00 00 00 00 00 01 0B 09 00 00 00 4C 55 00 0E 00 41 02 8D 00 00 00 00 00 01 8D 14 00 00 00 54 55 00 0E 00 41 02 8E 00 00 00 00 00 01 8D 14 00 00 00 B3
Aug-07 11:29:26 AM Sinope DEBUG Request 139, device ID 2315: ACK received
Aug-07 11:29:26 AM Sinope DEBUG Request 138, device ID 2315: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 8A 00 00 00 00 00 01 0B 09 00 00 00 85 55 00 0E 00 41 02 8B 00 00 00 00 00 01 0B 09 00 00 00 D8
Aug-07 11:29:26 AM Sinope DEBUG Request 137, device ID 2315: ACK received
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 89 00 00 00 00 00 01 0B 09 00 00 00 62
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 9E 00 00 00 00 00 00 00 00 00 00 BB 63 00 00 04 00 07 00 00 24
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 9D 00 00 00 00 00 00 00 00 00 00 0B 54 01 00 04 00 10 00 00 A7
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 9C 00 00 00 00 00 00 00 00 00 00 17 54 01 00 04 00 10 00 00 2C
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 9B 00 00 00 00 00 00 00 00 00 00 62 85 00 00 04 04 02 00 00 54
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 9A 00 00 00 00 00 00 00 00 00 00 62 85 00 00 04 11 02 00 00 51
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 99 00 00 00 00 00 00 00 00 00 00 62 85 00 00 04 20 02 00 00 9A
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 98 00 00 00 00 00 00 00 00 00 00 62 85 00 00 04 08 02 00 00 C8
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 97 00 00 00 00 00 00 00 00 00 00 62 85 00 00 04 03 02 00 00 E1
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 96 00 00 00 00 00 00 00 00 00 00 0B 17 00 00 04 04 02 00 00 AE
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 95 00 00 00 00 00 00 00 00 00 00 0B 17 00 00 04 11 02 00 00 F3
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 94 00 00 00 00 00 00 00 00 00 00 0B 17 00 00 04 20 02 00 00 60
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 93 00 00 00 00 00 00 00 00 00 00 0B 17 00 00 04 08 02 00 00 DA
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 92 00 00 00 00 00 00 00 00 00 00 0B 17 00 00 04 03 02 00 00 7C
Aug-07 11:29:26 AM Sinope DEBUG Request 136, device ID 2315: ACK received
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 91 00 00 00 00 00 00 00 00 00 00 8D 14 00 00 04 04 02 00 00 7A
Aug-07 11:29:26 AM Sinope DEBUG RX:55 00 0E 00 41 02 88 00 00 00 00 00 01 0B 09 00 00 00 3F
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 90 00 00 00 00 00 00 00 00 00 00 8D 14 00 00 04 11 02 00 00 7F
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 8F 00 00 00 00 00 00 00 00 00 00 8D 14 00 00 04 20 02 00 00 AD
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 8E 00 00 00 00 00 00 00 00 00 00 8D 14 00 00 04 08 02 00 00 FF
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 8D 00 00 00 00 00 00 00 00 00 00 8D 14 00 00 04 03 02 00 00 01
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 8C 00 00 00 00 00 00 00 00 00 00 0B 09 00 00 04 04 02 00 00 9A
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 8B 00 00 00 00 00 00 00 00 00 00 0B 09 00 00 04 11 02 00 00 77
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 8A 00 00 00 00 00 00 00 00 00 00 0B 09 00 00 04 20 02 00 00 E4
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 89 00 00 00 00 00 00 00 00 00 00 0B 09 00 00 04 08 02 00 00 EE
Aug-07 11:29:26 AM Sinope DEBUG TX:55 00 16 00 40 02 88 00 00 00 00 00 00 00 00 00 00 0B 09 00 00 04 03 02 00 00 48

Last edited by JoelWener; August 7th, 2017 at 11:38 AM. Reason: added more debug
Reply With Quote
  #22  
Old August 7th, 2017, 02:24 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by JoelWener View Post
Hi,

I have tested the load control devices. The commands seem to work on, off, but the status of the load controllers are not properly being reflected in homeseer. The devices are actually off (per schedule), but they show on in homeseer. I have also noticed that my Neviweb is going offline since I started to use this version.

- Also restarted pluggin, and load controllers dissapeared from the list?

- The way the load controllers are being created in homeseer, they are being recognized as a Thermostat. Should probably be created as a standard device or something that doesn't show up as a Thermostat.
I think I have fixed most of the problems you reported as well as the errors I saw in your logs in version 3.0.0.8 (available in first post).
Please test it and let me know. You may want to restart from scratch (i.e delete your Load Controllers devices and delete the LOAD_CONTROLLERS section in Sinope.ini)
Thanks
Reply With Quote
  #23  
Old August 30th, 2017, 10:26 AM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by JoelWener View Post
Hi,

I have tested the load control devices. The commands seem to work on, off, but the status of the load controllers are not properly being reflected in homeseer. The devices are actually off (per schedule), but they show on in homeseer. I have also noticed that my Neviweb is going offline since I started to use this version.

- Also restarted pluggin, and load controllers dissapeared from the list?

- The way the load controllers are being created in homeseer, they are being recognized as a Thermostat. Should probably be created as a standard device or something that doesn't show up as a Thermostat.
Is everything ok now, with version 3.0.0.8?
thanks
Reply With Quote
  #24  
Old August 30th, 2017, 07:53 PM
JoelWener JoelWener is offline
Seer
 
Join Date: Oct 2012
Location: Canada
Posts: 19
Quote:
Originally Posted by spud View Post
Is everything ok now, with version 3.0.0.8?
thanks
Hi,

For the most part everything seems to work. There is one exception. In the summer, I normally turn off the breaker for some of the thermostats (heat). While this doesn't cause a problem for Neviweb, it seems to cause a problem with the plug-in. The plug-in seems to continuously retry contacting the devices, and causes the Neviweb gateway to go offline. A timeout feature needs to be built into the program to stop retrying offline devices after a certain amount of time. This timeout resets if Homeseer is restarted it the plug-in is restarted..? Or retries each hour ???

If I put the other thermostats back online or disable the plug-in the gateway comes back online.

Thanks
Joel
Reply With Quote
  #25  
Old October 12th, 2017, 08:12 AM
Michel Michel is offline
Seer Deluxe
 
Join Date: Aug 2002
Location: Quebec, Canada
Posts: 125
Spud,

Still on trial with 3.0.0.8 but lately the post .368 core HS engine instability has grabbed all my available time.

This AM I noticed that whenever HS gets restarted, any Thermostats previously located are not in the config page anymore. The devices remains but with no more updates. The GT-125 remains OK.

I looked at the Sinope.ini file and changes made to the config page don't seem to be saved in this file.

Here's what the ini file looks like after Locating (1) thermostat.

[SINOPE]
gt125_ip=xxx.xxx.x.xxx
gt125_id=xxxxxxxxxxxxxxxx
api_key=xxxxxxxxxxxxxxxx

I would have expected to see additional lines for each T-Stat

Any idea what to look for?
Reply With Quote
  #26  
Old October 12th, 2017, 08:51 AM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by Michel View Post
Spud,

Still on trial with 3.0.0.8 but lately the post .368 core HS engine instability has grabbed all my available time.

This AM I noticed that whenever HS gets restarted, any Thermostats previously located are not in the config page anymore. The devices remains but with no more updates. The GT-125 remains OK.

I looked at the Sinope.ini file and changes made to the config page don't seem to be saved in this file.

Here's what the ini file looks like after Locating (1) thermostat.

[SINOPE]
gt125_ip=xxx.xxx.x.xxx
gt125_id=xxxxxxxxxxxxxxxx
api_key=xxxxxxxxxxxxxxxx

I would have expected to see additional lines for each T-Stat

Any idea what to look for?
It's not normal you should see a THERMOSTATS section in your ini file something like this:

Code:
[THERMOSTATS]
13438###type=LineVoltageThermostat
13438###name=Master Bedroom
11086###type=LineVoltageThermostat
11086###name=Living Room
Rich recently changed the way HS3 read and write to ini files, the problem is probably linked to that.
Someone reported that if the section does not exist yet the SavceINISettings doesn't work
https://forums.homeseer.com/showthre...06#post1326706

I don't know if that has been fixed yet.
Reply With Quote
  #27  
Old October 12th, 2017, 09:41 AM
Michel Michel is offline
Seer Deluxe
 
Join Date: Aug 2002
Location: Quebec, Canada
Posts: 125
Quote:
Originally Posted by spud View Post

Code:
[THERMOSTATS]
13438###type=LineVoltageThermostat
13438###name=Master Bedroom
Are the "#" the real characters or masking info. If as is, I will try to manually add the section with my own devices until HS gets a definitive fix.
Reply With Quote
  #28  
Old October 12th, 2017, 11:13 AM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by Michel View Post
Are the "#" the real characters or masking info. If as is, I will try to manually add the section with my own devices until HS gets a definitive fix.
they are real characters, but to add those lines manually you need to know the id of each thermostat.

Rich told me the changes for read/write to ini are not in the latest release version (.368), so if you run this version and add the thermostats again (by pressing the 2 buttons on your physical device) then they should be re-added and written to the ini file.
Reply With Quote
  #29  
Old November 5th, 2017, 12:01 AM
rkirstuk rkirstuk is offline
Seer
 
Join Date: Oct 2017
Location: Canada
Posts: 19
stelpro

is there any support or plugins for the stelpro thermostats ?
Reply With Quote
  #30  
Old November 6th, 2017, 07:33 AM
Michel Michel is offline
Seer Deluxe
 
Join Date: Aug 2002
Location: Quebec, Canada
Posts: 125
Quote:
Originally Posted by rkirstuk View Post
is there any support or plugins for the stelpro thermostats ?
The Stelpro Ki thermostats comes in two flavours. Z-Wave and ZigBee. If you go with the Z-wave version it is directly supported by the HS built-in Z-wave plug-in. No additional one needed.
Reply With Quote
  #31  
Old January 3rd, 2018, 08:43 PM
ebenisteriecst ebenisteriecst is offline
Viewer
 
Join Date: Jan 2018
Location: QC
Posts: 1
Multiple GT125

Does the plug-in allow to add multiple GT125. I have 3 GT125, one in the house and one in each of my garage.
Reply With Quote
  #32  
Old January 4th, 2018, 06:52 AM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by ebenisteriecst View Post
Does the plug-in allow to add multiple GT125. I have 3 GT125, one in the house and one in each of my garage.
It's not possible with the current version version of the plugin, but I will make it support multiple instances in the next version, so that you can start one instance of the plugin for each GT125.
Reply With Quote
  #33  
Old January 4th, 2018, 11:02 AM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by ebenisteriecst View Post
Does the plug-in allow to add multiple GT125. I have 3 GT125, one in the house and one in each of my garage.
In version 3.0.0.10 available here, I added support for multiple instances
Reply With Quote
  #34  
Old February 9th, 2018, 02:28 PM
IMBillRE IMBillRE is offline
Seer
 
Join Date: Jan 2016
Location: Phila, PA
Posts: 10
Is there anything existing or coming like this that would work with my Stelpro KI (STZW402WB+) Z-Wave Electric Baseboard Thermostat? I'm trying to control the baseboard heat using a multi-sensor rather than the built in thermostat.
Thanks
Reply With Quote
  #35  
Old February 9th, 2018, 02:36 PM
spud's Avatar
spud spud is online now
Moderator
 
Join Date: Jan 2012
Location: Canada
Posts: 4,823
Quote:
Originally Posted by IMBillRE View Post
Is there anything existing or coming like this that would work with my Stelpro KI (STZW402WB+) Z-Wave Electric Baseboard Thermostat? I'm trying to control the baseboard heat using a multi-sensor rather than the built in thermostat.
Thanks
since it is a ZWave device, it should work natively with the ZWave plugin
Reply With Quote
  #36  
Old February 9th, 2018, 06:09 PM
Michel Michel is offline
Seer Deluxe
 
Join Date: Aug 2002
Location: Quebec, Canada
Posts: 125
Quote:
Originally Posted by IMBillRE View Post
... I'm trying to control the baseboard heat using a multi-sensor rather than the built in thermostat.
Thanks
I've used these Stelpro and felt the control precision (PID) was fantastic. I'm curious to know why you don't want to rely on the built-in sensor.
Reply With Quote
  #37  
Old February 13th, 2018, 12:25 AM
IMBillRE IMBillRE is offline
Seer
 
Join Date: Jan 2016
Location: Phila, PA
Posts: 10
Quote:
Originally Posted by Michel View Post
I've used these Stelpro and felt the control precision (PID) was fantastic. I'm curious to know why you don't want to rely on the built-in sensor.
Michel, I have a somewhat odd situation. There is actually one heat register that runs between two rooms. (yah - bad design) When the door that separates the rooms is open it does not seem to be any problem. When is shut it means that the other room (bedroom) often ends up too hot or too cold. A sensor in the room where the Stelpro is not will hopefully help to minimize this problem.

So far I put a door sensor on the door between the rooms which when closed enables an event that reads the temperature from the multi-sensor in the bedroom. I'm not really experienced at script writing or whatever it might take to make this work better. Right now I just have the event tell stelpro to bump up to 80 degrees to heat and drop to 60 degrees to stop heating. So when the door is shut we're constantly fluctuating between full power or no power which means temps shoot up high then drop low. I'm hoping to figure out a way to reliably take advantage of the subtle adjustments to power to the heat register that Stelpro does so well on it's own.
Reply With Quote
  #38  
Old February 13th, 2018, 10:57 AM
Michel Michel is offline
Seer Deluxe
 
Join Date: Aug 2002
Location: Quebec, Canada
Posts: 125
Thanks for the detailed info. Bad design will always give bad results. In my brother's bathroom they installe the baseboard just under the thermostat...

The nice thing with HS is that you can do a lot with the events tool without writing a single line of code, as long as you are good at visualizing the If-then-do concepts and results. You can combine multiple events and avoid having them fight each other by creating virtual devices and updating it status with one of your Then statement.

Good luck.
Reply With Quote
  #39  
Old February 20th, 2018, 11:44 AM
IMBillRE IMBillRE is offline
Seer
 
Join Date: Jan 2016
Location: Phila, PA
Posts: 10
Quote:
Originally Posted by Michel View Post
Thanks for the detailed info. Bad design will always give bad results. In my brother's bathroom they installe the baseboard just under the thermostat...

The nice thing with HS is that you can do a lot with the events tool without writing a single line of code, as long as you are good at visualizing the If-then-do concepts and results. You can combine multiple events and avoid having them fight each other by creating virtual devices and updating it status with one of your Then statement.

Good luck.
Michel,
I appreciate your insights! If it works well I'll post the events.
Thanks
Bill

Sent from my SM-N950U using Tapatalk
Reply With Quote
Reply

Bookmarks

Tags
electric baseboard, line voltage thermostats, sinopé

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
UPB Plug-in - Beta Testing spud UPB plugin by Spud (3P) 102 December 30th, 2017 11:57 PM
Ecobee Plug-in - Beta Testing spud Ecobee (3P) 106 November 29th, 2017 09:22 AM
HS3 Beta Plug-In Available for Testing YoYo IRTrans (3P) 92 November 6th, 2017 09:10 PM
EnvisaLink DSC Plug-in - HS3 Beta Testing spud Envisalink DSC Plugin (3P) 52 May 30th, 2017 07:23 AM
Sinope Plug-in - User Guide spud Sinope Thermostat (3P) 2 March 16th, 2017 08:47 AM


All times are GMT -4. The time now is 09:38 PM.


Copyright HomeSeer Technologies, LLC