here are trace logs. the "pre" includes attempting a setpoint change and was downloaded immediately before attempting a status update on the thermostat device. the "post" log is everything after the plugin crashes.
Announcement
Collapse
No announcement yet.
Setpoint changes do not happen at TCC/Honeywell
Collapse
This topic is closed.
X
X
-
Originally posted by shill View PostI'm sorry but that's got to be an issue with your account or redlink or thermostat connection or something. The plugin is successfully communicating and Honeywell is accepting the request and saying "ok". Nothing more I can really do
I'll keep thinking about it in case I get any other ideas though.
Comment
-
Just had a thought, though if this is right I can't say why it would have ever worked.... you said "heat only". I don't have any experience working with such a unit, so I suppose there's a chance the format of a setpoint change for such a device might be different. Are you familiar with Google Chrome's "Inspect" (aka Developer Tools) window? What would help is if you could:- Log in and go to your thermostat
- Hit F12
- Go to the "Network" tab
- Change the setpoint (this should generate some lines in the Network tab)
- Click the red circle to stop recording
- Right-click on the table in the bottom of the network tab and choose "save all as HAR with content"
- Share the HAR file with me
Comment
-
update on the plugin crash on device status update, that seems to only happen when the plugin log is set to trace level
Originally posted by shill View PostJust had a thought, though if this is right I can't say why it would have ever worked.... you said "heat only". I don't have any experience working with such a unit, so I suppose there's a chance the format of a setpoint change for such a device might be different. Are you familiar with Google Chrome's "Inspect" (aka Developer Tools) window? What would help is if you could:- Log in and go to your thermostat
- Hit F12
- Go to the "Network" tab
- Change the setpoint (this should generate some lines in the Network tab)
- Click the red circle to stop recording
- Right-click on the table in the bottom of the network tab and choose "save all as HAR with content"
- Share the HAR file with me
and yeah i was wondering about that too, if maybe the way the reworked version of the plugin generates the request is slightly different from the way the 1.x versions did. would sure be nice if they provided an API and docs for you!Attached Files
Comment
-
Ok - maybe now we're on to something!
Here's what the plugin sends:
{
"DeviceID":4845008,
"SystemSwitch":null,
"HeatSetpoint":65.0,
"CoolSetpoint": 0.0,
"HeatNextPeriod":null,
"CoolNextPeriod ":null,
"StatusHeat":0,
"StatusCool":0,
"FanMode":null
}
Here's what your device (or, I assume, any device without cool mode) sends:
{
"DeviceID": 4845008,
"SystemSwitch": null,
"HeatSetpoint": 58,
"CoolSetpoint": null,
"HeatNextPeriod": null,
"CoolNextPeriod": null,
"StatusHeat": null,
"StatusCool": null,
"FanMode": null
}
Sending 0 instead of "null" could be the issue. I'll work something up and try and get it posted as beta this weekend for you to try out. If that doesn't work, you can actually add me as a user to your thermostat without having to share your credentials, but let's hold on to that as a next step only if necessary.
Comment
-
I just put 4.2.0.8 (and 3.2.0.8) out as Beta. You'll have to "Add" vs "Manage" to get it, but it addresses the difference in the commands being sent to match what was in your HAR file, and plugged a hole where an error could happen when trace logging is enabled and an unsuccessful response from Honeywell is received (usually because you've logged in too many times by restarting the plugin rapidly).
Comment
-
Sorry for not getting back about this sooner; the thermostat is at a ski rental and it's been booked solid. I was finally able to check things out last weekend.
Tried 4.2.0.8 and still have the same issue.
Replaced the HomeSeer system and moved from arm to x64 ubuntu, new install of HS4 4.2.16.0, this plugin version 4.2.1.2 and still have the same issue with the plugin logging in successfully, able to see setpoint changes made at thermostat/TCC app/TCC website and the indoor temperature, but setpoint changes made in the plugin not being reflected at TCC and eventually the plugin device setpoint going back to the existing setpoint on the thermostat/TCC after the next scheduled status update.
Comment
-
what TCC website sends
Code:{ "DeviceID":4845008, "SystemSwitch":null, "HeatSetpoint":64, "CoolSetpoint":null, "HeatNextPeriod":null, "CoolNextPeriod":null, "StatusHeat":null, "StatusCool":null, "FanMode":null }
Code:{ "DeviceID":4845008, "SystemSwitch":null, "HeatSetpoint":66.0, "CoolSetpoint":null, "HeatNextPeriod":null, "CoolNextPeriod":null, "StatusHeat":0, "StatusCool":null, "FanMode":null }
Comment
-
Originally posted by acabtp View Postwhat TCC website sends
Code:{ "DeviceID":4845008, "SystemSwitch":null, "HeatSetpoint":64, "CoolSetpoint":null, "HeatNextPeriod":null, "CoolNextPeriod":null, "StatusHeat":null, "StatusCool":null, "FanMode":null }
Code:{ "DeviceID":4845008, "SystemSwitch":null, "HeatSetpoint":66.0, "CoolSetpoint":null, "HeatNextPeriod":null, "CoolNextPeriod":null, "StatusHeat":0, "StatusCool":null, "FanMode":null }
Comment
Comment