3 hours ago3 hr I installed a T2000 and enabled "Local API". It also had an option for "API Time" which I left "off" initially. I tried Discovery with no Custom Parameters and then with Custom Parameters "Key" = "Upstairs", "Value" = "192.168.1.9" and never was able to find the T2000.I ran the following commands from eisy command prompt.curl http://192.168.1.9/query/status - {"error":true, "reason":"No Response for Requested URI"}curl http://192.168.1.9/query/info - {"name":"Upstairs HVAC","mode":0,"state":0,"activestage":0,"fan":0,"fanstate":0,"tempunits":0,"schedule":0,"schedulepart":1,"away":0,"spacetemp":70.0,"heattemp":73.0,"cooltemp":78.0,"hum_setpoint":25,"dehum_setpoint":80,"cooltempmin":35.0,"cooltempmax":99.0,"heattempmin":35.0,"heattempmax":99.0,"setpointdelta":2,"availablemodes":0}curl http://192.168.1.9/query/sensors - {"sensors": [{"name":"Thermostat","temp":70},{"name":"Space Temp","temp":70}]}curl http://192.168.1.9/ - {"api_ver": 7, "type": "residential", "model": "T2000", "firmware": "5.65"}I powered T2000 Off and back On after setting API to On and reran all Discovery tests with same results.I fear this thermostat or firmware does not support "/query/status". Which from reading other posts, may make this thermostat unusable by "VenstarCT". Can anyone confirm "query/status" is required or that the T2000 is not supported?
Create an account or sign in to comment