JayC Posted July 20, 2016 Posted July 20, 2016 Request New 3rd Party Pin doesn't work. Running NodeLink as a docker. Any tips?
rccoleman Posted July 20, 2016 Posted July 20, 2016 When you say that it doesn't work, do you not see a new code show up in the log? Clicking the button doesn't have any directly visible effect, only new entries in the log with the code to enter on the Ecobee website.
io_guy Posted July 20, 2016 Posted July 20, 2016 Check and see if you're using my new Dockerfile. It needs to install mono-complete.
JayC Posted July 20, 2016 Author Posted July 20, 2016 Check and see if you're using my new Dockerfile. It needs to install mono-complete. https://hub.docker.com/r/jcreynolds/nodelink/~/dockerfile/ When you say that it doesn't work, do you not see a new code show up in the log? Clicking the button doesn't have any directly visible effect, only new entries in the log with the code to enter on the Ecobee website. Thanks, this makes more sense. Does it take a bit to kick in? I've added the pin to ecobee and states nodelink is in myapps. However the page isn't updating with data. 2016-07-19 23:08:29 - ISY NodeLink Server v0.5.7 started 2016-07-19 23:08:29 - ISY resolved to 192.168.1.200 2016-07-19 23:08:29 - Web config server started (http://172.17.0.10:8090) 2016-07-19 23:08:29 - ISY Error: Error getting web response from the ISY (Error getting response stream (ReadDone2): ReceiveFailure) 2016-07-19 23:08:31 - Ecobee: New 3rd party app code is mm95 [ecobee1] 2016-07-19 23:08:31 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1] 2016-07-19 23:11:32 - Ecobee: Error refreshing tokens - if this continues try setting a new app pin [ecobee1] 2016-07-19 23:14:33 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1/report/status/GV2/-1/25) 2016-07-19 23:15:03 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1/report/status/GV2/-1/25) 2016-07-19 23:15:33 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1/report/status/GV2/-1/25) Is it supposed to create a new app code every time nodelink is restarted?
JayC Posted July 20, 2016 Author Posted July 20, 2016 Just gotta stay patient . However, does a new pin get generated on restart? I saw it once but it may have been a coincidence as I may have generated a pin and restarted. Thermostat Variables Name Home HeartBeat -1 HVAC Mode Cool HVAC State Cooling Schedule Mode Schedule Schedule Type Home Fan Min On Time 0 Fan State On Indoor Temperature 78.1 Indoor Humidity 52 Cool Setpoint 78 Heat Setpoint 69 Weather Temperature 71.7 Humidity 93 POP 11 High Temp 89.4 Low Temp 76.1 Sensors S1 Temp (Bedroom) 78.3 S1 Occupancy (Bedroom) 1 S2 Temp (Home) 77.9 S2 Occupancy (Home) 0
io_guy Posted July 20, 2016 Posted July 20, 2016 No, you should only need to generate the pin once. After that it saves the oauth keys and should be fine
JayC Posted July 20, 2016 Author Posted July 20, 2016 I can see the data in ISY, I also can change the setpoint from ISY and see it update on the Ecobee. However I am seeing the following errors in the logger: Also what is the Install ISY Nodes button supposed to do? By default my nodelink will add the the thermostat data into the isy. The check boxes when checked will automatically add the weather and sensors. 2016-07-20 08:32:46 - ISY NodeLink Server v0.5.7 started 2016-07-20 08:32:46 - ISY resolved to 192.168.1.200 2016-07-20 08:32:46 - Web config server started (http://172.17.0.10:8090) 2016-07-20 08:35:00 - ISY Error: Error getting web response from the ISY (Error getting response stream (ReadDone2): ReceiveFailure) 2016-07-20 08:35:35 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.6/14) 2016-07-20 08:36:05 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.7/14) 2016-07-20 08:36:35 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.7/14) 2016-07-20 08:37:06 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.7/14) 2016-07-20 08:37:36 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.7/14) 2016-07-20 08:38:06 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.7/14) 2016-07-20 08:38:36 - ISY Error: The remote server returned an error: (404) OK. (ns/1/nodes/n001_ecobee1_sen1/report/status/ST/78.7/14)
io_guy Posted July 20, 2016 Posted July 20, 2016 The readdone2 was a failure to add the new node in the ISY, hence the 404s. Keep hitting the install nodes button until the nOl001_ecobee1_sen1 node shows up in the ISY. Readdone2 is a mono bug.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.